comp.lang.fortran

• Thread Index

---

• Re: reading back a partially-written record on direct access
  • From: glen herrmannsfeldt
• Re: reading back a partially-written record on direct access
  • From: Richard Maine
• Re: Starting to doubt fortran
  • From: glen herrmannsfeldt
• Re: The Elements of Fortran Style
  • From: Phillip Helbig---remove CLOTHES to reply
• Re: copy and move files
  • From: Charles Russell
• Re: The Elements of Fortran Style
  • From: Gary Scott
• Re: The Elements of Fortran Style
  • From: Phillip Helbig---remove CLOTHES to reply
• Re: The Elements of Fortran Style
  • From: Phillip Helbig---remove CLOTHES to reply
• Re: Starting to doubt fortran
  • From: Gary Scott
• Re: John Backus 1924-2007
  • From: Gary Scott
• Re: Importing from Microsoft Access in Fortran
  • From: Gary Scott
• Re: reading back a partially-written record on direct access
  • From: Richard Maine
• Re: Starting to doubt fortran
  • From: Richard Maine
• Re: copy and move files
  • From: Charles Russell
• Re: Importing from Microsoft Access in Fortran
  • From: klaus . knebel
• Re: Starting to doubt fortran
  • From: Dan Nagle
• Re: LQ Decomposition and Null Space
  • From: Pierre Asselin
• Re: Why float is called as 'float', not 'real'?
  • From: Gordon Sande
• Re: Starting to doubt fortran
  • From: Pierre Asselin
• Re: Starting to doubt fortran
  • From: Pierre Asselin
• Re: array operations on non-conforming arrays -- do compilers catch them?
  • From: Beliavsky
• Re: Read a .BMP into Fortran?
  • From: Edward N Bromhead
• Re: John Backus 1924-2007
  • From: Edward N Bromhead
• Re: Starting to doubt fortran
  • From: Dan Nagle
• Re: reading back a partially-written record on direct access
  • From: glen herrmannsfeldt
• Re: John Backus 1924-2007
  • From: Jim Backus
• Importing from Microsoft Access in Fortran
  • From: iman
• Re: variable content lost
  • From: Louis Krupp
• reading back a partially-written record on direct access
  • From: Thomas König
• Re: Starting to doubt fortran
  • From: Lane Straatman
• Re: variable content lost
  • From: Richard Maine
• Re: Starting to doubt fortran
  • From: Richard Maine
• Re: Starting to doubt fortran
  • From: robert . corbett
• Re: variable content lost
  • From: Listad
• Re: variable content lost
  • From: Steven G. Kargl
• Re: Starting to doubt fortran
  • From: Pierre Asselin
• Re: Why float is called as 'float', not 'real'?
  • From: Pierre Asselin
• Re: Sample polling program code?
  • From: dpb
• Re: variable content lost
  • From: Beliavsky
• Re: variable content lost
  • From: Richard Maine
• Re: array operations on non-conforming arrays -- do compilers catch them?
  • From: Lane Straatman
• Re: Sample polling program code?
  • From: glen herrmannsfeldt
• Re: variable content lost
  • From: Beliavsky
• Re: variable content lost
  • From: Listad
• Re: variable content lost
  • From: Beliavsky
• variable content lost
  • From: listad
• Re: array operations on non-conforming arrays -- do compilers catch them?
  • From: Bart Vandewoestyne
• Re: undefined variable problem
  • From: Bart Vandewoestyne
• Re: undefined variable problem
  • From: glen herrmannsfeldt
• array operations on non-conforming arrays -- do compilers catch them?
  • From: Beliavsky
• Re: Sample polling program code?
  • From: glen herrmannsfeldt
• Re: undefined variable problem
  • From: Gordon Sande
• Re: undefined variable problem
  • From: Bart Vandewoestyne
• Re: Starting to doubt fortran
  • From: Richard Maine
• Re: Starting to doubt fortran
  • From: glen herrmannsfeldt
• Re: Starting to doubt fortran
  • From: Charles Russell
• Re: Sample polling program code?
  • From: dpb
• Re: Starting to doubt fortran
  • From: glen herrmannsfeldt
• Re: Starting to doubt fortran
  • From: Gordon Sande
• Re: undefined variable problem
  • From: John Appleyard
• Re: Starting to doubt fortran
  • From: Ben Hetland
• Re: variable names for different fortrans
  • From: Richard Maine
• Re: Starting to doubt fortran
  • From: Richard Maine
• Re: Why float is called as 'float', not 'real'?
  • From: gary . l . scott
• Re: undefined variable problem
  • From: Bart Vandewoestyne
• Re: Converting a string to reals
  • From: psycho_dad
• Re: Starting to doubt fortran
  • From: Gordon Sande
• Re: How old is the average Fortran programmer?
  • From: John Wingate
• Re: Starting to doubt fortran
  • From: Beliavsky
• Re: Starting to doubt fortran
  • From: Charles Russell
• Re: variable names for different fortrans
  • From: Beliavsky
• Re: undefined variable problem
  • From: Bart Vandewoestyne
• Re: Why float is called as 'float', not 'real'?
  • From: Dan Nagle
• Re: Starting to doubt fortran
  • From: Ben Hetland
• Re: variable names for different fortrans
  • From: Ben Hetland
• Re: Why float is called as 'float', not 'real'?
  • From: blmblm
• Re: Why float is called as 'float', not 'real'?
  • From: Gordon Sande
• Re: Starting to doubt fortran
  • From: Gordon Sande
• Re: Why float is called as 'float', not 'real'?
  • From: Gordon Sande
• Re: Starting to doubt fortran
  • From: Gordon Sande
• Re: undefined variable problem
  • From: Reinhold Bader
• Re: variable names for different fortrans
  • From: Beliavsky
• Re: Why float is called as 'float', not 'real'?
  • From: Gary Scott
• Re: Why float is called as 'float', not 'real'?
  • From: blmblm
• Re: Why float is called as 'float', not 'real'?
  • From: blmblm
• Re: Starting to doubt fortran
  • From: Ben Hetland
• Re: undefined variable problem
  • From: Catherine Rees Lay
• Re: undefined variable problem
  • From: Arjen Markus
• Re: variable names for different fortrans
  • From: Ben Hetland
• Re: Starting to doubt fortran
  • From: glen herrmannsfeldt
• undefined variable problem
  • From: Bart Vandewoestyne
• Re: calculation accuracy
  • From: glen herrmannsfeldt
• Re: Starting to doubt fortran
  • From: glen herrmannsfeldt
• Re: Starting to doubt fortran
  • From: Jan Vorbrüggen
• Re: Starting to doubt fortran
  • From: Richard Maine
• Re: Starting to doubt fortran
  • From: Charles Russell
• Re: Starting to doubt fortran
  • From: Charles Russell
• Re: How old is the average Fortran programmer?
  • From: Fernando M. Roxo da Motta
• Re: calculation accuracy
  • From: Tim Prince
• Re: calculation accuracy
  • From: Richard Maine
• Re: Why float is called as 'float', not 'real'?
  • From: Richard Maine
• Re: calculation accuracy
  • From: Lane Straatman
• Re: calculation accuracy
  • From: Richard Maine
• Re: calculation accuracy
  • From: Lane Straatman
• Re: Why float is called as 'float', not 'real'?
  • From: Lane Straatman
• Re: Why float is called as 'float', not 'real'?
  • From: Gordon Sande
• Re: Starting to doubt fortran
  • From: Gordon Sande
• Re: Why float is called as 'float', not 'real'?
  • From: blmblm
• Re: John Backus 1924-2007
  • From: subspace
• Re: calculation accuracy
  • From: subspace
• Re: Starting to doubt fortran
  • From: Ben Hetland
• Re: Starting to doubt fortran
  • From: Ben Hetland
• Re: John Backus 1924-2007
  • From: Jim Backus
• Re: Why float is called as 'float', not 'real'?
  • From: Lane Straatman
• Re: Converting a string to reals
  • From: Craig Powers
• Re: Starting to doubt fortran
  • From: Craig Powers
• Re: Starting to doubt fortran
  • From: blmblm
• Re: Starting to doubt fortran
  • From: blmblm
• Re: Converting a string to reals
  • From: psycho_dad
• Re: Converting a string to reals
  • From: psycho_dad
• Re: Converting a string to reals
  • From: e p chandler
• Re: Starting to doubt fortran
  • From: Gordon Sande
• LQ Decomposition and Null Space
  • From: michael
• Re: Starting to doubt fortran
  • From: highegg
• RE: Converting a string to reals
  • From: meek
• Converting a string to reals
  • From: psycho_dad
• Re: Starting to doubt fortran
  • From: Ben Hetland
• Re: BOZ literal constants, a puzzle for us Standard-loving types.
  • From: glen herrmannsfeldt
• writing fortran variable to file in gdb
  • From: jadoo.dost@xxxxxxxxx
• Re: copy and move files
  • From: dpb
• Re: copy and move files
  • From: Fluid
• Re: copy and move files
  • From: dpb
• Re: copy and move files
  • From: Fluid
• Re: copy and move files
  • From: Walter Spector
• Re: copy and move files
  • From: Arjen Markus
• Re: copy and move files
  • From: Beliavsky
• Re: BOZ literal constants, a puzzle for us Standard-loving types.
  • From: Gary Scott
• Re: copy and move files
  • From: Gib Bogle
• Re: copy and move files
  • From: Arjen Markus
• copy and move files
  • From: Fluid
• Re: BOZ literal constants, a puzzle for us Standard-loving types.
  • From: glen herrmannsfeldt
• Re: BOZ literal constants, a puzzle for us Standard-loving types.
  • From: Brooks Moses
• Re: BOZ literal constants, a puzzle for us Standard-loving types.
  • From: Brooks Moses
• Re: BOZ literal constants, a puzzle for us Standard-loving types.
  • From: Brooks Moses
• Re: BOZ literal constants, a puzzle for us Standard-loving types.
  • From: glen herrmannsfeldt
• Re: calculation accuracy
  • From: glen herrmannsfeldt
• Re: calculation accuracy
  • From: robert . corbett
• Re: calculation accuracy
  • From: robert . corbett
• Re: BOZ literal constants, a puzzle for us Standard-loving types.
  • From: glen herrmannsfeldt
• Re: BOZ literal constants, a puzzle for us Standard-loving types.
  • From: glen herrmannsfeldt
• Re: BOZ literal constants, a puzzle for us Standard-loving types.
  • From: Steven G. Kargl
• Re: Polyhedron 2005 benchmark results
  • From: robert . corbett
• Re: funny variable names in gdb
  • From: robert . corbett
• Re: calculation accuracy
  • From: robert . corbett
• Re: BOZ literal constants, a puzzle for us Standard-loving types.
  • From: Brooks Moses
• Re: BOZ literal constants, a puzzle for us Standard-loving types.
  • From: Brooks Moses
• Re: BOZ literal constants, a puzzle for us Standard-loving types.
  • From: glen herrmannsfeldt
• Re: calculation accuracy
  • From: FX
• funny variable names in gdb
  • From: jadoo.dost@xxxxxxxxx
• Re: calculation accuracy
  • From: glen herrmannsfeldt
• Re: Why float is called as 'float', not 'real'?
  • From: blmblm
• Re: BOZ literal constants, a puzzle for us Standard-loving types.
  • From: glen herrmannsfeldt
• Re: calculation accuracy
  • From: Terence
• Re: BOZ literal constants, a puzzle for us Standard-loving types.
  • From: Steven G. Kargl
• Re: calculation accuracy
  • From: Beliavsky
• Re: Why float is called as 'float', not 'real'?
  • From: Lane Straatman
• Re: BOZ literal constants, a puzzle for us Standard-loving types.
  • From: glen herrmannsfeldt
• Re: BOZ literal constants, a puzzle for us Standard-loving types.
  • From: Steven G. Kargl
• Re: BOZ literal constants, a puzzle for us Standard-loving types.
  • From: glen herrmannsfeldt
• Re: calculation accuracy
  • From: Ben Hetland
• Re: calculation accuracy
  • From: Lane Straatman
• Re: BOZ literal constants, a puzzle for us Standard-loving types.
  • From: Toon Moene
• RE: calculation accuracy
  • From: meek
• Re: BOZ literal constants, a puzzle for us Standard-loving types.
  • From: Steven G. Kargl
• Re: calculation accuracy
  • From: Beliavsky
• Re: unable to view symbols in gdb
  • From: jadoo.dost@xxxxxxxxx
• Re: calculation accuracy
  • From: Thomas Koenig
• BOZ literal constants, a puzzle for us Standard-loving types.
  • From: Toon Moene
• Re: variable names for different fortrans
  • From: Craig Powers
• unable to view symbols in gdb
  • From: jadoo.dost@xxxxxxxxx
• Re: Print statement within If-Then block changes output!!!????
  • From: Richard Maine
• Re: How to read .csv file in fortran77?
  • From: Herman D . Knoble
• Re: How to read .csv file in fortran77?
  • From: Nye
• Re: How to read .csv file in fortran77?
  • From: Beliavsky
• Re: Print statement within If-Then block changes output!!!????
  • From: Kevin G. Rhoads
• Re: Polyhedron 2005 benchmark results
  • From: Jan Vorbrüggen
• Re: How old is the average Fortran programmer?
  • From: Jan Vorbrüggen
• Re: How old is the average Fortran programmer?
  • From: Jan Vorbrüggen
• Re: calculation accuracy
  • From: Ben Hetland
• Re: How to read .csv file in fortran77?
  • From: Herman D . Knoble
• Re: http or tcp/ip
  • From: Jan Vorbrüggen
• Re: Fortran with a GUI??
  • From: Ben Hetland
• Re: http or tcp/ip
  • From: Jan Vorbrüggen
• Re: http or tcp/ip
  • From: Jan Vorbrüggen
• How to read .csv file in fortran77?
  • From: Nye
• Re: variable names for different fortrans
  • From: Ben Hetland
• Re: Is C faster than fortran?
  • From: FX
• Re: howto find where a variable is initialized
  • From: David Flower
• Re: Why float is called as 'float', not 'real'?
  • From: ttw
• Re: Starting to doubt fortran
  • From: Tim Prince
• Re: calculation accuracy
  • From: John Campbell
• ifort 9.1 on 64-bit openSuSE 10.2 (?)
  • From: Matthew Halfant
• Re: calculation accuracy
  • From: Rodrigo López Negrete
• Re: calculation accuracy
  • From: Rodrigo López Negrete
• Re: Why float is called as 'float', not 'real'?
  • From: Dave Seaman
• Re: calculation accuracy
  • From: e p chandler
• Re: Why float is called as 'float', not 'real'?
  • From: ttw
• Re: howto find where a variable is initialized
  • From: glen herrmannsfeldt
• Re: Starting to doubt fortran
  • From: Beliavsky
• Re: calculation accuracy
  • From: John Harper
• Re: Is C faster than fortran?
  • From: Lane Straatman
• Re: variable names for different fortrans
  • From: glen herrmannsfeldt
• Re: calculation accuracy
  • From: Lane Straatman
• Re: Why float is called as 'float', not 'real'?
  • From: blmblm
• Re: Profiling Fortran 77 using gprof on linux
  • From: Tim Prince
• Re: calculation accuracy
  • From: Richard Maine
• Re: calculation accuracy
  • From: e p chandler
• Re: calculation accuracy
  • From: John Harper
• Re: calculation accuracy
  • From: Lane Straatman
• Re: calculation accuracy
  • From: Richard Maine
• Re: calculation accuracy
  • From: glen herrmannsfeldt
• Re: Profiling Fortran 77 using gprof on linux
  • From: Kamaraju S Kusumanchi
• calculation accuracy
  • From: Ben
• Re: How to inspect an array value in gdb?
  • From: FX
• Re: howto find where a variable is initialized
  • From: Craig Powers
• Re: Why float is called as 'float', not 'real'?
  • From: Lane Straatman
• Re: howto find where a variable is initialized
  • From: Beliavsky
• Fortran
  • From: jfrench690
• Re: variable names for different fortrans
  • From: glen herrmannsfeldt
• Re: variable names for different fortrans
  • From: Ben Hetland
• Re: variable names for different fortrans
  • From: Ben Hetland
• Re: How old is the average Fortran programmer?
  • From: Ben Hetland
• Re: Starting to doubt fortran
  • From: Ron Shepard
• Re: howto find where a variable is initialized
  • From: Richard Maine
• Re: Starting to doubt fortran
  • From: Charles Russell
• Re: How to inspect an array value in gdb?
  • From: www
• Re: How to inspect an array value in gdb?
  • From: FX
• Re: Merits of fortran
  • From: Pierre Asselin
• How to inspect an array value in gdb?
  • From: www
• Re: howto find where a variable is initialized
  • From: FX
• Re: Why float is called as 'float', not 'real'?
  • From: Janne Blomqvist
• Re: How old is the average Fortran programmer?
  • From: Dr Ivan D. Reid
• Re: http or tcp/ip
  • From: Pierre Asselin
• Re: howto find where a variable is initialized
  • From: Herman D . Knoble
• Re: Why float is called as 'float', not 'real'?
  • From: glen herrmannsfeldt
• Re: Starting to doubt fortran
  • From: Beliavsky
• Re: howto find where a variable is initialized
  • From: Richard Maine
• Re: Fortran with a GUI??
  • From: baf
