comp.lang.fortran

• Thread Index

---

• Re: CDC Floating point = tests?
  • From: Paul van Delst
• Re: Question about out-of-bounds warning
  • From: Craig Powers
• Re: Huge program, no interfaces, ugh
  • From: Clive Page
• Re: Memory usage f95...
  • From: tripp
• Re: Declaration to get 8-bit (or 16-bit) integer?
  • From: Clive Page
• Re: Question about out-of-bounds warning
  • From: FX
• Re: Question about out-of-bounds warning
  • From: Sebastian Hanigk
• Question about out-of-bounds warning
  • From: Thomas Koenig
• Re: CVF and Vista
  • From: Paul van Delst
• Re: What is going on with Lahey?
  • From: awgreynolds
• Re: CVF and Vista
  • From: Kevin G. Rhoads
• Re: Huge program, no interfaces, ugh
  • From: Greg Lindahl
• Re: nested loop is not working...im new
  • From: Tunjang
• Re: nested loop is not working...im new
  • From: Tunjang
• Re: What is going on with Lahey?
  • From: Herman D . Knoble
• Re: nested loop is not working...im new
  • From: e p chandler
• Re: Huge program, no interfaces, ugh
  • From: Steve Lionel
• Re: What is going on with Lahey?
  • From: awgreynolds
• Re: CDC Floating point = tests?
  • From: stocksami@xxxxxxxxxxxxx
• Re: Huge program, no interfaces, ugh
  • From: Gordon Sande
• Re: Huge program, no interfaces, ugh
  • From: Dan Nagle
• Re: CVF and Vista
  • From: Jim
• Re: Huge program, no interfaces, ugh
  • From: Beliavsky
• Re: problem with library function
  • From: Beliavsky
• Huge program, no interfaces, ugh
  • From: Ancient_Hacker
• Re: CVF and Vista
  • From: Steve Lionel
• Re: CVF and Vista
  • From: Paul van Delst
• Re: problem with library function
  • From: nakisa
• Re: problem with library function
  • From: Beliavsky
• origin of a certain exercise
  • From: Bart Vandewoestyne
• problem with library function
  • From: nakisa
• Re: CVF and Vista
  • From: Steve Lionel
• Re: nested loop is not working...im new
  • From: Tunjang
• Re: F77 -> F95 Intro Presentation Material
  • From: Bil Kleb
• Re: CVF and Vista
  • From: Richard Maine
• Re: Declaration to get 8-bit (or 16-bit) integer?
  • From: Paul van Delst
• Re: What is going on with Lahey?
  • From: Herman D . Knoble
• Re: What is going on with Lahey?
  • From: Beliavsky
• Re: What is going on with Lahey?
  • From: awgreynolds
• Re: CVF and Vista
  • From: Michael Metcalf
• Re: F77 -> F95 Intro Presentation Material
  • From: Michael Metcalf
• Re: F77 -> F95 Intro Presentation Material
  • From: Bil Kleb
• Re: F77 -> F95 Intro Presentation Material
  • From: Bil Kleb
• Re: F77 -> F95 Intro Presentation Material
  • From: Bil Kleb
• Re: F77 -> F95 Intro Presentation Material
  • From: Bil Kleb
• Re: checking if a floating point number is equal in value to an integer
  • From: analyst41
• Re: Vista and reading/writing files
  • From: Jugoslav Dujic
• Re: F77 -> F95 Intro Presentation Material
  • From: Richard Maine
• Re: CDC Floating point = tests?
  • From: Richard Maine
• Re: CVF and Vista
  • From: Gary Scott
• Re: Declaration to get 8-bit (or 16-bit) integer?
  • From: Gary Scott
• Re: CVF and Vista
  • From: sureal
• Re: F77 -> F95 Intro Presentation Material
  • From: Bil Kleb
• Re: Declaration to get 8-bit (or 16-bit) integer?
  • From: Clive Page
• Re: Declaration to get 8-bit (or 16-bit) integer?
  • From: Paul van Delst
• Re: F77 -> F95 Intro Presentation Material
  • From: Clive Page
• Re: Declaration to get 8-bit (or 16-bit) integer?
  • From: Clive Page
• Re: F77 -> F95 Intro Presentation Material
  • From: John Harper
• Re: Vista and reading/writing files
  • From: dpb
• Vista and reading/writing files
  • From: James Parsly
• Re: F77 -> F95 Intro Presentation Material
  • From: Reinhold Bader
• Re: F77 -> F95 Intro Presentation Material
  • From: Michael Metcalf
• Re: CDC Floating point = tests?
  • From: glen herrmannsfeldt
• Re: F77 -> F95 Intro Presentation Material
  • From: Beliavsky
• Re: CDC Floating point = tests?
  • From: Herman D . Knoble
• Re: CDC Floating point = tests?
  • From: Gordon Sande
• F77 -> F95 Intro Presentation Material
  • From: Bil Kleb
• CDC Floating point = tests?
  • From: stocksami@xxxxxxxxxxxxx
• Re: What is going on with Lahey?
  • From: Beliavsky
• Re: What is going on with Lahey?
  • From: Herman D . Knoble
• Re: What is going on with Lahey?
  • From: dpb
• Re: CVF and Vista
  • From: Steve Lionel
• Re: Declaration to get 8-bit (or 16-bit) integer?
  • From: Gordon Sande
• CVF and Vista
  • From: Michael Metcalf
• Re: nested loop is not working...im new
  • From: e p chandler
• Re: What is going on with Lahey?
  • From: nobat
• Re: Handling large datasets in Fortran
  • From: L . Spadavecchia
• Re: checking if a floating point number is equal in value to an integer
  • From: glen herrmannsfeldt
• Re: Declaration to get 8-bit (or 16-bit) integer?
  • From: Dan Nagle
• Re: checking if a floating point number is equal in value to an integer
  • From: Ugo
• Re: Handling large datasets in Fortran
  • From: Jan Vorbrüggen
• Re: nested loop is not working.....
  • From: Tunjang
• Re: nested loop is not working...im new
  • From: Tunjang
• Re: Problem to use NAG libraries in C++
  • From: robert . corbett
• Re: Declaration to get 8-bit (or 16-bit) integer?
  • From: glen herrmannsfeldt
• Re: Declaration to get 8-bit (or 16-bit) integer?
  • From: robert . corbett
• Re: Is this code computationally economical?
  • From: Tim Prince
• Re: Declaration to get 8-bit (or 16-bit) integer?
  • From: Richard Maine
• Re: checking if a floating point number is equal in value to an integer
  • From: glen herrmannsfeldt
• Re: Declaration to get 8-bit (or 16-bit) integer?
  • From: glen herrmannsfeldt
• Re: checking if a floating point number is equal in value to an integer
  • From: Tim Prince
• Re: checking if a floating point number is equal in value to an integer
  • From: ejko123
• Re: checking if a floating point number is equal in value to an integer
  • From: ejko123
• checking if a floating point number is equal in value to an integer
  • From: analyst41
• Re: What is going on with Lahey?
  • From: John Fredrickson
• Re: 'java for fortran'
  • From: Gib Bogle
• Re: Is this code computationally economical?
  • From: Gib Bogle
• Re: Is this code computationally economical?
  • From: glen herrmannsfeldt
• Re: Declaration to get 8-bit (or 16-bit) integer?
  • From: Richard E Maine
• Re: Declaration to get 8-bit (or 16-bit) integer?
  • From: Terence
• Re: () in output lists
  • From: Phillip Helbig---remove CLOTHES to reply
• Re: Is this code computationally economical?
  • From: Thomas Koenig
• Re: Is this code computationally economical?
  • From: Greg Lindahl
• Re: Is this code computationally economical?
  • From: Greg Lindahl
• Re: Declaration to get 8-bit (or 16-bit) integer?
  • From: glen herrmannsfeldt
• Re: Is this code computationally economical?
  • From: andy2O
• Re: Is this code computationally economical?
  • From: glen herrmannsfeldt
• Re: Declaration to get 8-bit (or 16-bit) integer?
  • From: Richard E Maine
• Re: Handling large datasets in Fortran
  • From: glen herrmannsfeldt
• Re: string concatenation
  • From: glen herrmannsfeldt
• Re: Declaration to get 8-bit (or 16-bit) integer?
  • From: ejko123
• What is going on with Lahey?
  • From: nobat
• Re: string concatenation
  • From: Richard E Maine
• Re: Handling large datasets in Fortran
  • From: Richard E Maine
• Re: Is this code computationally economical?
  • From: Tim Prince
• Re: Is this code computationally economical?
  • From: Beliavsky
• Re: Problem to use NAG libraries in C++
  • From: SimonG
• Re: Handling large datasets in Fortran
  • From: Mark Morss
• Re: Declaration to get 8-bit (or 16-bit) integer?
  • From: Jan Vorbrüggen
• Re: Declaration to get 8-bit (or 16-bit) integer?
  • From: Joost
• Problem to use NAG libraries in C++
  • From: Diaboflo
• Re: Declaration to get 8-bit (or 16-bit) integer?
  • From: Arjen Markus
• Declaration to get 8-bit (or 16-bit) integer?
  • From: Clive Page
• Re: string concatenation
  • From: robert . corbett
• Re: Is this code computationally economical?
  • From: andy2O
• Re: () in output lists
  • From: Ian Bush
• Re: Is this code computationally economical?
  • From: Louis Krupp
• Re: nested loop is not working.....
  • From: Jan Vorbrüggen
• Re: nested loop is not working.....
  • From: glen herrmannsfeldt
• Re: string concatenation
  • From: glen herrmannsfeldt
• Re: Is this code computationally economical?
  • From: glen herrmannsfeldt
• Re: Is this code computationally economical?
  • From: highegg
• Re: string concatenation
  • From: robert . corbett
• Re: string concatenation
  • From: Richard Maine
• Re: string concatenation
  • From: robert . corbett
• Re: string concatenation
  • From: John Harper
• Re: () in output lists
  • From: Gary Scott
• Re: nested loop is not working...im new
  • From: e p chandler
• Re: string concatenation
  • From: James Giles
• Re: nested loop is not working.....
  • From: e p chandler
• Re: Is this code computationally economical?
  • From: glen herrmannsfeldt
• Re: string concatenation
  • From: glen herrmannsfeldt
• Re: () in output lists
  • From: John Harper
• Re: () in output lists
  • From: Rich Townsend
• Re: () in output lists
  • From: Richard Maine
• Re: nested loop is not working...im new
  • From: Jim
• Re: () in output lists
  • From: Phillip Helbig---remove CLOTHES to reply
• Re: Locate sources for Lawrence Livermore Nat'l Labs old OCTOPUS library routines
  • From: John Fredrickson
• Re: nested loop is not working.....
  • From: John Harper
• Re: string concatenation
  • From: John Harper
• Re: A file managment question
  • From: analyst41
• Re: nested loop is not working.....
  • From: e p chandler
• Re: OO Definitions
  • From: PJH
