comp.lang.fortran

• Date Index

---

• CSharifi, CVC
• matmul does not work., Kurda Yon
  • Re: matmul does not work., Kurda Yon
  • Re: matmul does not work., Richard Maine
    • Re: matmul does not work., Kurda Yon
      • Re: matmul does not work., Richard Maine
  • Re: matmul does not work., Rich Townsend
• Re-ordering columns or rows of an array efficiently, Mike
  • Re: Re-ordering columns or rows of an array efficiently, Dan Nagle
  • Re: Re-ordering columns or rows of an array efficiently, deltaseq0
  • Re: Re-ordering columns or rows of an array efficiently, glen herrmannsfeldt
    • Re: Re-ordering columns or rows of an array efficiently, Dan Nagle
      • Re: Re-ordering columns or rows of an array efficiently, glen herrmannsfeldt
      • Re: Re-ordering columns or rows of an array efficiently, Mike
      • Re: Re-ordering columns or rows of an array efficiently, fj
• initializing an array of user-defined data types, Bart Vandewoestyne
  • Re: initializing an array of user-defined data types, Richard Maine
    • Re: initializing an array of user-defined data types, garylscott
      • Re: initializing an array of user-defined data types, dpb
      • Re: initializing an array of user-defined data types, Richard Maine
    • Re: initializing an array of user-defined data types, glen herrmannsfeldt
  • Re: initializing an array of user-defined data types, Paul van Delst
    • Re: initializing an array of user-defined data types, Dan Nagle
  • Re: initializing an array of user-defined data types, Bart Vandewoestyne
• dynamic filename string, apek
  • Re: dynamic filename string, gary . l . scott
    • Re: dynamic filename string, Jan Vorbrüggen
    • Re: dynamic filename string, fj
      • Re: dynamic filename string, fj
• is this newsgroup accessible via gmane, Kamaraju S Kusumanchi
  • Re: is this newsgroup accessible via gmane, J. F. Cornwall
  • Re: is this newsgroup accessible via gmane, deltaseq0
  • Re: is this newsgroup accessible via gmane, David Jones
    • Re: is this newsgroup accessible via gmane, Wade Ward
      • Re: is this newsgroup accessible via gmane, Gary Scott
      • Re: is this newsgroup accessible via gmane, dpb
      • Re: is this newsgroup accessible via gmane, Jugoslav Dujic
      • Re: is this newsgroup accessible via gmane, Tom Micevski
• Allow interspersed named and positional arguments?, Beliavsky
  • Re: Allow interspersed named and positional arguments?, Paul van Delst
  • Re: Allow interspersed named and positional arguments?, Richard Maine
  • Re: Allow interspersed named and positional arguments?, Fly Away
    • Re: Allow interspersed named and positional arguments?, Richard Maine
      • Re: Allow interspersed named and positional arguments?, Fly Away
• Parallelization on Dell Workstations, Ganesh
  • Re: Parallelization on Dell Workstations, linuxl4
  • Re: Parallelization on Dell Workstations, Sebastian Hanigk
  • Re: Parallelization on Dell Workstations, Tim Prince
    • Re: Parallelization on Dell Workstations, Sebastian Hanigk
      • Re: Parallelization on Dell Workstations, Tim Prince
      • Re: Parallelization on Dell Workstations, Ganesh
      • Re: Parallelization on Dell Workstations, Sebastian Hanigk
      • Re: Parallelization on Dell Workstations, Sebastian Hanigk
• Read DOS or Unix files with the same fortran code, feenberg
  • Re: Read DOS or Unix files with the same fortran code, Arjen Markus
  • Re: Read DOS or Unix files with the same fortran code, Tim Prince
    • Re: Read DOS or Unix files with the same fortran code, user1
  • Re: Read DOS or Unix files with the same fortran code, e p chandler
  • Re: Read DOS or Unix files with the same fortran code, Terence
    • Re: Read DOS or Unix files with the same fortran code, fj
  • Re: Read DOS or Unix files with the same fortran code, tianyf@xxxxxxxxx
    • Re: Read DOS or Unix files with the same fortran code, glen herrmannsfeldt
    • Re: Read DOS or Unix files with the same fortran code, Richard Maine
      • Re: Read DOS or Unix files with the same fortran code, tianyf@xxxxxxxxx
      • Re: Read DOS or Unix files with the same fortran code, ajmf77
    • Re: Read DOS or Unix files with the same fortran code, Charles Russell
• Execution times running multiple instances of an application, deltaseq0
  • Re: Execution times running multiple instances of an application, Mark Mackey
    • Re: Execution times running multiple instances of an application, deltaseq0
      • Re: Execution times running multiple instances of an application, James Van Buskirk
      • Re: Execution times running multiple instances of an application, deltaseq0
  • Re: Execution times running multiple instances of an application, Dr Ivan D. Reid
    • Re: Execution times running multiple instances of an application, deltaseq0
    • Re: Execution times running multiple instances of an application, Tim Prince
• IVF 10.0 Win/VS 2005 Profiling, John S
  • Re: IVF 10.0 Win/VS 2005 Profiling, John S
    • Re: IVF 10.0 Win/VS 2005 Profiling, Tim Prince
      • Re: IVF 10.0 Win/VS 2005 Profiling, Steve Lionel
  • Re: IVF 10.0 Win/VS 2005 Profiling, Steve Lionel
• allocating arrays, trouble, Förster vom Silberwald
  • Re: allocating arrays, trouble, Förster vom Silberwald
    • Re: allocating arrays, trouble, Wade Ward
      • Re: allocating arrays, trouble, Förster vom Silberwald
      • Re: allocating arrays, trouble, Arjen Markus
      • Re: allocating arrays, trouble, Wade Ward
      • Re: allocating arrays, trouble, John Harper
      • Re: allocating arrays, trouble, glen herrmannsfeldt
      • Re: allocating arrays, trouble, Förster vom Silberwald
      • Re: allocating arrays, trouble, Förster vom Silberwald
      • Re: allocating arrays, trouble, Arjen Markus
      • Re: allocating arrays, trouble, Förster vom Silberwald
      • Re: allocating arrays, trouble, Arjen Markus
      • Re: allocating arrays, trouble, Förster vom Silberwald
      • Re: allocating arrays, trouble, Reinhold Bader
      • Re: allocating arrays, trouble, Arjen Markus
      • Re: allocating arrays, trouble, Förster vom Silberwald
      • Re: allocating arrays, trouble, michael
      • Re: allocating arrays, trouble, Förster vom Silberwald
      • Re: allocating arrays, trouble, Arjen Markus
      • Re: allocating arrays, trouble, Förster vom Silberwald
      • Re: allocating arrays, trouble, dpb
      • Re: allocating arrays, trouble, AnotherSquid
      • Re: allocating arrays, trouble, Gordon Sande
      • Re: allocating arrays, trouble, Förster vom Silberwald
      • Re: allocating arrays, trouble, Gordon Sande
      • Re: allocating arrays, trouble, John Harper
      • Re: allocating arrays, trouble, Richard Maine
  • Re: allocating arrays, trouble, michael
  • Re: allocating arrays, trouble, Charles Coldwell
    • Re: allocating arrays, trouble, Förster vom Silberwald
    • Re: allocating arrays, trouble, Förster vom Silberwald
      • Re: allocating arrays, trouble, Michael Metcalf
      • Re: allocating arrays, trouble, Förster vom Silberwald
• Reading binary file generated from 32-bit machine using 64-bit machine, yonas_kassa
  • Re: Reading binary file generated from 32-bit machine using 64-bit machine, Thomas Koenig
    • Re: Reading binary file generated from 32-bit machine using 64-bit machine, yonas_kassa
      • Re: Reading binary file generated from 32-bit machine using 64-bit machine, Louis Krupp
      • Re: Reading binary file generated from 32-bit machine using 64-bit machine, yonas_kassa
      • Re: Reading binary file generated from 32-bit machine using 64-bit machine, Louis Krupp
      • Re: Reading binary file generated from 32-bit machine using 64-bit machine, yonas_kassa
      • Re: Reading binary file generated from 32-bit machine using 64-bit machine, yonas_kassa
      • Re: Reading binary file generated from 32-bit machine using 64-bit machine, Louis Krupp
      • Re: Reading binary file generated from 32-bit machine using 64-bit machine, glen herrmannsfeldt
      • Re: Reading binary file generated from 32-bit machine using 64-bit machine, yonas_kassa
      • Re: Reading binary file generated from 32-bit machine using 64-bit machine, yonas_kassa
      • Re: Reading binary file generated from 32-bit machine using 64-bit machine, yonas_kassa
      • Re: Reading binary file generated from 32-bit machine using 64-bit machine, Thierry B.
      • Re: Reading binary file generated from 32-bit machine using 64-bit machine, Janne Blomqvist
