comp.lang.fortran

• Thread Index

---

• Re: linking dll with g95
  • From: Craig Powers
• Re: FORTRAN 90/95 program reading .dat file (\\ force line continuation)
  • From: OldSchool
• paypal payment)( www.brand-clothing.com )Discount Nike Jordan 24 Shoes Manufacture
  • From: Brand clothing
• Re: Static array versus allocatable array in derived type
  • From: fj
• Re: Static array versus allocatable array in derived type
  • From: Tobias Burnus
• Re: linking dll with g95
  • From: Tobias Burnus
• Re: linking dll with g95
  • From: albert
• Re: STREAM I/O questions
  • From: glen herrmannsfeldt
• Re: Free/commercial windows Fortran compilers
  • From: analyst41
• Re: STREAM I/O questions
  • From: Ron Shepard
• Re: FORTRAN 90/95 program reading .dat file (\\ force line continuation)
  • From: Richard Maine
• Re: STREAM I/O questions
  • From: jfh
• Re: FORTRAN 90/95 program reading .dat file (\\ force line continuation)
  • From: David Duffy
• Re: FORTRAN 90/95 program reading .dat file (\\ force line continuation)
  • From: dpb
• Re: FORTRAN 90/95 program reading .dat file (\\ force line continuation)
  • From: James
• Re: FORTRAN 90/95 program reading .dat file (\\ force line continuation)
  • From: steve
• Re: linking dll with g95
  • From: e p chandler
• Re: FORTRAN 90/95 program reading .dat file (\\ force line continuation)
  • From: dpb
• Re: FORTRAN 90/95 program reading .dat file (\\ force line continuation)
  • From: Alois Steindl
• Re: linking dll with g95
  • From: acp693
• FORTRAN 90/95 program reading .dat file (\\ force line continuation)
  • From: James
• Re: linking dll with g95
  • From: acp693
• Re: linking dll with g95
  • From: steve
• Re: linking dll with g95
  • From: e p chandler
• linking dll with g95
  • From: acp693
• Re: inquire in windows - special folder / file status
  • From: dpb
• Re: Static array versus allocatable array in derived type
  • From: robin
• Re: Why is this invalid?
  • From: Steve Lionel
• Airlines
  • From: yaqub
• Re: Static array versus allocatable array in derived type
  • From: fj
• Re: Free/commercial windows Fortran compilers
  • From: John Appleyard
• Re: inquire in windows - special folder / file status
  • From: dpb
• Re: inquire in windows - special folder / file status
  • From: dpb
• Re: inquire in windows - special folder / file status
  • From: Ragu
• Re: inquire in windows - special folder / file status
  • From: Ragu
• Re: Static array versus allocatable array in derived type
  • From: fj
• Re: Static array versus allocatable array in derived type
  • From: fj
• Re: Static array versus allocatable array in derived type
  • From: Richard Maine
• Re: inquire in windows - special folder / file status
  • From: Leclerc
• Re: Static array versus allocatable array in derived type
  • From: fj
• Re: Static array versus allocatable array in derived type
  • From: Richard Maine
• Re: inquire in windows - special folder / file status
  • From: dpb
• Static array versus allocatable array in derived type
  • From: fj
• Re: Pathscale/SiCoretex Fortran fortune
  • From: JB
• Re: Pathscale/SiCoretex Fortran fortune
  • From: nmm1
• Re: inquire in windows - special folder / file status
  • From: dpb
• Re: inquire in windows - special folder / file status
  • From: Ragu
• Pathscale/SiCoretex Fortran fortune
  • From: Mikhail Kuzminsky
• Re: Free/commercial windows Fortran compilers
  • From: Bil Kleb
• Re: inquire in windows - special folder / file status
  • From: dpb
• inquire in windows - special folder / file status
  • From: Ragu
• Amisha Patel's Secret Behind Sizzling Hot Figure
  • From: yaqub
• Re: Free/commercial windows Fortran compilers
  • From: analyst41
• Re: Free/commercial windows Fortran compilers
  • From: none
• Re: cannot pass variable size array to subroutine
  • From: Thomas Koenig
• Re: Free/commercial windows Fortran compilers
  • From: Arjan
• Re: Why is this invalid?
  • From: Jared Ahern
• Re: Free/commercial windows Fortran compilers
  • From: hes selex
• Re: cannot pass variable size array to subroutine
  • From: JB
• Re: Free/commercial windows Fortran compilers
  • From: m_b_metcalf
• Re: Why is this invalid?
  • From: robert . corbett
• Re: Fortran IDE and debugger
  • From: Lurkos
• Re: Why is this invalid?
  • From: Richard Maine
• Free/commercial windows Fortran compilers
  • From: analyst41
• Re: STREAM I/O questions
  • From: Richard Maine
• Re: STREAM I/O questions
  • From: John
• Re: Why is this invalid?
  • From: Jared Ahern
• Why is this invalid?
  • From: Jared Ahern
• Re: STREAM I/O questions
  • From: glen herrmannsfeldt
• Re: STREAM I/O questions
  • From: Richard Maine
• Re: cannot pass variable size array to subroutine
  • From: robin
• Re: STREAM I/O questions
  • From: Arjen Markus
• Re: STREAM I/O questions
  • From: Arjen Markus
• STREAM I/O questions
  • From: John
• How to create tags for fortran subroutine using ctags?
  • From: SHmech
• Re: cannot pass variable size array to subroutine
  • From: Richard Maine
• Re: cannot pass variable size array to subroutine
  • From: glen herrmannsfeldt
• Re: cannot pass variable size array to subroutine
  • From: James Van Buskirk
• Re: cannot pass variable size array to subroutine
  • From: fj
• Re: cannot pass variable size array to subroutine
  • From: Richard Maine
• Re: cannot pass variable size array to subroutine
  • From: Richard Maine
• Re: cannot pass variable size array to subroutine
  • From: fj
• Re: cannot pass variable size array to subroutine
  • From: robin
• Re: cannot pass variable size array to subroutine
  • From: glen herrmannsfeldt
• Re: cannot pass variable size array to subroutine
  • From: James Van Buskirk
• Re: cannot pass variable size array to subroutine
  • From: Richard Maine
• Re: cannot pass variable size array to subroutine
  • From: Ron Shepard
