comp.lang.fortran

• Thread Index

---

• Re: Recursion
  • From: John Harper
• Re: backslash-issues
  • From: Bart Vandewoestyne
• Re: backslash-issues
  • From: Bart Vandewoestyne
• Re: backslash-issues
  • From: Clive Page
• Re: backslash-issues
  • From: Bart Vandewoestyne
• Re: backslash-issues
  • From: bv
• Re: backslash-issues
  • From: Richard E Maine
• Re: backslash-issues
  • From: Joost
• Re: question about intel compiler
  • From: hchu
• Re: How to select a subset of an array in Fortran 90
  • From: Levent
• Re: backslash-issues
  • From: Bart Vandewoestyne
• Re: backslash-issues
  • From: Joost
• Re: backslash-issues
  • From: Joost
• [OT] Re: backslash-issues
  • From: Bart Vandewoestyne
• Re: backslash-issues
  • From: Walt Brainerd
• Re: backslash-issues
  • From: Walt Brainerd
• Re: Recursion
  • From: David Flower
• Re: moduel VS parameters
  • From: Richard E Maine
• Re: backslash-issues
  • From: Joost
• Re: backslash-issues
  • From: Walt Brainerd
• Re: backslash-issues
  • From: Richard E Maine
• Re: HELP ME - HOW THIS ERROR?
  • From: Richard E Maine
• Re: I have no ideas what can it be!
  • From: Walt Brainerd
• Re: moduel VS parameters
  • From: s . c . kramer
• Re: Recursion
  • From: Richard E Maine
• Re: backslash-issues
  • From: Richard E Maine
• HELP ME - HOW THIS ERROR?
  • From: WindCina
• Re: backslash-issues
  • From: Bart Vandewoestyne
• Re: backslash-issues
  • From: James Giles
• How to select a subset of an array in Fortran 90
  • From: Leonard W. Howell, Jr.
• Re: HELP ME, please
  • From: Duane Bozarth
• Re: Recursion
  • From: Michael Prager
• Re: HELP ME, please
  • From: Ciobin
• Re: HELP ME, please
  • From: Duane Bozarth
• Re: HELP ME, please
  • From: David Flower
• Re: How to select a subset of an array in Fortran 90
  • From: [JvO]
• HELP ME, please
  • From: Ciobin
• Re: How to select a subset of an array in Fortran 90
  • From: Michel OLAGNON
• Re: backslash-issues
  • From: Arjen Markus
• Re: Recursion
  • From: Jan Vorbrüggen
• Re: Passing a 2 dimensional array from fortran to c++
  • From: Jan Vorbrüggen
• Re: Recursion
  • From: Kay Diederichs
• Recursion
  • From: David Flower
• Re: Passing a 2 dimensional array from fortran to c++
  • From: Sam
• Re: backslash-issues
  • From: Joost
• Re: backslash-issues
  • From: Bart Vandewoestyne
• Re: MODULEand USE versus Argument Passing
  • From: Richard Edgar
• Re: moduel VS parameters
  • From: Richard Edgar
• Re: I have no ideas what can it be!
  • From: Michel OLAGNON
• moduel VS parameters
  • From: yuanliu1
• Re: Intel nonVisual fortran
  • From: bv
• Re: MODULEand USE versus Argument Passing
  • From: Walter Spector
• Re: MODULEand USE versus Argument Passing
  • From: Walter Spector
• Re: Passing a 2 dimensional array from fortran to c++
  • From: glen herrmannsfeldt
• Re: Passing a 2 dimensional array from fortran to c++
  • From: Rich Townsend
• Re: Passing a 2 dimensional array from fortran to c++
  • From: glen herrmannsfeldt
• Re: MODULEand USE versus Argument Passing
  • From: glen herrmannsfeldt
• Passing a 2 dimensional array from fortran to c++
  • From: Sam
• Re: MODULEand USE versus Argument Passing
  • From: E. Robert Tisdale
• Re: MODULEand USE versus Argument Passing
  • From: James Van Buskirk
• question about intel compiler
  • From: yuanliu1
• Re: MODULEand USE versus Argument Passing
  • From: Richard E Maine
• Re: MODULEand USE versus Argument Passing
  • From: John Harper
• Re: MODULEand USE versus Argument Passing
  • From: James Giles
• Re: MODULEand USE versus Argument Passing
  • From: glen herrmannsfeldt
• backslash-issues
  • From: Bart Vandewoestyne
• Re: I have no ideas what can it be!
  • From: Walt Brainerd
• Re: MODULEand USE versus Argument Passing
  • From: E. Robert Tisdale
• Re: how to use fortran modules in c++
  • From: E. Robert Tisdale
• Re: MODULEand USE versus Argument Passing
  • From: glen herrmannsfeldt
• Re: MODULEand USE versus Argument Passing
  • From: glen herrmannsfeldt
• Re: MODULEand USE versus Argument Passing
  • From: Rich Townsend
• Re: MODULEand USE versus Argument Passing
  • From: Richard E Maine
• Re: MODULEand USE versus Argument Passing
  • From: Herman D . Knoble
• Re: I have no ideas what can it be!
  • From: Dick Hendrickson
• Re: MODULEand USE versus Argument Passing
  • From: glen herrmannsfeldt
• Re: MODULEand USE versus Argument Passing
  • From: Dick Hendrickson
• I have no ideas what can it be!
  • From: kurdayon
• Re: MODULEand USE versus Argument Passing
  • From: Herman D . Knoble
• Re: Argument of subroutine is an array of unfixed length.
  • From: Dick Hendrickson
• Re: Argument of subroutine is an array of unfixed length.
  • From: Rich Townsend
• Re: Argument of subroutine is an array of unfixed length.
  • From: Richard E Maine
• Re: (something) /= something ?
  • From: Joost
• Re: Halt execution procedure
  • From: Walt Brainerd
• Re: MODULEand USE versus Argument Passing
  • From: Joost
• Re: MODULEand USE versus Argument Passing
  • From: Duane Bozarth
• MODULEand USE versus Argument Passing
  • From: Herman D . Knoble
• Re: (something) /= something ?
  • From: Steve Lionel
• Re: Halt execution procedure
  • From: Klaus Wacker
• Re: Argument of subroutine is an array of unfixed length.
  • From: David Frank
• Re: Halt execution procedure
  • From: Jan Vorbrüggen
• Re: Argument of subroutine is an array of unfixed length.
  • From: Rich Townsend
• Re: Argument of subroutine is an array of unfixed length.
  • From: David Frank
• Re: Argument of subroutine is an array of unfixed length.
  • From: Michel OLAGNON
• Re: Argument of subroutine is an array of unfixed length.
  • From: James Giles
• Re: Argument of subroutine is an array of unfixed length.
  • From: James Giles
• Re: Argument of subroutine is an array of unfixed length.
  • From: kurdayon
• Re: Argument of subroutine is an array of unfixed length.
  • From: Arjen Markus
• Re: Argument of subroutine is an array of unfixed length.
  • From: James Giles
• Re: Argument of subroutine is an array of unfixed length.
  • From: kurdayon
• Re: Halt execution procedure
  • From: Walter Spector
• Re: (something) /= something ?
  • From: Rich Townsend
• Re: (something) /= something ?
  • From: James Van Buskirk
• Announce: Fortran Tools (additions)
  • From: Walt Brainerd
• Re: Intel nonVisual fortran
  • From: Jim Klein
• Re: (something) /= something ?
  • From: James Giles
• Re: Halt execution procedure
  • From: glen herrmannsfeldt
• Re: Intel nonVisual fortran
  • From: bv
• Re: (something) /= something ?
  • From: James Van Buskirk
• (something) /= something ?
  • From: FJRA
• how to use fortran modules in c++
  • From: Santosh
• Re: IVF odd behaviour: subroutine vs function returning floating point number
  • From: hchu
• Re: Fortran syntax question (involving **)
  • From: James Giles
• Re: Fortran syntax question (involving **)
  • From: Greg Lindahl
• Re: gfortran and byte keyword
  • From: Greg Lindahl
• Re: Halt execution procedure
  • From: Walt Brainerd
• Re: Fortran syntax question (involving **)
  • From: glen herrmannsfeldt
• Re: mystery equation "tanfunc"
  • From: Al
• Re: Fortran syntax question (involving **)
  • From: James Giles
• Re: Off topid: finite element vs finite volume
  • From: glen herrmannsfeldt
• Re: Halt execution procedure
  • From: Walter Spector
• Re: HELP for C -> fortran
  • From: glen herrmannsfeldt
• Re: Fortran syntax question (involving **)
  • From: Steve Lionel
• Re: Halt execution procedure
  • From: glen herrmannsfeldt
• Re: Fortran syntax question (involving **)
  • From: glen herrmannsfeldt
• Re: Fortran syntax question (involving **)
  • From: Steve Lionel
• Re: Fortran syntax question (involving **)
  • From: glen herrmannsfeldt
• Re: Fortran syntax question (involving **)
  • From: Steve Lionel
• Re: Halt execution procedure
  • From: Richard E Maine
• Re: Halt execution procedure
  • From: Walter Spector
• Re: Off topid: finite element vs finite volume
  • From: Michael Bader
• Re: Fortran syntax question (involving **)
  • From: Richard E Maine
• Re: Fortran syntax question (involving **)
  • From: James Van Buskirk
• Re: Fortran syntax question (involving **)
  • From: Joost
• Re: Fortran syntax question (involving **)
  • From: Richard E Maine
• Re: Fortran syntax question (involving **)
  • From: Joost
• Re: Argument of subroutine is an array of unfixed length.
  • From: Dick Hendrickson
• Re: Fortran syntax question (involving **)
  • From: Joost
• Re: Argument of subroutine is an array of unfixed length.
  • From: Rich Townsend
• Re: Fortran syntax question (involving **)
  • From: Steve Lionel
• Re: IVF odd behaviour: subroutine vs function returning floating point number
  • From: Steve Lionel
• Fortran syntax question (involving **)
  • From: Jim Cownie
• HELP for C -> fortran
  • From: WindCina
• Re: Argument of subroutine is an array of unfixed length.
  • From: Herman D . Knoble
• Re: Argument of subroutine is an array of unfixed length.
  • From: David Frank
• Re: Argument of subroutine is an array of unfixed length.
  • From: David Frank
• Re: Argument of subroutine is an array of unfixed length.
  • From: Herman D . Knoble
• Re: Efficient Programming
  • From: Carlie J. Coats
• Re: Argument of subroutine is an array of unfixed length.
  • From: David Frank