• GFORTRAN PROBLEM WITH SAVE STATEMENT, mark . w . easter
  • Re: GFORTRAN PROBLEM WITH SAVE STATEMENT, Richard Maine
    • Re: GFORTRAN PROBLEM WITH SAVE STATEMENT, Wade Ward
    • Re: GFORTRAN PROBLEM WITH SAVE STATEMENT, john . collins
      • Re: GFORTRAN PROBLEM WITH SAVE STATEMENT, Michael Metcalf
      • Fortran Error Reporting Requirements (Was: GFORTRAN PROBLEM WITH SAVE STATEMENT), Craig Dedo
      • Re: Fortran Error Reporting Requirements (Was: GFORTRAN PROBLEM WITH SAVE STATEMENT), Dick Hendrickson
      • Re: Fortran Error Reporting Requirements (Was: GFORTRAN PROBLEM WITH SAVE STATEMENT), john . collins
      • Re: Fortran Error Reporting Requirements (Was: GFORTRAN PROBLEM WITH SAVE STATEMENT), Greg Lindahl
      • Re: Fortran Error Reporting Requirements (Was: GFORTRAN PROBLEM WITH SAVE STATEMENT), John Harper
      • Re: Fortran Error Reporting Requirements (Was: GFORTRAN PROBLEM WITH SAVE STATEMENT), Jan Vorbrüggen
      • Re: Fortran Error Reporting Requirements (Was: GFORTRAN PROBLEM WITH SAVE STATEMENT), john . collins
      • Re: Fortran Error Reporting Requirements (Was: GFORTRAN PROBLEM WITH SAVE STATEMENT), Dan Nagle
      • Re: Fortran Error Reporting Requirements (Was: GFORTRAN PROBLEM WITH SAVE STATEMENT), Craig Dedo
      • Re: Fortran Error Reporting Requirements (Was: GFORTRAN PROBLEM WITH SAVE STATEMENT), john . collins
      • Re: Fortran Error Reporting Requirements (Was: GFORTRAN PROBLEM WITH SAVE STATEMENT), Dan Nagle
      • Re: Fortran Error Reporting Requirements (Was: GFORTRAN PROBLEM WITH SAVE STATEMENT), Craig Dedo
      • Re: Fortran Error Reporting Requirements (Was: GFORTRAN PROBLEM WITH SAVE STATEMENT), Dick Hendrickson
      • Re: Fortran Error Reporting Requirements (Was: GFORTRAN PROBLEM WITH SAVE STATEMENT), Craig Powers
      • Re: Fortran Error Reporting Requirements (Was: GFORTRAN PROBLEM WITH SAVE STATEMENT), glen herrmannsfeldt
      • Re: Fortran Error Reporting Requirements (Was: GFORTRAN PROBLEM WITH SAVE STATEMENT), Greg Lindahl
      • Re: Fortran Error Reporting Requirements, Richard Maine
      • Re: Fortran Error Reporting Requirements, John Harper
      • Re: Fortran Error Reporting Requirements, John Appleyard
      • Re: Fortran Error Reporting Requirements, Greg Lindahl
      • Re: Fortran Error Reporting Requirements, garylscott
      • Re: Fortran Error Reporting Requirements, Greg Lindahl
      • Re: Fortran Error Reporting Requirements, Paul van Delst
      • Re: Fortran Error Reporting Requirements, Dan Nagle
      • Re: Fortran Error Reporting Requirements, Gary Scott
      • Re: Fortran Error Reporting Requirements, Dan Nagle
      • Re: Fortran Error Reporting Requirements, garylscott
      • Re: Fortran Error Reporting Requirements, Dan Nagle
      • Re: Fortran Error Reporting Requirements, garylscott
      • Re: Fortran Error Reporting Requirements, Greg Lindahl
      • Re: Fortran Error Reporting Requirements, garylscott
      • Re: Fortran Error Reporting Requirements, Greg Lindahl
      • Re: Fortran Error Reporting Requirements, garylscott
      • Re: Fortran Error Reporting Requirements, John Appleyard
      • Re: Fortran Error Reporting Requirements, glen herrmannsfeldt
      • Re: Fortran Error Reporting Requirements, Dan Nagle
• More gfortran and BIND(C), James Van Buskirk
  • Re: More gfortran and BIND(C), Richard Maine
    • Re: More gfortran and BIND(C), James Van Buskirk
      • Re: More gfortran and BIND(C), James Van Buskirk
      • Re: More gfortran and BIND(C), James Van Buskirk
      • Re: More gfortran and BIND(C), Richard Maine
      • Re: More gfortran and BIND(C), James Van Buskirk
      • Re: More gfortran and BIND(C), Richard Maine
      • Re: More gfortran and BIND(C), glen herrmannsfeldt
      • Re: More gfortran and BIND(C), Wade Ward
• Error: actual dummy arguments, Mike
  • Re: Error: actual dummy arguments, fj
• Limiting number of executions, Luka Djigas
• Pure curiosity about dot_product timing results, jiho
  • Re: Pure curiosity about dot_product timing results, Tobias Burnus
  • Re: Pure curiosity about dot_product timing results, mecej4
    • Re: Pure curiosity about dot_product timing results, Wade Ward
      • Re: Pure curiosity about dot_product timing results, Craig Dedo
      • Re: Pure curiosity about dot_product timing results, jiho
      • Re: Pure curiosity about dot_product timing results, James Van Buskirk
      • Re: Pure curiosity about dot_product timing results, glen herrmannsfeldt
      • Re: Pure curiosity about dot_product timing results, glen herrmannsfeldt
      • Re: Pure curiosity about dot_product timing results, jiho
• Problems in using NLSSetLocale function., Devendra
  • Re: Problems in using NLSSetLocale function., Dr Ivan D. Reid
    • Re: Problems in using NLSSetLocale function., Devendra
• Hollerith confusion, Robert Orban
  • Re: Hollerith confusion, James Van Buskirk
    • Re: Hollerith confusion, Robert Orban
  • Re: Hollerith confusion, glen herrmannsfeldt
