comp.lang.fortran

• Date Index

---

• fortran code for 'cp' / subroutine file_copy, Carsten Lemmen
  • Re: fortran code for 'cp' / subroutine file_copy, Arjen Markus
  • RE: fortran code for 'cp' / subroutine file_copy, meek
    • Re: fortran code for 'cp' / subroutine file_copy, Joost
      • Re: fortran code for 'cp' / subroutine file_copy, Walter Spector
      • Re: fortran code for 'cp' / subroutine file_copy, Janne Blomqvist
      • Re: fortran code for 'cp' / subroutine file_copy, Joost
    • Re: fortran code for 'cp' / subroutine file_copy, Joe Krahn
  • Re: fortran code for 'cp' / subroutine file_copy, Richard E Maine
• question on character-like variable defination, sunnylele
  • Re: question on character-like variable defination, James Giles
    • Re: question on character-like variable defination, robert . corbett
      • Re: question on character-like variable defination, James Giles
  • RE: question on character-like variable defination, meek
    • Re: question on character-like variable defination, Richard E Maine
• O/T: Patenting a computational scheme?, AN O'Nymous
  • Re: O/T: Patenting a computational scheme?, Richard Maine
    • Re: O/T: Patenting a computational scheme?, Jan Vorbrüggen
      • Re: O/T: Patenting a computational scheme?, Joost
      • Re: O/T: Patenting a computational scheme?, AN O'Nymous
      • Re: O/T: Patenting a computational scheme?, Pierre Asselin
    • Re: O/T: Patenting a computational scheme?, Jan Vorbrüggen
      • Re: O/T: Patenting a computational scheme?, Joe Krahn
      • Re: O/T: Patenting a computational scheme?, Kevin G. Rhoads
    • Re: O/T: Patenting a computational scheme?, AN O'Nymous
      • Re: O/T: Patenting a computational scheme?, Richard E Maine
  • Re: O/T: Patenting a computational scheme?, Steven G. Kargl
• Automatic allocation of an available file unit, Joe Krahn
  • Re: Automatic allocation of an available file unit, Richard Maine
    • Re: Automatic allocation of an available file unit, Pierre Asselin
      • Re: Automatic allocation of an available file unit, Richard E Maine
    • Re: Automatic allocation of an available file unit, Joe Krahn
      • Re: Automatic allocation of an available file unit, Paul Van Delst
  • Re: Automatic allocation of an available file unit, Paul Van Delst
    • Re: Automatic allocation of an available file unit, beliavsky
      • Re: Automatic allocation of an available file unit, Paul Van Delst
• Help: IFC stack overflow, Ben
  • Re: Help: IFC stack overflow, Joost
    • Re: Help: IFC stack overflow, Rich Townsend
      • Re: Help: IFC stack overflow, Joost
      • Re: Help: IFC stack overflow, Richard E Maine
      • Re: Help: IFC stack overflow, Rich Townsend
      • Re: Help: IFC stack overflow, Greg Lindahl
  • Re: Help: IFC stack overflow, Joe Krahn
    • Re: Help: IFC stack overflow, Ben
      • Re: Help: IFC stack overflow, Joost
      • Re: Help: IFC stack overflow, Ben
• procedure argument, Roland Schmehl
  • Re: procedure argument, Joe Krahn
  • Re: procedure argument, Richard E Maine
• Making fortran libraries, stuart Lynn
  • Re: Making fortran libraries, stuart Lynn
    • Re: Making fortran libraries, Kevin G. Rhoads
  • Re: Making fortran libraries, Pierre Asselin
• use a c dll in fortran?, tripplowe
  • Re: use a c dll in fortran?, N. Shamsundar
• RE: JOB - SHOP & FORTRAN 77, meek
• How to link a Fortran static library to a C++ program?, Guch Wu
  • Re: How to link a Fortran static library to a C++ program?, N. Shamsundar
    • Re: How to link a Fortran static library to a C++ program?, Guch Wu
    • Re: How to link a Fortran static library to a C++ program?, Guch Wu
      • Re: How to link a Fortran static library to a C++ program?, Jan Vorbrüggen
      • Re: How to link a Fortran static library to a C++ program?, N. Shamsundar
      • Re: How to link a Fortran static library to a C++ program?, Guch Wu
      • Re: How to link a Fortran static library to a C++ program?, Guch Wu
  • Re: How to link a Fortran static library to a C++ program?, Tim Prince
• Structure of large link libraries in f95, Charles Russell
  • Re: Structure of large link libraries in f95, robert . corbett
    • Re: Structure of large link libraries in f95, Charles Russell
      • Re: Structure of large link libraries in f95, robert . corbett
      • Re: Structure of large link libraries in f95, simon
      • Re: Structure of large link libraries in f95, robert . corbett
      • Re: Structure of large link libraries in f95, Walter Spector
      • Re: Structure of large link libraries in f95, Jan Vorbrüggen
      • Re: Structure of large link libraries in f95, Walter Spector
      • Re: Structure of large link libraries in f95, Gordon Sande
      • Re: Structure of large link libraries in f95, Walter Spector
      • Re: Structure of large link libraries in f95, Jan Vorbrüggen
      • Re: Structure of large link libraries in f95, Charles Russell
      • Re: Structure of large link libraries in f95, Walter Spector
      • Re: Structure of large link libraries in f95, Charles Russell
      • Re: Structure of large link libraries in f95, Joe Krahn
      • Re: Structure of large link libraries in f95, Jan Vorbrüggen
      • Re: Structure of large link libraries in f95, Joe Krahn
      • Re: Structure of large link libraries in f95, Charles Russell
      • Re: Structure of large link libraries in f95, Charles Russell
      • Re: Structure of large link libraries in f95, Richard E Maine
      • Re: Structure of large link libraries in f95, Charles Russell
      • Re: Structure of large link libraries in f95, Paul Van Delst
      • Re: Structure of large link libraries in f95, Charles Russell
      • Re: Structure of large link libraries in f95, Paul Van Delst
      • Re: Structure of large link libraries in f95, Charles Russell
      • Re: Structure of large link libraries in f95, Charles Russell
      • Re: Structure of large link libraries in f95, Charles Russell
      • Re: Structure of large link libraries in f95, Gordon Sande
      • Re: Structure of large link libraries in f95, Dan Nagle
      • Re: Structure of large link libraries in f95, Charles Russell
• send array using MPI, Fabian Braennstroem
  • Re: send array using MPI, Michael Wild
    • Re: send array using MPI, Fabian Braennstroem
      • Re: send array using MPI, Michael Wild
      • Re: send array using MPI, Ron Shepard
      • Re: send array using MPI, Richard E Maine
      • Re: send array using MPI, Dan Nagle
      • Re: send array using MPI, Paul Van Delst
      • Re: send array using MPI, Fabian Braennstroem
  • Re: send array using MPI, Douglas Sondak
• ANN: Free Fortran Tools with F on AMD64, Walt Brainerd
• Sharing generic names among functions and subroutines, Joe Krahn
  • Re: Sharing generic names among functions and subroutines, Paul Van Delst
    • Re: Sharing generic names among functions and subroutines, Brooks Moses
      • Re: Sharing generic names among functions and subroutines, Paul Van Delst
      • Re: Sharing generic names among functions and subroutines, Joe Krahn
• Calling Matlab in Compaq visual fortran at Windows XP, Ic-Pyo Hong
  • Re: Calling Matlab in Compaq visual fortran at Windows XP, Gib Bogle
    • Re: Calling Matlab in Compaq visual fortran at Windows XP, N. Shamsundar
• Using Java to read unformatted Fortran output files?, stocksami@xxxxxxxxxxxxx
  • Re: Using Java to read unformatted Fortran output files?, Rich Townsend
    • Re: Using Java to read unformatted Fortran output files?, stocksami@xxxxxxxxxxxxx
• C versus FORTRAN90, ambi
  • Re: C versus FORTRAN90, Paul Van Delst
  • Re: C versus FORTRAN90, Steven G. Kargl
  • Re: C versus FORTRAN90, beliavsky
  • Re: C versus FORTRAN90, Ronald Benedik
    • Re: C versus FORTRAN90, Michael Wild
  • Re: C versus FORTRAN90, Dmitry Gorbatovsky
  • Re: C versus FORTRAN90, Dan Nagle
  • Re: C versus FORTRAN90, analyst41
  • Re: C versus FORTRAN90, Dmitry Gorbatovsky
    • Re: C versus FORTRAN90, Jan Vorbrüggen
      • Re: C versus FORTRAN90, Dmitry Gorbatovsky
  • Re: C versus FORTRAN90, Catherine Rees Lay
    • Re: C versus FORTRAN90, robert . corbett
  • Re: C versus FORTRAN90, David Flower
  • Re: C versus FORTRAN90, feenberg
    • Re: C versus FORTRAN90, Steven G. Kargl
  • Re: C versus FORTRAN90, David
• is there as simple way to drive html with fortran ?, Philippe Lehert
  • Re: is there as simple way to drive html with fortran ?, beliavsky
  • Re: is there as simple way to drive html with fortran ?, N. Shamsundar
  • Re: is there as simple way to drive html with fortran ?, e p chandler
  • Re: is there as simple way to drive html with fortran ?, Anton Haumer
  • Re: is there as simple way to drive html with fortran ?, Joe Krahn
• how can I use progress control in FORTRAN PowerStation 4.0, shengbaojun
• Efficient neighbourhood searching, AN O'Nymous
  • Re: Efficient neighbourhood searching, beliavsky
    • Re: Efficient neighbourhood searching, Rich Townsend
      • Re: Efficient neighbourhood searching, Gordon Sande
      • Re: Efficient neighbourhood searching, Rich Townsend
      • Re: Efficient neighbourhood searching, AN O'Nymous
      • Re: Efficient neighbourhood searching, Jan Vorbrüggen
      • Re: Efficient neighbourhood searching, Gordon Sande
      • Re: Efficient neighbourhood searching, Gordon Sande
      • Re: Efficient neighbourhood searching, beliavsky
      • Re: Efficient neighbourhood searching, Rich Townsend
      • Re: Efficient neighbourhood searching, Rich Townsend
  • Re: Efficient neighbourhood searching, Gordon Sande
    • Re: Efficient neighbourhood searching, AN O'Nymous
  • Re: Efficient neighbourhood searching, Janne Blomqvist
• Salford FTN95 Access violation on compile time, Mathemagician
  • Re: Salford FTN95 Access violation on compile time, beliavsky
    • Re: Salford FTN95 Access violation on compile time, Mathemagician
    • Re: Salford FTN95 Access violation on compile time, Mathemagician
      • Re: Salford FTN95 Access violation on compile time, Herman D . Knoble
      • Re: Salford FTN95 Access violation on compile time, Mathemagician
  • Re: Salford FTN95 Access violation on compile time, Herman D . Knoble
    • Re: Salford FTN95 Access violation on compile time, Mathemagician
    • Re: Salford FTN95 Access violation on compile time, Mathemagician
      • Re: Salford FTN95 Access violation on compile time, Richard E Maine
• Using Orderpack..., tripplowe
  • Re: Using Orderpack..., beliavsky
• .mod generation question, Joost
  • Re: .mod generation question, robert . corbett
    • Re: .mod generation question, Joost
      • Re: .mod generation question, Rich Townsend
      • Re: .mod generation question, Joost
      • Re: .mod generation question, glen herrmannsfeldt
    • Re: .mod generation question, Joost
      • Re: .mod generation question, robert . corbett
  • Re: .mod generation question, Bil . Kleb
    • Re: .mod generation question, Joost
  • Re: .mod generation question, Joe Krahn
    • Re: .mod generation question, Joe Krahn
      • Re: .mod generation question, Steven G. Kargl
      • Re: .mod generation question, Richard Maine
      • Re: .mod generation question, Joe Krahn
    • Re: .mod generation question, James Giles
      • Re: .mod generation question, Pierre Asselin
• Retrieving position of a dialog in (Compaq) Visual Fortran, berger@xxxxxx
  • Re: Retrieving position of a dialog in (Compaq) Visual Fortran, Steve Lionel
  • Re: Retrieving position of a dialog in (Compaq) Visual Fortran, jdujic
    • Re: Retrieving position of a dialog in (Compaq) Visual Fortran, berger@xxxxxx
• Command-line argument parsing library?, Bil Kleb
  • Re: Command-line argument parsing library?, Dmitry Gorbatovsky
    • Re: Command-line argument parsing library?, Bil Kleb