• Re: Announcing Intel Fortran Compilers 9.0
  • From: glen herrmannsfeldt
• Modules, libraries and CVF
  • From: Michael Yoshpe
• Argument of subroutine is an array of unfixed length.
  • From: kurdayon
• Re: gfortran and byte keyword
  • From: robert . corbett
• Re: Fortran 2003 features supported
  • From: owl
• IVF odd behaviour: subroutine vs function returning floating point number
  • From: hchu
• Re: Efficient Programming
  • From: Salomon Turgman
• Re: Efficient Programming
  • From: glen herrmannsfeldt
• Re: Announcing Intel Fortran Compilers 9.0
  • From: hchu
• Re: Efficient Programming
  • From: Salomon Turgman
• Re: Announcing Intel Fortran Compilers 9.0
  • From: hchu
• Re: gfortran and byte keyword
  • From: glen herrmannsfeldt
• Re: Efficient Programming
  • From: FJRA
• Re: gfortran and byte keyword
  • From: Richard E Maine
• Re: gfortran and byte keyword
  • From: glen herrmannsfeldt
• Re: gfortran and byte keyword
  • From: Richard E Maine
• Re: Efficient Programming
  • From: Herman D . Knoble
• Re: Efficient Programming
  • From: Salomon Turgman
• Re: Efficient Programming
  • From: Salomon Turgman
• Re: Efficient Programming
  • From: Dick Hendrickson
• Re: Efficient Programming
  • From: Salomon Turgman
• Re: Efficient Programming
  • From: Joost
• Re: Efficient Programming
  • From: Richard E Maine
• Re: Efficient Programming
  • From: Salomon Turgman
• Re: Efficient Programming
  • From: Joost
• Efficient Programming
  • From: Salomon Turgman
• Re: Halt execution procedure
  • From: Richard E Maine
• gfortran and byte keyword
  • From: Roggie H. Boone III
• C to Fortran
  • From: WindCina
• Re: Intel® Math Kernel Library +intel fortran
  • From: Steve Lionel
• Re: Announcing Intel Fortran Compilers 9.0
  • From: Steve Lionel
• Re: Intel® Math Kernel Library +intel fortran
  • From: Ronald Benedik
• Re: Halt execution procedure
  • From: glen herrmannsfeldt
• Re: Off topid: finite element vs finite volume
  • From: Andy Spragg
• Intel® Math Kernel Library +intel fortran
  • From: Pirata
• Re: Halt execution procedure
  • From: David Flower
• Re: Halt execution procedure
  • From: Jan Vorbrüggen
• Re: Halt execution procedure
  • From: glen herrmannsfeldt
• Re: global variables
  • From: glen herrmannsfeldt
• Re: hypergeometric function
  • From: glen herrmannsfeldt
• Re: Announcing Intel Fortran Compilers 9.0
  • From: Tim Prince
• Re: Announcing Intel Fortran Compilers 9.0
  • From: Tim Prince
• Re: global variables
  • From: Dave Thompson
• Re: Halt execution procedure
  • From: Dave Thompson
• Re: Announcing Intel Fortran Compilers 9.0
  • From: hchu
• Re: Announcing Intel Fortran Compilers 9.0
  • From: hchu
• Re: Announcing Intel Fortran Compilers 9.0
  • From: Gary L. Scott
• Re: Announcing Intel Fortran Compilers 9.0
  • From: Gary L. Scott
• Re: Announcing Intel Fortran Compilers 9.0
  • From: Tim Prince
• Re: Announcing Intel Fortran Compilers 9.0
  • From: Tim Prince
• Re: hypergeometric function
  • From: Steven G. Kargl
• Re: Announcing Intel Fortran Compilers 9.0
  • From: awd
• Re: hypergeometric function
  • From: awd
• Re: hypergeometric function
  • From: Joost
• Re: hypergeometric function
  • From: Gordon Sande
• Re: hypergeometric function
  • From: Donald R. Fredkin
• Re: Announcing Intel Fortran Compilers 9.0
  • From: Richard E Maine
• Re: Use'ing two functions with same name
  • From: Madhusudan Singh
• Re: Announcing Intel Fortran Compilers 9.0
  • From: hchu
• Re: using fortran modules in c++
  • From: Gary L. Scott
• using fortran modules in c++
  • From: Santosh
• Re: Announcing Intel Fortran Compilers 9.0
  • From: Rich Townsend
• Re: Announcing Intel Fortran Compilers 9.0
  • From: hchu
• Re: Announcing Intel Fortran Compilers 9.0
  • From: Rich Townsend
• Re: Announcing Intel Fortran Compilers 9.0
  • From: hchu
• Re: ADVANCE='no' and complex variables
  • From: James Giles
• Re: ADVANCE='no' and complex variables
  • From: Richard E Maine
• Re: Use'ing two functions with same name
  • From: glen herrmannsfeldt
• Re: Use'ing two functions with same name
  • From: Richard E Maine
• Re: ADVANCE='no' and complex variables
  • From: glen herrmannsfeldt
• Re: ADVANCE='no' and complex variables
  • From: Gary L. Scott
• Use'ing two functions with same name
  • From: Madhusudan Singh
• Re: ADVANCE='no' and complex variables
  • From: Greg Lindahl
• Re: 2nd rank concept, but is 1D array better?
  • From: Richard E Maine
• Re: ADVANCE='no' and complex variables
  • From: Richard E Maine
• Re: 2nd rank concept, but is 1D array better?
  • From: Ron Shepard
• Re: Array of my type
  • From: Richard E Maine
• Array of my type
  • From: WindCina
• Re: ADVANCE='no' and complex variables
  • From: Gary L. Scott
• Re: Terminator 2.0 Fortran Source Code
  • From: Gary L. Scott
• Re: Terminator 2.0 Fortran Source Code
  • From: Clive Page
• Re: Return Type
  • From: Abdul Qat
• Re: Announcing Intel Fortran Compilers 9.0
  • From: Rich Townsend
• Re: ADVANCE='no' and complex variables
  • From: Rich Townsend
• Re: 2nd rank concept, but is 1D array better?
  • From: glen herrmannsfeldt
• Re: 2nd rank concept, but is 1D array better?
  • From: Richard Seymour
• Re: Halt execution procedure
  • From: Walt Brainerd
• Re: Announcing Intel Fortran Compilers 9.0
  • From: hchu
• Re: ADVANCE='no' and complex variables
  • From: beliavsky
• Re: ADVANCE='no' and complex variables
  • From: bvoh
• Re: 2nd rank concept, but is 1D array better?
  • From: Richard E Maine
• Re: 2nd rank concept, but is 1D array better?
  • From: glen herrmannsfeldt
• 2nd rank concept, but is 1D array better?
  • From: Richard Seymour
• Re: ADVANCE='no' and complex variables
  • From: glen herrmannsfeldt
• Re: ADVANCE='no' and complex variables
  • From: James Van Buskirk
• Re: LF95 5.70f and integer exponentiation
  • From: James Van Buskirk
• Re: What is the Best Way to handle Optional Arguments with Default Values?
  • From: NuclearWizard
• Re: Counter with continuosly changing value
  • From: Richard E Maine
• Re: ADVANCE='no' and complex variables
  • From: glen herrmannsfeldt
• Re: ADVANCE='no' and complex variables
  • From: Rich Townsend
• Re: ADVANCE='no' and complex variables
  • From: Richard E Maine
• Re: Halt execution procedure
  • From: Richard E Maine
• Re: Terminator 2.0 Fortran Source Code
  • From: Paul Van Delst
• Re: Terminator 2.0 Fortran Source Code
  • From: Rich Townsend
• Re: What is the Best Way to handle Optional Arguments with Default Values?
  • From: Dick Hendrickson
• Re: Terminator 2.0 Fortran Source Code
  • From: [JvO]
• Re: What is the Best Way to handle Optional Arguments with Default Values?
  • From: [JvO]
• Re: Halt execution procedure
  • From: Dick Hendrickson
• Re: ADVANCE='no' and complex variables
  • From: [JvO]
• What is the Best Way to handle Optional Arguments with Default Values?
  • From: NuclearWizard
• ADVANCE='no' and complex variables
  • From: Rich Townsend
• Re: Off topid: finite element vs finite volume
  • From: Arjen Markus
• Re: LF95 5.70f and integer exponentiation
  • From: Herman D . Knoble
• Re: Off topid: finite element vs finite volume
  • From: Tim Prince
• Re: Off topid: finite element vs finite volume
  • From: Tim Prince
• Re: LF95 5.70f and integer exponentiation
  • From: Kay Diederichs
• Re: Off topid: finite element vs finite volume
  • From: Phony Account
• Re: Counter with continuosly changing value
  • From: Rich Townsend
• Re: Halt execution procedure
  • From: Jan Vorbrüggen
• Re: Off topid: finite element vs finite volume
  • From: Arjen Markus
• Re: Counter with continuosly changing value
  • From: kia
• Re: Counter with continuosly changing value
  • From: Richard E Maine
• Re: How to Clear Memory in Fortran 90/95
  • From: Ryo
• Re: Fortran source code reformatter
  • From: Ira Baxter
• Re: grammar for fortran language
  • From: Ira Baxter
• Re: Counter with continuosly changing value
  • From: NuclearWizard
• Re: Halt execution procedure
  • From: Richard E Maine
• Re: Halt execution procedure
  • From: NuclearWizard
• Re: private pointer derived data type members
  • From: Levent
• Re: private pointer derived data type members
  • From: Dick Hendrickson
• Re: private pointer derived data type members
  • From: Levent
• Re: Halt execution procedure
  • From: NuclearWizard
• Re: private pointer derived data type members
  • From: Paul Van Delst
• private pointer derived data type members
  • From: Levent
• Re: ifort and CVF
  • From: AlokSharma
• Re: LF95 5.70f and integer exponentiation
  • From: James Van Buskirk
• Re: Terminator 2.0 Fortran Source Code
  • From: Steven G. Kargl
• Terminator 2.0 Fortran Source Code
  • From: BTU Bill
• Re: How to Clear Memory in Fortran 90/95
  • From: glen herrmannsfeldt
• Re: Off topid: finite element vs finite volume
  • From: glen herrmannsfeldt
• Re: "The Terminator" Fortran routine
  • From: glen herrmannsfeldt
• Re: LF95 5.70f and integer exponentiation
  • From: i . chivers
• Re: Halt execution procedure
  • From: Paul Van Delst