• Re: cannot pass variable size array to subroutine
  • From: James Van Buskirk
• Re: cannot pass variable size array to subroutine
  • From: glen herrmannsfeldt
• Re: cannot pass variable size array to subroutine
  • From: Richard Maine
• Re: cannot pass variable size array to subroutine
  • From: fj
• Re: cannot pass variable size array to subroutine
  • From: Richard Maine
• Re: cannot pass variable size array to subroutine
  • From: glen herrmannsfeldt
• Re: cannot pass variable size array to subroutine
  • From: glen herrmannsfeldt
• Re: cannot pass variable size array to subroutine
  • From: fj
• Re: cannot pass variable size array to subroutine
  • From: fj
• Re: cannot pass variable size array to subroutine
  • From: Gordon Sande
• Re: cannot pass variable size array to subroutine
  • From: Richard Maine
• Re: cannot pass variable size array to subroutine
  • From: Richard Maine
• Re: cannot pass variable size array to subroutine
  • From: fj
• Re: the format of reading data from file
  • From: nakisa
• Re: cannot pass variable size array to subroutine
  • From: James Van Buskirk
• Re: cannot pass variable size array to subroutine
  • From: Gordon Sande
• Re: cannot pass variable size array to subroutine
  • From: fj
• Re: the format of reading data from file
  • From: fj
• Re: the format of reading data from file
  • From: m_b_metcalf
• Re: the format of reading data from file
  • From: Louis Krupp
• Re: the format of reading data from file
  • From: nakisa
• Re: the format of reading data from file
  • From: m_b_metcalf
• Re: the format of reading data from file
  • From: nakisa
• Re: the format of reading data from file
  • From: m_b_metcalf
• the format of reading data from file
  • From: nakisa
• Re: creating a library
  • From: mecej4
• Re: creating a library
  • From: rudra
• creating a library
  • From: rudra
• Health
  • From: yaqub khan82
• Re: what is wrong with this code ?
  • From: dpb
• Re: Dynamic F03 Interfaces?
  • From: Jared Ahern
• Re: what is wrong with this code ?
  • From: jfh
• Re: Dynamic F03 Interfaces?
  • From: Craig Powers
• Re: #line directive on Fortran 2003
  • From: GaryScott
• Re: #line directive on Fortran 2003
  • From: glen herrmannsfeldt
• Re: cannot pass variable size array to subroutine
  • From: Ron Shepard
• Re: #line directive on Fortran 2003
  • From: Kool
• Re: what is wrong with this code ?
  • From: dpb
• Re: #line directive on Fortran 2003
  • From: Jared Ahern
• Re: #line directive on Fortran 2003
  • From: glen herrmannsfeldt
• Dynamic F03 Interfaces?
  • From: Jared Ahern
• Re: #line directive on Fortran 2003
  • From: GaryScott
• #line directive on Fortran 2003
  • From: Kool
• Re: what is wrong with this code ?
  • From: glen herrmannsfeldt
• Re: what is wrong with this code ?
  • From: glen herrmannsfeldt
• Re: what is wrong with this code ?
  • From: Richard Maine
• Re: what is wrong with this code ?
  • From: dpb
• Re: what is wrong with this code ?
  • From: Dick Hendrickson
• Re: what is wrong with this code ?
  • From: Richard Maine
• Re: what is wrong with this code ?
  • From: David Flower
• Re: what is wrong with this code ?
  • From: dpb
• Re: Intel Fortran Compiler version 11.1 now available
  • From: Steve Lionel
• Re: what is wrong with this code ?
  • From: dpb
• Re: what is wrong with this code ?
  • From: m_b_metcalf
• Re: what is wrong with this code ?
  • From: James
• what is wrong with this code ?
  • From: VICTOR
• Re: when will gdb support variable- length arrays (VLA) for fortran or C99
  • From: Tobias Burnus
• Re: Intel Fortran Compiler version 11.1 now available
  • From: Colin Watters
• Re: How to check permissions for a directory
  • From: Arjen Markus
• Re: cannot pass variable size array to subroutine
  • From: robin
• Re: cannot pass variable size array to subroutine
  • From: robin
• Nike Jordan 11 Shoes Wholesalers Options
  • From: fei
• Re: cannot pass variable size array to subroutine
  • From: e p chandler
• Re: lapack sgesv / dgesv routines problem / cpu / stall / compile
  • From: h4rdc0d3d
• Re: cannot pass variable size array to subroutine
  • From: Richard Maine
• Re: cannot pass variable size array to subroutine
  • From: glen herrmannsfeldt
• Re: lapack sgesv / dgesv routines problem / cpu / stall / compile
  • From: Les Neilson
• Re: How to check permissions for a directory
  • From: Andris
• lapack sgesv / dgesv routines problem / cpu / stall / compile
  • From: FG
• Intel Fortran Compiler version 11.1 now available
  • From: Steve Lionel
• Re: cannot pass variable size array to subroutine
  • From: m_b_metcalf
• when will gdb support variable- length arrays (VLA) for fortran or C99
  • From: guoguo
• Re: cannot pass variable size array to subroutine
  • From: dpb
• Re: cannot pass variable size array to subroutine
  • From: pjh
• Re: cannot pass variable size array to subroutine
  • From: Philippe
• Re: cannot pass variable size array to subroutine
  • From: Gordon Sande
• cannot pass variable size array to subroutine
  • From: Philippe
• Re: new release of Sun compilers
  • From: glen herrmannsfeldt
• Re: How to check permissions for a directory
  • From: Arjen Markus
• Re: new release of Sun compilers
  • From: robert . corbett
• Re: new release of Sun compilers
  • From: robert . corbett
• How to check permissions for a directory
  • From: Andris
• making a filter using stream I/O
  • From: John
• Re: strange result of mod function
  • From: robert . corbett
• Re: new release of Sun compilers
  • From: glen herrmannsfeldt
• new release of Sun compilers
  • From: robert . corbett
• Re: Sun Fortran Survey
  • From: robert . corbett
• (paypal payment)( www.brand-clothing.com ) wholesale POLO 3 T-shirt
  • From: xxv
• Re: argument intent in C procedure bindings
  • From: Damian
• Re: strange result of mod function
  • From: Klaus Wacker
• Re: argument intent in C procedure bindings
  • From: Erik Toussaint
