comp.lang.fortran

• Thread Index

---

• Re: Reading data
  • From: hhu
• Re: Reading data
  • From: Beliavsky
• Re: allocation error
  • From: AeroSpace Ed
• Re: Reading data
  • From: hhu
• Re: Reading data
  • From: mecej4
• Re: Reading data
  • From: Richard Maine
• Re: Disappointed with Intel
  • From: AeroSpace Ed
• Re: Bit Concatenation
  • From: robin
• Re: allocation error
  • From: robin
• Re: Reading data
  • From: Beliavsky
• Reading data
  • From: hhu
• Re: generating win32 exe on linux platform
  • From: Jean Baptiste Faure
• Re: OT: Disappointed with Intel
  • From: Terence
• Re: allocation error
  • From: Beliavsky
• Re: Proper way to return a string
  • From: Walter Spector
• Re: allocation error
  • From: lane straatman
• Re: Proper way to return a string
  • From: Richard Maine
• Re: Proper way to return a string
  • From: Steven G. Kargl
• Re: Proper way to return a string
  • From: Steven G. Kargl
• Re: Proper way to return a string
  • From: Richard Maine
• Re: Proper way to return a string
  • From: Walter Spector
• Re: Proper way to return a string
  • From: David Frank
• Re: Proper way to return a string
  • From: David Frank
• Re: Proper way to return a string
  • From: Richard Maine
• Re: Proper way to return a string
  • From: Walter Spector
• Re: Proper way to return a string
  • From: Ron Shepard
• Re: Proper way to return a string
  • From: Steven G. Kargl
• Re: Proper way to return a string
  • From: Walter Spector
• Re: Proper way to return a string
  • From: Rich Townsend
• Re: Is there any problem with the following program?
  • From: Rich Townsend
• Re: Is there any problem with the following program?
  • From: Tim Prince
• Re: Is there any problem with the following program?
  • From: Beliavsky
• Re: Proper way to return a string
  • From: Beliavsky
• Is there any problem with the following program?
  • From: zhngbn
• Re: OT: Disappointed with Intel and Polyhedron
  • From: Steve Lionel
• Re: OT: Disappointed with Intel and Polyhedron
  • From: Gary Scott
• Re: OT: Disappointed with Intel and Polyhedron
  • From: Rich Townsend
• Re: OT: Disappointed with Intel and Polyhedron
  • From: Terence
• Re: allocation error
  • From: Beliavsky
• Disappointed with Intel
  • From: Terence
• Re: allocation error
  • From: Terence
• Re: OT: Disappointed with Intel and Polyhedron
  • From: Gary Scott
• Re: OT: Disappointed with Intel and Polyhedron
  • From: Steve Lionel
• Re: allocation error
  • From: dpb
• Re: OT: Disappointed with Intel and Polyhedron
  • From: Terence
• Re: How to transfer a file in an array
  • From: Jean-Charles
• Re: allocation error
  • From: Richard Maine
• Re: allocation error
  • From: Rich Townsend
• Re: allocation error
  • From: dpb
• Re: allocation error
  • From: Beliavsky
• Re: allocation error
  • From: dpb
• Re: allocation error
  • From: Richard Maine
• allocation error
  • From: lane straatman
• Re: flop counter
  • From: Richard Maine
• Re: dummy argument assumed-size
  • From: Gordon Sande
• Re: dummy argument assumed-size
  • From: Steve Lionel
• flop counter
  • From: Pietro
• Re: dummy argument assumed-size
  • From: Pietro
• Re: Bit Concatenation
  • From: David Frank
• Re: OT: Disappointed with Intel and Polyhedron
  • From: Alex Gibson
• Re: Sun Studio Express 3 compilers available for download
  • From: Greg Lindahl
• Re: Bit Concatenation
  • From: Gary Scott
• Re: Problem with my split routine I am not understanding
  • From: Richard E Maine
• Re: Proper way to return a string
  • From: Terence
• Re: How to transfer a file in an array
  • From: Terence
• Re: Problem with my split routine I am not understanding
  • From: Donald Fredkin
• How to transfer a file in an array
  • From: Jean-Charles
• Re: How to transfer a file in an array
  • From: Ancient_Hacker
• Re: Problem with my split routine I am not understanding
  • From: Jeremy
• Re: Problem with my split routine I am not understanding
  • From: Dick Hendrickson
• Re: Problem with my split routine I am not understanding
  • From: Beliavsky
• Re: Proper way to return a string
  • From: Richard E Maine
• Problem with my split routine I am not understanding
  • From: Jeremy
• Re: Proper way to return a string
  • From: Paul van Delst
• Re: dummy argument assumed-size
  • From: Richard E Maine
• Re: Bit Concatenation
  • From: Dan Nagle
• Re: F2003: pass disallowed for procedure pointer components?
  • From: Richard E Maine
• Re: dummy argument assumed-size
  • From: Pietro
• Re: Proper way to return a string
  • From: Richard E Maine
• Re: Proper way to return a string
  • From: Richard E Maine
• Re: internal I/O to substring
  • From: Richard E Maine
• F2003: pass disallowed for procedure pointer components?
  • From: Reinhold Bader
• Re: Dimension attribute based on host-associated variable - bug in Intel Fortran
  • From: Steve Lionel
• Re: Dimension attribute based on host-associated variable - bug in Intel Fortran
  • From: Arjen Markus
• Re: Dimension attribute based on host-associated variable - bug in Intel Fortran
  • From: Rich Townsend
• Re: Dimension attribute based on host-associated variable - bug in Intel Fortran
  • From: David Frank
• Re: Write A, left justified, howto?
  • From: Dick Russell
• Re: Write A, left justified, howto?
  • From: Dick Russell
• Re: Dimension attribute based on host-associated variable - bug in Intel Fortran
  • From: Arjen Markus
• Re: Dimension attribute based on host-associated variable - bug in Intel Fortran
  • From: David Frank
• Re: Write A, left justified, howto?
  • From: Arjen Markus
• Write A, left justified, howto?
  • From: Jeremy
• Re: General Subroutine Error
  • From: Steven G. Kargl
• General Subroutine Error
  • From: rjmagyar
• Re: Proper way to return a string
  • From: e p chandler
• Dimension attribute based on host-associated variable - bug in Intel Fortran
  • From: Rich Townsend
• Re: Proper way to return a string
  • From: Ron Shepard
• Re: Proper way to return a string
  • From: Terence
• Re: one element in the inverse matrix
  • From: yuanliu1
• Re: Okular-Infos -
  • From: Hani Andreas Ibrahim
• Okular-Infos
  • From: Hani Andreas Ibrahim
• Re: Proper way to return a string
  • From: Steven G. Kargl
• Re: Proper way to return a string
  • From: Ron Shepard
• Re: Proper way to return a string
  • From: Gordon Sande
• Re: Proper way to return a string
  • From: Steven G. Kargl
• Re: READ and delimited format
  • From: Dan Nagle
• Proper way to return a string
  • From: Jeremy
• Re: Converting string to Integer, Real, etc...
  • From: dpb
• Re: READ and delimited format
  • From: Dan Nagle
• Re: READ and delimited format
  • From: dpb
• Re: Converting string to Integer, Real, etc...
  • From: Beliavsky
• Re: Converting string to Integer, Real, etc...
  • From: Dick Hendrickson
• Re: Converting string to Integer, Real, etc...
  • From: dpb
• Re: Converting string to Integer, Real, etc...
  • From: Paul van Delst
• Re: READ and delimited format
  • From: Beliavsky
• Converting string to Integer, Real, etc...
  • From: Jeremy
• READ and delimited format
  • From: Jeremy
• Re: printing in fortran
  • From: Dave Thompson
• Re: defining an arbitrary type in your newer Fortrans
  • From: Dave Thompson
• Re: Popularity contests
  • From: Dave Thompson
• Re: (very) slow recursive function
  • From: robin
• Re: Bit Concatenation
  • From: robin
• Re: (very) slow recursive function
  • From: robin
• Re: book to obviate a grab bag of forum questions
  • From: Terence
• book to obviate a grab bag of forum questions
  • From: lane straatman
• Re: the efficiency of STRUCTURE on SGI IRIX
  • From: dpb
• Re: the efficiency of STRUCTURE on SGI IRIX
  • From: Tim Prince
• Re: the efficiency of STRUCTURE on SGI IRIX
  • From: zuying@xxxxxxxxx
• Re: the efficiency of STRUCTURE on SGI IRIX
  • From: gary . l . scott
• Re: one element in the inverse matrix
  • From: NuclearWizard
• Re: the efficiency of STRUCTURE on SGI IRIX
  • From: Tim Prince
• Re: the efficiency of STRUCTURE on SGI IRIX
  • From: Walter Spector
• Re: the efficiency of STRUCTURE on SGI IRIX
  • From: gary . l . scott
• Re: the efficiency of STRUCTURE on SGI IRIX
  • From: dpb
• the efficiency of STRUCTURE on SGI IRIX
  • From: Nye
• Re: one element in the inverse matrix
  • From: Ron Shepard
• Re: one element in the inverse matrix
  • From: Terence
• Re: one element in the inverse matrix
  • From: yuanliu1