• status of quadruple precision arithmetic in g95 and gfortran?, Bart Vandewoestyne
  • Re: status of quadruple precision arithmetic in g95 and gfortran?, Tim Prince
    • Re: status of quadruple precision arithmetic in g95 and gfortran?, Bart Vandewoestyne
      • Re: status of quadruple precision arithmetic in g95 and gfortran?, Joost
      • Re: status of quadruple precision arithmetic in g95 and gfortran?, Bernhard Enders
      • Re: status of quadruple precision arithmetic in g95 and gfortran?, glen herrmannsfeldt
      • Re: status of quadruple precision arithmetic in g95 and gfortran?, Tim Prince
      • Re: status of quadruple precision arithmetic in g95 and gfortran?, Bernhard Enders
      • Re: status of quadruple precision arithmetic in g95 and gfortran?, Tim Prince
      • Re: status of quadruple precision arithmetic in g95 and gfortran?, Herman D . Knoble
      • Re: status of quadruple precision arithmetic in g95 and gfortran?, Ian Gay
      • Re: status of quadruple precision arithmetic in g95 and gfortran?, Richard E Maine
      • Re: status of quadruple precision arithmetic in g95 and gfortran?, Herman D . Knoble
      • Re: status of quadruple precision arithmetic in g95 and gfortran?, Ian Gay
      • Re: status of quadruple precision arithmetic in g95 and gfortran?, Richard Maine
      • Re: status of quadruple precision arithmetic in g95 and gfortran?, Ian Gay
      • Re: status of quadruple precision arithmetic in g95 and gfortran?, robert . corbett
      • Re: status of quadruple precision arithmetic in g95 and gfortran?, Herman D . Knoble
      • Re: status of quadruple precision arithmetic in g95 and gfortran?, Bernhard Enders
      • Re: status of quadruple precision arithmetic in g95 and gfortran?, Richard E Maine
      • Re: status of quadruple precision arithmetic in g95 and gfortran?, Steven G. Kargl
      • Re: status of quadruple precision arithmetic in g95 and gfortran?, Herman D . Knoble
      • Re: status of quadruple precision arithmetic in g95 and gfortran?, robert . corbett
      • Re: status of quadruple precision arithmetic in g95 and gfortran?, Joost
      • Re: status of quadruple precision arithmetic in g95 and gfortran?, James Giles
      • Re: status of quadruple precision arithmetic in g95 and gfortran?, Joost
      • Re: status of quadruple precision arithmetic in g95 and gfortran?, robert . corbett
      • Re: status of quadruple precision arithmetic in g95 and gfortran?, Joost
      • Re: status of quadruple precision arithmetic in g95 and gfortran?, glen herrmannsfeldt
      • Re: status of quadruple precision arithmetic in g95 and gfortran?, James Giles
      • Re: status of quadruple precision arithmetic in g95 and gfortran?, Ian Gay
      • Re: status of quadruple precision arithmetic in g95 and gfortran?, James Giles
      • Re: status of quadruple precision arithmetic in g95 and gfortran?, glen herrmannsfeldt
      • Re: status of quadruple precision arithmetic in g95 and gfortran?, James Giles
      • Re: status of quadruple precision arithmetic in g95 and gfortran?, robert . corbett
      • Re: status of quadruple precision arithmetic in g95 and gfortran?, Jan Vorbrüggen
• Setting/Using Exit Handlers, R. MacDonald
  • Re: Setting/Using Exit Handlers, Steve Lionel
    • Re: Setting/Using Exit Handlers, R. MacDonald
• Re: buying old copy of Microsoft,Powerstation Fortran, kia
  • Re: buying old copy of Microsoft,Powerstation Fortran, Gary L. Scott
• short size for transfer, Thomas Koenig
  • Re: short size for transfer, Richard Maine
    • Re: short size for transfer, John Harper
• [g95] Enum not found in PNNL FLIB library, Hani Andreas Ibrahim
  • Re: Enum not found in PNNL FLIB library, Joost
    • Re: Enum not found in PNNL FLIB library, Hani Andreas Ibrahim
      • Re: Enum not found in PNNL FLIB library, Gary L. Scott
      • Re: Enum not found in PNNL FLIB library, Hani Andreas Ibrahim
      • Re: Enum not found in PNNL FLIB library, Andy
• RNGs for normal distributions, AN O'Nymous
  • Re: RNGs for normal distributions, Janne Blomqvist
    • Re: RNGs for normal distributions, AN O'Nymous
  • Re: RNGs for normal distributions, beliavsky
    • Re: RNGs for normal distributions, AN O'Nymous
      • Re: RNGs for normal distributions, Gib Bogle
• powers of five, robert . corbett
• Character String Dynamic Allocation, gary . l . scott
  • Re: Character String Dynamic Allocation, robert . corbett
    • Re: Character String Dynamic Allocation, Gary L. Scott
      • Re: Character String Dynamic Allocation, robert . corbett
      • Re: Character String Dynamic Allocation, Gary L. Scott
      • Re: Character String Dynamic Allocation, Gary L. Scott
      • Re: Character String Dynamic Allocation, Joost
      • Re: Character String Dynamic Allocation, Gary L. Scott
      • Re: Character String Dynamic Allocation, Brooks Moses
      • Re: Character String Dynamic Allocation, Gary L. Scott
      • Re: Character String Dynamic Allocation, Brooks Moses
      • Re: Character String Dynamic Allocation, Gary L. Scott
      • Re: Character String Dynamic Allocation, gary . l . scott
      • Re: Character String Dynamic Allocation, gary . l . scott
• Can anybody compile and run this code?, Sergio
  • Re: Can anybody compile and run this code?, Kevin G. Rhoads
  • Re: Can anybody compile and run this code?, robin
  • Re: Can anybody compile and run this code?, Dr Ivan D. Reid
• I searches: FORTRAN-66 (Fortran-IV) for DOS,IBM PC, x
  • Re: I searches: FORTRAN-66 (Fortran-IV) for DOS,IBM PC, Dan Nagle
  • Re: I searches: FORTRAN-66 (Fortran-IV) for DOS,IBM PC, Lynn McGuire
  • Re: I searches: FORTRAN-66 (Fortran-IV) for DOS,IBM PC, Kevin G. Rhoads
    • Re: I searches: FORTRAN-66 (Fortran-IV) for DOS,IBM PC, x
      • Re: I searches: FORTRAN-66 (Fortran-IV) for DOS,IBM PC, Louis Krupp
      • Re: I searches: FORTRAN-66 (Fortran-IV) for DOS,IBM PC, e p chandler
      • Re: I searches: FORTRAN-66 (Fortran-IV) for DOS,IBM PC, glen herrmannsfeldt
      • Re: I searches: FORTRAN-66 (Fortran-IV) for DOS,IBM PC, Gary L. Scott
      • Re: I searches: FORTRAN-66 (Fortran-IV) for DOS,IBM PC, glen herrmannsfeldt
      • Re: I searches: FORTRAN-66 (Fortran-IV) for DOS,IBM PC, Kevin G. Rhoads
      • Re: I searches: FORTRAN-66 (Fortran-IV) for DOS,IBM PC, Kevin G. Rhoads
      • Re: I searches: FORTRAN-66 (Fortran-IV) for DOS,IBM PC, glen herrmannsfeldt
      • RE: I searches: FORTRAN-66 (Fortran-IV) for DOS,IBM PC, meek
      • Re: I searches: FORTRAN-66 (Fortran-IV) for DOS,IBM PC, Kevin G. Rhoads
• Unions in Fortran, s8ngsu3
  • Re: Unions in Fortran, beliavsky
    • Re: Unions in Fortran, Paul Van Delst
    • Re: Unions in Fortran, Paul Van Delst
      • Re: Unions in Fortran, Brooks Moses
      • Re: Unions in Fortran, Dan Nagle
      • Re: Unions in Fortran, Joe Krahn
      • Re: Unions in Fortran, Dan Nagle
      • Re: Unions in Fortran, Michael Metcalf
      • Re: Unions in Fortran, James Giles
      • Re: Unions in Fortran, Gary L. Scott
      • Re: Unions in Fortran, James Giles
      • Re: Unions in Fortran, glen herrmannsfeldt
      • Re: Unions in Fortran, James Giles
      • Re: Unions in Fortran, Brooks Moses
      • Re: Unions in Fortran, James Giles
      • Re: Unions in Fortran, glen herrmannsfeldt
      • Re: Unions in Fortran, glen herrmannsfeldt
  • Re: Unions in Fortran, gary . l . scott
    • Re: Unions in Fortran, David Flower
    • Re: Unions in Fortran, Lynn McGuire
  • Re: Unions in Fortran, Joe Krahn
    • Re: Unions in Fortran, James Giles
      • Re: Unions in Fortran, Dan Nagle
      • Re: Unions in Fortran, James Giles
  • Re: Unions in Fortran, Richard E Maine
• Mixing programming with Lisp, Dmitry V. Gorbatovsky
• Problems about Mixed programming with C++ and Fortran, Guch
  • Re: Problems about Mixed programming with C++ and Fortran, Guch Wu
  • Re: Problems about Mixed programming with C++ and Fortran, Craig Powers
    • Re: Problems about Mixed programming with C++ and Fortran, Guch Wu
      • Re: Problems about Mixed programming with C++ and Fortran, Pierre Asselin
      • Re: Problems about Mixed programming with C++ and Fortran, Craig Powers
      • Re: Problems about Mixed programming with C++ and Fortran, Joe Krahn
• Need suggestion on Sparse Matrix Library, andywenj@xxxxxxxxx
  • Re: Need suggestion on Sparse Matrix Library, Bernhard Enders
  • Re: Need suggestion on Sparse Matrix Library, Herman D . Knoble
• STOP while writing, John Harper
  • Re: STOP while writing, James Giles
• Extra parentheses matter in internal read?, ellips
  • Re: Extra parentheses matter in internal read?, Richard E Maine
    • Re: Extra parentheses matter in internal read?, glen herrmannsfeldt
      • Re: Extra parentheses matter in internal read?, Richard E Maine
      • Re: Extra parentheses matter in internal read?, glen herrmannsfeldt
      • Re: Extra parentheses matter in internal read?, James Giles
      • Re: Extra parentheses matter in internal read?, Richard Maine
      • Re: Extra parentheses matter in internal read?, glen herrmannsfeldt
      • Re: Extra parentheses matter in internal read?, Richard E Maine
      • Re: Extra parentheses matter in internal read?, glen herrmannsfeldt
  • Re: Extra parentheses matter in internal read?, Richard E Maine
    • Re: Extra parentheses matter in internal read?, ellips
      • Re: Extra parentheses matter in internal read?, Richard E Maine
      • Re: Extra parentheses matter in internal read?, Michael Metcalf
  • Re: Extra parentheses matter in internal read?, glen herrmannsfeldt
• C style compound assignment operators, Bernhard Enders
  • Re: C style compound assignment operators, Richard E Maine
    • Re: C style compound assignment operators, Bernhard Enders
      • Re: C style compound assignment operators, Dan Nagle
      • Re: C style compound assignment operators, glen herrmannsfeldt
      • Re: C style compound assignment operators, Ben Hetland
    • Re: C style compound assignment operators, Dick Hendrickson
      • Re: C style compound assignment operators, Ben Hetland
      • Re: C style compound assignment operators, James Giles
    • Re: C style compound assignment operators, Ben Hetland
  • Re: C style compound assignment operators, glen herrmannsfeldt
    • Re: C style compound assignment operators, Richard E Maine
  • Re: C style compound assignment operators, James Giles
    • Re: C style compound assignment operators, beliavsky
      • Re: C style compound assignment operators, Dan Nagle
      • Re: C style compound assignment operators, Richard E Maine
      • Re: C style compound assignment operators, Tom Micevski
      • Re: C style compound assignment operators, Paul Van Delst
      • Re: C style compound assignment operators, glen herrmannsfeldt
      • Re: C style compound assignment operators, Ben Hetland
      • Re: C style compound assignment operators, James Giles
      • Re: C style compound assignment operators, Ben Hetland
      • Re: C style compound assignment operators, James Giles
      • Re: C style compound assignment operators, Ben Hetland
      • Re: C style compound assignment operators, Ben Hetland
      • Re: C style compound assignment operators, James Giles
      • Re: C style compound assignment operators, glen herrmannsfeldt
      • Re: C style compound assignment operators, Joe Krahn
      • Re: C style compound assignment operators, Richard E Maine
      • Re: C style compound assignment operators, James Giles
• Interaction of generic names and assumed size arguments, Craig Powers
  • Re: Interaction of generic names and assumed size arguments, Michael Metcalf
    • Re: Interaction of generic names and assumed size arguments, Craig Powers
      • Re: Interaction of generic names and assumed size arguments, Joost
      • Re: Interaction of generic names and assumed size arguments, Richard E Maine
  • Re: Interaction of generic names and assumed size arguments, Richard E Maine
    • Re: Interaction of generic names and assumed size arguments, Craig Powers
  • Re: Interaction of generic names and assumed size arguments, Steve Lionel
    • Re: Interaction of generic names and assumed size arguments, Craig Powers
    • Re: Interaction of generic names and assumed size arguments, Richard E Maine
    • Re: Interaction of generic names and assumed size arguments, Steve Lionel
• compilation with ifort9 aborts with strange message, tommyA
  • Re: compilation with ifort9 aborts with strange message, Tim Prince
    • Re: compilation with ifort9 aborts with strange message, tommyA