• Re: argument intent in C procedure bindings
  • From: Damian
• Re: argument intent in C procedure bindings
  • From: Richard Maine
• argument intent in C procedure bindings
  • From: Damian
• Re: strange result of mod function
  • From: glen herrmannsfeldt
• Re: strange result of mod function
  • From: Michael Goerz
• Re: strange result of mod function
  • From: Ron Shepard
• Re: Passing a string as argument to a (Matlab) C function
  • From: Erik Toussaint
• Re: Passing a string as argument to a (Matlab) C function
  • From: Erik Toussaint
• Re: strange result of mod function
  • From: dpb
• Re: Passing a string as argument to a (Matlab) C function
  • From: Erik Toussaint
• Re: strange result of mod function
  • From: glen herrmannsfeldt
• Re: strange result of mod function
  • From: glen herrmannsfeldt
• Re: strange result of mod function
  • From: Richard Maine
• Re: strange result of mod function
  • From: Gordon Sande
• Re: strange result of mod function
  • From: Michael Goerz
• Re: strange result of mod function
  • From: dpb
• Re: strange result of mod function
  • From: Richard Maine
• strange result of mod function
  • From: Michael Goerz
• Re: Passing a string as argument to a (Matlab) C function
  • From: Richard Maine
• Passing a string as argument to a (Matlab) C function
  • From: Erik Toussaint
• Luxury Living
  • From: yaqub khan
• Re: compaq VF consistently crashes on "add files to project"
  • From: Cheryl H Porter
• Re: Reversing Array Elements?
  • From: Dan Nagle
• Re: compaq VF consistently crashes on "add files to project"
  • From: Luka Djigas
• compaq VF consistently crashes on "add files to project"
  • From: Cheryl H Porter
• Re: Reversing Array Elements?
  • From: Richard Maine
• Re: Reversing Array Elements?
  • From: James Van Buskirk
• Re: IEEE NaN problem
  • From: jfh
• Re: Intel Fortran segfault
  • From: Jason Blevins
• Re: Reversing Array Elements?
  • From: robin
• Re: Reversing Array Elements?
  • From: robin
• Re: Intel Fortran segfault
  • From: Tim Springer
• Re: When is someone ready to be taught programming (especially Fortran)?
  • From: Dave
• Re: Intel Fortran segfault
  • From: Tim Prince
• Re: Intel Fortran segfault
  • From: Steve Lionel
• Re: Intel Fortran segfault
  • From: fj
• Intel Fortran segfault
  • From: Jason Blevins
• Re: gfortran/gcc and runtme error
  • From: Tobias Burnus
• Re: gfortran/gcc and runtme error
  • From: Richard Maine
• Re: gfortran/gcc and runtme error
  • From: Tim Prince
• Re: gfortran/gcc and runtme error
  • From: steve
• Re: gfortran/gcc and runtme error
  • From: steve
• Re: gfortran/gcc and runtme error
  • From: m_b_metcalf
• Re: gfortran/gcc and runtme error
  • From: JKB
• Re: gfortran/gcc and runtme error
  • From: Michel Olagnon
• Sun Fortran Survey
  • From: robert . corbett
• Re: gfortran/gcc and runtme error
  • From: JKB
• Re: gfortran/gcc and runtme error
  • From: robert . corbett
• gfortran/gcc and runtme error
  • From: JKB
• Re: When is someone ready to be taught programming (especially Fortran)?
  • From: Catherine Rees Lay
• Re: IEEE NaN problem
  • From: robert . corbett
• Re: IEEE NaN problem
  • From: Dick Hendrickson
• Re: Reversing Array Elements?
  • From: Richard Maine
• Re: IEEE NaN problem
  • From: Tim Prince
• Re: Reversing Array Elements?
  • From: Dick Hendrickson
• Re: Reversing Array Elements?
  • From: Dan Nagle
• Re: Reversing Array Elements?
  • From: robin
• Re: Reversing Array Elements?
  • From: robin
• IEEE NaN problem
  • From: jfh
• Re: Compaq Visual Fortran 6.6 and Matlab r2009a
  • From: Nathan
• Re: Compaq Visual Fortran 6.6 and Matlab r2009a
  • From: dpb
• Re: Compaq Visual Fortran 6.6 and Matlab r2009a
  • From: Luka Djigas
• Re: Compaq Visual Fortran 6.6 and Matlab r2009a
  • From: Nathan
• Re: Compaq Visual Fortran 6.6 and Matlab r2009a
  • From: dpb
• Re: Compaq Visual Fortran 6.6 and Matlab r2009a
  • From: dpb
• Re: Compaq Visual Fortran 6.6 and Matlab r2009a
  • From: Nathan
• Re: Compaq Visual Fortran 6.6 and Matlab r2009a
  • From: dpb
• Re: Compaq Visual Fortran 6.6 and Matlab r2009a
  • From: Nathan
• Re: Compaq Visual Fortran 6.6 and Matlab r2009a
  • From: dpb
• Re: Compaq Visual Fortran 6.6 and Matlab r2009a
  • From: Nathan
• Re: Compaq Visual Fortran 6.6 and Matlab r2009a
  • From: Nathan
• Re: Compaq Visual Fortran 6.6 and Matlab r2009a
  • From: dpb
• Re: Compaq Visual Fortran 6.6 and Matlab r2009a
  • From: Nathan
• Re: Reversing Array Elements?
  • From: Dan Nagle
• Re: Reversing Array Elements?
  • From: Dick Hendrickson
• AT&T Usenet Netnews Service Shutting Down
  • From: newsmaster
• Re: Compaq Visual Fortran 6.6 and Matlab r2009a
  • From: Mark Westwood
• Re: Compaq Visual Fortran 6.6 and Matlab r2009a
  • From: Luka Djigas
• Re: Compaq Visual Fortran 6.6 and Matlab r2009a
  • From: Nathan
• Re: Reversing Array Elements?
  • From: robin
• Re: Basic ASCII File Reading
  • From: LR
• Re: Basic ASCII File Reading
  • From: robin
• Re: Modifying subroutine or function arguments
  • From: robin
• Re: Compaq Visual Fortran 6.6 and Matlab r2009a
  • From: TideMan
• Compaq Visual Fortran 6.6 and Matlab r2009a
  • From: Nathan