• Re: howto find where a variable is initialized
  • From: mintoo
• Re: Fortran with a GUI??
  • From: Bil Kleb
• Re: Fortran90/95 Call tree
  • From: Bil Kleb
• Re: howto find where a variable is initialized
  • From: mecej4
• Re: how to display the source file in ddd?
  • From: Tim Prince
• Re: Profiling Fortran 77 using gprof on linux
  • From: Tim Prince
• Re: Why float is called as 'float', not 'real'?
  • From: Lane Straatman
• Re: Why float is called as 'float', not 'real'?
  • From: glen herrmannsfeldt
• Re: Read a .BMP into Fortran?
  • From: Gary Scott
• Re: Read a .BMP into Fortran?
  • From: David . Paterson
• Re: Why float is called as 'float', not 'real'?
  • From: glen herrmannsfeldt
• Re: Fortran with a GUI??
  • From: Gary Scott
• Re: Why float is called as 'float', not 'real'?
  • From: Brooks Moses
• Re: How do I make a library file with XLF?
  • From: Shawn
• Re: Fortran with a GUI??
  • From: widmar
• Re: Read a .BMP into Fortran?
  • From: e p chandler
• Re: FYI: Canaimasoft Web Site Back Up
  • From: William Asher
• howto find where a variable is initialized
  • From: mintoo
• Re: Read a .BMP into Fortran?
  • From: gary . l . scott
• FYI: Canaimasoft Web Site Back Up
  • From: gary . l . scott
• Read a .BMP into Fortran?
  • From: David . Paterson
• Re: Fortran90/95 Call tree
  • From: glen herrmannsfeldt
• Re: OT usage nitpick (was Re: Starting to doubt fortran)
  • From: blmblm
• Re: How do I make a library file with XLF?
  • From: Paul van Delst
• Re: OT usage nitpick (was Re: Starting to doubt fortran)
  • From: John Harper
• Re: OT usage nitpick (was Re: Starting to doubt fortran)
  • From: e p chandler
• Re: how to call a file.out in a fortran file?
  • From: Élodie
• Re: OT usage nitpick (was Re: Starting to doubt fortran)
  • From: blmblm
• Re: Why float is called as 'float', not 'real'?
  • From: blmblm
• Re: how to call a file.out in a fortran file?
  • From: Élodie
• Re: Fortran90/95 Call tree
  • From: glen herrmannsfeldt
• Re: Why float is called as 'float', not 'real'?
  • From: blmblm
• Re: Fortran90/95 Call tree
  • From: jadoo.dost@xxxxxxxxx
• Re: how to call a file.out in a fortran file?
  • From: e p chandler
• Re: how to call a file.out in a fortran file?
  • From: jadoo.dost@xxxxxxxxx
• how to call a file.out in a fortran file?
  • From: Élodie
• How do I make a library file with XLF?
  • From: Shawn
• Fortran90/95 Call tree
  • From: jadoo.dost@xxxxxxxxx
• Re: Why float is called as 'float', not 'real'?
  • From: Toon Moene
• Re: Newbie Question!
  • From: Kamaraju S Kusumanchi
• Re: Profiling Fortran 77 using gprof on linux
  • From: Kamaraju S Kusumanchi
• Re: how to display the source file in ddd?
  • From: Kamaraju S Kusumanchi
• Re: declaring variables in the code
  • From: glen herrmannsfeldt
• Re: How old is the average Fortran programmer?
  • From: Gordon Sande
• Re: How old is the average Fortran programmer?
  • From: Kevin G. Rhoads
• Re: How old is the average Fortran programmer?
  • From: Kevin G. Rhoads
• Re: Why float is called as 'float', not 'real'?
  • From: Kevin G. Rhoads
• Re: How old is the average Fortran programmer?
  • From: KingHarvest
• Re: Why float is called as 'float', not 'real'?
  • From: Ron Shepard
• Re: declaring variables in the code
  • From: Dick Hendrickson
• Re: Fortran with a GUI??
  • From: Hani Ibrahim
• Re: OT usage nitpick (was Re: Starting to doubt fortran)
  • From: Gary Scott
• Re: OT usage nitpick (was Re: Starting to doubt fortran)
  • From: Nomad.C@xxxxxxxxx
• Re: Why float is called as 'float', not 'real'?
  • From: Gordon Sande
• Re: OT usage nitpick (was Re: Starting to doubt fortran)
  • From: blmblm
• Re: OT usage nitpick (was Re: Starting to doubt fortran)
  • From: Louis Krupp
• Re: how to get the gradient of a function?
  • From: Terence
• Re: OT usage nitpick (was Re: Starting to doubt fortran)
  • From: Terence
• Re: Why float is called as 'float', not 'real'?
  • From: blmblm
• Re: OT usage nitpick (was Re: Starting to doubt fortran)
  • From: blmblm
• Re: OT usage nitpick (was Re: Starting to doubt fortran)
  • From: Louis Krupp
• Re: Why float is called as 'float', not 'real'?
  • From: Richard Maine
• Re: how to get the gradient of a function?
  • From: Arjen Markus
• Re: Fortran with a GUI??
  • From: Arjen Markus
• Re: declaring variables in the code
  • From: Louis Krupp
• Re: Why float is called as 'float', not 'real'?
  • From: highegg
• Re: Why float is called as 'float', not 'real'?
  • From: ttw
• Re: Why float is called as 'float', not 'real'?
  • From: glen herrmannsfeldt
• Re: .mul ? what does it mean ?
  • From: Leif Harcke
• Re: Starting to doubt fortran
  • From: Tim Prince
• Re: declaring variables in the code
  • From: Richard Maine
• Re: Why float is called as 'float', not 'real'?
  • From: ttw
• Re: Why float is called as 'float', not 'real'?
  • From: Gary Scott
• Re: Why float is called as 'float', not 'real'?
  • From: sureal
• Re: Why float is called as 'float', not 'real'?
  • From: sureal
• OT usage nitpick (was Re: Starting to doubt fortran)
  • From: blmblm
• Re: declaring variables in the code
  • From: Lynn
• Re: Starting to doubt fortran
  • From: e p chandler
• Re: declaring variables in the code
  • From: John Harper
• Re: Why float is called as 'float', not 'real'?
  • From: Lane Straatman
• Re: How old is the average Fortran programmer?
  • From: Tom Micevski
• Re: Why float is called as 'float', not 'real'?
  • From: John Harper
• Re: How old is the average Fortran programmer?
  • From: John Harper
• Re: How old is the average Fortran programmer?
  • From: John Harper
• Re: Starting to doubt fortran
  • From: Gary Scott
• Re: declaring variables in the code
  • From: Lynn
• Re: Why float is called as 'float', not 'real'?
  • From: Gordon Sande
• Re: Starting to doubt fortran
  • From: Lane Straatman
• Re: Starting to doubt fortran
  • From: highegg
• Re: Why float is called as 'float', not 'real'?
  • From: Lane Straatman
• Re: Why float is called as 'float', not 'real'?
  • From: Lane Straatman
• Re: declaring variables in the code
  • From: Beliavsky
• Re: declaring variables in the code
  • From: Gary Scott
• Re: declaring variables in the code
  • From: Louis Krupp
• Re: Why float is called as 'float', not 'real'?
  • From: Richard Maine
• Re: Starting to doubt fortran
  • From: e p chandler
• Re: How old is the average Fortran programmer?
  • From: George N. White III
• Re: Starting to doubt fortran
  • From: Gary Scott
• Re: Starting to doubt fortran
  • From: Nomad.C@xxxxxxxxx
• Re: Starting to doubt fortran
  • From: Beliavsky
• Re: declaring variables in the code
  • From: Gary Scott
• Starting to doubt fortran
  • From: Nomad.C@xxxxxxxxx
• Re: How old is the average Fortran programmer?
  • From: George N. White III
• Re: adding and displaying harmonic series
  • From: robin
• Re: adding and displaying harmonic series
  • From: robin
• Re: adding and displaying harmonic series
  • From: robin
• Re: declaring variables in the code
  • From: Gordon Sande
• Re: Why float is called as 'float', not 'real'?
  • From: Gordon Sande
• Re: declaring variables in the code
  • From: Beliavsky
• Re: Intel Fortran 9.1
  • From: Tom Micevski
• Re: Intel Fortran 9.1
  • From: Tim Prince
• Re: Intel Fortran 9.1
  • From: Steve Lionel
• Re: Intel Fortran 9.1
  • From: gsal
• Intel Fortran 9.1
  • From: michael
• Re: .mul ? what does it mean ?
  • From: glen herrmannsfeldt
• Re: increasing width
  • From: glen herrmannsfeldt
• Re: Why float is called as 'float', not 'real'?
  • From: Dan Nagle
• Re: Different results with same executable using openmp clause
  • From: FX
• Re: increasing width
  • From: FX
• Different results with same executable using openmp clause
  • From: anshu . bhola
• Re: Why float is called as 'float', not 'real'?
  • From: Louis Krupp
• Re: declaring variables in the code
  • From: Colin Watters
• Re: How old is the average Fortran programmer?
  • From: Richard Steiner
• Re: Why float is called as 'float', not 'real'?
  • From: Lane Straatman
• Re: declaring variables in the code
  • From: Brooks Moses
• declaring variables in the code
  • From: Lynn
• Re: http or tcp/ip
  • From: Brooks Moses
• Re: how to get the gradient of a function?
  • From: e p chandler
• how to get the gradient of a function?
  • From: zhngbn
• Re: Newbie Question!
  • From: Lane Straatman
• Re: Newbie Question!
  • From: Beliavsky
• Re: increasing width
  • From: Lane Straatman
• Re: Why float is called as 'float', not 'real'?
  • From: Gordon Sande
• Re: Why float is called as 'float', not 'real'?
  • From: Richard Maine
• Re: Why float is called as 'float', not 'real'?
  • From: Lane Straatman
• Re: increasing width
  • From: robin
• Re: increasing width
  • From: robin
• Re: increasing width
  • From: robin
• Re: Newbie Question!
  • From: mecej4
• Re: Why float is called as 'float', not 'real'?
  • From: Richard Maine
• Re: .mul ? what does it mean ?
  • From: mecej4
• Re: Why float is called as 'float', not 'real'?
  • From: Lane Straatman
• .mul ? what does it mean ?
  • From: coolchick
• Re: Profiling Fortran 77 using gprof on linux
  • From: coolchick
• Re: Fortran with a GUI??
  • From: Gary Scott
• Fortran with a GUI??
  • From: Nomad.C@xxxxxxxxx
• Re: Why float is called as 'float', not 'real'?
  • From: glen herrmannsfeldt
• Re: Newbie Question!
  • From: Tim Prince
• Newbie Question!
  • From: Nomad.C@xxxxxxxxx
• Re: Why float is called as 'float', not 'real'?
  • From: Richard Maine
• Re: Why float is called as 'float', not 'real'?
  • From: Gary Scott
• ffnet 0.6 - neural networks and fortran
  • From: Marek Wojciechowski
• Re: Why float is called as 'float', not 'real'?
  • From: Louis Krupp
• Re: How old is the average Fortran programmer?
  • From: Sebastian Hanigk
• Re: Why float is called as 'float', not 'real'?
  • From: glen herrmannsfeldt
• Re: How old is the average Fortran programmer?
  • From: Dave Weatherall
• Re: Polyhedron 2005 benchmark results
  • From: robert . corbett
• Re: Why float is called as 'float', not 'real'?
  • From: Gib Bogle
• Re: Why float is called as 'float', not 'real'?
  • From: ttw
• Why float is called as 'float', not 'real'?
  • From: DirtyHarry
• Re: How old is the average Fortran programmer?
  • From: Tim Prince
• Re: How old is the average Fortran programmer?
  • From: J. F. Cornwall
• Re: http or tcp/ip
  • From: Gary Scott
• Re: How old is the average Fortran programmer?
  • From: Bob Chapman
• Re: How old is the average Fortran programmer?
  • From: Richard Maine
• Re: John Backus 1924-2007
  • From: subspace
• Re: How old is the average Fortran programmer?
  • From: subspace
• Re: How old is the average Fortran programmer?
  • From: Charles Russell
• Re: How old is the average Fortran programmer?
  • From: Richard Maine
• Re: How old is the average Fortran programmer?
  • From: J. F. Cornwall
• Re: How old is the average Fortran programmer?
  • From: glen herrmannsfeldt
• Libraries on Linux
  • From: Hĺkan Lane
• Re: Equivalence of derived types with default initializers?
  • From: robert . corbett
• Re: How old is the average Fortran programmer?
  • From: Ken Fairfield
• Re: http or tcp/ip
  • From: Lane Straatman
• Re: http or tcp/ip
  • From: Richard Maine
• Re: How old is the average Fortran programmer?
  • From: gary . l . scott
• Re: How old is the average Fortran programmer?
  • From: Thomas Koenig
• Re: http or tcp/ip
  • From: glen herrmannsfeldt
• Re: http or tcp/ip
  • From: gary . l . scott
• Re: Libraries on Linux
  • From: Lane Straatman
• Re: http or tcp/ip
  • From: gary . l . scott
• Re: http or tcp/ip
  • From: Richard Maine
• Re: http or tcp/ip
  • From: Dick Hendrickson
• Re: http or tcp/ip
  • From: gary . l . scott
• Re: http or tcp/ip
  • From: Dick Hendrickson
• Re: http or tcp/ip
  • From: Jan Vorbrüggen
• Re: Merits of fortran
  • From: highegg
• Re: http or tcp/ip
  • From: Steve Lionel
• Re: Libraries on Linux
  • From: Tim Prince
• Re: http or tcp/ip
  • From: gary . l . scott
• Re: CVF Version 6.1.A Bug
  • From: Steve Lionel
• Re: http or tcp/ip
  • From: Pierre Asselin
• Re: Merits of fortran
  • From: Pierre Asselin
• Re: Print statement within If-Then block changes output!!!????
  • From: glen herrmannsfeldt
• Re: http or tcp/ip
  • From: glen herrmannsfeldt
• Re: http or tcp/ip
  • From: Jan Vorbrüggen
• Re: http or tcp/ip
  • From: Gary Scott
• Re: Print statement within If-Then block changes output!!!????
  • From: Gary Scott
• Re: Polyhedron 2005 benchmark results
  • From: FX
• Re: http or tcp/ip
  • From: Dan Nagle
• Re: http or tcp/ip
  • From: Jan Vorbrüggen
• Re: http or tcp/ip
  • From: Jan Vorbrüggen
• Re: http or tcp/ip
  • From: Jan Vorbrüggen
• Re: http or tcp/ip
  • From: Jan Vorbrüggen
• Re: Equivalence of derived types with default initializers?
  • From: Brooks Moses
• Re: Efficient arrays for artificial neural networks?
  • From: Jan Vorbrüggen
• Re: Polyhedron 2005 benchmark results
  • From: Jan Vorbrüggen
• Re: CVF Version 6.1.A Bug
  • From: John Harper
• how to display the source file in ddd?
  • From: zhngbn
• Re: Equivalence of derived types with default initializers?
  • From: robert . corbett
• Re: MR&C 7.9
  • From: glen herrmannsfeldt
• Re: CVF Version 6.1.A Bug
  • From: Richard Maine
• CVF Version 6.1.A Bug
  • From: michael
• Re: Print statement within If-Then block changes output!!!????
  • From: Richard Maine
• Re: Print statement within If-Then block changes output!!!????
  • From: glen herrmannsfeldt
• Re: Print statement within If-Then block changes output!!!????
  • From: e p chandler
• Re: Profiling Fortran 77 using gprof on linux
  • From: Tim Prince
• Re: MR&C 7.9
  • From: Lane Straatman
• Re: alpha stage OpenMP compilers for Fortran 95 and C
  • From: glen herrmannsfeldt
• Re: Print statement within If-Then block changes output!!!????
  • From: Lane Straatman
• Re: alpha stage OpenMP compilers for Fortran 95 and C
  • From: Michael Metcalf
• Re: MR&C 7.9
  • From: Ken Fairfield
• Re: Equivalence of derived types with default initializers?
  • From: Brooks Moses
• Re: alpha stage OpenMP compilers for Fortran 95 and C
  • From: Michael Metcalf
• Profiling Fortran 77 using gprof on linux
  • From: coolchick
• Re: Merits of fortran
  • From: Toon Moene
• Re: Print statement within If-Then block changes output!!!????
  • From: glen herrmannsfeldt
• Re: alpha stage OpenMP compilers for Fortran 95 and C
  • From: glen herrmannsfeldt
• Re: Print statement within If-Then block changes output!!!????
  • From: Richard Maine
• Re: Print statement within If-Then block changes output!!!????
  • From: e p chandler
• Re: Print statement within If-Then block changes output!!!????
  • From: Lane Straatman
• Re: Print statement within If-Then block changes output!!!????
  • From: Dick Hendrickson
• Re: Print statement within If-Then block changes output!!!????
  • From: Gordon Sande
• Re: alpha stage OpenMP compilers for Fortran 95 and C
  • From: FX
• alpha stage OpenMP compilers for Fortran 95 and C
  • From: Beliavsky
• Re: Print statement within If-Then block changes output!!!????
  • From: e p chandler
• Re: Merits of fortran
  • From: Pierre Asselin