• Re: one element in the inverse matrix
  • From: Ron Shepard
• Re: one element in the inverse matrix
  • From: yuanliu1
• Re: "Bad DLL calling convention" error
  • From: Athena
• Re: "Bad DLL calling convention" error
  • From: PJH
• "Bad DLL calling convention" error
  • From: Athena
• Re: one element in the inverse matrix
  • From: Gordon Sande
• Re: Bit Concatenation
  • From: PJH
• Re: Bit Concatenation
  • From: David Frank
• Re: internal I/O to substring
  • From: Steve Lionel
• Re: generating win32 exe on linux platform
  • From: glen herrmannsfeldt
• Re: generating win32 exe on linux platform
  • From: Tim Prince
• Re: one element in the inverse matrix
  • From: yuanliu1
• Re: Sun Studio Express 3 compilers available (new URL)
  • From: robert . corbett
• Re: Bit Concatenation
  • From: Terence
• Re: gfortran Google Group
  • From: Beliavsky
• Re: gfortran Google Group
  • From: Fly Away
• gfortran Google Group
  • From: Beliavsky
• Re: Bit Concatenation
  • From: Dan Nagle
• Re: Bit Concatenation
  • From: PJH
• Re: Bit Concatenation
  • From: Dick Hendrickson
• Re: generating win32 exe on linux platform
  • From: glen herrmannsfeldt
• Re: Machine/Compiler Independent Results
  • From: widmar
• Re: internal I/O to substring
  • From: analyst41
• generating win32 exe on linux platform
  • From: Jean Baptiste Faure
• Re: Bit Concatenation
  • From: Gary Scott
• Re: Bit Concatenation
  • From: PJH
• Re: Bit Concatenation
  • From: glen herrmannsfeldt
• Re: Bit Concatenation
  • From: Gary Scott
• Bit Concatenation
  • From: PJH
• internal I/O to substring
  • From: Thomas Koenig
• Re: one element in the inverse matrix
  • From: glen herrmannsfeldt
• Re: include file problem
  • From: allelopath
• Re: include file problem
  • From: AeroSpace Ed
• include file problem
  • From: allelopath
• Re: Sun Studio Express 3 compilers available (new URL)
  • From: Daniel Franke
• Re: Sun Studio Express 3 compilers available for download
  • From: Bil Kleb
• Re: Sun Studio Express 3 compilers available (new URL)
  • From: Bil Kleb
• Re: Sun Studio Express 3 compilers available (new URL)
  • From: Daniel Franke
• Re: Machine/Compiler Independent Results
  • From: David Frank
• Re: Machine/Compiler Independent Results
  • From: glen herrmannsfeldt
• Re: Machine/Compiler Independent Results
  • From: Arjen Markus
• Re: Sun Studio Express 3 compilers available for download
  • From: robert . corbett
• Re: Sun Studio Express 3 compilers available for download
  • From: robert . corbett
• Re: Sun Studio Express 3 compilers available for download
  • From: Gary Scott
• Re: Sun Studio Express 3 compilers available for download
  • From: Bil Kleb
• Re: one element in the inverse matrix
  • From: Pierre Asselin
• Re: Machine/Compiler Independent Results
  • From: glen herrmannsfeldt
• Re: Machine/Compiler Independent Results
  • From: Steven G. Kargl
• Re: one element in the inverse matrix
  • From: glen herrmannsfeldt
• Re: Machine/Compiler Independent Results
  • From: John Harper
• Re: one element in the inverse matrix
  • From: glen herrmannsfeldt
• Re: Sun Studio Express 3 compilers available (new URL)
  • From: robert . corbett
• Re: Sun Studio Express 3 compilers available for download
  • From: robert . corbett
• Re: one element in the inverse matrix
  • From: Gordon Sande
• Re: one element in the inverse matrix
  • From: glen herrmannsfeldt
• Re: Machine/Compiler Independent Results
  • From: Greg Lindahl
• Re: Sun Studio Express 3 compilers available for download
  • From: robert . corbett
• one element in the inverse matrix
  • From: yuanliu1
• Re: Machine/Compiler Independent Results
  • From: glen herrmannsfeldt
• Re: Sun Studio Express 3 compilers available for download
  • From: robert . corbett
• Re: Machine/Compiler Independent Results
  • From: John Harper
• Re: OT: Disappointed with Intel and Polyhedron
  • From: John Harper
• Re: OT: Disappointed with Intel and Polyhedron
  • From: Terence
• Re: Machine/Compiler Independent Results
  • From: glen herrmannsfeldt
• Re: Machine/Compiler Independent Results
  • From: Steven G. Kargl
• Re: Machine/Compiler Independent Results
  • From: John Harper
• Re: OT: Disappointed with Intel and Polyhedron
  • From: paul . richard . thomas
• Re: Machine/Compiler Independent Results
  • From: Gordon Sande
• Re: Machine/Compiler Independent Results
  • From: glen herrmannsfeldt
• Re: Machine/Compiler Independent Results
  • From: glen herrmannsfeldt
• Re: dummy argument assumed-size
  • From: Jugoslav Dujic
• Re: dummy argument assumed-size
  • From: Steve Lionel
• Re: Sun Studio Express 3 compilers available for download
  • From: Keith Refson
• dummy argument assumed-size
  • From: Pietro
• Re: OT: Disappointed with Intel and Polyhedron
  • From: Steve Lionel
• Re: OT: Disappointed with Intel and Polyhedron
  • From: Steve Lionel
• Re: OT: Disappointed with Intel and Polyhedron
  • From: Beliavsky
• Re: Machine/Compiler Independent Results
  • From: Arjen Markus
• Re: Machine/Compiler Independent Results
  • From: Dan Nagle
• Re: Machine/Compiler Independent Results
  • From: Arjen Markus
• Re: OT: Disappointed with Intel and Polyhedron
  • From: John Appleyard
• Re: Machine/Compiler Independent Results
  • From: Jan Vorbrüggen
• Re: Machine/Compiler Independent Results
  • From: Joost
• Re: LEN_TRIM performance issue
  • From: Ron Shepard
• Re: OT: Disappointed with Intel and Polyhedron
  • From: Terence
• Re: a compiler bug?
  • From: Jerry DeLisle
• Machine/Compiler Independent Results
  • From: Bil Kleb
• Procedure Argument/External
  • From: Gary Scott
• Re: a compiler bug?
  • From: Chris Hulbert
• OT: Disappointed with Intel and Polyhedron
  • From: Dr Ivan D. Reid
• Re: a compiler bug?
  • From: George Trojan
• Re: Sun Studio Express 3 compilers available for download
  • From: Beliavsky
• Re: Sun Studio Express 3 compilers available for download
  • From: cup
• Re: a compiler bug?
  • From: Dan Nagle
• Re: a compiler bug?
  • From: Beliavsky
• a compiler bug?
  • From: George Trojan
• Re: LEN_TRIM performance issue
  • From: glen herrmannsfeldt
• Re: avoiding writing an interface blocks
  • From: glen herrmannsfeldt
• Re: LEN_TRIM performance issue
  • From: Richard E Maine
• Re: LEN_TRIM performance issue
  • From: Ancient_Hacker
• Re: avoiding writing an interface blocks
  • From: David Frank
• Re: LEN_TRIM performance issue
  • From: Dick Hendrickson
• Re: LEN_TRIM performance issue
  • From: Gordon Sande
• Re: LEN_TRIM performance issue
  • From: gary . l . scott
• Re: avoiding writing an interface blocks
  • From: Kamaraju Kusumanchi
• Re: Sun Studio Express 3 compilers available for download
  • From: Sebastian Hanigk
• Re: avoiding writing an interface blocks
  • From: Kamaraju Kusumanchi
• Re: LEN_TRIM performance issue
  • From: olof . liungman
• Re: Sun Studio Express 3 compilers available for download
  • From: Bil Kleb
• Re: avoiding writing an interface blocks
  • From: Herman D . Knoble
• Re: Sun Studio Express 3 compilers available for download
  • From: Beliavsky
• Re: avoiding writing an interface blocks
  • From: deltaquattro
• Re: Object oriented programming in Fortran 95
  • From: PJH
• Sun Studio Express 3 compilers available for download
  • From: robert . corbett
• Re: avoiding writing an interface blocks
  • From: Kamaraju Kusumanchi
• Re: avoiding writing an interface blocks
  • From: glen herrmannsfeldt
• Re: f2003 - abstract types and abstract interfaces
  • From: Richard E Maine
• Re: avoiding writing an interface blocks
  • From: Richard E Maine
• Re: f2003 - abstract types and abstract interfaces
  • From: Norman S. Clerman
• Re: avoiding writing an interface blocks
  • From: Dan Nagle
• Re: avoiding writing an interface blocks
  • From: Kamaraju Kusumanchi
• Re: avoiding writing an interface blocks
  • From: Kamaraju Kusumanchi
• Re: avoiding writing an interface blocks
  • From: Kamaraju Kusumanchi
• Re: LEN_TRIM performance issue
  • From: glen herrmannsfeldt
• Re: avoiding writing an interface blocks
  • From: glen herrmannsfeldt