• Integrated Developement Environment - looked for..., Phillip
  • Re: Integrated Developement Environment - looked for..., Arjen Markus
    • Re: Integrated Developement Environment - looked for..., Vincent MAGNIN
      • Re: Integrated Developement Environment - looked for..., Bart Vandewoestyne
  • RE: Integrated Developement Environment - looked for..., meek
    • Re: Integrated Developement Environment - looked for..., Kevin G. Rhoads
      • Re: Integrated Developement Environment - looked for..., Lynn McGuire
      • RE: Integrated Developement Environment - looked for..., meek
    • Re: Integrated Developement Environment - looked for..., kia
  • Re: Integrated Developement Environment - looked for..., Bernhard Enders
    • Re: Integrated Developement Environment - looked for..., Joost
      • Re: Integrated Developement Environment - looked for..., Bernhard Enders
      • Re: Integrated Developement Environment - looked for..., Michael Prager
    • Re: Integrated Developement Environment - looked for..., Dan Nagle
    • Re: Integrated Developement Environment - looked for..., Gib Bogle
      • Re: Integrated Developement Environment - looked for..., Brooks Moses
      • Re: Integrated Developement Environment - looked for..., Gib Bogle
    • Re: Integrated Developement Environment - looked for..., Joe Krahn
      • Re: Integrated Developement Environment - looked for..., kia
      • Re: Integrated Developement Environment - looked for..., Kevin G. Rhoads
  • Re: Integrated Developement Environment - looked for..., i . chivers
    • Re: Integrated Developement Environment - looked for..., Phillip
  • Re: Integrated Developement Environment - looked for..., Dmitry Gorbatovsky
  • Re: Integrated Developement Environment - looked for..., jussij
• array definition with reshape - f90 , Compaq tru64, Damien MATTEI
  • Re: array definition with reshape - f90 , Compaq tru64, Joost
    • Re: array definition with reshape - f90 , Compaq tru64, Damien MATTEI
      • Re: array definition with reshape - f90 , Compaq tru64, Richard E Maine
      • Re: array definition with reshape - f90 , Compaq tru64, Damien MATTEI
      • Re: array definition with reshape - f90 , Compaq tru64, Richard E Maine
  • Re: array definition with reshape - f90 , Compaq tru64, Steve Lionel
    • Re: array definition with reshape - f90 , Compaq tru64, Damien MATTEI
• Not-equals as '#' ?, Joe Krahn
  • Re: Not-equals as '#' ?, Arjen Markus
    • Re: Not-equals as '#' ?, Ben Hetland
  • Re: Not-equals as '#' ?, James Giles
  • Re: Not-equals as '#' ?, Erik Edelmann
    • Re: Not-equals as '#' ?, Michael Metcalf
      • Re: Not-equals as '#' ?, Gareth Owen
      • Re: Not-equals as '#' ?, Richard E Maine
      • Re: Not-equals as '#' ?, James Parsly
      • Re: Not-equals as '#' ?, glen herrmannsfeldt
      • Re: Not-equals as '#' ?, Rich Townsend
      • Re: Not-equals as '#' ?, Gareth Owen
      • Re: Not-equals as '#' ?, Craig Powers
      • Re: Not-equals as '#' ?, glen herrmannsfeldt
      • Re: Not-equals as '#' ?, Rich Townsend
      • Re: Not-equals as '#' ?, glen herrmannsfeldt
      • Re: Not-equals as '#' ?, Joe Krahn
      • Re: Not-equals as '#' ?, Les
      • Re: Not-equals as '#' ?, beliavsky
      • Re: Not-equals as '#' ?, Les
      • Re: Not-equals as '#' ?, Richard E Maine
  • Re: Not-equals as '#' ?, Paul Van Delst
    • Re: Not-equals as '#' ?, gary . l . scott
  • Re: Not-equals as '#' ?, glen herrmannsfeldt
    • Re: Not-equals as '#' ?, Ben Hetland
    • Re: Not-equals as '#' ?, gary . l . scott
    • Re: Not-equals as '#' ?, Brooks Moses
      • Re: Not-equals as '#' ?, Michael Wild
• Strings with escape sequences., Joe Krahn
  • Re: Strings with escape sequences., James Giles
    • Re: Strings with escape sequences., Joe Krahn
      • Re: Strings with escape sequences., Brooks Moses
      • Re: Strings with escape sequences., Dan Nagle
      • Re: Strings with escape sequences., James Giles
      • Re: Strings with escape sequences., Brooks Moses
      • Re: Strings with escape sequences., Dan Nagle
      • Re: Strings with escape sequences., James Giles
      • Re: Strings with escape sequences., Dan Nagle
      • Re: Strings with escape sequences., James Giles
• Allocatable derived type with allocatable components in fortran 90, dont
  • Re: Allocatable derived type with allocatable components in fortran 90, Richard E Maine
    • Re: Allocatable derived type with allocatable components in fortran 90, Shriram Ramanathan
      • Re: Allocatable derived type with allocatable components in fortran 90, Richard E Maine
      • Re: Allocatable derived type with allocatable components in fortran 90, ramanath
      • Re: Allocatable derived type with allocatable components in fortran 90, s8ngsu3
      • Re: Allocatable derived type with allocatable components in fortran 90, Brooks Moses
      • Re: Allocatable derived type with allocatable components in fortran 90, Ben Hetland
      • Re: Allocatable derived type with allocatable components in fortran 90, glen herrmannsfeldt
      • Re: Allocatable derived type with allocatable components in fortran 90, Ben Hetland
      • Re: Allocatable derived type with allocatable components in fortran 90, Brooks Moses
  • Re: Allocatable derived type with allocatable components in fortran 90, Joe Krahn
• Nomenclature for entity(...) ?, Joe Krahn
• Help: declare an array without knowing the rank and size, laserbin
  • Re: Help: declare an array without knowing the rank and size, Richard E Maine
    • Re: Help: declare an array without knowing the rank and size, Ben
      • Re: Help: declare an array without knowing the rank and size, Richard E Maine
      • Re: Help: declare an array without knowing the rank and size, Paul Van Delst
  • Re: Help: declare an array without knowing the rank and size, Bernhard Enders
    • Re: Help: declare an array without knowing the rank and size, beliavsky
  • Re: Help: declare an array without knowing the rank and size, Gordon Sande
    • Re: Help: declare an array without knowing the rank and size, Ben
      • Re: Help: declare an array without knowing the rank and size, Paul Van Delst
      • Re: Help: declare an array without knowing the rank and size, jwm
      • Re: Help: declare an array without knowing the rank and size, Ben Hetland
      • Re: Help: declare an array without knowing the rank and size, Michael Metcalf
• Object library problem, Dieter Britz
  • Re: Object library problem, Joe Krahn
    • Re: Object library problem, Dieter Britz
      • Re: Object library problem, Paul Van Delst
      • Re: Object library problem, Steve Lionel
• Using MS VB to debug fotran code (*.f files), Bhima
  • Re: Using MS VB to debug fotran code (*.f files), beliavsky
    • Re: Using MS VB to debug fotran code (*.f files), J.F. Cornwall
• Derived types with derived types with allocatables, Arno
  • Re: Derived types with derived types with allocatables, Joost
    • Re: Derived types with derived types with allocatables, Arno
      • Re: Derived types with derived types with allocatables, Joost
      • Re: Derived types with derived types with allocatables, Les
      • Re: Derived types with derived types with allocatables, Arno
      • Re: Derived types with derived types with allocatables, Joe Krahn
      • Re: Derived types with derived types with allocatables, Rich Townsend
      • Re: Derived types with derived types with allocatables, Les
• lahey lf95: option to use integer as logical?, chrisschardt@xxxxxxxxxxxxx
  • Re: lahey lf95: option to use integer as logical?, Dan Nagle
    • Re: lahey lf95: option to use integer as logical?, Richard E Maine
      • Re: lahey lf95: option to use integer as logical?, Dan Nagle
      • Re: lahey lf95: option to use integer as logical?, Joe Krahn
      • Re: lahey lf95: option to use integer as logical?, Brooks Moses
  • Re: lahey lf95: option to use integer as logical?, jwm
  • Re: lahey lf95: option to use integer as logical?, Joe Krahn
    • Re: lahey lf95: option to use integer as logical?, James Giles
      • Re: lahey lf95: option to use integer as logical?, Joe Krahn
      • Re: lahey lf95: option to use integer as logical?, James Giles
    • Re: lahey lf95: option to use integer as logical?, Ken Fairfield
      • Re: lahey lf95: option to use integer as logical?, glen herrmannsfeldt
• Re: How can I use dreal and dimag in a f90 program?, robin
  • Re: How can I use dreal and dimag in a f90 program?, Rich Townsend
    • Re: How can I use dreal and dimag in a f90 program?, robin
      • Re: How can I use dreal and dimag in a f90 program?, Rich Townsend
      • Re: How can I use dreal and dimag in a f90 program?, AeroSpace Ed
      • Re: How can I use dreal and dimag in a f90 program?, robin
• Re: How can I use dreal and dimag in a f90 program?, robin
• g77 double precision data initialization problem, mvuk
  • Re: g77 double precision data initialization problem, Joe Krahn
    • Re: g77 double precision data initialization problem, e p chandler
    • Re: g77 double precision data initialization problem, Paul Van Delst
      • Re: g77 double precision data initialization problem, mvuk
• function problem, pieterprovoost
  • Re: function problem, Joost
  • Re: function problem, Richard E Maine
    • Re: function problem, pieterprovoost
      • Re: function problem, Michael Metcalf
      • Re: function problem, pieterprovoost
      • Re: function problem, pieterprovoost
      • Re: function problem, Jan Vorbrüggen
      • Re: function problem, Joe Krahn
      • Re: function problem, John Harper
      • Re: function problem, robin
      • Re: function problem, Dick Hendrickson
      • Re: function problem, robin
      • Re: function problem, robin
      • Re: function problem, pieterprovoost
  • Re: function problem, robin
• Write statement does not print correct value?, jchauvin
  • Re: Write statement does not print correct value?, Michael Metcalf
    • Re: Write statement does not print correct value?, Joost
      • Re: Write statement does not print correct value?, Michael Metcalf
  • Re: Write statement does not print correct value?, Warner BRUNS
    • Re: Write statement does not print correct value?, Richard E Maine
  • Re: Write statement does not print correct value?, Gordon Sande
  • Re: Write statement does not print correct value?, Walter Spector
• help: linear operators of IMSL fortran 90 MP library, andywenj@xxxxxxxxx
  • Re: linear operators of IMSL fortran 90 MP library, Michael Metcalf
    • Re: linear operators of IMSL fortran 90 MP library, andywenj@xxxxxxxxx
• Memory allocated, kaper
  • Re: Memory allocated, Bernhard Enders
  • Re: Memory allocated, Joost
    • Re: Memory allocated, Dan Nagle
      • Re: Memory allocated, Joost
      • Re: Memory allocated, Gordon Sande
      • Re: Memory allocated, Michael Metcalf
      • Re: Memory allocated, Dan Nagle
      • Re: Memory allocated, Keith Refson
  • Re: Memory allocated, Joe Krahn
• how to compute B*inv(A) efficiently ?, andywenj@xxxxxxxxx
  • Re: how to compute B*inv(A) efficiently ?, Joost
  • Re: how to compute B*inv(A) efficiently ?, Dave Seaman
    • Re: how to compute B*inv(A) efficiently ?, andywenj@xxxxxxxxx
      • Re: how to compute B*inv(A) efficiently ?, Brooks Moses
• Dll for Excel, richard symonds
  • Re: Dll for Excel, Steve Lionel
    • Re: Dll for Excel, richard symonds
      • Re: Dll for Excel, richard symonds
      • Re: Dll for Excel, sbergero
      • Re: Dll for Excel, Kevin G. Rhoads
      • Re: Dll for Excel, Steve Lionel
  • Re: Dll for Excel, e p chandler
• Will the *real* vms fortran please stand up? (historical questions), transnet
  • Re: Will the *real* vms fortran please stand up? (historical questions), glen herrmannsfeldt
  • Re: Will the *real* vms fortran please stand up? (historical questions), Jim
    • Re: Will the *real* vms fortran please stand up? (historical questions), transnet
    • Re: Will the *real* vms fortran please stand up? (historical questions), Steve Lionel
  • Re: Will the *real* vms fortran please stand up? (historical questions), Steve Lionel
    • Re: Will the *real* vms fortran please stand up? (historical questions), Jim
      • Re: Will the *real* vms fortran please stand up? (historical questions), Greg Lindahl
      • Re: Will the *real* vms fortran please stand up? (historical questions), glen herrmannsfeldt
      • Re: Will the *real* vms fortran please stand up? (historical questions), Patrick L. Nolan
  • Re: Will the *real* vms fortran please stand up? (historical questions), Ken Fairfield
    • Re: Will the *real* vms fortran please stand up? (historical questions), glen herrmannsfeldt
• how to eleminate the spurious ??, Millena
  • Re: how to eleminate the spurious ??, glen herrmannsfeldt
    • Re: how to eleminate the spurious ??, Millena
      • Re: how to eleminate the spurious ??, glen herrmannsfeldt
  • Re: how to eleminate the spurious ??, Brooks Moses
    • Re: how to eleminate the spurious ??, Bernhard Enders
  • Re: how to eleminate the spurious ??, John Harper
