comp.lang.fortran

• Date Index

---

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

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