• gfortran diagnostics and so on, James Van Buskirk
  • Re: gfortran diagnostics and so on, Tobias Burnus
    • Re: gfortran diagnostics and so on, James Van Buskirk
      • Re: gfortran diagnostics and so on, Richard Maine
  • Re: gfortran diagnostics and so on, Tobias Burnus
    • Re: gfortran diagnostics and so on, Richard Maine
      • Re: gfortran diagnostics and so on, Tobias Burnus
      • Re: gfortran diagnostics and so on, glen herrmannsfeldt
      • Re: gfortran diagnostics and so on, Dr Ivan D. Reid
      • Re: gfortran diagnostics and so on, Dan Nagle
      • Re: gfortran diagnostics and so on, Craig Dedo
      • Re: gfortran diagnostics and so on, Gordon Sande
      • Re: gfortran diagnostics and so on, Craig Dedo
      • Re: gfortran diagnostics and so on, Gordon Sande
      • Re: gfortran diagnostics and so on, Steven G. Kargl
      • Re: gfortran diagnostics and so on, Craig Dedo
      • Re: gfortran diagnostics and so on, Steven G. Kargl
      • Re: gfortran diagnostics and so on, Craig Dedo
      • Re: gfortran diagnostics and so on, Steven G. Kargl
      • Re: gfortran diagnostics and so on, Dick Hendrickson
      • Re: gfortran diagnostics and so on, Gary Scott
      • Re: gfortran diagnostics and so on, Craig Dedo
      • Re: gfortran diagnostics and so on, jamesgiles@xxxxxxx
      • Re: gfortran diagnostics and so on, Dan Nagle
      • Re: gfortran diagnostics and so on, jamesgiles@xxxxxxx
      • Re: gfortran diagnostics and so on, Gary Scott
      • Re: gfortran diagnostics and so on, jamesgiles@xxxxxxx
      • Re: gfortran diagnostics and so on, Gary Scott
      • C String Prefix Operator Idea (Was: gfortran diagnostics and so on), Craig Dedo
      • Re: C String Prefix Operator Idea (Was: gfortran diagnostics and so on), James Van Buskirk
      • Re: C String Prefix Operator Idea (Was: gfortran diagnostics and so on), Craig Dedo
      • Re: C String Prefix Operator Idea (Was: gfortran diagnostics and so on), Gary Scott
      • Re: C String Prefix Operator Idea (Was: gfortran diagnostics and so on), Gary Scott
      • Re: C String Prefix Operator Idea (Was: gfortran diagnostics and so on), jamesgiles@xxxxxxx
      • Re: C String Prefix Operator Idea (Was: gfortran diagnostics and so on), Gary Scott
      • Re: C String Prefix Operator Idea (Was: gfortran diagnostics and so on), jamesgiles@xxxxxxx
      • Re: C String Prefix Operator Idea (Was: gfortran diagnostics and so on), Gary Scott
      • Re: C String Prefix Operator Idea (Was: gfortran diagnostics and so on), jamesgiles@xxxxxxx
      • Re: C String Prefix Operator Idea (Was: gfortran diagnostics and so on), glen herrmannsfeldt
      • Re: C String Prefix Operator Idea (Was: gfortran diagnostics and so on), Gary Scott
      • Re: C String Prefix Operator Idea (Was: gfortran diagnostics and so on), glen herrmannsfeldt
      • Re: C String Prefix Operator Idea (Was: gfortran diagnostics and so on), Dan Nagle
      • Re: C String Prefix Operator Idea (Was: gfortran diagnostics and so on), Gary Scott
      • Re: C String Prefix Operator Idea (Was: gfortran diagnostics and so on), Dan Nagle
      • Re: C String Prefix Operator Idea (Was: gfortran diagnostics and so on), Gary Scott
      • Re: C String Prefix Operator Idea (Was: gfortran diagnostics and so on), jamesgiles@xxxxxxx
      • Re: C String Prefix Operator Idea (Was: gfortran diagnostics and so on), James Van Buskirk
      • Re: C String Prefix Operator Idea (Was: gfortran diagnostics and so on), jamesgiles@xxxxxxx
      • Re: C String Prefix Operator Idea (Was: gfortran diagnostics and so on), Wade Ward
      • Re: C String Prefix Operator Idea (Was: gfortran diagnostics and so on), Craig Dedo
      • Re: C String Prefix Operator Idea (Was: gfortran diagnostics and so on), Wade Ward
      • Re: C String Prefix Operator Idea (Was: gfortran diagnostics and so on), glen herrmannsfeldt
      • Re: C String Prefix Operator Idea (Was: gfortran diagnostics and so on), Craig Dedo
      • Re: gfortran diagnostics and so on, Gary Scott
      • Re: gfortran diagnostics and so on, glen herrmannsfeldt
      • Re: gfortran diagnostics and so on, Dan Nagle
      • Re: gfortran diagnostics and so on, Richard Maine
      • Re: gfortran diagnostics and so on, glen herrmannsfeldt
      • Re: gfortran diagnostics and so on, Dan Nagle
      • Re: gfortran diagnostics and so on, Richard Maine
      • Re: gfortran diagnostics and so on, jamesgiles@xxxxxxx
      • Backslashes (was: gfortran diagnostics and so on), Thomas Koenig
      • Re: Backslashes (was: gfortran diagnostics and so on), mike . prager
      • Re: Backslashes, Gary Scott
      • Re: Backslashes, Craig Dedo
      • Re: Backslashes, Steven G. Kargl
      • Re: Backslashes, Dick Hendrickson
      • Re: Backslashes, Steven G. Kargl
      • Re: Backslashes, Greg Lindahl
      • Re: Backslashes, Michael Prager
      • Re: Backslashes, Janne Blomqvist
      • Re: Backslashes, Dan Nagle
      • Re: Backslashes, Michael Prager
      • Re: gfortran diagnostics and so on, ttw
    • Re: gfortran diagnostics and so on, James Van Buskirk
    • Re: gfortran diagnostics and so on, Richard Maine
      • Re: gfortran diagnostics and so on, John Harper
• Programming with tied hands, Förster vom Silberwald
  • Re: Programming with tied hands, Terence
  • Re: Programming with tied hands, Bil Kleb
    • Re: Programming with tied hands, Förster vom Silberwald
  • Re: Programming with tied hands, Arjen Markus
    • Re: Programming with tied hands, Förster vom Silberwald
• Read binaries from matlab, Farhad
  • Re: Read binaries from matlab, dpb
  • Re: Read binaries from matlab, Förster vom Silberwald
    • Re: Read binaries from matlab, dpb
  • Re: Read binaries from matlab, James Tursa
    • Re: Read binaries from matlab, dpb
      • Re: Read binaries from matlab, Farhad
      • Re: Read binaries from matlab, Richard Maine
      • Re: Read binaries from matlab, Thomas Koenig
      • Re: Read binaries from matlab, Farhad
      • Re: Read binaries from matlab, James Tursa
• Object Oriented Optimization, relaxmike
  • Re: Object Oriented Optimization, Reinhold Bader
  • Re: Object Oriented Optimization, Arjen Markus
  • Re: Object Oriented Optimization, alexzenk
    • Re: Object Oriented Optimization, alexzenk
    • Re: Object Oriented Optimization, Richard Maine
      • Re: Object Oriented Optimization, Gary Scott
• making even and odd index parameter?, Martin Jørgensen
  • Re: making even and odd index parameter?, Richard Maine
    • Re: making even and odd index parameter?, Martin Jørgensen
      • Re: making even and odd index parameter?, Richard Maine
      • Re: making even and odd index parameter?, Paul van Delst
• Problem when creating a.out and -convert big_endian compiler option, Förster vom Silberwald
  • Re: Problem when creating a.out and -convert big_endian compiler option, Paul van Delst
    • Re: Problem when creating a.out and -convert big_endian compiler option, Förster vom Silberwald
    • Re: Problem when creating a.out and -convert big_endian compiler option, Förster vom Silberwald
      • Re: Problem when creating a.out and -convert big_endian compiler option, Michael Metcalf
      • Re: Problem when creating a.out and -convert big_endian compiler option, Förster vom Silberwald
      • Re: Problem when creating a.out and -convert big_endian compiler option, Dan Nagle
      • Re: Problem when creating a.out and -convert big_endian compiler option, mecej4
      • Re: Problem when creating a.out and -convert big_endian compiler option, Ken Fairfield
      • Re: Problem when creating a.out and -convert big_endian compiler option, Richard Maine
      • Re: Problem when creating a.out and -convert big_endian compiler option, James Van Buskirk
      • Re: Problem when creating a.out and -convert big_endian compiler option, glen herrmannsfeldt
      • Re: Problem when creating a.out and -convert big_endian compiler option, Paul van Delst
    • Re: Problem when creating a.out and -convert big_endian compiler option, Richard Maine
      • Re: Problem when creating a.out and -convert big_endian compiler option, Paul van Delst
    • Re: Problem when creating a.out and -convert big_endian compiler option, Förster vom Silberwald
  • Re: Problem when creating a.out and -convert big_endian compiler option, andy271828
    • Re: Problem when creating a.out and -convert big_endian compiler option, Steve Lionel
      • Re: Problem when creating a.out and -convert big_endian compiler option, andy271828
      • Re: Problem when creating a.out and -convert big_endian compiler option, Paul van Delst
• (un)trustworthy tools -- a problem..., Carlie J. Coats
  • Re: (un)trustworthy tools -- a problem..., Herman D . Knoble
  • Re: (un)trustworthy tools -- a problem..., James Van Buskirk
    • Re: (un)trustworthy tools -- a problem..., Carlie J. Coats
      • Re: (un)trustworthy tools -- a problem..., dpb