• Re: Generics with alternate-return arguments?
  • From: James Giles
• Re: F2003: creating polymorphic entities
  • From: Reinhold Bader
• Re: Generics with alternate-return arguments?
  • From: Richard E Maine
• Re: F2003: creating polymorphic entities
  • From: Richard E Maine
• Re: LEN_TRIM performance issue
  • From: dpb
• Re: avoiding writing an interface blocks
  • From: Richard E Maine
• Re: avoiding writing an interface blocks
  • From: Richard E Maine
• Re: F2003: creating polymorphic entities
  • From: Brooks Moses
• Re: Generics with alternate-return arguments?
  • From: Brooks Moses
• Re: SEQUENCE
  • From: paul . richard . thomas
• Re: LEN_TRIM performance issue
  • From: glen herrmannsfeldt
• Re: avoiding writing an interface blocks
  • From: glen herrmannsfeldt
• Re: LEN_TRIM performance issue
  • From: James Giles
• Re: Generics with alternate-return arguments?
  • From: James Giles
• Re: Save statement
  • From: allelopath
• Re: LEN_TRIM performance issue
  • From: Jugoslav Dujic
• F2003: creating polymorphic entities
  • From: Reinhold Bader
• Re: Object oriented programming in Fortran 95
  • From: Beliavsky
• Re: LEN_TRIM performance issue
  • From: Gary Scott
• Re: SEQUENCE
  • From: Jan Vorbrüggen
• Re: f2003 - abstract types and abstract interfaces
  • From: Michael Metcalf
• Re: Generics with alternate-return arguments?
  • From: Michael Metcalf
• Re: avoiding writing an interface blocks
  • From: Dan Nagle
• Re: avoiding writing an interface blocks
  • From: Richard E Maine
• Fortran Programmers Club
  • From: news.donpac.ru
• Re: Object oriented programming in Fortran 95
  • From: deltaquattro
• Re: Performance trouble
  • From: fj
• LEN_TRIM performance issue
  • From: olof . liungman
• Re: avoiding writing an interface blocks
  • From: Alois Steindl
• [OT] Fortran Forum new issue
  • From: Tim Prince
• Re: SEQUENCE
  • From: Gary Scott
• Re: SEQUENCE
  • From: Gary Scott
• Re: Generics with alternate-return arguments?
  • From: Brooks Moses
• Re: SEQUENCE
  • From: glen herrmannsfeldt
• Re: SEQUENCE
  • From: Steve Lionel
• avoiding writing an interface blocks
  • From: Kamaraju Kusumanchi
• Re: SEQUENCE
  • From: Dan Nagle
• Re: SEQUENCE
  • From: gary . l . scott
• Re: Is there an Eclipse plug-in for gfortran or g95 under cygwin?
  • From: Dan Nagle
• Is there an Eclipse plug-in for gfortran or g95 under cygwin?
  • From: Dr Ivan D. Reid
• Re: SEQUENCE
  • From: Richard E Maine
• Re: SEQUENCE
  • From: Paul van Delst
• Re: Performance trouble
  • From: dpb
• Re: SEQUENCE
  • From: Craig Powers
• Re: SEQUENCE
  • From: Michael Metcalf
• Re: Fortran UUID Generator
  • From: max
• SEQUENCE
  • From: gary . l . scott
• Re: Summary of F2003 features supported in each compiler
  • From: Rich Townsend
• Re: Summary of F2003 features supported in each compiler
  • From: Steve Lionel
• Re: herding global vars to a module
  • From: lane straatman
• Re: Knuth: Linear Congruential Method
  • From: Craig Powers
• Re: Two simple questions
  • From: Paul van Delst
• Re: Performance trouble
  • From: fj
• Re: Getting the decimal points to line up!
  • From: Dick Hendrickson
• Re: cputime
  • From: Tim Prince
• Re: cputime
  • From: Dan Nagle
• Re: Performance trouble
  • From: dpb
• Re: Installing g95
  • From: Michael Prager
• Re: Performance trouble
  • From: Tim Prince
• Re: Object oriented programming in Fortran 95
  • From: Beliavsky
• Re: cputime
  • From: Beliavsky
• cputime
  • From: Padiyath sREEKUMAR
• Performance trouble
  • From: fj
• Re: Generics with alternate-return arguments?
  • From: Michael Metcalf
• Object oriented programming in Fortran 95
  • From: deltaquattro
• Re: f2003 - abstract types and abstract interfaces
  • From: Reinhold Bader
• Re: Getting the decimal points to line up!
  • From: glen herrmannsfeldt
• Re: Save statement
  • From: glen herrmannsfeldt
• Re: Generics with alternate-return arguments?
  • From: paul . richard . thomas
• Re: Generics with alternate-return arguments?
  • From: Brooks Moses
• f2003 - abstract types and abstract interfaces
  • From: Norman S. Clerman
• Re: Getting the decimal points to line up!
  • From: James Giles
• Re: Getting the decimal points to line up!
  • From: Gary Scott
• Re: allocated array
  • From: Gary Scott
• Re: Fortran UUID Generator
  • From: Gary Scott
• Re: Getting the decimal points to line up!
  • From: John Harper
• Re: Getting the decimal points to line up!
  • From: Dick Hendrickson
• Re: PGI Visual Fortran
  • From: Dick Hendrickson
• Re: Save statement
  • From: Richard E Maine
• Re: allocated array
  • From: Richard E Maine
• Re: basic Fortran info
  • From: Steven G. Kargl
• Re: basic Fortran info
  • From: Michael Metcalf
• Re: Save statement
  • From: allelopath
• basic Fortran info
  • From: markww
• Re: Fortran UUID Generator
  • From: PJH
• Re: Save statement
  • From: Steve Lionel
• Re: Fortran UUID Generator
  • From: max
• Re: Fortran UUID Generator
  • From: PJH
• Re: Fortran UUID Generator
  • From: Terence
• Re: Save statement
  • From: Beliavsky
• Re: Save statement
  • From: jwm
• Re: Save statement
  • From: allelopath
• Fortran UUID Generator
  • From: PJH
• Re: Save statement
  • From: jwm
• Re: Save statement
  • From: allelopath
• Re: allocated array
  • From: Gary Scott
• Re: Generics with alternate-return arguments?
  • From: paul . richard . thomas
• Re: Two simple questions
  • From: Dick Hendrickson
• Re: allocated array
  • From: Dick Hendrickson
• Re: Generics with alternate-return arguments?
  • From: Michael Metcalf
• Re: Generics with alternate-return arguments?
  • From: David Frank
• Re: Getting the decimal points to line up!
  • From: glen herrmannsfeldt
• Re: herding global vars to a module
  • From: Brooks Moses
• Generics with alternate-return arguments?
  • From: Brooks Moses
• Re: Getting the decimal points to line up!
  • From: Richard E Maine
• Re: herding global vars to a module
  • From: Michael Metcalf
• Re: herding global vars to a module
  • From: Terence
• Re: Getting the decimal points to line up!
  • From: glen herrmannsfeldt
• Re: Two simple questions
  • From: Terence
• Re: herding global vars to a module
  • From: lane straatman
• Re: Getting the decimal points to line up!
  • From: Richard E Maine
• Re: herding global vars to a module
  • From: Michael Metcalf
• Re: Two simple questions
  • From: Paul van Delst
• Re: allocated array
  • From: Paul van Delst
• herding global vars to a module
  • From: lane straatman
• Two simple questions
  • From: alan . lemon
• Re: Getting the decimal points to line up!
  • From: glen herrmannsfeldt
• Re: allocated array
  • From: Beliavsky
• Re: Getting the decimal points to line up!
  • From: Terence
• Re: allocated array
  • From: Paul van Delst
• Re: allocated array
  • From: Richard E Maine
• Re: Getting the decimal points to line up!
  • From: Richard E Maine
• Re: Printing large arrays in Fortran
  • From: robin
• Re: fortran give false value !!!
  • From: robin
• Re: check monotony of array values
  • From: robin
• Re: allocated array
  • From: robin
• Re: A problem with READ statement.
  • From: robin
• Re: Knuth: Linear Congruential Method
  • From: robin
• Re: printing in fortran
  • From: robin
• Re: how NOT to program in FORTRAN
  • From: robin
• Re: f90
  • From: robin
• Re: Knuth: Linear Congruential Method
  • From: allelopath
• Re: Knuth: Linear Congruential Method
  • From: allelopath
• Re: Knuth: Linear Congruential Method
  • From: Craig Powers
• Re: Derived type - valued function with pointer member.
  • From: Che Gannarelli
• Re: Getting the decimal points to line up!
  • From: Gordon Sande
• Re: Derived type - valued function with pointer member.
  • From: Paul van Delst
• Getting the decimal points to line up!
  • From: Ancient_Hacker
• Re: Getting the decimal points to line up!
  • From: Michel Olagnon
• Re: Derived type - valued function with pointer member.
  • From: Che Gannarelli
• Re: Save statement
  • From: allelopath
• Re: Allocation interoperability (Fortran/C)
  • From: Anton Haumer
• Re: Knuth: Linear Congruential Method
  • From: allelopath