• Re: "The Terminator" Fortran routine
  • From: BTU Bill
• Re: LF95 5.70f and integer exponentiation
  • From: i . chivers
• Re: mystery equation "tanfunc"
  • From: Ron Fowler
• Re: Halt execution procedure
  • From: Richard E Maine
• Re: Halt execution procedure
  • From: Richard E Maine
• Re: Halt execution procedure
  • From: NuclearWizard
• Re: Lowercase
  • From: Richard E Maine
• Re: Halt execution procedure
  • From: Richard E Maine
• Re: Halt execution procedure
  • From: NuclearWizard
• Re: "The Terminator" Fortran routine
  • From: BTU Bill
• Re: "The Terminator" Fortran routine
  • From: BTU Bill
• Re: "The Terminator" Fortran routine
  • From: BTU Bill
• Re: "The Terminator" Fortran routine
  • From: BTU Bill
• Re: Off topid: finite element vs finite volume
  • From: s . c . kramer
• mystery equation "tanfunc"
  • From: Al
• Re: Counter with continuosly changing value
  • From: David Frank
• Re: Intel nonVisual fortran
  • From: Haje Korth
• Re: Counter with continuosly changing value
  • From: Dick Russell
• Re: LF95 5.70f and integer exponentiation - jvbtest.out (1/1)
  • From: Herman D . Knoble
• Re: LF95 5.70f and integer exponentiation - jvbtest.out (0/1)
  • From: Herman D . Knoble
• Re: LF95 5.70f and integer exponentiation
  • From: Herman D . Knoble
• Counter with continuosly changing value
  • From: Dimitris K Fidaros
• Re: How to Clear Memory in Fortran 90/95
  • From: beliavsky
• Re: Halt execution procedure
  • From: Jan Vorbrüggen
• Re: Halt execution procedure
  • From: Jan Vorbrüggen
• Re: Intel nonVisual fortran
  • From: Jan Vorbrüggen
• Re: How to Clear Memory in Fortran 90/95
  • From: Bart Vandewoestyne
• RE: mystery equation "tanfunc"
  • From: meek
• Re: Lowercase
  • From: Arjen Markus
• Re: Off topid: finite element vs finite volume
  • From: Arjen Markus
• Re: How to Clear Memory in Fortran 90/95
  • From: glen herrmannsfeldt
• Re: Off topid: finite element vs finite volume
  • From: Gib Bogle
• How to Clear Memory in Fortran 90/95
  • From: akang
• Re: Lowercase
  • From: Ron Shepard
• Re: Intel nonVisual fortran
  • From: Tim Prince
• Re: "The Terminator" Fortran routine
  • From: Tim Prince
• Re: I need some help with a research project
  • From: Ken Plotkin
• Re: Lowercase
  • From: Richard E Maine
• Re: Halt execution procedure
  • From: glen herrmannsfeldt
• Re: Lowercase
  • From: Paul Van Delst
• Re: Halt execution procedure
  • From: Paul Van Delst
• Re: Halt execution procedure
  • From: Richard E Maine
• LF95 5.70f and integer exponentiation
  • From: James Van Buskirk
• Re: Halt execution procedure
  • From: Richard E Maine
• Re: Halt execution procedure
  • From: James Van Buskirk
• Re: Halt execution procedure
  • From: Richard E Maine
• Re: "The Terminator" Fortran routine
  • From: e p chandler
• Re: Lowercase
  • From: Greg Lindahl
• Re: Halt execution procedure
  • From: NuclearWizard
• Intel nonVisual fortran
  • From: bvoh
• Re: "The Terminator" Fortran routine
  • From: Michael Metcalf
• Re: "The Terminator" Fortran routine
  • From: Jon Harrop
• Re: I need some help with a research project
  • From: glen herrmannsfeldt
• "The Terminator" Fortran routine
  • From: BTU Bill
• Re: I need some help with a research project
  • From: Kevin G. Rhoads
• Re: I need some help with a research project
  • From: glen herrmannsfeldt
• Re: I need some help with a research project
  • From: BTU Bill
• Re: I need some help with a research project
  • From: BTU Bill
• Re: I need some help with a research project
  • From: BTU Bill
• Re: I need some help with a research project
  • From: BTU Bill
• Re: Allocatable Targets in F90
  • From: cFLRestrict
• Re: Off topid: finite element vs finite volume
  • From: Arjen Markus
• Re: Fortran 2003 features supported
  • From: Steve Lionel
• Re: Q: [visual fortran 6.0] problem with array name
  • From: Pierre Asselin
• Re: Off topid: finite element vs finite volume
  • From: Michael Bader
• Re: Off topid: finite element vs finite volume
  • From: Phony Account
• Re: divide and store the result of a function in two arrays
  • From: David Flower
• Re: I need some help with a research project
  • From: guillem
• Re: Halt execution procedure
  • From: Jan Vorbrüggen
• Re: Allocatable Targets in F90
  • From: Michael Metcalf
• Re: Allocatable Targets in F90
  • From: glen herrmannsfeldt
• Allocatable Targets in F90
  • From: icthiele
• Re: I need some help with a research project
  • From: glen herrmannsfeldt
• Re: F2k8+/- : Direct Access File Record Locking
  • From: Gary L. Scott
• Re: Q: [visual fortran 6.0] problem with array name
  • From: glen herrmannsfeldt
• Re: I need some help with a research project
  • From: Rich Townsend
• Re: Q: [visual fortran 6.0] problem with array name
  • From: Gib Bogle
• Re: I need some help with a research project
  • From: glen herrmannsfeldt
• I need some help with a research project
  • From: whclark2
• Re: Fortran 2003 features supported
  • From: Nonesuch
• Re: why is this happening?
  • From: James Giles
• Re: (nessun oggetto)
  • From: Richard Maine
• Re: why is this happening?
  • From: Richard Maine
• (nessun oggetto)
  • From: TC
• Re: Lowercase
  • From: Walter Spector
• Re: Halt execution procedure
  • From: Walter Spector
• Re: Halt execution procedure
  • From: Paul Van Delst
• Re: divide and store the result of a function in two arrays
  • From: David Frank
• OpenWatcom F77 -- anyone interested in helping to maintain the installer?
  • From: Kevin G. Rhoads
• Re: Lowercase
  • From: John Appleyard
• Re: Lowercase
  • From: Herman D . Knoble
• Re: linking error in FORTRAN 90
  • From: John Mansell
• Re: Lowercase
  • From: John Appleyard
• linking error in FORTRAN 90
  • From: pankajsy17
• Re: Announcing Intel Fortran Compilers 9.0
  • From: Abdul Qat
• Re: divide and store the result of a function in two arrays
  • From: Michael Metcalf
• Re: why is this happening?
  • From: James Giles
• divide and store the result of a function in two arrays
  • From: Kamaraju Kusumanchi
• Re: Halt execution procedure
  • From: glen herrmannsfeldt
• Re: Halt execution procedure
  • From: Walter Spector
• Re: Halt execution procedure
  • From: NuclearWizard
• Re: Announcing Intel Fortran Compilers 9.0
  • From: Ryo
• Re: why is this happening?
  • From: Richard E Maine
• Re: F2k8+/- : Direct Access File Record Locking
  • From: Gary L. Scott
• Re: Halt execution procedure
  • From: NuclearWizard
• Re: Halt execution procedure
  • From: NuclearWizard
• Re: Halt execution procedure
  • From: glen herrmannsfeldt
• Re: F2k8+/- : Direct Access File Record Locking
  • From: Richard E Maine
• Re: Halt execution procedure
  • From: Richard E Maine
• Re: Q: [visual fortran 6.0] problem with array name
  • From: Gib Bogle
• Re: High Level Architecture, message passing, and Fortran
  • From: glen herrmannsfeldt
• Re: Inverse Matrix
  • From: John Doe
• Re: Halt execution procedure
  • From: glen herrmannsfeldt
• Re: Halt execution procedure
  • From: glen herrmannsfeldt
• High Level Architecture, message passing, and Fortran
  • From: mcelhane
• Re: Halt execution procedure
  • From: Paul Van Delst
• Re: [visual fortran 6.0] problem with array name
  • From: Jim
• Re: Announcing Intel Fortran Compilers 9.0
  • From: Steve Lionel
• Re: Halt execution procedure
  • From: NuclearWizard
• Re: Announcing Intel Fortran Compilers 9.0
  • From: Steve Lionel
• Re: F2k8+/- : Direct Access File Record Locking
  • From: glen herrmannsfeldt
• Re: Announcing Intel Fortran Compilers 9.0
  • From: Gordon Sande
• Re: F2k8+/- : Direct Access File Record Locking
  • From: gary . l . scott
• Re: Announcing Intel Fortran Compilers 9.0
  • From: Rich Townsend
• Re: Announcing Intel Fortran Compilers 9.0
  • From: Steve Lionel
• Re: F2k8+/- : Direct Access File Record Locking
  • From: Janne Blomqvist
• Re: Announcing Intel Fortran Compilers 9.0
  • From: Steve Lionel
• Re: F2k8+/- : Direct Access File Record Locking
  • From: Ken Fairfield
• Re: Q: [visual fortran 6.0] problem with array name
  • From: Ken Fairfield
• Re: Q: [visual fortran 6.0] problem with array name
  • From: FJRA
• Re: Q: [visual fortran 6.0] problem with array name
  • From: Duane Bozarth
• Re: Q: [visual fortran 6.0] problem with array name
  • From: Joost
• Re: How can I print .....
  • From: James Giles
• Q: [visual fortran 6.0] problem with array name
  • From: Bernd . Schmitt . News
• Inverse Matrix
  • From: David
• Re: F2k8+/- : Direct Access File Record Locking
  • From: gary . l . scott
• Re: copy colorized fortran in CVF
  • From: Jugoslav Dujic
• Re: Off topid: finite element vs finite volume
  • From: beliavsky
• Re: Lowercase
  • From: Paul Van Delst
• Re: Lowercase
  • From: Herman D . Knoble
• Re: Off topid: finite element vs finite volume
  • From: Arjen Markus
• Re: Off topid: finite element vs finite volume
  • From: Tim Prince
• Re: Returning to shell
  • From: allagappan
• Re: How can I print .....
  • From: Michael Metcalf
• Re: Off topid: finite element vs finite volume
  • From: Arjen Markus
• How can I print .....
  • From: Ciobin
• Off topid: finite element vs finite volume
  • From: Phony Account
• Re: Lowercase
  • From: Arjen Markus