• nested loop is not working...im new
  • From: Tunjang
• Re: OO Definitions
  • From: glen herrmannsfeldt
• Re: OO Definitions
  • From: PJH
• Re: Pointer-based arrays output strange
  • From: Sebastian Hanigk
• nested loop is not working.....
  • From: Tunjang
• Re: Pointer-based arrays output strange
  • From: Thomas Koenig
• Re: Pointer-based arrays output strange
  • From: Sebastian Hanigk
• Re: Pointer-based arrays output strange
  • From: Sebastian Hanigk
• Locate sources for Lawrence Livermore Nat'l Labs old OCTOPUS library routines
  • From: Paul
• Re: Pointer-based arrays output strange
  • From: Richard Maine
• Re: Pointer-based arrays output strange
  • From: Richard Maine
• Re: Is this code computationally economical?
  • From: Dick Hendrickson
• Re: A file managment question
  • From: Gary Scott
• Re: pointer and allocatable array problem
  • From: Michael Metcalf
• Re: Is this code computationally economical?
  • From: Thomas Koenig
• Re: () in output lists
  • From: J. F. Cornwall
• Re: Is this code computationally economical?
  • From: Walter Spector
• Re: A file managment question
  • From: Walter Spector
• Re: Is this code computationally economical?
  • From: Walter Spector
• Re: Is this code computationally economical?
  • From: Arjen Markus
• Re: A file managment question
  • From: mail-to . signature
• Re: A file managment question
  • From: John Appleyard
• Re: Pointer-based arrays output strange
  • From: Sebastian Hanigk
• Re: Pointer-based arrays output strange
  • From: Joost
• Re: Is this code computationally economical?
  • From: glen herrmannsfeldt
• Re: string concatenation
  • From: glen herrmannsfeldt
• Is this code computationally economical?
  • From: qquito
• Re: A file managment question
  • From: Beliavsky
• Re: A file managment question
  • From: Beliavsky
• Re: A file managment question
  • From: Beliavsky
• Re: A file managment question
  • From: Beliavsky
• Re: A file managment question
  • From: ejko123
• Re: string concatenation
  • From: Gary Scott
• Re: A file managment question
  • From: Tim Prince
• A file managment question
  • From: analyst41
• Re: () in output lists
  • From: glen herrmannsfeldt
• Re: string concatenation
  • From: glen herrmannsfeldt
• Re: () in output lists
  • From: Brooks Moses
• Re: Pointer-based arrays output strange
  • From: Sebastian Hanigk
• Re: Pointer-based arrays output strange
  • From: Sebastian Hanigk
• Re: Pointer-based arrays output strange
  • From: Sebastian Hanigk
• Re: string concatenation
  • From: glen herrmannsfeldt
• Re: () in output lists
  • From: widmar
• Re: pointer and allocatable array problem
  • From: pieterprovoost@xxxxxxxxx
• Re: () in output lists
  • From: Richard E Maine
• Re: Pointer-based arrays output strange
  • From: Richard Maine
• Re: Pointer-based arrays output strange
  • From: Steven G. Kargl
• Re: () in output lists
  • From: Brooks Moses
• Pointer-based arrays output strange
  • From: Sebastian Hanigk
• Re: string concatenation
  • From: Janne Blomqvist
• Re: Handling large datasets in Fortran
  • From: Greg Lindahl
• Re: pointer and allocatable array problem
  • From: Steve Lionel
• Re: () in output lists
  • From: James Giles
• Re: () in output lists
  • From: J.F. Cornwall
• Re: pointer and allocatable array problem
  • From: Michael Metcalf
• Re: () in output lists
  • From: Michael Metcalf
• Re: pointer and allocatable array problem
  • From: pieterprovoost@xxxxxxxxx
• Re: string concatenation
  • From: Richard E Maine
• Re: pointer and allocatable array problem
  • From: Michael Metcalf
• Re: () in output lists
  • From: Paul van Delst
• Re: pointer and allocatable array problem
  • From: pieterprovoost@xxxxxxxxx
• Re: string concatenation
  • From: Steven G. Kargl
• Re: () in output lists
  • From: Richard E Maine
• Re: pointer and allocatable array problem
  • From: Richard E Maine
• Re: () in output lists
  • From: Paul van Delst
• Re: () in output lists
  • From: Richard E Maine
• pointer and allocatable array problem
  • From: pieterprovoost@xxxxxxxxx
• Re: string concatenation
  • From: Janne Blomqvist
• Re: () in output lists
  • From: Ron Shepard
• Re: string concatenation
  • From: Dick Hendrickson
• Re: string concatenation
  • From: Jim McDonald
• Re: string concatenation
  • From: Richard Maine
• Re: string concatenation
  • From: Beliavsky
• Re: schedule for Gfortran Windows binaries
  • From: FX
• Re: string concatenation
  • From: Michael Prager
• Re: string concatenation
  • From: Paul van Delst
• Re: Most elegant way to read to allocatable array?
  • From: Steve Lionel
• Re: Handling large datasets in Fortran
  • From: Gordon Sande
• Re: string concatenation
  • From: Gary Scott
• Re: Most elegant way to read to allocatable array?
  • From: Gary Scott
• Re: fortran programs with big RAM requirement
  • From: golu
• Re: Handling large datasets in Fortran
  • From: Arjen Markus
• Re: string concatenation
  • From: Jugoslav Dujic
• Re: Associative arrays in Fortran
  • From: Arjen Markus
• Re: () in output lists
  • From: glen herrmannsfeldt
• Re: string concatenation
  • From: glen herrmannsfeldt
• Handling large datasets in Fortran
  • From: L . Spadavecchia
• Re: string concatenation
  • From: heavytull
• Re: string concatenation
  • From: Ian Bush
• Re: string concatenation
  • From: heavytull
• Re: Most elegant way to read to allocatable array?
  • From: James Giles
• Re: Most elegant way to read to allocatable array?
  • From: Jan Vorbrüggen
• Re: () in output lists
  • From: James Giles
• Re: Most elegant way to read to allocatable array?
  • From: James Giles
• Re: () in output lists
  • From: Richard Maine
• Re: Most elegant way to read to allocatable array?
  • From: glen herrmannsfeldt
• Re: Most elegant way to read to allocatable array?
  • From: glen herrmannsfeldt
• Re: string concatenation
  • From: Richard Maine
• () in output lists
  • From: Ron Shepard
• Re: Most elegant way to read to allocatable array?
  • From: Jan Vorbrüggen
• Re: Most elegant way to read to allocatable array?
  • From: Jan Vorbrüggen
• Re: Most elegant way to read to allocatable array?
  • From: Jan Vorbrüggen
• Re: Questions about Fortran 2003 "volatile"
  • From: Steven Correll
• Re: string concatenation
  • From: Greg Lindahl
• Re: string concatenation
  • From: Gary Scott
• Re: What is the option for ifort to stop at first statement in IF
  • From: glen herrmannsfeldt
• Re: string concatenation
  • From: Richard Maine
• Re: string concatenation
  • From: Michael Metcalf
• Re: schedule for Gfortran Windows binaries
  • From: Ian Gay
• Re: What is the option for ifort to stop at first statement in IF
  • From: Greg Lindahl
• Re: What is the option for ifort to stop at first statement in IF
  • From: Dan Nagle
• Re: schedule for Gfortran Windows binaries
  • From: Beliavsky
• Re: directories creation
  • From: Richard Maine
• Re: string concatenation
  • From: glen herrmannsfeldt
• Re: string concatenation
  • From: glen herrmannsfeldt
• Re: directories creation
  • From: glen herrmannsfeldt
• Re: string concatenation
  • From: George Schroeder
• Re: string concatenation
  • From: Richard Maine
• Re: string concatenation
  • From: Rich Townsend
• Re: directories creation
  • From: heavytull
• Re: string concatenation
  • From: heavytull
• Re: What is the option for ifort to stop at first statement in IF
  • From: Craig Powers
• Re: string concatenation
  • From: Richard Maine
• Re: directories creation
  • From: Gordon Sande
• Re: Most elegant way to read to allocatable array?
  • From: James Giles
• Re: string concatenation
  • From: Michael Metcalf
• Re: string concatenation
  • From: Rich Townsend
• Re: Most elegant way to read to allocatable array?
  • From: James Giles
• Re: directories creation
  • From: Beliavsky
• Re: directories creation
  • From: Steven G. Kargl
• string concatenation
  • From: heavytull
• Re: Most elegant way to read to allocatable array?
  • From: Steve Lionel
• Re: What is the option for ifort to stop at first statement in IF
  • From: Greg Lindahl
• Re: directories creation
  • From: heavytull
• Re: RE: directories creation
  • From: Richard Maine
• Re: directories creation
  • From: glen herrmannsfeldt
• Re: directories creation
  • From: Beliavsky
• RE: directories creation
  • From: meek
• Re: directories creation
  • From: Richard E Maine
• Re: directories creation
  • From: Rich Townsend
• directories creation
  • From: heavytull
• Re: Most elegant way to read to allocatable array?
  • From: glen herrmannsfeldt
• Re: Initialization for derived-type arrays
  • From: Richard Maine
• Re: Initialization for derived-type arrays
  • From: Dan Nagle
• Re: 'java for fortran'
  • From: Rich Townsend
• Re: Initialization for derived-type arrays
  • From: Rich Townsend
• 'java for fortran'
  • From: max
• Re: Initialization for derived-type arrays
  • From: Jugoslav Dujic
• Re: Initialization for derived-type arrays
  • From: Jan Vorbrüggen
• Re: Initialization for derived-type arrays
  • From: Joost
• Initialization for derived-type arrays
  • From: Rich Townsend
• Fortran FAQ (was Re: integer to char conversion)
  • From: Beliavsky
• Re: Most elegant way to read to allocatable array?
  • From: Pierre Asselin
• Re: integer to char conversion
  • From: Gordon Grubert
• Re: integer to char conversion
  • From: heavytull
• Re: Select Case Fallthrough
  • From: Jan Vorbrüggen
• Re: Most elegant way to read to allocatable array?
  • From: Jan Vorbrüggen
• Re: Most elegant way to read to allocatable array?
  • From: Jan Vorbrüggen
• Re: OO Definitions
  • From: Arjen Markus
• Re: Select Case Fallthrough
  • From: Aidan
• Re: integer to char conversion
  • From: Diten
• Re: Most elegant way to read to allocatable array?
  • From: Gary Scott
• Re: Most elegant way to read to allocatable array?
  • From: James Giles
• Re: What is the option for ifort to stop at first statement in IF
  • From: Dan Nagle
• Re: OO Definitions
  • From: Gary Scott
• Re: integer to char conversion
  • From: Jim
• Re: integer to char conversion
  • From: Paul van Delst
• Re: OO Definitions
  • From: Gary Scott
• integer to char conversion
  • From: heavytull
• Re: OO Definitions
  • From: sureal
• Re: Most elegant way to read to allocatable array?
  • From: Richard Maine