• Re: allocated array
  • From: Mark Westwood
• Re: Save statement
  • From: allelopath
• RE: Getting the decimal points to line up!
  • From: meek
• Re: allocated array
  • From: Beliavsky
• Re: allocated array
  • From: Sebastian Hanigk
• Re: Derived type - valued function with pointer member.
  • From: Paul van Delst
• Re: Derived type - valued function with pointer member.
  • From: Paul van Delst
• Re: F2K C Interoperability - SIZEOF
  • From: Dick Hendrickson
• Re: Derived type - valued function with pointer member.
  • From: Che Gannarelli
• Getting the decimal points to line up!
  • From: Ancient_Hacker
• Re: allocated array
  • From: Les
• Re: allocated array
  • From: Ancient_Hacker
• Re: Knuth: Linear Congruential Method
  • From: allelopath
• Re: Knuth: Linear Congruential Method
  • From: allelopath
• Re: allocated array
  • From: Paul van Delst
• Re: Save statement
  • From: allelopath
• Re: Installing g95
  • From: Menderes ISKIN
• Re: Derived type - valued function with pointer member.
  • From: Richard E Maine
• Re: Derived type - valued function with pointer member.
  • From: Che Gannarelli
• Re: Allocation interoperability (Fortran/C)
  • From: Sebastian Hanigk
• Re: allocated array
  • From: Beliavsky
• Re: Derived type - valued function with pointer member.
  • From: Jan Vorbrüggen
• Re: Derived type - valued function with pointer member.
  • From: Michael Metcalf
• Re: allocated array
  • From: Michael Metcalf
• Derived type - valued function with pointer member.
  • From: Che Gannarelli
• Re: Allocation interoperability (Fortran/C)
  • From: Jugoslav Dujic
• Re: Save statement
  • From: Jugoslav Dujic
• Re: F2003
  • From: Mehmet Karatay
• Re: F2K C Interoperability - SIZEOF
  • From: Jugoslav Dujic
• Re: allocated array
  • From: Les
• Re: allocated array
  • From: nakisa
• Re: Save statement
  • From: David Flower
• Re: allocated array
  • From: glen herrmannsfeldt
• Re: allocated array
  • From: Steven G. Kargl
• Re: allocated array
  • From: nakisa
• Re: allocated array
  • From: Steven G. Kargl
• Re: allocated array
  • From: robert . corbett
• Re: allocated array
  • From: Brooks Moses
• allocated array
  • From: nakisa
• Re: Save statement
  • From: Jim
• Re: threaded avl trees?!
  • From: Richard E Maine
• Re: how NOT to program in FORTRAN
  • From: Richard E Maine
• Re: F2K C Interoperability - SIZEOF
  • From: Richard E Maine
• Re: IVF and DLLs
  • From: Steve Lionel
• IVF and DLLs
  • From: Kenny Stultz
• Re: F2K C Interoperability - SIZEOF
  • From: Brooks Moses
• Re: Save statement
  • From: Paul van Delst
• Re: F2K C Interoperability - SIZEOF
  • From: Dick Hendrickson
• Re: F2K C Interoperability - SIZEOF
  • From: gary . l . scott
• RE: how NOT to program in FORTRAN
  • From: meek
• Re: F2K C Interoperability - SIZEOF
  • From: Dick Hendrickson
• Re: F2K C Interoperability - SIZEOF
  • From: Dan Nagle
• Re: F2K C Interoperability - SIZEOF
  • From: gary . l . scott
• Re: threaded avl trees?!
  • From: ejko123
• Re: F2K C Interoperability - SIZEOF
  • From: glen herrmannsfeldt
• Re: F2K C Interoperability - SIZEOF
  • From: Richard E Maine
• Re: Save statement
  • From: glen herrmannsfeldt
• F2K C Interoperability - SIZEOF
  • From: gary . l . scott
• Re: Save statement
  • From: Steven G. Kargl
• Re: Save statement
  • From: highegg
• Re: Save statement
  • From: Beliavsky
• Re: Save statement
  • From: allelopath
• Re: how NOT to program in FORTRAN
  • From: Mark Westwood
• Re: Save statement
  • From: Paul van Delst
• Re: Allocation interoperability (Fortran/C)
  • From: Sebastian Hanigk
• Save statement
  • From: allelopath
• how NOT to program in FORTRAN
  • From: Beliavsky
• Re: Allocation interoperability (Fortran/C)
  • From: Richard E Maine
• Re: Allocation interoperability (Fortran/C)
  • From: Sebastian Hanigk
• Re: fortran give false value !!!
  • From: Clive Page
• Re: F2003
  • From: Michael Metcalf
• Re: threaded avl trees?!
  • From: Daniel Franke
• Re: Allocation interoperability (Fortran/C)
  • From: Dan Nagle
• Re: How to deal with a file with binary and formatted blocks at once ?
  • From: Clive Page
• Re: Stack overflow with structured array, why?
  • From: deltaquattro
• Re: Allocation interoperability (Fortran/C)
  • From: Sebastian Hanigk
• Re: Stack overflow with structured array, why?
  • From: deltaquattro
• Re: threaded avl trees?!
  • From: Arjen Markus
• Re: F2003
  • From: Reinhold Bader
• Re: F2003
  • From: Reinhold Bader
• Re: threaded avl trees?!
  • From: Daniel Franke
• Re: Stack overflow with structured array, why?
  • From: Jugoslav Dujic
• Re: gfortran uses four-byte record markers by default
  • From: robert . corbett
• Re: gfortran uses four-byte record markers by default
  • From: Rich Townsend
• Re: gfortran uses four-byte record markers by default
  • From: Terence
• Re: writing in array
  • From: Michael Metcalf
• Re: writing in array
  • From: glen herrmannsfeldt
• Re: writing in array
  • From: Michael Metcalf
• Re: writing in array
  • From: Beliavsky
• Re: Allocation interoperability (Fortran/C)
  • From: Steve Lionel
• Re: gfortran uses four-byte record markers by default
  • From: Thomas Koenig
• Re: code critique wanted
  • From: Craig Powers
• Re: Allocation interoperability (Fortran/C)
  • From: Brooks Moses
• Re: Printing large arrays in Fortran
  • From: Michael Prager
• Re: Allocation interoperability (Fortran/C)
  • From: Joost
• Re: writing in array
  • From: glen herrmannsfeldt
• Re: Printing large arrays in Fortran
  • From: Gordon Sande
• Re: Installing g95
  • From: Michael Prager
• Re: Installing g95
  • From: Michael Prager
• Re: printing in fortran
  • From: lane straatman
• Re: Installing g95
  • From: Beliavsky
• Re: Printing large arrays in Fortran
  • From: Beliavsky
• Re: Power Term serveur...
  • From: rjkematick@xxxxxxxxxxx
• Re: Printing large arrays in Fortran
  • From: Herman D . Knoble
• Re: Installing g95
  • From: Sebastian Gallinat
• Re: Printing large arrays in Fortran
  • From: Michael Prager
• Installing g95
  • From: Mike Prager
• Re: Stack overflow with structured array, why?
  • From: Paul van Delst
• Re: Stack overflow with structured array, why?
  • From: Bernhard Enders
• Re: Printing large arrays in Fortran
  • From: Gordon Sande
• Stack overflow with structured array, why?
  • From: deltaquattro
• Re: Power Term serveur...
  • From: hornblende
• Re: Allocation interoperability (Fortran/C)
  • From: Steve Lionel
• Re: Printing large arrays in Fortran
  • From: Beliavsky
• Re: Knuth: Linear Congruential Method
  • From: allelopath
• Re: code critique wanted
  • From: George Trojan
• Re: Allocation interoperability (Fortran/C)
  • From: Sebastian Hanigk
• Re: code critique wanted
  • From: Beliavsky
• Re: Allocation interoperability (Fortran/C)
  • From: Steve Lionel
• Re: Printing large arrays in Fortran
  • From: Gordon Sande
• Re: code critique wanted
  • From: Paul van Delst
• Re: Printing large arrays in Fortran
  • From: Beliavsky
• Re: Allocation interoperability (Fortran/C)
  • From: Sebastian Hanigk
• Re: code critique wanted
  • From: George Trojan
• Re: Allocation interoperability (Fortran/C)
  • From: Ian Bush
• Re: F2003
  • From: Mehmet Karatay
• Re: Aargh - can't get makefile to work in gfortran under WindowsXP
  • From: Kamaraju Kusumanchi
• Re: Aargh - can't get makefile to work in gfortran under WindowsXP
  • From: olegus
• Re: Allocation interoperability (Fortran/C)
  • From: Sebastian Hanigk
• F2003
  • From: Mehmet Karatay
• Re: Allocation interoperability (Fortran/C)
  • From: Steve Lionel
• Re: writing in array
  • From: Mark Morss
• Allocation interoperability (Fortran/C)
  • From: Sebastian Hanigk
• Re: writing in array
  • From: Ian Bush
• Re: writing in array
  • From: nakisa
• Re: writing in array
  • From: nakisa
• Re: Power Term serveur...
  • From: John Smith
• Re: writing in array
  • From: Ian Bush
• Re: writing in array
  • From: nakisa