• Fortran vs C++ for scientific computing, Kobe
  • Re: Fortran vs C++ for scientific computing, glen herrmannsfeldt
  • Re: Fortran vs C++ for scientific computing, Erik Edelmann
    • Re: Fortran vs C++ for scientific computing, beliavsky
      • Re: Fortran vs C++ for scientific computing, Erik Edelmann
  • Re: Fortran vs C++ for scientific computing, Brooks Moses
  • Re: Fortran vs C++ for scientific computing, Joe Krahn
    • Re: Fortran vs C++ for scientific computing, max
    • Re: Fortran vs C++ for scientific computing, Ben Hetland
      • Re: Fortran vs C++ for scientific computing, Joe Krahn
      • Re: Fortran vs C++ for scientific computing, beliavsky
      • Re: Fortran vs C++ for scientific computing, Ben Hetland
      • Re: Fortran vs C++ for scientific computing, beliavsky
      • Re: Fortran vs C++ for scientific computing, Joe Krahn
      • Re: Fortran vs C++ for scientific computing, Ben Hetland
      • Re: Fortran vs C++ for scientific computing, Richard E Maine
      • Re: Fortran vs C++ for scientific computing, Ben Hetland
      • Re: Fortran vs C++ for scientific computing, Richard E Maine
      • Re: Fortran vs C++ for scientific computing, Ben Hetland
      • Re: Fortran vs C++ for scientific computing, Les
  • Re: Fortran vs C++ for scientific computing, Jim
  • Re: Fortran vs C++ for scientific computing, Dr Ivan D. Reid
    • Re: Fortran vs C++ for scientific computing, beliavsky
    • Re: Fortran vs C++ for scientific computing, Bart Vandewoestyne
      • Re: Fortran vs C++ for scientific computing, Dan Nagle
      • Re: Fortran vs C++ for scientific computing, Bart Vandewoestyne
      • Re: Fortran vs C++ for scientific computing, Dan Nagle
      • Re: Fortran vs C++ for scientific computing, Greg Lindahl
      • Re: Fortran vs C++ for scientific computing, Gib Bogle
      • Re: Fortran vs C++ for scientific computing, Paul Van Delst
      • Re: Fortran vs C++ for scientific computing, Michael Prager
      • Re: Fortran vs C++ for scientific computing, John Harper
      • Re: Fortran vs C++ for scientific computing, Brooks Moses
      • Re: Fortran vs C++ for scientific computing, Greg Lindahl
    • Re: Fortran vs C++ for scientific computing, Kobe
  • Re: Fortran vs C++ for scientific computing, DVG
    • Re: Fortran vs C++ for scientific computing, robin
      • Re: Fortran vs C++ for scientific computing, Michael Metcalf
      • Re: Fortran vs C++ for scientific computing, robin
      • Re: Fortran vs C++ for scientific computing, Dan Nagle
      • Re: Fortran vs C++ for scientific computing, Rich Townsend
      • Re: Fortran vs C++ for scientific computing, Rich Townsend
      • Re: Fortran vs C++ for scientific computing, Dmitry Gorbatovsky
  • Re: Fortran vs C++ for scientific computing, robin
• Why stack overflow here?, Bernhard Enders
  • Re: Why stack overflow here?, Michael Metcalf
    • Re: Why stack overflow here?, Bernhard Enders
      • Re: Why stack overflow here?, Joost
      • Re: Why stack overflow here?, Bernhard Enders
      • Re: Why stack overflow here?, Joost
      • Re: Why stack overflow here?, Bernhard Enders
      • Re: Why stack overflow here?, Richard Maine
      • Re: Why stack overflow here?, Joe Krahn
      • Re: Why stack overflow here?, Paul Van Delst
      • Re: Why stack overflow here?, Bernhard Enders
  • Re: Why stack overflow here?, Ugo
• Statement functions, Joe Krahn
  • Re: Statement functions, James Giles
    • Re: Statement functions, Joe Krahn
      • Re: Statement functions, James Giles
  • Re: Statement functions, Richard Maine
    • Re: Statement functions, Joe Krahn
      • Re: Statement functions, Michael Metcalf
      • Re: Statement functions, James Giles
      • Re: Statement functions, Joe Krahn
      • Re: Statement functions, James Giles
      • Re: Statement functions, Richard Maine
      • Re: Statement functions, Ron Shepard
      • Re: Statement functions, Paul Van Delst
      • Re: Statement functions, Joe Krahn
      • Re: Statement functions, Richard E Maine
      • Re: Statement functions, glen herrmannsfeldt
      • Re: Statement functions, Paul Van Delst
      • Re: Statement functions, Joe Krahn
      • Re: Statement functions, Richard Maine
      • Re: Statement functions, Richard E Maine
      • Re: Statement functions, Ben Hetland
• Have you ever considered of mousing ambidextrously?, WangQiang
  • Re: Have you ever considered of mousing ambidextrously?, Michael Wild
  • Re: Have you ever considered of mousing ambidextrously?, Ken Plotkin
• Mac Fortran Programs, Jim Klein
  • Re: Mac Fortran Programs, awgreynolds
  • Re: Mac Fortran Programs, Steve Lionel
• What's the purpose of explicit interfaces?, Joe Krahn
  • Re: What's the purpose of explicit interfaces?, Michael Metcalf
    • Re: What's the purpose of explicit interfaces? (Pun intended?), N. Shamsundar
      • Re: What's the purpose of explicit interfaces? (Pun intended?), James Giles
      • Re: What's the purpose of explicit interfaces? (Pun intended?), N. Shamsundar
      • Re: What's the purpose of explicit interfaces? (Pun intended?), James Giles
      • Re: What's the purpose of explicit interfaces? (Pun intended?), Ben Hetland
  • Re: What's the purpose of explicit interfaces?, Erik Edelmann
    • Re: What's the purpose of explicit interfaces?, Joe Krahn
  • Re: What's the purpose of explicit interfaces?, Kevin G. Rhoads
  • Re: What's the purpose of explicit interfaces?, Richard E Maine
    • Re: What's the purpose of explicit interfaces?, Joe Krahn
• Re: Photran 3.0.0, Walter
• Photran debug, Walter
  • Re: Photran debug, Jim McDonald
• Anyone for help with DEC (Vax) Fortran-IV ?, transnet
  • Re: Anyone for help with DEC (Vax) Fortran-IV ?, Jim
    • Re: Anyone for help with DEC (Vax) Fortran-IV ?, Dan Nagle
      • Re: Anyone for help with DEC (Vax) Fortran-IV ?, transnet
      • Re: Anyone for help with DEC (Vax) Fortran-IV ?, Richard E Maine
      • Re: Anyone for help with DEC (Vax) Fortran-IV ?, transnet
      • Re: Anyone for help with DEC (Vax) Fortran-IV ?, Richard Maine
      • Re: Anyone for help with DEC (Vax) Fortran-IV ?, transnet
      • Re: Anyone for help with DEC (Vax) Fortran-IV ?, Brooks Moses
      • Re: Anyone for help with DEC (Vax) Fortran-IV ?, transnet
      • Re: Anyone for help with DEC (Vax) Fortran-IV ?, Brooks Moses
      • Re: Anyone for help with DEC (Vax) Fortran-IV ?, transnet
    • Re: Anyone for help with DEC (Vax) Fortran-IV ?, Steve Lionel
      • Re: Anyone for help with DEC (Vax) Fortran-IV ?, transnet
      • Re: Anyone for help with DEC (Vax) Fortran-IV ?, Jim
      • Re: Anyone for help with DEC (Vax) Fortran-IV ?, Richard E Maine
      • Re: Anyone for help with DEC (Vax) Fortran-IV ?, transnet
      • Re: Anyone for help with DEC (Vax) Fortran-IV ?, Jim
      • Re: Anyone for help with DEC (Vax) Fortran-IV ?, Gary L. Scott
      • Re: Anyone for help with DEC (Vax) Fortran-IV ?, transnet
      • Re: Anyone for help with DEC (Vax) Fortran-IV ?, Steve Lionel
      • Re: Anyone for help with DEC (Vax) Fortran-IV ?, transnet
      • Re: Anyone for help with DEC (Vax) Fortran-IV ?, Richard Maine
      • Re: Anyone for help with DEC (Vax) Fortran-IV ?, Gary L. Scott
    • Re: Anyone for help with DEC (Vax) Fortran-IV ?, Phillip Helbig---remove CLOTHES to reply
  • Re: Anyone for help with DEC (Vax) Fortran-IV ?, Steve Lionel
  • Re: Anyone for help with DEC (Vax) Fortran-IV ?, Richard E Maine
    • Re: Anyone for help with DEC (Vax) Fortran-IV ?, William Asher
      • Re: Anyone for help with DEC (Vax) Fortran-IV ?, transnet
      • Re: Anyone for help with DEC (Vax) Fortran-IV ?, William Asher
      • Re: Anyone for help with DEC (Vax) Fortran-IV ?, William Asher
      • Re: Anyone for help with DEC (Vax) Fortran-IV ?, Richard Maine
      • Re: Anyone for help with DEC (Vax) Fortran-IV ?, transnet
      • Re: Anyone for help with DEC (Vax) Fortran-IV ?, William Asher
      • Re: Anyone for help with DEC (Vax) Fortran-IV ?, transnet
      • Re: Anyone for help with DEC (Vax) Fortran-IV ?, William Asher
      • Re: Anyone for help with DEC (Vax) Fortran-IV ?, transnet
      • Re: Anyone for help with DEC (Vax) Fortran-IV ?, transnet
      • Re: Anyone for help with DEC (Vax) Fortran-IV ?, transnet
      • Re: Anyone for help with DEC (Vax) Fortran-IV ?, Brooks Moses
• entity naming conventions, Joe Krahn
  • Re: entity naming conventions, Dan Nagle
  • Re: entity naming conventions, Paul Van Delst
    • Re: entity naming conventions, Steven G. Kargl
      • Re: entity naming conventions, Paul Van Delst
    • Re: entity naming conventions, Joe Krahn
  • Re: entity naming conventions, Richard E Maine
  • Re: entity naming conventions, Colin Watters
    • Re: entity naming conventions, Richard E Maine
  • Re: entity naming conventions, David Flower
• finding the type name of a variable in fortran, arthur
  • Re: finding the type name of a variable in fortran, Michael Wild
    • Re: finding the type name of a variable in fortran, Ron Shepard
• Error when compiling with FTN95, dtshedd
  • Re: Error when compiling with FTN95, beliavsky
  • Re: Error when compiling with FTN95, Joost
    • Re: Error when compiling with FTN95, glen herrmannsfeldt
      • Re: Error when compiling with FTN95, Richard E Maine
      • Re: Error when compiling with FTN95, Bernhard Enders
  • Re: Error when compiling with FTN95, Herman D . Knoble
• a system_clock that doesn't roll, Joost
  • Re: a system_clock that doesn't roll, Brooks Moses
    • Re: a system_clock that doesn't roll, Joost
      • Re: a system_clock that doesn't roll, Richard E Maine
  • Re: a system_clock that doesn't roll, Walter Spector
    • Re: a system_clock that doesn't roll, Joost
• Data alignment and performance, sunnyabc
  • Re: Data alignment and performance, Joost
    • Re: Data alignment and performance, Ben Hetland
      • Re: Data alignment and performance, Joost
      • Re: Data alignment and performance, Ben Hetland
      • Re: Data alignment and performance, Joe Krahn
      • Re: Data alignment and performance, Richard E Maine
      • Re: Data alignment and performance, Jan Vorbrüggen
      • Re: Data alignment and performance, Michael Metcalf
      • Re: Data alignment and performance, Richard E Maine
  • Re: Data alignment and performance, Jan Vorbrüggen
• generalized WHILE() extension/feature?, Joe Krahn
  • Re: generalized WHILE() extension/feature?, Steven G. Kargl
    • Re: generalized WHILE() extension/feature?, James Giles
      • Fortran variant (was Re: generalized WHILE() extension/feature?), beliavsky
      • Re: Fortran variant (was Re: generalized WHILE() extension/feature?), James Giles
      • Re: Fortran variant (was Re: generalized WHILE() extension/feature?), Brooks Moses
      • Re: generalized WHILE() extension/feature?, Paul Van Delst
      • Re: generalized WHILE() extension/feature?, James Giles
      • Re: generalized WHILE() extension/feature?, Joe Krahn
      • Re: generalized WHILE() extension/feature?, James Giles
      • Re: generalized WHILE() extension/feature?, Joe Krahn
      • Re: generalized WHILE() extension/feature?, James Giles
    • Re: generalized WHILE() extension/feature?, Joe Krahn
  • Re: generalized WHILE() extension/feature?, Paul Van Delst
  • Re: generalized WHILE() extension/feature?, Clive Page
    • Re: generalized WHILE() extension/feature?, James Giles
• Formatted IO of huge/tiny values, Janne Blomqvist
  • Re: Formatted IO of huge/tiny values, robert . corbett
  • Re: Formatted IO of huge/tiny values, Richard E Maine
    • Re: Formatted IO of huge/tiny values, James Giles
      • Re: Formatted IO of huge/tiny values, Joe Krahn
      • Re: Formatted IO of huge/tiny values, James Giles
      • Re: Formatted IO of huge/tiny values, Richard E Maine
      • Re: Formatted IO of huge/tiny values, James Giles
      • Re: Formatted IO of huge/tiny values, Joe Krahn
      • Re: Formatted IO of huge/tiny values, James Giles
      • Re: Formatted IO of huge/tiny values, Joe Krahn
      • Re: Formatted IO of huge/tiny values, glen herrmannsfeldt
      • Re: Formatted IO of huge/tiny values, Dan Nagle
      • Re: Formatted IO of huge/tiny values, glen herrmannsfeldt
      • Re: Formatted IO of huge/tiny values, Dan Nagle
      • Re: Formatted IO of huge/tiny values, glen herrmannsfeldt
      • Re: Formatted IO of huge/tiny values, James Giles
      • Re: Formatted IO of huge/tiny values, Dan Nagle
      • Re: Formatted IO of huge/tiny values, James Giles
      • Re: Formatted IO of huge/tiny values, glen herrmannsfeldt
      • Re: Formatted IO of huge/tiny values, James Giles
      • Re: Formatted IO of huge/tiny values, glen herrmannsfeldt
      • Re: Formatted IO of huge/tiny values, James Giles
      • Re: Formatted IO of huge/tiny values, Joe Krahn
      • Re: Formatted IO of huge/tiny values, James Giles
      • Re: Formatted IO of huge/tiny values, Joe Krahn
      • Re: Formatted IO of huge/tiny values, glen herrmannsfeldt
      • Re: Formatted IO of huge/tiny values, Richard E Maine
      • Re: Formatted IO of huge/tiny values, glen herrmannsfeldt
      • Re: Formatted IO of huge/tiny values, Clive Page
      • Re: Formatted IO of huge/tiny values, Joost
      • Re: Formatted IO of huge/tiny values, glen herrmannsfeldt