• Re: Fortran 90/95 syntax highlighting in NEdit 5.5 ?
  • From: Paul van Delst
• Re: Reversing Array Elements?
  • From: James Van Buskirk
• The Newest Special Offers/Discount/Coupons This Week
  • From: SuperCool
• Re: Reversing Array Elements?
  • From: robin
• Re: Reversing Array Elements?
  • From: robin
• Re: Why a PRINT statement changes calculation result?
  • From: robin
• Re: Reversing Array Elements?
  • From: dpb
• Re: Reversing Array Elements?
  • From: Terence
• Re: Fortran 90/95 syntax highlighting in NEdit 5.5 ?
  • From: Carlie Coats
• Fortran 90/95 syntax highlighting in NEdit 5.5 ?
  • From: Bart Vandewoestyne
• Re: function request
  • From: Tobias Burnus
• function request
  • From: rudra
• Re: Reversing Array Elements?
  • From: Tim Prince
• Re: Why a PRINT statement changes calculation result?
  • From: TideMan
• Re: Why a PRINT statement changes calculation result?
  • From: Craig Powers
• Re: Why a PRINT statement changes calculation result?
  • From: Dick Hendrickson
• Re: Why a PRINT statement changes calculation result?
  • From: glen herrmannsfeldt
• Re: Why a PRINT statement changes calculation result?
  • From: Clive Page
• Re: Reversing Array Elements?
  • From: Richard Maine
• Re: Reversing Array Elements?
  • From: glen herrmannsfeldt
• Re: Why a PRINT statement changes calculation result?
  • From: Richard Maine
• Re: Reversing Array Elements?
  • From: steve
• Re: Reversing Array Elements?
  • From: m_b_metcalf
• Re: Reversing Array Elements?
  • From: dpb
• Re: Generating documentation on the structure of a program
  • From: Arjen Markus
• Re: Should Fortran be taught to undergraduates?
  • From: Kevin G. Rhoads
• Re: Reversing Array Elements?
  • From: Arjen Markus
• Re: Generating documentation on the structure of a program
  • From: Arjen Markus
• Reversing Array Elements?
  • From: Rob
• Re: Why a PRINT statement changes calculation result?
  • From: Koen Poppe
• Re: Fortran IDE and debugger
  • From: Les Neilson
• Re: Generating documentation on the structure of a program
  • From: Jan Gerrit Kootstra
• Re: Why a PRINT statement changes calculation result?
  • From: hill
• Re: Should Fortran be taught to undergraduates?
  • From: michael.p.croucher@xxxxxxxxxxxxxx
• Re: Generating documentation on the structure of a program
  • From: nmm1
• Re: Why a PRINT statement changes calculation result?
  • From: Arjen Markus
• Re: Generating documentation on the structure of a program
  • From: Arjen Markus
• Why a PRINT statement changes calculation result?
  • From: hill
• Re: Generating documentation on the structure of a program
  • From: nmm1
• Re: Generating documentation on the structure of a program
  • From: Arjen Markus
• Re: Generating documentation on the structure of a program
  • From: Damian
• Re: Possible problems in memory allocation
  • From: robin
• Re: When is someone ready to be taught programming (especially Fortran)?
  • From: Maciej Marek
• Re: Generating documentation on the structure of a program
  • From: VICTOR
• Re: Generating documentation on the structure of a program
  • From: m_b_metcalf
• Generating documentation on the structure of a program
  • From: VICTOR
• Re: Should Fortran be taught to undergraduates?
  • From: steve
• Re: How to bind an argument when passing a function?
  • From: Ron Shepard
• Re: How to bind an argument when passing a function?
  • From: Craig Powers
• Re: How to bind an argument when passing a function?
  • From: Алексей Аверченко
• Re: Fortran Do Loop Exceeding its Index Limit?
  • From: robin
• Re: How to bind an argument when passing a function?
  • From: fj
• Re: Basic ASCII File Reading
  • From: Dr Ivan D. Reid
• Re: Profiling with Shark
  • From: Koen Poppe
• Re: How to bind an argument when passing a function?
  • From: Алексей Аверченко
• Re: How to bind an argument when passing a function?
  • From: fj
• How to bind an argument when passing a function?
  • From: Алексей Аверченко
• Re: Fortran Do Loop Exceeding its Index Limit?
  • From: Richard Maine
• Re: Fortran Do Loop Exceeding its Index Limit?
  • From: Richard Maine
• Re: Fortran Do Loop Exceeding its Index Limit?
  • From: Dick Hendrickson
• Re: Fortran Do Loop Exceeding its Index Limit?
  • From: MtnFlyer
• Re: declaring module functions in the module itself
  • From: Ron Shepard
• Re: ENTRY statement
  • From: GaryScott
• Re: Fortran Do Loop Exceeding its Index Limit?
  • From: Sjouke Burry
• Re: Fortran Do Loop Exceeding its Index Limit?
  • From: Ron Shepard
• Re: Fortran Do Loop Exceeding its Index Limit?
  • From: MtnFlyer
• Re: Fortran Do Loop Exceeding its Index Limit?
  • From: Craig Powers
• Re: Fortran IDE and debugger
  • From: Craig Powers
• Re: Fortran Do Loop Exceeding its Index Limit?
  • From: MtnFlyer
• Re: Fortran Do Loop Exceeding its Index Limit?
  • From: Sjouke Burry
• Re: ENTRY statement
  • From: Ron Shepard
• Fortran Do Loop Exceeding its Index Limit?
  • From: MtnFlyer
• Re: Fortran IDE and debugger
  • From: Richard Maine
• Re: declaring module functions in the module itself
  • From: Richard Maine
• Re: Fortran IDE and debugger
  • From: Craig Powers
• Re: declaring module functions in the module itself
  • From: BenR
• Re: Fortran IDE and debugger
  • From: J. F. Cornwall
• Re: ENTRY statement
  • From: GaryScott
• Re: Should Fortran be taught to undergraduates?
  • From: Dick Hendrickson
• Re: ENTRY statement
  • From: Dick Hendrickson
• Re: Should Fortran be taught to undergraduates?
  • From: Mark Westwood
• Re: declaring module functions in the module itself
  • From: Ron Shepard
• Re: ENTRY statement
  • From: Ron Shepard