• Re: writing in array
  • From: nakisa
• Re: Printing large arrays in Fortran
  • From: Ian Bush
• Re: writing in array
  • From: Ian Bush
• Re: writing in array
  • From: Michel Olagnon
• Re: Printing large arrays in Fortran
  • From: Dylan Sung
• Re: Power Term serveur...
  • From: hornblende
• writing in array
  • From: nakisa
• Re: Power Term serveur...
  • From: Beliavsky
• Re: Printing large arrays in Fortran
  • From: Dmitry V. Gorbatovsky
• Re: Printing large arrays in Fortran
  • From: James Giles
• Re: Printing large arrays in Fortran
  • From: James Giles
• Re: command for measuring computing time in milli sec.
  • From: Sv. Broholm
• Re: Printing large arrays in Fortran
  • From: Mark B Stucky
• Re: code critique wanted
  • From: James Giles
• Power Term serveur...
  • From: hornblende
• Re: Printing large arrays in Fortran
  • From: Terence
• Re: code critique wanted
  • From: Mark Morss
• Re: Printing large arrays in Fortran
  • From: Ancient_Hacker
• RE: Printing large arrays in Fortran
  • From: meek
• Re: Printing large arrays in Fortran
  • From: dpb
• Re: index value after FORALL
  • From: John Harper
• Re: Knuth: Linear Congruential Method
  • From: e p chandler
• Re: Knuth: Linear Congruential Method
  • From: glen herrmannsfeldt
• Re: f90
  • From: Kevin Vang
• f90
  • From: wyatt
• Re: Knuth: Linear Congruential Method
  • From: allelopath
• Re: Printing large arrays in Fortran
  • From: glen herrmannsfeldt
• Re: code critique wanted
  • From: George Trojan
• Re: index value after FORALL
  • From: glen herrmannsfeldt
• Re: code critique wanted
  • From: Paul van Delst
• Re: Printing large arrays in Fortran
  • From: fai391
• Re: code critique wanted
  • From: Michael Metcalf
• Re: Printing large arrays in Fortran
  • From: Beliavsky
• Re: Printing large arrays in Fortran
  • From: fai391
• Re: code critique wanted
  • From: Rich Townsend
• Printing large arrays in Fortran
  • From: fai391
• Re: code critique wanted
  • From: George Trojan
• Re: code critique wanted
  • From: Paul van Delst
• Re: code critique wanted
  • From: Beliavsky
• Re: code critique wanted
  • From: Mark Morss
• code critique wanted
  • From: George Trojan
• Re: index value after FORALL
  • From: Richard E Maine
• Re: Variable name with different font size
  • From: Richard E Maine
• Re: Knuth: Linear Congruential Method
  • From: Gordon Sande
• Re: Aargh - can't get makefile to work in gfortran under WindowsXP
  • From: hywel . owen
• Re: threaded avl trees?!
  • From: Arjen Markus
• Re: Knuth: Linear Congruential Method
  • From: e p chandler
• Re: Aargh - can't get makefile to work in gfortran under WindowsXP
  • From: olegus
• threaded avl trees?!
  • From: Daniel Franke
• Re: Aargh - can't get makefile to work in gfortran under WindowsXP
  • From: hywel . owen
• Re: Aargh - can't get makefile to work in gfortran under WindowsXP
  • From: hywel . owen
• Re: Knuth: Linear Congruential Method
  • From: allelopath
• Re: Aargh - can't get makefile to work in gfortran under WindowsXP
  • From: FX
• Re: Aargh - can't get makefile to work in gfortran under WindowsXP
  • From: FX
• Re: index value after FORALL
  • From: Brooks Moses
• Re: index value after FORALL
  • From: glen herrmannsfeldt
• Re: command for measuring computing time in milli sec.
  • From: glen herrmannsfeldt
• Re: index value after FORALL
  • From: Brooks Moses
• Re: index value after FORALL
  • From: Brooks Moses
• Re: index value after FORALL
  • From: glen herrmannsfeldt
• Re: Knuth: Linear Congruential Method
  • From: e p chandler
• Re: index value after FORALL
  • From: glen herrmannsfeldt
• Re: index value after FORALL
  • From: John Harper
• Re: index value after FORALL
  • From: John Harper
• Re: PGI Visual Fortran
  • From: Gary Scott
• Re: Knuth: Linear Congruential Method
  • From: allelopath
• Re: Knuth: Linear Congruential Method
  • From: e p chandler
• Re: index value after FORALL
  • From: Brooks Moses
• Re: Knuth: Linear Congruential Method
  • From: Terence
• Re: Aargh - can't get makefile to work in gfortran under WindowsXP
  • From: Gene Wagenbreth
• Re: PGI Visual Fortran
  • From: Steve Lionel
• Re: Aargh - can't get makefile to work in gfortran under WindowsXP
  • From: Craig Powers
• Re: Aargh - can't get makefile to work in gfortran under WindowsXP
  • From: glen herrmannsfeldt
• Re: Aargh - can't get makefile to work in gfortran under WindowsXP
  • From: hywel . owen
• Re: PGI Visual Fortran
  • From: gary . l . scott
• Re: PGI Visual Fortran
  • From: gary . l . scott
• Re: index value after FORALL
  • From: glen herrmannsfeldt
• Re: Aargh - can't get makefile to work in gfortran under WindowsXP
  • From: hywel . owen
• Re: Aargh - can't get makefile to work in gfortran under WindowsXP
  • From: Steven G. Kargl
• Re: index value after FORALL
  • From: Steven G. Kargl
• Re: Aargh - can't get makefile to work in gfortran under WindowsXP
  • From: hywel . owen
• index value after FORALL
  • From: Beliavsky
• Re: [ANN] PGI Visual Fortran
  • From: Paul van Delst
• Re: Aargh - can't get makefile to work in gfortran under WindowsXP
  • From: olegus
• Knuth: Linear Congruential Method
  • From: allelopath
• Re: Aargh - can't get makefile to work in gfortran under WindowsXP
  • From: Sebastian Gallinat
• Aargh - can't get makefile to work in gfortran under WindowsXP
  • From: hywel . owen
• Re: check monotony of array values
  • From: glen herrmannsfeldt
• Re: printing in fortran
  • From: lane straatman
• Re: fortran give false value !!!
  • From: nakisa
• Re: fortran give false value !!!
  • From: lane straatman
• Re: fortran give false value !!!
  • From: Rich Townsend
• Re: fortran give false value !!!
  • From: Michel Olagnon
• Re: fortran give false value !!!
  • From: David Flower
• Re: fortran give false value !!!
  • From: Paul van Delst
• fortran give false value !!!
  • From: nakisa
• Re: Computing zero set of function of two variables
  • From: Beliavsky
• Re: check monotony of array values
  • From: Rich Townsend
• Re: check monotony of array values
  • From: Michael Metcalf
• Re: How to deal with a file with binary and formatted blocks at once ?
  • From: Jan Vorbrüggen
• How to deal with a file with binary and formatted blocks at once ?
  • From: abbad
• Real-Time program terminate faults
  • From: David Frank
• Re: check monotony of array values
  • From: Dr Ivan D. Reid
• Re: check monotony of array values
  • From: Dr Ivan D. Reid
• Re: INQUIRE - FORM vs. (UN)FORMATTED
  • From: Jan Vorbrüggen
• Re: INQUIRE - FORM vs. (UN)FORMATTED
  • From: Jan Vorbrüggen
• Re: INQUIRE - FORM vs. (UN)FORMATTED
  • From: glen herrmannsfeldt
• Re: Computing zero set of function of two variables
  • From: glen herrmannsfeldt
• Re: INQUIRE - FORM vs. (UN)FORMATTED
  • From: glen herrmannsfeldt
• Re: INQUIRE - FORM vs. (UN)FORMATTED
  • From: Terence
• Re: check monotony of array values
  • From: Terence
• Re: Computing zero set of function of two variables
  • From: Terence
• Re: check monotony of array values
  • From: Mike
• Computing zero set of function of two variables
  • From: veda
• Re: check monotony of array values
  • From: Michael Metcalf
• RE: INQUIRE - FORM vs. (UN)FORMATTED
  • From: meek
• check monotony of array values
  • From: Mike
• Re: command for measuring computing time in milli sec.
  • From: Sebastian Hanigk
• Re: INQUIRE - FORM vs. (UN)FORMATTED
  • From: Jim
• Re: Summary of F2003 features supported in each compiler
  • From: ian_d_chivers
• Re: INQUIRE - FORM vs. (UN)FORMATTED
  • From: Dr Ivan D. Reid
• Re: Variable name with different font size
  • From: Terence
• Re: INQUIRE - FORM vs. (UN)FORMATTED
  • From: Terence
• Re: CPU_TIME() and OpenMP
  • From: Ron Shepard
• CPU_TIME() and OpenMP
  • From: Leif Harcke
• Re: INQUIRE - FORM vs. (UN)FORMATTED
  • From: Richard E Maine
• Re: INQUIRE - FORM vs. (UN)FORMATTED
  • From: Terence
• Re: Variable name with different font size
  • From: Terence
• Re: Popularity contests
  • From: Gary Scott