• Re: Print statement within If-Then block changes output!!!????
  • From: e p chandler
• Re: Print statement within If-Then block changes output!!!????
  • From: Richard Maine
• Re: MR&C 7.9
  • From: Jan Vorbrüggen
• Re: Print statement within If-Then block changes output!!!????
  • From: Dan Nagle
• Re: Print statement within If-Then block changes output!!!????
  • From: FX
• Re: Print statement within If-Then block changes output!!!????
  • From: Jugoslav Dujic
• Re: Equivalence of derived types with default initializers?
  • From: Dan Nagle
• Re: AMD Opteron + intel fortran (linux)
  • From: Jan Vorbrüggen
• Visual Fortran add-in program - VFTool 2.20
  • From: kangzhao
• Re: make
  • From: Hani Ibrahim
• Re: Equivalence of derived types with default initializers?
  • From: Richard Maine
• Re: complex number & sort
  • From: nakisa
• Re: Equivalence of derived types with default initializers?
  • From: Brooks Moses
• Re: make
  • From: gsal
• Re: Equivalence of derived types with default initializers?
  • From: Richard Maine
• Re: integer factorization subroutine
  • From: Terence
• Re: John Backus 1924-2007
  • From: Eugene Miya
• Re: Equivalence of derived types with default initializers?
  • From: Dick Hendrickson
• Re: The Elements of Fortran Style
  • From: Richard Maine
• Re: http or tcp/ip
  • From: Brooks Moses
• Re: The Elements of Fortran Style
  • From: Gary Scott
• Re: The Elements of Fortran Style
  • From: Gordon Sande
• Re: make
  • From: glen herrmannsfeldt
• Re: g77 efficiency
  • From: Tobias Burnus
• Re: The Elements of Fortran Style
  • From: Dan Nagle
• The Elements of Fortran Style
  • From: Michael Metcalf
• Re: John Backus 1924-2007
  • From: Lane Straatman
• Re: g77 efficiency
  • From: Beliavsky
• Re: John Backus 1924-2007
  • From: Eugene Miya
• Re: Redefining intrinsic operators
  • From: Richard Maine
• Re: John Backus 1924-2007
  • From: Eugene Miya
• g77 efficiency
  • From: Gene Wagenbreth
• Re: How old is the average Fortran programmer?
  • From: Richard Maine
• Re: Merits of fortran
  • From: FX
• Re: Redefining intrinsic operators
  • From: Dick Hendrickson
• Re: Gfortran 2 years behind G95 and still not ready for prime time
  • From: Beliavsky
• Re: Print statement within If-Then block changes output!!!????
  • From: Paul van Delst
• Re: Print statement within If-Then block changes output!!!????
  • From: watsteel
• Re: Gfortran 2 years behind G95 and still not ready for prime time
  • From: Dick Hendrickson
• Re: Gfortran 2 years behind G95 and still not ready for prime time
  • From: paul . richard . thomas
• Re: Print statement within If-Then block changes output!!!????
  • From: watsteel
• Re: Merits of fortran
  • From: Michael Metcalf
• Re: Merits of fortran
  • From: Pierre Asselin
• Re: About IMSL library and global variable
  • From: highegg
• Re: Print statement within If-Then block changes output!!!????
  • From: e p chandler
• Re: Redefining intrinsic operators
  • From: Michael Metcalf
• Re: About IMSL library and global variable
  • From: Beliavsky
• Re: About IMSL library and global variable
  • From: Steve Lionel
• Re: make
  • From: Beliavsky
• Redefining intrinsic operators
  • From: FX
• Re: About IMSL library and global variable
  • From: Beliavsky
• Re: make
  • From: Tim Prince
• Re: How old is the average Fortran programmer?
  • From: Tim Prince
• make
  • From: tuli
• Re: How old is the average Fortran programmer?
  • From: michael
• About IMSL library and global variable
  • From: Way
• about IMSL library and global variable
  • From: cswbww@xxxxxxxxx
• Re: iso_c_binding: use of c_int in an initialization expression
  • From: John Harper
• Re: iso_c_binding: use of c_int in an initialization expression
  • From: Richard Maine
• Re: iso_c_binding: use of c_int in an initialization expression
  • From: glen herrmannsfeldt
• Re: iso_c_binding: use of c_int in an initialization expression
  • From: Lane Straatman
• Re: iso_c_binding: use of c_int in an initialization expression
  • From: Richard Maine
• Re: Print statement within If-Then block changes output!!!????
  • From: Beliavsky
• Re: iso_c_binding: use of c_int in an initialization expression
  • From: Lane Straatman
• Re: http or tcp/ip
  • From: Toon Moene
• Re: Print statement within If-Then block changes output!!!????
  • From: watsteel
• Re: iso_c_binding: use of c_int in an initialization expression
  • From: Richard Maine
• Re: http or tcp/ip
  • From: Richard Maine
• Re: How old is the average Fortran programmer?
  • From: Toon Moene
• Re: Code Too Large for MS FORTRAN
  • From: Toon Moene
• Re: John Backus 1924-2007
  • From: John Harper
• Re: How old is the average Fortran programmer?
  • From: Richard Maine
• Re: Append to screen IO
  • From: Richard Maine
• Re: Merits of fortran
  • From: Toon Moene
• Re: Any free Fortran 90-95 compilers for Cray Y-MP ?
  • From: Toon Moene
• Re: integer factorization subroutine
  • From: glen herrmannsfeldt
• Re: Append to screen IO
  • From: John Harper
• Re: John Backus 1924-2007
  • From: Eugene Miya
• Re: John Backus 1924-2007
  • From: Terence
• Re: John Backus 1924-2007
  • From: Lane Straatman
• Re: Print statement within If-Then block changes output!!!????
  • From: Gib Bogle
• Re: integer factorization subroutine
  • From: Dick Hendrickson
• Re: Print statement within If-Then block changes output!!!????
  • From: Gib Bogle
• Re: How old is the average Fortran programmer?
  • From: Toon Moene
• Re: Print statement within If-Then block changes output!!!????
  • From: Beliavsky
• Re: Print statement within If-Then block changes output!!!????
  • From: watsteel
• Re: Print statement within If-Then block changes output!!!????
  • From: watsteel
• Re: integer factorization subroutine
  • From: Lane Straatman
• Re: John Backus 1924-2007
  • From: Charles Russell
• Re: John Backus 1924-2007
  • From: rms
• Re: integer factorization subroutine
  • From: Paul van Delst
• Re: iso_c_binding: use of c_int in an initialization expression
  • From: gary . l . scott
• Re: Array of procedure pointers in F2003?
  • From: highegg
• Array of procedure pointers in F2003?
  • From: Arjen Markus
• Re: NAGWare Fortran 95 Syntax Checker Available online
  • From: Arjen Markus
• Re: John Backus 1924-2007
  • From: rusi_pathan
• Re: iso_c_binding: use of c_int in an initialization expression
  • From: Dan Nagle
• Re: complex number & sort
  • From: highegg
• Re: iso_c_binding: use of c_int in an initialization expression
  • From: Brooks Moses
• Re: iso_c_binding: use of c_int in an initialization expression
  • From: Brooks Moses
• Re: complex number & sort
  • From: nakisa
• Re: complex number & sort
  • From: highegg
• Re: complex number & sort
  • From: nakisa
• Re: complex number & sort
  • From: highegg
• Re: complex number & sort
  • From: highegg
• Re: John Backus 1924-2007
  • From: aeroguy
• Re: complex number & sort
  • From: nakisa
• Re: integer factorization subroutine
  • From: Dick Hendrickson
• John Backus 1924-2007
  • From: Beliavsky
• Re: integer factorization subroutine
  • From: Gordon Sande
• Re: iso_c_binding: use of c_int in an initialization expression
  • From: FX
• Re: integer factorization subroutine
  • From: Lane Straatman
• Re: iso_c_binding: use of c_int in an initialization expression
  • From: Dan Nagle
• Re: integer factorization subroutine
  • From: Terence
• Re: integer factorization subroutine
  • From: Terence
• Re: Reading in a file as raw hex bytes?
  • From: Terence
• Re: iso_c_binding: use of c_int in an initialization expression
  • From: Steve Lionel
• Re: iso_c_binding: use of c_int in an initialization expression
  • From: Dan Nagle
• RE: Reading in a file as raw hex bytes?
  • From: meek
• Re: iso_c_binding: use of c_int in an initialization expression
  • From: Tobias Burnus
• Re: iso_c_binding: use of c_int in an initialization expression
  • From: Steve Lionel
• iso_c_binding: use of c_int in an initialization expression
  • From: nobat
• Re: complex number & sort
  • From: Kevin G. Rhoads
• Re: integer factorization subroutine
  • From: Paul van Delst
• Re: integer factorization subroutine
  • From: ttw
• Re: Zombie Code -- Re: How old is the average Fortran programmer?
  • From: Beliavsky
• Re: Zombie Code -- Re: How old is the average Fortran programmer?
  • From: Michael Metcalf
• Re: Zombie Code -- Re: How old is the average Fortran programmer?
  • From: Gordon Sande
• Re: Zombie Code -- Re: How old is the average Fortran programmer?
  • From: Ben Hetland
• Re: complex number & sort
  • From: highegg
• Re: variable names for different fortrans
  • From: PJH
• RE: complex number & sort
  • From: meek
• Re: complex number & sort
  • From: Michael Metcalf
• complex number & sort
  • From: nakisa
• Re: integer factorization subroutine
  • From: Gordon Sande
• Re: integer factorization subroutine
  • From: Arjen Markus
• integer factorization subroutine
  • From: Bart Vandewoestyne
• Re: Append to screen IO
  • From: Ben Hetland
• Re: variable names for different fortrans
  • From: Brooks Moses
• Re: Aren't the fuddy-duddies in the group going to comment on Fortress
  • From: J. F. Cornwall
• Re: Print statement within If-Then block changes output!!!????
  • From: Brooks Moses
• Re: Print statement within If-Then block changes output!!!????
  • From: Dan Nagle
• Re: Print statement within If-Then block changes output!!!????
  • From: Colin Watters
• Re: Aren't the fuddy-duddies in the group going to comment on Fortress
  • From: Sebastian Hanigk
• Re: http or tcp/ip
  • From: Gary Scott
• Re: http or tcp/ip
  • From: Gary Scott
• Re: http or tcp/ip
  • From: Brooks Moses
• Re: Print statement within If-Then block changes output!!!????
  • From: Ron Shepard
• Re: Print statement within If-Then block changes output!!!????
  • From: Colin Watters
• Re: Print statement within If-Then block changes output!!!????
  • From: Steven G. Kargl
• Re: Print statement within If-Then block changes output!!!????
  • From: Beliavsky
• Re: Print statement within If-Then block changes output!!!????
  • From: Dan Nagle
• Print statement within If-Then block changes output!!!????
  • From: watsteel
• Re: http or tcp/ip
  • From: Steve Lionel
• Re: variable names for different fortrans
  • From: Dan Nagle
• Re: variable names for different fortrans
  • From: Beliavsky
• Re: http or tcp/ip
  • From: David Frank
• Re: http or tcp/ip
  • From: PJH
• Re: variable names for different fortrans
  • From: PJH
• NAGWare Fortran 95 Syntax Checker Available online
  • From: Beliavsky
• Re: http or tcp/ip
  • From: Brooks Moses
• Re: http or tcp/ip
  • From: Gary Scott
• Re: Gfortran 2 years behind G95 and still not ready for prime time
  • From: Brooks Moses
• Re: http or tcp/ip
  • From: Gary Scott
• Re: http or tcp/ip
  • From: Gary Scott
• Re: http or tcp/ip
  • From: Gary Scott
• Re: http or tcp/ip
  • From: Steve Lionel
• Re: Gfortran 2 years behind G95 and still not ready for prime time
  • From: Kamaraju S Kusumanchi
• Re: http or tcp/ip
  • From: Gary Scott
• Re: http or tcp/ip
  • From: Gary Scott
• Re: http or tcp/ip
  • From: Steve Lionel
• Re: Aren't the fuddy-duddies in the group going to comment on Fortress
  • From: Brooks Moses
• Re: Aren't the fuddy-duddies in the group going to comment on Fortress
  • From: glen herrmannsfeldt
• Re: http or tcp/ip
  • From: Gary Scott
• Re: http or tcp/ip
  • From: Beliavsky
• Re: Gfortran 2 years behind G95 and still not ready for prime time
  • From: Joost
• Re: http or tcp/ip
  • From: David Frank
• Re: Aren't the fuddy-duddies in the group going to comment on Fortress
  • From: analyst41
• Re: variable names for different fortrans
  • From: David Frank
• Re: variable names for different fortrans
  • From: Thomas Koenig
• Re: variable names for different fortrans
  • From: glen herrmannsfeldt
• Re: MR&C 7.9
  • From: Richard Maine
• Re: variable names for different fortrans
  • From: Terence
• Re: Polyhedron 2005 benchmark results
  • From: Steven G. Kargl
• Re: Polyhedron 2005 benchmark results
  • From: Brooks Moses
• Re: Aren't the fuddy-duddies in the group going to comment on Fortress
  • From: robin
• Fortran language course
  • From: maan . alasfoor
• Re: Sun Studio 12 early access compilers go live
  • From: robert . corbett
• Re: Polyhedron 2005 benchmark results
  • From: Steven G. Kargl
• Re: variable names for different fortrans
  • From: Lane Straatman
• Re: MR&C 7.9
  • From: Brooks Moses
• Re: Guess what's sitting on my desk?
  • From: J. F. Cornwall
• Re: MR&C 7.9
  • From: Lane Straatman
• Re: variable names for different fortrans
  • From: Richard Maine
• Re: MR&C 7.9
  • From: Richard Maine
• Re: F2k8 BITS
  • From: Richard Maine
• Re: variable names for different fortrans
  • From: Gordon Sande
• Re: MR&C 7.9
  • From: Dan Nagle
• Re: Wrong recipient (obviously!) Sorry, folks.
  • From: Lynn McGuire
• Re: MR&C 7.9
  • From: Lane Straatman
• Re: F-compiler installation
  • From: e p chandler
• Re: MR&C 7.9
  • From: Brooks Moses
• Re: variable names for different fortrans
  • From: Brooks Moses
• Re: MR&C 7.9
  • From: Lane Straatman
• Re: F2k8 BITS
  • From: Gary Scott
• Re: variable names for different fortrans
  • From: Richard Maine
• Re: MR&C 7.9
  • From: Brooks Moses
• Re: variable names for different fortrans
  • From: Lane Straatman
• Re: F2k8 BITS
  • From: Brooks Moses
• Re: MR&C 7.9
  • From: Richard Maine
• Re: AMD Opteron + intel fortran (linux)
  • From: Rich Townsend
• Re: Gfortran 2 years behind G95 and still not ready for prime time
  • From: Brooks Moses
• Re: fortran equivalent of matlab num2str
  • From: Lane Straatman
• Equivalence of derived types with default initializers?
  • From: Brooks Moses
• Re: AMD Opteron + intel fortran (linux)
  • From: Beliavsky
• Re: Gfortran 2 years behind G95 and still not ready for prime time
  • From: Thomas Koenig
• Re: Gfortran 2 years behind G95 and still not ready for prime time
  • From: Beliavsky
• F2k8 BITS
  • From: gary . l . scott
• Re: MR&C 7.9
  • From: Lane Straatman
• Re: Gfortran 2 years behind G95 and still not ready for prime time
  • From: Beliavsky
• Re: MR&C 7.9
  • From: Brooks Moses
• Re: Need help with fortran file output
  • From: glen herrmannsfeldt
• Re: Need help with fortran file output
  • From: Richard Maine
• Re: MR&C 7.9
  • From: Richard Maine
• Re: Gfortran 2 years behind G95 and still not ready for prime time
  • From: FX
• Re: MR&C 7.9
  • From: Lane Straatman
• Re: F-compiler installation
  • From: Kevin G. Rhoads
• Re: Gfortran 2 years behind G95 and still not ready for prime time
  • From: Charles Russell
• Re: AMD Opteron + intel fortran (linux)
  • From: Paul van Delst
• Re: AMD Opteron + intel fortran (linux)
  • From: pantarei
• Re: variable names for different fortrans
  • From: pantarei
• Re: http or tcp/ip
  • From: gary . l . scott
• Re: Wrong recipient (obviously!) Sorry, folks.
  • From: Dick Hendrickson
• Re: Append to screen IO
  • From: Dick Hendrickson
• Re: How old is the average Fortran programmer?
  • From: Dick Hendrickson
• Re: http or tcp/ip
  • From: e p chandler
• Re: Gfortran 2 years behind G95 and still not ready for prime time
  • From: Dick Hendrickson
• Re: Polyhedron 2005 benchmark results
  • From: Steve Lionel
• Re: Polyhedron 2005 benchmark results
  • From: FX
• Re: Polyhedron 2005 benchmark results
  • From: Brooks Moses
• Re: Gfortran 2 years behind G95 and still not ready for prime time
  • From: Brooks Moses
• Re: Gfortran 2 years behind G95 and still not ready for prime time
  • From: Brooks Moses
• http or tcp/ip
  • From: allelopath
• Re: Function kind attribute: valid fortran?
  • From: James Giles
• Re: Windows gfortran binaries
  • From: Ian Gay
• Re: Function kind attribute: valid fortran?
  • From: Paul van Delst