• Returning pointers to objects that are not TARGETs in the parent?, Brooks Moses
  • Re: Returning pointers to objects that are not TARGETs in the parent?, Joost
  • Re: Returning pointers to objects that are not TARGETs in the parent?, James Giles
    • Re: Returning pointers to objects that are not TARGETs in the parent?, glen herrmannsfeldt
      • Re: Returning pointers to objects that are not TARGETs in the parent?, James Giles
      • Re: Returning pointers to objects that are not TARGETs in the parent?, glen herrmannsfeldt
    • Re: Returning pointers to objects that are not TARGETs in the parent?, Brooks Moses
  • Re: Returning pointers to objects that are not TARGETs in the parent?, Ron Shepard
    • Re: Returning pointers to objects that are not TARGETs in the parent?, Pierre Asselin
      • Re: Returning pointers to objects that are not TARGETs in the parent?, Joost
    • Re: Returning pointers to objects that are not TARGETs in the parent?, Herman D . Knoble
• contour map of 3-D subsurface resistivity distribution, bowo
• include files and long fixed form lines, robert . corbett
  • Re: include files and long fixed form lines, Joe Krahn
  • Re: include files and long fixed form lines, Ben Hetland
    • Re: include files and long fixed form lines, Richard E Maine
      • Re: include files and long fixed form lines, Ben Hetland
      • Re: include files and long fixed form lines, Joe Krahn
      • Re: include files and long fixed form lines, Ben Hetland
      • Re: include files and long fixed form lines, Richard E Maine
      • Re: include files and long fixed form lines, Richard E Maine
      • Re: include files and long fixed form lines, Ben Hetland
      • Re: include files and long fixed form lines, Richard E Maine
      • Re: include files and long fixed form lines, James Giles
    • Re: include files and long fixed form lines, Brooks Moses
      • Re: include files and long fixed form lines, robin
      • Re: include files and long fixed form lines, Brooks Moses
      • Re: include files and long fixed form lines, Richard E Maine
    • Re: include files and long fixed form lines, robin
  • Re: include files and long fixed form lines, robin
• generating a random permutation, Bart Vandewoestyne
  • Re: generating a random permutation, Bart Vandewoestyne
    • Re: generating a random permutation, Michael Metcalf
  • Re: generating a random permutation, Joe Krahn
  • Re: generating a random permutation, Jan Vorbrüggen
  • Re: generating a random permutation, ttw
    • Re: generating a random permutation, Michael Metcalf
• [Looking For] example of FSA for lexical analysis, leconte.jerome1
• short question concerning SIZE, Tom
  • Re: short question concerning SIZE, Brooks Moses
    • Re: short question concerning SIZE, James Giles
      • Re: short question concerning SIZE, robert . corbett
      • Re: short question concerning SIZE, Tom
      • Re: short question concerning SIZE, Michael Metcalf
      • Re: short question concerning SIZE, Richard E Maine
      • Re: short question concerning SIZE, glen herrmannsfeldt
      • Re: short question concerning SIZE, Gordon Sande
      • Re: short question concerning SIZE, glen herrmannsfeldt
    • Re: short question concerning SIZE, Richard Maine
  • Re: short question concerning SIZE, Rich Townsend
  • Re: short question concerning SIZE, robin
    • Re: short question concerning SIZE, Dick Hendrickson
• Translate Fortran to Java, Gib Bogle
  • Re: Translate Fortran to Java, Kevin G. Rhoads
  • Re: Translate Fortran to Java, Rich Townsend
    • Re: Translate Fortran to Java, Gib Bogle
  • Re: Translate Fortran to Java, David Frank
    • Re: Translate Fortran to Java, Rich Townsend
      • Re: Translate Fortran to Java, David Frank
      • Re: Translate Fortran to Java, Rich Townsend
      • Re: Translate Fortran to Java, Michael Wild
      • Re: Translate Fortran to Java, David Frank
      • Re: Translate Fortran to Java, Rich Townsend
      • Re: Translate Fortran to Java, David Frank
      • Re: Translate Fortran to Java, Rich Townsend
      • Re: Translate Fortran to Java, Joe Krahn
    • Re: Translate Fortran to Java, Gib Bogle
      • Re: Translate Fortran to Java, Joe Krahn
      • Re: Translate Fortran to Java, Gary L. Scott
  • Re: Translate Fortran to Java, kia
    • Re: Translate Fortran to Java, Gib Bogle
      • Re: Translate Fortran to Java, kia
      • Re: Translate Fortran to Java, Gary L. Scott
• What's up with Lahey?, awgreynolds
  • Re: What's up with Lahey?, Richard E Maine
  • Re: What's up with Lahey?, Steven G. Kargl
  • Re: What's up with Lahey?, beliavsky
    • Re: What's up with Lahey?, Brooks Moses
• Derived types with pointer arrays. Functions to extract data, Arno
  • Re: Derived types with pointer arrays. Functions to extract data, Michael Metcalf
    • Re: Derived types with pointer arrays. Functions to extract data, Arno
  • Re: Derived types with pointer arrays. Functions to extract data, Richard E Maine
  • Re: Derived types with pointer arrays. Functions to extract data, Joe Krahn
• OpenMP problem, Matthias Möller
  • Re: OpenMP problem, Dan Nagle
    • Re: OpenMP problem, Matthias Möller
• Is this ordering procedure dangerous?, lello
  • Re: Is this ordering procedure dangerous?, Joost
    • Re: Is this ordering procedure dangerous?, Jan Vorbrüggen
  • Re: Is this ordering procedure dangerous?, David Frank
    • Re: Is this ordering procedure dangerous?, lello
• Fortran Exception: Too Many Names. Table Limit now 802, Kiran Pannu
  • Re: Fortran Exception: Too Many Names. Table Limit now 802, Paul Van Delst
  • Re: Fortran Exception: Too Many Names. Table Limit now 802, Richard E Maine
• help: how to call fortran95 routine of Intel Math Kernel Library in CVF, andywenj@xxxxxxxxx
  • <Possible follow-ups>
  • help: how to call fortran95 routine of Intel Math Kernel Library in CVF, andywenj@xxxxxxxxx
    • Re: help: how to call fortran95 routine of Intel Math Kernel Library in CVF, Steve Lionel
• Just fo fun: a minimal implementation of QuickSort, Arjen Markus
  • Re: Just fo fun: a minimal implementation of QuickSort, Joost
  • Re: Just fo fun: a minimal implementation of QuickSort, Salvatore
    • Re: Just fo fun: a minimal implementation of QuickSort, Arjen Markus
  • Re: Just fo fun: a minimal implementation of QuickSort, James Giles
  • Re: Just fo fun: a minimal implementation of QuickSort, analyst41
    • Re: Just fo fun: a minimal implementation of QuickSort, e p chandler
      • Re: Just fo fun: a minimal implementation of QuickSort, James Giles
      • Re: Just fo fun: a minimal implementation of QuickSort, James Giles
      • Re: Just fo fun: a minimal implementation of QuickSort, ttw
      • Re: Just fo fun: a minimal implementation of QuickSort, Brooks Moses
      • Re: Just fo fun: a minimal implementation of QuickSort, Joe Krahn
      • Re: Just fo fun: a minimal implementation of QuickSort, Arjen Markus
      • Real ODE fun - [was: Just fo fun: a minimal implementation of QuickSort], kia
      • Re: Real ODE fun - [was: Just fo fun: a minimal implementation of QuickSort], Arjen Markus
• Do compilers recognize branching within fast loops, Niels L Ellegaard
  • Re: Do compilers recognize branching within fast loops, Greg Lindahl
  • Re: Do compilers recognize branching within fast loops, glen herrmannsfeldt
    • Re: Do compilers recognize branching within fast loops, Brooks Moses
      • Re: Do compilers recognize branching within fast loops, glen herrmannsfeldt
      • Re: Do compilers recognize branching within fast loops, Tim Prince
  • Re: Do compilers recognize branching within fast loops, beliavsky
  • Re: Do compilers recognize branching within fast loops, s8ngsu3
    • Re: Do compilers recognize branching within fast loops, Arjen Markus
    • Re: Do compilers recognize branching within fast loops, Tim Prince
• Using g95 with MATLAB (MAC OS X), tlaloc
  • Re: Using g95 with MATLAB (MAC OS X), Richard Maine
    • Re: Using g95 with MATLAB (MAC OS X), tlaloc
• Lost BLOCKDATA initialisation in LIB files, PJH
  • Re: Lost BLOCKDATA initialisation in LIB files, Michael Metcalf
    • Re: Lost BLOCKDATA initialisation in LIB files, PJH
      • Re: Lost BLOCKDATA initialisation in LIB files, Dan Nagle
      • Re: Lost BLOCKDATA initialisation in LIB files, Gordon Sande
      • Re: Lost BLOCKDATA initialisation in LIB files, Joost
      • Re: Lost BLOCKDATA initialisation in LIB files, Gordon Sande
      • Re: Lost BLOCKDATA initialisation in LIB files, Richard E Maine
      • Re: Lost BLOCKDATA initialisation in LIB files, Dan Nagle
      • Re: Lost BLOCKDATA initialisation in LIB files, Richard E Maine
      • Re: Lost BLOCKDATA initialisation in LIB files, Richard E Maine
      • Re: Lost BLOCKDATA initialisation in LIB files, Joe Krahn
      • Re: Lost BLOCKDATA initialisation in LIB files, Richard E Maine
      • Re: Lost BLOCKDATA initialisation in LIB files, Joe Krahn
      • Re: Lost BLOCKDATA initialisation in LIB files, Joe Krahn
      • Re: Lost BLOCKDATA initialisation in LIB files, glen herrmannsfeldt
  • Re: Lost BLOCKDATA initialisation in LIB files, PJH
• how to call the functions using index, rotarywing
  • Re: how to call the functions using index, Michael Metcalf
    • Re: how to call the functions using index, rotarywing
• OpenGL to g95 (g95gl WIn32), leszpol
  • Re: OpenGL to g95 (g95gl WIn32), Dan Nagle
    • Re: OpenGL to g95 (g95gl WIn32), leszpol
      • Re: OpenGL to g95 (g95gl WIn32), Dan Nagle
      • Re: OpenGL to g95 (g95gl WIn32), leszpol
• Re: command line input and output, gnohmon
  • Re: command line input and output, Brooks Moses
• CVF DLL, problems reading binary file, johan
  • Re: CVF DLL, problems reading binary file, Dick Hendrickson
  • Re: CVF DLL, problems reading binary file, e p chandler
  • Re: CVF DLL, problems reading binary file, Colin Watters
    • Re: CVF DLL, problems reading binary file, Jan Vorbrüggen
      • Re: CVF DLL, problems reading binary file, johan
• Compaq Visual Fortran help: cannot save file, andywenj@xxxxxxxxx
  • Re: Compaq Visual Fortran help: cannot save file, Michael Metcalf
  • Re: Compaq Visual Fortran help: cannot save file, Steve Lionel
    • Re: Compaq Visual Fortran help: cannot save file, Steve Lionel
    • Re: Compaq Visual Fortran help: cannot save file, andywenj@xxxxxxxxx
• help: stack overflow, andywenj@xxxxxxxxx
  • Re: stack overflow, Michael Metcalf
    • Re: stack overflow, andywenj@xxxxxxxxx
  • Re: help: stack overflow, N. Shamsundar
• ANN: Free F version of Fortran Tools, Walt Brainerd
  • Re: Free F version of Fortran Tools, John Fredrickson
    • Re: Free F version of Fortran Tools, Walt Brainerd