• Re: Most elegant way to read to allocatable array?
  • From: Richard Maine
• Re: OO Definitions
  • From: Michael Metcalf
• Re: Most elegant way to read to allocatable array?
  • From: Janne Blomqvist
• Re: Most elegant way to read to allocatable array?
  • From: Dick Hendrickson
• Re: What is the option for ifort to stop at first statement in IF
  • From: James Giles
• Re: What is the option for ifort to stop at first statement in IF
  • From: Craig Powers
• Re: Change to posting display
  • From: John Harper
• Re: What is the option for ifort to stop at first statement in IF
  • From: James Giles
• Re: Select Case Fallthrough
  • From: Thomas Koenig
• Re: trouble with initializing array of complex type
  • From: glen herrmannsfeldt
• Re: Associative arrays in Fortran
  • From: glen herrmannsfeldt
• Re: Double Posts ... (Reading Binary data re-up)
  • From: David Koch
• Re: OO Definitions
  • From: Beliavsky
• Re: OO Definitions
  • From: Richard Maine
• OO Definitions
  • From: gary . l . scott
• Re: Associative arrays in Fortran
  • From: Pierre Asselin
• attn: mark - genuinely inspiring fast downloads - vir ruttu fevyo - (1/1)
  • From: riley
• Re: trouble with initializing array of complex type
  • From: Les
• Re: trouble with initializing array of complex type
  • From: qsc
• Re: trouble with initializing array of complex type
  • From: Paul van Delst
• Re: trouble with initializing array of complex type
  • From: Steve Lionel
• trouble with initializing array of complex type
  • From: qsc
• Re: What is the option for ifort to stop at first statement in IF
  • From: Dan Nagle
• Re: pointer association with empty targets
  • From: Steve Lionel
• Re: Change to posting display
  • From: Steve Lionel
• Re: What is the option for ifort to stop at first statement in IF
  • From: Steve Lionel
• Re: pointer association with empty targets
  • From: FX
• Re: Change to posting display
  • From: Gary Scott
• Re: OT: Change to posting display
  • From: jon
• Re: No user control on leading zeros in fraction(?)
  • From: AeroSpace Ed
• Re: Where to place IMPLICIT NONE
  • From: bru
• Re: Select Case Fallthrough
  • From: glen herrmannsfeldt
• Re: Most elegant way to read to allocatable array?
  • From: glen herrmannsfeldt
• Re: Change to posting display
  • From: Catherine Rees Lay
• Re: Where to place IMPLICIT NONE
  • From: Sebastian Hanigk
• Where to place IMPLICIT NONE
  • From: bru
• Re: No user control on leading zeros in fraction(?)
  • From: Terence
• Re: NEQNF/DNEQNF
  • From: nakisa
• Change to posting display
  • From: Terence
• Re: Most elegant way to read to allocatable array?
  • From: James Giles
• Re: Most elegant way to read to allocatable array?
  • From: Janne Blomqvist
• Re: No user control on leading zeros in fraction(?)
  • From: Richard Maine
• Re: No user control on leading zeros in fraction(?)
  • From: ttw
• Re: Select Case Fallthrough
  • From: glen herrmannsfeldt
• Re: Select Case Fallthrough
  • From: Aidan
• Re: Most elegant way to read to allocatable array?
  • From: James Giles
• Re: Most elegant way to read to allocatable array?
  • From: Steven G. Kargl
• Re: Most elegant way to read to allocatable array?
  • From: Gary Scott
• Re: User Defined Data Types
  • From: glen herrmannsfeldt
• Re: User Defined Data Types
  • From: Richard Maine
• Re: What is the option for ifort to stop at first statement in IF
  • From: glen herrmannsfeldt
• Re: Associative arrays in Fortran
  • From: Greg Lindahl
• Re: Most elegant way to read to allocatable array?
  • From: Janne Blomqvist
• Re: Select Case Fallthrough
  • From: glen herrmannsfeldt
• User Defined Data Types
  • From: jdturner
• Re: Select Case Fallthrough
  • From: PJH
• Re: Associative arrays in Fortran
  • From: Louis Krupp
• Re: What is the option for ifort to stop at first statement in IF
  • From: Richard Maine
• Re: Associative arrays in Fortran
  • From: Craig Powers
• Re: What is the option for ifort to stop at first statement in IF
  • From: Greg Lindahl
• Re: What is the option for ifort to stop at first statement in IF
  • From: Thomas Koenig
• Re: What is the option for ifort to stop at first statement in IF
  • From: e p chandler
• Re: What is the option for ifort to stop at first statement in IF
  • From: Gordon Sande
• Re: What is the option for ifort to stop at first statement in IF
  • From: Steve Lionel
• What is the option for ifort to stop at first statement in IF
  • From: sk4online@xxxxxxxxx
• Re: Associative arrays in Fortran
  • From: Greg Lindahl
• Re: Associative arrays in Fortran
  • From: glen herrmannsfeldt
• Re: pointer association with empty targets
  • From: Greg Lindahl
• Re: No user control on leading zeros in fraction(?)
  • From: glen herrmannsfeldt
• Associative arrays in Fortran
  • From: max
• Re: No user control on leading zeros in fraction(?)
  • From: gary . l . scott
• Re: No user control on leading zeros in fraction(?)
  • From: Dan Nagle
• No user control on leading zeros in fraction(?)
  • From: yair999@xxxxxxxxx
• Re: Question about ACHAR and IACHAR.
  • From: glen herrmannsfeldt
• Re: Double Posts ... (Reading Binary data re-up)
  • From: glen herrmannsfeldt
• Re: Double Posts ... (Reading Binary data re-up)
  • From: Gordon Sande
• Re: Double Posts ... (Reading Binary data re-up)
  • From: Richard Maine
• Re: Double Posts ... (Reading Binary data re-up)
  • From: Richard Maine
• Re: Double Posts ... (Reading Binary data re-up)
  • From: David Koch
• Re: Question about ACHAR and IACHAR.
  • From: James Parsly
• Re: Most elegant way to read to allocatable array?
  • From: Pierre Asselin
• Re: NEQNF/DNEQNF
  • From: Beliavsky
• Re: restructuring tool for Fortran 90
  • From: Beliavsky
• restructuring tool for Fortran 90
  • From: Poecher@xxxxxxx
• Re: NEQNF/DNEQNF
  • From: nakisa
• Re: pop-up dialog box showing module sub/fun or derived type contents
  • From: Jugoslav Dujic
• Re: Assignment of derived types
  • From: robert . corbett
• Re: Question about ACHAR and IACHAR.
  • From: e p chandler
• Re: Question about ACHAR and IACHAR.
  • From: glen herrmannsfeldt
• Re: Question about ACHAR and IACHAR.
  • From: Richard Maine
• Question about ACHAR and IACHAR.
  • From: Brooks Moses
• Re: how to read a parameter from a normal text file
  • From: glen herrmannsfeldt
• Re: schedule for Gfortran Windows binaries
  • From: FX
• Re: how to read a parameter from a normal text file
  • From: glen herrmannsfeldt
• Re: how to read a parameter from a normal text file
  • From: P.Wholey
• Re: Assignment of derived types
  • From: Steve Lionel
• Re: Unexplainable Behaviour with Array Assigment on Intel 9 Compiler
  • From: glen herrmannsfeldt
• Re: NEQNF/DNEQNF
  • From: jwm
• Re: Assignment of derived types
  • From: Gib Bogle
• Re: Select Case Fallthrough
  • From: glen herrmannsfeldt
• Re: Unexplainable Behaviour with Array Assigment on Intel 9 Compiler
  • From: Greg Lindahl
• Re: Most elegant way to read to allocatable array?
  • From: Richard E Maine
• Re: Select Case Fallthrough
  • From: Richard Maine
• Re: Most elegant way to read to allocatable array?
  • From: Dan Nagle
• Re: Select Case Fallthrough
  • From: glen herrmannsfeldt
• Re: Select Case Fallthrough
  • From: Ron Shepard
• Re: Most elegant way to read to allocatable array?
  • From: glen herrmannsfeldt
• Re: Most elegant way to read to allocatable array?
  • From: Richard E Maine
• Re: Select Case Fallthrough
  • From: Richard E Maine
• NEQNF/DNEQNF
  • From: nakisa
• Re: Most elegant way to read to allocatable array?
  • From: Richard E Maine
• Re: Assignment of derived types
  • From: mm148881
• Re: schedule for Gfortran Windows binaries
  • From: Vincent MAGNIN
• Re: Assignment of derived types
  • From: Richard E Maine
• Re: Assignment of derived types
  • From: mm148881
• Re: Assignment of derived types
  • From: Steve Lionel
• Re: Assignment of derived types
  • From: Michael Metcalf
• Re: Unexplainable Behaviour with Array Assigment on Intel 9 Compiler
  • From: Keith Refson
• Assignment of derived types
  • From: mm148881
• Re: Most elegant way to read to allocatable array?
  • From: Pierre Asselin
• Re: Most elegant way to read to allocatable array?
  • From: Pierre Asselin
• Re: Unexplainable Behaviour with Array Assigment on Intel 9 Compiler
  • From: Tim Prince
• Re: Unexplainable Behaviour with Array Assigment on Intel 9 Compiler
  • From: Steve Lionel
• Re: schedule for Gfortran Windows binaries
  • From: FX
• Re: Unexplainable Behaviour with Array Assigment on Intel 9 Compiler
  • From: Keith Refson
• Re: Select Case Fallthrough
  • From: PJH
• schedule for Gfortran Windows binaries
  • From: Beliavsky
• Re: Most elegant way to read to allocatable array?
  • From: Gary Scott
• Re: Select Case Fallthrough
  • From: PJH
• Re: Double Posts ... (Reading Binary data re-up)
  • From: Michael Metcalf
• Re: Double Posts ... (Reading Binary data re-up)
  • From: David Koch
• Re: how to read a parameter from a normal text file
  • From: Dr Ivan D. Reid
• Re: Most elegant way to read to allocatable array?
  • From: James Giles
• Re: Most elegant way to read to allocatable array?
  • From: James Giles
• Re: Most elegant way to read to allocatable array?
  • From: robert . corbett
• Re: Most elegant way to read to allocatable array?
  • From: Richard Maine
• Re: Most elegant way to read to allocatable array?
  • From: Gary Scott
• Re: IMSL
  • From: jwm
• Re: Most elegant way to read to allocatable array?
  • From: James Giles
• Re: Select Case Fallthrough
  • From: robert . corbett
• Re: Most elegant way to read to allocatable array?
  • From: Richard Maine
• Re: Most elegant way to read to allocatable array?
  • From: glen herrmannsfeldt
• Re: Select Case Fallthrough
  • From: Steven G. Kargl
• Re: IMSL
  • From: Beliavsky
• Re: Select Case Fallthrough
  • From: PJH
• Re: Most elegant way to read to allocatable array?
  • From: Gary Scott
• Re: Most elegant way to read to allocatable array?
  • From: Pierre Asselin