• Re: Function kind attribute: valid fortran?
  • From: Richard Maine
• Re: Polyhedron 2005 benchmark results
  • From: FX
• Re: Function kind attribute: valid fortran?
  • From: Michael Metcalf
• Re: Polyhedron 2005 benchmark results
  • From: Steve Lionel
• Function kind attribute: valid fortran?
  • From: Bil Kleb
• Re: Need help with fortran file output
  • From: Beliavsky
• Re: variable names for different fortrans
  • From: gary . l . scott
• Re: variable names for different fortrans
  • From: Ron Shepard
• Re: Need help with fortran file output
  • From: Charles Russell
• Re: variable names for different fortrans
  • From: Richard Harter
• Re: AMD Opteron + intel fortran (linux)
  • From: Peter
• Re: variable names for different fortrans
  • From: glen herrmannsfeldt
• Re: Wrong recipient (obviously!) Sorry, folks.
  • From: Kevin G. Rhoads
• Re: Gfortran 2 years behind G95 and still not ready for prime time
  • From: Richard Maine
• Re: Efficient arrays for artificial neural networks?
  • From: Beliavsky
• Re: Append to screen IO
  • From: Richard Maine
• Re: variable names for different fortrans
  • From: allelopath
• Zombie Code -- Re: How old is the average Fortran programmer?
  • From: Kevin G. Rhoads
• Re: Need help with fortran file output
  • From: Michael Prager
• Re: Need help with fortran file output
  • From: Michael Prager
• Re: variable names for different fortrans
  • From: James Parsly
• Re: Code Too Large for MS FORTRAN
  • From: Pierre Asselin
• Re: g77 default array index starts at 0?
  • From: Pierre Asselin
• Re: Gfortran 2 years behind G95 and still not ready for prime time
  • From: glen herrmannsfeldt
• Re: Gfortran 2 years behind G95 and still not ready for prime time
  • From: glen herrmannsfeldt
• Re: AMD Opteron + intel fortran (linux)
  • From: Mark Mackey
• Re: AMD Opteron + intel fortran (linux)
  • From: Mark Mackey
• Re: variable names for different fortrans
  • From: Michael Metcalf
• Re: Gfortran 2 years behind G95 and still not ready for prime time
  • From: awgreynolds
• Re: variable names for different fortrans
  • From: Beliavsky
• Re: Gfortran 2 years behind G95 and still not ready for prime time
  • From: glen herrmannsfeldt
• Re: How old is the average Fortran programmer?
  • From: Kevin G. Rhoads
• Re: Gfortran 2 years behind G95 and still not ready for prime time
  • From: FX
• Re: How old is the average Fortran programmer?
  • From: Arjen Markus
• Re: Gfortran 2 years behind G95 and still not ready for prime time
  • From: awgreynolds
• Re: variable names for different fortrans
  • From: David Flower
• Re: MR&C 7.9
  • From: Michael Metcalf
• Re: Gfortran 2 years behind G95 and still not ready for prime time
  • From: awgreynolds
• Re: Gfortran 2 years behind G95 and still not ready for prime time
  • From: Joost
• Re: Gfortran 2 years behind G95 and still not ready for prime time
  • From: awgreynolds
• Re: Windows gfortran binaries
  • From: FX
• Re: Gfortran 2 years behind G95 and still not ready for prime time
  • From: FX
• Re: Gfortran 2 years behind G95 and still not ready for prime time
  • From: Brooks Moses
• Re: Netcat and Fortran
  • From: glen herrmannsfeldt
• Re: Gfortran 2 years behind G95 and still not ready for prime time
  • From: glen herrmannsfeldt
• Re: Gfortran 2 years behind G95 and still not ready for prime time
  • From: awgreynolds
• Re: How old is the average Fortran programmer?
  • From: Catherine Rees Lay
• Wrong recipient (obviously!) Sorry, folks.
  • From: Catherine Rees Lay
• Re: variable names for different fortrans
  • From: Ben Hetland
• Re: g77 default array index starts at 0?
  • From: glen herrmannsfeldt
• Re: How old is the average Fortran programmer?
  • From: Ben Hetland
• Guess what's sitting on my desk?
  • From: Catherine Rees Lay
• Re: How old is the average Fortran programmer?
  • From: Ben Hetland
• Polyhedron 2005 benchmark results
  • From: FX
• Re: Aren't the fuddy-duddies in the group going to comment on Fortress
  • From: Sebastian Hanigk
• Re: Gfortran 2 years behind G95 and still not ready for prime time
  • From: FX
• Re: Append to screen IO
  • From: Ben Hetland
• Re: Gfortran 2 years behind G95 and still not ready for prime time
  • From: Joost
• Re: Code Too Large for MS FORTRAN
  • From: Brooks Moses
• Re: Code Too Large for MS FORTRAN
  • From: Beliavsky
• Re: Gfortran 2 years behind G95 and still not ready for prime time
  • From: Brooks Moses
• Re: How old is the average Fortran programmer?
  • From: Charles Russell
• Re: design question
  • From: Beliavsky
• Re: How old is the average Fortran programmer?
  • From: Beliavsky
• Re: Gfortran 2 years behind G95 and still not ready for prime time
  • From: Steven G. Kargl
• Re: How old is the average Fortran programmer?
  • From: blmblm
• Re: Need help with fortran file output
  • From: Beliavsky
• Re: How old is the average Fortran programmer?
  • From: Terence
• Re: Need help with fortran file output
  • From: Terence
• Re: design question
  • From: Douglas Wells
• Re: How old is the average Fortran programmer?
  • From: Lane Straatman
• Re: Gfortran 2 years behind G95 and still not ready for prime time
  • From: Richard Maine
• Re: Gfortran 2 years behind G95 and still not ready for prime time
  • From: Steve Lionel
• Re: MR&C 7.9
  • From: Lane Straatman
• Re: How old is the average Fortran programmer?
  • From: blmblm
• Re: MR&C 7.9
  • From: glen herrmannsfeldt
• Re: Gfortran 2 years behind G95 and still not ready for prime time
  • From: glen herrmannsfeldt
• Re: Windows gfortran binaries
  • From: Ken Fairfield
• Need help with fortran file output
  • From: zcai886
• Re: Aren't the fuddy-duddies in the group going to comment on Fortress
  • From: analyst41
• Re: Gfortran 2 years behind G95 and still not ready for prime time
  • From: awgreynolds
• Re: Gfortran 2 years behind G95 and still not ready for prime time
  • From: Richard Maine
• Re: MR&C 7.9
  • From: Richard Maine
• Re: MR&C 7.9
  • From: glen herrmannsfeldt
• Re: Merits of fortran
  • From: Beliavsky
• Re: MR&C 7.9
  • From: glen herrmannsfeldt
• Re: Gfortran 2 years behind G95 and still not ready for prime time
  • From: Brooks Moses
• Re: How old is the average Fortran programmer?
  • From: Lane Straatman
• Re: Windows gfortran binaries
  • From: Brooks Moses
• Re: MR&C 7.9
  • From: Lane Straatman
• Re: Gfortran 2 years behind G95 and still not ready for prime time
  • From: Thomas Koenig
• Re: How old is the average Fortran programmer?
  • From: blmblm
• Re: g77 default array index starts at 0?
  • From: Jan Wagner
• Re: variable names for different fortrans
  • From: glen herrmannsfeldt
• Re: Code Too Large for MS FORTRAN
  • From: max
• Gfortran 2 years behind G95 and still not ready for prime time
  • From: awgreynolds
• Re: MR&C 7.9
  • From: Richard Maine
• Re: Windows gfortran binaries
  • From: Richard Maine
• Re: MR&C 7.9
  • From: Lane Straatman
• Re: variable names for different fortrans
  • From: Ancient_Hacker
• Re: Windows gfortran binaries
  • From: Beliavsky
• Re: Windows gfortran binaries
  • From: Ken Fairfield
• Re: variable names for different fortrans
  • From: Richard Maine
• Re: Inverse of a square matrix
  • From: Greg Lindahl
• Re: variable names for different fortrans
  • From: Richard Maine
• Re: Append to screen IO
  • From: Richard Maine
• Re: Aren't the fuddy-duddies in the group going to comment on Fortress
  • From: Greg Lindahl
• Re: variable names for different fortrans
  • From: Rich Townsend
• Re: How old is the average Fortran programmer?
  • From: Kevin G. Rhoads
• Re: variable names for different fortrans
  • From: Ancient_Hacker
• Re: variable names for different fortrans
  • From: Beliavsky
• Netcat and Fortran
  • From: feenberg
• Re: Inverse of a square matrix
  • From: Beliavsky
• variable names for different fortrans
  • From: allelopath
• Re: Merits of Fortran - followup summary
  • From: Richard Harter
• Inverse of a square matrix
  • From: michael
• Re: design question
  • From: Michael Metcalf
• Re: design question
  • From: Rich Townsend
• Re: Append to screen IO
  • From: Dick Hendrickson
• design question
  • From: Bart Vandewoestyne
• Re: MR&C 7.9
  • From: Dick Hendrickson
• Re: Windows gfortran binaries
  • From: FX
• Re: Windows gfortran binaries
  • From: Beliavsky
• Re: AMD Opteron + intel fortran (linux)
  • From: Tom Micevski
• Re: Debug Symbols missing in Intel Visual Fortran
  • From: Beliavsky
• Windows gfortran binaries
  • From: FX
• Re: Append to screen IO
  • From: Ben Hetland
• Re: How old is the average Fortran programmer?
  • From: Warner BRUNS
• Re: Append to screen IO
  • From: John Deas
• Re: presentations at "Fifty Years of Fortran"
  • From: Lane Straatman
• Re: AMD Opteron + intel fortran (linux)
  • From: Peter
• Debug Symbols missing in Intel Visual Fortran
  • From: R. MacDonald
• Re: Aren't the fuddy-duddies in the group going to comment on Fortress
  • From: Gary Scott
• Re: Aren't the fuddy-duddies in the group going to comment on Fortress
  • From: Rich Townsend
• Re: presentations at "Fifty Years of Fortran"
  • From: Gary Scott
• Re: MR&C 7.9
  • From: Ken Fairfield
• Re: Aren't the fuddy-duddies in the group going to comment on Fortress
  • From: analyst41
• Re: MR&C 7.9
  • From: glen herrmannsfeldt
• Re: MR&C 7.9
  • From: Lane Straatman
• Re: MR&C 7.9
  • From: Lane Straatman
• Re: MR&C 7.9
  • From: Lane Straatman
• Re: How old is the average Fortran programmer?
  • From: Kamaraju S Kusumanchi
• Re: Merits of fortran
  • From: glen herrmannsfeldt
• presentations at "Fifty Years of Fortran"
  • From: Beliavsky
• Re: Merits of Fortran - followup summary
  • From: Richard Harter
• Re: Merits of Fortran - followup summary
  • From: Lane Straatman
• Re: Merits of fortran
  • From: Kevin G. Rhoads
• Re: Benchmarking "transfer"
  • From: Dick Hendrickson
• Merits of Fortran - followup summary
  • From: Richard Harter
• Re: Merits of fortran
  • From: Richard Harter
• Re: Merits of Fortran - followup summary
  • From: Arjen Markus
• Re: How old is the average Fortran programmer?
  • From: Craig Powers
• Re: Benchmarking "transfer"
  • From: Arjen Markus
• Re: Merits of Fortran - followup summary
  • From: Beliavsky
• Re: compilers: Compaq, Lahey, Intel
  • From: Paul van Delst
• Re: Append to screen IO
  • From: Dick Hendrickson
• Re: AMD Opteron + intel fortran (linux)
  • From: Tim Prince
• Re: Code Too Large for MS FORTRAN
  • From: Thomas Koenig
• Re: compilers: Compaq, Lahey, Intel
  • From: Bil Kleb
• Re: How old is the average Fortran programmer?
  • From: Charles Russell
• Re: Append to screen IO
  • From: Ben Hetland
• Re: Append to screen IO
  • From: Dick Hendrickson
• Re: Merits of fortran
  • From: Kevin G. Rhoads
• Re: When will this ng come to accept that Fortran needs to go "back to the future" ?
  • From: Charles Russell
• Re: How old is the average Fortran programmer?
  • From: Kevin G. Rhoads
• Re: When will this ng come to accept that Fortran needs to go "back to the future" ?
  • From: gary . l . scott
• Re: Append to screen IO
  • From: Beliavsky
• Re: Append to screen IO
  • From: gsal
• Re: Append to screen IO
  • From: Beliavsky
• Re: Append to screen IO
  • From: Ugo
• Re: AMD Opteron + intel fortran (linux)
  • From: Tim Prince
• Append to screen IO
  • From: John Deas
• Re: AMD Opteron + intel fortran (linux)
  • From: jmj75
• Re: AMD Opteron + intel fortran (linux)
  • From: Mark Mackey
• Re: AMD Opteron + intel fortran (linux)
  • From: jmj75
• Re: How old is the average Fortran programmer?
  • From: Richard Maine
• Re: TRANSFER on the derived types with allocatable components ( Was Benchmarking "transfer")
  • From: Richard Maine
• Re: When will this ng come to accept that Fortran needs to go "back to the future" ?
  • From: Charles Russell
• Re: How old is the average Fortran programmer?
  • From: Kevin G. Rhoads
• Re: Code Too Large for MS FORTRAN
  • From: Kevin G. Rhoads
• Re: AMD Opteron + intel fortran (linux)
  • From: Helge Avlesen
• Re: Code Too Large for MS FORTRAN
  • From: Kevin G. Rhoads
• Re: Code Too Large for MS FORTRAN
  • From: Kevin G. Rhoads
• TRANSFER on the derived types with allocatable components ( Was Benchmarking "transfer")
  • From: nobat
• Re: AMD Opteron + intel fortran (linux)
  • From: Tim Prince
• Re: AMD Opteron + intel fortran (linux)
  • From: Pierre Asselin
• Re: When will this ng come to accept that Fortran needs to go "back to the future" ?
  • From: Ben Hetland
• Re: compilers: Compaq, Lahey, Intel
  • From: Pierre Asselin
• Re: Code Too Large for MS FORTRAN
  • From: e p chandler
• Re: AMD Opteron + intel fortran (linux)
  • From: Sebastian Hanigk
• Re: Code Too Large for MS FORTRAN
  • From: Terence
• Re: AMD Opteron + intel fortran (linux)
  • From: Sebastian Hanigk
• Re: using somebody else's function
  • From: Jugoslav Dujic
• Re: compilers: Compaq, Lahey, Intel
  • From: Catherine Rees Lay
• Re: How old is the average Fortran programmer?
  • From: Jan Vorbrüggen
• Re: How old is the average Fortran programmer?
  • From: Catherine Rees Lay
• Re: DDD and modules
  • From: John Deas
• Re: AMD Opteron + intel fortran (linux)
  • From: Keith Refson
• Re: AMD Opteron + intel fortran (linux)
  • From: Keith Refson
• Re: AMD Opteron + intel fortran (linux)
  • From: Keith Refson
• Re: How old is the average Fortran programmer?
  • From: Ben Hetland
• Re: Code Too Large for MS FORTRAN
  • From: FX
• Re: using somebody else's function
  • From: Jan Vorbrüggen
• Re: When will this ng come to accept that Fortran needs to go "back to the future" ?
  • From: Greg Lindahl
• Re: When will this ng come to accept that Fortran needs to go "back to the future" ?
  • From: Richard Maine
• Re: When will this ng come to accept that Fortran needs to go "back to the future" ?
  • From: Terence
• Re: using somebody else's function
  • From: Lane Straatman
• Re: Code Too Large for MS FORTRAN
  • From: Terence
• Re: using somebody else's function
  • From: Richard Maine
• Re: using somebody else's function
  • From: Lane Straatman
• Re: Code Too Large for MS FORTRAN
  • From: monir
• Re: compilers: Compaq, Lahey, Intel
  • From: John Harper
• Re: using somebody else's function
  • From: Ken Fairfield
• Re: using somebody else's function
  • From: Lane Straatman
• Re: Code Too Large for MS FORTRAN
  • From: FX
• Re: compilers: Compaq, Lahey, Intel
  • From: Beliavsky
• Re: compilers: Compaq, Lahey, Intel
  • From: Paul van Delst
• Re: How old is the average Fortran programmer?
  • From: pantarei
• Re: compilers: Compaq, Lahey, Intel
  • From: Gary Scott
• Re: increasing width
  • From: Ken Fairfield
• Re: Code Too Large for MS FORTRAN
  • From: e p chandler
• Re: compilers: Compaq, Lahey, Intel
  • From: Dan Nagle
• compilers: Compaq, Lahey, Intel
  • From: allelopath
• Re: Code Too Large for MS FORTRAN
  • From: FX
• Re: How old is the average Fortran programmer?
  • From: Gary Scott
• Re: How old is the average Fortran programmer?
  • From: Ben Hetland
• Re: Code Too Large for MS FORTRAN
  • From: e p chandler
• Re: How old is the average Fortran programmer?
  • From: Greg Lindahl
• Re: Merits of fortran
  • From: Craig Powers
• Re: Question to IBM xlf users
  • From: Richard Maine
• Re: Code Too Large for MS FORTRAN
  • From: Kevin G. Rhoads