• Re: declaring module functions in the module itself
  • From: Richard Maine
• Re: ENTRY statement
  • From: Richard Maine
• declaring module functions in the module itself
  • From: BenR
• Re: Possible problems in memory allocation
  • From: Tim Prince
• Re: ENTRY statement
  • From: Tim Prince
• Re: Modifying subroutine or function arguments
  • From: Richard Maine
• Re: ENTRY statement
  • From: Ron Shepard
• Re: Possible problems in memory allocation
  • From: Dan Nagle
• Re: Basic ASCII File Reading
  • From: makyo
• Re: Should Fortran be taught to undergraduates?
  • From: dpb
• Re: Modifying subroutine or function arguments
  • From: robin
• Re: ENTRY statement
  • From: robin
• Re: Modifying subroutine or function arguments
  • From: robin
• Re: Possible problems in memory allocation
  • From: robin
• Re: Modifying subroutine or function arguments
  • From: mecej4
• Re: When is someone ready to be taught programming (especially Fortran)?
  • From: mecej4
• Re: Should Fortran be taught to undergraduates?
  • From: Gary Scott
• Re: Should Fortran be taught to undergraduates?
  • From: Beliavsky
• Re: Should Fortran be taught to undergraduates?
  • From: nmm1
• Re: Fortran IDE and debugger
  • From: nmm1
• Re: Should Fortran be taught to undergraduates?
  • From: Les Neilson
• Re: Should Fortran be taught to undergraduates?
  • From: Richard Maine
• Re: Should Fortran be taught to undergraduates?
  • From: Arjen Markus
• Re: Should Fortran be taught to undergraduates?
  • From: rudra
• Re: Fortran IDE and debugger
  • From: Luka Djigas
• Re: Should Fortran be taught to undergraduates?
  • From: Tim Prince
• Re: Possible problems in memory allocation
  • From: robin
• Re: Basic ASCII File Reading
  • From: robin
• Re: Basic ASCII File Reading
  • From: robin
• Re: Should Fortran be taught to undergraduates?
  • From: David Duffy
• Re: Should Fortran be taught to undergraduates?
  • From: jfh
• Re: Should Fortran be taught to undergraduates?
  • From: Beliavsky
• Re: Fortran IDE and debugger
  • From: Jerry Xue
• Re: Modifying subroutine or function arguments
  • From: Richard Maine
• Re: ENTRY statement
  • From: Ron Shepard
• Re: ENTRY statement
  • From: glen herrmannsfeldt
• Re: Modifying subroutine or function arguments
  • From: glen herrmannsfeldt
• Re: Should Fortran be taught to undergraduates?
  • From: Ron Shepard
• Re: Should Fortran be taught to undergraduates?
  • From: dpb
• ENTRY statement
  • From: Thomas Robitaille
• Re: Modifying subroutine or function arguments
  • From: Richard Maine
• Re: When is someone ready to be taught programming (especially Fortran)?
  • From: jfh
• Re: Should Fortran be taught to undergraduates?
  • From: Tim Prince
• Re: Modifying subroutine or function arguments
  • From: glen herrmannsfeldt
• Re: Modifying subroutine or function arguments
  • From: Richard Maine
• Re: Should Fortran be taught to undergraduates?
  • From: Richard Maine
• Re: Modifying subroutine or function arguments
  • From: steve
• Re: Modifying subroutine or function arguments
  • From: Richard Maine
• Re: Should Fortran be taught to undergraduates?
  • From: Clive Page
• Modifying subroutine or function arguments
  • From: Thomas Robitaille
• Re: Should Fortran be taught to undergraduates?
  • From: Jan Gerrit Kootstra
• Re: Should Fortran be taught to undergraduates?
  • From: Luka Djigas
• Re: Should Fortran be taught to undergraduates?
  • From: Paul Thomas
• Re: dynamic array allocation behavior, initial values
  • From: dpb
• When is someone ready to be taught programming (especially Fortran)?
  • From: Beliavsky
• Profiling with Shark
  • From: Thomas Robitaille
• Re: Should Fortran be taught to undergraduates?
  • From: mlohry
• Re: Possible problems in memory allocation
  • From: Dan Nagle
• Re: Should Fortran be taught to undergraduates?
  • From: e p chandler
• Re: Should Fortran be taught to undergraduates?
  • From: Richard Harter
• Re: Possible problems in memory allocation
  • From: robin
• Re: explicit array allocation 0
  • From: robin
• Re: explicit array allocation 0
  • From: robin
• Re: explicit array allocation 0
  • From: robin
• Re: Should Fortran be taught to undergraduates?
  • From: Arjen Markus
• Should Fortran be taught to undergraduates?
  • From: michael.p.croucher@xxxxxxxxxxxxxx
• Re: Basic ASCII File Reading
  • From: makyo
• Re: Basic ASCII File Reading
  • From: Richard Maine
• Re: Basic ASCII File Reading
  • From: David Duffy
• Re: Basic ASCII File Reading
  • From: makyo
• Re: Basic ASCII File Reading
  • From: Richard Maine
• Re: Basic ASCII File Reading
  • From: makyo
• Re: explicit array allocation 0
  • From: glen herrmannsfeldt
• Re: explicit array allocation 0
  • From: Ron Shepard
• Re: explicit array allocation 0
  • From: Craig Powers
• Re: explicit array allocation 0
  • From: mlohry
• Re: explicit array allocation 0
  • From: Richard Maine
• Re: dynamic array allocation behavior, initial values
  • From: glen herrmannsfeldt
• Re: explicit array allocation 0
  • From: mlohry
• Re: explicit array allocation 0
  • From: Richard Maine
• Re: Array of pointers as a component of a derived type
  • From: Maciej Marek
• Re: explicit array allocation 0
  • From: dick
• Re: explicit array allocation 0
  • From: Richard Maine
• Re: dynamic array allocation behavior, initial values
  • From: Richard Maine
• Re: explicit array allocation 0
  • From: kargls
• Re: explicit array allocation 0
  • From: mlohry
• Re: explicit array allocation 0
  • From: mlohry
• Re: explicit array allocation 0
  • From: michaelmetcalf
• Re: dynamic array allocation behavior, initial values
  • From: dpb
• explicit array allocation 0
  • From: mlohry
