comp.lang.fortran

• Date Index

---

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