• Re: F2k8+/- : Direct Access File Record Locking
  • From: Jan Vorbrüggen
• Re: why is this happening?
  • From: Jan Vorbrüggen
• Re: Lowercase
  • From: David Flower
• Re: Lowercase
  • From: Arjen Markus
• Re: Lowercase
  • From: David Flower
• Re: Scope
  • From: Dave Thompson
• Re: calling fortran from c++
  • From: Dave Thompson
• Re: why is this happening?
  • From: James Giles
• Re: F2k8+/- : Direct Access File Record Locking
  • From: glen herrmannsfeldt
• Re: why is this happening?
  • From: Rich Townsend
• Re: why is this happening?
  • From: James Giles
• Re: why is this happening?
  • From: Richard E Maine
• Re: F2k8+/- : Direct Access File Record Locking
  • From: Richard E Maine
• Re: F2k8+/- : Direct Access File Record Locking
  • From: Gary L. Scott
• Re: why is this happening?
  • From: James Giles
• Re: Return Type
  • From: Gary L. Scott
• Re: Return Type
  • From: Madhusudan Singh
• Re: Return Type
  • From: Gary L. Scott
• Re: Return Type
  • From: Madhusudan Singh
• F2k8+/- : Direct Access File Record Locking
  • From: Gary L. Scott
• Re: why is this happening?
  • From: Gary L. Scott
• Re: Return Type
  • From: Gary L. Scott
• Re: why is this happening?
  • From: Michael Metcalf
• Re: Return Type
  • From: Abdul Qat
• Re: why is this happening?
  • From: student
• Re: Return Type
  • From: Richard E Maine
• Re: why is this happening?
  • From: glen herrmannsfeldt
• Re: efficiency question: type versus array
  • From: glen herrmannsfeldt
• why is this happening?
  • From: student
• Re: more f77 errors
  • From: student
• Re: more f77 errors
  • From: Tim Prince
• Re: f77 errors
  • From: Tim Prince
• more f77 errors
  • From: student
• f77 errors
  • From: student
• Re: Return Type
  • From: TC
• Re: Return Type
  • From: Joost
• Re: Return Type
  • From: David Frank
• Re: Return Type
  • From: David Frank
• Re: Return Type
  • From: Bart Vandewoestyne
• Re: Lowercase
  • From: Joost
• Return Type
  • From: TC
• Lowercase
  • From: TC
• Re: libfortranposix.so is shipped without SONAME
  • From: Kamaraju Kusumanchi
• Re: BREAK and RETURN
  • From: Duane Bozarth
• Re: Halt execution procedure
  • From: Richard E Maine
• Re: Halt execution procedure
  • From: NuclearWizard
• Re: Announcing Intel Fortran Compilers 9.0
  • From: Ryo
• Re: Announcing Intel Fortran Compilers 9.0
  • From: Steven G. Kargl
• Re: f77 vs f90
  • From: Greg Lindahl
• BREAK and RETURN
  • From: TC
• Re: Fortran source code reformatter
  • From: Herman D . Knoble
• Re: Announcing Intel Fortran Compilers 9.0
  • From: Haje Korth
• Re: Announcing Intel Fortran Compilers 9.0
  • From: Gordon Sande
• Fortran source code reformatter
  • From: E. Robert Tisdale
• Announcing Intel Fortran Compilers 9.0
  • From: Steve Lionel
• Re: f77 vs f90
  • From: David Flower
• Re: copy colorized fortran in CVF
  • From: Tom Micevski
• Re: HELP! READ TEXT FILE
  • From: FJRA
• Re: copy colorized fortran in CVF
  • From: FJRA
• Re: Scope
  • From: Michael Prager
• Re: f77 vs f90
  • From: Joost
• Re: f77 vs f90
  • From: Richard Edgar
• Re: global variables
  • From: Arjen Markus
• Re: global variables
  • From: TC
• Re: truncated lines with gfortran
  • From: Damien MATTEI
• Re: f77 vs f90
  • From: Gordon Sande