• Re: IMSL
  • From: jwm
• Re: Select Case Fallthrough
  • From: James Giles
• Re: pointer association with empty targets
  • From: Greg Lindahl
• Re: IMSL
  • From: Tim Prince
• Re: IMSL
  • From: Tim Prince
• Re: Select Case Fallthrough
  • From: Tim Prince
• IMSL
  • From: nakisa
• Re: Most elegant way to read to allocatable array?
  • From: Gary Scott
• Re: pointer association with empty targets
  • From: Michael Metcalf
• pointer association with empty targets
  • From: highegg
• Re: Most elegant way to read to allocatable array?
  • From: Dan Nagle
• Select Case Fallthrough
  • From: PJH
• Re: Derived vs. Atomic types, was Re: Most elegant way to read to allocatable array?
  • From: James Giles
• Re: Derived vs. Atomic types, was Re: Most elegant way to read to allocatable array?
  • From: Brooks Moses
• Derived vs. Atomic types, was Re: Most elegant way to read to allocatable array?
  • From: Brooks Moses
• Re: Most elegant way to read to allocatable array?
  • From: glen herrmannsfeldt
• Re: Most elegant way to read to allocatable array?
  • From: Richard Maine
• Re: Most elegant way to read to allocatable array?
  • From: Dan Nagle
• Re: Questions about Fortran 2003 "volatile"
  • From: Tobias Burnus
• Re: Most elegant way to read to allocatable array?
  • From: Richard Maine
• Re: Most elegant way to read to allocatable array?
  • From: Richard Maine
• Re: Most elegant way to read to allocatable array?
  • From: Dan Nagle
• Re: Most elegant way to read to allocatable array?
  • From: James Giles
• Re: Most elegant way to read to allocatable array?
  • From: Richard Maine
• Re: Most elegant way to read to allocatable array?
  • From: Dan Nagle
• Re: Random number generator?
  • From: bwb
• Re: Random number generator?
  • From: bwb
• Re: Most elegant way to read to allocatable array?
  • From: James Giles
• Re: Most elegant way to read to allocatable array?
  • From: Gary Scott
• Re: Most elegant way to read to allocatable array?
  • From: Richard Maine
• Re: Most elegant way to read to allocatable array?
  • From: Richard Maine
• Re: Most elegant way to read to allocatable array?
  • From: Gary Scott
• Re: Most elegant way to read to allocatable array?
  • From: Gary Scott
• Re: Most elegant way to read to allocatable array?
  • From: Ron Shepard
• Re: Many small programs vs. one large program?
  • From: Richard Maine
• Re: Most elegant way to read to allocatable array?
  • From: Richard Maine
• Re: Most elegant way to read to allocatable array?
  • From: Richard Maine
• Re: Many small programs vs. one large program?
  • From: Ken Fairfield
• Re: Random number generator?
  • From: Walter Spector
• Re: Most elegant way to read to allocatable array?
  • From: Walter Spector
• Re: Random number generator?
  • From: Michael Prager
• Re: Most elegant way to read to allocatable array?
  • From: Dan Nagle
• Re: Most elegant way to read to allocatable array?
  • From: Gary Scott
• Re: how to read a parameter from a normal text file
  • From: Tobias Burnus
• how to read a parameter from a normal text file
  • From: P.Wholey
• Re: Examples of FORALL and nested FORALL
  • From: Steven G. Kargl
• Re: Examples of FORALL and nested FORALL
  • From: Tom Micevski
• Re: Many small programs vs. one large program?
  • From: ttw
• Re: Most elegant way to read to allocatable array?
  • From: James Giles
• Re: Many small programs vs. one large program?
  • From: Gib Bogle
• Re: Random number generator?
  • From: Thomas Koenig
• Re: Random number generator?
  • From: Craig Powers
• Re: Pointer to subroutine?
  • From: Beliavsky
• Pointer to subroutine?
  • From: Andi Stephens
• Re: Many small programs vs. one large program?
  • From: Richard Maine
• Random number generator?
  • From: Andi Stephens
• Re: Many small programs vs. one large program?
  • From: Richard Maine
• Re: Many small programs vs. one large program?
  • From: Louis Krupp
• Re: Many small programs vs. one large program?
  • From: glen herrmannsfeldt
• Re: Most elegant way to read to allocatable array?
  • From: Richard Maine
• Re: Many small programs vs. one large program?
  • From: Richard Maine
• Re: Most elegant way to read to allocatable array?
  • From: glen herrmannsfeldt
• Re: Most elegant way to read to allocatable array?
  • From: glen herrmannsfeldt
• Re: Questions about Fortran 2003 "volatile"
  • From: Steve Lionel
• Re: Many small programs vs. one large program?
  • From: glen herrmannsfeldt
• Re: Most elegant way to read to allocatable array?
  • From: Michael Prager
• Re: Multithreading on Multicore Processors
  • From: glen herrmannsfeldt
• Re: Looking for a good Fortran 90/95 text for beginners
  • From: Tunjang
• Re: Most elegant way to read to allocatable array?
  • From: Richard Maine
• Re: unix "time" command as performance measure
  • From: Ron Shepard
• Re: Most elegant way to read to allocatable array?
  • From: yair999@xxxxxxxxx
• Re: Multithreading on Multicore Processors
  • From: Beliavsky
• Re: pop-up dialog box showing module sub/fun or derived type contents
  • From: Joost
• Re: unix "time" command as performance measure
  • From: Beliavsky
• Re: Many small programs vs. one large program?
  • From: Pierre Asselin
• Re: pop-up dialog box showing module sub/fun or derived type contents
  • From: Dan Nagle
• Re: pop-up dialog box showing module sub/fun or derived type contents
  • From: Beliavsky
• Re: Multithreading on Multicore Processors
  • From: Janne Blomqvist
• Re: Many small programs vs. one large program?
  • From: Gary Scott
• Re: Questions about Fortran 2003 "volatile"
  • From: Michael Metcalf
• Re: Most elegant way to read to allocatable array?
  • From: Louis Krupp
• Re: run-time error M6101 : MATH
  • From: Tunjang
• Re: run-time error M6101 : MATH
  • From: Tunjang
• Re: Most elegant way to read to allocatable array?
  • From: yair999@xxxxxxxxx
• Re: Array/Vector Cross product
  • From: Ron Shepard
• Re: run-time error M6101 : MATH
  • From: e p chandler
• Re: run-time error M6101 : MATH
  • From: Terence
• Re: run-time error M6101 : MATH
  • From: Tunjang
• Re: ibits order. Was: Hollerith constants on a little endian machine
  • From: John Harper
• Re: Many small programs vs. one large program?
  • From: Ken Fairfield
• Re: pop-up dialog box showing module sub/fun or derived type contents
  • From: Gary Scott
• Re: Encapsulate
  • From: Mike
• pop-up dialog box showing module sub/fun or derived type contents
  • From: Mike
• Encapsulate
  • From: Mike
• Re: Many small programs vs. one large program?
  • From: Mike
• Re: run-time error M6101 : MATH
  • From: e p chandler
• Re: Most elegant way to read to allocatable array?
  • From: Richard Maine
• Re: Necessity of Deallocate/Close statements at end of program?
  • From: stocksami@xxxxxxxxxxxxx
• Re: Most elegant way to read to allocatable array?
  • From: Louis Krupp
• Re: Many small programs vs. one large program?
  • From: Terence
• Re: Get the version of IMSL/Fortran Mathematics and Statistics and NAG/Fortran Numeric Algorithms Library Library
  • From: DTB
• Re: Problem reading a binary file in fortran
  • From: James Giles
• Re: Most elegant way to read to allocatable array?
  • From: PJH
• Re: advance="no" on list-directed read
  • From: glen herrmannsfeldt
• Re: Most elegant way to read to allocatable array?
  • From: glen herrmannsfeldt
• Re: advance="no" on list-directed read
  • From: Richard E Maine
• run-time error M6101 : MATH
  • From: Tunjang
• Re: Most elegant way to read to allocatable array?
  • From: glen herrmannsfeldt
• advance="no" on list-directed read (was: Most elegant way to read to allocatable array?)
  • From: Thomas Koenig
• Re: Most elegant way to read to allocatable array?
  • From: Richard E Maine
• Re: Most elegant way to read to allocatable array?
  • From: yair999@xxxxxxxxx
• Re: Most elegant way to read to allocatable array?
  • From: glen herrmannsfeldt
• Re: Most elegant way to read to allocatable array?
  • From: Richard Maine
• Re: Hollerith constants on a little endian machine
  • From: glen herrmannsfeldt
• Re: Most elegant way to read to allocatable array?
  • From: Richard Maine
• Re: Most elegant way to read to allocatable array?
  • From: Richard Maine
• Re: Necessity of Deallocate/Close statements at end of program?
  • From: glen herrmannsfeldt
• Re: Most elegant way to read to allocatable array?
  • From: glen herrmannsfeldt
• Re: Most elegant way to read to allocatable array?
  • From: glen herrmannsfeldt
• Re: Problem reading a binary file in fortran
  • From: glen herrmannsfeldt
• Re: Get the version of IMSL/Fortran Mathematics and Statistics and NAG/Fortran Numeric Algorithms Library Library
  • From: pod69
• Re: Problem reading a binary file in fortran
  • From: glen herrmannsfeldt
• Re: Hollerith constants on a little endian machine
  • From: Steve Lionel
• Re: Most elegant way to read to allocatable array?
  • From: yair999@xxxxxxxxx
• Re: Most elegant way to read to allocatable array?
  • From: yair999@xxxxxxxxx
• Re: Most elegant way to read to allocatable array?
  • From: yair999@xxxxxxxxx
• Re: Many small programs vs. one large program?
  • From: Richard Maine
• Re: Hollerith constants on a little endian machine
  • From: glen herrmannsfeldt
• Re: Necessity of Deallocate/Close statements at end of program?
  • From: Richard Maine
• Re: Get the version of IMSL/Fortran Mathematics and Statistics and NAG/Fortran Numeric Algorithms Library Library
  • From: Steve Lionel
• Re: Get the version of IMSL/Fortran Mathematics and Statistics and NAG/Fortran Numeric Algorithms Library Library
  • From: Beliavsky
• Re: Necessity of Deallocate/Close statements at end of program?
  • From: Steve Lionel
• Get the version of IMSL/Fortran Mathematics and Statistics and NAG/Fortran Numeric Algorithms Library Library
  • From: pod69
• Re: Most elegant way to read to allocatable array?
  • From: Richard Maine
• Re: Most elegant way to read to allocatable array?
  • From: Thomas Koenig
• Re: ibits order. Was: Hollerith constants on a little endian machine
  • From: Walter Spector
• Re: Most elegant way to read to allocatable array?
  • From: Beliavsky
• Most elegant way to read to allocatable array?
  • From: yair999@xxxxxxxxx
• Re: Array/Vector Cross product
  • From: Beliavsky
• Re: Problem reading a binary file in fortran
  • From: Charles Russell