• Re: Popularity contests
  • From: analyst41
• Re: Variable name with different font size
  • From: Ancient_Hacker
• Re: INQUIRE - FORM vs. (UN)FORMATTED
  • From: robert . corbett
• Re: Popularity contests
  • From: Gary Scott
• Re: printing in fortran
  • From: Gary Scott
• Re: Compiling Fortran in 32 bit mode
  • From: Brooks Moses
• Re: Variable name with different font size
  • From: glen herrmannsfeldt
• Variable name with different font size
  • From: Mike
• Re: Compiling Fortran in 32 bit mode
  • From: Gib Bogle
• Re: Compiling Fortran in 32 bit mode
  • From: Ishmael
• Re: Compiling Fortran in 32 bit mode
  • From: Ishmael
• Re: Popularity contests
  • From: analyst41
• Re: Compiling Fortran in 32 bit mode
  • From: Ishmael
• Re: Compiling Fortran in 32 bit mode
  • From: Ishmael
• Re: Compiling Fortran in 32 bit mode
  • From: Ishmael
• Re: Compiling Fortran in 32 bit mode
  • From: olegus
• Re: Compiling Fortran in 32 bit mode
  • From: glen herrmannsfeldt
• Re: Compiling Fortran in 32 bit mode
  • From: Greg Lindahl
• Re: Compiling Fortran in 32 bit mode
  • From: Ishmael
• Re: Compiling Fortran in 32 bit mode
  • From: olegus
• Re: printing in fortran
  • From: Dr Ivan D. Reid
• Re: Compiling Fortran in 32 bit mode
  • From: Dr Ivan D. Reid
• Re: Compiling Fortran in 32 bit mode
  • From: Richard Maine
• Re: printing in fortran
  • From: Richard Maine
• Re: Compiling Fortran in 32 bit mode
  • From: glen herrmannsfeldt
• Re: printing in fortran
  • From: glen herrmannsfeldt
• Re: printing in fortran
  • From: Richard Maine
• Re: Compiling Fortran in 32 bit mode
  • From: Richard Maine
• Re: Compiling Fortran in 32 bit mode
  • From: Beliavsky
• Re: printing in fortran
  • From: lane straatman
• Compiling Fortran in 32 bit mode
  • From: Ishmael
• Re: Memory usage f95...
  • From: glen herrmannsfeldt
• Re: INQUIRE - FORM vs. (UN)FORMATTED
  • From: glen herrmannsfeldt
• Re: Popularity contests
  • From: Greg Lindahl
• Re: Memory usage f95...
  • From: Craig Powers
• Re: INQUIRE - FORM vs. (UN)FORMATTED
  • From: Tobias Burnus
• Re: Popularity contests
  • From: Richard Maine
• Re: Summary of F2003 features supported in each compiler
  • From: gary . l . scott
• Re: INQUIRE - FORM vs. (UN)FORMATTED
  • From: Richard Maine
• Memory usage f95...
  • From: tripp
• Re: Popularity contests
  • From: Rich Townsend
• Re: Summary of F2003 features supported in each compiler
  • From: Rich Townsend
• RE: command for measuring computing time in milli sec.
  • From: meek
• Re: Popularity contests
  • From: Greg Lindahl
• Re: [OT] random numbers in fortran
  • From: Jugoslav Dujic
• Re: command for measuring computing time in milli sec.
  • From: glen herrmannsfeldt
• INQUIRE - FORM vs. (UN)FORMATTED
  • From: Tobias Burnus
• Re: Fortran 90/95 code obfuscator?
  • From: David Flower
• Re: command for measuring computing time in milli sec.
  • From: Sebastian Hanigk
• Re: command for measuring computing time in milli sec.
  • From: Richard Maine
• Re: command for measuring computing time in milli sec.
  • From: Sebastian Hanigk
• Re: command for measuring computing time in milli sec.
  • From: Sebastian Hanigk
• Re: command for measuring computing time in milli sec.
  • From: Sebastian Hanigk
• Re: command for measuring computing time in milli sec.
  • From: glen herrmannsfeldt
• Re: command for measuring computing time in milli sec.
  • From: Sebastian Hanigk
• Re: command for measuring computing time in milli sec.
  • From: glen herrmannsfeldt
• Re: Popularity contests
  • From: analyst41
• Re: Summary of F2003 features supported in each compiler
  • From: Greg Lindahl
• Re: printing in fortran
  • From: Richard E Maine
• Re: printing in fortran
  • From: Joost
• Re: Summary of F2003 features supported in each compiler
  • From: Joost
• printing in fortran
  • From: lane straatman
• RE: command for measuring computing time in milli sec.
  • From: meek
• Re: random numbers in fortran
  • From: lane straatman
• Re: command for measuring computing time in milli sec.
  • From: glen herrmannsfeldt
• Re: command for measuring computing time in milli sec.
  • From: glen herrmannsfeldt
• RE: command for measuring computing time in milli sec.
  • From: meek
• Re: command for measuring computing time in milli sec.
  • From: glen herrmannsfeldt
• Re: command for measuring computing time in milli sec.
  • From: Steve Lionel
• Re: Summary of F2003 features supported in each compiler
  • From: Greg Lindahl
• Re: Can Java program evoke and run a FORTRAN program directly?
  • From: J.F. Cornwall
• RE: command for measuring computing time in milli sec.
  • From: meek
• Re: command for measuring computing time in milli sec.
  • From: glen herrmannsfeldt
• Re: Fortran 2003: Procedures in assignments
  • From: nospam . mehmet
• Re: Fortran 2003: Procedures in assignments
  • From: Richard E Maine
• Re: Fortran 2003: Procedures in assignments
  • From: Reinhold Bader
• Re: Can Java program evoke and run a FORTRAN program directly?
  • From: Steve Lionel
• Fortran 2003: Procedures in assignments
  • From: nospam . mehmet
• Re: Can Java program evoke and run a FORTRAN program directly?
  • From: Steve Lionel
• Re: Summary of F2003 features supported in each compiler
  • From: Steve Lionel
• Re: Can Java program evoke and run a FORTRAN program directly?
  • From: Richard E Maine
• Re: Can Java program evoke and run a FORTRAN program directly?
  • From: Herman D . Knoble
• Re: Can Java program evoke and run a FORTRAN program directly?
  • From: J.F. Cornwall
• Re: random numbers in fortran
  • From: Ian Bush
• Re: Summary of F2003 features supported in each compiler
  • From: Beliavsky
• Re: Summary of F2003 features supported in each compiler
  • From: Tobias Burnus
• Re: command for measuring computing time in milli sec.
  • From: Tim Prince
• Re: random numbers in fortran
  • From: Jugoslav Dujic
• Re: Summary of F2003 features supported in each compiler
  • From: mat_cross
• Summary of F2003 features supported in each compiler
  • From: Rich Townsend
• Re: couple c and fortran 95
  • From: Beliavsky
• Re: Fortran dud ...
  • From: David Flower
• Re: command for measuring computing time in milli sec.
  • From: Tobias Burnus
• Re: generic interface and not referred ambiguous symbols
  • From: Jan Vorbrüggen
• Re: How to pad integer output with zeros
  • From: Sebastian Hanigk
• Re: How to pad integer output with zeros
  • From: Tobias Burnus
• Re: How to pad integer output with zeros
  • From: Les
• Re: How to pad integer output with zeros
  • From: Dan Nagle
• How to pad integer output with zeros
  • From: Sebastian Hanigk
• Re: command for measuring computing time in milli sec.
  • From: Helge Avlesen
• Re: Fortran dud ...
  • From: David the Dude
• Re: command for measuring computing time in milli sec.
  • From: Daniel Franke
• Re: Using the same subroutine to read files with different structures
  • From: Arjen Markus
• command for measuring computing time in milli sec.
  • From: viraginspires@xxxxxxxxx
• Re: random numbers in fortran
  • From: Gordon Sande
• Re: Using the same subroutine to read files with different structures
  • From: Gordon Sande
• Re: couple c and fortran 95
  • From: PJH
• Re: couple c and fortran 95
  • From: glen herrmannsfeldt
• Re: generic interface and not referred ambiguous symbols
  • From: Dick Hendrickson
• couple c and fortran 95
  • From: pradeep.bhattad@xxxxxxxxx
• Re: Fortran dud ...
  • From: rjkematick@xxxxxxxxxxx
• Re: generic interface and not referred ambiguous symbols
  • From: Tobias Burnus
• Re: Fortran dud ...
  • From: Richard E Maine
• Re: Fortran dud ...
  • From: glen herrmannsfeldt
• Re: Fortran dud ...
  • From: Richard E Maine
• Re: Fortran 90/95 code obfuscator?
  • From: Richard E Maine
• Re: Fortran dud ...
  • From: rjkematick@xxxxxxxxxxx
• Re: Fortran 90/95 code obfuscator?
  • From: John Harper
• Re: Fortran 90/95 code obfuscator?
  • From: Ancient_Hacker
• Re: generic interface and not referred ambiguous symbols
  • From: Richard E Maine
• Re: Fortran dud ...
  • From: Gary Scott
• Re: Using the same subroutine to read files with different structures
  • From: Gary Scott