• eqv vs ==, Arno
  • Re: eqv vs ==, Les
    • Re: eqv vs ==, Arno
  • Re: eqv vs ==, Tim Prince
  • Re: eqv vs ==, Steve Lionel
    • Re: eqv vs ==, Jugoslav Dujic
      • Re: eqv vs ==, Arjen Markus
      • Re: eqv vs ==, Arjen Markus
      • Re: eqv vs ==, dpb
      • Re: eqv vs ==, Arjen Markus
      • Re: eqv vs ==, Jugoslav Dujic
      • Re: eqv vs ==, dpb
      • Re: eqv vs ==, Richard Maine
      • Re: eqv vs ==, Dan Nagle
      • Re: eqv vs ==, Richard Maine
      • Re: eqv vs ==, Dan Nagle
      • Re: eqv vs ==, Gary Scott
      • Re: eqv vs ==, John Harper
      • Re: eqv vs ==, glen herrmannsfeldt
      • Re: eqv vs ==, James Van Buskirk
      • Re: eqv vs ==, Steve Lionel
• dsign, erik
  • Re: dsign, Arno
  • Re: dsign, Dr Ivan D. Reid
  • Re: dsign, glen herrmannsfeldt
    • Re: dsign, erik
      • Re: dsign, Ian Bush
      • Re: dsign, Osiris
• Procedures as arguments - set dummy arguments, vincent . rotival
  • Re: Procedures as arguments - set dummy arguments, Richard Maine
    • Re: Procedures as arguments - set dummy arguments, Reinhold Bader
      • Re: Procedures as arguments - set dummy arguments, paul . richard . thomas
      • Re: Procedures as arguments - set dummy arguments, James Van Buskirk
  • Re: Procedures as arguments - set dummy arguments, James Van Buskirk
  • Re: Procedures as arguments - set dummy arguments, James Van Buskirk
• Re: Data Plotting Library DISLIN 9.2, linuxl4
  • Re: Data Plotting Library DISLIN 9.2, Luka Djigas
    • Re: Data Plotting Library DISLIN 9.2, s1166
• metacommand $debug, ramiAIT
  • RE: metacommand $debug, meek
    • Re: metacommand $debug, ramiAIT
      • RE: metacommand $debug, meek
• linking to OpenMP run-time library with gfortran, Damian
  • Re: linking to OpenMP run-time library with gfortran, Steven G. Kargl
    • Re: linking to OpenMP run-time library with gfortran, Damian
      • Re: linking to OpenMP run-time library with gfortran, Steven G. Kargl
  • Re: linking to OpenMP run-time library with gfortran, linuxl4
• g95 on Windows: g95.exe: no input files, igor
  • Re: g95 on Windows: g95.exe: no input files, Tim Prince
    • Re: g95 on Windows: g95.exe: no input files, igor
      • Re: g95 on Windows: g95.exe: no input files, John Smith
  • Re: g95 on Windows: g95.exe: no input files, proximum
    • Re: g95 on Windows: g95.exe: no input files, proximum
  • Re: g95 on Windows: g95.exe: no input files, user1
• character array constructor question, John Harper
  • Re: character array constructor question, Richard Maine
    • Re: character array constructor question, Richard Maine
  • Re: character array constructor question, robin
• Eternity II, Bart Vandewoestyne
• Any suggestions?, sara_patty
  • Re: Any suggestions?, Daniel Platt
    • Re: Any suggestions?, Richard Maine
      • Re: Any suggestions?, Richard Maine
    • Re: Any suggestions?, sara_patty
  • Re: Any suggestions?, James Van Buskirk
    • Re: Any suggestions?, sara_patty
      • Re: Any suggestions?, James Van Buskirk
      • Re: Any suggestions?, Craig Dedo
      • Re: Any suggestions?, sara_patty
      • Re: Any suggestions?, Craig Dedo
      • Re: Any suggestions?, Craig Powers
      • Re: Any suggestions?, Les
      • Re: Any suggestions?, Richard Maine
      • Re: Any suggestions?, James Van Buskirk
    • Re: Any suggestions?, James Van Buskirk
      • Re: Any suggestions?, Richard Maine
      • Re: Any suggestions?, James Van Buskirk
      • Re: Any suggestions?, Craig Dedo
      • Re: Any suggestions?, Richard Maine
      • Re: Any suggestions?, sara_patty
      • Re: Any suggestions?, dpb
      • Re: Any suggestions?, Richard Maine
      • Re: Any suggestions?, dpb
  • Re: Any suggestions?, Craig Dedo
• what dose "character layer*(*)" mean?, leed
  • Re: what dose "character layer*(*)" mean?, John Harper
  • Re: what dose "character layer*(*)" mean?, jamesgiles@xxxxxxx
  • Re: what dose "character layer*(*)" mean?, leed
• Trouble with Sun Fortran and Module name clashes, braams
  • Re: Trouble with Sun Fortran and Module name clashes, braams
• Re: G77 can't compile complex(512, 512) ??, mecej4
  • Re: G77 can't compile complex(512, 512) ??, Nianming Zuo
    • Re: G77 can't compile complex(512, 512) ??, Richard Maine
    • Re: G77 can't compile complex(512, 512) ??, glen herrmannsfeldt
    • Re: G77 can't compile complex(512, 512) ??, Tim Prince
      • Re: G77 can't compile complex(512, 512) ??, Nianming Zuo
  • <Possible follow-ups>
  • Re: G77 can't compile complex(512, 512) ??, Chip Coldwell
    • Re: G77 can't compile complex(512, 512) ??, Nianming Zuo
      • Re: G77 can't compile complex(512, 512) ??, Richard Maine
      • Re: G77 can't compile complex(512, 512) ??, glen herrmannsfeldt
      • Re: G77 can't compile complex(512, 512) ??, Richard Maine
      • Re: G77 can't compile complex(512, 512) ??, Chip Coldwell
• File reading problem, galkas
  • Re: File reading problem, Gary Scott
    • Re: File reading problem, Gary Scott
  • Re: File reading problem, dpb
    • Re: File reading problem, galkas
      • Re: File reading problem, dpb
      • Re: File reading problem, gary . l . scott
      • Re: File reading problem, galkas
      • Re: File reading problem, Les
      • Re: File reading problem, Gary Scott
      • Re: File reading problem, Jim Backus
      • Re: File reading problem, Terence
      • Re: File reading problem, Richard Maine
      • Re: File reading problem, Jim Backus
      • Re: File reading problem, Wade Ward
      • Re: File reading problem, glen herrmannsfeldt
• num.analysis, Wade Ward
  • Re: num.analysis, Rich Townsend
  • Re: num.analysis, John Harper
    • Re: num.analysis, Beliavsky
      • Re: num.analysis, Wade Ward
• Verifying TLE data :-), RadSurfer
• Gene Golub (1932-2007), Steven G. Kargl
  • Re: Gene Golub (1932-2007), Chip Coldwell
• Parsing TLE data, RadSurfer
  • Re: Parsing TLE data, Richard Maine
  • Re: Parsing TLE data, Michael Metcalf
    • Re: Parsing TLE data, RadSurfer
    • Re: Parsing TLE data, glen herrmannsfeldt
      • Re: Parsing TLE data, RadSurfer
      • Re: Parsing TLE data, glen herrmannsfeldt
      • F Edit Descriptor & Blank Interpretation Mode (Was: Parsing TLE data), Craig Dedo
      • Re: Parsing TLE data, Michael Metcalf
  • Re: Parsing TLE data, RadSurfer
  • Re: Parsing TLE data, RadSurfer
    • Re: Parsing TLE data, Brian Wannamaker
• Is there a way to find the unit associated w/an open file?, jomarbueyes
  • Re: Is there a way to find the unit associated w/an open file?, Michael Metcalf
    • Re: Is there a way to find the unit associated w/an open file?, jomarbueyes
      • Re: Is there a way to find the unit associated w/an open file?, Michael Metcalf
      • Re: Is there a way to find the unit associated w/an open file?, jomarbueyes