• Re: It's stupid but I don't know fortran :-(((
  • From: Bruce Bowler
• Re: f77 vs f90
  • From: FX
• copy colorized fortran in CVF
  • From: Gertjan Spierenburg
• Re: f77 vs f90
  • From: David Flower
• Re: calling fortran from c++
  • From: Oyvind Sylta
• Re: global variables
  • From: Arjen Markus
• Re: f77 vs f90
  • From: FX
• Re: f77 vs f90
  • From: Joost
• Re: calling fortran from c++
  • From: David Frank
• Re: f77 vs f90
  • From: FX
• Re: global variables
  • From: glen herrmannsfeldt
• Re: truncated lines with gfortran
  • From: FX
• truncated lines with gfortran
  • From: Damien MATTEI
• Re: global variables
  • From: Arjen Markus
• Re: f77 vs f90
  • From: Arjen Markus
• Re: f77 vs f90
  • From: Arjen Markus
• global variables
  • From: TC
• Re: f77 vs f90
  • From: Joost
• Re: calling fortran from c++
  • From: Oyvind Sylta
• Re: Fortran 2003 features supported
  • From: robert . corbett
• Re: Intel Visual Fortran 9 released
  • From: Abdul Qat
• Re: templates - generic programming
  • From: Arjen Markus
• Re: It's stupid but I don't know fortran :-(((
  • From: Tim Prince
• Re: f77 vs f90
  • From: Tim Prince
• Re: f77 vs f90
  • From: Greg Lindahl
• Re: f77 vs f90
  • From: Steve Kargl
• Re: Intel Visual Fortran 9 released
  • From: bv
• Re: HELP! READ TEXT FILE
  • From: Richard E Maine
• Re: FORMAT and INDEX problems
  • From: Richard E Maine
• f77 vs f90
  • From: student
• Re: Scope
  • From: Richard E Maine
• Re: FORMAT and INDEX problems
  • From: John Harper
• Re: It's stupid but I don't know fortran :-(((
  • From: Ciobin
• Re: templates - generic programming
  • From: James Van Buskirk
• Re: It's stupid but I don't know fortran :-(((
  • From: Duane Bozarth
• Re: It's stupid but I don't know fortran :-(((
  • From: Ciobin
• Re: It's stupid but I don't know fortran :-(((
  • From: Ciobin
• Re: It's stupid but I don't know fortran :-(((
  • From: Ciobin
• Re: It's stupid but I don't know fortran :-(((
  • From: Ciobin
• Re: templates - generic programming
  • From: Levent
• Re: is this recursive IO ?
  • From: Joost
• Re: It's stupid but I don't know fortran :-(((
  • From: e p chandler
• Re: is this recursive IO ?
  • From: Dick Hendrickson
• Re: Compiler Comparison Updates
  • From: JA
• is this recursive IO ?
  • From: Joost
• Re: It's stupid but I don't know fortran :-(((
  • From: beliavsky
• Re: It's stupid but I don't know fortran :-(((
  • From: Dick Russell
• Re: It's stupid but I don't know fortran :-(((
  • From: FX
• Re: It's stupid but I don't know fortran :-(((
  • From: Duane Bozarth
• Re: templates - generic programming
  • From: beliavsky
• It's stupid but I don't know fortran :-(((
  • From: Ciobin
• Re: hypergeometric function
  • From: Rich Townsend
• Re: hypergeometric function
  • From: Abdul Qat
• Re: hypergeometric function
  • From: bv
• templates - generic programming
  • From: Levent
• Re: HELP! READ TEXT FILE
  • From: FJRA
• Re: Intel Visual Fortran 9 released
  • From: Greg Lindahl
• Re: calling fortran from c++
  • From: David Frank
• Re: Intel Visual Fortran 9 released
  • From: Kamaraju Kusumanchi
• Re: Scope
  • From: Michael Prager
• Re: hypergeometric function
  • From: Joost
• Re: Intel Visual Fortran 9 released
  • From: beliavsky
• Re: hypergeometric function
  • From: Steven G. Kargl
• Re: calling fortran from c++
  • From: Ken Fairfield
• Re: Scope
  • From: Ron Shepard
• Re: Intel Visual Fortran 9 released
  • From: Kamaraju Kusumanchi
• Re: Scope
  • From: Michael Prager
• Re: Scope
  • From: Michael Metcalf
• Re: Scope
  • From: Joost
• Scope
  • From: Michael Prager
• Re: calling fortran from c++
  • From: Jason Nielsen
• Re: Intel Visual Fortran 9 released
  • From: Janne Blomqvist
• Re: Intel Visual Fortran 9 released
  • From: Gary L. Scott
• Re: HELP! READ TEXT FILE
  • From: TC
• Re: HELP! READ TEXT FILE
  • From: David Flower
• Re: HELP! READ TEXT FILE
  • From: FJRA
• Re: calling fortran from c++
  • From: Dick Russell
• Re: Intel Visual Fortran 9 released
  • From: Harald Anlauf
• Re: FORMAT and INDEX problems
  • From: Duane Bozarth
• Re: Compiler Comparison Updates
  • From: beliavsky
• Re: small example for etime/dtime with g77
  • From: Fabian Braennstroem
• Re: small example for etime/dtime with g77
  • From: Fabian Braennstroem
• Re: calling fortran from c++
  • From: Oyvind Sylta
• Re: Intel Visual Fortran 9 released
  • From: Haje Korth
• Re: calling fortran from c++
  • From: Dick Russell
• Re: calling fortran from c++
  • From: Dick Russell
• Re: Intel Visual Fortran 9 released
  • From: Rich Townsend
• Re: Intel Visual Fortran 9 released
  • From: Rich Townsend
• Re: HELP! READ TEXT FILE
  • From: Dr Ivan D. Reid
• Re: hypergeometric function
  • From: David Jones
• calling fortran from c++
  • From: Oyvind Sylta
• Compiler Comparison Updates
  • From: John Appleyard
• Re: hypergeometric function
  • From: Joost
• Re: HELP! READ TEXT FILE
  • From: beliavsky
• Re: hypergeometric function
  • From: Bart Vandewoestyne
• Re: HELP! READ TEXT FILE
  • From: Dr Ivan D. Reid
• Re: FORMAT and INDEX problems
  • From: DrLecter . gulli
• Re: Intel Visual Fortran 9 released
  • From: Fabian Braennstroem
• Re: Intel Visual Fortran 9 released
  • From: Jason Nielsen
• Re: FORMAT and INDEX problems
  • From: David Flower
• Re: FORMAT and INDEX problems
  • From: DrLecter . gulli
• Re: problem with ifort intel fortran compiler
  • From: glen herrmannsfeldt
• Re: efficiency question: type versus array
  • From: Jan Vorbrüggen
• Re: hypergeometric function
  • From: glen herrmannsfeldt
• HELP! READ TEXT FILE
  • From: TC
• Re: Intel Visual Fortran 9 released
  • From: Fabian Braennstroem
• Re: hypergeometric function
  • From: Arjen Markus
• Re: hypergeometric function
  • From: Abdul Qat
• Re: problem with ifort intel fortran compiler
  • From: yuanliu1
• Re: efficiency question: type versus array
  • From: glen herrmannsfeldt
• Re: hypergeometric function
  • From: James Van Buskirk
• Re: efficiency question: type versus array
  • From: Greg Lindahl
• Re: efficiency question: type versus array
  • From: glen herrmannsfeldt
• Re: Intel Visual Fortran 9 released
  • From: PouetPasPoete
• Re: efficiency question: type versus array
  • From: Richard E Maine
• Re: problem with ifort intel fortran compiler
  • From: yuanliu1
• Re: save attribute for derived types
  • From: Richard E Maine
• Re: FORMAT and INDEX problems
  • From: Richard E Maine
• Fortran data --> R (beta testers)
  • From: Michael Prager
• Re: FORMAT and INDEX problems
  • From: FJRA
• Re: FORMAT and INDEX problems
  • From: DrLecter . gulli
• Re: Just use the series -- Re: hypergeometric function
  • From: Bart Vandewoestyne
• Re: FORMAT and INDEX problems
  • From: DrLecter . gulli
• Re: save attribute for derived types
  • From: Joost
• Re: hypergeometric function
  • From: Harald Anlauf
• save attribute for derived types
  • From: Levent
• Just use the series -- Re: hypergeometric function
  • From: Kevin G. Rhoads
• Re: efficiency question: type versus array
  • From: Greg Lindahl
• Re: efficiency question: type versus array
  • From: Ushnish Basu
• Re: efficiency question: type versus array
  • From: glen herrmannsfeldt
• Re: hypergeometric function
  • From: Bart Vandewoestyne
• Re: hypergeometric function
  • From: Kevin G. Rhoads
• Re: Halt execution procedure
  • From: Dick Hendrickson
• Re: efficiency question: type versus array
  • From: Greg Lindahl
• Re: Halt execution procedure
  • From: Dick Hendrickson
• Re: efficiency question: type versus array
  • From: James Van Buskirk
• Re: Halt execution procedure
  • From: NuclearWizard
• Re: efficiency question: type versus array
  • From: Richard E Maine
• Re: Fortran 2003 features supported
  • From: Paul Van Delst
• Re: Fortran 2003 features supported
  • From: Richard E Maine
• Re: problem with ifort intel fortran compiler
  • From: Richard E Maine
• efficiency question: type versus array
  • From: Ushnish Basu
• Re: problem with ifort intel fortran compiler
  • From: Kamaraju Kusumanchi
• Re: hypergeometric function
  • From: James Van Buskirk
• Re: Fortran 2003 features supported
  • From: gary . l . scott
• Re: Halt execution procedure
  • From: Håkan
• problem with ifort intel fortran compiler
  • From: yuanliu1
• Re: hypergeometric function
  • From: Rich Townsend
• Re: hypergeometric function
  • From: Dick Hendrickson
• Re: hypergeometric function
  • From: Richard E Maine
• Re: Fortran 2003 features supported
  • From: Rich Townsend
• Re: Fortran 2003 features supported
  • From: Matthew Halfant
• Re: FORMAT and INDEX problems
  • From: Richard E Maine
• Re: Portability of IOStat values
  • From: Paul Van Delst
• Re: FORMAT and INDEX problems
  • From: David Flower
• Re: FORMAT and INDEX problems
  • From: Duane Bozarth
• Re: Portability of IOStat values
  • From: Walt Brainerd
• FORMAT and INDEX problems
  • From: DrLecter . gulli
• Re: hypergeometric function
  • From: Arjen Markus
• Re: hypergeometric function
  • From: Jan Vorbrüggen
• Re: hypergeometric function
  • From: Rich Townsend
• Re: hypergeometric function
  • From: Bart Vandewoestyne
• Re: hypergeometric function
  • From: Bart Vandewoestyne
• Re: hypergeometric function
  • From: Bart Vandewoestyne
• Re: hypergeometric function
  • From: Bart Vandewoestyne
• Re: hypergeometric function
  • From: Rich Townsend
• Re: hypergeometric function
  • From: Arjen Markus
• Re: hypergeometric function
  • From: Joost
• Re: hypergeometric function
  • From: Arjen Markus
• Re: Intel Visual Fortran 9 released
  • From: David Frank
• Re: hypergeometric function
  • From: Jugoslav Dujic
• Re: hypergeometric function
  • From: Joost
• Re: hypergeometric function
  • From: Harald Anlauf
• Re: hypergeometric function
  • From: Michael Metcalf
• RE: Fortran 2003 features supported
  • From: meek
• hypergeometric function
  • From: Bart Vandewoestyne
• Re: Portability of IOStat values
  • From: Joost
• Re: Portability of IOStat values
  • From: Arjen Markus
• Re: Portability of IOStat values
  • From: David Flower
• Re: bye bye CVF
  • From: j.strand
• Re: small example for etime/dtime with g77
  • From: Tim Prince
• Re: Portability of IOStat values
  • From: Rich Townsend
• Intel Visual Fortran 9 released
  • From: beliavsky
• Re: Portability of IOStat values
  • From: Walt Brainerd
• Re: Portability of IOStat values
  • From: beliavsky
• Re: Portability of IOStat values
  • From: Paul Van Delst
• Re: small example for etime/dtime with g77
  • From: John Harper
• Portability of IOStat values
  • From: Neilen Marais
• Re: Halt execution procedure
  • From: Håkan
• Re: My two cents on Intel Visual Fortran versus ...
  • From: Andy Vaught
• Re: wanted fast routines
  • From: NuclearWizard
• Re: convert array in do loops fortran?
  • From: glen herrmannsfeldt
• Re: Ancient history
  • From: glen herrmannsfeldt
• Re: Halt execution procedure
  • From: NuclearWizard
• Re: small example for etime/dtime with g77
  • From: Fabian Braennstroem
• Re: Halt execution procedure
  • From: Duane Bozarth
• Re: Halt execution procedure
  • From: Rich Townsend
• Re: Halt execution procedure
  • From: Richard E Maine
• Halt execution procedure
  • From: Håkan Lane
• Re: Ancient history
  • From: Richard E Maine
• Re: Ancient history
  • From: Jan Vorbrüggen
• Re: Ancient history
  • From: Nick Maclaren
• Re: convert array in do loops fortran?
  • From: Janne Blomqvist
• Re: Intel compiler
  • From: Herman D . Knoble
• Intel compiler
  • From: giovanniparodi79
• Fortran 90/95 in Live CD Linux?
  • From: akang
• Re: My two cents on Intel Visual Fortran versus ...
  • From: Stig Kildegård Andersen
• Re: small example for etime/dtime with g77
  • From: Fabian Braennstroem
• Re: bye bye CVF
  • From: Ken Plotkin
• Re: Changing MPI compiler
  • From: Tim Prince
• Re: bye bye CVF
  • From: Brooks Moses
• Re: Changing MPI compiler
  • From: Rich Townsend
• Re: Changing MPI compiler
  • From: Greg Lindahl
• Re: My two cents on Intel Visual Fortran versus ...
  • From: Bart Vandewoestyne
• Re: Changing MPI compiler
  • From: Rich Townsend
• Re: Changing MPI compiler
  • From: Richard E Maine
• Re: Changing MPI compiler
  • From: Richard E Maine
• Re: Changing MPI compiler
  • From: Rich Townsend
• Re: Changing MPI compiler
  • From: Greg Lindahl
• Re: Returning to shell
  • From: Kevin G. Rhoads
• Re: Changing MPI compiler
  • From: Richard E Maine
• Re: Returning to shell
  • From: Richard E Maine
• Re: Returning to shell
  • From: jamesgiles@xxxxxxx
• Re: Returning to shell
  • From: allagappan
• Re: My two cents on Intel Visual Fortran versus ...
  • From: Tim Prince
• Re: KIND error?
  • From: Paul Van Delst
• Re: Changing MPI compiler
  • From: Håkan
• Re: KIND error?
  • From: Joost
• Re: Ancient history
  • From: Richard E Maine
• Re: KIND error?
  • From: Paul Van Delst
• Re: Changing MPI compiler
  • From: Tim Prince
• Re: My two cents on Intel Visual Fortran versus ...
  • From: James Van Buskirk
• Re: Something amiss
  • From: Kevin G. Rhoads
• Re: f77 how to link ar libraries to program
  • From: clusardi2k
• Re: f77 how to link ar libraries to program
  • From: clusardi2k
• Changing MPI compiler
  • From: Håkan
• Re: My two cents on Intel Visual Fortran versus ...
  • From: Tim Prince
• Re: My two cents on Intel Visual Fortran versus ...
  • From: Tim Prince
• Re: small example for etime/dtime with g77
  • From: Tim Prince
• Re: forall/where and openmp
  • From: Richard Edgar
• small example for etime/dtime with g77
  • From: Fabian Braennstroem
• Re: My two cents on Intel Visual Fortran versus ...
  • From: Abdul Qat
• Re: My two cents on Intel Visual Fortran versus ...
  • From: James Van Buskirk
• Re: My two cents on Intel Visual Fortran versus ...
  • From: Tim Prince
• Re: convert array in do loops fortran?
  • From: glen herrmannsfeldt
• Re: bye bye IVF (was: bye bye CVF)
  • From: Abdul Qat
• Re: bye bye CVF
  • From: Abdul Qat
• Re: My two cents on Intel Visual Fortran versus ...
  • From: James Van Buskirk
• Re: Returning to shell
  • From: Walt Brainerd
• libfortranposix.so is shipped without SONAME
  • From: Kamaraju Kusumanchi
• Re: Something amiss
  • From: Another Jake
• Re: bye bye CVF
  • From: Abdul Qat
• Re: Returning to shell
  • From: John Harper
• Re: bye bye IVF (was: bye bye CVF)
  • From: Abdul Qat
• Re: Something amiss
  • From: John Harper
• Re: problems with stack management for large runs on beowulf cluster using intel fortran compiler 8.1.024
  • From: Tim Prince
• Re: My two cents on Intel Visual Fortran versus ...
  • From: Tim Prince
• Re: My two cents on Intel Visual Fortran versus ...
  • From: James Van Buskirk
• Re: bye bye CVF
  • From: Gary L. Scott
• Re: testing/timing lapack/blas with xlf (mac os x)
  • From: Ron Shepard
• problems with stack management for large runs on beowulf cluster using intel fortran compiler 8.1.024
  • From: Antonio
• Re: convert array in do loops fortran?
  • From: David Frank
• Re: convert array in do loops fortran?
  • From: akang
• Re: convert array in do loops fortran?
  • From: David Frank
• Re: convert array in do loops fortran?
  • From: Duane Bozarth
• Re: convert array in do loops fortran?
  • From: akang
• Re: convert array in do loops fortran?
  • From: David Frank
• convert array in do loops fortran?
  • From: akang
• Re: Returning to shell
  • From: Joost
• Returning to shell
  • From: allagappan
• Re: bye bye CVF
  • From: Ken Plotkin
• Re: bye bye CVF
  • From: Gary L. Scott
• testing/timing lapack/blas with xlf (mac os x)
  • From: peterp
• bye bye IVF (was: bye bye CVF)
  • From: bv
• Re: bye bye CVF
  • From: Ken Plotkin
• Re: My two cents on Intel Visual Fortran versus ...
  • From: beliavsky
• Re: where vs. forall in f95
  • From: glen herrmannsfeldt
• Re: forall/where and openmp
  • From: Tim Prince
• Re: where vs. forall in f95
  • From: robert . corbett
• Re: forall/where and openmp
  • From: robert . corbett
• Re: My two cents on Intel Visual Fortran versus ...
  • From: James Van Buskirk
• forall/where and openmp
  • From: Ushnish Basu
• Re: Something amiss
  • From: Another Jake
• Re: My two cents on Intel Visual Fortran versus ...
  • From: bv
• Re: My two cents on Intel Visual Fortran versus ...
  • From: beliavsky
• Re: My two cents on Intel Visual Fortran versus ...
  • From: bv
• Re: My two cents on Intel Visual Fortran versus ...
  • From: Stig Kildegård Andersen
• Re: My two cents on Intel Visual Fortran versus ...
  • From: awgreynolds
• Re: I want a good, free, fortran 77 compiler for winXP
  • From: bv
• Re: Something amiss
  • From: beliavsky
• Something amiss
  • From: lone_eagle
• Re: My two cents on Intel Visual Fortran versus ...
  • From: Steve Lionel
• Re: f77 how to link ar libraries to program
  • From: clusardi2k
• Re: f77 how to link ar libraries to program
  • From: Erik Edelmann
• Re: f77 how to link ar libraries to program
  • From: Richard E Maine
• Re: f77 how to link ar libraries to program
  • From: Richard E Maine
• Re: f77 how to link ar libraries to program
  • From: clusardi2k
• Re: f77 how to link ar libraries to program
  • From: Richard E Maine
• Re: f77 how to link ar libraries to program
  • From: clusardi2k
• Re: f77 how to link ar libraries to program
  • From: Erik Edelmann
• Re: f77 how to link ar libraries to program
  • From: clusardi2k
• Re: My two cents on Intel Visual Fortran versus ...
  • From: Brian Wannamaker
• Re: f77 how to link ar libraries to program
  • From: clusardi2k
• Re: f77 how to link ar libraries to program
  • From: clusardi2k
• Re: f77 how to link ar libraries to program
  • From: clusardi2k
• Re: f77 how to link ar libraries to program
  • From: Richard E Maine
• Re: My two cents on Intel Visual Fortran versus ...
  • From: awgreynolds
• f77 how to link ar libraries to program
  • From: clusardi2k
• Re: My two cents on Intel Visual Fortran versus ...
  • From: Abdul Qat
• Re: My two cents on Intel Visual Fortran versus ...
  • From: Rich Townsend
• Re: where vs. forall in f95
  • From: Tim Prince
• Re: My two cents on Intel Visual Fortran versus ...
  • From: Jan Vorbrüggen
• Re: where vs. forall in f95
  • From: glen herrmannsfeldt
• Re: My two cents on Intel Visual Fortran versus ...
  • From: Richard E Maine
• Re: pack function for 2D matrix in fortran?
  • From: glen herrmannsfeldt
• Re: My two cents on Intel Visual Fortran versus ...
  • From: awgreynolds
• Re: pack function for 2D matrix in fortran?
  • From: akang
• Re: My two cents on Intel Visual Fortran versus ...
  • From: Steve Lionel
• Re: My two cents on Intel Visual Fortran versus ...
  • From: Steve Lionel
• Re: My two cents on Intel Visual Fortran versus ...
  • From: Herman D . Knoble
• Re: pack function for 2D matrix in fortran?
  • From: Arjen Markus
• Re: SGI DATE_AND_TIME Unresolved text symbol
  • From: clusardi2k
• Re: pack function for 2D matrix in fortran?
  • From: akang
• Re: My two cents on Intel Visual Fortran versus ...
  • From: Umberto D'Ortona
• Re: writing \ character
  • From: Patrick Begou
• Re: g95 Fortran compiler on AMD opteron running SUN Solaris 10
  • From: robert . corbett
• Re: g95 Fortran compiler on AMD opteron running SUN Solaris 10
  • From: Joost
• Re: Fortran 90/95 standard?
  • From: robert . corbett
• Re: where vs. forall in f95
  • From: robert . corbett
• Re: g95 Fortran compiler on AMD opteron running SUN Solaris 10
  • From: robert . corbett
• Re: My two cents on Intel Visual Fortran versus ...
  • From: Richard Maine
• g95 Fortran compiler on AMD opteron running SUN Solaris 10
  • From: Andry William
• where vs. forall in f95
  • From: Ushnish Basu
• Re: My two cents on Intel Visual Fortran versus ...
  • From: awgreynolds
• Re: make: *** No rule to make target `inc/myProgram.inc'
  • From: Al
• Re: writing \ character
  • From: John Harper
• Re: writing about 100 colomns of real data into text file
  • From: jamesgiles@xxxxxxx
• Re: writing about 100 colomns of real data into text file
  • From: Richard E Maine
• Re: writing about 100 colomns of real data into text file
  • From: jamesgiles@xxxxxxx
• Re: writing about 100 colomns of real data into text file
  • From: jamesgiles@xxxxxxx
• Re: writing about 100 colomns of real data into text file
  • From: glen herrmannsfeldt
• Re: writing about 100 colomns of real data into text file
  • From: Richard E Maine
• Re: writing about 100 colomns of real data into text file
  • From: jamesgiles@xxxxxxx
• Re: writing about 100 colomns of real data into text file
  • From: glen herrmannsfeldt
• Re: Fortran 90/95 standard?
  • From: Richard E Maine
• Re: My two cents on Intel Visual Fortran versus ...
  • From: Richard E Maine
• Re: writing about 100 colomns of real data into text file
  • From: glen herrmannsfeldt
• Re: bye bye CVF
  • From: kia
• Re: pack function for 2D matrix in fortran?
  • From: glen herrmannsfeldt
• Re: make: *** No rule to make target `inc/myProgram.inc'
  • From: Janne Blomqvist
• Re: 99. not 99.0
  • From: Jim
• My two cents on Intel Visual Fortran versus ...
  • From: awgreynolds
• Re: Fortran 90/95 standard?
  • From: wclodius
• Re: Fortran 90/95 standard?
  • From: Bart Vandewoestyne
• Re: make: *** No rule to make target `inc/myProgram.inc'
  • From: Al
• Re: make: *** No rule to make target `inc/myProgram.inc'
  • From: Al
• Re: make: *** No rule to make target `inc/myProgram.inc'
  • From: Al
• Re: writing \ character
  • From: Richard E Maine
• Re: make: *** No rule to make target `inc/myProgram.inc'
  • From: Al
• Re: bye bye CVF
  • From: Abdul Qat
• Re: writing about 100 colomns of real data into text file
  • From: Richard E Maine
• Re: cholesky decompostion and inverses of upper diagonal matrices
  • From: Abdul Qat
• Re: Fortran 90/95 standard?
  • From: Richard E Maine
• Re: writing about 100 colomns of real data into text file
  • From: jamesgiles@xxxxxxx
• Re: writing \ character
  • From: Joost
• Re: pack function for 2D matrix in fortran?
  • From: Rich Townsend
• Re: make: *** No rule to make target `inc/myProgram.inc'
  • From: Erik Edelmann
• Re: make: *** No rule to make target `inc/myProgram.inc'
  • From: Erik Edelmann
• writing \ character
  • From: Patrick Begou
• Re: pack function for 2D matrix in fortran?
  • From: Arjen Markus
• pack function for 2D matrix in fortran?
  • From: akang
• Re: make: *** No rule to make target `inc/myProgram.inc'
  • From: Al
• Re: bye bye CVF
  • From: Abdul Qat
• Re: SGI DATE_AND_TIME Unresolved text symbol
  • From: Walter Spector
• Re: bye bye CVF
  • From: Steve Lionel
• Re: cholesky decompostion and inverses of upper diagonal matrices
  • From: Rich Townsend
• Re: Fortran 90/95 standard?
  • From: beliavsky
• Re: writing about 100 colomns of real data into text file
  • From: Bart Vandewoestyne
• Re: Fortran 90/95 standard?
  • From: Joost
• Fortran 90/95 standard?
  • From: Bart Vandewoestyne
• Modules, libraries and CVF
  • From: c_inquisitor
• Re: writing about 100 colomns of real data into text file
  • From: Jan Vorbrüggen
• Re: writing about 100 colomns of real data into text file
  • From: Bart Vandewoestyne
• Re: writing about 100 colomns of real data into text file
  • From: Bart Vandewoestyne
• Re: cholesky decompostion and inverses of upper diagonal matrices
  • From: Greg Lindahl
• RE: I want a good, free, fortran 77 compiler for winXP
  • From: meek
• Re: make: *** No rule to make target `inc/myProgram.inc'
  • From: Michel OLAGNON
• Re: cholesky decompostion and inverses of upper diagonal matrices
  • From: David Frank
• Re: 99. not 99.0
  • From: Arjen Markus
• Re: wanted fast routines
  • From: Arjen Markus
• Re: make: *** No rule to make target `inc/myProgram.inc'
  • From: Ron Shepard
• Re: SGI DATE_AND_TIME Unresolved text symbol
  • From: Tim Prince
• Re: I want a good, free, fortran 77 compiler for winXP
  • From: bv
• Re: writing about 100 colomns of real data into text file
  • From: Richard Maine
• Re: writing about 100 colomns of real data into text file
  • From: FJRA
• Re: writing about 100 colomns of real data into text file
  • From: jamesgiles@xxxxxxx
• Re: writing about 100 colomns of real data into text file
  • From: glen herrmannsfeldt
• Re: bye bye CVF
  • From: Richard E Maine
• Re: writing about 100 colomns of real data into text file
  • From: Richard E Maine
• Re: bye bye CVF
  • From: Abdul Qat
• Re: bye bye CVF
  • From: Abdul Qat
• Re: writing about 100 colomns of real data into text file
  • From: glen herrmannsfeldt
• Re: bye bye CVF
  • From: Steve Lionel
• Re: cholesky decompostion and inverses of upper diagonal matrices
  • From: Rich Townsend
• Re: cholesky decompostion and inverses of upper diagonal matrices
  • From: Janne Blomqvist
• Re: writing about 100 colomns of real data into text file
  • From: Bart Vandewoestyne
• Re: 99. not 99.0
  • From: Dick Hendrickson
• Re: writing about 100 colomns of real data into text file
  • From: Bart Vandewoestyne
• Re: wanted fast routines
  • From: Greg Lindahl
• Re: make: *** No rule to make target `inc/myProgram.inc'
  • From: Richard E Maine
• Re: writing about 100 colomns of real data into text file
  • From: Richard E Maine
• Re: writing about 100 colomns of real data into text file
  • From: FJRA
• Re: 99. not 99.0
  • From: jamesgiles@xxxxxxx
• writing about 100 colomns of real data into text file
  • From: Bart Vandewoestyne
• Re: cholesky decompostion and inverses of upper diagonal matrices
  • From: Rich Townsend
• Re: cholesky decompostion and inverses of upper diagonal matrices
  • From: David Frank
• Re: cholesky decompostion and inverses of upper diagonal matrices
  • From: Rich Townsend
• Re: 99. not 99.0
  • From: Richard E Maine
• 99. not 99.0
  • From: Al
• Re: wanted fast routines
  • From: Rich Townsend
• Re: SGI DATE_AND_TIME Unresolved text symbol
  • From: Richard E Maine
• Re: SGI DATE_AND_TIME Unresolved text symbol
  • From: clusardi2k
• Re: SGI DATE_AND_TIME Unresolved text symbol
  • From: clusardi2k
• Re: make: *** No rule to make target `inc/myProgram.inc'
  • From: Al
• Re: cholesky decompostion and inverses of upper diagonal matrices
  • From: Victor Eijkhout
• Re: I want a good, free, fortran 77 compiler for winXP
  • From: Richard E Maine
• Re: bye bye CVF
  • From: Abdul Qat
• Re: wanted fast routines
  • From: James Van Buskirk
• Re: wanted fast routines
  • From: Rich Townsend
• Re: wanted fast routines
  • From: Rich Townsend
• Re: make: *** No rule to make target `inc/myProgram.inc'
  • From: Ron Shepard
• Re: I want a good, free, fortran 77 compiler for winXP
  • From: beliavsky
• Re: SGI DATE_AND_TIME Unresolved text symbol
  • From: Richard E Maine
• Re: SGI DATE_AND_TIME Unresolved text symbol
  • From: Dr Ivan D. Reid
• Re: I want a good, free, fortran 77 compiler for winXP
  • From: Rich Townsend
• Re: make: *** No rule to make target `inc/myProgram.inc'
  • From: Michel OLAGNON
• Re: I want a good, free, fortran 77 compiler for winXP
  • From: beliavsky
• Re: I want a good, free, fortran 77 compiler for winXP
  • From: Gordo
• SGI DATE_AND_TIME Unresolved text symbol
  • From: clusardi2k
• Re: cholesky decompostion and inverses of upper diagonal matrices
  • From: David Frank
• Re: wanted fast routines
  • From: David Frank
• Re: wanted fast routines
  • From: David Frank
• make: *** No rule to make target `inc/myProgram.inc'
  • From: Al
• Re: Fortran functions
  • From: Arjen Markus
• Re: I want a good, free, fortran 77 compiler for winXP
  • From: Arjen Markus
• RE: I want a good, free, fortran 77 compiler for winXP
  • From: meek
• Re: You are my hope. Please
  • From: beliavsky
• Re: wanted fast routines
  • From: glen herrmannsfeldt
• Re: cholesky decompostion and inverses of upper diagonal matrices
  • From: Salvatore
• RE: I want a good, free, fortran 77 compiler for winXP
  • From: meek
• Re: wanted fast routines
  • From: David Frank
• Re: gains from vectorization
  • From: Bart Vandewoestyne
• Re: gains from vectorization
  • From: Ian Bush
• RE: I want a good, free, fortran 77 compiler for winXP
  • From: meek
• Re: GUI Build with Tcl/Tk vs. Winteracter/GINO
  • From: Arjen Markus
• Re: Interpreting Profiler Report
  • From: Joost
• Re: You are my hope. Please
  • From: Ryo
• Re: gains from vectorization
  • From: Joost
• Re: Interpreting Profiler Report
  • From: Tim Prince
• Re: Interpreting Profiler Report
  • From: student
• Re: Interpreting Profiler Report
  • From: Tim Prince
• Re: gains from vectorization
  • From: Tim Prince
• Re: You are my hope. Please
  • From: e p chandler
• Re: Fortran functions
  • From: Tim Prince
• Re: bye bye CVF
  • From: Gary L. Scott
• Interpreting Profiler Report
  • From: student
• Re: gains from vectorization
  • From: student
• Re: gains from vectorization
  • From: Joost
• Re: gains from vectorization
  • From: Joost
• Re: gains from vectorization
  • From: Rich Townsend
• Re: You are my hope. Please
  • From: Steven G. Kargl
• Re: You are my hope. Please
  • From: Ciobin
• makefile with include files
  • From: Al
• Re: You are my hope. Please
  • From: Steven G. Kargl
• Re: wanted fast routines
  • From: NuclearWizard
• Re: gains from vectorization
  • From: Steven G. Kargl
• Re: wanted fast routines
  • From: NuclearWizard
• You are my hope. Please
  • From: Ciobin
• Re: f90gl
  • From: NuclearWizard
• Re: gains from vectorization
  • From: Bart Vandewoestyne
• Re: gains from vectorization
  • From: student
• Re: gains from vectorization
  • From: Steven G. Kargl
• Re: gains from vectorization
  • From: student
• Re: writing to files
  • From: glen herrmannsfeldt
• Re: Problem while compiling
  • From: beatdown
• Re: writing to files
  • From: Richard E Maine
• Re: gains from vectorization
  • From: Ronald Benedik
• Re: gains from vectorization
  • From: Steven G. Kargl
• Re: SGI: What is this END, puzzled
  • From: beliavsky
• Re: writing to files
  • From: icymist
• SGI: What is this END, puzzled
  • From: clusardi2k
• SGI: What is this END, puzzled
  • From: clusardi2k
• Re: cholesky decompostion and inverses of upper diagonal matrices
  • From: jon
• Re: DATA Statement syntax question
  • From: glen herrmannsfeldt
• Re: gains from vectorization
  • From: student
• Re: DATA Statement syntax question
  • From: cgilley
• Re: writing to files
  • From: Richard E Maine
• Re: gains from vectorization
  • From: Joost
• Re: DATA Statement syntax question
  • From: robert . corbett
• Re: gains from vectorization
  • From: student
• Re: Problem while compiling
  • From: Richard E Maine
• Re: gains from vectorization
  • From: Steven G. Kargl
• Re: writing to files
  • From: glen herrmannsfeldt
• Re: DATA Statement syntax question
  • From: cgilley
• cholesky decompostion and inverses of upper diagonal matrices
  • From: student
• gains from vectorization
  • From: student
• Re: DATA Statement syntax question
  • From: glen herrmannsfeldt
• Re: Problem while compiling
  • From: glen herrmannsfeldt
• Re: Fortran functions
  • From: glen herrmannsfeldt
• Re: writing to files
  • From: Richard E Maine
• Re: DATA Statement syntax question
  • From: Richard E Maine
• writing to files
  • From: icymist
• Re: wanted fast routines
  • From: Dick Hendrickson
• Re: DATA Statement syntax question
  • From: Jan Vorbrüggen
• DATA Statement syntax question
  • From: cgilley
• Re: Problem while compiling
  • From: Richard E Maine
• Re: wanted fast routines
  • From: Richard E Maine
• Re: writing data to file
  • From: Richard E Maine
• Re: f90gl
  • From: Steve Lionel
• Re: Intel Fortran on Mac?
  • From: Steve Lionel
• writing data to file
  • From: icymist
• Re: Fortran functions
  • From: Tim Prince
• Re: Some misc fortran advice please - cranking warnings, interpreting an error, lint, TotalView?
  • From: beliavsky
• Re: f90gl
  • From: Jan Vorbrüggen
• Re: bye bye CVF
  • From: Abdul Qat
• Re: bye bye CVF
  • From: Abdul Qat
• Re: bye bye CVF
  • From: Abdul Qat
• Re: Intel Fortran on Mac?
  • From: FX
• Re: Good compilable langauge for math and graphics?
  • From: Jon Harrop
• Re: Problem while compiling
  • From: James Van Buskirk
• Re: charting
  • From: Abdul Qat
• Re: Problem while compiling
  • From: Alois Steindl
• Re: Problem while compiling
  • From: David Flower
• Re: read tektronix .wfm file
  • From: Jugoslav Dujic
• Re: read tektronix .wfm file
  • From: Jugoslav Dujic
• Re: wanted fast routines
  • From: Greg Lindahl
• Re: Fortran functions
  • From: robert . corbett
• Some misc fortran advice please - cranking warnings, interpreting an error, lint, TotalView?
  • From: Dan Stromberg
• Re: Fortran functions
  • From: robert . corbett
• Re: Intel Fortran on Mac?
  • From: Ron Shepard
• Re: wanted fast routines
  • From: jamesgiles
• f90gl
  • From: NuclearWizard
• Re: wanted fast routines
  • From: NuclearWizard
• Re: Good compilable langauge for math and graphics?
  • From: Rich Townsend
• Re: Good compilable langauge for math and graphics?
  • From: Rich Townsend
• Re: Problem while compiling
  • From: James Van Buskirk
• Re: KIND error?
  • From: James Van Buskirk
• Re: Problem while compiling
  • From: beliavsky
• Re: Good compilable langauge for math and graphics?
  • From: glen herrmannsfeldt
• Problem while compiling
  • From: beatdown
• Re: Good compilable langauge for math and graphics?
  • From: Richard E Maine
• Re: KIND error?
  • From: John Harper
• Re: Intel Fortran on Mac?
  • From: Brooks Moses
• Re: Good compilable langauge for math and graphics?
  • From: Jon Harrop
• Re: Good compilable langauge for math and graphics?
  • From: Jon Harrop
• Re: Good compilable langauge for math and graphics?
  • From: Jon Harrop
• Intel Fortran on Mac?
  • From: Richard E Maine
• Re: http site text-only read possible?
  • From: Janne Blomqvist
• Re: http site text-only read possible?
  • From: Dr Ivan D. Reid
• read tektronix .wfm file
  • From: wiggy13
• Re: wanted fast routines
  • From: glen herrmannsfeldt
• Re: http site text-only read possible?
  • From: e p chandler
• Re: Fortran functions
  • From: Bart Vandewoestyne
• Re: http site text-only read possible?
  • From: Harold Stevens
• Re: http site text-only read possible?
  • From: Bart Vandewoestyne
• Re: wanted fast routines
  • From: Richard E Maine
• Re: http site text-only read possible?
  • From: David Frank
• Re: Fortran functions
  • From: glen herrmannsfeldt
• Re: http site text-only read possible?
  • From: David Frank
• Re: Fortran functions
  • From: James Van Buskirk
• Re: http site text-only read possible?
  • From: Dr Ivan D. Reid
• Re: http site text-only read possible?
  • From: Janne Blomqvist
• Re: wanted fast routines
  • From: David Frank
• http site text-only read possible?
  • From: David Frank
• GUI Build with Tcl/Tk vs. Winteracter/GINO
  • From: tornado Jeff
• Re: wanted fast routines
  • From: FJRA
• Re: wanted fast routines
  • From: Giorgio Pastore
• Re: Fortran functions
  • From: Charles Russell
• Re: Fortran functions
  • From: Tim Prince
• Re: Fortran functions
  • From: Dieter Britz
• Re: Fortran functions
  • From: David Frank
• Re: wanted fast routines
  • From: David Frank
• Re: Fortran functions
  • From: Arjen Markus
• Fortran functions
  • From: Dieter Britz
• relative optimas
  • From: Baloff
• charting
  • From: Baloff
• Re: wanted fast routines
  • From: glen herrmannsfeldt
• Re: wanted fast routines
  • From: Tim Prince
• Re: wanted fast routines
  • From: Rich Townsend
• Re: wanted fast routines
  • From: Brooks Moses
• Re: wanted fast routines
  • From: Steven G. Kargl
• wanted fast routines
  • From: student
• Re: KIND error?
  • From: James Van Buskirk
• Re: KIND error?
  • From: student
• Re: Printing newlines
  • From: Rich Townsend
• Re: Good compilable langauge for math and graphics?
  • From: Rich Townsend
• Re: KIND error?
  • From: Tim Prince
• Re: relative optimas
  • From: Michael Metcalf
• Re: relative optimas
  • From: James Van Buskirk
• KIND error?
  • From: student
• Re: relative optimas
  • From: Michael Metcalf
• Re: Printing newlines
  • From: Leif Harcke
• Re: Move/problem
  • From: Madhusudan Singh
• Move/problem
  • From: Michael Metcalf
• Re: "Compaq FORTRAN ver. 7.0" misprint?
  • From: Gary L. Scott
• Re: "Compaq FORTRAN ver. 7.0" misprint?
  • From: e p chandler
• Re: bye bye CVF
  • From: Gary L. Scott
• Re: "Compaq FORTRAN ver. 7.0" misprint?
  • From: Gary L. Scott
• Re: bye bye CVF
  • From: glen herrmannsfeldt
• "Compaq FORTRAN ver. 7.0" misprint?
  • From: awgreynolds
• Re: bye bye CVF
  • From: Gary L. Scott
• Re: Good compilable langauge for math and graphics?
  • From: Richard E Maine
• Re: bye bye CVF
  • From: Tim Prince
• Re: F95 question: non-standard code or gfortran bug?
  • From: Dr Ivan D. Reid
• Re: Good compilable langauge for math and graphics?
  • From: Jon Harrop
• Re: bye bye CVF
  • From: glen herrmannsfeldt
• Re: bye bye CVF
  • From: Ken Plotkin
• Re: Good compilable langauge for math and graphics?
  • From: Jon Harrop
• Re: F95 question: non-standard code or gfortran bug?
  • From: Steven G. Kargl
• F95 question: non-standard code or gfortran bug?
  • From: Dr Ivan D. Reid
• Re: bye bye CVF
  • From: bv
• Re: creating directories on the fly
  • From: Bart Vandewoestyne
• Re: Zero-size array literals
  • From: Andy Vaught
• Re: creating directories on the fly
  • From: Richard E Maine
• Re: Zero-size array literals
  • From: Richard E Maine
• Re: creating directories on the fly
  • From: Jan Vorbrüggen
• Re: bye bye CVF
  • From: Steve Lionel
• Re: creating directories on the fly
  • From: Walt Brainerd
• Re: creating directories on the fly
  • From: David Flower
• Re: A few quick questions about gfortran under cygwin
  • From: Dr Ivan D. Reid
• Re: Improve efficiency of 3 big array ops.
  • From: Dr Ivan D. Reid
• Re: creating directories on the fly
  • From: Bart Vandewoestyne
• Re: bye bye CVF
  • From: Abdul Qat
• Re: something like MS Visual Studio for Fortran?
  • From: Abdul Qat
• Re: Good compilable langauge for math and graphics?
  • From: Abdul Qat
• Re: bye bye CVF
  • From: Phillip Helbig---remove CLOTHES to reply
• Re: bye bye CVF
  • From: Abdul Qat
• bye bye CVF
  • From: Walt Brainerd
• Re: Zero-size array literals
  • From: Walt Brainerd
• Re: Zero-size array literals
  • From: Dave Seaman
• Zero-size array literals
  • From: Rich Townsend
• Re: Fortran Code or Algorithm for Polygon Clipping ?
  • From: Aidan
• Re: creating directories on the fly
  • From: Steven G. Kargl
• Re: creating directories on the fly
  • From: Bart Vandewoestyne
• Re: Tiger OS X 10.4 Big Fortran Problem
  • From: Andy Vaught
• Re: Compilator Fortran
  • From: Walt Brainerd
• Re: Compilator Fortran
  • From: Herman D . Knoble
• Re: Fortran book advertisement
  • From: Walt Brainerd
• Re: Compilator Fortran
  • From: Herman D . Knoble
• Re: Compilator Fortran
  • From: Ciobin
• Re: Compilator Fortran
  • From: Herman D . Knoble
• Re: Fortran book advertisement
  • From: Andy Spragg
• Compilator Fortran
  • From: Ciobin
• Re: Tiger OS X 10.4 Big Fortran Problem
  • From: Richard E Maine
• Re: Fortran Code or Algorithm for Polygon Clipping ?
  • From: FJRA
• Fortran Code or Algorithm for Polygon Clipping ?
  • From: Klemens Barfus
• Re: implementation of DACOSD
  • From: Jan Vorbrüggen
• Re: A few quick questions about gfortran under cygwin
  • From: Walter Spector
• Re: A few quick questions about gfortran under cygwin
  • From: Brooks Moses
• Re: Printing newlines
  • From: Michael Gray
• Re: Tiger OS X 10.4 Big Fortran Problem
  • From: c. konig
• Re: Printing newlines
  • From: glen herrmannsfeldt
• Re: Improve efficiency of 3 big array ops.
  • From: glen herrmannsfeldt
• Re: Printing newlines
  • From: Duane Bozarth
• Re: implementation of DACOSD
  • From: glen herrmannsfeldt
• Re: something like MS Visual Studio for Fortran?
  • From: bv
• Printing newlines
  • From: Jon Harrop
• Re: Improve efficiency of 3 big array ops.
  • From: Christoph Arns
• Re: implementation of DACOSD
  • From: Ken Fairfield
• Re: Fortran and simple tree recursion
  • From: Dr Ivan D. Reid
• Re: creating directories on the fly
  • From: Richard E Maine
• Re: creating directories on the fly
  • From: Bart Vandewoestyne
• Re: Improve efficiency of 3 big array ops.
  • From: Richard E Maine
• Re: Improve efficiency of 3 big array ops.
  • From: Greg Lindahl
• Re: Improve efficiency of 3 big array ops.
  • From: Joost
• Re: Improve efficiency of 3 big array ops.
  • From: Dr Ivan D. Reid
• Re: creating directories on the fly
  • From: Madhusudan Singh
• Re: Improve efficiency of 3 big array ops.
  • From: andy2O
• Re: A few quick questions about gfortran under cygwin
  • From: Steven G. Kargl
• Re: Improve efficiency of 3 big array ops.
  • From: andy2O
• Re: Improve efficiency of 3 big array ops.
  • From: Greg Lindahl
• Re: Improve efficiency of 3 big array ops.
  • From: Joost
• Re: Improve efficiency of 3 big array ops.
  • From: beliavsky
• Re: creating directories on the fly
  • From: Walter Spector
• Re: creating directories on the fly
  • From: Walt Brainerd
• creating directories on the fly
  • From: Bart Vandewoestyne
• Re: A few quick questions about gfortran under cygwin
  • From: Walter Spector
• Re: Improve efficiency of 3 big array ops.
  • From: Tim Prince
• Re: Improve efficiency of 3 big array ops.
  • From: Michel OLAGNON
• Re: Improve efficiency of 3 big array ops.
  • From: Michel OLAGNON
• Re: Improve efficiency of 3 big array ops.
  • From: Michel OLAGNON
• Re: implementation of DACOSD
  • From: Michel OLAGNON
• Improve efficiency of 3 big array ops.
  • From: andy2O
• Re: implementation of DACOSD
  • From: Damien MATTEI
• Re: A few quick questions about gfortran under cygwin
  • From: Dr Ivan D. Reid
• Re: A few quick questions about gfortran under cygwin
  • From: Tim Prince
• A few quick questions about gfortran under cygwin
  • From: Dr Ivan D. Reid

• Security
• UNIX
• Linux
• Coding
• Usenet

• Archive
• About
• Privacy
• Search
• Imprint

coding.derkeiler.com  > Archive  > Fortran  > comp.lang.fortran  > 2005-06