• Re: random numbers in fortran
  • From: lane straatman
• Re: generic interface and not referred ambiguous symbols
  • From: Tobias Burnus
• Re: Can Java program evoke and run a FORTRAN program directly?
  • From: Richard E Maine
• Re: Can Java program evoke and run a FORTRAN program directly?
  • From: Shawn
• Re: Fortran dud ...
  • From: Richard E Maine
• Re: Can Java program evoke and run a FORTRAN program directly?
  • From: PJH
• Re: Using the same subroutine to read files with different structures
  • From: Gordon Sande
• Re: Using the same subroutine to read files with different structures
  • From: PJH
• Re: Fortran dud ...
  • From: Beliavsky
• Re: Fortran 90/95 code obfuscator?
  • From: Richard E Maine
• Re: Can Java program evoke and run a FORTRAN program directly?
  • From: Steve Lionel
• Re: Can Java program evoke and run a FORTRAN program directly?
  • From: Shawn
• Re: Can Java program evoke and run a FORTRAN program directly?
  • From: glen herrmannsfeldt
• Re: Can Java program evoke and run a FORTRAN program directly?
  • From: Gary Scott
• Re: Fortran dud ...
  • From: Steven G. Kargl
• Can Java program evoke and run a FORTRAN program directly?
  • From: Shawn
• Fortran dud ...
  • From: David the Dude
• Re: Using the same subroutine to read files with different structures
  • From: Gary Scott
• Re: Fortran 90/95 code obfuscator?
  • From: Gary Scott
• Re: Using the same subroutine to read files with different structures
  • From: Gordon Sande
• Re: Popularity contests
  • From: Greg Lindahl
• Re: Fortran 90/95 code obfuscator?
  • From: Bil Kleb
• Re: Using the same subroutine to read files with different structures
  • From: Gary Scott
• Re: A problem with READ statement.
  • From: PJH
• Re: Using the same subroutine to read files with different structures
  • From: PJH
• Re: gfortran install on PCC OSX
  • From: baf
• Re: Popularity contests
  • From: analyst41
• Re: random numbers in fortran
  • From: Gordon Sande
• Fortran for old Computer Automation mini-computers
  • From: hamren
• Re: random numbers in fortran
  • From: lane straatman
• Re: random numbers in fortran
  • From: lane straatman
• Re: How popular is Fortran and what is it's future ?
  • From: Mark Morss
• Re: Fortran books
  • From: Paul van Delst
• Re: Fortran books
  • From: Beliavsky
• Re: Fortran books
  • From: Paul van Delst
• Re: Fortran books
  • From: Beliavsky
• Re: random numbers in fortran
  • From: lane straatman
• Re: Fortran books
  • From: Michael Prager
• Re: Using the same subroutine to read files with different structures
  • From: Herman D . Knoble
• Re: Using the same subroutine to read files with different structures
  • From: Richard Maine
• Re: Fortran books
  • From: Richard Maine
• Re: How popular is Fortran and what is it's future ?
  • From: Richard Maine