• dynamic array allocation behavior, initial values
  • From: mlohry
• Re: Basic ASCII File Reading
  • From: Richard Maine
• Re: Basic ASCII File Reading
  • From: makyo
• Re: Array of pointers as a component of a derived type
  • From: Gordon Sande
• Re: Array of pointers as a component of a derived type
  • From: James Van Buskirk
• Array of pointers as a component of a derived type
  • From: e . macmar
• Re: Basic ASCII File Reading
  • From: Dan Nagle
• Allergy | Buy Cheap Allegra, Clarinex, Zyrtec, Claritin at the best price.
  • From: Catherine
• Re: Creating an array containing values from 1 to 100?
  • From: robparker23
• Re: Intel fortran compiler 11 on AMD opteron
  • From: Mark Mackey
• Re: Creating an array containing values from 1 to 100?
  • From: michaelmetcalf
• Re: Creating an array containing values from 1 to 100?
  • From: Arjen Markus
• Creating an array containing values from 1 to 100?
  • From: robparker23
• Re: christmas tree in fortran
  • From: Luka Djigas
• Re: Basic ASCII File Reading
  • From: Michel Olagnon
• Re: Basic ASCII File Reading
  • From: Jerry Xue
• Re: christmas tree in fortran
  • From: Jan Gerrit Kootstra
• Re: expanding INCLUDE statements
  • From: robert . corbett
• Re: Basic ASCII File Reading
  • From: Dave Allured
• Re: Compiler 64 bit windows xp pro
  • From: Gary Scott
• Re: Compiler 64 bit windows xp pro
  • From: Steve Lionel
• Re: Intel fortran compiler 11 on AMD opteron
  • From: Steve Lionel
• Re: christmas tree in fortran
  • From: glen herrmannsfeldt
• Re: Possible problems in memory allocation
  • From: Richard Maine
• christmas tree in fortran
  • From: Luka Djigas
• Re: Possible problems in memory allocation
  • From: glen herrmannsfeldt
• Re: Possible problems in memory allocation
  • From: Thomas Koenig
• Re: Possible problems in memory allocation
  • From: glen herrmannsfeldt
• Re: Possible problems in memory allocation
  • From: Richard Maine
• Re: Basic ASCII File Reading
  • From: robin
• Re: Intel fortran compiler 11 on AMD opteron
  • From: sambarluc
• Re: Intel fortran compiler 11 on AMD opteron
  • From: ken . fairfield
• Re: Possible problems in memory allocation
  • From: Dan Nagle
• Re: Intel fortran compiler 11 on AMD opteron
  • From: sambarluc
• Re: Compiler 64 bit windows xp pro
  • From: Luka Djigas
• Re: Intel fortran compiler 11 on AMD opteron
  • From: sambarluc
• Re: Intel fortran compiler 11 on AMD opteron
  • From: Mark Mackey
• Intel fortran compiler 11 on AMD opteron
  • From: sambarluc
• Re: Compiler 64 bit windows xp pro
  • From: fort jon
• Re: fortran calling c
  • From: rudra
• Re: Compiler 64 bit windows xp pro
  • From: Luka Djigas
• Re: Possible problems in memory allocation
  • From: robin
• Re: Basic ASCII File Reading
  • From: robin
• Re: Basic ASCII File Reading
  • From: robin
• Re: Compiler 64 bit windows xp pro
  • From: guoguo
• Compiler 64 bit windows xp pro
  • From: tuli
• Re: Basic ASCII File Reading
  • From: Dave Allured
• Re: Basic ASCII File Reading
  • From: Richard Maine
• Re: employ of matrix in loop
  • From: glen herrmannsfeldt
• Re: employ of matrix in loop
  • From: glen herrmannsfeldt
• Re: Basic ASCII File Reading
  • From: glen herrmannsfeldt
• Re: expanding INCLUDE statements
  • From: Michael Prager
• Re: fortran calling c
  • From: fj
• Re: fortran calling c
  • From: James Van Buskirk
• Re: employ of matrix in loop
  • From: e p chandler
• Re: fortran calling c
  • From: fj
• Re: Basic ASCII File Reading
  • From: feenberg
• Re: fortran calling c
  • From: fj
• Re: employ of matrix in loop
  • From: fj
• Re: fortran calling c
  • From: rudra
• employ of matrix in loop
  • From: Elaheh
• Re: fortran calling c
  • From: fj
• fortran calling c
  • From: rudra
• Re: severe(163): Program Exception - floating stack check
  • From: Richard Maine
• Re: severe(163): Program Exception - floating stack check
  • From: guoguo
• Re: Use of deferred type parameter and ALLOCATE
  • From: Richard Maine
• Re: Use of deferred type parameter and ALLOCATE
  • From: dpb
• Re: Use of deferred type parameter and ALLOCATE
  • From: Colin Watters
• Re: Use of deferred type parameter and ALLOCATE
  • From: Richard Maine
• Re: Use of deferred type parameter and ALLOCATE
  • From: kargls
• Re: Use of deferred type parameter and ALLOCATE
  • From: glen herrmannsfeldt
• Re: Use of deferred type parameter and ALLOCATE
  • From: Richard Maine
• Re: Use of deferred type parameter and ALLOCATE
  • From: Richard Maine
• Use of deferred type parameter and ALLOCATE
  • From: kargls
• Re: severe(163): Program Exception - floating stack check
  • From: kargls
• Re: Basic ASCII File Reading
  • From: Richard Maine
• Re: Basic ASCII File Reading
  • From: dpb
• Re: expanding INCLUDE statements
  • From: Bil Kleb
• Re: severe(163): Program Exception - floating stack check
  • From: Gordon Sande
• Re: Basic ASCII File Reading
  • From: feenberg
• Re: severe(163): Program Exception - floating stack check
  • From: guoguo
• Re: severe(163): Program Exception - floating stack check
  • From: guoguo
• Re: severe(163): Program Exception - floating stack check
  • From: guoguo
• Re: expanding INCLUDE statements
  • From: mecej4
• Re: expanding INCLUDE statements
  • From: Bil Kleb
• Luxuriescars
  • From: oubaid . 98
• Luxuriescars
  • From: oubaid . 98
• Re: Fortran IDE and debugger
  • From: J. F. Cornwall