• Re: Many small programs vs. one large program?
  • From: Beliavsky
• Re: Many small programs vs. one large program?
  • From: Beliavsky
• Re: Multithreading on Multicore Processors
  • From: Thomas Koenig
• Re: passing variables.... crazy error?
  • From: Richard Edgar
• Re: Hollerith constants on a little endian machine
  • From: Steve Lionel
• Re: Multithreading on Multicore Processors
  • From: Grogley
• Re: Array/Vector Cross product
  • From: Cleverbum
• Re: Array/Vector Cross product
  • From: Arjen Markus
• Array/Vector Cross product
  • From: Cleverbum
• Re: passing variables.... crazy error?
  • From: Arjen Markus
• Re: Problem reading a binary file in fortran
  • From: James Giles
• Re: Problem reading a binary file in fortran
  • From: Richard Maine
• Re: Problem reading a binary file in fortran
  • From: Charles Russell
• Re: ibits order. Was: Hollerith constants on a little endian machine
  • From: Steven G. Kargl
• Re: Many small programs vs. one large program?
  • From: Beliavsky
• Re: Hollerith constants on a little endian machine
  • From: glen herrmannsfeldt
• Re: ibits order. Was: Hollerith constants on a little endian machine
  • From: glen herrmannsfeldt
• Re: ibits order. Was: Hollerith constants on a little endian machine
  • From: Brooks Moses
• Re: Problem reading a binary file in fortran
  • From: James Giles
• Re: Hollerith constants on a little endian machine
  • From: robert . corbett
• Re: Problem reading a binary file in fortran
  • From: glen herrmannsfeldt
• Re: Problem reading a binary file in fortran
  • From: Gary Scott
• Re: Problem reading a binary file in fortran
  • From: Charles Russell
• Re: using optional arguments
  • From: Richard Maine
• Re: Multithreading on Multicore Processors
  • From: Harold Stevens
• Re: Problem reading a binary file in fortran
  • From: James Giles
• Re: ibits order. Was: Hollerith constants on a little endian machine
  • From: John Harper
• Re: Problem reading a binary file in fortran
  • From: Gary Scott
• Re: Multithreading on Multicore Processors
  • From: AeroSpace Ed
• Re: using optional arguments
  • From: Mike
• Re: Problem reading a binary file in fortran
  • From: glen herrmannsfeldt
• Re: Can WHERE help?
  • From: glen herrmannsfeldt
• Re: Problem reading a binary file in fortran
  • From: James Giles
• Re: Error while compiling using CHARACTER*(*) attribute in a NAMELIST
  • From: robin
• Re: Many small programs vs. one large program?
  • From: robin
• Re: Looking for a good Fortran 90/95 text for beginners
  • From: robin
• Re: Can WHERE help?
  • From: robin
• Re: Hollerith constants on a little endian machine
  • From: robin
• Re: ibits order. Was: Hollerith constants on a little endian machine
  • From: Steven G. Kargl
• Re: Problem reading a binary file in fortran
  • From: Steve Lionel
• Re: Problem reading a binary file in fortran
  • From: glen herrmannsfeldt
• Questions about Fortran 2003 "volatile"
  • From: Steven Correll
• ibits order. Was: Hollerith constants on a little endian machine
  • From: John Harper
• Re: Problem reading a binary file in fortran
  • From: pradeep.bhattad@xxxxxxxxx
• Re: Problem reading a binary file in fortran
  • From: Richard Maine
• RE: Problem reading a binary file in fortran
  • From: meek
• Re: passing variables.... crazy error?
  • From: Jim
• Re: Problem reading a binary file in fortran
  • From: James Giles
• Re: Problem reading a binary file in fortran
  • From: pradeep.bhattad@xxxxxxxxx
• Re: passing variables.... crazy error?
  • From: Colin Watters
• Re: Multithreading on Multicore Processors
  • From: Brooks Moses
• Re: Problem reading a binary file in fortran
  • From: Richard Maine
• Re: Problem reading a binary file in fortran
  • From: Gib Bogle
• Re: Problem reading a binary file in fortran
  • From: Louis Krupp
• Re: passing variables.... crazy error?
  • From: Dave
• Re: Problem reading a binary file in fortran
  • From: glen herrmannsfeldt
• Re: Problem reading a binary file in fortran
  • From: Gib Bogle
• Re: passing variables.... crazy error?
  • From: Thomas Koenig
• Re: passing variables.... crazy error?
  • From: Gordon Sande
• Re: Problem reading a binary file in fortran
  • From: Gordon Sande
• passing variables.... crazy error?
  • From: Dave
• Re: Problem reading a binary file in fortran
  • From: pradeep.bhattad@xxxxxxxxx
• Re: Problem reading a binary file in fortran
  • From: Gordon Sande
• Re: Double Posts ... (Reading Binary data re-up)
  • From: Richard Maine
• Re: Problem reading a binary file in fortran
  • From: Richard E Maine
• Re: Problem reading a binary file in fortran
  • From: glen herrmannsfeldt
• Re: Unexplainable Behaviour with Array Assigment on Intel 9 Compiler
  • From: glen herrmannsfeldt
• Re: Problem reading a binary file in fortran
  • From: mecej4
• Re: Problem reading a binary file in fortran
  • From: pradeep.bhattad@xxxxxxxxx
• Re: Problem reading a binary file in fortran
  • From: David Frank
• Re: gfortran and ifort unformatted files
  • From: Ron Shepard
• Re: gfortran and ifort unformatted files
  • From: Ron Shepard
• Problem reading a binary file in fortran
  • From: pradeep.bhattad@xxxxxxxxx
• Re: Passing Unallocated Allocatable arrays
  • From: Richard E Maine
• Re: gfortran and ifort unformatted files
  • From: Richard Maine
• Re: Error while compiling using CHARACTER*(*) attribute in a NAMELIST
  • From: Richard Maine
• Re: Unexplainable Behaviour with Array Assigment on Intel 9 Compiler
  • From: Michael Metcalf
• Re: gfortran and ifort unformatted files
  • From: Paul van Delst
• Re: Unexplainable Behaviour with Array Assigment on Intel 9 Compiler
  • From: Paul van Delst
• Re: Double Posts ... (Reading Binary data re-up)
  • From: Gordon Sande
• Re: Double Posts ... (Reading Binary data re-up)
  • From: David Koch
• Re: Multithreading on Multicore Processors
  • From: Steve Lionel
• Re: using optional arguments
  • From: Herman D . Knoble
• Re: using optional arguments
  • From: Michael Metcalf
• Re: using optional arguments
  • From: Jugoslav Dujic
• Re: using optional arguments
  • From: Mike
• Re: Unexplainable Behaviour with Array Assigment on Intel 9 Compiler
  • From: Michael Metcalf
• using optional arguments
  • From: Mike
• Re: What is run-time error F6501?
  • From: Tunjang
• Re: Multithreading on Multicore Processors
  • From: Mark Westwood
• Re: Multithreading on Multicore Processors
  • From: Mark Westwood
• Re: Multithreading on Multicore Processors
  • From: Mark Westwood
• Re: Multithreading on Multicore Processors
  • From: Grogley
• Re: Multithreading on Multicore Processors
  • From: Grogley
• Re: Passing Unallocated Allocatable arrays
  • From: Ian Bush
• Re: Passing Unallocated Allocatable arrays
  • From: Jan Vorbrüggen
• Re: Passing Unallocated Allocatable arrays
  • From: Ian Bush
• Re: Passing Unallocated Allocatable arrays
  • From: Jan Vorbrüggen
• Re: Multithreading on Multicore Processors
  • From: Jan Vorbrüggen
• Re: Multithreading on Multicore Processors
  • From: Janne Blomqvist
• Re: Error while compiling using CHARACTER*(*) attribute in a NAMELIST
  • From: neha
• Re: writing step by step
  • From: Sebastian Hanigk
• Re: Hollerith constants on a little endian machine
  • From: glen herrmannsfeldt
• Re: gfortran and ifort unformatted files
  • From: Tobias Burnus
• gfortran and ifort unformatted files
  • From: Ron Shepard
• Re: unix "time" command as performance measure
  • From: Richard Maine
• Re: unix "time" command as performance measure
  • From: Fly Away
• Re: unix "time" command as performance measure
  • From: robert . corbett
• Re: unix "time" command as performance measure
  • From: robert . corbett
• Re: unix "time" command as performance measure
  • From: Steven G. Kargl
• Re: Error while compiling using CHARACTER*(*) attribute in a NAMELIST
  • From: robert . corbett
• Re: Hollerith constants on a little endian machine
  • From: Tim Prince
• Re: unix "time" command as performance measure
  • From: robert . corbett
• unix "time" command as performance measure
  • From: Fly Away
• Re: Hollerith constants on a little endian machine
  • From: Greg Lindahl
• Re: Hollerith constants on a little endian machine
  • From: robert . corbett
• Re: Hollerith constants on a little endian machine
  • From: Richard Maine
• Re: Can WHERE help?
  • From: glen herrmannsfeldt
• Re: Multithreading on Multicore Processors
  • From: Brooks Moses
• Re: Hollerith constants on a little endian machine
  • From: Greg Lindahl
• Re: Unexplainable Behaviour with Array Assigment on Intel 9 Compiler
  • From: Richard Maine
• Re: Hollerith constants on a little endian machine
  • From: robert . corbett
• Re: Multithreading on Multicore Processors
  • From: Richard Maine
• Re: Hollerith constants on a little endian machine
  • From: robert . corbett
• Re: Hollerith constants on a little endian machine
  • From: Richard Maine
• Re: Hollerith constants on a little endian machine
  • From: glen herrmannsfeldt
• Can WHERE help?
  • From: Bruce Bowler
• Hollerith constants on a little endian machine
  • From: robert . corbett
• Re: Unexplainable Behaviour with Array Assigment on Intel 9 Compiler
  • From: glen herrmannsfeldt
• Re: Multithreading on Multicore Processors
  • From: Grogley
• Re: Multithreading on Multicore Processors
  • From: Grogley
• Re: Multithreading on Multicore Processors
  • From: Grogley
• Unexplainable Behaviour with Array Assigment on Intel 9 Compiler
  • From: timothy . stitt
• Re: Multithreading on Multicore Processors
  • From: Grogley
• Re: What is run-time error F6501?
  • From: ian_d_chivers
• Re: What is run-time error F6501?
  • From: Paul van Delst
• Re: VAST/77to90
  • From: max
• Re: Many small programs vs. one large program?
  • From: Charles Russell
• Re: What is run-time error F6501?
  • From: dpb
• Re: MS Fortran Powerstation 4.0 and Win XP
  • From: Dr Ivan D. Reid
• Re: writing step by step
  • From: John Harper
• Re: What is run-time error F6501?
  • From: Craig Powers
• Re: OT: first source release of Fortress
  • From: Greg Lindahl
• Re: MS Fortran Powerstation 4.0 and Win XP
  • From: Terence