• (Yet another) EQUIVALENCE problem in modules and common blocks, raj
  • Re: (Yet another) EQUIVALENCE problem in modules and common blocks, glen herrmannsfeldt
    • Re: (Yet another) EQUIVALENCE problem in modules and common blocks, Tim Prince
      • Re: (Yet another) EQUIVALENCE problem in modules and common blocks, glen herrmannsfeldt
      • Re: (Yet another) EQUIVALENCE problem in modules and common blocks, Richard Maine
      • Re: (Yet another) EQUIVALENCE problem in modules and common blocks, raj
      • Re: (Yet another) EQUIVALENCE problem in modules and common blocks, Ron Shepard
      • Re: (Yet another) EQUIVALENCE problem in modules and common blocks, Richard Maine
  • Re: (Yet another) EQUIVALENCE problem in modules and common blocks, Michael Metcalf
• Pointers and DLLs/shared libraries, Arjen Markus
  • Re: Pointers and DLLs/shared libraries, Craig Powers
    • Re: Pointers and DLLs/shared libraries, Arjen Markus
    • Re: Pointers and DLLs/shared libraries, Steve Lionel
      • Re: Pointers and DLLs/shared libraries, Arjen Markus
      • Re: Pointers and DLLs/shared libraries, James Van Buskirk
      • Re: Pointers and DLLs/shared libraries, Steve Lionel
• Question on call system, deltaquattro
  • Re: Question on call system, glen herrmannsfeldt
    • Re: Question on call system, Arjen Markus
    • Re: Question on call system, Richard Maine
• Fortran and LaTeX, Patrick Begou
  • Re: Fortran and LaTeX, Alois Steindl
  • Re: Fortran and LaTeX, Craig Dedo
  • Re: Fortran and LaTeX, Sebastian Hanigk
    • Re: Fortran and LaTeX, Janne Blomqvist
  • Re: Fortran and LaTeX, Klaus Wacker
  • Re: Fortran and LaTeX, deltaseq0
  • Re: Fortran and LaTeX, Richard Maine
  • Re: Fortran and LaTeX, Craig Powers
    • Re: Fortran and LaTeX, Tom Micevski
      • Re: Fortran and LaTeX, Craig Powers
  • Re: Fortran and LaTeX, Michael Prager
    • Re: Fortran and LaTeX, Patrick Begou
  • Re: Fortran and LaTeX, Bil Kleb
  • Re: Fortran and LaTeX, George N. White III
    • Re: Fortran and LaTeX, glen herrmannsfeldt
  • Re: Fortran and LaTeX, Wade Ward
  • Re: Fortran and LaTeX, Patrick Begou
• VB.NET Boolean vs Visual Fortran Logical, my . spam . 5406
  • Re: VB.NET Boolean vs Visual Fortran Logical, Steve Lionel
  • Re: VB.NET Boolean vs Visual Fortran Logical, Richard Maine
  • Re: VB.NET Boolean vs Visual Fortran Logical, James Van Buskirk
    • Re: VB.NET Boolean vs Visual Fortran Logical, Craig Powers
• Needed Language Reference in various languages!, RadSurfer
  • Re: Needed Language Reference in various languages!, Beliavsky
  • Re: Needed Language Reference in various languages!, Michael Metcalf
• TLE Satellite Data, RadSurfer
  • Re: TLE Satellite Data, Arjen Markus
    • Re: TLE Satellite Data, Michael Metcalf
      • Re: TLE Satellite Data, Arjen Markus
      • Re: TLE Satellite Data, Michel Olagnon
      • Re: TLE Satellite Data, Richard Maine
      • Re: TLE Satellite Data, glen herrmannsfeldt
    • Re: TLE Satellite Data, glen herrmannsfeldt
  • Re: TLE Satellite Data, Michel Olagnon
  • Re: TLE Satellite Data, RadSurfer
• #define in an "include file", sarvin . moghaddam
  • Re: #define in an "include file", Craig Dedo
    • Re: #define in an "include file", glen herrmannsfeldt
      • Re: #define in an "include file", Craig Dedo
      • Re: #define in an "include file", Richard Maine
      • Re: #define in an "include file", Wade Ward
    • Re: #define in an "include file", David Thompson
  • Re: #define in an "include file", tim prince
    • Re: #define in an "include file", tim prince
• speed up calculation suggestions, rleavitt
  • Re: speed up calculation suggestions, glen herrmannsfeldt
  • Re: speed up calculation suggestions, Richard Maine
    • Re: speed up calculation suggestions, Carlie J. Coats
  • Re: speed up calculation suggestions, Paul van Delst
    • Re: speed up calculation suggestions, rleavitt
      • Re: speed up calculation suggestions, Richard Maine
      • Re: speed up calculation suggestions, dpb
      • Re: speed up calculation suggestions, rleavitt
      • Re: speed up calculation suggestions, glen herrmannsfeldt
      • Re: speed up calculation suggestions, Craig Dedo
      • Re: speed up calculation suggestions, John Appleyard
      • Re: speed up calculation suggestions, glen herrmannsfeldt
      • Re: speed up calculation suggestions, glen herrmannsfeldt
      • Re: speed up calculation suggestions, Craig Dedo
      • Re: speed up calculation suggestions, Louis Krupp
      • Re: speed up calculation suggestions, Michael Metcalf
  • Re: speed up calculation suggestions, e p chandler
    • Re: speed up calculation suggestions, glen herrmannsfeldt
  • Re: speed up calculation suggestions, David Jones
    • Re: speed up calculation suggestions, rleavitt
      • Re: speed up calculation suggestions, Paul van Delst
      • Re: speed up calculation suggestions, Richard Maine
      • Re: speed up calculation suggestions, rleavitt
      • Re: speed up calculation suggestions, e p chandler
      • Re: speed up calculation suggestions, Paul van Delst
      • Re: speed up calculation suggestions, rleavitt
      • Re: speed up calculation suggestions, glen herrmannsfeldt
      • Re: speed up calculation suggestions, Carlie J. Coats
      • Re: speed up calculation suggestions, rleavitt
      • Re: speed up calculation suggestions, Paul van Delst
      • Re: speed up calculation suggestions, rleavitt
      • Re: speed up calculation suggestions, glen herrmannsfeldt
      • Re: speed up calculation suggestions, rleavitt
      • Re: speed up calculation suggestions, Wade Ward
      • Re: speed up calculation suggestions, rleavitt
      • Re: speed up calculation suggestions, Paul van Delst
      • Re: speed up calculation suggestions, dpb
      • Re: speed up calculation suggestions, e p chandler
      • Re: speed up calculation suggestions, Wade Ward
      • Re: speed up calculation suggestions, Gib
      • Re: speed up calculation suggestions, rleavitt
      • Re: speed up calculation suggestions, Wade Ward
      • Re: speed up calculation suggestions, ssragunath
      • Re: speed up calculation suggestions, e p chandler
      • Re: speed up calculation suggestions, Sebastian Hanigk
      • Re: speed up calculation suggestions, Paul van Delst
      • Re: speed up calculation suggestions, glen herrmannsfeldt
      • Re: speed up calculation suggestions, glen herrmannsfeldt
      • Re: speed up calculation suggestions, Wade Ward
  • Re: speed up calculation suggestions, Chip Coldwell
  • Re: speed up calculation suggestions, Terence
• association of pointers, John Harper
  • Re: association of pointers, glen herrmannsfeldt
  • Re: association of pointers, Richard Maine
    • Re: association of pointers, jtravs
      • Re: association of pointers, Paul van Delst
      • Re: association of pointers, Richard Maine
  • Re: association of pointers, mecej4
• Creating Dll CVF 6.6, Rafael Tini
  • Re: Creating Dll CVF 6.6, e p chandler