• Number to string conversion without internal writes, comp.text.tex
  • Re: Number to string conversion without internal writes, Paul Van Delst
  • Re: Number to string conversion without internal writes, beliavsky
  • Re: Number to string conversion without internal writes, Richard Maine
    • Re: Number to string conversion without internal writes, comp.text.tex
      • Re: Number to string conversion without internal writes, Richard Maine
      • Re: Number to string conversion without internal writes, beliavsky
      • Re: Number to string conversion without internal writes, glen herrmannsfeldt
      • Re: Number to string conversion without internal writes, Richard Maine
      • Re: Number to string conversion without internal writes, glen herrmannsfeldt
      • Re: Number to string conversion without internal writes, Dan Nagle
      • Re: Number to string conversion without internal writes, Richard Maine
      • Re: Number to string conversion without internal writes, Louis Krupp
      • Re: Number to string conversion without internal writes, Richard Maine
      • Re: Number to string conversion without internal writes, glen herrmannsfeldt
      • Re: Number to string conversion without internal writes, Brooks Moses
      • Re: Number to string conversion without internal writes, James Giles
      • Re: Number to string conversion without internal writes, Brooks Moses
      • Re: Number to string conversion without internal writes, glen herrmannsfeldt
      • Re: Number to string conversion without internal writes, Brooks Moses
      • Re: Number to string conversion without internal writes, Walter Spector
      • Re: Number to string conversion without internal writes, James Giles
      • Re: Number to string conversion without internal writes, Brooks Moses
      • Re: Number to string conversion without internal writes, Walter Spector
      • Re: Number to string conversion without internal writes, James Giles
      • Re: Number to string conversion without internal writes, Brooks Moses
      • Re: Number to string conversion without internal writes, James Giles
  • Re: Number to string conversion without internal writes, Ken Plotkin
• COM/Automation problem with CVF 6.x, Vladimir Vasilchenko
  • Re: COM/Automation problem with CVF 6.x, Les
  • Re: COM/Automation problem with CVF 6.x, kia
• Sparse matrix subroutines for Fortran?, Wong Yung
  • Re: Sparse matrix subroutines for Fortran?, Alfredo Buttari
    • Re: Sparse matrix subroutines for Fortran?, Wong Yung
  • Re: Sparse matrix subroutines for Fortran?, Helge Avlesen
  • Re: Sparse matrix subroutines for Fortran?, Damien
    • Re: Sparse matrix subroutines for Fortran?, Wong Yung
      • Re: Sparse matrix subroutines for Fortran?, glen herrmannsfeldt
      • Re: Sparse matrix subroutines for Fortran?, beliavsky
      • Re: Sparse matrix subroutines for Fortran?, Pierre Asselin
      • Re: Sparse matrix subroutines for Fortran?, Pierre Asselin
      • Re: Sparse matrix subroutines for Fortran?, Victor Eijkhout
  • Re: Sparse matrix subroutines for Fortran?, Dirk Clasen
• Initialization of local variables, Joe Krahn
  • Re: Initialization of local variables, jwm
  • Re: Initialization of local variables, Richard E Maine
  • Re: Initialization of local variables, glen herrmannsfeldt
• Strategy Pattern, Ben Hetland
  • Re: Strategy Pattern, Arjen Markus
    • Re: Strategy Pattern, Ben Hetland
    • Re: Strategy Pattern, Patrick Begou
      • Re: Strategy Pattern, Ian Chivers
      • Re: Strategy Pattern, i . chivers
• Pointer as Argument to procedure, Colin Watters
  • Re: Pointer as Argument to procedure, James Giles
  • Re: Pointer as Argument to procedure, Richard E Maine
    • Re: Pointer as Argument to procedure, Colin Watters
• Arpack - complex Hermitian driver?, Wong Yung
• Parser test samples?, Joe Krahn
  • Re: Parser test samples?, Michael Metcalf
  • Re: Parser test samples?, Arjen Markus
    • Re: Parser test samples?, James Giles
  • Re: Parser test samples?, Dick Hendrickson
• read in a dummy variable without declaring variable...possibe?, Ben
  • Re: read in a dummy variable without declaring variable...possibe?, Dick Hendrickson
    • Re: read in a dummy variable without declaring variable...possibe?, Ben
      • Re: read in a dummy variable without declaring variable...possibe?, Joe Krahn
  • Re: read in a dummy variable without declaring variable...possibe?, John Harper
    • Re: read in a dummy variable without declaring variable...possibe?, Ben
      • Re: read in a dummy variable without declaring variable...possibe?, Jan Vorbrüggen
      • Re: read in a dummy variable without declaring variable...possibe?, Ben
  • Re: read in a dummy variable without declaring variable...possibe?, glen herrmannsfeldt
• Small arrays and loop performance, s8ngsu3
  • Re: Small arrays and loop performance, Jim
    • Re: Small arrays and loop performance, Tim Prince
  • Re: Small arrays and loop performance, Mark Mackey
  • Re: Small arrays and loop performance, Richard E Maine
    • Re: Small arrays and loop performance, Paul Van Delst
      • Re: Small arrays and loop performance, Gordon Sande
      • Re: Small arrays and loop performance, Colin Watters
  • Re: Small arrays and loop performance, Greg Lindahl
  • Re: Small arrays and loop performance, s8ngsu3
    • Re: Small arrays and loop performance, Arjen Markus
• where/forall question, Bruce Bowler
  • Re: where/forall question, Joost
    • Re: where/forall question, Bruce Bowler
  • Re: where/forall question, Michael Metcalf
    • Re: where/forall question, Dick Hendrickson
      • Re: where/forall question, Michael Metcalf
  • Re: where/forall question, beliavsky
  • Re: where/forall question, Brooks Moses
• ifc7.1 and c++, Claudenê Correia
  • Re: ifc7.1 and c++, simon
  • Re: ifc7.1 and c++, Tim Prince
  • Re: ifc7.1 and c++, Tim Prince
  • Re: ifc7.1 and c++, Jan Vorbrüggen
• Error handling in I/O Statements, Jerry DeLisle
  • Re: Error handling in I/O Statements, Brooks Moses
  • Re: Error handling in I/O Statements, Richard E Maine
    • Re: Error handling in I/O Statements, Jerry DeLisle
    • Re: Error handling in I/O Statements, Brooks Moses
      • Re: Error handling in I/O Statements, Dan Nagle
      • Re: Error handling in I/O Statements, Richard E Maine
      • Re: Error handling in I/O Statements, Dan Nagle
      • Re: Error handling in I/O Statements, Steven G. Kargl
      • Re: Error handling in I/O Statements, Richard E Maine
      • Re: Error handling in I/O Statements, Brooks Moses
• Any way to use fortran90 module in C?, Yuan MEI
  • Re: Any way to use fortran90 module in C?, Richard Maine
    • Re: Any way to use fortran90 module in C?, glen herrmannsfeldt
      • Re: Any way to use fortran90 module in C?, Dave Thompson
      • Re: Any way to use fortran90 module in C?, glen herrmannsfeldt
      • Re: Any way to use fortran90 module in C?, Joe Krahn
  • Re: Any way to use fortran90 module in C?, Joe Krahn
• reading the number of unknown rows and columns, kbaum
  • Re: reading the number of unknown rows and columns, glen herrmannsfeldt
  • Re: reading the number of unknown rows and columns, Catherine Rees Lay
    • Re: reading the number of unknown rows and columns, caola
  • Re: reading the number of unknown rows and columns, Arjen Markus
  • Re: reading the number of unknown rows and columns, Michael Wild
  • Re: reading the number of unknown rows and columns, David Frank
    • Re: reading the number of unknown rows and columns, glen herrmannsfeldt
      • Re: reading the number of unknown rows and columns, David Frank
      • Re: reading the number of unknown rows and columns, Delie
      • Re: reading the number of unknown rows and columns, beliavsky
      • Re: reading the number of unknown rows and columns, Michael Metcalf
      • Re: reading the number of unknown rows and columns, David Frank
      • Re: reading the number of unknown rows and columns, Rich Townsend
      • Re: reading the number of unknown rows and columns, robin
• Re: DBF file format, Clive Page
  • Re: DBF file format, Arjen Markus
    • Re: DBF file format, Richard E Maine
      • Re: DBF file format, Arjen Markus
      • Re: DBF file format, Clive Page
      • Re: DBF file format, Richard Maine
• Coding guidelines question, Paul Van Delst
  • Re: Coding guidelines question, Richard E Maine
  • Re: Coding guidelines question, James Giles
  • Re: Coding guidelines question, beliavsky
    • Re: Coding guidelines question, Dan Nagle
    • Re: Coding guidelines question, Paul Van Delst
      • Re: Coding guidelines question, Pierre Asselin
      • Re: Coding guidelines question, Dan Nagle
      • Re: Coding guidelines question, Pierre Asselin
      • Re: Coding guidelines question, Dave Thompson
      • Re: Coding guidelines question, Richard Edgar
      • Re: Coding guidelines question, Pierre Asselin
  • Re: Coding guidelines question, Richard Edgar
    • Re: Coding guidelines question, Arjen Markus
      • Re: Coding guidelines question, Richard E Maine
      • Re: Coding guidelines question, Paul Van Delst
      • Re: Coding guidelines question, Richard E Maine
      • Re: Coding guidelines question, Keith Refson
      • Re: Coding guidelines question, Richard E Maine
  • Re: Coding guidelines question, Joe Krahn
  • Re: Coding guidelines question, Keith Refson
    • Re: Coding guidelines question, Bil Kleb
  • Re: Coding guidelines question, Bil Kleb
  • Re: Coding guidelines question, Catherine Rees Lay
    • Re: Coding guidelines question, Michael Wild
    • Re: Coding guidelines question, Dan Nagle
      • Re: Coding guidelines question, Catherine Rees Lay
      • Re: Coding guidelines question, Dan Nagle
    • Re: Coding guidelines question, Richard E Maine
      • Re: Coding guidelines question, Paul Van Delst
    • Re: Coding guidelines question, James Giles
      • Re: Coding guidelines question, Rich Townsend
      • Re: Coding guidelines question, James Giles
      • Re: Coding guidelines question, Rich Townsend
      • Re: Coding guidelines question, James Giles
      • Re: Coding guidelines question, Rich Townsend
      • Re: Coding guidelines question, James Giles
      • Re: Coding guidelines question, Rich Townsend
      • Re: Coding guidelines question, Dan Nagle
      • Re: Coding guidelines question, Rich Townsend
      • Re: Coding guidelines question, James Giles
      • Re: Coding guidelines question, Rich Townsend
      • Re: Coding guidelines question, James Giles
      • Re: Coding guidelines question, Rich Townsend
      • Re: Coding guidelines question, Paul Van Delst
      • Re: Coding guidelines question, Richard Edgar
      • Re: Coding guidelines question, James Giles
      • Re: Coding guidelines question, Pierre Asselin
      • Re: Coding guidelines question, James Giles
      • Re: Coding guidelines question, Walt Brainerd
      • Re: Coding guidelines question, Paul Van Delst
      • Re: Coding guidelines question, James Giles
      • Re: Coding guidelines question, Bil Kleb
      • Re: Coding guidelines question, Pierre Asselin
      • Re: Coding guidelines question, Paul Van Delst
      • Re: Coding guidelines question, Bil Kleb
      • Re: Coding guidelines question, Paul Van Delst
      • Re: Coding guidelines question, Pierre Asselin
      • Re: Coding guidelines question, Paul Van Delst
      • Re: Coding guidelines question, Bil Kleb
      • Re: Coding guidelines question, James Giles
      • Re: Coding guidelines question, Walt Brainerd
      • Re: Coding guidelines question, James Giles
      • Re: Coding guidelines question, glen herrmannsfeldt
      • Re: Coding guidelines question, James Giles
      • Re: Coding guidelines question, John Harper
      • Re: Coding guidelines question, James Giles
      • Re: Coding guidelines question, Gordon Sande
      • Re: Coding guidelines question, beliavsky
• READ file positioning, chris
  • Re: READ file positioning, Richard E Maine
    • Re: READ file positioning, Joe Krahn
      • Re: READ file positioning, Jim
• spaces in path for Fortran 77 open routine, dflorian
  • Re: spaces in path for Fortran 77 open routine, Richard E Maine
    • Re: spaces in path for Fortran 77 open routine, dflorian
      • Re: spaces in path for Fortran 77 open routine, Mark Hadfield
      • Re: spaces in path for Fortran 77 open routine, Richard Maine
      • Re: spaces in path for Fortran 77 open routine, Ian Gay
  • RE: spaces in path for Fortran 77 open routine, meek
    • Re: spaces in path for Fortran 77 open routine, Dan Nagle
      • RE: spaces in path for Fortran 77 open routine, meek
      • Re: spaces in path for Fortran 77 open routine, Dan Nagle
      • RE: spaces in path for Fortran 77 open routine, meek
    • Re: spaces in path for Fortran 77 open routine, Richard E Maine
• Default initialization and save, kfitch42@xxxxxxxxx
  • Re: Default initialization and save, Brooks Moses
  • Re: Default initialization and save, Richard E Maine
    • Re: Default initialization and save, Herman D . Knoble
      • Re: Default initialization and save, Richard E Maine
      • Re: Default initialization and save, Steve Lionel
      • Re: Default initialization and save, Richard E Maine
      • Re: Default initialization and save, Herman D . Knoble
      • Re: Default initialization and save, Steven Correll
      • Re: Default initialization and save, Herman D . Knoble
      • Re: Default initialization and save, Steven Correll
      • Re: Default initialization and save, Herman D . Knoble
    • Re: Default initialization and save, Herman D . Knoble
      • Re: Default initialization and save, Richard E Maine
      • Re: Default initialization and save, Herman D . Knoble
  • Re: Default initialization and save, Richard E Maine
    • Re: Default initialization and save, kfitch42@xxxxxxxxx
      • Re: Default initialization and save, Richard E Maine
      • Re: Default initialization and save, kfitch42@xxxxxxxxx
      • Re: Default initialization and save, James Giles
      • Re: Default initialization and save, Richard E Maine
      • Re: Default initialization and save, Colin Watters
      • Re: Default initialization and save, Jan Vorbrüggen
      • Re: Default initialization and save, Richard E Maine
      • Re: Default initialization and save, Colin Watters