• Re: AMD Opteron + intel fortran (linux)
  • From: Kevin G. Rhoads
• Re: Code Too Large for MS FORTRAN
  • From: bandito
• Re: Code Too Large for MS FORTRAN
  • From: Michael Prager
• Re: DDD and modules
  • From: Gary Scott
• Re: DDD and modules
  • From: gsal
• Re: Can allocatable dummies be optional?
  • From: Ron Shepard
• Re: increasing width
  • From: Ron Shepard
• Re: When will this ng come to accept that Fortran needs to go "back to the future" ?
  • From: Janne Blomqvist
• Re: Aren't the fuddy-duddies in the group going to comment on Fortress
  • From: Greg Lindahl
• Re: Using unused variables
  • From: Gordon Sande
• Re: Aren't the fuddy-duddies in the group going to comment on Fortress
  • From: Charles Russell
• Code Too Large for MS FORTRAN
  • From: monir
• Re: Question to IBM xlf users
  • From: Patrick Begou
• Re: How old is the average Fortran programmer?
  • From: Dick Hendrickson
• Re: Benchmarking "transfer"
  • From: Dick Hendrickson
• Re: Using unused variables
  • From: Dick Hendrickson
• Re: MR&C 7.9
  • From: Gary Scott
• Re: How old is the average Fortran programmer?
  • From: Gary Scott
• Re: MR&C 7.9
  • From: Rich Townsend
• Re: How old is the average Fortran programmer?
  • From: Ben Hetland
• Re: How old is the average Fortran programmer?
  • From: Kevin G. Rhoads
• Re: How old is the average Fortran programmer?
  • From: Ben Hetland
• Re: MR&C 7.9
  • From: Kevin G. Rhoads
• Re: Benchmarking "transfer"
  • From: Arjen Markus
• Re: Using unused variables
  • From: Gordon Sande
• Re: increasing width
  • From: Ian Bush
• Re: increasing width
  • From: Paul van Delst
• Re: DDD and modules
  • From: Joost
• Re: DDD and modules
  • From: Herman D . Knoble
• Re: Using unused variables
  • From: Pierre Asselin
• Re: DDD and modules
  • From: John Deas
• Re: using blank common as malloc on Cray Fortran
  • From: Walter Spector
• Re: using somebody else's function
  • From: Michael Metcalf
• Re: DDD and modules
  • From: Les
• DDD and modules
  • From: John Deas
• Re: Merits of fortran
  • From: Sebastian Hanigk
• Re: Question to IBM xlf users
  • From: Ian Bush
• Re: AMD Opteron + intel fortran (linux)
  • From: Sebastian Hanigk
• Re: Can allocatable dummies be optional?
  • From: deltaquattro
• Re: using blank common as malloc on Cray Fortran
  • From: Jan Vorbrüggen
• Re: AMD Opteron + intel fortran (linux)
  • From: Jan Vorbrüggen
• Re: using somebody else's function
  • From: Lane Straatman
• Re: Aren't the fuddy-duddies in the group going to comment on Fortress
  • From: James Giles
• Re: using somebody else's function
  • From: Richard Maine
• Re: Aren't the fuddy-duddies in the group going to comment on Fortress
  • From: Jan Vorbrüggen
• Re: using somebody else's function
  • From: Lane Straatman
• Re: Using unused variables
  • From: glen herrmannsfeldt
• Re: Using unused variables
  • From: Ron Shepard
• Re: Question to IBM xlf users
  • From: insun.song@xxxxxxxxx
• Re: Aren't the fuddy-duddies in the group going to comment on Fortress
  • From: Charles Russell
• Re: using somebody else's function
  • From: Richard Maine
• Re: increasing width
  • From: glen herrmannsfeldt
• Re: increasing width
  • From: Lane Straatman
• Re: using somebody else's function
  • From: Lane Straatman
• Re: Merits of fortran
  • From: Gary Scott
• Re: Merits of fortran
  • From: James Giles
• Re: Merits of fortran
  • From: Gary Scott
• Re: Merits of fortran
  • From: Dan Nagle
• Re: Aren't the fuddy-duddies in the group going to comment on Fortress
  • From: Greg Lindahl
• Re: Aren't the fuddy-duddies in the group going to comment on Fortress
  • From: Greg Lindahl
• Re: Merits of fortran
  • From: James Giles
• Re: MR&C 7.9
  • From: Richard Maine
• Re: reset the video buffer
  • From: Richard Maine
• Re: using somebody else's function
  • From: glen herrmannsfeldt
• Re: using somebody else's function
  • From: Dick Hendrickson
• Re: increasing width
  • From: Ken Fairfield
• Re: MR&C 7.9
  • From: Rich Townsend
• Re: Aren't the fuddy-duddies in the group going to comment on Fortress
  • From: Rich Townsend
• Re: Aren't the fuddy-duddies in the group going to comment on Fortress
  • From: analyst41
• Re: AMD Opteron + intel fortran (linux)
  • From: joehill
• using somebody else's function
  • From: Lane Straatman
• Re: Aren't the fuddy-duddies in the group going to comment on Fortress
  • From: Janne Blomqvist
• Re: Merits of fortran
  • From: Gary Scott
• Re: Merits of fortran
  • From: ejkost
• Re: Any free Fortran 90-95 compilers for Cray Y-MP ?
  • From: Janne Blomqvist
• Re: Merits of fortran
  • From: Alinabi
• Re: Merits of fortran
  • From: Gary Scott
• Re: Merits of fortran
  • From: Gary Scott
• Re: Merits of fortran
  • From: Craig Powers
• Re: increasing width
  • From: Lane Straatman
• Re: increasing width
  • From: glen herrmannsfeldt
• Re: AMD Opteron + intel fortran (linux)
  • From: Greg Lindahl
• Re: MR&C 7.9
  • From: glen herrmannsfeldt
• Re: Merits of fortran
  • From: Greg Lindahl
• Re: MR&C 7.9
  • From: Rich Townsend
• Re: MR&C 7.9
  • From: Lane Straatman
• Re: Merits of fortran
  • From: Gary Scott
• Re: increasing width
  • From: Gordon Sande
• Re: Merits of fortran
  • From: Colin Watters
• Re: increasing width
  • From: Lane Straatman
• Re: increasing width
  • From: glen herrmannsfeldt
• Re: Aren't the fuddy-duddies in the group going to comment on Fortress
  • From: Steven G. Kargl
• Re: Aren't the fuddy-duddies in the group going to comment on Fortress
  • From: Charles Russell
• Re: Merits of fortran
  • From: Alinabi
• Re: Aren't the fuddy-duddies in the group going to comment on Fortress
  • From: Charles Russell
• Re: reset the video buffer
  • From: glen herrmannsfeldt
• Re: AMD Opteron + intel fortran (linux)
  • From: Sebastian Hanigk
• Re: MR&C 7.9
  • From: glen herrmannsfeldt
• Re: Aren't the fuddy-duddies in the group going to comment on Fortress
  • From: Greg Lindahl
• Re: using blank common as malloc on Cray Fortran
  • From: Dan
• Re: Using unused variables
  • From: Gordon Sande
• Re: Merits of fortran
  • From: Beliavsky
• Re: AMD Opteron + intel fortran (linux)
  • From: Steve Lionel
• Re: Using unused variables
  • From: Richard Maine
• Re: MR&C 7.9
  • From: Michael Metcalf
• Re: AMD Opteron + intel fortran (linux)
  • From: Steven G. Kargl
• Re: MR&C 7.9
  • From: Kevin G. Rhoads
• Re: Merits of fortran
  • From: Alinabi
• Re: Merits of fortran
  • From: James Giles
• AMD Opteron + intel fortran (linux)
  • From: jmj75
• Re: increasing width
  • From: Dick Hendrickson
• Re: Using unused variables
  • From: Ron Shepard
• Re: increasing width
  • From: Pierre Asselin
• Re: Aren't the fuddy-duddies in the group going to comment on Fortress
  • From: Steven G. Kargl
• Re: Can allocatable dummies be optional?
  • From: Ron Shepard
• Re: Merits of fortran
  • From: Pierre Asselin
• Re: Aren't the fuddy-duddies in the group going to comment on Fortress
  • From: Gary Scott
• Re: Question to IBM xlf users
  • From: Patrick Begou
• Question to IBM xlf users
  • From: Patrick Begou
• Re: Aren't the fuddy-duddies in the group going to comment on Fortress
  • From: Michael Metcalf
• Re: Using unused variables
  • From: Walter Spector
• Re: Aren't the fuddy-duddies in the group going to comment on Fortress
  • From: Charles Russell
• Re: Using unused variables
  • From: Gary Scott
• Re: Merits of fortran
  • From: Michael Prager
• Re: Using unused variables
  • From: Walter Spector
• Re: Using unused variables
  • From: Gary Scott
• Re: Merits of fortran
  • From: Beliavsky
• Re: multiple precision arithmetic
  • From: Beliavsky
• Re: multiple precision arithmetic
  • From: highegg
• Re: Can allocatable dummies be optional?
  • From: Beliavsky
• Re: multiple precision arithmetic
  • From: Herman D . Knoble
• Re: multiple precision arithmetic
  • From: Herman D . Knoble
• Re: Using unused variables
  • From: Beliavsky
• Re: Using unused variables
  • From: Daniel Franke
• Re: Can allocatable dummies be optional?
  • From: Steve Lionel
• Re: using blank common as malloc on Cray Fortran
  • From: Walter Spector
• Re: Using unused variables
  • From: Gordon Sande
• Re: Merits of fortran
  • From: Gordon Sande
• Benchmarking "transfer"
  • From: nobat
• Re: Using unused variables
  • From: Michael Metcalf
• Re: Using unused variables
  • From: Tom Micevski
• Re: Aren't the fuddy-duddies in the group going to comment on Fortress
  • From: Jan Vorbrüggen
• Re: Aren't the fuddy-duddies in the group going to comment on Fortress
  • From: Michael Metcalf
• Re: When will this ng come to accept that Fortran needs to go "back to the future" ?
  • From: Jan Vorbrüggen
• Re: Object-oriented programing (was Re: How old is the average Fortran programmer?)
  • From: Arjen Markus
• Re: Using unused variables
  • From: Daniel Franke
• Re: Using unused variables
  • From: highegg
• Re: Can allocatable dummies be optional?
  • From: deltaquattro
• Re: Can allocatable dummies be optional?
  • From: deltaquattro
• Using unused variables
  • From: Daniel Franke
• multiple precision arithmetic
  • From: Bart Vandewoestyne
• Re: Merits of fortran
  • From: glen herrmannsfeldt
• Re: Merits of fortran
  • From: James Giles
• Re: Merits of fortran
  • From: Greg Lindahl
• Re: reset the video buffer
  • From: Richard Maine
• Re: reset the video buffer
  • From: Lane Straatman
• Re: reset the video buffer
  • From: Terence
• Re: increasing width
  • From: glen herrmannsfeldt
• Re: MR&C 7.9
  • From: Lane Straatman
• using blank common as malloc on Cray Fortran
  • From: Dan
• Re: MR&C 7.9
  • From: Michael Metcalf
• MR&C 7.9
  • From: Lane Straatman
• Re: Any free Fortran 90-95 compilers for Cray Y-MP ?
  • From: Dan
• Re: MR&C 7.9
  • From: Rich Townsend
• Re: increasing width
  • From: Lane Straatman
• Re: adding and displaying harmonic series
  • From: John Harper
• Re: Merits of fortran
  • From: David Flower
• Re: increasing width
  • From: Gordon Sande
• Re: Aren't the fuddy-duddies in the group going to comment on Fortress
  • From: Richard Maine
• Re: increasing width
  • From: Dick Hendrickson
• Re: reset the video buffer
  • From: Gordon Sande
• Re: reset the video buffer
  • From: heavytull
• F2k3 Translation - UML 2 Test Profile Example
  • From: Gary Scott
• Re: Aren't the fuddy-duddies in the group going to comment on Fortress
  • From: Dan Nagle
• Re: Aren't the fuddy-duddies in the group going to comment on Fortress
  • From: Charles Russell
• Any free Fortran 90-95 compilers for Cray Y-MP ?
  • From: Ancient_Hacker
• Re: Merits of fortran
  • From: David Rowell
• Re: Aren't the fuddy-duddies in the group going to comment on Fortress
  • From: Sebastian Hanigk
• Re: Aren't the fuddy-duddies in the group going to comment on Fortress
  • From: Richard Maine
• Re: Merits of fortran
  • From: Dan Nagle
• Re: Aren't the fuddy-duddies in the group going to comment on Fortress
  • From: Lane Straatman
• Re: adding and displaying harmonic series
  • From: Dan Nagle
• Re: Merits of fortran
  • From: James Giles
• Re: Aren't the fuddy-duddies in the group going to comment on Fortress
  • From: Rich Townsend
• Re: adding and displaying harmonic series
  • From: Lane Straatman
• Re: adding and displaying harmonic series
  • From: James Giles
• Re: increasing width
  • From: Tom Micevski
• Re: increasing width
  • From: Brooks Moses
• Re: increasing width
  • From: Lane Straatman
• Re: adding and displaying harmonic series
  • From: robin
• Re: adding and displaying harmonic series
  • From: robin
• Re: adding and displaying harmonic series
  • From: robin
• Re: Merits of fortran
  • From: Brooks Moses
• Re: increasing width
  • From: Lane Straatman
• Re: Merits of fortran
  • From: glen herrmannsfeldt
• Re: increasing width
  • From: Steve Lionel
• Re: increasing width
  • From: Lane Straatman
• Re: increasing width
  • From: Lane Straatman
• Re: Aren't the fuddy-duddies in the group going to comment on Fortress
  • From: Sebastian Hanigk
• Re: increasing width
  • From: Michael Metcalf
• Re: increasing width
  • From: Dick Hendrickson
• Re: increasing width
  • From: Steve Lionel
• Re: increasing width
  • From: gsal
• Re: Merits of fortran
  • From: Sebastian Hanigk
• Re: Object-oriented programing (was Re: How old is the average Fortran programmer?)
  • From: Charles Russell
• increasing width
  • From: Lane Straatman
• Re: Merits of fortran
  • From: Richard Harter
• Re: reset the video buffer
  • From: Richard Maine
• reset the video buffer
  • From: heavytull
• Re: More object-oriented programming, was Re: ... comment on Fortress
  • From: Richard Maine
• Re: Aren't the fuddy-duddies in the group going to comment on Fortress
  • From: Richard Maine
• More object-oriented programming, was Re: ... comment on Fortress
  • From: Brooks Moses
• Re: Aren't the fuddy-duddies in the group going to comment on Fortress
  • From: Greg Lindahl
• Re: Aren't the fuddy-duddies in the group going to comment on Fortress
  • From: Gary Scott
• Re: Aren't the fuddy-duddies in the group going to comment on Fortress
  • From: Richard Maine
• Re: Merits of fortran
  • From: Gib Bogle
• Re: Object-oriented programing
  • From: Richard Maine
• Re: Aren't the fuddy-duddies in the group going to comment on Fortress
  • From: Gordon Sande
• Re: Aren't the fuddy-duddies in the group going to comment on Fortress
  • From: Sebastian Hanigk
• Re: Object-oriented programing (was Re: How old is the average Fortran programmer?)
  • From: Ron Shepard
• Re: Aren't the fuddy-duddies in the group going to comment on Fortress
  • From: analyst41
• Re: Getting literal newline \n in output after porting code
  • From: Ron Shepard
• Re: Merits of fortran
  • From: Richard Harter
• Re: Getting literal newline \n in output after porting code
  • From: Richard Maine
• Re: Merits of fortran
  • From: Louis Krupp
• Re: Aren't the fuddy-duddies in the group going to comment on Fortress
  • From: Beliavsky
• Re: Merits of fortran
  • From: Charles Russell
• Re: Object-oriented programing (was Re: How old is the average Fortran programmer?)
  • From: Charles Russell
• Re: Merits of fortran
  • From: Beliavsky
• Re: Object-oriented programing (was Re: How old is the average Fortran programmer?)
  • From: Ron Shepard
• Re: Aren't the fuddy-duddies in the group going to comment on Fortress
  • From: max
• Re: Merits of fortran
  • From: max
• Merits of fortran
  • From: Richard Harter
• Re: Help! Fortran90 errata corrige
  • From: Edward N Bromhead
• Re: Object-oriented programing (was Re: How old is the average Fortran programmer?)
  • From: Thomas Koenig
• Aren't the fuddy-duddies in the group going to comment on Fortress
  • From: analyst41
• Re: Object-oriented programing (was Re: How old is the average Fortran programmer?)
  • From: Arjen Markus
• Re: Object-oriented programing (was Re: How old is the average Fortran programmer?)
  • From: Arjen Markus
• Re: Object-oriented programing (was Re: How old is the average Fortran programmer?)
  • From: Arjen Markus
• Re: Getting literal newline \n in output after porting code
  • From: Dan Nagle
• Re: Getting literal newline \n in output after porting code
  • From: glen herrmannsfeldt
• Re: Getting literal newline \n in output after porting code
  • From: robert . corbett
• Re: Getting literal newline \n in output after porting code
  • From: robert . corbett
• Re: g77 default array index starts at 0?
  • From: Brooks Moses
• Re: g77 default array index starts at 0?
  • From: Bart Vandewoestyne