• Re: What is run-time error F6501?
  • From: Terence
• Re: Many small programs vs. one large program?
  • From: Terence
• Re: Many small programs vs. one large program?
  • From: Terence
• Re: Passing pointers to subroutines in other modules
  • From: Håkan Lane
• Re: writing step by step
  • From: robert . corbett
• Re: Many small programs vs. one large program?
  • From: Terence
• Re: Many small programs vs. one large program?
  • From: Paul van Delst
• Re: Many small programs vs. one large program?
  • From: Beliavsky
• Re: Many small programs vs. one large program?
  • From: Herman D . Knoble
• Re: Many small programs vs. one large program?
  • From: Louis Krupp
• Re: writing step by step
  • From: glen herrmannsfeldt
• Re: Many small programs vs. one large program?
  • From: Beliavsky
• Re: Many small programs vs. one large program?
  • From: Richard Maine
• Re: writing step by step
  • From: Richard Maine
• Re: Many small programs vs. one large program?
  • From: Gordon Sande
• Re: Multithreading on Multicore Processors
  • From: David Jones
• Re: Passing Unallocated Allocatable arrays
  • From: Richard Maine
• Re: Multithreading on Multicore Processors
  • From: Charles Russell
• Re: Error while compiling using CHARACTER*(*) attribute in a NAMELIST
  • From: Richard Maine
• What is run-time error F6501?
  • From: Tunjang
• Re: Multithreading on Multicore Processors
  • From: Charles Russell
• Re: MS Fortran Powerstation 4.0 and Win XP
  • From: Tunjang
• Re: Multithreading on Multicore Processors
  • From: Mark Westwood
• Re: VAST/77to90
  • From: yair999@xxxxxxxxx
• Re: Examples of FORALL and nested FORALL
  • From: Craig Powers
• Re: VAST/77to90
  • From: yair999@xxxxxxxxx
• Re: VAST/77to90
  • From: yair999@xxxxxxxxx
• Re: writing step by step
  • From: highegg
• Re: VAST/77to90
  • From: Tim Prince
• Re: OT: first source release of Fortress
  • From: Beliavsky
• Re: writing step by step
  • From: Beliavsky
• Re: writing step by step
  • From: Gary Scott
• Re: Examples of FORALL and nested FORALL
  • From: Beliavsky
• Re: OT: first source release of Fortress
  • From: Mark Morss
• Re: Error while compiling using CHARACTER*(*) attribute in a NAMELIST
  • From: Michael Metcalf
• Re: Passing Unallocated Allocatable arrays
  • From: Jan Vorbrüggen
• Re: Examples of FORALL and nested FORALL
  • From: Joost
• Re: Multithreading on Multicore Processors
  • From: David Jones
• Re: Examples of FORALL and nested FORALL
  • From: Tobias Burnus
• Re: Passing Unallocated Allocatable arrays
  • From: Ian Bush
• Re: Examples of FORALL and nested FORALL
  • From: glen herrmannsfeldt
• Re: writing step by step
  • From: highegg
• Re: writing step by step
  • From: Sebastian Hanigk
• Re: writing step by step
  • From: nakisa
• Re: writing step by step
  • From: Arjen Markus
• writing step by step
  • From: nakisa
• Re: VAST/77to90
  • From: Joost
• Re: Examples of FORALL and nested FORALL
  • From: Joost
• Re: rewinding and backspacing standard output on UNIX
  • From: Ron Shepard
• Re: rewinding and backspacing standard output on UNIX
  • From: glen herrmannsfeldt
• Re: rewinding and backspacing standard output on UNIX
  • From: Ron Shepard
• Re: Examples of FORALL and nested FORALL
  • From: spam . brian . taylor
• Re: Examples of FORALL and nested FORALL
  • From: Steven G. Kargl
• Re: Error while compiling using CHARACTER*(*) attribute in a NAMELIST
  • From: neha
• Re: Examples of FORALL and nested FORALL
  • From: Tim Prince
• Re: OT: first source release of Fortress
  • From: robert . corbett
• Re: Examples of FORALL and nested FORALL
  • From: Steven G. Kargl
• Re: Multithreading on Multicore Processors
  • From: glen herrmannsfeldt
• Re: Multithreading on Multicore Processors
  • From: Tim Prince
• Re: Examples of FORALL and nested FORALL
  • From: Tim Prince
• Re: Multithreading on Multicore Processors
  • From: Greg Lindahl
• Re: Multithreading on Multicore Processors
  • From: Brooks Moses
• Re: Multithreading on Multicore Processors
  • From: Nobody
• Re: Looking for a good Fortran 90/95 text for beginners
  • From: Greg Lindahl
• Re: rewinding and backspacing standard output on UNIX
  • From: glen herrmannsfeldt
• Re: rewinding and backspacing standard output on UNIX
  • From: glen herrmannsfeldt
• Re: Error while compiling using CHARACTER*(*) attribute in a NAMELIST
  • From: glen herrmannsfeldt
• Re: rewinding and backspacing standard output on UNIX
  • From: Gordon Sande
• Re: rewinding and backspacing standard output on UNIX
  • From: Thomas Koenig
• Re: Looking for a good Fortran 90/95 text for beginners
  • From: Lane Straatman
• Re: VAST/77to90
  • From: Michael Metcalf
• Re: Examples of FORALL and nested FORALL
  • From: Steven G. Kargl
• Re: Passing Unallocated Allocatable arrays
  • From: Richard Maine
• Re: Examples of FORALL and nested FORALL
  • From: Steven G. Kargl
• Re: VAST/77to90
  • From: Joost
• VAST/77to90
  • From: yair999@xxxxxxxxx
• Re: Looking for a good Fortran 90/95 text for beginners
  • From: yair999@xxxxxxxxx
• Re: Examples of FORALL and nested FORALL
  • From: Joost
• Re: Examples of FORALL and nested FORALL
  • From: Michael Metcalf
• Re: Examples of FORALL and nested FORALL
  • From: Herman D . Knoble
• Re: Error while compiling using CHARACTER*(*) attribute in a NAMELIST
  • From: Michael Metcalf
• Re: Error while compiling using CHARACTER*(*) attribute in a NAMELIST
  • From: dpb
• Re: Error while compiling using CHARACTER*(*) attribute in a NAMELIST
  • From: Arjen Markus
• Re: Looking for a good Fortran 90/95 text for beginners
  • From: Beliavsky
• Re: Looking for a good Fortran 90/95 text for beginners
  • From: Gary Scott
• Re: rewinding and backspacing standard output on UNIX
  • From: Gary Scott
• Re: Looking for a good Fortran 90/95 text for beginners
  • From: Mark Westwood
• Re: Examples of FORALL and nested FORALL
  • From: Tom Micevski
• Re: Linking fortran and c++, segfault when using write(*,*)
  • From: Anders Schau Knatten
• Re: Linking fortran and c++, segfault when using write(*,*)
  • From: Anders Schau Knatten
• Re: Passing Unallocated Allocatable arrays
  • From: Herman D . Knoble
• Re: reference to undefined variable
  • From: robin
• Re: Weird behaviour with intent
  • From: robin
• Re: Fortran array optimizations
  • From: Herman D . Knoble
• Re: Passing Unallocated Allocatable arrays
  • From: Ian Bush
• Re: Passing Unallocated Allocatable arrays
  • From: Jan Vorbrüggen
• Re: Passing Unallocated Allocatable arrays
  • From: Arjen Markus
• Passing Unallocated Allocatable arrays
  • From: Ian Bush
• Error while compiling using CHARACTER*(*) attribute in a NAMELIST
  • From: neha
• Re: New book: "Writing Scientific Software"
  • From: Arjen Markus
• Re: rewinding and backspacing standard output on UNIX
  • From: glen herrmannsfeldt
• Re: rewinding and backspacing standard output on UNIX
  • From: glen herrmannsfeldt
• Re: rewinding and backspacing standard output on UNIX
  • From: glen herrmannsfeldt
• Re: rewinding and backspacing standard output on UNIX
  • From: Ron Shepard
• Re: Looking for a good Fortran 90/95 text for beginners
  • From: jwm
• Re: rewinding and backspacing standard output on UNIX
  • From: glen herrmannsfeldt
• Re: Looking for a good Fortran 90/95 text for beginners
  • From: Gary Scott
• Re: Looking for a good Fortran 90/95 text for beginners
  • From: Lane Straatman
• Re: HELP!How to recover .f file from exsting .o or bin file?
  • From: robin
• Re: rewinding and backspacing standard output on UNIX
  • From: Gordon Sande
• Re: rewinding and backspacing standard output on UNIX
  • From: Thomas Koenig
• Looking for a good Fortran 90/95 text for beginners
  • From: yair999@xxxxxxxxx
• Re: The D language seems similar to our F?
  • From: Lane Straatman
• Examples of FORALL and nested FORALL
  • From: Steven G. Kargl
• Re: Linking fortran and c++, segfault when using write(*,*)
  • From: Lane Straatman
• Re: OT: first source release of Fortress
  • From: Bil Kleb
• Re: rewinding and backspacing standard output on UNIX
  • From: Dan Nagle
• Re: rewinding and backspacing standard output on UNIX
  • From: Ron Shepard
• Re: rewinding and backspacing standard output on UNIX
  • From: Richard Maine
• Re: rewinding and backspacing standard output on UNIX
  • From: Gary Scott
• Re: Multithreading on Multicore Processors
  • From: Tim Prince
• Multithreading on Multicore Processors
  • From: Nobody
• rewinding and backspacing standard output on UNIX
  • From: robert . corbett
• OT: first source release of Fortress
  • From: robert . corbett
• Re: Fortran array optimizations
  • From: Tom Micevski
• Re: gfortran -M option not recognized
  • From: robert . corbett
• Re: F2003: Polymorphic argument association
  • From: robert . corbett
• Re: Passing pointers to subroutines in other modules
  • From: Gib Bogle
• Re: compiler issue and LSODE
  • From: pls
• Re: compiler issue and LSODE
  • From: Pierre Asselin
• Re: Linking fortran and c++, segfault when using write(*,*)
  • From: roman . janowczyk
• Re: Compaq Visual Fortran 6.6 installation problem
  • From: Steve Lionel
• Re: Reading Arguments from Command Line and reading binary data
  • From: glen herrmannsfeldt
• Re: Reading Arguments from Command Line and reading binary data
  • From: David Koch
• Re: Passing pointers to subroutines in other modules
  • From: Håkan Lane
• Re: Linking fortran and c++, segfault when using write(*,*)
  • From: PJH
• Re: cputime
  • From: Janne Blomqvist
• Re: Reading Arguments from Command Line and reading binary data
  • From: Richard Maine
• Re: [slightly OT] Fortran and gnu autoheader
  • From: Janne Blomqvist
• Re: Help! simple compile question
  • From: Michael Metcalf
• Re: Linking fortran and c++, segfault when using write(*,*)
  • From: Tim Prince