• Standard PRAGMAs?, Joe Krahn
  • Re: Standard PRAGMAs?, Richard E Maine
    • Re: Standard PRAGMAs?, Joe Krahn
• Allocatable derived type components fail, J Kaplan
  • Re: Allocatable derived type components fail, Richard E Maine
    • Re: Allocatable derived type components fail, jwm
      • Re: Allocatable derived type components fail, Dan Nagle
      • Re: Allocatable derived type components fail, Richard E Maine
      • Re: Allocatable derived type components fail, J Kaplan
      • Re: Allocatable derived type components fail, jwm
      • Re: Allocatable derived type components fail, Richard Maine
      • Re: Allocatable derived type components fail, J Kaplan
      • Re: Allocatable derived type components fail, Jan Vorbrüggen
      • Re: Allocatable derived type components fail, Richard E Maine
• undefined reference to `_systemqq_', Oliver Vecernik
  • Re: undefined reference to `_systemqq_', Jan Vorbrüggen
• Re: fortran, robin
  • Re: fortran, Rich Townsend
  • Re: fortran, max
• How to avoid forward references in Modules?, Dan
  • Re: How to avoid forward references in Modules?, Michael Metcalf
  • Re: How to avoid forward references in Modules?, Colin Watters
  • Re: How to avoid forward references in Modules?, James Giles
  • Re: How to avoid forward references in Modules?, Ron Shepard
    • Re: How to avoid forward references in Modules?, James Giles
    • Re: How to avoid forward references in Modules?, Richard Maine
      • Re: How to avoid forward references in Modules?, Ron Shepard
      • Re: How to avoid forward references in Modules?, Richard E Maine
      • Re: How to avoid forward references in Modules?, James Giles
      • Re: How to avoid forward references in Modules?, Brooks Moses
      • Re: How to avoid forward references in Modules?, James Giles
      • Re: How to avoid forward references in Modules?, Jan Vorbrüggen
      • Re: How to avoid forward references in Modules?, kia
    • Re: How to avoid forward references in Modules?, Bil Kleb
      • Re: How to avoid forward references in Modules?, James Giles
      • Re: How to avoid forward references in Modules?, Bil Kleb
      • Re: How to avoid forward references in Modules?, James Giles
      • Re: How to avoid forward references in Modules?, Bil Kleb
      • Re: How to avoid forward references in Modules?, James Giles
      • Re: How to avoid forward references in Modules?, Richard E Maine
• suggestions for Fortran 2008 loops, beliavsky
  • Re: suggestions for Fortran 2008 loops, Richard Maine
    • Re: suggestions for Fortran 2008 loops, robin
      • Re: suggestions for Fortran 2008 loops, Brooks Moses
  • Re: suggestions for Fortran 2008 loops, Jan Vorbrüggen
  • Re: suggestions for Fortran 2008 loops, Niels L Ellegaard
    • Re: suggestions for Fortran 2008 loops, Michael Metcalf
      • Re: suggestions for Fortran 2008 loops, Gordon Sande
      • Re: suggestions for Fortran 2008 loops, Michael Metcalf
      • Re: suggestions for Fortran 2008 loops, Gordon Sande
    • Re: suggestions for Fortran 2008 loops, James Giles
• gprof call graph error?, Aravindakshan Babu
• g95 problem with HDF5, zpzhang
  • Re: g95 problem with HDF5, zhangzepu
    • Re: g95 problem with HDF5, Steven G. Kargl
      • Re: g95 problem with HDF5, zhangzepu
      • Re: g95 problem with HDF5, Steven G. Kargl
      • Re: g95 problem with HDF5, zhangzepu
      • Re: g95 problem with HDF5, Joost
      • Re: g95 problem with HDF5, Steven G. Kargl
      • Re: g95 problem with HDF5, zhangzepu
      • Re: g95 problem with HDF5, Steven G. Kargl
• G95 + in-line function, Jeff Layton
  • Re: G95 + in-line function, Michael Metcalf
  • Re: G95 + in-line function, Richard Maine
    • Re: G95 + in-line function, Joost
      • Re: G95 + in-line function, Joost
      • Re: G95 + in-line function, Jeff Layton
      • Re: G95 + in-line function, Richard Maine
• (Newbie) F77 - function returns wrong value, Ronny Mandal
  • Re: (Newbie) F77 - function returns wrong value, Dan Nagle
    • Re: (Newbie) F77 - function returns wrong value, Erik Edelmann
      • Re: (Newbie) F77 - function returns wrong value, Erik Edelmann
  • Re: (Newbie) F77 - function returns wrong value, Kevin G. Rhoads
  • Re: (Newbie) F77 - function returns wrong value, glen herrmannsfeldt
  • Re: (Newbie) F77 - function returns wrong value, James Giles
    • Re: (Newbie) F77 - function returns wrong value, Ronny Mandal
      • Re: (Newbie) F77 - function returns wrong value, Richard Maine
      • Re: (Newbie) F77 - function returns wrong value, glen herrmannsfeldt
      • Re: (Newbie) F77 - function returns wrong value, Richard Maine
      • Re: (Newbie) F77 - function returns wrong value, glen herrmannsfeldt
      • Re: (Newbie) F77 - function returns wrong value, Jan Vorbrüggen
  • Re: (Newbie) F77 - function returns wrong value, Ronny Mandal
• All things must pass?, William Asher
  • Re: All things must pass?, Michael Metcalf
    • Re: All things must pass?, William Asher
    • Re: All things must pass?, glen herrmannsfeldt
  • Re: All things must pass?, Herman D . Knoble
    • Re: All things must pass?, William Asher
  • Re: All things must pass?, glen herrmannsfeldt
    • Re: All things must pass?, William Asher
• size after failed allocation, Thomas Koenig
  • Re: size after failed allocation, Rich Townsend
    • Re: size after failed allocation, Rich Townsend
    • Re: size after failed allocation, Richard E Maine
• Multiple Key Sort in Fortran, Archie
  • Re: Multiple Key Sort in Fortran, Herman D . Knoble
    • Re: Multiple Key Sort in Fortran, Michel OLAGNON
  • Re: Multiple Key Sort in Fortran, Gordon Sande
  • Re: Multiple Key Sort in Fortran, glen herrmannsfeldt
  • Re: Multiple Key Sort in Fortran, Joe Krahn
    • Re: Multiple Key Sort in Fortran, Brooks Moses
      • Re: Multiple Key Sort in Fortran, Joe Krahn
• problem with intel math kernel, Ronald Haynes
  • Re: problem with intel math kernel, Steve Lionel
  • Re: problem with intel math kernel, N. Shamsundar
• F2003 syntax ambiguity?, Joe Krahn
  • Re: F2003 syntax ambiguity?, Richard Maine
    • Re: F2003 syntax ambiguity?, Joe Krahn
• f2003 source file suffix?, Joe Krahn
  • Re: f2003 source file suffix?, Colin Watters
    • Re: f2003 source file suffix?, Phillip Helbig---remove CLOTHES to reply
      • Re: f2003 source file suffix?, gary . l . scott
  • Re: f2003 source file suffix?, jwm
• Re: Converting fixed-to-free format, robin
  • Re: Converting fixed-to-free format, Michael Prager
  • Re: Converting fixed-to-free format, Ken Plotkin
    • Re: Converting fixed-to-free format, Joe Krahn
      • Re: Converting fixed-to-free format, Michael Metcalf
      • Re: Converting fixed-to-free format, Joe Krahn
      • Re: Converting fixed-to-free format, Michael Metcalf
      • Re: Converting fixed-to-free format, Ken Plotkin
      • Re: Converting fixed-to-free format, Richard Maine
      • Re: Converting fixed-to-free format, robin
      • Re: Converting fixed-to-free format, Ken Plotkin
      • Re: Converting fixed-to-free format, robin
      • Re: Converting fixed-to-free format, Ken Plotkin
      • Re: Converting fixed-to-free format, glen herrmannsfeldt
    • Re: Converting fixed-to-free format, robin
      • Re: Converting fixed-to-free format, Dan Nagle
      • Re: Converting fixed-to-free format, Ken Plotkin
      • Re: Converting fixed-to-free format, Richard Maine
      • Re: Converting fixed-to-free format, Dan Nagle
      • Re: Converting fixed-to-free format, Ken Plotkin
      • Re: Converting fixed-to-free format, Gary L. Scott
      • Re: Converting fixed-to-free format, Gordon Sande
      • Re: Converting fixed-to-free format, Dan Nagle
      • Re: Converting fixed-to-free format, robin
      • Re: Converting fixed-to-free format, Dan Nagle
      • Re: Converting fixed-to-free format, Rich Townsend
      • Re: Converting fixed-to-free format, robin
      • Re: Converting fixed-to-free format, robin
  • <Possible follow-ups>
  • Re: Converting fixed-to-free format, David Flower
    • Re: Converting fixed-to-free format, Joe Krahn
      • Re: Converting fixed-to-free format, James Giles
      • Re: Converting fixed-to-free format, Joe Krahn
      • Re: Converting fixed-to-free format, Richard E Maine
      • Re: Converting fixed-to-free format, Dave Thompson
  • Re: Converting fixed-to-free format, Ken Plotkin
    • Re: Converting fixed-to-free format, James Giles
    • Re: Converting fixed-to-free format, J. F. Cornwall
    • Re: Converting fixed-to-free format, Michael Metcalf
      • Re: Converting fixed-to-free format, J. F. Cornwall
  • Re: Converting fixed-to-free format, Ron Shepard
  • Re: Converting fixed-to-free format, George N. White III
    • Re: Converting fixed-to-free format, Gary L. Scott
      • Re: Converting fixed-to-free format, Gordon Sande
      • Re: Converting fixed-to-free format, James Giles
      • Re: Converting fixed-to-free format, robin
      • Re: Converting fixed-to-free format, James Giles
      • Re: Converting fixed-to-free format, robin
      • Re: Converting fixed-to-free format, James Giles
      • Re: Converting fixed-to-free format, glen herrmannsfeldt
      • Re: Converting fixed-to-free format, James Giles
      • Re: Converting fixed-to-free format, robin
      • Re: Converting fixed-to-free format, James Giles
      • Re: Converting fixed-to-free format, robin
      • Re: Converting fixed-to-free format, Dan Nagle
      • Re: Converting fixed-to-free format, Joe Krahn
      • Re: Converting fixed-to-free format, Dan Nagle
      • Re: Converting fixed-to-free format, robin
      • Re: Converting fixed-to-free format, robin
      • Re: Converting fixed-to-free format, Dan Nagle
      • Re: Converting fixed-to-free format, robin
      • Re: Converting fixed-to-free format, Dan Nagle
      • Re: Converting fixed-to-free format, glen herrmannsfeldt
      • Re: Converting fixed-to-free format, Dan Nagle
      • Re: Converting fixed-to-free format, robin
      • Re: Converting fixed-to-free format, Dan Nagle
      • Re: Converting fixed-to-free format, robin
      • Re: Converting fixed-to-free format, Dan Nagle
      • Re: Converting fixed-to-free format, glen herrmannsfeldt
      • Re: Converting fixed-to-free format, Joe Krahn
      • Re: Converting fixed-to-free format, Brooks Moses
      • Re: Converting fixed-to-free format, Richard Maine
      • Re: Converting fixed-to-free format, Brooks Moses
      • Re: Converting fixed-to-free format, Richard E Maine
      • Re: Converting fixed-to-free format, Ken Plotkin
      • Re: Converting fixed-to-free format, glen herrmannsfeldt
      • Re: Converting fixed-to-free format, robin
      • Re: Converting fixed-to-free format, robin
      • Re: Converting fixed-to-free format, Dan Nagle
      • Re: Converting fixed-to-free format, robin
      • Re: Converting fixed-to-free format, glen herrmannsfeldt
      • Re: Converting fixed-to-free format, John Harper
      • Re: Converting fixed-to-free format, robin
      • Re: Converting fixed-to-free format, Rich Townsend
      • Re: Converting fixed-to-free format, robin
      • Re: Converting fixed-to-free format, Rich Townsend
      • Re: Converting fixed-to-free format, robin
      • Re: Converting fixed-to-free format, James Giles
      • Re: Converting fixed-to-free format, robin
      • Re: Converting fixed-to-free format, Rich Townsend
      • Re: Converting fixed-to-free format, James Giles
      • Re: Converting fixed-to-free format, robin
      • Re: Converting fixed-to-free format, James Giles
      • Re: Converting fixed-to-free format, robin
      • Re: Converting fixed-to-free format, James Giles
      • Re: Converting fixed-to-free format, robin
      • Re: Converting fixed-to-free format, James Giles
      • Re: WARNINGS, robin
      • Re: WARNINGS, Rich Townsend
      • Re: WARNINGS, Mr Hrundi V Bakshi
      • Re: WARNINGS, Rich Townsend
      • Re: WARNINGS, James Giles
      • Re: WARNINGS, Mr Hrundi V Bakshi
      • Re: WARNINGS, James Giles
      • Re: WARNINGS, Mr Hrundi V Bakshi
      • Re: WARNINGS, ttw
      • Re: WARNINGS, Richard Maine
      • Re: WARNINGS, Rich Townsend
      • Re: WARNINGS, James Giles
      • Re: WARNINGS, James Giles
      • Re: WARNINGS, James Giles
      • Re: WARNINGS, robin
      • Re: WARNINGS, Rich Townsend
      • Re: WARNINGS, robin
      • Re: WARNINGS, Dan Nagle
      • Re: WARNINGS, Gary L. Scott
      • Re: WARNINGS, Rich Townsend
      • Re: Converting fixed-to-free format, robin
      • Re: Converting fixed-to-free format, Ken Plotkin
      • Re: Converting fixed-to-free format, Dan Nagle
      • Re: Converting fixed-to-free format, J. F. Cornwall
      • Re: Converting fixed-to-free format, Dan Nagle
      • Re: Converting fixed-to-free format, J.F. Cornwall
      • Re: Converting fixed-to-free format, Brooks Moses
      • Re: Converting fixed-to-free format, Ken Plotkin
      • Re: Converting fixed-to-free format, kia
      • Re: Converting fixed-to-free format, Brooks Moses
    • Re: Converting fixed-to-free format, robin
      • Re: Converting fixed-to-free format, Rich Townsend
      • Re: Converting fixed-to-free format, robin