• How to Make F77 Program Faster (g95 compiler) ??, monir
  • Re: How to Make F77 Program Faster (g95 compiler) ??, Steven G. Kargl
    • Re: How to Make F77 Program Faster (g95 compiler) ??, deltaseq0
      • Re: How to Make F77 Program Faster (g95 compiler) ??, Steven G. Kargl
      • Re: How to Make F77 Program Faster (g95 compiler) ??, glen herrmannsfeldt
      • Re: How to Make F77 Program Faster (g95 compiler) ??, Tim Prince
      • Re: How to Make F77 Program Faster (g95 compiler) ??, deltaseq0
      • Re: How to Make F77 Program Faster (g95 compiler) ??, glen herrmannsfeldt
  • Re: How to Make F77 Program Faster (g95 compiler) ??, linuxl4
  • Re: How to Make F77 Program Faster (g95 compiler) ??, Carlie J. Coats
    • Re: How to Make F77 Program Faster (g95 compiler) ??, James Giles
      • Re: How to Make F77 Program Faster (g95 compiler) ??, Terence
      • Re: How to Make F77 Program Faster (g95 compiler) ??, Janne Blomqvist
      • Re: How to Make F77 Program Faster (g95 compiler) ??, James Giles
      • Re: How to Make F77 Program Faster (g95 compiler) ??, Janne Blomqvist
      • Re: How to Make F77 Program Faster (g95 compiler) ??, linuxl4
      • Re: How to Make F77 Program Faster (g95 compiler) ??, Carlie J. Coats
      • Re: How to Make F77 Program Faster (g95 compiler) ??, Bart Vandewoestyne
      • Re: How to Make F77 Program Faster (g95 compiler) ??, Bart Vandewoestyne
      • Re: How to Make F77 Program Faster (g95 compiler) ??, Paul van Delst
      • Re: How to Make F77 Program Faster (g95 compiler) ??, Bart Vandewoestyne
      • Re: How to Make F77 Program Faster (g95 compiler) ??, Richard Maine
      • Re: How to Make F77 Program Faster (g95 compiler) ??, Paul van Delst
      • Re: How to Make F77 Program Faster (g95 compiler) ??, Bart Vandewoestyne
      • Re: How to Make F77 Program Faster (g95 compiler) ??, glen herrmannsfeldt
      • Re: How to Make F77 Program Faster (g95 compiler) ??, monir
      • Re: How to Make F77 Program Faster (g95 compiler) ??, Steven G. Kargl
      • Re: How to Make F77 Program Faster (g95 compiler) ??, monir
      • Re: How to Make F77 Program Faster (g95 compiler) ??, Carlie J. Coats
      • Re: How to Make F77 Program Faster (g95 compiler) ??, Steven G. Kargl
      • Re: How to Make F77 Program Faster (g95 compiler) ??, glen herrmannsfeldt
      • Re: How to Make F77 Program Faster (g95 compiler) ??, David Thompson
  • Re: How to Make F77 Program Faster (g95 compiler) ??, Chip Coldwell
    • Re: How to Make F77 Program Faster (g95 compiler) ??, Steve Lionel
  • Re: How to Make F77 Program Faster (g95 compiler) ??, mecej4
    • Re: How to Make F77 Program Faster (g95 compiler) ??, Richard Maine
      • Re: How to Make F77 Program Faster (g95 compiler) ??, Gary Scott
      • Re: How to Make F77 Program Faster (g95 compiler) ??, John Harper
      • Re: How to Make F77 Program Faster (g95 compiler) ??, Richard Maine
      • Re: How to Make F77 Program Faster (g95 compiler) ??, monir
      • Re: How to Make F77 Program Faster (g95 compiler) ??, Richard Maine
      • Re: How to Make F77 Program Faster (g95 compiler) ??, glen herrmannsfeldt
      • Re: How to Make F77 Program Faster (g95 compiler) ??, Tim Prince
      • Re: How to Make F77 Program Faster (g95 compiler) ??, Steven G. Kargl
      • Re: How to Make F77 Program Faster (g95 compiler) ??, highegg
      • Re: How to Make F77 Program Faster (g95 compiler) ??, Ian Gay
• Wrapping routines, Arjen Markus
  • Re: Wrapping routines, Richard Maine
    • Re: Wrapping routines, Arjen Markus
  • Re: Wrapping routines, Fei Liu
    • Re: Wrapping routines, Arjen Markus
• vim, ctags, and fortran source browsing, Fei Liu
  • Re: vim, ctags, and fortran source browsing, Craig Powers
    • Re: vim, ctags, and fortran source browsing, Fei Liu
      • Re: vim, ctags, and fortran source browsing, Craig Powers
      • Re: vim, ctags, and fortran source browsing, Fei Liu
      • Re: vim, ctags, and fortran source browsing, Craig Powers
      • Re: vim, ctags, and fortran source browsing, Fei Liu
      • Re: vim, ctags, and fortran source browsing, Craig Powers
      • Re: vim, ctags, and fortran source browsing, Craig Powers
      • Re: vim, ctags, and fortran source browsing, Fei Liu
      • Re: vim, ctags, and fortran source browsing, Craig Powers
      • Re: vim, ctags, and fortran source browsing, Fei Liu
      • Re: vim, ctags, and fortran source browsing, Craig Powers
    • Re: vim, ctags, and fortran source browsing, Fei Liu
  • Re: vim, ctags, and fortran source browsing, linuxl4
• Re: Cubic Spline Integration, Ingo Thies
• CALL statement in FORALL block, bau12374
  • Re: CALL statement in FORALL block, paul . richard . thomas
  • Re: CALL statement in FORALL block, James Van Buskirk
    • Re: CALL statement in FORALL block, paul . richard . thomas
  • Re: CALL statement in FORALL block, Richard Maine
• Re: I know this has been discussed before, but..., David Thompson
• Does PGI Fortran Compiler support some F2003 standard?, li . simula
  • Re: Does PGI Fortran Compiler support some F2003 standard?, Michael Metcalf
• Win32 API and gfortran, James Van Buskirk
  • Re: Win32 API and gfortran, Steve Lionel
    • Re: Win32 API and gfortran, James Van Buskirk
      • Re: Win32 API and gfortran, Steve Lionel
      • Re: Win32 API and gfortran, James Van Buskirk
      • Re: Win32 API and gfortran, Steve Lionel
      • Re: Win32 API and gfortran, James Van Buskirk
      • Re: Win32 API and gfortran, Steve Lionel
      • Re: Win32 API and gfortran, James Van Buskirk
      • Re: Win32 API and gfortran, glen herrmannsfeldt
      • Re: Win32 API and gfortran, Steven G. Kargl
      • Re: Win32 API and gfortran, Greg Lindahl
      • Re: Win32 API and gfortran, James Van Buskirk
      • Re: Win32 API and gfortran, Steve Lionel
      • Re: Win32 API and gfortran, James Van Buskirk
      • Re: Win32 API and gfortran, Steve Lionel
      • Re: Win32 API and gfortran, Steve Lionel
    • Re: Win32 API and gfortran, stevenb . gcc
      • Re: Win32 API and gfortran, glen herrmannsfeldt
      • Re: Win32 API and gfortran, Jugoslav Dujic
      • Re: Win32 API and gfortran, Steve Lionel
      • Re: Win32 API and gfortran, Tobias Burnus
      • Re: Win32 API and gfortran, Steve Lionel
      • Re: Win32 API and gfortran, Tobias Burnus
      • Re: Win32 API and gfortran, Steve Lionel
      • Re: Win32 API and gfortran, e p chandler
      • Re: Win32 API and gfortran, Gary Scott
      • Re: Win32 API and gfortran, Wade Ward
      • Re: Win32 API and gfortran, Jugoslav Dujic
      • Re: Win32 API and gfortran, Steve Lionel
      • Re: Win32 API and gfortran, dpb
      • Re: Win32 API and gfortran, Steve Lionel
      • Re: Win32 API and gfortran, dpb
      • Re: Win32 API and gfortran, Craig Powers
  • Re: Win32 API and gfortran, alexzenk
    • Re: Win32 API and gfortran, Gary Scott
  • Re: Win32 API and gfortran, e p chandler
    • Re: Win32 API and gfortran, James Van Buskirk
      • Re: Win32 API and gfortran, e p chandler