• Re: expanding INCLUDE statements
  • From: glen herrmannsfeldt
• Re: expanding INCLUDE statements
  • From: robin
• Re: Basic ASCII File Reading
  • From: Richard Maine
• Re: Basic ASCII File Reading
  • From: TideMan
• Re: expanding INCLUDE statements
  • From: Andrew Smith
• Re: expanding INCLUDE statements
  • From: Richard Maine
• Re: Basic ASCII File Reading
  • From: Richard Maine
• Re: Basic ASCII File Reading
  • From: makyo
• Re: Memory Leaks
  • From: robin
• Re: expanding INCLUDE statements
  • From: nmm1
• Re: expanding INCLUDE statements
  • From: Luka Djigas
• Re: expanding INCLUDE statements
  • From: dpb
• Re: expanding INCLUDE statements
  • From: Gary Scott
• Re: Basic ASCII File Reading
  • From: fj
• Re: Basic ASCII File Reading
  • From: TideMan
• Re: expanding INCLUDE statements
  • From: Andrew Smith
• Re: Basic ASCII File Reading
  • From: fj
• expanding INCLUDE statements
  • From: robert . corbett
• Re: Basic ASCII File Reading
  • From: robparker23
• Re: function in module
  • From: Richard Maine
• function in module
  • From: sumesh.pt
• Re: severe(163): Program Exception - floating stack check
  • From: robin
• Re: Memory allocation failed for Subroutine
  • From: Richard Maine
• Re: Basic ASCII File Reading
  • From: Richard Maine
• Re: Basic ASCII File Reading
  • From: fj
• Basic ASCII File Reading
  • From: robparker23
• Re: Memory allocation failed for Subroutine
  • From: fj
• Re: Memory allocation failed for Subroutine
  • From: kargls
• Memory allocation failed for Subroutine
  • From: Raj
• Re: severe(163): Program Exception - floating stack check
  • From: Steve Lionel
• Re: severe(163): Program Exception - floating stack check
  • From: kargls
• Memory Leaks
  • From: sdbiking@xxxxxxxxx
• Re: severe(163): Program Exception - floating stack check
  • From: James Van Buskirk
• Re: Leading zero for printing real numbers
  • From: robin
• Re: Request search for valid source BMD09D.FOR program
  • From: nmm1
• Re: Request search for valid source BMD09D.FOR program
  • From: Terence
• Re: modifying INTENT(in) argument
  • From: Richard Maine
• Re: severe(163): Program Exception - floating stack check
  • From: guoguo
• Re: severe(163): Program Exception - floating stack check
  • From: kargls
• Re: modifying INTENT(in) argument
  • From: michaelmetcalf
• Re: severe(163): Program Exception - floating stack check
  • From: guoguo
• Re: severe(163): Program Exception - floating stack check
  • From: guoguo
• modifying INTENT(in) argument
  • From: fj
• Re: severe(163): Program Exception - floating stack check
  • From: kargls
• Re: severe(163): Program Exception - floating stack check
  • From: guoguo
• Re: severe(163): Program Exception - floating stack check
  • From: guoguo
• Re: severe(163): Program Exception - floating stack check
  • From: James Van Buskirk
• severe(163): Program Exception - floating stack check
  • From: guoguo
• Re: Possible problems in memory allocation
  • From: Richard Maine
• Re: Possible problems in memory allocation
  • From: Richard Maine
• Possible problems in memory allocation
  • From: Lurkos
• Re: Hard-coding compile date/options
  • From: robin
• Re: Are there any test coverage tools for FORTRAN90?
  • From: Bil Kleb
• Re: Hard-coding compile date/options
  • From: Bil Kleb
• EARN MORE THAN 18000$ WITH CJ JOBS
  • From: pinky.mona6@xxxxxxxxx
• Re: Are there any test coverage tools for FORTRAN90?
  • From: Arjen Markus
• Re: Are there any test coverage tools for FORTRAN90?
  • From: Tobias Burnus
• Re: Are there any test coverage tools for FORTRAN90?
  • From: Colin Watters
• Re: Are there any test coverage tools for FORTRAN90?
  • From: TideMan
• Re: Are there any test coverage tools for FORTRAN90?
  • From: Tobias Burnus
• Are there any test coverage tools for FORTRAN90?
  • From: Ira Baxter
• Re: Leading zero for printing real numbers
  • From: robin
• Re: Hard-coding compile date/options
  • From: Tim Prince
• Re: Hard-coding compile date/options
  • From: David Duffy
• Re: Hard-coding compile date/options
  • From: Richard Maine
• Re: Hard-coding compile date/options
  • From: OldSchool
• Re: Hard-coding compile date/options
  • From: Richard Maine
• Re: Leading zero for printing real numbers
  • From: Luka Djigas
• Re: Islam
  • From: Sjouke Burry
• Re: Hard-coding compile date/options
  • From: Ragu
• Hard-coding compile date/options
  • From: Lorents
• Re: Assign a generic name to a function based on user decision
  • From: nmm1
• Re: Assign a generic name to a function based on user decision
  • From: Ron Shepard
• Re: Subroutines in Separate Files
  • From: ken . fairfield
• Re: Leading zero for printing real numbers
  • From: Les Neilson
• Re: Assign a generic name to a function based on user decision
  • From: Gordon Sande
• Re: Assign a generic name to a function based on user decision
  • From: nmm1
• Re: Assign a generic name to a function based on user decision
  • From: e p chandler
• Re: Leading zero for printing real numbers
  • From: Jugoslav Dujic
• Re: f95 module for checkpointing
  • From: dreamer371
• Re: f95 module for checkpointing
  • From: dreamer371
• Islam
  • From: s
• Re: open syntax error with gfortran
  • From: Franken Sense
• Re: open syntax error with gfortran
  • From: nmm1
• Re: Assign a generic name to a function based on user decision
  • From: nmm1
• Re: Assign a generic name to a function based on user decision
  • From: e p chandler
• Re: open syntax error with gfortran
  • From: user1
• Re: Assign a generic name to a function based on user decision
  • From: Gordon Sande
• Re: Assign a generic name to a function based on user decision
  • From: Lurkos
• Re: Assign a generic name to a function based on user decision
  • From: Lurkos
• Re: open syntax error with gfortran
  • From: Franken Sense