• Re: Can allocatable dummies be optional?
  • From: deltaquattro
• Re: Sun Studio 12 early access compilers go live
  • From: robert . corbett
• Re: maxloc question
  • From: Rich Townsend
• Re: optional argument of elemental function
  • From: Beliavsky
• Re: IVF quirks, or standard?
  • From: Steve Lionel
• Re: When will this ng come to accept that Fortran needs to go "back to the future" ?
  • From: Greg Lindahl
• Re: When will this ng come to accept that Fortran needs to go "back to the future" ?
  • From: Greg Lindahl
• Re: dynamically growable vector?
  • From: Rich Townsend
• Re: optional argument of elemental function
  • From: Rich Townsend
• Re: optional argument of elemental function
  • From: glen herrmannsfeldt
• Re: g77 default array index starts at 0?
  • From: Richard Maine
• Re: Getting literal newline \n in output after porting code
  • From: Dan Nagle
• optional argument of elemental function
  • From: Beliavsky
• Re: dynamically growable vector?
  • From: glen herrmannsfeldt
• Re: g77 default array index starts at 0?
  • From: glen herrmannsfeldt
• Re: IVF quirks, or standard?
  • From: Beliavsky
• Re: g77 default array index starts at 0?
  • From: Beliavsky
• Re: Getting literal newline \n in output after porting code
  • From: Richard Maine
• Re: Getting literal newline \n in output after porting code
  • From: Brooks Moses
• Re: g77 default array index starts at 0?
  • From: Richard Maine
• Re: IVF quirks, or standard?
  • From: Brooks Moses
• Re: IVF quirks, or standard?
  • From: Richard Maine
• Re: g77 default array index starts at 0?
  • From: Ancient_Hacker
• Re: Getting literal newline \n in output after porting code
  • From: glen herrmannsfeldt
• Re: generic deallocate possible?
  • From: Richard Maine
• IVF quirks, or standard?
  • From: Ancient_Hacker
• generic deallocate possible?
  • From: Ancient_Hacker
• Re: maxloc question
  • From: Richard Maine
• Re: Getting literal newline \n in output after porting code
  • From: Brooks Moses
• Re: adding and displaying harmonic series
  • From: Lane Straatman
• Re: Getting literal newline \n in output after porting code
  • From: glen herrmannsfeldt
• Re: maxloc question
  • From: glen herrmannsfeldt
• Re: maxloc question
  • From: glen herrmannsfeldt
• Re: Getting literal newline \n in output after porting code
  • From: Richard Maine
• Re: Getting literal newline \n in output after porting code
  • From: glen herrmannsfeldt
• Re: Can allocatable dummies be optional?
  • From: Dick Hendrickson
• Re: How old is the average Fortran programmer?
  • From: glen herrmannsfeldt
• Re: Getting literal newline \n in output after porting code
  • From: glen herrmannsfeldt
• Re: Help! Fortran90 errata corrige
  • From: Richard Maine
• Re: Can allocatable dummies be optional?
  • From: FX
• Re: Can allocatable dummies be optional?
  • From: deltaquattro
• Re: Getting literal newline \n in output after porting code
  • From: Richard Maine
• Re: Can allocatable dummies be optional?
  • From: Richard Maine
• Re: Object-oriented programing (was Re: How old is the average Fortran programmer?)
  • From: Ron Shepard
• Can allocatable dummies be optional?
  • From: deltaquattro
• Re: How old is the average Fortran programmer?
  • From: Kevin G. Rhoads
• warn about unused PRIVATE entities
  • From: Beliavsky
• Re: How old is the average Fortran programmer?
  • From: Kevin G. Rhoads
• Re: Getting literal newline \n in output after porting code
  • From: Steve Lionel
• Re: How old is the average Fortran programmer?
  • From: mach
• Re: maxloc question
  • From: Bart Vandewoestyne
• Re: Sun Studio 12 early access compilers go live
  • From: Beliavsky
• Re: How old is the average Fortran programmer?
  • From: Gary Scott
• Re: Object-oriented programing (was Re: How old is the average Fortran programmer?)
  • From: Beliavsky
• Re: Object-oriented programing (was Re: How old is the average Fortran programmer?)
  • From: Jan Vorbrüggen
• Re: Object-oriented programing (was Re: How old is the average Fortran programmer?)
  • From: Bil Kleb
• Re: Getting literal newline \n in output after porting code
  • From: AeroSpace Ed
• Re: Object-oriented programing (was Re: How old is the average Fortran programmer?)
  • From: Arjen Markus
• Re: ANSI way to zero last few bits of doubles?
  • From: Herman D . Knoble
• Re: Getting literal newline \n in output after porting code
  • From: Dan Nagle
• Re: use of user defined types in Fortran 90 modules
  • From: Michael Metcalf
• Re: maxloc question
  • From: Rich Townsend
• Re: Sun Studio 12 early access compilers go live
  • From: robert . corbett
• Re: Getting literal newline \n in output after porting code
  • From: glen herrmannsfeldt
• Re: maxloc question
  • From: glen herrmannsfeldt
• Re: How old is the average Fortran programmer?
  • From: PJH
• Re: maxloc question
  • From: Arjen Markus
• Re: F-compiler installation
  • From: Arjen Markus
• Re: Sun Studio 12 early access compilers go live
  • From: Daniel Franke
• Re: Help! Fortran90 errata corrige
  • From: Brooks Moses
• Re: Sun Studio 12 early access compilers go live
  • From: robert . corbett
• Help! Fortran90 errata corrige
  • From: Luca Andrea Sconosciuto
• maxloc question
  • From: Bart Vandewoestyne
• Re: Sun Studio 12 early access compilers go live
  • From: Daniel Franke
• Help. Fortran 90
  • From: Luca Andrea Sconosciuto
• Re: F-compiler installation
  • From: Bart Vandewoestyne
• Sun Studio 12 early access compilers go live
  • From: robert . corbett
• Re: F-compiler installation
  • From: Arjen Markus
• Re: adding and displaying harmonic series
  • From: Lane Straatman
• Re: ANSI way to zero last few bits of doubles?
  • From: Jan Vorbrüggen
• Re: ANSI way to zero last few bits of doubles?
  • From: Jan Vorbrüggen
• Re: Getting literal newline \n in output after porting code
  • From: robert . corbett
• Re: Getting literal newline \n in output after porting code
  • From: baf
• Getting literal newline \n in output after porting code
  • From: misteromaha
• Re: use of user defined types in Fortran 90 modules
  • From: Richard Maine
• Re: How old is the average Fortran programmer?
  • From: Ken Fairfield
• Re: adding and displaying harmonic series
  • From: glen herrmannsfeldt
• Re: adding and displaying harmonic series
  • From: Lane Straatman
• Re: use of user defined types in Fortran 90 modules
  • From: dancerchris
• Re: use of user defined types in Fortran 90 modules
  • From: Michael Metcalf
• Re: ANSI way to zero last few bits of doubles?
  • From: ttw
• Re: How old is the average Fortran programmer?
  • From: dancerchris
• use of user defined types in Fortran 90 modules
  • From: dancerchris
• Re: debugging segmentation faults (gfortran)
  • From: rawlins02
• Re: How old is the average Fortran programmer?
  • From: Lane Straatman
• Re: ANSI way to zero last few bits of doubles?
  • From: glen herrmannsfeldt
• Re: ANSI way to zero last few bits of doubles?
  • From: Richard Maine
• Re: When will this ng come to accept that Fortran needs to go "back to the future" ?
  • From: robin
• Re: adding and displaying harmonic series
  • From: John Harper
• Re: ANSI way to zero last few bits of doubles?
  • From: ttw
• Re: Extreme Newbie Help
  • From: Dan Nagle
• Re: How old is the average Fortran programmer?
  • From: gary . l . scott
• Re: Extreme Newbie Help
  • From: Steven G. Kargl
• Re: Extreme Newbie Help
  • From: Richard Maine
• Re: Extreme Newbie Help
  • From: Beliavsky
• Re: Extreme Newbie Help
  • From: hmiller@xxxxxxxxxxxx
• Re: ANSI way to zero last few bits of doubles?
  • From: Steven G. Kargl
• Re: Extreme Newbie Help
  • From: Dan Nagle
• Re: Object-oriented programing (was Re: How old is the average Fortran programmer?)
  • From: Paul van Delst
• Extreme Newbie Help
  • From: hmiller@xxxxxxxxxxxx
• Re: ANSI way to zero last few bits of doubles?
  • From: glen herrmannsfeldt
• Re: ANSI way to zero last few bits of doubles?
  • From: glen herrmannsfeldt
• Re: ANSI way to zero last few bits of doubles?
  • From: Richard Maine
• Re: debugging segmentation faults (gfortran)
  • From: Kamaraju S Kusumanchi
• Re: Object-oriented programing (was Re: How old is the average Fortran programmer?)
  • From: Bart Vandewoestyne
• Re: debugging segmentation faults (gfortran)
  • From: Steven G. Kargl
• Re: ANSI way to zero last few bits of doubles?
  • From: FTN_90_Programmer
• absoft fortran-mrwe application
  • From: heavytull
• Re: ANSI way to zero last few bits of doubles?
  • From: highegg
• Re: How old is the average Fortran programmer?
  • From: PJH
• debugging segmentation faults (gfortran)
  • From: rawlins02
• Re: How old is the average Fortran programmer?
  • From: James Giles
• Re: ANSI way to zero last few bits of doubles?
  • From: Richard Maine
• Re: ANSI way to zero last few bits of doubles?
  • From: highegg
• Re: Object-oriented programing
  • From: Richard Maine
• Re: ANSI way to zero last few bits of doubles?
  • From: Richard Maine
• Re: ANSI way to zero last few bits of doubles?
  • From: Paul van Delst
• Re: F-compiler installation
  • From: Bart Vandewoestyne
• Re: ANSI way to zero last few bits of doubles?
  • From: Michael Prager
• Re: ANSI way to zero last few bits of doubles?
  • From: Herman D . Knoble
• Re: Object-oriented programing (was Re: How old is the average Fortran programmer?)
  • From: Rich Townsend
• Re: ANSI way to zero last few bits of doubles?
  • From: Dan Nagle
• Re: Calling a dll c function returning a pointer
  • From: רוזנברג אוהד ועידית
• Re: ANSI way to zero last few bits of doubles?
  • From: Sebastian Hanigk
• Re: Object-oriented programing (was Re: How old is the average Fortran programmer?)
  • From: Michael Metcalf
• Re: ANSI way to zero last few bits of doubles?
  • From: Herman D . Knoble
• Re: Object-oriented programing (was Re: How old is the average Fortran programmer?)
  • From: Jan Vorbrüggen
• Re: Cray-pointer-based array initialisation
  • From: Sebastian Hanigk
• Re: ANSI way to zero last few bits of doubles?
  • From: Michael Metcalf
• Re: ANSI way to zero last few bits of doubles?
  • From: Sebastian Hanigk
• Re: ANSI way to zero last few bits of doubles?
  • From: Herman D . Knoble
• Re: ANSI way to zero last few bits of doubles?
  • From: Tim Prince
• ANSI way to zero last few bits of doubles?
  • From: FTN_90_Programmer
• Re: How old is the average Fortran programmer?
  • From: Craig Powers
• Re: Object-oriented programing (was Re: How old is the average Fortran programmer?)
  • From: Arjen Markus
• Object-oriented programing (was Re: How old is the average Fortran programmer?)
  • From: Beliavsky
• Re: Problem using procedures and functions in modules
  • From: Tom Micevski
• Re: F-compiler installation
  • From: Arjen Markus
• Re: How old is the average Fortran programmer?
  • From: Gary Scott
• Re: How old is the average Fortran programmer?
  • From: Daniel Franke
• Re: When will this ng come to accept that Fortran needs to go "back to the future" ?
  • From: Jan Vorbrüggen
• Re: How old is the average Fortran programmer?
  • From: Jan Vorbrüggen
• Re: How old is the average Fortran programmer?
  • From: Helmut Michels
• Re: How old is the average Fortran programmer?
  • From: Jan Vorbrüggen
• Re: adding and displaying harmonic series
  • From: Lane Straatman
• Re: When will this ng come to accept that Fortran needs to go "back to the future" ?
  • From: Walter Spector
• Re: When will this ng come to accept that Fortran needs to go "back to the future" ?
  • From: Steven G. Kargl
• Re: adding and displaying harmonic series
  • From: Richard Maine
• Re: adding and displaying harmonic series
  • From: Lane Straatman
• Re: How old is the average Fortran programmer?
  • From: Gary Scott
• Re: How old is the average Fortran programmer?
  • From: Lane Straatman
• Re: When will this ng come to accept that Fortran needs to go "back to the future" ?
  • From: Greg Lindahl
• Re: How old is the average Fortran programmer?
  • From: Greg Lindahl
• Re: When will this ng come to accept that Fortran needs to go "back to the future" ?
  • From: Greg Lindahl
• Re: When will this ng come to accept that Fortran needs to go "back to the future" ?
  • From: pantarei
• Re: How old is the average Fortran programmer?
  • From: pantarei
• Re: fortran equivalent of matlab num2str
  • From: Beliavsky
• Re: When will this ng come to accept that Fortran needs to go "back to the future" ?
  • From: robin
• Re: fortran equivalent of matlab num2str
  • From: Lane Straatman
• Re: When will this ng come to accept that Fortran needs to go "back to the future" ?
  • From: glen herrmannsfeldt
• Re: How old is the average Fortran programmer?
  • From: James Giles
• Re: fortran equivalent of matlab num2str
  • From: andy2O
• Re: fortran equivalent of matlab num2str
  • From: andy2O
• Re: When will this ng come to accept that Fortran needs to go "back to the future" ?
  • From: Richard Maine
• Re: fortran equivalent of matlab num2str
  • From: Beliavsky
• Re: fortran equivalent of matlab num2str
  • From: Brooks Moses
• Re: When will this ng come to accept that Fortran needs to go "back to the future" ?
  • From: Richard Maine
• Re: How old is the average Fortran programmer?
  • From: Richard Maine
• Re: How old is the average Fortran programmer?
  • From: Thomas Koenig
• Re: How old is the average Fortran programmer?
  • From: Anton Haumer
• Re: fortran equivalent of matlab num2str
  • From: Bart Vandewoestyne
• Re: How old is the average Fortran programmer?
  • From: glen herrmannsfeldt
• fortran equivalent of matlab num2str
  • From: louisJ
• Re: How old is the average Fortran programmer?
  • From: James Giles
• Re: How old is the average Fortran programmer?
  • From: James Giles
• Re: How old is the average Fortran programmer?
  • From: James Giles
• Re: Parameter usage in interface blocks
  • From: Pierre Asselin
• Re: How old is the average Fortran programmer?
  • From: J.Verburgt
• Re: How old is the average Fortran programmer?
  • From: Brooks Moses
• Re: When will this ng come to accept that Fortran needs to go "back to the future" ?
  • From: Pierre Asselin
• Re: When will this ng come to accept that Fortran needs to go "back to the future" ?
  • From: Pierre Asselin
• Re: How old is the average Fortran programmer?
  • From: Pierre Asselin
• Re: Cray-pointer-based array initialisation
  • From: Pierre Asselin
• Re: When will this ng come to accept that Fortran needs to go "back to the future" ?
  • From: Steven G. Kargl
• Re: When will this ng come to accept that Fortran needs to go "back to the future" ?
  • From: Pierre Asselin
• Re: How old is the average Fortran programmer?
  • From: Kevin G. Rhoads
• Re: How old is the average Fortran programmer?
  • From: Dan Nagle
• Re: When will this ng come to accept that Fortran needs to go "back to the future" ?
  • From: Rich Townsend
• Re: How old is the average Fortran programmer?
  • From: MrAsm
• Re: How old is the average Fortran programmer?
  • From: jon
• Re: How old is the average Fortran programmer?
  • From: Michael Metcalf
• Re: How old is the average Fortran programmer?
  • From: Steven G. Kargl
• Re: When will this ng come to accept that Fortran needs to go "back to the future" ?
  • From: Jan Vorbrüggen
• Re: How old is the average Fortran programmer?
  • From: Beliavsky
• Re: How old is the average Fortran programmer?
  • From: Michael Metcalf
• Re: need help making function elemental
  • From: Dick Hendrickson
• Re: When will this ng come to accept that Fortran needs to go "back to the future" ?
  • From: Charles Russell
• Re: How old is the average Fortran programmer?
  • From: MrAsm
• Re: When will this ng come to accept that Fortran needs to go "back to the future" ?
  • From: Dan Nagle
• Re: converting a R code to fortran
  • From: fortee
• Re: When will this ng come to accept that Fortran needs to go "back to the future" ?
  • From: Jan Vorbrüggen
• Re: How old is the average Fortran programmer?
  • From: highegg
• Re: How old is the average Fortran programmer?
  • From: Jan Vorbrüggen
• Re: When will this ng come to accept that Fortran needs to go "back to the future" ?
  • From: Jan Vorbrüggen
• Re: When will this ng come to accept that Fortran needs to go "back to the future" ?
  • From: Charles Russell
• Re: How old is the average Fortran programmer?
  • From: highegg
• Re: How old is the average Fortran programmer?
  • From: Les
• Re: When will this ng come to accept that Fortran needs to go "back to the future" ?
  • From: Charles Russell