• Re: Variable length/precision formats?, robin
  • Re: Variable length/precision formats?, James Giles
    • Re: Variable length/precision formats?, robin
      • Re: Variable length/precision formats?, James Giles
      • Re: Variable length/precision formats?, Richard Maine
      • Re: Variable length/precision formats?, glen herrmannsfeldt
      • Re: Variable length/precision formats?, robin
      • Re: Variable length/precision formats?, glen herrmannsfeldt
      • Re: Variable length/precision formats?, Richard E Maine
      • Re: Variable length/precision formats?, glen herrmannsfeldt
      • Re: Variable length/precision formats?, Brooks Moses
      • Re: Variable length/precision formats?, glen herrmannsfeldt
      • Re: Variable length/precision formats?, robin
      • Re: Variable length/precision formats?, Dave Thompson
      • Re: Variable length/precision formats?, glen herrmannsfeldt
  • He's Ba-a-ack! Was: Re: Variable length/precision formats?, Dan Nagle
    • Re: Variable length/precision formats?, robin
  • <Possible follow-ups>
  • Re: Variable length/precision formats?, robert . corbett
    • Re: Variable length/precision formats?, John Harper
      • Re: Variable length/precision formats?, glen herrmannsfeldt
      • Re: Variable length/precision formats?, robin
      • Re: Variable length/precision formats?, John Harper
      • Re: Variable length/precision formats?, robin
  • Re: Variable length/precision formats?, robert . corbett
  • Re: Variable length/precision formats?, robert . corbett
  • Re: Variable length/precision formats?, robert . corbett
    • Re: Variable length/precision formats?, Joe Krahn
      • Re: Variable length/precision formats?, Richard Maine
      • Re: Variable length/precision formats?, Joe Krahn
      • Re: Variable length/precision formats?, Richard E Maine
      • Re: Variable length/precision formats?, glen herrmannsfeldt
      • Re: Variable length/precision formats?, Richard E Maine
      • Re: Variable length/precision formats?, Joe Krahn
      • Re: Variable length/precision formats?, glen herrmannsfeldt
      • Re: Variable length/precision formats?, robin
      • Re: Variable length/precision formats?, glen herrmannsfeldt
      • Re: Variable length/precision formats?, James Giles
      • Re: Variable length/precision formats?, robin
      • Re: Variable length/precision formats?, James Giles
      • Re: Variable length/precision formats?, robin
      • Re: Variable length/precision formats?, Rich Townsend
      • Re: Variable length/precision formats?, James Giles
      • Re: Variable length/precision formats?, robin
      • Re: Variable length/precision formats?, James Giles
      • Re: Variable length/precision formats?, James Giles
      • Re: Variable length/precision formats?, robin
      • Re: Variable length/precision formats?, Dan Nagle
      • Re: Variable length/precision formats?, robert . corbett
      • Re: Variable length/precision formats?, glen herrmannsfeldt
      • Re: Variable length/precision formats?, robin
      • Re: Variable length/precision formats?, Dan Nagle
      • Re: Variable length/precision formats?, robin
      • Re: Variable length/precision formats?, James Giles
      • Re: Variable length/precision formats?, robin
      • Re: Variable length/precision formats?, James Giles
      • Re: Variable length/precision formats?, robin
      • Re: Variable length/precision formats?, James Giles
      • Re: Variable length/precision formats?, robin
      • Re: Variable length/precision formats?, Dan Nagle
      • Re: Variable length/precision formats?, robin
      • Re: Variable length/precision formats?, robin
      • Re: Variable length/precision formats?, robert . corbett
      • Re: Variable length/precision formats?, James Giles
      • Re: Variable length/precision formats?, robert . corbett
      • Re: Variable length/precision formats?, James Giles
      • Re: Variable length/precision formats?, robert . corbett
      • Re: Variable length/precision formats?, James Giles
      • Re: Variable length/precision formats?, robin
      • Re: Variable length/precision formats?, glen herrmannsfeldt
      • Re: Variable length/precision formats?, robert . corbett
      • Re: Variable length/precision formats?, glen herrmannsfeldt
      • Re: Variable length/precision formats?, robert . corbett
      • Re: Variable length/precision formats?, James Giles
      • Re: Variable length/precision formats?, robert . corbett
      • Re: Variable length/precision formats?, James Giles
      • Re: Variable length/precision formats?, robert . corbett
      • Re: Variable length/precision formats?, glen herrmannsfeldt
      • Re: Variable length/precision formats?, robert . corbett
      • Re: Variable length/precision formats?, Dan Nagle
      • Re: Variable length/precision formats?, robin
      • Re: Variable length/precision formats?, robin
      • Re: Variable length/precision formats?, robin
      • Re: Variable length/precision formats?, robin
      • Re: Variable length/precision formats?, Rich Townsend
      • Re: Variable length/precision formats?, James Giles
      • Re: Variable length/precision formats?, robin
      • Re: Variable length/precision formats?, Dan Nagle
      • Re: Variable length/precision formats?, James Giles
      • Re: Variable length/precision formats?, Dan Nagle
      • Re: Variable length/precision formats?, James Giles
      • Re: Variable length/precision formats?, Dan Nagle
      • Re: Variable length/precision formats?, James Giles
      • Re: Variable length/precision formats?, Rich Townsend
      • Re: Variable length/precision formats?, Mr Hrundi V Bakshi
      • Re: Variable length/precision formats?, robin
      • Re: Variable length/precision formats?, robin
      • Re: Variable length/precision formats?, robin
      • Re: Variable length/precision formats?, Gordon Sande
      • Re: Variable length/precision formats?, robert . corbett
      • Re: Variable length/precision formats?, robin
      • Re: Variable length/precision formats?, robin
      • Re: Variable length/precision formats?, glen herrmannsfeldt
      • Re: Variable length/precision formats?, robert . corbett
      • Re: Variable length/precision formats?, glen herrmannsfeldt
      • Re: Variable length/precision formats?, robert . corbett
    • Re: Variable length/precision formats?, Dan Nagle
      • Re: Variable length/precision formats?, robert . corbett
  • Re: Variable length/precision formats?, Dave Thompson
    • Re: Variable length/precision formats?, glen herrmannsfeldt
  • Re: Variable length/precision formats?, robin
  • Re: Variable length/precision formats?, robin
• F2003 parsing, Joe Krahn
• Re: Informations about G95, Herman D . Knoble
  • Re: Informations about G95, Joost
    • Re: Informations about G95, Herman D . Knoble
  • <Possible follow-ups>
  • Re: Informations about G95, beliavsky
  • Re: Informations about G95, Walter
• Re: CVF under Linux using Wine ?, beliavsky
• Subroutine to let the CPU idle ?, Vincent MAGNIN
  • Re: Subroutine to let the CPU idle ?, Jan Vorbrüggen
    • Re: Subroutine to let the CPU idle ?, Vincent MAGNIN
      • Re: Subroutine to let the CPU idle ?, Ian Brown
      • Re: Subroutine to let the CPU idle ?, nikaggel
      • Re: Subroutine to let the CPU idle ?, Rich Townsend
      • Re: Subroutine to let the CPU idle ?, Mr Hrundi V Bakshi
• Re: get "undefined reference" with routines contained in a module, Hani Andreas Ibrahim
• g95 and Endianess, Jeff Layton
  • Re: g95 and Endianess, Helge Avlesen
  • Re: g95 and Endianess, ejko123
    • Re: g95 and Endianess, Paul Van Delst
      • Re: g95 and Endianess, Richard Maine
      • Re: g95 and Endianess, Paul Van Delst
      • Re: g95 and Endianess, Richard Maine
      • Re: g95 and Endianess, glen herrmannsfeldt
      • Re: g95 and Endianess, calvin . vu
      • Re: g95 and Endianess, ejko123
• Re: X-sudoku challenge (OT), Gib Bogle
  • Re: X-sudoku challenge (OT), Dr Ivan D. Reid
  • <Possible follow-ups>
  • Re: X-sudoku challenge (OT), Joe Krahn
    • Re: X-sudoku challenge (OT), Michael Metcalf
• Re: dll fortran for visual basic .net (little bit long data output), michael
  • <Possible follow-ups>
  • Re: dll fortran for visual basic .net (little bit long data output), R. MacDonald
    • Re: dll fortran for visual basic .net (little bit long data output), cappa
• Re: Illegal internal write?, John Harper
  • Re: Illegal internal write?, Richard Maine
  • Re: Illegal internal write?, glen herrmannsfeldt
    • Re: Illegal internal write?, John Harper
      • Re: Illegal internal write?, Steven G. Kargl
  • Re: Illegal internal write?, robert . corbett
    • Re: Illegal internal write?, glen herrmannsfeldt
      • Re: Illegal internal write?, Dave Thompson
      • Re: Illegal internal write?, Gary L. Scott
      • Re: Illegal internal write?, glen herrmannsfeldt
      • Re: Illegal internal write?, Richard Maine
      • Re: Illegal internal write?, glen herrmannsfeldt
      • Re: Illegal internal write?, Dave Thompson
      • Re: Illegal internal write?, glen herrmannsfeldt
      • Re: Illegal internal write?, John Harper
    • Re: Illegal internal write?, Steven G. Kargl
      • Re: Illegal internal write?, glen herrmannsfeldt
      • Re: Illegal internal write?, Richard Maine
      • Re: Illegal internal write?, James Giles
      • Re: Illegal internal write?, John Harper
      • Re: Illegal internal write?, Steven G. Kargl
  • <Possible follow-ups>
  • Re: Illegal internal write?, Dick Hendrickson
    • Re: Illegal internal write?, Joe Krahn
      • Re: Illegal internal write?, Richard Maine
  • Re: Illegal internal write?, Richard E Maine
• Re: Python for Fortran programmers, Joe Krahn
  • Re: Python for Fortran programmers, Helge Avlesen
  • Re: Python for Fortran programmers, Bil Kleb
  • Re: Python for Fortran programmers, Cameron Laird
  • Re: Python for Fortran programmers, Cameron Laird
    • Re: Python for Fortran programmers, Joe Krahn
    • Re: Python for Fortran programmers, Brian Elmegaard
      • Re: Python for Fortran programmers, Bil Kleb
      • Re: Python for Fortran programmers, Brian Elmegaard
      • Re: Python for Fortran programmers, Bil Kleb
  • Re: Python for Fortran programmers, Cameron Laird
    • Re: Python for Fortran programmers, Joe Krahn
      • Re: Python for Fortran programmers, Pierre Asselin
      • Re: Python for Fortran programmers, Harold Stevens
      • Re: Python for Fortran programmers, Cameron Laird
      • Re: Python for Fortran programmers, Bil Kleb
      • Re: Python for Fortran programmers, Cameron Laird
      • Re: Python for Fortran programmers, Brooks Moses
      • Re: Python for Fortran programmers, Pierre Asselin
    • Re: Python for Fortran programmers, Bil Kleb
  • <Possible follow-ups>
  • Re: Python for Fortran programmers, Joe Krahn
  • Re: Python for Fortran programmers, Michael Wild
  • Re: Python for Fortran programmers, mtobis
    • Re: Python for Fortran programmers, beliavsky
      • Re: Python for Fortran programmers, mtobis
  • Re: Python for Fortran programmers, mtobis
    • Re: Python for Fortran programmers, Bil Kleb
    • Re: Python for Fortran programmers, mtobis
    • Re: Python for Fortran programmers, mtobis
    • test harnesses (was: Python for Fortran programmers), Pierre Asselin
      • Re: test harnesses, Bil Kleb
      • Re: test harnesses, Arjen Markus
      • Re: test harnesses, Bil Kleb
      • Re: test harnesses (was: Python for Fortran programmers), mtobis
  • Re: Python for Fortran programmers, mtobis
    • Re: Python for Fortran programmers, Bil Kleb
    • Re: Python for Fortran programmers, Jan Vorbrüggen
    • Re: Python for Fortran programmers, beliavsky
  • Re: Python for Fortran programmers, mtobis
  • Re: Python for Fortran programmers, Bil Kleb

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