comp.lang.fortran

• Thread Index

---

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

We are proud to have Web Hosting and Rack Housing from 9 Net Avenue Deutschland.
(17)