• Re: How old is the average Fortran programmer?
  • From: MrAsm
• Re: Parameter usage in interface blocks
  • From: Steve Lionel
• Re: How old is the average Fortran programmer?
  • From: highegg
• Re: When will this ng come to accept that Fortran needs to go "back to the future" ?
  • From: Pierre Asselin
• Re: When will this ng come to accept that Fortran needs to go "back to the future" ?
  • From: Walter Spector
• Re: How old is the average Fortran programmer?
  • From: Dan Nagle
• F-compiler installation
  • From: Bart Vandewoestyne
• Re: Parameter usage in interface blocks
  • From: Tobias Burnus
• Re: Division of large negative number leads to integer overflow
  • From: robin
• Re: How old is the average Fortran programmer?
  • From: MrAsm
• Re: How old is the average Fortran programmer?
  • From: MrAsm
• Re: When will this ng come to accept that Fortran needs to go "back to the future" ?
  • From: Pierre Asselin
• Re: Parameter usage in interface blocks
  • From: Sebastian Hanigk
• Re: Parameter usage in interface blocks
  • From: highegg
• Re: Parameter usage in interface blocks
  • From: Jan Vorbrüggen
• Re: How old is the average Fortran programmer?
  • From: PJH
• Parameter usage in interface blocks
  • From: Sebastian Hanigk
• Re: How old is the average Fortran programmer?
  • From: gary . l . scott
• Re: How old is the average Fortran programmer?
  • From: highegg
• Re: When will this ng come to accept that Fortran needs to go "back to the future" ?
  • From: analyst41
• Re: Division of large negative number leads to integer overflow
  • From: ttw
• Re: How old is the average Fortran programmer?
  • From: highegg
• Re: When will this ng come to accept that Fortran needs to go "back to the future" ?
  • From: Jan Vorbrüggen
• Re: When will this ng come to accept that Fortran needs to go "back to the future" ?
  • From: Jan Vorbrüggen
• Re: Calling a dll c function returning a pointer
  • From: Jugoslav Dujic
• Re: Division of large negative number leads to integer overflow
  • From: Thomas Koenig
• Re: How old is the average Fortran programmer?
  • From: Brooks Moses
• Re: How old is the average Fortran programmer?
  • From: Brooks Moses
• Re: How old is the average Fortran programmer?
  • From: PJH
• Re: How old is the average Fortran programmer?
  • From: Jon Harrop
• Re: How old is the average Fortran programmer?
  • From: aeroguy
• Re: How old is the average Fortran programmer?
  • From: PJH
• Re: g77 default array index starts at 0?
  • From: glen herrmannsfeldt
• Re: Calling a dll c function returning a pointer
  • From: glen herrmannsfeldt
• Re: How old is the average Fortran programmer?
  • From: MrAsm
• Re: How old is the average Fortran programmer?
  • From: glen herrmannsfeldt
• Re: How old is the average Fortran programmer?
  • From: MrAsm
• Re: Calling a dll c function returning a pointer
  • From: Jugoslav Dujic
• Re: When will this ng come to accept that Fortran needs to go "back to the future" ?
  • From: Jan Vorbrüggen
• Re: When will this ng come to accept that Fortran needs to go "back to the future" ?
  • From: Jan Vorbrüggen
• Re: When will this ng come to accept that Fortran needs to go "back to the future" ?
  • From: Jan Vorbrüggen
• Re: Cray-pointer-based array initialisation
  • From: Sebastian Hanigk
• Calling a dll c function returning a pointer
  • From: רוזנברג אוהד ועידית
• Re: When will this ng come to accept that Fortran needs to go "back to the future" ?
  • From: Richard Maine
• Re: When will this ng come to accept that Fortran needs to go "back to the future" ?
  • From: Charles Russell
• Re: converting a R code to fortran
  • From: e p chandler
• Re: When will this ng come to accept that Fortran needs to go "back to the future" ?
  • From: analyst41
• Re: adding and displaying harmonic series
  • From: Lane Straatman
• Re: adding and displaying harmonic series
  • From: James Giles
• adding and displaying harmonic series
  • From: Lane Straatman
• Re: Digital/Compaq/HP Visual Fortran on Windows 2000/XP
  • From: subspace
• Re: When will this ng come to accept that Fortran needs to go "back to the future" ?
  • From: Terence
• Re: How old is the average Fortran programmer?
  • From: Craig Powers
• Re: How old is the average Fortran programmer?
  • From: Craig Powers
• Re: Division of large negative number leads to integer overflow
  • From: robin
• Re: need help making function elemental
  • From: robin
• Re: Division of large negative number leads to integer overflow
  • From: robin
• Re: How old is the average Fortran programmer?
  • From: Craig Powers
• Re: How old is the average Fortran programmer?
  • From: subspace
• Re: How old is the average Fortran programmer?
  • From: gary . l . scott
• Re: How old is the average Fortran programmer?
  • From: gary . l . scott
• Re: How old is the average Fortran programmer?
  • From: gary . l . scott
• Re: How old is the average Fortran programmer?
  • From: gary . l . scott
• Re: How old is the average Fortran programmer?
  • From: gary . l . scott
• Re: Cray-pointer-based array initialisation
  • From: John Harper
• Re: How old is the average Fortran programmer?
  • From: gary . l . scott
• Re: When will this ng come to accept that Fortran needs to go "back to the future" ?
  • From: Richard Maine
• Re: How old is the average Fortran programmer?
  • From: Lane Straatman
• Re: When will this ng come to accept that Fortran needs to go "back to the future" ?
  • From: analyst41
• Re: Cray-pointer-based array initialisation
  • From: gary . l . scott
• Re: Cray-pointer-based array initialisation
  • From: Richard Maine
• Re: Cray-pointer-based array initialisation
  • From: Sebastian Hanigk
• Re: Cray-pointer-based array initialisation
  • From: Richard Maine
• Re: Cray-pointer-based array initialisation
  • From: Sebastian Hanigk
• Re: Cray-pointer-based array initialisation
  • From: robert . corbett
• Re: How old is the average Fortran programmer?
  • From: joaquin . casanova
• Re: Cray-pointer-based array initialisation
  • From: John Harper
• Re: How old is the average Fortran programmer?
  • From: jim . lahman
• Re: How old is the average Fortran programmer?
  • From: PJH
• Re: How old is the average Fortran programmer?
  • From: Lane Straatman
• Re: How old is the average Fortran programmer?
  • From: Charles Russell
• Re: Cray-pointer-based array initialisation
  • From: Richard Maine
• Re: Cray-pointer-based array initialisation
  • From: Sebastian Hanigk
• Re: How old is the average Fortran programmer?
  • From: PJH
• Re: When will this ng come to accept that Fortran needs to go "back to the future" ?
  • From: ttw
• Re: When will this ng come to accept that Fortran needs to go "back to the future" ?
  • From: glen herrmannsfeldt
• Re: When will this ng come to accept that Fortran needs to go "back to the future" ?
  • From: glen herrmannsfeldt
• Re: When will this ng come to accept that Fortran needs to go "back to the future" ?
  • From: Thomas Koenig
• Re: Cray-pointer-based array initialisation
  • From: Richard Maine
• Re: When will this ng come to accept that Fortran needs to go "back to the future" ?
  • From: Steven G. Kargl
• Re: When will this ng come to accept that Fortran needs to go "back to the future" ?
  • From: John Harper
• Re: When will this ng come to accept that Fortran needs to go "back to the future" ?
  • From: Paul van Delst
• Re: When will this ng come to accept that Fortran needs to go "back to the future" ?
  • From: Steven G. Kargl
• Re: When will this ng come to accept that Fortran needs to go "back to the future" ?
  • From: Craig Powers
• Re: OMP Parallel for MS Visual Studio with Intel Fortran
  • From: mattsdad
• Cray-pointer-based array initialisation
  • From: Sebastian Hanigk
• Re: When will this ng come to accept that Fortran needs to go "back to the future" ?
  • From: Richard Maine
• Re: OMP Parallel for MS Visual Studio with Intel Fortran
  • From: Beliavsky
• Re: When will this ng come to accept that Fortran needs to go "back to the future" ?
  • From: glen herrmannsfeldt
• Re: How old is the average Fortran programmer?
  • From: Richard Maine
• OMP Parallel for MS Visual Studio with Intel Fortran
  • From: mattsdad
• Re: How old is the average Fortran programmer?
  • From: Craig Powers
• Re: When will this ng come to accept that Fortran needs to go "back to the future" ?
  • From: Paul van Delst
• Re: Pentiium 4 Math Functions
  • From: glen herrmannsfeldt
• Re: How old is the average Fortran programmer?
  • From: Charles Russell
• Re: When will this ng come to accept that Fortran needs to go "back to the future" ?
  • From: Craig Powers
• Re: How old is the average Fortran programmer?
  • From: Richard Maine
• Re: Problem using procedures and functions in modules
  • From: Richard Maine
• g77 default array index starts at 0?
  • From: Jan Wagner
• Re: How old is the average Fortran programmer?
  • From: Charles Russell
• Re: How old is the average Fortran programmer?
  • From: Michel Oui
• Re: How old is the average Fortran programmer?
  • From: Charles Russell
• Re: OT - 4 stager -- Launch Picture
  • From: e p chandler
• Re: How old is the average Fortran programmer?
  • From: David Rowell
• Re: When will this ng come to accept that Fortran needs to go "back to the future" ?
  • From: Bil Kleb
• Re: When will this ng come to accept that Fortran needs to go "back to the future" ?
  • From: Jan Vorbrüggen
• Re: DATE_AND_TIME
  • From: Jan Vorbrüggen
• Re: DATE_AND_TIME
  • From: Bart Vandewoestyne
• Re: When will this ng come to accept that Fortran needs to go "back to the future" ?
  • From: analyst41
• Re: How old is the average Fortran programmer?
  • From: Dr Ivan D. Reid
• Re: When will this ng come to accept that Fortran needs to go "back to the future" ?
  • From: Bil Kleb
• Re: How old is the average Fortran programmer?
  • From: Bil Kleb
• Re: How old is the average Fortran programmer?
  • From: Harold Stevens
• Re: Optional arguments in nested subroutines
  • From: alexei . matveev
• Re: Problem using procedures and functions in modules
  • From: deltaquattro
• Re: DATE_AND_TIME
  • From: James Giles
• DATE_AND_TIME
  • From: Bart Vandewoestyne
• Re: When will this ng come to accept that Fortran needs to go "back to the future" ?
  • From: James Giles
• Re: How old is the average Fortran programmer?
  • From: Greg Lindahl
• Re: How old is the average Fortran programmer?
  • From: Jan Vorbrüggen
• Re: How old is the average Fortran programmer?
  • From: Jan Vorbrüggen
• Re: How old is the average Fortran programmer?
  • From: Jugoslav Dujic
• Re: Digital/Compaq/HP Visual Fortran on Windows 2000/XP
  • From: Jan Vorbrüggen
• Re: When will this ng come to accept that Fortran needs to go "back to the future" ?
  • From: Jan Vorbrüggen
• Re: When will this ng come to accept that Fortran needs to go "back to the future" ?
  • From: Jan Vorbrüggen
• Re: How old is the average Fortran programmer?
  • From: Gib Bogle
• Re: When will this ng come to accept that Fortran needs to go "back to the future" ?
  • From: Jan Vorbrüggen
• Re: How old is the average Fortran programmer?
  • From: Bart Vandewoestyne
• Re: When will this ng come to accept that Fortran needs to go "back to the future" ?
  • From: Jan Vorbrüggen
• Re: When will this ng come to accept that Fortran needs to go "back to the future" ?
  • From: Jan Vorbrüggen
• Re: How old is the average Fortran programmer?
  • From: Steven G. Kargl
• Re: How old is the average Fortran programmer?
  • From: Terence
• Re: How old is the average Fortran programmer?
  • From: Norman S. Clerman
• Re: When will this ng come to accept that Fortran needs to go "back to the future" ?
  • From: analyst41
• Re: How old is the average Fortran programmer?
  • From: Paul van Delst
• Re: How old is the average Fortran programmer?
  • From: Lane Straatman
• Re: How old is the average Fortran programmer?
  • From: Paul van Delst
• Re: How old is the average Fortran programmer?
  • From: gary . l . scott
• Re: How old is the average Fortran programmer?
  • From: Greg Lindahl
• Re: How old is the average Fortran programmer?
  • From: Colin Watters
• Re: How old is the average Fortran programmer?
  • From: ttw
• Re: When will this ng come to accept that Fortran needs to go "back to the future" ?
  • From: Thomas Koenig
• Re: How old is the average Fortran programmer?
  • From: cup
• Re: Digital/Compaq/HP Visual Fortran on Windows 2000/XP
  • From: max
• Re: Problem using procedures and functions in modules
  • From: Gordon Sande
• Re: How old is the average Fortran programmer?
  • From: Richard Maine
• OT - 4 stager -- Launch Picture
  • From: Kevin G. Rhoads
• Re: How old is the average Fortran programmer?
  • From: Kevin G. Rhoads
• Re: Digital/Compaq/HP Visual Fortran on Windows 2000/XP
  • From: Kevin G. Rhoads
• Re: Problem using procedures and functions in modules
  • From: John Harper
• RE: How old is the average Fortran programmer?
  • From: meek
• Re: Problem using procedures and functions in modules
  • From: Paul van Delst
• Re: How old is the average Fortran programmer?
  • From: kris
• Re: How old is the average Fortran programmer?
  • From: Bart Vandewoestyne
• Re: When will this ng come to accept that Fortran needs to go "back to the future" ?
  • From: James Giles
• Re: Problem using procedures and functions in modules
  • From: glen herrmannsfeldt
• Re: When will this ng come to accept that Fortran needs to go "back to the future" ?
  • From: glen herrmannsfeldt
• Re: When will this ng come to accept that Fortran needs to go "back to the future" ?
  • From: Richard Edgar
• Re: Problem using procedures and functions in modules
  • From: James Giles
• Re: When will this ng come to accept that Fortran needs to go "back to the future" ?
  • From: Rich Townsend
• Re: When will this ng come to accept that Fortran needs to go "back to the future" ?
  • From: Rich Townsend
• Re: When will this ng come to accept that Fortran needs to go "back to the future" ?
  • From: glen herrmannsfeldt
• Re: Problem using procedures and functions in modules
  • From: glen herrmannsfeldt
• Re: How old is the average Fortran programmer?
  • From: Charles Russell
• Re: How old is the average Fortran programmer?
  • From: Les
• Re: Problem using procedures and functions in modules
  • From: Les
• Re: When will this ng come to accept that Fortran needs to go "back to the future" ?
  • From: Richard Maine
• Re: When will this ng come to accept that Fortran needs to go "back to the future" ?
  • From: Richard Maine
• Re: How old is the average Fortran programmer?
  • From: w5ygr
• Re: When will this ng come to accept that Fortran needs to go "back to the future" ?
  • From: Jan Vorbrüggen
• Re: Problem using procedures and functions in modules
  • From: Richard Maine
• Re: How old is the average Fortran programmer?
  • From: Jan Vorbrüggen
• Re: Optional arguments in nested subroutines
  • From: Richard Maine
• Re: 2D Graph Programme with ASCII Input
  • From: Michael Prager
• Re: How old is the average Fortran programmer?
  • From: AeroSpace Ed
• Re: How old is the average Fortran programmer?
  • From: James Parsly
• Re: Controlling excel from fortran
  • From: Herman D . Knoble
• Re: How old is the average Fortran programmer?
  • From: Beliavsky
• Re: When will this ng come to accept that Fortran needs to go "back to the future" ?
  • From: Pierre Asselin
• Re: Problem using procedures and functions in modules
  • From: deltaquattro
• Re: How old is the average Fortran programmer?
  • From: Norman S. Clerman
• Re: Optional arguments in nested subroutines
  • From: Michael Metcalf
• Re: How old is the average Fortran programmer?
  • From: Ian Bush
• Re: How old is the average Fortran programmer?
  • From: Zuczek
• Re: How old is the average Fortran programmer?
  • From: Dan Nagle
• Re: Problem using procedures and functions in modules
  • From: jwm
• Re: Problem using procedures and functions in modules
  • From: Reinhold Bader
• Problem using procedures and functions in modules
  • From: deltaquattro
• Re: How old is the average Fortran programmer?
  • From: Les
• Re: How old is the average Fortran programmer?
  • From: alexei . matveev
• Re: Optional arguments in nested subroutines
  • From: alexei . matveev
• Re: How old is the average Fortran programmer?
  • From: Klaus Wacker
• Re: How old is the average Fortran programmer?
  • From: Arjen Markus
• Re: How old is the average Fortran programmer?
  • From: Ian Bush
• Re: When will this ng come to accept that Fortran needs to go "back to the future" ?
  • From: David Flower
• Re: How old is the average Fortran programmer?
  • From: SimonG
• Re: How old is the average Fortran programmer?
  • From: David Flower
• Re: When will this ng come to accept that Fortran needs to go "back to the future" ?
  • From: Terence
• Re: Digital/Compaq/HP Visual Fortran on Windows 2000/XP
  • From: Terence
• Re: Digital/Compaq/HP Visual Fortran on Windows 2000/XP
  • From: Kelvin Hales
• Re: How old is the average Fortran programmer?
  • From: highegg