• Fortran books (was Re: How popular is Fortran and what is it's future ?)
  • From: Beliavsky
• Re: How popular is Fortran and what is it's future ?
  • From: Richard Maine
• Re: How popular is Fortran and what is it's future ?
  • From: Beliavsky
• Re: gfortran install on PCC OSX
  • From: Richard Maine
• Re: Using the same subroutine to read files with different structures
  • From: Beliavsky
• Re: Using the same subroutine to read files with different structures
  • From: David Frank
• Re: How popular is Fortran and what is it's future ?
  • From: Mark Morss
• Re: Using the same subroutine to read files with different structures
  • From: David Frank
• Re: random numbers in fortran
  • From: Michael Metcalf
• Using the same subroutine to read files with different structures
  • From: deltaquattro
• Re: gfortran install on PCC OSX
  • From: FX
• Re: gfortran install on PCC OSX
  • From: Tobias Burnus
• Re: gfortran install on PCC OSX
  • From: Dr Ivan D. Reid
• gfortran install on PCC OSX
  • From: baf
• Re: defining an arbitrary type in your newer Fortrans
  • From: Richard Maine
• Re: defining an arbitrary type in your newer Fortrans
  • From: celeia
• Re: random numbers in fortran
  • From: lane straatman
• Re: gfortran uses four-byte record markers by default
  • From: robert . corbett
• Re: A problem with READ statement.
  • From: Richard E Maine
• Re: A problem with READ statement.
  • From: Jim
• Re: Problems with big modules of subroutines
  • From: Jan Vorbrüggen
• Re: locating freeware subroutines (Netlib, GAMS, etc)
  • From: David Duffy
• Re: Question concerning submodules
  • From: Richard E Maine
• Re: Question concerning submodules
  • From: glen herrmannsfeldt
• Question concerning submodules
  • From: Reinhold Bader
• Re: convert code with Hollerith constants
  • From: Ancient_Hacker
• Re: convert code with Hollerith constants
  • From: Beliavsky
• Re: convert code with Hollerith constants
  • From: Richard E Maine
• Re: convert code with Hollerith constants
  • From: Richard E Maine
• Re: convert code with Hollerith constants
  • From: Steve Lionel
• Re: Fortran 90/95 code obfuscator?
  • From: Jugoslav Dujic
• Re: generic interface and not referred ambiguous symbols
  • From: Steve Lionel
• convert code with Hollerith constants
  • From: Beliavsky
• Re: subroutine argument question
  • From: John
• Re: subroutine argument question
  • From: Klaus Wacker
• Re: Fortran 90/95 code obfuscator?
  • From: Jugoslav Dujic
• Re: subroutine argument question
  • From: Jugoslav Dujic
• Re: Interface problem
  • From: Jugoslav Dujic
• Re: subroutine argument question
  • From: John
• Re: subroutine argument question
  • From: John
• Re: Interface problem
  • From: Dieter Britz
• Re: Interface problem
  • From: Michael Metcalf
• Re: subroutine argument question
  • From: Michael Metcalf
• Re: Interface problem
  • From: Arjen Markus
• Re: Problems with big modules of subroutines
  • From: deltaquattro
• subroutine argument question
  • From: John
• Interface problem
  • From: Dieter Britz
• Re: Fortran 90/95 code obfuscator?
  • From: David Flower
• Re: Fortran 90/95 code obfuscator?
  • From: Oskar Enoksson
• Re: Fortran 90/95 code obfuscator?
  • From: Ron Shepard
• Re: A problem with READ statement.
  • From: Richard Maine
• Re: A problem with READ statement.
  • From: Dan Nagle
• Re: A problem with READ statement.
  • From: Fortran Learner
• Re: A problem with READ statement.
  • From: Dan Nagle
• A problem with READ statement.
  • From: Fortran Learner
• Re: How popular is Fortran and what is it's future ?
  • From: Beliavsky
• Re: Fortran 90/95 code obfuscator?
  • From: Ancient_Hacker
• Re: How popular is Fortran and what is it's future ?
  • From: Terence
• Re: generic interface and not referred ambiguous symbols
  • From: Tobias Burnus
• Re: Fortran 90/95 code obfuscator?
  • From: Dick Hendrickson
• Re: How popular is Fortran and what is it's future ?
  • From: Gary Scott
• Re: generic interface and not referred ambiguous symbols
  • From: Richard Maine
• Re: How popular is Fortran and what is it's future ?
  • From: Beliavsky
• generic interface and not referred ambiguous symbols
  • From: Tobias Burnus
• Re: Problems with big modules of subroutines
  • From: robin
• Re: How popular is Fortran and what is it's future ?
  • From: Tobias Burnus
• Fortran 90/95 code obfuscator?
  • From: Oskar Enoksson
• Re: How popular is Fortran and what is it's future ?
  • From: Gary Scott
• Re: How popular is Fortran and what is it's future ?
  • From: dpb
• Re: Problems with big modules of subroutines
  • From: Steve Lionel
• Re: How popular is Fortran and what is it's future ?
  • From: Beliavsky
• Re: How popular is Fortran and what is it's future ?
  • From: Dylan Sung
• How popular is Fortran and what is it's future ?
  • From: Random
• Re: A problem to read a SEG-file using Fortran90 code on PC
  • From: Terence
• Re: problem about "undefined reference to *** "
  • From: Fortran Learner
• problem about "undefined reference to *** "
  • From: Fortran Learner
• Re: A problem to read a SEG-file using Fortran90 code on PC
  • From: glen herrmannsfeldt
• Re: HELP : LINUX TOP analysis query
  • From: Richard Maine
• Re: HELP : LINUX TOP analysis query
  • From: Beliavsky
• HELP : LINUX TOP analysis query
  • From: igthibau
• Re: gfortran uses four-byte record markers by default
  • From: Thomas Koenig
• Re: A problem to read a SEG-file using Fortran90 code on PC
  • From: Michel Olagnon
• Re: Problems with big modules of subroutines
  • From: Colin Watters
• Re: gfortran uses four-byte record markers by default
  • From: glen herrmannsfeldt
• Re: gfortran uses four-byte record markers by default
  • From: glen herrmannsfeldt
• Re: gfortran uses four-byte record markers by default
  • From: Richard Maine
• Re: gfortran uses four-byte record markers by default
  • From: Terence
• Re: gfortran uses four-byte record markers by default
  • From: Richard Maine
• Re: Problems with big modules of subroutines
  • From: Richard Maine
• Re: Problems with big modules of subroutines
  • From: Paul van Delst
• Re: Problems with big modules of subroutines
  • From: Beliavsky
• Re: gfortran uses four-byte record markers by default
  • From: Steve Lionel
• Re: Problems with big modules of subroutines
  • From: PJH
• Re: Popularity contests
  • From: Mark B Stucky
• Re: gfortran uses four-byte record markers by default
  • From: robert . corbett
• gfortran uses four-byte record markers by default
  • From: Thomas Koenig
• Re: Problems with big modules of subroutines
  • From: Richard Maine
• Re: Problems with big modules of subroutines
  • From: PJH
• Re: A problem to read a SEG-file using Fortran90 code on PC
  • From: glen herrmannsfeldt
• Re: using optional arguments not present (bug)
  • From: glen herrmannsfeldt
• Re: Problems with big modules of subroutines
  • From: Mark Morss
• Re: Popularity contests
  • From: Mark Morss
• Re: Problems with big modules of subroutines
  • From: Beliavsky
• Re: Popularity contests
  • From: J.F. Cornwall
• Re: Popularity contests
  • From: PJH
• Re: Problems with big modules of subroutines
  • From: PJH
• Re: Popularity contests
  • From: Mark Morss
• Re: Popularity contests
  • From: PJH
• Re: Problems with big modules of subroutines
  • From: Craig Powers
• Problems with big modules of subroutines
  • From: deltaquattro
• Re: Popularity contests
  • From: Paul van Delst
• Re: using optional arguments not present (bug)
  • From: Richard Edgar
• Re: Popularity contests
  • From: Mark Morss
• Re: Popularity contests
  • From: Mark Morss
• Re: Sparse matrix assmbly Finite Volumes
  • From: Zadig
• Re: Popularity contests
  • From: gary . l . scott
• Re: Sparse matrix assmbly Finite Volumes
  • From: Pierre Asselin
• Re: debug error 'AFTER NORMAL BLOCK'
  • From: Steve Lionel
• Re: Popularity contests
  • From: Beliavsky
• Re: A problem to read a SEG-file using Fortran90 code on PC
  • From: Michel Olagnon
• A problem to read a SEG-file using Fortran90 code on PC
  • From: abbad
• Re: debug error 'AFTER NORMAL BLOCK'
  • From: Dr Ivan D. Reid
• Re: functions returning (pointer to) subroutine?
  • From: Daniel Franke
• debug error 'AFTER NORMAL BLOCK'
  • From: Kristien
• Re: Popularity contests
  • From: PJH
• Re: Popularity contests
  • From: Mark Westwood
• Re: using optional arguments not present (bug)
  • From: glen herrmannsfeldt
• Re: format questions
  • From: Beliavsky
• format questions
  • From: liyuzhen_2000
• Re: using optional arguments not present (bug)
  • From: Richard Maine
• Re: using optional arguments not present (bug)
  • From: Richard Maine
• Re: functions returning (pointer to) subroutine?
  • From: Richard Maine
• functions returning (pointer to) subroutine?
  • From: Daniel Franke
• Re: using optional arguments not present (bug)
  • From: Richard E Maine
• Re: Popularity contests
  • From: Greg Lindahl
• Re: using optional arguments not present (bug)
  • From: Steve Lionel
• Re: using optional arguments not present (bug)
  • From: Craig Powers
• Re: using optional arguments not present (bug)
  • From: Paul van Delst
• Re: using optional arguments not present (bug)
  • From: Rich Townsend
• Re: using optional arguments not present (bug)
  • From: Richard E Maine
• Re: using optional arguments not present (bug)
  • From: Paul van Delst
• RE: Popularity contests
  • From: meek
• Re: using optional arguments not present (bug)
  • From: Richard E Maine
• Re: using optional arguments not present (bug)
  • From: Thomas Koenig
• Re: using optional arguments not present (bug)
  • From: Richard E Maine
• Re: using optional arguments not present (bug)
  • From: glen herrmannsfeldt
• using optional arguments not present (bug)
  • From: Beliavsky
• Re: Popularity contests
  • From: PJH
• Re: random numbers in fortran
  • From: Mark Morss
• Re: Sparse matrix assmbly Finite Volumes
  • From: Zadig
• Re: Popularity contests
  • From: Beliavsky
• Re: Popularity contests
  • From: Beliavsky
• Re: Popularity contests
  • From: gary . l . scott
• Re: Can I do this in Fortran?
  • From: Reinhold Bader
• Re: Can I do this in Fortran?
  • From: Ancient_Hacker
• Re: Can I do this in Fortran?
  • From: Paul van Delst
• Re: Sparse matrix assmbly Finite Volumes
  • From: Pierre Asselin
• Re: Popularity contests
  • From: Dr Ivan D. Reid
• Re: Can I do this in Fortran?
  • From: Jan Vorbrüggen
• Can I do this in Fortran?
  • From: Ancient_Hacker
• Re: random numbers in fortran
  • From: Gordon Sande
• Re: A problem in writting a sequential binary file (compiled with LF95)
  • From: P.Wholey
• Re: random numbers in fortran
  • From: Michael Metcalf
• Re: random numbers in fortran
  • From: Michael Metcalf
• Re: random numbers in fortran
  • From: Herman D . Knoble
• Popularity contests
  • From: Bil Kleb
• Re: random numbers in fortran
  • From: Gordon Sande
• Sparse matrix assmbly Finite Volumes
  • From: Zadig
• Re: random numbers in fortran
  • From: Mark Morss
• Re: random numbers in fortran
  • From: Dr Ivan D. Reid
• Re: random numbers in fortran
  • From: glen herrmannsfeldt
• Re: random numbers in fortran
  • From: Jan Vorbrüggen
• Re: random numbers in fortran
  • From: Dr Ivan D. Reid
• Re: random numbers in fortran
  • From: Ron Shepard
• Re: random numbers in fortran
  • From: Ron Shepard
• Re: Reading Multiple files in fortran
  • From: Louis Krupp
• Re: locating freeware subroutines (Netlib, GAMS, etc)
  • From: Mark Morss
• Re: random numbers in fortran
  • From: Mark Morss
• Re: Reading Multiple files in fortran
  • From: Beliavsky
• Reading Multiple files in fortran
  • From: swetha . panguluri
• Re: random numbers in fortran
  • From: Mark Morss
• Re: locating freeware subroutines (Netlib, GAMS, etc)
  • From: rawlins02
• Re: locating freeware subroutines (Netlib, GAMS, etc)
  • From: Beliavsky
• Re: locating freeware subroutines (Netlib, GAMS, etc)
  • From: Bil Kleb
• Re: locating freeware subroutines (Netlib, GAMS, etc)
  • From: Ian Brown
• Re: locating freeware subroutines (Netlib, GAMS, etc)
  • From: Paul van Delst
• Re: How to assign a=b=c=2 in fortran in one statement
  • From: Ancient_Hacker
• Re: What does /= do?
  • From: dpb
• Re: What does /= do?
  • From: Tobias Burnus
• Re: locating freeware subroutines (Netlib, GAMS, etc)
  • From: Beliavsky
• Re: What does /= do?
  • From: Richard E Maine
• Re: random numbers in fortran
  • From: glen herrmannsfeldt
• Re: What does /= do?
  • From: dpb
• Re: What does /= do?
  • From: dpb
• locating freeware subroutines (Netlib, GAMS, etc)
  • From: rawlins02
• Re: What does /= do?
  • From: tripp
• Re: What does /= do?
  • From: tripp
• Re: What does /= do?
  • From: Beliavsky
• What does /= do?
  • From: tripp
• Re: random numbers in fortran
  • From: Herman D . Knoble
• Re: random numbers in fortran
  • From: Ron Shepard
• Re: defining an arbitrary type in your newer Fortrans
  • From: Richard E Maine
• Re: defining an arbitrary type in your newer Fortrans
  • From: Richard E Maine
• Re: defining an arbitrary type in your newer Fortrans
  • From: Steve Lionel
• Re: random numbers in fortran
  • From: Herman D . Knoble
• Re: (OT) random numbers in fortran
  • From: Jugoslav Dujic
• Re: random numbers in fortran
  • From: glen herrmannsfeldt
• Re: Cray binary format
  • From: Ian Bush
• Re: defining an arbitrary type in your newer Fortrans
  • From: glen herrmannsfeldt
• Re: random numbers in fortran
  • From: Dr Ivan D. Reid
• Re: defining an arbitrary type in your newer Fortrans
  • From: Jan Vorbrüggen
• Re: defining an arbitrary type in your newer Fortrans
  • From: Jan Vorbrüggen
• Re: random numbers in fortran
  • From: glen herrmannsfeldt
• RE: rounding a number
  • From: meek
• RE: Cray binary format
  • From: meek
• RE: Pet hates
  • From: meek
• RE: integer to character?
  • From: meek
• RE: too long function
  • From: meek

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