• Re: Help! simple compile question
  • From: J.F. Cornwall
• Linking fortran and c++, segfault when using write(*,*)
  • From: Anders Schau Knatten
• Re: reference to undefined variable
  • From: Gordon Sande
• Re: reference to undefined variable
  • From: Bart Vandewoestyne
• Re: The D language seems similar to our F?
  • From: Bil Kleb
• Re: Reading Arguments from Command Line and reading binary data
  • From: David Koch
• reference to undefined variable
  • From: Bart Vandewoestyne
• Re: The D language seems similar to our F?
  • From: PJH
• Re: Double Posts ...
  • From: glen herrmannsfeldt
• Re: Double Posts ...
  • From: Richard Maine
• Re: Double Posts ...
  • From: glen herrmannsfeldt
• Re: Help! simple compile question
  • From: Lane Straatman
• Re: Double Posts ...
  • From: Lane Straatman
• Re: compiler issue and LSODE
  • From: Walter Spector
• Re: compiler issue and LSODE
  • From: glen herrmannsfeldt
• compiler issue and LSODE
  • From: pls
• Re: gfortran -M option not recognized
  • From: Craig Powers
• Re: Reading Arguments from Command Line and reading binary data
  • From: Richard Maine
• Re: Reading Arguments from Command Line and reading binary data
  • From: David Koch
• Re: Double Posts ...
  • From: glen herrmannsfeldt
• Re: Reading Arguments from Command Line and reading binary data
  • From: David Koch
• Re: Reading Arguments from Command Line and reading binary data
  • From: Richard Maine
• Double Posts ...
  • From: David Koch
• Re: gfortran -M option not recognized
  • From: Richard Maine
• RE: Reading Arguments from Command Line and reading binary data
  • From: meek
• Re: gfortran -M option not recognized
  • From: Dave Seaman
• gfortran -M option not recognized
  • From: Shawn
• Re: Fortran array optimizations
  • From: Herman D . Knoble
• The D language seems similar to our F?
  • From: Bil Kleb
• Reading Arguments from Command Line and reading binary data
  • From: David the Dude
• Re: Fortran array optimizations
  • From: Tom Micevski
• Re: F2003: Polymorphic argument association
  • From: Richard Maine
• Re: F2003: Polymorphic argument association
  • From: Richard Maine
• Re: F2003: Polymorphic argument association
  • From: robert . corbett
• Re: Help! simple compile question
  • From: Richard E Maine
• Re: Help! simple compile question
  • From: Jerry Xue
• Re: Help! simple compile question
  • From: Richard Maine
• Re: Help! simple compile question
  • From: Richard Maine
• Re: Help! simple compile question
  • From: Ron Shepard
• Re: Help! simple compile question
  • From: Jerry Xue
• Re: Get installation path of a Fortran program
  • From: George N. White III
• Re: Help! simple compile question
  • From: Paul van Delst
• Re: New book: "Writing Scientific Software"
  • From: Bil Kleb
• New book: "Writing Scientific Software"
  • From: Beliavsky
• Re: Compaq Visual Fortran 6.6 installation problem
  • From: Tim Prince
• Re: Fortran array optimizations
  • From: Herman D . Knoble
• Re: Fortran array optimizations
  • From: Ian Bush
• Re: Help! simple compile question
  • From: Zuczek
• Re: Help! simple compile question
  • From: Catherine Rees Lay
• Parsing input arguments from command line and reading binary data
  • From: David the Dude
• Re: Help! simple compile question
  • From: Zuczek
• Compaq Visual Fortran 6.6 installation problem
  • From: Klemens Barfus
• Re: Help! simple compile question
  • From: Jerry Xue
• Re: g77 t shirt
  • From: Charles Russell
• Re: Parsing input arguments from command line and reading binary data
  • From: Richard Maine
• Re: Help! simple compile question
  • From: Richard Maine
• Re: Parsing input arguments from command line and reading binary data
  • From: John Harper
• Re: Parsing input arguments from command line and reading binary data
  • From: Lane Straatman
• Re: Passing pointers to subroutines in other modules
  • From: Gib Bogle
• Re: Help! simple compile question
  • From: Lane Straatman
• Re: Help! simple compile question
  • From: Richard Maine
• Re: Help! simple compile question
  • From: Richard Maine
• Help! simple compile question
  • From: Jerry Xue
• Help! simple compile question
  • From: Jerry Xue
• Help! simple compile question
  • From: Jerry Xue
• Re: Passing pointers to subroutines in other modules
  • From: Håkan Lane
• Re: intent attribute
  • From: robin
• Re: Fortran array optimizations
  • From: robin
• Re: Get installation path of a Fortran program
  • From: Hani Andreas Ibrahim
• Re: Parsing input arguments from command line and reading binary data
  • From: Hani Andreas Ibrahim
• Re: Fortran array optimizations
  • From: John Harper
• Re: Parsing input arguments from command line and reading binary data
  • From: glen herrmannsfeldt
• Parsing input arguments from command line and reading binary data
  • From: David the Dude
• Re: allocation error
  • From: glen herrmannsfeldt
• Re: allocation error
  • From: Thomas Koenig
• Re: allocation error
  • From: glen herrmannsfeldt
• Re: allocation error
  • From: Lane Straatman
• Re: intent attribute
  • From: Richard Maine
• Re: Get installation path of a Fortran program
  • From: Ron Shepard
• Re: Fortran array optimizations
  • From: Herman D . Knoble
• Get installation path of a Fortran program
  • From: Hani Andreas Ibrahim
• Re: Fortran array optimizations
  • From: Dr Ivan D. Reid
• Re: Fortran array optimizations
  • From: highegg
• Re: Fortran array optimizations
  • From: Jugoslav Dujic
• Re: Fortran array optimizations
  • From: Herman D . Knoble
• Re: intent attribute
  • From: glen herrmannsfeldt
• Re: intent attribute
  • From: Jan Vorbrüggen
• Re: intent attribute
  • From: David Flower
• Re: Passing pointers to subroutines in other modules
  • From: Reinhold Bader
• Re: F2003: Polymorphic argument association
  • From: Reinhold Bader
• Re: Fortran array optimizations
  • From: Jan Vorbrüggen
• Re: Passing pointers to subroutines in other modules
  • From: Gib Bogle
• Re: Sun Studio Express 3 compilers available for download
  • From: robert . corbett
• Re: intent attribute
  • From: glen herrmannsfeldt
• Re: intent attribute
  • From: Richard Maine
• Re: F2003: Polymorphic argument association
  • From: Richard Maine
• g77 t shirt
  • From: Greg Lindahl
• Re: intent attribute
  • From: Steve Lionel
• intent attribute
  • From: Roman S.
• Re: Fortran array optimizations
  • From: Steve Lionel
• Re: Fortran array optimizations
  • From: Steven G. Kargl
• Re: Fortran array optimizations
  • From: Greg Lindahl
• F2003: Polymorphic argument association
  • From: Reinhold Bader
• Re: Fortran array optimizations
  • From: highegg
• Re: Fortran array optimizations
  • From: Paul van Delst
• Re: Fortran array optimizations
  • From: Greg Lindahl
• Re: Fortran array optimizations
  • From: Steven G. Kargl
• Re: Fortran array optimizations
  • From: Craig Powers
• Re: Fortran array optimizations
  • From: highegg
• Re: Fortran array optimizations
  • From: Beliavsky
• Re: Fortran array optimizations
  • From: Greg Lindahl
• Re: Fortran array optimizations
  • From: Richard Maine
• Re: Fortran array optimizations
  • From: highegg
• Re: Fortran array optimizations
  • From: highegg
• Re: Fortran array optimizations
  • From: Beliavsky
• Re: Passing pointers to subroutines in other modules
  • From: Richard Maine
• Passing pointers to subroutines in other modules
  • From: Håkan Lane
• Re: Fortran array optimizations
  • From: Richard Maine
• Re: Fortran array optimizations
  • From: Beliavsky
• Fortran array optimizations
  • From: highegg
• Re: dummy argument assumed-size
  • From: Joost
• Re: dummy argument assumed-size
  • From: Steve Lionel
• Re: flop counter
  • From: Alfredo Buttari
• Re: flop counter
  • From: Arjen Markus
• Re: TRANSFER Function on pgf95 6.2-5 64-bit
  • From: PJH
• Re: flop counter
  • From: Pietro
• Re: dummy argument assumed-size
  • From: Pietro
• Re: Multiple declaration support in HP-FORTRAN compiler
  • From: Walter Spector
• Re: TRANSFER Function on pgf95 6.2-5 64-bit
  • From: mm148881
• Re: TRANSFER Function on pgf95 6.2-5 64-bit
  • From: Michael Metcalf
• TRANSFER Function on pgf95 6.2-5 64-bit
  • From: mm148881
• Re: fortran programs with big RAM requirement
  • From: Dr Ivan D. Reid
• Re: Bit Concatenation
  • From: Dr Ivan D. Reid
• Re: Bit Concatenation
  • From: glen herrmannsfeldt
• Re: Bit Concatenation
  • From: Richard Maine
• Re: Bit Concatenation
  • From: Gary Scott
• Re: Gfortran 2006 Year End Status Report
  • From: Steven G. Kargl
• Re: Bit Concatenation
  • From: glen herrmannsfeldt
• Re: Bit Concatenation
  • From: robin
• Re: Bit Concatenation
  • From: robin
• Re: Gfortran 2006 Year End Status Report
  • From: Richard Maine
• Re: Gfortran 2006 Year End Status Report
  • From: Brooks Moses
• Re: Multiple declaration support in HP-FORTRAN compiler
  • From: Steve Lionel
• Re: Multiple declaration support in HP-FORTRAN compiler
  • From: Jim
• Re: Multiple declaration support in HP-FORTRAN compiler
  • From: Greg Lindahl
• Re: fortran programs with big RAM requirement
  • From: Greg Lindahl
• Re: fortran programs with big RAM requirement
  • From: Herman D . Knoble
• Re: Sun Studio Express 3 compilers available for download
  • From: Dick Hendrickson
• Re: fortran programs with big RAM requirement
  • From: antonioparodi74@xxxxxxxxx
• Re: Multiple declaration support in HP-FORTRAN compiler
  • From: Dick Hendrickson
• Re: Multiple declaration support in HP-FORTRAN compiler
  • From: Gordon Sande
• Re: Multiple declaration support in HP-FORTRAN compiler
  • From: Steve Lionel
• Re: Multiple declaration support in HP-FORTRAN compiler
  • From: Tim Prince
• Re: Multiple declaration support in HP-FORTRAN compiler
  • From: Beliavsky
• Re: Weird behaviour with intent
  • From: paul . richard . thomas
• Re: Sun Studio Express 3 compilers available for download
  • From: Keith Refson
• Re: Sun Studio Express 3 compilers available for download
  • From: Keith Refson
• Re: Multiple declaration support in HP-FORTRAN compiler
  • From: Devendra
• Re: Weird behaviour with intent
  • From: jellby