• Re: Coarrays: procedure execution image
  • From: Franken Sense
• Re: open syntax error with gfortran
  • From: Franken Sense
• Re: open syntax error with gfortran
  • From: nmm1
• Re: Assign a generic name to a function based on user decision
  • From: nmm1
• Re: Coarrays: procedure execution image
  • From: Jared Ahern
• Re: Assign a generic name to a function based on user decision
  • From: Jason Blevins
• Re: Assign a generic name to a function based on user decision
  • From: nmm1
• Re: open syntax error with gfortran
  • From: nmm1
• Re: Assign a generic name to a function based on user decision
  • From: nmm1
• Re: Assign a generic name to a function based on user decision
  • From: Jason Blevins
• Re: open syntax error with gfortran
  • From: Michael Goerz
• Re: Assign a generic name to a function based on user decision
  • From: e p chandler
• Re: solve of a equation
  • From: glen herrmannsfeldt
• Re: solve of a equation
  • From: Dave Allured
• Re: Assign a generic name to a function based on user decision
  • From: nmm1
• Re: Assign a generic name to a function based on user decision
  • From: e p chandler
• Re: Assign a generic name to a function based on user decision
  • From: Richard Maine
• Re: f95 module for checkpointing
  • From: glen herrmannsfeldt
• Re: Assign a generic name to a function based on user decision
  • From: Lurkos
• Re: Fortran IDE and debugger
  • From: Mark Stevens
• Re: Fortran IDE and debugger
  • From: Lurkos
• Re: open syntax error with gfortran
  • From: nmm1
• Re: f95 module for checkpointing
  • From: dreamer371
• Re: f95 module for checkpointing
  • From: dreamer371
• open syntax error with gfortran
  • From: Michael Goerz
• Coarrays: procedure execution image
  • From: Jared Ahern
• Re: Subroutines in Separate Files
  • From: Jugoslav Dujic
• Re: Assign a generic name to a function based on user decision
  • From: James Van Buskirk
• Re: Fortran IDE and debugger
  • From: rudra
• Re: Assign a generic name to a function based on user decision
  • From: Richard Maine
• Re: Assign a generic name to a function based on user decision
  • From: e p chandler
• Fortran IDE and debugger
  • From: Lurkos
• Assign a generic name to a function based on user decision
  • From: Lurkos
• Re: SUBROUTINE and real kind definition
  • From: Lurkos
• Is this where all the good shit is inaccesible because we are all so greedy?
  • From: mike . swarski1
• f95 module for checkpointing
  • From: dreamer371
• Welcome to our site: www.ec21baba.com we are a leading company in dealing with brand shoes
  • From: jinguo_007@xxxxxxxxxxx
• Re: sloppy-char flag strangeness
  • From: Ron Shepard
• Re: sloppy-char flag strangeness
  • From: glen herrmannsfeldt
• Re: sloppy-char flag strangeness
  • From: robert . corbett
• Re: Subroutines in Separate Files
  • From: Richard Maine
• Re: Subroutines in Separate Files
  • From: fj
• Re: Subroutines in Separate Files
  • From: Bil Kleb
• Re: Subroutines in Separate Files
  • From: Jerry Xue
• Re: solve of a equation
  • From: Ron Shepard
• Re: generalized eigenvalue problem
  • From: Ron Shepard
• Re: Subroutines in Separate Files
  • From: Bill Obscured
• generalized eigenvalue problem
  • From: Elaheh
• Re: sloppy-char flag strangeness
  • From: glen herrmannsfeldt
• Re: C/Fortran performance differences (gcc/gfortran, icc/ifort) on X86_64
  • From: Evan McClain
• Re: C/Fortran performance differences (gcc/gfortran, icc/ifort) on X86_64
  • From: Tim Prince
• Re: solve of a equation
  • From: James Van Buskirk
• Request serach for valid source BMD09D.FOR program
  • From: Terence
• Re: sloppy-char flag strangeness
  • From: ken . fairfield
• Re: Subroutines in Separate Files
  • From: Bil Kleb
• Re: Intel Fortran on Fedora 10+
  • From: Jared Ahern
• Re: Intel Fortran on Fedora 10+
  • From: Steve Lionel
• Re: solve of a equation
  • From: fj
• C/Fortran performance differences (gcc/gfortran, icc/ifort) on X86_64
  • From: Evan McClain
• Re: sloppy-char flag strangeness
  • From: Richard Maine
• Re: sloppy-char flag strangeness
  • From: Norminator
• Re: sloppy-char flag strangeness
  • From: Richard Maine
• Re: sloppy-char flag strangeness
  • From: glen herrmannsfeldt
• Re: sloppy-char flag strangeness
  • From: Richard Maine
• Re: sloppy-char flag strangeness
  • From: glen herrmannsfeldt
• Re: sloppy-char flag strangeness
  • From: Norminator
• Re: Reading direct-access files is slow with Intel Fortran?
  • From: fj
• Re: Subroutines in Separate Files
  • From: Craig Powers
• Re: solve of a equation
  • From: Richard Maine
• Re: GDB print array in a module
  • From: fj
• Re: sloppy-char flag strangeness
  • From: Richard Maine
• Re: sloppy-char flag strangeness
  • From: glen herrmannsfeldt
• Re: sloppy-char flag strangeness
  • From: Norminator
• Re: sloppy-char flag strangeness
  • From: Thomas Koenig
• Re: Subroutines in Separate Files
  • From: fj
• Re: Subroutines in Separate Files
  • From: ken . fairfield
• Intel Fortran on Fedora 10+
  • From: Jared Ahern
• Re: Subroutines in Separate Files
  • From: ken . fairfield
• Re: eigenvalue problem
  • From: Alois Steindl
• Fortran job
  • From: Walt Brainerd
• Re: sloppy-char flag strangeness
  • From: Norminator
• eigenvalue problem
  • From: Elaheh
• Re: Reading direct-access files is slow with Intel Fortran?
  • From: Arjen Markus
• Re: Reading direct-access files is slow with Intel Fortran?
  • From: Arjen Markus

• Security
• UNIX
• Linux
• Coding
• Usenet

• Archive
• About
• Privacy
• Search
• Imprint

coding.derkeiler.com  > Archive  > Fortran  > comp.lang.fortran  > 2009-06