• gfortran and OpenMP, Bart Vandewoestyne
  • Re: gfortran and OpenMP, highegg
    • Re: gfortran and OpenMP, Bart Vandewoestyne
  • Re: gfortran and OpenMP, deltaseq0
    • Re: gfortran and OpenMP, Bart Vandewoestyne
  • Re: gfortran and OpenMP, Bart Vandewoestyne
    • Re: gfortran and OpenMP, Salvatore
      • Re: gfortran and OpenMP, malzfreund
      • Re: gfortran and OpenMP, linuxl4
      • Re: gfortran and OpenMP, Bart Vandewoestyne
      • Re: gfortran and OpenMP, linuxl4
      • Re: gfortran and OpenMP, linuxl4
      • Re: gfortran and OpenMP, Toon Moene
      • Re: gfortran and OpenMP, Tobias Burnus
      • Re: gfortran and OpenMP, Bart Vandewoestyne
      • Re: gfortran and OpenMP, linuxl4
      • Re: gfortran and OpenMP, Tobias Burnus
      • Re: gfortran and OpenMP, linuxl4
      • Re: gfortran and OpenMP, Steven G. Kargl
      • Re: gfortran and OpenMP, linuxl4
      • Re: gfortran and OpenMP, deltaseq0
      • Re: gfortran and OpenMP, linuxl4
      • Re: gfortran and OpenMP, Tobias Burnus
      • Re: gfortran and OpenMP, Steven G. Kargl
      • Re: gfortran and OpenMP, linuxl4
    • Re: gfortran and OpenMP, linuxl4
      • Re: gfortran and OpenMP, malzfreund
• Reusability: arguments vs modules, deltaquattro
  • Re: Reusability: arguments vs modules, deltaseq0
  • Re: Reusability: arguments vs modules, Walter Spector
    • Re: Reusability: arguments vs modules, gary . l . scott
    • Re: Reusability: arguments vs modules, pixel
      • Re: Reusability: arguments vs modules, Walter Spector
      • Re: Reusability: arguments vs modules, Ron Shepard
      • Re: Reusability: arguments vs modules, Walter Spector
    • Re: Reusability: arguments vs modules, deltaquattro
  • Re: Reusability: arguments vs modules, Paul van Delst
    • Re: Reusability: arguments vs modules, fj
      • Re: Reusability: arguments vs modules, Dan Nagle
      • Re: Reusability: arguments vs modules, fj
      • Re: Reusability: arguments vs modules, Paul van Delst
      • Re: Reusability: arguments vs modules, Dan Nagle
    • Re: Reusability: arguments vs modules, deltaquattro
  • Re: Reusability: arguments vs modules, Craig Powers
    • Re: Reusability: arguments vs modules, Steve Lionel
      • Re: Reusability: arguments vs modules, Richard Maine
      • Re: Reusability: arguments vs modules, glen herrmannsfeldt
• Challenge: reading ascii data, David Frank
  • Re: Challenge: reading ascii data, David Frank
    • Re: Challenge: reading ascii data, robin
    • Re: Challenge: reading ascii data, Rich Townsend
      • Re: Challenge: reading ascii data, David Frank
      • Re: Challenge: reading ascii data, Rich Townsend
      • Re: Challenge: reading ascii data, David Frank
      • Re: Challenge: reading ascii data, Dick Hendrickson
      • Re: Challenge: reading ascii data, David Frank
  • Re: Challenge: reading ascii data, David Flower
    • Re: Challenge: reading ascii data, robin
  • Re: Challenge: reading ascii data, Bil Kleb
    • Re: Challenge: reading ascii data, David Frank
      • Re: Challenge: reading ascii data, Bil Kleb
      • Re: Challenge: reading ascii data, David Frank
      • Re: Challenge: reading ascii data, Bil Kleb
      • Re: Challenge: reading ascii data, David Frank
      • Re: Challenge: reading ascii data, Bil Kleb
      • Re: Challenge: reading ascii data, Paul van Delst
      • Re: Challenge: reading ascii data, Harold Stevens
      • Re: Challenge: reading ascii data, Eric I.
      • Re: Challenge: reading ascii data, David Frank
      • Re: Challenge: reading ascii data, Bil Kleb
      • Re: Challenge: reading ascii data, David Frank
      • Re: Challenge: reading ascii data, Bil Kleb
      • Re: Challenge: reading ascii data, robin
      • Re: Challenge: reading ascii data, Eric I.
      • Re: Challenge: reading ascii data, David Frank
      • Re: Challenge: reading ascii data, Eric I.
      • Re: Challenge: reading ascii data, David Frank
      • Re: Challenge: reading ascii data, robin
  • Re: Challenge: reading ascii data, David Frank
    • Re: Challenge: reading ascii data, Bil Kleb
    • Re: Challenge: reading ascii data, robin
      • Re: Challenge: reading ascii data, David Frank
      • Re: Challenge: reading ascii data, robin
      • Re: Challenge: reading ascii data, glen herrmannsfeldt
      • Re: Challenge: reading ascii data, robin
    • Re: Challenge: reading ascii data, robin
      • Re: Challenge: reading ascii data, LR
      • Re: Challenge: reading ascii data, glen herrmannsfeldt
      • Re: Challenge: reading ascii data, LR
      • Re: Challenge: reading ascii data, glen herrmannsfeldt
      • Re: Challenge: reading ascii data, robin
  • Re: Challenge: reading ascii data, Eric I.
    • Re: Challenge: reading ascii data, Eric I.
      • Re: Challenge: reading ascii data, robin
      • Re: Challenge: reading ascii data, Eric I.
      • Re: Challenge: reading ascii data, robin
      • Re: Challenge: reading ascii data, Eric I.
      • Re: Challenge: reading ascii data, robin
  • Re: Challenge: reading ascii data, mdvandeelen@xxxxxxxxx
    • Re: Challenge: reading ascii data, Bil Kleb
      • Re: Challenge: reading ascii data, Bil Kleb
• dynamic allocation doubt, raj
  • Re: dynamic allocation doubt, Reinhold Bader
    • Re: dynamic allocation doubt, Paul van Delst
  • Re: dynamic allocation doubt, Dan Nagle
    • Re: dynamic allocation doubt, Richard Maine
  • Re: dynamic allocation doubt, Michael Metcalf
  • Re: dynamic allocation doubt, Colin Watters
    • Re: dynamic allocation doubt, Richard Maine
      • Re: dynamic allocation doubt, James Tursa
      • Re: dynamic allocation doubt, raj
• Implicit none with IVF, johnharwood@xxxxxxxxxx
  • Re: Implicit none with IVF, Tim Prince
• Introduction to Programming in Fortran 95, Shaun
• Building Unix based library in windows, vijay . varanasi
  • Re: Building Unix based library in windows, Richard Maine
    • Re: Building Unix based library in windows, James Van Buskirk
    • Re: Building Unix based library in windows, vijay . varanasi
      • Re: Building Unix based library in windows, Richard Maine
      • Re: Building Unix based library in windows, deltaseq0
      • Re: Building Unix based library in windows, dpb
      • Re: Building Unix based library in windows, Craig Powers
• Control ofUSB devices, Terence
  • Re: Control ofUSB devices, Terence
  • Re: Control ofUSB devices, Daniel Platt
    • Re: Control ofUSB devices, Rich Townsend
      • Re: Control ofUSB devices, Richard Maine
      • Re: Control ofUSB devices, Daniel Platt
      • Re: Control ofUSB devices, Terence
      • Re: Control ofUSB devices, Rich Townsend
      • Re: Control ofUSB devices, Terence
• Control of USB devices, Terence
  • Re: Control of USB devices, Terence
• NEWBIE QUESTION: "Warning: Extension: REAL array index at (1)" - please help, Martin Jørgensen
  • Re: NEWBIE QUESTION: "Warning: Extension: REAL array index at (1)" - please help, Michael Metcalf
    • Re: NEWBIE QUESTION: "Warning: Extension: REAL array index at (1)" - please help, Michael Metcalf
  • Re: NEWBIE QUESTION: "Warning: Extension: REAL array index at (1)" - please help, dpb
    • Re: NEWBIE QUESTION: "Warning: Extension: REAL array index at (1)" - please help, Martin Jørgensen
  • Re: NEWBIE QUESTION: "Warning: Extension: REAL array index at (1)" - please help, Steven G. Kargl
  • Re: NEWBIE QUESTION: "Warning: Extension: REAL array index at (1)" - please help, Richard Maine
    • Re: NEWBIE QUESTION: "Warning: Extension: REAL array index at (1)" - please help, Richard Maine
    • Re: NEWBIE QUESTION: "Warning: Extension: REAL array index at (1)" - please help, glen herrmannsfeldt
      • Re: NEWBIE QUESTION: "Warning: Extension: REAL array index at (1)" - please help, Martin Jørgensen
      • Re: NEWBIE QUESTION: "Warning: Extension: REAL array index at (1)" - please help, Dick Hendrickson
      • Re: NEWBIE QUESTION: "Warning: Extension: REAL array index at (1)" - please help, John Harper
      • Re: NEWBIE QUESTION: "Warning: Extension: REAL array index at (1)" - please help, Dick Hendrickson
      • Re: NEWBIE QUESTION: "Warning: Extension: REAL array index at (1)" - please help, Martin Jørgensen
      • Re: NEWBIE QUESTION: "Warning: Extension: REAL array index at (1)" - please help, Dan Nagle
      • Re: NEWBIE QUESTION: "Warning: Extension: REAL array index at (1)" - please help, glen herrmannsfeldt
    • Re: NEWBIE QUESTION: "Warning: Extension: REAL array index at (1)" - please help, Martin Jørgensen
  • Re: NEWBIE QUESTION: "Warning: Extension: REAL array index at (1)" - please help, Dick Hendrickson