• Re: Multiple declaration support in HP-FORTRAN compiler
  • From: Greg Lindahl
• Re: gfortran and cpp
  • From: glen herrmannsfeldt
• Re: gfortran and cpp
  • From: Steven G. Kargl
• Re: gfortran and cpp
  • From: glen herrmannsfeldt
• Re: Multiple declaration support in HP-FORTRAN compiler
  • From: Colin Watters
• Multiple declaration support in HP-FORTRAN compiler
  • From: Devendra
• Re: gfortran and cpp
  • From: Brooks Moses
• Re: gfortran on old machines
  • From: Kamaraju Kusumanchi
• Re: gfortran on old machines
  • From: Thomas Koenig
• Re: Sun Studio Express 3 compilers available for download
  • From: Greg Lindahl
• Re: Weird behaviour with intent
  • From: Greg Lindahl
• Re: Gfortran 2006 Year End Status Report
  • From: Steven G. Kargl
• Re: Gfortran 2006 Year End Status Report
  • From: Greg Lindahl
• Re: Sun Studio Express 3 compilers available for download
  • From: Dick Hendrickson
• Re: Gfortran 2006 Year End Status Report
  • From: Steven G. Kargl
• Re: Gfortran 2006 Year End Status Report
  • From: ejko123
• Re: Sun Studio Express 3 compilers available for download
  • From: ejko123
• Re: A problem to read a SEG-file using Fortran90 code on PC
  • From: Reginald Beardsley
• Re: Weird behaviour with intent
  • From: Richard E Maine
• Re: Allocation interoperability (Fortran/C)
  • From: Reginald Beardsley
• Re: Weird behaviour with intent
  • From: Dick Hendrickson
• Re: gfortran on old machines
  • From: Kamaraju Kusumanchi
• Re: Allowed return codes from SYSTEM call in ifort/linux.
  • From: Pierre Asselin
• Re: Gfortran 2006 Year End Status Report
  • From: Bil Kleb
• Re: Weird behaviour with intent
  • From: Gordon Sande
• Re: Weird behaviour with intent
  • From: Herman D . Knoble
• Re: Gfortran 2006 Year End Status Report
  • From: Keith Refson
• Re: Weird behaviour with intent
  • From: glen herrmannsfeldt
• Re: Weird behaviour with intent
  • From: Joost
• Weird behaviour with intent
  • From: jellby
• Re: Gfortran 2006 Year End Status Report
  • From: Joost
• Re: fortran programs with big RAM requirement
  • From: Johan
• Re: HELP!How to recover .f file from exsting .o or bin file?
  • From: celeia
• Re: Gfortran 2006 Year End Status Report
  • From: Richard Maine
• Re: Gfortran 2006 Year End Status Report
  • From: glen herrmannsfeldt
• Re: Gfortran 2006 Year End Status Report
  • From: Steven G. Kargl
• Re: gfortran and cpp
  • From: Fly Away
• Re: Gfortran 2006 Year End Status Report
  • From: Richard E Maine
• Re: Gfortran 2006 Year End Status Report
  • From: Greg Lindahl
• Re: gfortran and cpp
  • From: Richard E Maine
• Re: Gfortran 2006 Year End Status Report
  • From: Richard E Maine
• Re: Gfortran 2006 Year End Status Report
  • From: Steven G. Kargl
• Re: Gfortran 2006 Year End Status Report
  • From: awgreynolds
• gfortran and cpp
  • From: Fly Away
• Re: avoiding writing an interface blocks
  • From: glen herrmannsfeldt
• Re: gfortran on old machines
  • From: Thomas Koenig
• Re: avoiding writing an interface blocks
  • From: Dave Thompson
• Re: fortran programs with big RAM requirement
  • From: Greg Lindahl
• Re: fortran programs with big RAM requirement
  • From: Steve Lionel
• Re: fortran programs with big RAM requirement
  • From: Jim
• fortran programs with big RAM requirement
  • From: hyperion
• Re: Gfortran 2006 Year End Status Report
  • From: Steven G. Kargl
• Re: Gfortran 2006 Year End Status Report
  • From: Steven G. Kargl
• Re: Gfortran 2006 Year End Status Report
  • From: ejko123
• Re: Allowed return codes from SYSTEM call in ifort/linux.
  • From: Ron Shepard
• Re: Allowed return codes from SYSTEM call in ifort/linux.
  • From: Keith Refson
• Re: Allowed return codes from SYSTEM call in ifort/linux.
  • From: Pierre Asselin
• Re: Allowed return codes from SYSTEM call in ifort/linux.
  • From: George Trojan
• Re: xlf AIX compiler for files with .f and .f90 suffix
  • From: Bil Kleb
• Re: allocation error
  • From: Herman D . Knoble
• Re: xlf AIX compiler for files with .f and .f90 suffix
  • From: Bil Kleb
• Allowed return codes from SYSTEM call in ifort/linux.
  • From: Keith Refson
• Re: Gfortran 2006 Year End Status Report
  • From: Keith Refson
• Re: [slightly OT] Fortran and gnu autoheader
  • From: John
• Re: Fortran and gnu autoheader
  • From: Brooks Moses
• Re: [slightly OT] Fortran and gnu autoheader
  • From: Brooks Moses
• Re: Distance Transform , Skeletonization , Binary Image
  • From: Sharad
• Re: Disappointed with Intel
  • From: Tom Micevski
• Re: Fortran and gnu autoheader
  • From: John
• Re: Fortran and gnu autoheader
  • From: John
• Re: Distance Transform , Skeletonization , Binary Image
  • From: Terence
• Re: Distance Transform , Skeletonization , Binary Image
  • From: Sharad
• Re: Bit Concatenation
  • From: Terence
• Re: Distance Transform , Skeletonization , Binary Image
  • From: Terence
• Re: Disappointed with Intel
  • From: Terence
• Re: Bit Concatenation
  • From: glen herrmannsfeldt
• Re: Distance Transform , Skeletonization , Binary Image
  • From: Sharad
• Re: Distance Transform , Skeletonization , Binary Image
  • From: Terence
• Re: allocation error
  • From: John Harper
• Distance Transform , Skeletonization , Binary Image
  • From: Sharad
• Re: gfortran on old machines
  • From: Kamaraju Kusumanchi
• Re: a compiler bug?
  • From: glen herrmannsfeldt
• Re: a compiler bug?
  • From: Craig Powers
• Re: HELP!How to recover .f file from exsting .o or bin file?
  • From: cup
• Re: gfortran on old machines
  • From: Thomas Koenig
• Re: HELP!How to recover .f file from exsting .o or bin file?
  • From: zuying@xxxxxxxxx
• gfortran on old machines
  • From: Kamaraju Kusumanchi
• Re: HELP!How to recover .f file from exsting .o or bin file?
  • From: Dave Seaman
• Re: xlf AIX compiler for files with .f and .f90 suffix
  • From: Dave Seaman
• xlf AIX compiler for files with .f and .f90 suffix
  • From: McKinldj
• Re: HELP!How to recover .f file from exsting .o or bin file?
  • From: Richard Maine
• Re: HELP!How to recover .f file from exsting .o or bin file?
  • From: Kamaraju Kusumanchi
• Re: HELP!How to recover .f file from exsting .o or bin file?
  • From: Dan Nagle
• Re: "Bad DLL calling convention" error
  • From: Craig Powers
• Re: Fortran and gnu autoheader
  • From: Chris Hulbert
• Re: HELP!How to recover .f file from exsting .o or bin file?
  • From: Jim
• Re: HELP!How to recover .f file from exsting .o or bin file?
  • From: Steve Lionel
• Re: Bit Concatenation
  • From: Gordon Sande
• Re: Fortran and gnu autoheader
  • From: SimonG
• [slightly OT] Fortran and gnu autoheader
  • From: John
• HELP!How to recover .f file from exsting .o or bin file?
  • From: zuying@xxxxxxxxx
• Re: F2003: pass disallowed for procedure pointer components?
  • From: Reinhold Bader
• Re: Bit Concatenation
  • From: David Frank
• Re: Expanding memory
  • From: SimonG
• Re: allocation error
  • From: AeroSpace Ed
• Re: Bit Concatenation
  • From: AeroSpace Ed
• Re: Gfortran 2006 Year End Status Report
  • From: Beliavsky
• Gfortran 2006 Year End Status Report
  • From: Steven G. Kargl
• Re: allocation error
  • From: glen herrmannsfeldt
• Re: Disappointed with Intel
  • From: subspace
• Re: allocation error
  • From: lane straatman
• Re: Generic Functions
  • From: glen herrmannsfeldt
• Re: Bit Concatenation
  • From: glen herrmannsfeldt
• Re: Bit Concatenation
  • From: Richard Maine
• Re: Bit Concatenation
  • From: Terence
• Re: Bit Concatenation
  • From: Terence
• Re: Expanding memory
  • From: paul . richard . thomas
• Re: Is Katherine Trimble an envy racist bigot?
  • From: ttw
• Re: Generic Functions
  • From: Ron Shepard
• Re: Expanding memory
  • From: Richard Maine
• Re: Expanding memory
  • From: Johan
• Expanding memory
  • From: SimonG
• Re: Generic Functions
  • From: Dan Nagle
• Is Katherine Trimble an envy racist bigot?
  • From: destroyallenvy
• Re: Generic Functions
  • From: Dick Hendrickson
• Re: Bit Concatenation
  • From: AeroSpace Ed
• Re: Generic Functions
  • From: Richard Maine
• Re: allocation error
  • From: glen herrmannsfeldt
• Re: Generic Functions
  • From: PJH
• Re: Bit Concatenation
  • From: Terence
• Re: Generic Functions
  • From: Richard Maine
• Re: Generic Functions
  • From: PJH
• Re: Fortran Preprocessor?
  • From: Dan Nagle
• Re: Reading data
  • From: Richard Maine
• Re: Generic Functions
  • From: Richard Maine
• Re: Reading data
  • From: dpb
• Re: Generic Functions
  • From: Beliavsky
• Re: Fortran Preprocessor?
  • From: Timothy Patrick Gallagher
• Generic Functions
  • From: PJH
• Re: Fortran Preprocessor?
  • From: Ron Shepard
• Re: Fortran Preprocessor?
  • From: Richard Maine
• Re: Fortran Preprocessor?
  • From: Dan Nagle
• Re: Fortran Preprocessor?
  • From: Tim Prince
• Re: Fortran Preprocessor?
  • From: Steve Lionel
• Re: Fortran Preprocessor?
  • From: Tim Prince
• Re: Fortran Preprocessor?
  • From: Beliavsky
• Fortran Preprocessor?
  • From: Timothy Patrick Gallagher
• RE: Getting the decimal points to line up!
  • From: meek

• Security
• UNIX
• Linux
• Coding
• Usenet

• Archive
• About
• Privacy
• Search
• Imprint

coding.derkeiler.com  > Archive  > Fortran  > comp.lang.fortran  > 2007-01