• Re: How old is the average Fortran programmer?
  • From: Gib Bogle
• Re: Digital/Compaq/HP Visual Fortran on Windows 2000/XP
  • From: Tim Prince
• Re: How old is the average Fortran programmer?
  • From: Steven G. Kargl
• Re: When will this ng come to accept that Fortran needs to go "back to the future" ?
  • From: Walter Spector
• Re: Division of large negative number leads to integer overflow
  • From: J. F. Cornwall
• Re: How old is the average Fortran programmer?
  • From: Lynn
• Re: When will this ng come to accept that Fortran needs to go "back to the future" ?
  • From: Walter Spector
• Re: Digital/Compaq/HP Visual Fortran on Windows 2000/XP
  • From: jwm
• Re: How old is the average Fortran programmer?
  • From: Lane Straatman
• Re: need help making function elemental
  • From: Beliavsky
• Re: Digital/Compaq/HP Visual Fortran on Windows 2000/XP
  • From: Beliavsky
• Re: When will this ng come to accept that Fortran needs to go "back to the future" ?
  • From: glen herrmannsfeldt
• Re: When will this ng come to accept that Fortran needs to go "back to the future" ?
  • From: pantarei
• Re: When will this ng come to accept that Fortran needs to go "back to the future" ?
  • From: pantarei
• Re: How old is the average Fortran programmer?
  • From: Bob Stryk
• Re: When will this ng come to accept that Fortran needs to go "back to the future" ?
  • From: Rich Townsend
• Re: How old is the average Fortran programmer?
  • From: John Harper
• Re: How old is the average Fortran programmer?
  • From: Greg Lindahl
• Re: How old is the average Fortran programmer?
  • From: Pierre Asselin
• Re: When will this ng come to accept that Fortran needs to go "back to the future" ?
  • From: Pierre Asselin
• Re: 2D Graph Programme with ASCII Input
  • From: Pierre Asselin
• Re: How old is the average Fortran programmer?
  • From: Gary Scott
• Re: How old is the average Fortran programmer?
  • From: Pierre Asselin
• Re: When will this ng come to accept that Fortran needs to go "back to the future" ?
  • From: James Giles
• openMP reduction with arrays
  • From: Nico
• Re: ISO C Binding: Pointer to a pointer of pointers: ***argv
  • From: Richard Maine
• Re: When will this ng come to accept that Fortran needs to go "back to the future" ?
  • From: analyst41
• Re: How old is the average Fortran programmer?
  • From: Charles Russell
• Re: When will this ng come to accept that Fortran needs to go "back to the future" ?
  • From: Rich Townsend
• Re: How old is the average Fortran programmer?
  • From: FX
• Re: When will this ng come to accept that Fortran needs to go "back to the future" ?
  • From: Gary Scott
• Re: When will this ng come to accept that Fortran needs to go "back to the future" ?
  • From: analyst41
• Re: How old is the average Fortran programmer?
  • From: e p chandler
• Re: When will this ng come to accept that Fortran needs to go "back to the future" ?
  • From: Gary Scott
• Re: When will this ng come to accept that Fortran needs to go "back to the future" ?
  • From: Rich Townsend
• Re: How old is the average Fortran programmer?
  • From: Beliavsky
• Re: How old is the average Fortran programmer?
  • From: PJH
• Re: When will this ng come to accept that Fortran needs to go "back to the future" ?
  • From: analyst41
• Re: Where can I find the information such as....
  • From: Beliavsky
• Re: When will this ng come to accept that Fortran needs to go "back to the future" ?
  • From: Carlie J. Coats
• Re: When will this ng come to accept that Fortran needs to go "back to the future" ?
  • From: David Frank
• Re: When will this ng come to accept that Fortran needs to go "back to the future" ?
  • From: glen herrmannsfeldt
• Re: ISO C Binding: Pointer to a pointer of pointers: ***argv
  • From: glen herrmannsfeldt
• Re: How old is the average Fortran programmer?
  • From: Harold Stevens
• Re: How old is the average Fortran programmer?
  • From: Joost
• Re: How old is the average Fortran programmer?
  • From: Brooks Moses
• Re: How old is the average Fortran programmer?
  • From: Brooks Moses
• Re: When will this ng come to accept that Fortran needs to go "back to the future" ?
  • From: Thomas Koenig
• Where can I find the information such as....
  • From: Liang-Chun Liu
• Where can I find the information such as....
  • From: Liang-Chun Liu
• Re: When will this ng come to accept that Fortran needs to go "back to the future" ?
  • From: Terence
• Re: How old is the average Fortran programmer?
  • From: Terence
• Re: How old is the average Fortran programmer?
  • From: Dave Weatherall
• Re: How old is the average Fortran programmer?
  • From: Richard Steiner
• Re: How old is the average Fortran programmer?
  • From: baf
• Re: How old is the average Fortran programmer?
  • From: glen herrmannsfeldt
• Re: When will this ng come to accept that Fortran needs to go "back to the future" ?
  • From: Walter Spector
• Re: When will this ng come to accept that Fortran needs to go "back to the future" ?
  • From: Walter Spector
• Re: converting a R code to fortran
  • From: e p chandler
• Re: How old is the average Fortran programmer?
  • From: Gib Bogle
• Re: When will this ng come to accept that Fortran needs to go "back to the future" ?
  • From: analyst41
• Re: How old is the average Fortran programmer?
  • From: Lane Straatman
• Re: How old is the average Fortran programmer?
  • From: Gary Scott
• Re: How old is the average Fortran programmer?
  • From: Lane Straatman
• Re: When will this ng come to accept that Fortran needs to go "back to the future" ?
  • From: Gary Scott
• Re: When will this ng come to accept that Fortran needs to go "back to the future" ?
  • From: pantarei
• Re: When will this ng come to accept that Fortran needs to go "back to the future" ?
  • From: pantarei
• Re: How old is the average Fortran programmer?
  • From: pantarei
• Re: When will this ng come to accept that Fortran needs to go "back to the future" ?
  • From: Richard Maine
• Re: How old is the average Fortran programmer?
  • From: Richard Maine
• Re: When will this ng come to accept that Fortran needs to go "back to the future" ?
  • From: ejko123
• Re: How old is the average Fortran programmer?
  • From: Bart Vandewoestyne
• Re: Division of large negative number leads to integer overflow
  • From: glen herrmannsfeldt
• Re: When will this ng come to accept that Fortran needs to go "back to the future" ?
  • From: analyst41
• Re: 2D Graph Programme with ASCII Input
  • From: Beliavsky
• Re: Division of large negative number leads to integer overflow
  • From: Louis Krupp
• Re: converting a R code to fortran
  • From: e p chandler
• Re: When will this ng come to accept that Fortran needs to go "back to the future" ?
  • From: Gary Scott
• Re: When will this ng come to accept that Fortran needs to go "back to the future" ?
  • From: Richard Maine
• Re: ISO C Binding: Pointer to a pointer of pointers: ***argv
  • From: Richard Maine
• Re: How old is the average Fortran programmer?
  • From: Carlie J. Coats
• Re: When will this ng come to accept that Fortran needs to go "back to the future" ?
  • From: Carlie J. Coats
• Re: How old is the average Fortran programmer?
  • From: hoblit
• Re: re-allocating an allocatable
  • From: glen herrmannsfeldt
• Re: ISO C Binding: Pointer to a pointer of pointers: ***argv
  • From: glen herrmannsfeldt
• Re: How old is the average Fortran programmer?
  • From: Steven G. Kargl
• Re: When will this ng come to accept that Fortran needs to go "back to the future" ?
  • From: Richard Maine
• Re: When will this ng come to accept that Fortran needs to go "back to the future" ?
  • From: Richard Maine
• Re: When will this ng come to accept that Fortran needs to go "back to the future" ?
  • From: Gary Scott
• Re: How old is the average Fortran programmer?
  • From: Ian Gay
• Re: When will this ng come to accept that Fortran needs to go "back to the future" ?
  • From: Gary Scott
• Re: How old is the average Fortran programmer?
  • From: Fred Webb
• Re: ISO C Binding: Pointer to a pointer of pointers: ***argv
  • From: glen herrmannsfeldt
• Re: How old is the average Fortran programmer?
  • From: Gary Scott
• 2D Graph Programme with ASCII Input
  • From: Matt
• Re: How old is the average Fortran programmer?
  • From: rusi_pathan
• Re: When will this ng come to accept that Fortran needs to go "back to the future" ?
  • From: Richard Maine
• Re: ISO C Binding: Pointer to a pointer of pointers: ***argv
  • From: Richard Maine
• Re: How old is the average Fortran programmer?
  • From: Richard Maine
• Re: When will this ng come to accept that Fortran needs to go "back to the future" ?
  • From: Walter Spector
• Re: How old is the average Fortran programmer?
  • From: Dick Hendrickson
• Re: How old is the average Fortran programmer?
  • From: highegg
• Re: When will this ng come to accept that Fortran needs to go "back to the future" ?
  • From: Rich Townsend
• Re: When will this ng come to accept that Fortran needs to go "back to the future" ?
  • From: e p chandler
• Re: How old is the average Fortran programmer?
  • From: Jon Harrop
• When will this ng come to accept that Fortran needs to go "back to the future" ?
  • From: analyst41
• Re: How old is the average Fortran programmer?
  • From: Rich Townsend
• Re: How old is the average Fortran programmer?
  • From: J. F. Cornwall
• Re: ISO C Binding: Pointer to a pointer of pointers: ***argv
  • From: Tobias Burnus
• Re: How old is the average Fortran programmer?
  • From: Sebastian Hanigk
• Re: ISO C Binding: Pointer to a pointer of pointers: ***argv
  • From: glen herrmannsfeldt
• Re: How old is the average Fortran programmer?
  • From: Anton Haumer
• Re: How old is the average Fortran programmer?
  • From: Richard Hoffpauir
• Re: ISO C Binding: Pointer to a pointer of pointers: ***argv
  • From: Tobias Burnus
• How old is the average Fortran programmer?
  • From: Bart Vandewoestyne
• Re: re-allocating an allocatable
  • From: Bart Vandewoestyne
• Re: ISO C Binding: Pointer to a pointer of pointers: ***argv
  • From: robert . corbett
• Re: fortran 2003 compiler
  • From: Steven G. Kargl
• Re: fortran 2003 compiler
  • From: Steven G. Kargl
• Re: fortran 2003 compiler
  • From: highegg
• Re: Controlling excel from fortran
  • From: William Asher
• Re: re-allocating an allocatable
  • From: Beliavsky
• Re: re-allocating an allocatable
  • From: Richard Maine
• Re: re-allocating an allocatable
  • From: highegg
• Re: fortran 2003 compiler
  • From: highegg
• re-allocating an allocatable
  • From: Bart Vandewoestyne
• Re: ISO C Binding: Pointer to a pointer of pointers: ***argv
  • From: Lane Straatman
• Re: ISO C Binding: Pointer to a pointer of pointers: ***argv
  • From: Tobias Burnus
• Re: fortran 2003 compiler
  • From: Lane Straatman
• Re: need help making function elemental
  • From: Bart Vandewoestyne
• Re: Array size by module variables
  • From: Thomas Koenig
• Re: Division of large negative number leads to integer overflow
  • From: Thomas Koenig
• Re: Division of large negative number leads to integer overflow
  • From: Richard Maine
• Re: Controlling excel from fortran
  • From: Beliavsky
• Re: Controlling excel from fortran
  • From: Craig Powers
• Re: fortran 2003 compiler
  • From: nobat
• Controlling excel from fortran
  • From: tuli
• Re: ISO C Binding: Pointer to a pointer of pointers: ***argv
  • From: glen herrmannsfeldt
• Re: fortran 2003 compiler
  • From: Steven G. Kargl
• Re: Array intrinsics with zero-size array argument
  • From: Dick Hendrickson
• Re: fortran 2003 compiler
  • From: Beliavsky
• Re: Division of large negative number leads to integer overflow
  • From: glen herrmannsfeldt
• Re: fortran 2003 compiler
  • From: Steven G. Kargl
• Re: Array intrinsics with zero-size array argument
  • From: Michael Metcalf
• Re: line input
  • From: Tobias Burnus
• Re: line input
  • From: Tobias Burnus
• Re: Array intrinsics with zero-size array argument
  • From: Michael Metcalf
• line input
  • From: tuli
• Re: Array intrinsics with zero-size array argument
  • From: Tobias Burnus
• Re: Array intrinsics with zero-size array argument
  • From: Beliavsky
• ISO C Binding: Pointer to a pointer of pointers: ***argv
  • From: Tobias Burnus
• Array intrinsics with zero-size array argument
  • From: awgreynolds
• Re: need help making function elemental
  • From: Richard Maine
• Re: Division of large negative number leads to integer overflow
  • From: Richard Maine
• need help making function elemental
  • From: Bart Vandewoestyne
• Re: Array size by module variables
  • From: Steve Lionel
• Re: fortran 2003 compiler
  • From: Dan Nagle
• Re: Array size by module variables
  • From: Beliavsky
• Re: fortran 2003 compiler
  • From: Gordon Sande
• Re: Intel Support
  • From: Steve Lionel
• Re: Array size by module variables
  • From: James Giles
• Re: fortran 2003 compiler
  • From: Beliavsky
• Re: fortran 2003 compiler
  • From: Tobias Burnus
• Re: Array size by module variables
  • From: Dan Nagle
• Re: Array size by module variables
  • From: Michael Metcalf
• Re: Array size by module variables
  • From: robert . corbett
• Re: F2003: C interop binding labels
  • From: Reinhold Bader
• Re: Division of large negative number leads to integer overflow
  • From: robert . corbett
• Re: Division of large negative number leads to integer overflow
  • From: Arjen Markus
• Re: Division of large negative number leads to integer overflow
  • From: glen herrmannsfeldt
• Re: Division of large negative number leads to integer overflow
  • From: Richard Maine
• Re: Division of large negative number leads to integer overflow
  • From: Richard Maine
• Division of large negative number leads to integer overflow
  • From: Arjen Markus
• Re: Array size by module variables
  • From: Johan
• Re: converting a R code to fortran
  • From: e p chandler
• Re: fortran 2003 compiler
  • From: Richard Maine
• Re: fortran 2003 compiler
  • From: Lane Straatman
• Re: Intel Support
  • From: Pierre Asselin
• Re: About generating random numbers under Unix using Fortran90
  • From: Lane Straatman
• Re: IBM XL Fortran bug
  • From: Gib Bogle
• Re: F2003: C interop binding labels
  • From: Richard Maine
• F2003: C interop binding labels
  • From: Reinhold Bader
• Re: Array size by module variables
  • From: Steve Lionel
• Re: Absoft Fortran Problem
  • From: gsal
• Re: Array size by module variables
  • From: Rich Townsend
• Re: Array size by module variables
  • From: Rich Townsend
• Re: Array size by module variables
  • From: Richard Maine
• Re: Array size by module variables
  • From: Dick Hendrickson
• Array size by module variables
  • From: Johan
• Re: converting a R code to fortran
  • From: fortee
• Re: ifort 64 vs 32-bit addressing compiler flag
  • From: Mike Casey
• Re: converting a R code to fortran
  • From: Michel Olagnon
• Re: Absoft Fortran Problem
  • From: gsal
• Re: Absoft Fortran Problem
  • From: hardy
• Re: ifort 64 vs 32-bit addressing compiler flag
  • From: Reinhold Bader
• ifort 64 vs 32-bit addressing compiler flag
  • From: Mike Casey
• Re: converting a R code to fortran
  • From: fortee
• Re: IBM XL Fortran
  • From: Ron Shepard
• Re: End of record marker - 32 vs. 64 bit
  • From: Richard Maine
• Re: Absoft Fortran Problem
  • From: Richard Maine
• Re: Absoft Fortran Problem
  • From: gsal
• Re: Intel Support
  • From: Dieter Britz
• Re: Absoft Fortran Problem
  • From: Dave Seaman
• Re: optional argument versus subroutine overloading
  • From: Arjen Markus
• Re: End of record marker - 32 vs. 64 bit
  • From: Chris Theis
• Re: End of record marker - 32 vs. 64 bit
  • From: Chris Theis
• Re: Intel Support
  • From: Dieter Britz
• Re: Absoft Fortran Problem
  • From: Tim Prince
• Absoft Fortran Problem
  • From: hardy
• Absoft Fotran Problem
  • From: hardy
• Re: IBM XL Fortran
  • From: Dave Seaman
• Re: Array Constructors
  • From: robert . corbett
• Re: IBM XL Fortran
  • From: Richard Maine
• Re: Array Constructors
  • From: John Harper
• Re: Pentiium 4 Math Functions
  • From: Tim Prince
• Re: Pentiium 4 Math Functions
  • From: Steve Lionel
• Re: Matlab -> Fortran
  • From: Gib Bogle
• Re: IBM XL Fortran
  • From: Gib Bogle
• Re: IBM XL Fortran
  • From: Gib Bogle
• Re: Pentiium 4 Math Functions
  • From: Edward N Bromhead
• Re: Array Constructors
  • From: robert . corbett
• Re: End of record marker - 32 vs. 64 bit
  • From: glen herrmannsfeldt
• Re: IBM XL Fortran
  • From: Paul van Delst
• Re: IBM XL Fortran
  • From: awgreynolds