• CASE SELECT vs IF statements, Pietro
  • Re: CASE SELECT vs IF statements, Michael Metcalf
    • Re: CASE SELECT vs IF statements, James Giles
      • Re: CASE SELECT vs IF statements, Michael Metcalf
      • Re: CASE SELECT vs IF statements, glen herrmannsfeldt
      • Re: CASE SELECT vs IF statements, mcalhoun
  • Re: CASE SELECT vs IF statements, robin
• Word of warning: MacOSX Leopard upgrade breaks several Fortrans, Al Greynolds
  • Re: Word of warning: MacOSX Leopard upgrade breaks several Fortrans, Gordon Sande
  • Re: Word of warning: MacOSX Leopard upgrade breaks several Fortrans, Dave Seaman
  • Re: Word of warning: MacOSX Leopard upgrade breaks several Fortrans, Steve Lionel
    • Re: Word of warning: MacOSX Leopard upgrade breaks several Fortrans, glen herrmannsfeldt
    • Re: Word of warning: MacOSX Leopard upgrade breaks several Fortrans, Al Greynolds
• Text Editor for Programming, Kurda Yon
  • Re: Text Editor for Programming, Walter Spector
    • Re: Text Editor for Programming, Kurda Yon
      • Re: Text Editor for Programming, david.baxendale@xxxxxxxxx
  • Re: Text Editor for Programming, Kamaraju S Kusumanchi
  • Re: Text Editor for Programming, ajmf77
• translation of coordinates using minloc, Johan
  • Re: translation of coordinates using minloc, Dick Hendrickson
• IVF odd man out (again!), Al Greynolds
  • Re: IVF odd man out (again!), Steve Lionel
    • Re: IVF odd man out (again!), Steve Lionel
• reading two separate files, kipps
  • Re: reading two separate files, dpb
    • Re: reading two separate files, kipps
      • Re: reading two separate files, deltaseq0
      • Re: reading two separate files, Richard Maine
      • Re: reading two separate files, jomarbueyes
      • Re: reading two separate files, kipps
      • Re: reading two separate files, dpb
      • Re: reading two separate files, dpb
      • Re: reading two separate files, Paul van Delst
      • Re: reading two separate files, Terence
      • Re: reading two separate files, kipps
      • Re: reading two separate files, Dan Nagle
      • Re: reading two separate files, Paul van Delst
      • Re: reading two separate files, Richard Maine
      • Re: reading two separate files, Michael Metcalf
      • Re: reading two separate files, Richard Maine
      • Re: reading two separate files, Terence
      • Re: reading two separate files, John Harper
      • Re: reading two separate files, Terence
      • Re: reading two separate files, Dan Nagle
      • Re: reading two separate files, Bill Gunshannon
      • Re: reading two separate files, Gary Scott
      • Re: reading two separate files, Bill Gunshannon
      • Re: reading two separate files, Paul van Delst
      • Re: reading two separate files, Dan Nagle
      • Re: reading two separate files, Richard Maine
      • Re: reading two separate files, Paul van Delst
      • Re: reading two separate files, Terence
      • Re: reading two separate files, sara_patty
      • Re: reading two separate files, Michael Metcalf
      • Re: reading two separate files, Richard Maine
      • Re: reading two separate files, dpb
• Unexpected STATEMENT FN, GT
  • Re: Unexpected STATEMENT FN, mposh372
    • Re: Unexpected STATEMENT FN, GT
  • Re: Unexpected STATEMENT FN, Herman D . Knoble
• fortran code reading ascii file., rajkrai
  • Re: fortran code reading ascii file., Jan Gerrit Kootstra
    • Re: fortran code reading ascii file., glen herrmannsfeldt
      • Re: fortran code reading ascii file., robin
      • Re: fortran code reading ascii file., glen herrmannsfeldt
      • Re: fortran code reading ascii file., robin
    • Re: fortran code reading ascii file., robin
  • Re: fortran code reading ascii file., glen herrmannsfeldt
  • Re: fortran code reading ascii file., glen herrmannsfeldt
  • Re: fortran code reading ascii file., David Frank
    • Re: fortran code reading ascii file., Terence
    • Re: fortran code reading ascii file., Bil Kleb
      • Re: fortran code reading ascii file., dpb
    • Re: fortran code reading ascii file., robin
  • Re: fortran code reading ascii file., Gib Bogle
• Regexp Format for G95 in the jEdit editor., david.baxendale@xxxxxxxxx
  • Re: Regexp Format for G95 in the jEdit editor., Arjen Markus
    • Re: Regexp Format for G95 in the jEdit editor., david.baxendale@xxxxxxxxx
      • Re: Regexp Format for G95 in the jEdit editor., Arjen Markus
      • Re: Regexp Format for G95 in the jEdit editor., david.baxendale@xxxxxxxxx
• GNU-Fortran, Silvio Binato
  • Re: GNU-Fortran, John Smith
    • Re: GNU-Fortran, Terence
    • Re: GNU-Fortran, Terence
      • Re: GNU-Fortran, John Smith
      • Re: GNU-Fortran, Terence
      • Re: GNU-Fortran, John Smith
      • Re: GNU-Fortran, Steven G. Kargl
  • Re: GNU-Fortran, Jerry DeLisle
    • Re: GNU-Fortran, Terence
      • Re: GNU-Fortran, Greg Lindahl
      • Re: GNU-Fortran, Gary Scott
      • Re: GNU-Fortran, Greg Lindahl
      • Re: GNU-Fortran, Richard Maine
      • Re: GNU-Fortran, Gary Scott
      • Hardware Limits of Yesteryear (Was: GNU-Fortran), Craig Dedo
      • Re: Hardware Limits of Yesteryear (Was: GNU-Fortran), Louis Krupp
      • Re: Hardware Limits of Yesteryear (Was: GNU-Fortran), Sjouke Burry
      • Re: Hardware Limits of Yesteryear (Was: GNU-Fortran), Craig Dedo
      • Re: Hardware Limits of Yesteryear (Was: GNU-Fortran), Dick Hendrickson
      • Re: Hardware Limits of Yesteryear (Was: GNU-Fortran), James Giles
      • Re: Hardware Limits of Yesteryear (Was: GNU-Fortran), James Parsly
      • Re: Hardware Limits of Yesteryear (Was: GNU-Fortran), dpb
      • Re: Hardware Limits of Yesteryear (Was: GNU-Fortran), deltaseq0
      • Re: Hardware Limits of Yesteryear (Was: GNU-Fortran), dpb
      • Re: Hardware Limits of Yesteryear (Was: GNU-Fortran), James Parsly
      • Re: Hardware Limits of Yesteryear (Was: GNU-Fortran), Walter Spector
      • Re: Hardware Limits of Yesteryear, Richard Maine
      • Re: Hardware Limits of Yesteryear, Walter Spector
      • Re: Hardware Limits of Yesteryear (Was: GNU-Fortran), glen herrmannsfeldt
      • Re: Hardware Limits of Yesteryear (Was: GNU-Fortran), gary . l . scott
      • Re: Hardware Limits of Yesteryear (Was: GNU-Fortran), glen herrmannsfeldt
      • Re: GNU-Fortran, Terence