comp.lang.fortran

• Thread Index

---

• Re: question about using array intrinsic functions
  • From: PCAT
• Re: Allocatable attribute on derived type components
  • From: Richard E Maine
• Re: EDITOR: Compaq Visual Fortran
  • From: Craig Powers
• Re: question about using array intrinsic functions
  • From: Steven G. Kargl
• question about using array intrinsic functions
  • From: PCAT
• Re: EDITOR: Compaq Visual Fortran
  • From: kis
• Re: EDITOR: Compaq Visual Fortran
  • From: Craig Powers
• Re: EDITOR: Compaq Visual Fortran
  • From: dpb
• Re: Allocatable attribute on derived type components
  • From: gaurav
• Re: recl on g95 and gfortran
  • From: UHAP023
• Re: How to Find Memory Used (IVF 9.1, WinXP)
  • From: dpb
• EDITOR: Compaq Visual Fortran
  • From: kis
• [ANN] fUnit 0.1.3 - A Fortran Unit Testing Framework
  • From: Bil Kleb
• Re: removing blanks from a file
  • From: dpb
• Re: WRITE, FORMAT problem
  • From: Richard E Maine
• Re: Random Numbers
  • From: Walt Brainerd
• Re: automatic variables are not initialized correctly?
  • From: Jugoslav Dujic
• Re: removing blanks from a file
  • From: Luka Djigas
• Re: Random Numbers
  • From: CTallant
• Re: How to Find Memory Used (IVF 9.1, WinXP)
  • From: Jugoslav Dujic
• Re: removing blanks from a file
  • From: Luka Djigas
• Re: Allocatable attribute on derived type components
  • From: Arjen Markus
• Allocatable attribute on derived type components
  • From: gaurav
• Re: removing blanks from a file
  • From: David Frank
• Re: linking g95-built library from VC++
  • From: Jugoslav Dujic
• Re: removing blanks from a file
  • From: David Frank
• Re: pass several filenames to the subroutine
  • From: Ian Bush
• Re: WRITE, FORMAT problem
  • From: Ian Bush
• Re: WRITE, FORMAT problem
  • From: R. MacDonald
• Re: the hot key in CVF 6.6
  • From: Jugoslav Dujic
• the hot key in CVF 6.6
  • From: Mike
• WRITE, FORMAT problem
  • From: aborel
• pass several filenames to the subroutine
  • From: Mike
• Re: linking g95-built library from VC++
  • From: Matthew Halfant
• Re: Random Numbers
  • From: kia
• Re: Efficient way to pass different shaped arrays?
  • From: John Harper
• Re: removing blanks from a file
  • From: Richard Maine
• linking g95-built library from VC++
  • From: Matthew Halfant
• Re: removing blanks from a file
  • From: Luka Djigas
• Re: removing blanks from a file
  • From: dpb
• Re: removing blanks from a file
  • From: e p chandler
• Re: removing blanks from a file
  • From: glen herrmannsfeldt
• Re: removing blanks from a file
  • From: Bil Kleb
• Re: Fortran refactoring
  • From: Bil Kleb
• Re: removing blanks from a file
  • From: tholen
• removing blanks from a file
  • From: Luka Djigas
• Re: Efficient way to pass different shaped arrays?
  • From: glen herrmannsfeldt
• Re: Efficient way to pass different shaped arrays?
  • From: John Harper
• Re: How to Find Memory Used (IVF 9.1, WinXP)
  • From: John S
• Re: How to Find Memory Used (IVF 9.1, WinXP)
  • From: dpb
• Re: How to Find Memory Used (IVF 9.1, WinXP)
  • From: dpb
• Re: How to Find Memory Used (IVF 9.1, WinXP)
  • From: John S
• Re: Random Numbers
  • From: Steven G. Kargl
• Re: Random Numbers
  • From: Richard E Maine
• Re: How to Find Memory Used (IVF 9.1, WinXP)
  • From: Colin Watters
• Re: Random Numbers
  • From: Ken Fairfield
• Re: Random Numbers
  • From: Pierre Asselin
• Re: Random Numbers
  • From: Michael Metcalf
• Re: How to Find Memory Used (IVF 9.1, WinXP)
  • From: dpb
• Re: Random Numbers
  • From: Steven G. Kargl
• Re: Random Numbers
  • From: Dick Hendrickson
• Re: Random Numbers
  • From: dpb
• How to Find Memory Used (IVF 9.1, WinXP)
  • From: John S
• Re: Random Numbers
  • From: Richard E Maine
• Re: Random Numbers
  • From: dpb
• Random Numbers
  • From: CTallant
• Re: Efficient way to pass different shaped arrays?
  • From: Dick Hendrickson
• Re: Fortran refactoring
  • From: Ian Bush
• Re: heap allocation of arrays
  • From: Tim Prince
• Re: recl on g95 and gfortran
  • From: Richard Maine
• Re: Interface Question
  • From: A
• Re: heap allocation of arrays
  • From: Richard Maine
• Re: recl on g95 and gfortran
  • From: robert . corbett
• Re: recl on g95 and gfortran
  • From: robert . corbett
• Re: heap allocation of arrays
  • From: robert . corbett
• Re: Interfaces
  • From: Richard Maine
• Re: Interfaces
  • From: John Keenan
• Re: Efficient way to pass different shaped arrays?
  • From: Michael Metcalf
• Re: Efficient way to pass different shaped arrays?
  • From: glen herrmannsfeldt
• Re: Efficient way to pass different shaped arrays?
  • From: glen herrmannsfeldt
• Re: Efficient way to pass different shaped arrays?
  • From: Richard Maine
• Re: Efficient way to pass different shaped arrays?
  • From: Peter
• Re: Efficient way to pass different shaped arrays?
  • From: Michael Metcalf
• Re: Fortran refactoring
  • From: phillip.news@xxxxxxxxx
• Re: Fortran refactoring
  • From: Richard Maine
• Re: heap allocation of arrays
  • From: phillip.news@xxxxxxxxx
• Fortran refactoring
  • From: phillip.news@xxxxxxxxx
• Efficient way to pass different shaped arrays?
  • From: Peter
• Re: delay was due to parallel processing
  • From: max
• Re: recl on g95 and gfortran
  • From: Richard Maine
• Re: Fortran compiled executable form visual basic
  • From: max
• Re: recl on g95 and gfortran
  • From: Joost
• Re: automatic variables are not initialized correctly?
  • From: Brooks Moses
• Re: recl on g95 and gfortran
  • From: Richard Maine
• Re: Interface Question
  • From: Richard Maine
• Re: automatic variables are not initialized correctly?
  • From: Richard Maine
• Re: delay was due to parallel processing
  • From: Craig Powers
• Re: delay was due to parallel processing
  • From: Craig Powers
• Re: Non-recursive introspective sort in Fortran?
  • From: James Giles
• Re: Non-recursive introspective sort in Fortran?
  • From: Brooks Moses
• Re: Non-recursive introspective sort in Fortran?
  • From: Gordon Sande
• Fortran executable with Visual Basic : delay was due to parallel processing
  • From: aka
• delay was due to parallel processing
  • From: aka
• Re: Non-recursive introspective sort in Fortran?
  • From: jon
• Re: Non-recursive introspective sort in Fortran?
  • From: Gordon Sande
• Re: Non-recursive introspective sort in Fortran?
  • From: Arjen Markus
• Re: recl on g95 and gfortran
  • From: Michael Metcalf
• Re: Array size?
  • From: Michael Metcalf
• Re: Array size?
  • From: Dan Nagle
• Array size?
  • From: rjmagyar
• Re: automatic variables are not initialized correctly?
  • From: Gordon Sande
• Re: CVF compiler question, program giving inconsistent results
  • From: Tom Micevski
• Re: recl on g95 and gfortran
  • From: beliavsky
• Re: automatic variables are not initialized correctly?
  • From: David Flower
• Re: Interface Question
  • From: Arjen Markus
• Re: recl on g95 and gfortran
  • From: Arjen Markus
• Interface Question
  • From: A
• Re: automatic variables are not initialized correctly?
  • From: kia
• Re: opening files and code cleanup
  • From: Aidan
• Re: Fortran compiled executable form visual basic
  • From: glen herrmannsfeldt
• Re: Fortran compiled executable form visual basic
  • From: Michael Prager
• Re: using openmp section directive to break up a loop
  • From: Richard Edgar
• using openmp section directive to break up a loop
  • From: thewhites2000
• Fortran compiled executable form visual basic
  • From: akansha . khandelwal
• recl on g95 and gfortran
  • From: beliavsky
• Re: Polyhedron's compiler comparison updated with gfortran
  • From: awgreynolds
• Re: CVF compiler question, program giving inconsistent results
  • From: Kevin G. Rhoads
• Re: linking error
  • From: Richard E Maine
• Non-recursive introspective sort in Fortran?
  • From: jon
• linking error
  • From: Robert
• Re: Status of an iolist variable after READ error
  • From: Richard E Maine
• Re: Status of an iolist variable after READ error
  • From: awgreynolds
• Re: Status of an iolist variable after READ error
  • From: Richard E Maine
• Re: How to implement error line number in F95
  • From: Gareth Owen
• Re: Status of an iolist variable after READ error
  • From: awgreynolds
• Re: How to implement error line number in F95
  • From: Richard E Maine
• Re: How to implement error line number in F95
  • From: beliavsky
• Status of an iolist variable after READ error
  • From: awgreynolds
• How to implement error line number in F95
  • From: Karolina
• Re: array expressions - stack size
  • From: Sebastian Hanigk
• Re: array expressions - stack size
  • From: Jugoslav Dujic
• Re: Mixing FORTRAN with C!
  • From: Jugoslav Dujic
• Re: array expressions - stack size
  • From: Sebastian Hanigk
• Re: Mixing FORTRAN with C!
  • From: vashwath
• Re: Mixing FORTRAN with C!
  • From: Klaus Wacker
• Re: array expressions - stack size
  • From: Joost
• array expressions - stack size
  • From: Sebastian Hanigk
• Mixing FORTRAN with C!
  • From: vashwath
• Re: usually forgot to "use" some modules
  • From: Colin Watters
• Re: No enumeration data type in Fortran?
  • From: James Giles
• Polyhedron's compiler comparison updated with gfortran
  • From: Steven G. Kargl
• Re: how DEALLOCATE statement works in f2003
  • From: Jugoslav Dujic
• Re: No enumeration data type in Fortran?
  • From: Richard E Maine
• Re: Interfaces
  • From: Richard E Maine
• Re: automatic variables are not initialized correctly?
  • From: Richard E Maine
• Re: how DEALLOCATE statement works in f2003
  • From: Michael Metcalf
• Re: automatic variables are not initialized correctly?
  • From: glen herrmannsfeldt
• Re: maximum 1D array size
  • From: Herman D . Knoble
• how DEALLOCATE statement works in f2003
  • From: manish
• how DEALLOCATE works in f2003
  • From: manish
• Re: automatic variables are not initialized correctly?
  • From: Jugoslav Dujic
• Re: automatic variables are not initialized correctly?
  • From: glen herrmannsfeldt
• Re: Interfaces
  • From: glen herrmannsfeldt
• Re: catch RaiseException with VB.Net
  • From: jmdelfa@xxxxxxxxx
• Re: No enumeration data type in Fortran?
  • From: glen herrmannsfeldt
• Re: automatic variables are not initialized correctly?
  • From: glen herrmannsfeldt
• Re: automatic variables are not initialized correctly?
  • From: David Flower
• Re: automatic variables are not initialized correctly?
  • From: glen herrmannsfeldt
• Re: heap allocation of arrays
  • From: glen herrmannsfeldt
• Re: No enumeration data type in Fortran?
  • From: Brooks Moses
• Re: Interfaces
  • From: Richard Maine
• Re: Interfaces
  • From: Richard Maine
• Re: automatic variables are not initialized correctly?
  • From: Richard Maine
• Interfaces
  • From: John Keenan
• Re: heap allocation of arrays
  • From: Dave Thompson
• Re: automatic variables are not initialized correctly?
  • From: Dave Thompson
• Re: automatic variables are not initialized correctly?
  • From: Dave Thompson
• Re: No enumeration data type in Fortran?
  • From: Dave Thompson
• compilers and graphics libraries for Windows (was Re: Shortage of Fortran Programmers)
  • From: beliavsky
• Re: superb Lahey product LF95
  • From: beliavsky
• superb Lahey product LF95
  • From: analyst41
• Re: Best book to help transition from F77 to F90/95
  • From: Dan Nagle
• Re: CVF compiler question, program giving inconsistent results
  • From: Steven G. Kargl
• Re: CVF compiler question, program giving inconsistent results
  • From: bmurphy
• Re: CVF compiler question, program giving inconsistent results
  • From: Brooks Moses
• CVF compiler question, program giving inconsistent results
  • From: bmurphy
• Re: Best book to help transition from F77 to F90/95
  • From: Brooks Moses
• Re: Best book to help transition from F77 to F90/95
  • From: Dan Nagle
• Re: Best book to help transition from F77 to F90/95
  • From: Gary Scott
• Re: Best book to help transition from F77 to F90/95
  • From: Clive Page
• Re: usually forgot to "use" some modules
  • From: Jugoslav Dujic
• Re: usually forgot to "use" some modules
  • From: Mike
• Re: maximum 1D array size
  • From: Tim Prince
• Re: maximum 1D array size
  • From: Richard Maine
• Re: maximum 1D array size
  • From: Steven G. Kargl
• Re: Pointers to functions: Is this the right [f03] syntax?
  • From: Craig Powers
• Re: maximum 1D array size
  • From: optionstraderjeff
• Re: Pointers to functions: Is this the right [f03] syntax?
  • From: glen herrmannsfeldt
• Re: Allocate-on-write for strings?
  • From: Richard Maine
• Allocate-on-write for strings?
  • From: Joe Krahn
• Re: Windows/Dos memory -- when is Allocate/Deallocate necessary
  • From: Kevin G. Rhoads
• Re: Windows/Dos memory -- when is Allocate/Deallocate necessary
  • From: glen herrmannsfeldt
• Re: Pointers to functions: Is this the right [f03] syntax?
  • From: Ken Fairfield
• Re: GUI for fortran
  • From: Jim Klein
• Re: Windows/Dos memory -- when is Allocate/Deallocate necessary
  • From: Richard Maine
• Re: Pointers to functions: Is this the right [f03] syntax?
  • From: Dick Hendrickson
• Re: Best book to help transition from F77 to F90/95
  • From: Dan Nagle
• Re: Best book to help transition from F77 to F90/95
  • From: Gary Scott
• Re: GUI for fortran
  • From: Gary Scott
• Re: Best book to help transition from F77 to F90/95
  • From: beliavsky
• Re: Read JPEG Open Source Module??
  • From: David Frank
• Re: Where is kernel32.mod
  • From: Jugoslav Dujic
• Where is kernel32.mod
  • From: Behrang
• Re: GUI for fortran
  • From: Catherine Rees Lay
• Re: Best book to help transition from F77 to F90/95
  • From: Richard Maine
• Best book to help transition from F77 to F90/95
  • From: jurgarden2001
• Re: usually forgot to "use" some modules
  • From: Joost
• Re: usually forgot to "use" some modules
  • From: highegg
• Re: Pointers to functions: Is this the right [f03] syntax?
  • From: James Giles
• Re: problem of block data contained in module
  • From: Mike
• usually forgot to "use" some modules
  • From: Mike
• Re: Pointers to functions: Is this the right [f03] syntax?
  • From: glen herrmannsfeldt
• Re: problem of block data contained in module
  • From: Richard Maine
• Re: problem of block data contained in module
  • From: robert . corbett
• Re: problem of block data contained in module
  • From: Richard Maine
• Re: problem of block data contained in module
  • From: Mike
• Re: heap allocation of arrays
  • From: Norman Yarvin
• Re: Read JPEG Open Source Module??
  • From: R. Vowels
• Re: Pointers to functions: Is this the right [f03] syntax?
  • From: John Harper
• Re: Pointers to functions: Is this the right [f03] syntax?
  • From: Richard E Maine
• Re: Pointers to functions: Is this the right [f03] syntax?
  • From: James Giles
• Re: Pointers to functions: Is this the right [f03] syntax?
  • From: James Giles
• Re: Pointers to functions: Is this the right [f03] syntax?
  • From: Richard E Maine
• Re: Pointers to functions: Is this the right [f03] syntax?
  • From: glen herrmannsfeldt
• Re: Pointers to functions: Is this the right [f03] syntax?
  • From: Dick Hendrickson
• Re: Pointers to functions: Is this the right [f03] syntax?
  • From: glen herrmannsfeldt
• Re: Pointers to functions: Is this the right [f03] syntax?
  • From: James Giles
• Re: Pointers to functions: Is this the right [f03] syntax?
  • From: Dick Hendrickson
• Re: Pointers to functions: Is this the right [f03] syntax?
  • From: James Giles
• Re: Read JPEG Open Source Module??
  • From: Brooks Moses
• Re: is there a utility putenv() in fortran or perl?
  • From: glen herrmannsfeldt
• Re: problem of block data contained in module
  • From: Richard E Maine
• Re: is there a utility putenv() in fortran or perl?
  • From: Ron Shepard
• Re: is there a utility putenv() in fortran or perl?
  • From: Richard E Maine
• Re: problem of block data contained in module
  • From: Ron Shepard
• Re: Pointers to functions: Is this the right [f03] syntax?
  • From: Richard E Maine
• Re: Save an array to memory for another program to read it
  • From: gary . l . scott
• Re: Save an array to memory for another program to read it
  • From: dpb
• Re: is there a utility putenv() in fortran or perl?
  • From: Tim Prince
• Re: GUI for fortran
  • From: PJH
• Re: Calling Fortran from C
  • From: Jan Vorbrüggen
• Re: Calling Fortran from C
  • From: hicham
• Re: Pointers to functions: Is this the right [f03] syntax?
  • From: Dan Nagle
• Re: Calling Fortran from C
  • From: Arjen Markus
• Re: Calling Fortran from C
  • From: Arjen Markus
• Re: Calling Fortran from C
  • From: ghriss . hicham
• Re: Calling Fortran from C
  • From: Jan Vorbrüggen
• Calling Fortran from C
  • From: ghriss . hicham
• Re: Read JPEG Open Source Module??
  • From: Richard Maine
• Re: Pointers to functions: Is this the right [f03] syntax?
  • From: Richard Maine
• Re: help for reading a binary file
  • From: phywho
• Re: Read JPEG Open Source Module??
  • From: Brooks Moses
• Re: Pointers to functions: Is this the right [f03] syntax?
  • From: glen herrmannsfeldt
• Read JPEG Open Source Module??
  • From: daelomin@xxxxxxxxx
• Re: heap allocation of arrays
  • From: Jan Vorbrüggen
• Re: heap allocation of arrays
  • From: robert . corbett
• Re: Pointers to functions: Is this the right [f03] syntax?
  • From: Andy
• Re: Preprocessor for gfortran
  • From: Tim Prince
• Re: Pointers to functions: Is this the right [f03] syntax?
  • From: Richard Maine
• Re: Pointers to functions: Is this the right [f03] syntax?
  • From: Andy
• Re: help for reading a binary file
  • From: e p chandler
• Re: help for reading a binary file
  • From: robin
• Re: GUI for fortran
  • From: robin
• Re: help for reading a binary file
  • From: e p chandler
• Re: Save an array to memory for another program to read it
  • From: Gary Scott
• Re: Save an array to memory for another program to read it
  • From: dpb
• Re: Save an array to memory for another program to read it
  • From: Gary Scott
• Re: Save an array to memory for another program to read it
  • From: e p chandler
• Re: Save an array to memory for another program to read it
  • From: gary . l . scott
• Re: help for reading a binary file
  • From: Clive Page
• Re: heap allocation of arrays
  • From: Norman Yarvin
• Re: Save an array to memory for another program to read it
  • From: dpb
• Re: problem of block data contained in module
  • From: Richard E Maine
• Re: problem of block data contained in module
  • From: Dan Nagle
• Re: Save an array to memory for another program to read it
  • From: gary . l . scott
• Re: problem of block data contained in module
  • From: Richard E Maine
• Re: Save an array to memory for another program to read it
  • From: Richard E Maine
• Re: problem of block data contained in module
  • From: Richard E Maine
• Re: problem of block data contained in module
  • From: Dan Nagle
• Re: Pointers to functions: Is this the right [f03] syntax?
  • From: Richard E Maine
• problem of block data contained in module
  • From: Mike
• Re: help for reading a binary file
  • From: oph
• Re: Save an array to memory for another program to read it
  • From: pdafniotis
• Re: Save an array to memory for another program to read it
  • From: Gordon Sande
• Re: maximum 1D array size
  • From: Jan Vorbrüggen
• maximum 1D array size
  • From: jgphpc
• Re: Algorithm help for unique string searching/counting within an array.
  • From: Herman D . Knoble
• Re: Save an array to memory for another program to read it
  • From: Catherine Rees Lay
• Re: GUI for fortran
  • From: Catherine Rees Lay
• Re: Pointers to functions: Is this the right [f03] syntax?
  • From: Reinhold Bader
• Re: help for reading a binary file
  • From: glen herrmannsfeldt
• Re: help for reading a binary file
  • From: phywho
• Re: Pointers to functions: Is this the right [f03] syntax?
  • From: Andy
• Re: Algorithm help for unique string searching/counting within an array.
  • From: Arjen Markus
• Re: Algorithm help for unique string searching/counting within an array.
  • From: Arjen Markus
• Re: Pointers to functions: Is this the right [f03] syntax?
  • From: highegg
• Re: TRIM
  • From: Sjouke Burry
• Re: fold the details of program in CVF
  • From: jussij
• Re: function with allocatable type? (IVF 9.1)
  • From: Jamming
• Re: TRIM
  • From: James Giles
• Re: TRIM
  • From: robin
• Re: Algorithm help for unique string searching/counting within an array.
  • From: robin
• Re: GUI for fortran
  • From: robin
• Re: help for reading a binary file
  • From: robin
• Re: Save an array to memory for another program to read it
  • From: Dan Nagle
• Re: Save an array to memory for another program to read it
  • From: Dan Nagle
• Save an array to memory for another program to read it
  • From: Nektarios - Greece
• Re: Windows/Dos memory -- when is Allocate/Deallocate necessary
  • From: Brooks Moses
• Re: Pointers to functions: Is this the right [f03] syntax?
  • From: glen herrmannsfeldt
• Re: heap allocation of arrays
  • From: glen herrmannsfeldt
• Re: help for reading a binary file
  • From: Clive Page
• Re: Pointers to functions: Is this the right [f03] syntax?
  • From: Pere
• Re: Pointers to functions: Is this the right [f03] syntax?
  • From: Richard E Maine
• Re: heap allocation of arrays
  • From: Richard E Maine
• Re: heap allocation of arrays
  • From: robert . corbett
• Re: TRIM
  • From: James Giles
• Re: Pointers to functions: Is this the right [f03] syntax?
  • From: Joost
• Re: Pointers to functions: Is this the right [f03] syntax?
  • From: Richard E Maine
• Re: Algorithm help for unique string searching/counting within an array.
  • From: Richard E Maine
• Pointers to functions: Is this the right [f03] syntax?
  • From: Pere
• Re: GUI for fortran
  • From: gary . l . scott
• Re: Algorithm help for unique string searching/counting within an array.
  • From: Herman D . Knoble
• Re: Algorithm help for unique string searching/counting within an array.
  • From: Dan Nagle
• Re: GUI for fortran
  • From: Steven G. Kargl
• Re: GUI for fortran
  • From: gary . l . scott
• Re: Algorithm help for unique string searching/counting within an array.
  • From: Richard E Maine
• Re: heap allocation of arrays
  • From: Richard E Maine
• Re: TRIM
  • From: Dan Nagle
• Re: Algorithm help for unique string searching/counting within an array.
  • From: Herman D . Knoble
• Re: Algorithm help for unique string searching/counting within an array.
  • From: Dan Nagle
• Re: Algorithm help for unique string searching/counting within an array.
  • From: Herman D . Knoble
• Re: Algorithm help for unique string searching/counting within an array.
  • From: Arjen Markus
• Re: help for reading a binary file
  • From: Arjen Markus
• Re: Algorithm help for unique string searching/counting within an array.
  • From: Herman D . Knoble
• Re: TRIM
  • From: robin
• help for reading a binary file
  • From: phywho
• Re: GUI for fortran
  • From: e p chandler
• Re: GUI for fortran
  • From: Warner BRUNS
• Re: Algorithm help for unique string searching/counting within an array.
  • From: Arjen Markus
• Re: GUI for fortran
  • From: Gary Scott
• Re: GUI for fortran
  • From: acp693
• Re: GUI for fortran
  • From: acp693
• Re: function with allocatable type? (IVF 9.1)
  • From: Jugoslav Dujic
• Re: GUI for fortran
  • From: fj
• Re: opening files and code cleanup
  • From: highegg
• Re: Windows/Dos memory -- when is Allocate/Deallocate necessary
  • From: john
• Re: opening files and code cleanup
  • From: Walter Spector
• Re: function with allocatable type? (IVF 9.1)
  • From: Jan Vorbrüggen
• Re: opening files and code cleanup
  • From: Arjen Markus
• Re: GUI for fortran
  • From: Arjen Markus
• Re: opening files and code cleanup
  • From: highegg
• GUI for fortran
  • From: siamak faridani
• Re: opening files and code cleanup
  • From: Walter Spector
• function with allocatable type? (IVF 9.1)
  • From: Jamming
• Re: heap allocation of arrays
  • From: glen herrmannsfeldt
• Re: heap allocation of arrays
  • From: David Frank
• Re: Windows/Dos memory -- when is Allocate/Deallocate necessary
  • From: Dan Nagle
• Re: Windows/Dos memory -- when is Allocate/Deallocate necessary
  • From: Brooks Moses
• Re: Windows/Dos memory -- when is Allocate/Deallocate necessary
  • From: Dan Nagle
• Re: Windows/Dos memory -- when is Allocate/Deallocate necessary
  • From: Brooks Moses
• Re: heap allocation of arrays
  • From: glen herrmannsfeldt
• Re: heap allocation of arrays
  • From: glen herrmannsfeldt
• Re: Preprocessor for gfortran
  • From: Brooks Moses
• Windows/Dos memory -- when is Allocate/Deallocate necessary
  • From: john
• Re: TRIM
  • From: James Giles
• Re: Preprocessor for gfortran
  • From: Steven G. Kargl
• Re: TRIM
  • From: David Frank
• Re: TRIM
  • From: Gareth Owen
• Re: TRIM
  • From: gary . l . scott
• Re: TRIM
  • From: rjkematick
• Re: Preprocessor for gfortran
  • From: Gareth Owen
• Re: Preprocessor for gfortran
  • From: jellby
• Re: Array of subroutines
  • From: John Keenan
• Re: TRIM
  • From: Gareth Owen
• Re: heap allocation of arrays
  • From: Ron Shepard
• Re: TRIM
  • From: robin
• Re: compile problem:subroutines in module procedure (CVF6.6)
  • From: dpb
• Re: Preprocessor for gfortran
  • From: Gareth Owen
• Re: Preprocessor for gfortran
  • From: jellby
• Re: Preprocessor for gfortran
  • From: Dan Nagle
• Calling Matlab functions on s Linux cluster
  • From: Hakan Lane
• Preprocessor for gfortran
  • From: jellby
• Re: compile problem:subroutines in module procedure (CVF6.6)
  • From: Mike
• Re: Calling Matlab functions on s Linux cluster
  • From: highegg
• Re: compile problem:subroutines in module procedure (CVF6.6)
  • From: Mike
• Re: heap allocation of arrays
  • From: Richard E Maine
• Re: heap allocation of arrays
  • From: highegg
• Re: compile problem:subroutines in module procedure (CVF6.6)
  • From: Richard E Maine
• Re: Array of subroutines
  • From: beliavsky
• Re: heap allocation of arrays
  • From: Jugoslav Dujic
• Re: using the same function for stdout and files
  • From: beliavsky
• Re: heap allocation of arrays
  • From: Jan Vorbrüggen
• Re: Performance of allocatable components implementation
  • From: Jan Vorbrüggen
• Re: heap allocation of arrays
  • From: David Frank
• Re: heap allocation of arrays
  • From: glen herrmannsfeldt
• Re: opening files and code cleanup
  • From: Jan Vorbrüggen
• Re: how to track and handle the floating point exception ?
  • From: R. MacDonald
• Re: using the same function for stdout and files
  • From: jwm
• Re: compile problem:subroutines in module procedure (CVF6.6)
  • From: jwm
• Re: compile problem:subroutines in module procedure (CVF6.6)
  • From: Jugoslav Dujic
• Re: Array of subroutines
  • From: Jugoslav Dujic
• f2003 allocatable extension
  • From: manish
• heap allocation of arrays
  • From: robert . corbett
• Re: using the same function for stdout and files
  • From: Arjen Markus
• Re: TRIM
  • From: David Frank
• Re: using the same function for stdout and files
  • From: Nasser Abbasi
• Re: compile problem:subroutines in module procedure (CVF6.6)
  • From: Mike
• using the same function for stdout and files
  • From: Kamaraju Kusumanchi
• Re: Direct access and derived types.
  • From: Dave Thompson
• Re: List-directed input with no <CR> on last record
  • From: Dave Thompson
• Re: TRIM
  • From: John Doe
• Re: TRIM
  • From: robin
• Re: Array of subroutines
  • From: Michael Metcalf
• Re: Array of subroutines
  • From: Brooks Moses
• Array of subroutines
  • From: John Keenan
• Re: automatic variables are not initialized correctly?
  • From: Ugo
• Re: TRIM
  • From: David Frank
• Re: automatic variables are not initialized correctly?
  • From: glen herrmannsfeldt
• Re: Question: Fotran FFT package
  • From: glen herrmannsfeldt
• Re: automatic variables are not initialized correctly?
  • From: glen herrmannsfeldt
• Re: automatic variables are not initialized correctly?
  • From: glen herrmannsfeldt
• Re: automatic variables are not initialized correctly?
  • From: glen herrmannsfeldt
• Re: automatic variables are not initialized correctly?
  • From: glen herrmannsfeldt
• Re: opening files and code cleanup
  • From: glen herrmannsfeldt
• Re: What Algorithims are used for IEEE Mathematical and Inquiry Intrinsic Procedures
  • From: Mike
• Re: automatic variables are not initialized correctly?
  • From: Richard E Maine
• Re: automatic variables are not initialized correctly?
  • From: Dan Nagle
• Re: automatic variables are not initialized correctly?
  • From: James Giles
• Re: automatic variables are not initialized correctly?
  • From: kia
• Re: automatic variables are not initialized correctly?
  • From: kia
• Re: automatic variables are not initialized correctly?
  • From: Nasser Abbasi
• Re: automatic variables are not initialized correctly?
  • From: Gary Scott
• Re: opening files and code cleanup
  • From: Dan Nagle
• Re: automatic variables are not initialized correctly?
  • From: Ron Shepard
• Re: opening files and code cleanup
  • From: highegg
• Re: opening files and code cleanup
  • From: James Giles
• Re: opening files and code cleanup
  • From: Dan Nagle
• re: TRIM
  • From: robin
• re: TRIM
  • From: robin
• Re: No enumeration data type in Fortran?
  • From: glen herrmannsfeldt
• Re: opening files and code cleanup
  • From: Walter Spector
• Re: opening files and code cleanup
  • From: Walter Spector
• Re: compile problem:subroutines in module procedure (CVF6.6)
  • From: jwm
• Re: No enumeration data type in Fortran?
  • From: Gary Scott
• Re: automatic variables are not initialized correctly?
  • From: Gary Scott
• compile problem:subroutines in module procedure (CVF6.6)
  • From: Mike
• Re: No enumeration data type in Fortran?
  • From: Dan Nagle
• Re: Floating Point: Binary Shift Subroutine
  • From: robin
• Re: Size of Integer in Fortran 77
  • From: Richard E Maine
• Re: automatic variables are not initialized correctly?
  • From: Richard E Maine
• Re: No enumeration data type in Fortran?
  • From: James Giles
• Re: opening files and code cleanup
  • From: Richard E Maine
• Re: No enumeration data type in Fortran?
  • From: Richard E Maine
• Re: No enumeration data type in Fortran?
  • From: James Giles
• Re: automatic variables are not initialized correctly?
  • From: James Giles
• Re: No enumeration data type in Fortran?
  • From: Dan Nagle
• Re: automatic variables are not initialized correctly?
  • From: Nasser Abbasi
• Re: No enumeration data type in Fortran?
  • From: gary . l . scott
• Re: Convert Char String to ASCII-96 Symbol
  • From: e p chandler
• Re: automatic variables are not initialized correctly?
  • From: gary . l . scott
• Re: automatic variables are not initialized correctly?
  • From: James Giles
• Re: automatic variables are not initialized correctly?
  • From: Dan Nagle
• Re: Quickly show the purposes of all programs in a directory
  • From: Brooks Moses
• Re: automatic variables are not initialized correctly?
  • From: Nasser Abbasi
• Re: automatic variables are not initialized correctly?
  • From: Tobias
• Re: automatic variables are not initialized correctly?
  • From: Steven G. Kargl
• Re: automatic variables are not initialized correctly?
  • From: Dan Nagle
• automatic variables are not initialized correctly?
  • From: Nasser Abbasi
• Re: No enumeration data type in Fortran?
  • From: James Giles
• Re: opening files and code cleanup
  • From: James Giles
• Re: Converting fixed-to-free format
  • From: Dick Hendrickson
• Re: No enumeration data type in Fortran?
  • From: David Frank
• how to track and handle the floating point exception ?
  • From: bei
• Re: opening files and code cleanup
  • From: Craig Powers
• Re: opening files and code cleanup
  • From: Dan Nagle
• Re: opening files and code cleanup
  • From: Walter Spector
• Re: opening files and code cleanup
  • From: Walter Spector
• Re: Question: Fotran FFT package
  • From: Gordon Sande
• Re: if module file as one of the source files, compile is wrong? (using CVF6.6)
  • From: jwm
• Re: opening files and code cleanup
  • From: Dick Hendrickson
• Re: opening files and code cleanup
  • From: Dan Nagle
• Re: opening files and code cleanup
  • From: Walter Spector
• Re: Question: Fotran FFT package
  • From: ben
• Re: "Insufficient virtual memory" error message in Linux
  • From: Lorents
• Re: What Algorithims are used for IEEE Mathematical and Inquiry Intrinsic Procedures
  • From: Herman D . Knoble
• Re: No enumeration data type in Fortran?
  • From: Dan Nagle
• Re: No enumeration data type in Fortran?
  • From: James Giles
• Re: What Algorithims are used for IEEE Mathematical and Inquiry Intrinsic Procedures
  • From: glen herrmannsfeldt
• Re: The power that is C++
  • From: glen herrmannsfeldt
• Re: No enumeration data type in Fortran?
  • From: robert . corbett
• Re: Floating Point: Binary Shift Subroutine
  • From: glen herrmannsfeldt
• Re: Performance of allocatable components implementation
  • From: glen herrmannsfeldt
• Re: pretty-print for Fortran 90/95 for windows?
  • From: Glenn Morris
• Re: opening files and code cleanup
  • From: Arjen Markus
• Re: No enumeration data type in Fortran?
  • From: Arjen Markus
• Re: if module file as one of the source files, compile is wrong? (using CVF6.6)
  • From: Jugoslav Dujic
• No enumeration data type in Fortran?
  • From: Nasser Abbasi
• Re: if module file as one of the source files, compile is wrong? (using CVF6.6)
  • From: Mike
• Re: The power that is C++
  • From: Dave Weatherall
• Re: if module file as one of the source files, compile is wrong? (using CVF6.6)
  • From: Mike
• Re: if module file as one of the source files, compile is wrong? (using CVF6.6)
  • From: jwm
• Re: The power that is C++
  • From: Brooks Moses
• if module file as one of the source files, compile is wrong? (using CVF6.6)
  • From: Mike
• Re: Converting fixed-to-free format
  • From: Dan Nagle
• Re: Converting fixed-to-free format
  • From: Dan Nagle
• Re: Converting fixed-to-free format
  • From: Dan Nagle
• Re: Size of Integer in Fortran 77
  • From: Brooks Moses
• Re: Converting fixed-to-free format
  • From: James Giles
• Re: Converting fixed-to-free format
  • From: robin
• Re: Converting fixed-to-free format
  • From: robin
• Re: Converting fixed-to-free format
  • From: robin
• Re: Converting fixed-to-free format
  • From: robin
• Re: Size of Integer in Fortran 77
  • From: John
• Re: Question: Fotran FFT package
  • From: stevenj
• Re: Size of Integer in Fortran 77
  • From: robin
• Re: opening files and code cleanup
  • From: Frank Silvermann
• Re: opening files and code cleanup
  • From: Richard E Maine
• Re: opening files and code cleanup
  • From: Frank Silvermann
• Re: The power that is C++
  • From: John Harper
• Re: Performance of allocatable components implementation
  • From: Richard E Maine
• Question: Fotran FFT package
  • From: ben
• Re: Performance of allocatable components implementation
  • From: glen herrmannsfeldt
• Re: Converting fixed-to-free format
  • From: gary . l . scott
• Re: The power that is C++
  • From: max
• Re: Converting fixed-to-free format
  • From: James Giles
• Re: Converting fixed-to-free format
  • From: Richard E Maine
• Re: Converting fixed-to-free format
  • From: Dan Nagle
• Re: Converting fixed-to-free format
  • From: Paul Van Delst
• Re: Files suggested to be included, and being opened even not in the same directory?
  • From: Craig Powers
• Re: Converting fixed-to-free format
  • From: gary . l . scott
• Re: opening files and code cleanup
  • From: Walter Spector
• Re: Floating Point: Binary Shift Subroutine
  • From: Ken Fairfield
• Re: Size of Integer in Fortran 77
  • From: James Giles
• Re: Floating Point: Binary Shift Subroutine
  • From: Ken Fairfield
• Re: Converting fixed-to-free format
  • From: Dan Nagle
• Re: opening files and code cleanup
  • From: Craig Powers
• Re: The power that is C++
  • From: gary . l . scott
• Re: Necessary to declare arguments of subroutines in module again?
  • From: Richard E Maine
• Re: pretty-print for Fortran 90/95 for windows?
  • From: Ian Chivers
• Re: The power that is C++
  • From: David Jones
• Re: Files suggested to be included, and being opened even not in the same directory?
  • From: Mike
• Re: Quotes(" or ') (was:The power that is C++)
  • From: Michael Metcalf
• Re: g77: 32-bit to 64-bit
  • From: Anatoliy V. Volkov
• Re: Floating Point: Binary Shift Subroutine
  • From: Grant
• SYMMLQ
  • From: Hakan Lane
• Re: Performance of allocatable components implementation
  • From: Thomas Koenig
• Re: automatic arrays with negative size in g95 and gfortran
  • From: Thomas Koenig
• Re: Size of Integer in Fortran 77
  • From: glen herrmannsfeldt
• Re: Necessary to declare arguments of subroutines in module again?
  • From: Jugoslav Dujic
• Re: Files suggested to be included, and being opened even not in the same directory?
  • From: Arjen Markus
• Necessary to declare arguments of subroutines in module again?
  • From: Mike
• Re: opening files and code cleanup
  • From: Arjen Markus
• Files suggested to be included, and being opened even not in the same directory?
  • From: Mike
• Re: pretty-print for Fortran 90/95 for windows?
  • From: Nasser Abbasi
• Re: Size of Integer in Fortran 77
  • From: robin
• Re: pretty-print for Fortran 90/95 for windows?
  • From: Dan Nagle
• Re: pretty-print for Fortran 90/95 for windows?
  • From: Nasser Abbasi
• Re: pretty-print for Fortran 90/95 for windows?
  • From: Nasser Abbasi
• Re: pretty-print for Fortran 90/95 for windows?
  • From: Bil Kleb
• Re: Performance of allocatable components implementation
  • From: Gordon Sande
• Re: pretty-print for Fortran 90/95 for windows?
  • From: Bil Kleb
• Re: Earthquake and Tornado Forecasting Programs June 13, 2006
  • From: Frank Silvermann
• Re: pretty-print for Fortran 90/95 for windows?
  • From: Steven G. Kargl
• Re: pretty-print for Fortran 90/95 for windows?
  • From: Dan Nagle
• Re: Floating Point: Binary Shift Subroutine
  • From: glen herrmannsfeldt
• pretty-print for Fortran 90/95 for windows?
  • From: Nasser Abbasi
• Re: Floating Point: Binary Shift Subroutine
  • From: Richard E Maine
• Re: automatic arrays with negative size in g95 and gfortran
  • From: glen herrmannsfeldt
• Re: Performance of allocatable components implementation
  • From: glen herrmannsfeldt
• Re: Floating Point: Binary Shift Subroutine
  • From: glen herrmannsfeldt
• Re: [newbe]: help me debugging this script, please!
  • From: e p chandler
• Quotes(" or ') (was:The power that is C++)
  • From: James Giles
• Re: [newbe]: help me debugging this script, please!
  • From: Brooks Moses
• Re: [newbe]: help me debugging this script, please!
  • From: Richard E Maine
• Re: [newbe]: help me debugging this script, please!
  • From: stefjnoskynov
• Re: [newbe]: help me debugging this script, please!
  • From: Richard E Maine
• Re: opening files and code cleanup
  • From: Walter Spector
• Re: [newbe]: help me debugging this script, please!
  • From: David Flower
• [newbe]: help me debugging this script, please!
  • From: stefjnoskynov
• Re: Converting fixed-to-free format
  • From: Dick Hendrickson
• Re: opening files and code cleanup
  • From: Richard E Maine
• Re: opening files and code cleanup
  • From: highegg
• Re: Size of Integer in Fortran 77
  • From: David Flower
• Computing power of non-native code
  • From: Joe Krahn
• Re: catch RaiseException with VB.Net
  • From: dpb
• Re: opening files and code cleanup
  • From: Richard E Maine
• Re: g77: 32-bit to 64-bit
  • From: Richard E Maine
• Re: Size of Integer in Fortran 77
  • From: robin
• Re: Floating Point: Binary Shift Subroutine
  • From: robin
• Re: Converting fixed-to-free format
  • From: robin
• Re: opening files and code cleanup
  • From: Ron Shepard
• Re: g77: 32-bit to 64-bit
  • From: Tim Prince
• Re: opening files and code cleanup
  • From: beliavsky
• Re: g77: 32-bit to 64-bit
  • From: rjkematick
• Re: opening files and code cleanup
  • From: beliavsky
• Re: opening files and code cleanup
  • From: Bart Vandewoestyne
• Re: The power that is C++
  • From: Craig Powers
• Re: g77: 32-bit to 64-bit
  • From: rjkematick
• Re: opening files and code cleanup
  • From: highegg
• Re: opening files and code cleanup
  • From: Walter Spector
• Re: opening files and code cleanup
  • From: highegg
• Re: opening files and code cleanup
  • From: Arjen Markus
• Re: opening files and code cleanup
  • From: Jan Vorbrüggen
• Compiler Test Results Updated
  • From: Herman D . Knoble
• Re: opening files and code cleanup
  • From: Bart Vandewoestyne
• RE: [newbe]: help me debugging this script, please!
  • From: meek
• Re: opening files and code cleanup
  • From: Arjen Markus
• Re: catch RaiseException with VB.Net
  • From: jmdelfa@xxxxxxxxx
• Re: Floating Point: Binary Shift Subroutine
  • From: e p chandler
• opening files and code cleanup
  • From: Bart Vandewoestyne
• Re: catch RaiseException with VB.Net
  • From: jmdelfa@xxxxxxxxx
• Re: catch RaiseException with VB.Net
  • From: R. MacDonald
• Re: Floating Point: Binary Shift Subroutine
  • From: Jugoslav Dujic
• Re: Performance of allocatable components implementation
  • From: Jan Vorbrüggen
• Re: catch RaiseException with VB.Net
  • From: Brooks Moses
• Re: how to create a Snapshot of subroutines or functions used in a project
  • From: jussij
• Re: catch RaiseException with VB.Net
  • From: jmdelfa@xxxxxxxxx
• Re: Floating Point: Binary Shift Subroutine
  • From: Dave Weatherall
• Re: The power that is C++
  • From: Dave Weatherall
• Re: Floating Point: Binary Shift Subroutine
  • From: Jim
• Re: Floating Point: Binary Shift Subroutine
  • From: e p chandler
• Re: catch RaiseException with VB.Net
  • From: pacman
• Re: Inserting data in linked lists
  • From: robin
• Re: The power that is C++
  • From: John Harper
• Re: "Insufficient virtual memory" error message in Linux
  • From: Jim
• Re: Floating Point: Binary Shift Subroutine
  • From: glen herrmannsfeldt
• Re: Size of Integer in Fortran 77
  • From: robert . corbett
• Re: Floating Point: Binary Shift Subroutine
  • From: Richard E Maine
• Re: Performance of allocatable components implementation
  • From: Bernhard Enders
• Re: Size of Integer in Fortran 77
  • From: gary . l . scott
• Re: Size of Integer in Fortran 77
  • From: e p chandler
• Re: Floating Point: Binary Shift Subroutine
  • From: Grant
• Re: Floating Point: Binary Shift Subroutine
  • From: e p chandler
• Re: Performance of allocatable components implementation
  • From: Gordon Sande
• Re: Character to Real*8
  • From: Dan Nagle
• Re: Character to Real*8
  • From: Richard E Maine
• Re: Character to Real*8
  • From: Richard E Maine
• Re: Character to Real*8
  • From: Dan Nagle
• Re: The power that is C++
  • From: Walter Spector
• Character to Real*8
  • From: rjmagyar
• Re: Size of Integer in Fortran 77
  • From: Richard E Maine
• Re: Floating Point: Binary Shift Subroutine
  • From: Grant
• Re: Size of Integer in Fortran 77
  • From: David Flower
• Performance of allocatable components implementation
  • From: Bernhard Enders
• Re: Floating Point: Binary Shift Subroutine
  • From: Richard E Maine
• Re: Floating Point: Binary Shift Subroutine
  • From: e p chandler
• Re: Size of Integer in Fortran 77
  • From: Michael Metcalf
• Size of Integer in Fortran 77
  • From: Michael McGarry
• Re: Stackdump issues
  • From: Richard E Maine
• Re: Floating Point: Binary Shift Subroutine
  • From: Grant
• Re: Floating Point: Binary Shift Subroutine
  • From: Michael Metcalf
• Re: automatic arrays with negative size in g95 and gfortran
  • From: Richard E Maine
• Re: catch RaiseException with VB.Net
  • From: dpb
• Re: Converting fixed-to-free format
  • From: Rich Townsend
• Re: The power that is C++
  • From: beliavsky
• Floating Point: Binary Shift Subroutine
  • From: Grant
• Re: The power that is C++
  • From: James Giles
• Re: The power that is C++
  • From: gary . l . scott
• Re: The power that is C++
  • From: Walt Brainerd
• Re: Converting fixed-to-free format
  • From: Dan Nagle
• Re: Stackdump issues
  • From: Bijan Minaee
• Re: Converting fixed-to-free format
  • From: robin
• Re: Converting fixed-to-free format
  • From: robin
• Re: Simple formatting question
  • From: Dick Russell
• Re: Simple formatting question
  • From: Dick Russell
• Re: Simple formatting question
  • From: Jan Vorbrüggen
• Simple formatting question
  • From: tco99
• Re: "Insufficient virtual memory" error message in Linux
  • From: glen herrmannsfeldt
• Re: g77: 32-bit to 64-bit
  • From: glen herrmannsfeldt
• Re: automatic arrays with negative size in g95 and gfortran
  • From: glen herrmannsfeldt
• catch RaiseException with VB.Net
  • From: jmdelfa@xxxxxxxxx
• Re: g77: 32-bit to 64-bit
  • From: Jan Vorbrüggen
• Re: automatic arrays with negative size in g95 and gfortran
  • From: robert . corbett
• Re: g77: 32-bit to 64-bit
  • From: Anatoliy V. Volkov
• Re: g77: 32-bit to 64-bit
  • From: Robert Kematick
• Re: "Insufficient virtual memory" error message in Linux
  • From: Tim Prince
• "Insufficient virtual memory" error message in Linux
  • From: Lorents
• Re: The power that is C++
  • From: glen herrmannsfeldt
• Re: g77: 32-bit to 64-bit
  • From: glen herrmannsfeldt
• Re: The power that is C++
  • From: max
• Re: The power that is C++
  • From: John Harper
• g77: 32-bit to 64-bit
  • From: Anatoliy V. Volkov
• Re: Convert Char String to ASCII-96 Symbol
  • From: e p chandler
• Re: Convert Char String to ASCII-96 Symbol
  • From: Richard E Maine
• Re: Convert Char String to ASCII-96 Symbol
  • From: Grant
• Re: Convert Char String to ASCII-96 Symbol
  • From: e p chandler
• Re: Convert Char String to ASCII-96 Symbol
  • From: glen herrmannsfeldt
• Re: [g95] DECIMAL='comma' do not work !?
  • From: Andy
• Re: Convert Char String to ASCII-96 Symbol
  • From: Grant
• Re: Convert Char String to ASCII-96 Symbol
  • From: Richard E Maine
• Re: Convert Char String to ASCII-96 Symbol
  • From: David Flower
• Re: Stackdump issues
  • From: Richard E Maine
• Convert Char String to ASCII-96 Symbol
  • From: Grant
• Re: Stackdump issues
  • From: Jim
• Re: I'm still confused about pointers
  • From: Ron Shepard
• Re: I'm still confused about pointers
  • From: David Flower
• Re: I'm still confused about pointers
  • From: Michael Metcalf
• Re: The power that is C++
  • From: highegg
• I'm still confused about pointers
  • From: David Flower
• RE: Convert Char String to ASCII-96 Symbol
  • From: meek
• Re: Stackdump issues
  • From: Tim Prince
• Re: Stackdump issues
  • From: Dan Nagle
• Re: The power that is C++
  • From: John Smith
• Re: help with cray ftn namelist
  • From: Ian Bush
• Re: Standard violation or Absoft bug?
  • From: Bil Kleb
• RE: Convert Char String to ASCII-96 Symbol
  • From: meek
• Re: Large-Scale Fortran Software Design
  • From: Bil Kleb
• Re: Standard violation or Absoft bug?
  • From: Jan Vorbrüggen
• Re: Stackdump issues
  • From: Bijan Minaee
• Re: The power that is C++
  • From: glen herrmannsfeldt
• The power that is C++
  • From: max
• Re: [g95] DECIMAL='comma' do not work !?
  • From: Hani Andreas Ibrahim
• Re: Large-Scale Fortran Software Design
  • From: Arjen Markus
• Re: [g95] DECIMAL='comma' do not work !?
  • From: John Harper
• Re: [g95] DECIMAL='comma' do not work !?
  • From: Walt Brainerd
• Re: [g95] DECIMAL='comma' do not work !?
  • From: Michael Metcalf
• Re: PGI Visual Fortran Preview Edition available
  • From: Gary Scott
• PGI Visual Fortran Preview Edition available
  • From: beliavsky
• [g95] DECIMAL='comma' do not work !?
  • From: Hani Andreas Ibrahim
• Re: Stackdump issues
  • From: Richard Maine
• Re: Stackdump issues
  • From: Dan Nagle
• Stackdump issues
  • From: Bijan Minaee
• Re: allocatrouble arrays
  • From: Brooks Moses
• Re: help with cray ftn namelist
  • From: glen herrmannsfeldt
• Re: help with cray ftn namelist
  • From: Dan Nagle
• Re: help with cray ftn namelist
  • From: Steve Lionel
• Re: gfortran matmul
  • From: Ian Gay
• help with cray ftn namelist
  • From: Joe Hill
• Re: General advice on C++ F77 multi-language compiling and linking
  • From: deltaseq0
• Re: allocatrouble arrays
  • From: highegg
• gfortran matmul
  • From: Egil Holvik
• Re: changing a bit of a real
  • From: Walter Spector
• Re: how to write a program to solve the linear equation with inequality?
  • From: glen herrmannsfeldt
• Re: Question about elemental functions
  • From: Greg Lindahl
• Re: Intel OS X Fortran Extension
  • From: Jim S
• Re: Intel OS X Fortran Extension
  • From: Steve Lionel
• Re: Intel OS X Fortran Extension
  • From: Richard Maine
• how to write a program to solve the linear equation with inequality?
  • From: PCAT
• Intel OS X Fortran Extension
  • From: Jim S
• Re: Question about elemental functions
  • From: pacman
• Re: automatic arrays with negative size in g95 and gfortran
  • From: glen herrmannsfeldt
• Re: Question about elemental functions
  • From: Norman Clerman
• Re: allocatrouble arrays
  • From: glen herrmannsfeldt
• Re: Question about elemental functions
  • From: Michael Metcalf
• Re: allocatrouble arrays
  • From: highegg
• Question about elemental functions
  • From: pacman
• Re: allocatrouble arrays
  • From: Joost
• Re: Standard violation or Absoft bug?
  • From: Richard Maine
• Re: gfortran and ifort, compatible binary files??
  • From: Richard Maine
• allocatrouble arrays
  • From: highegg
• Re: gfortran and ifort, compatible binary files??
  • From: Thomas Koenig
• Standard violation or Absoft bug?
  • From: Bil Kleb
• Re: mixed c++ fortran code link error
  • From: Tim Prince
• Re: General advice on C++ F77 multi-language compiling and linking
  • From: Tim Prince
• Large-Scale Fortran Software Design
  • From: Bil Kleb
• mixed c++ fortran code link error
  • From: zhiguoqian
• Re: how to know which .o file has the definition of a function/subroutine
  • From: yuanliu1
• Re: General advice on C++ F77 multi-language compiling and linking
  • From: deltaseq0
• Re: automatic arrays with negative size in g95 and gfortran
  • From: Richard Maine
• General advice on C++ F77 multi-language compiling and linking
  • From: deltaseq0
• Re: Quickly show the purposes of all programs in a directory
  • From: Paul Van Delst
• Re: I'm new to pointers...
  • From: Dan Nagle
• gfortran and ifort, compatible binary files??
  • From: Niels L Ellegaard
• Re: automatic arrays with negative size in g95 and gfortran
  • From: Jugoslav Dujic
• Re: I'm new to pointers...
  • From: Joost
• Re: I'm new to pointers...
  • From: Dan Nagle
• I'm new to pointers...
  • From: David Flower
• Re: automatic arrays with negative size in g95 and gfortran
  • From: Mark Westwood
• Re: gfortran & openmp on windows
  • From: FX
• Re: gfortran & openmp on windows
  • From: J. Luo
• Re: Quickly show the purposes of all programs in a directory
  • From: Brooks Moses
• Re: fortran compiler for Windows CE
  • From: Lynn McGuire
• Re: fortran compiler for Windows CE
  • From: bcaller
• Re: automatic arrays with negative size in g95 and gfortran
  • From: Steven G. Kargl
• Re: automatic arrays with negative size in g95 and gfortran
  • From: Richard E Maine
• Re: Quickly show the purposes of all programs in a directory
  • From: Paul Van Delst
• Re: automatic arrays with negative size in g95 and gfortran
  • From: Steven G. Kargl
• Re: Quickly show the purposes of all programs in a directory
  • From: Craig Powers
• Re: automatic arrays with negative size in g95 and gfortran
  • From: Thomas Koenig
• fortran compiler for Windows CE
  • From: Lynn McGuire
• Re: automatic arrays with negative size in g95 and gfortran
  • From: Richard E Maine
• Re: Quickly show the purposes of all programs in a directory
  • From: Paul Van Delst
• automatic arrays with negative size in g95 and gfortran
  • From: beliavsky
• gfortran & openmp on windows
  • From: J. Luo
• Re: Quickly show the purposes of all programs in a directory
  • From: Bil Kleb
• Re: gfortran message
  • From: Steven G. Kargl
• Re: Quickly show the purposes of all programs in a directory
  • From: Craig Powers
• Re: gfortran message
  • From: Bart Vandewoestyne
• Re: gfortran message
  • From: Steven G. Kargl
• Re: gfortran message
  • From: Bart Vandewoestyne
• Re: Quickly show the purposes of all programs in a directory
  • From: Paul Van Delst
• Re: dll trouble - final status
  • From: Kevin G. Rhoads
• Re: how to know which .o file has the definition of a function/subroutine
  • From: Richard E Maine
• Re: Quickly show the purposes of all programs in a directory
  • From: Richard Edgar
• how to know which .o file has the definition of a function/subroutine
  • From: yuanliu1
• Re: Quickly show the purposes of all programs in a directory
  • From: Richard E Maine
• Re: Quickly show the purposes of all programs in a directory
  • From: Paul Van Delst
• Re: Asynchronous parallel computing
  • From: gary . l . scott
• Re: NAGWare f95 licencing issues...
  • From: Bart Vandewoestyne
• Re: F2C converter
  • From: Lynn McGuire
• Re: NAGWare f95 licencing issues...
  • From: Richard E Maine
• Re: gfortran message
  • From: Richard E Maine
• Re: gfortran message
  • From: Craig Powers
• Re: Asynchronous parallel computing
  • From: blmblm
• Re: gfortran message
  • From: Bart Vandewoestyne
• Re: Asynchronous parallel computing
  • From: blmblm
• Re: Asynchronous parallel computing
  • From: Ron Shepard
• Re: gfortran message
  • From: Tim Prince
• Re: gfortran message
  • From: FX
• Re: Version numbers
  • From: Craig Powers
• Re: dll trouble - final status
  • From: David Frank
• Re: gfortran message
  • From: Bart Vandewoestyne
• Re: dll trouble - final status
  • From: Jugoslav Dujic
• Re: gfortran message
  • From: Tim Prince
• Re: dll trouble - final status
  • From: Kresimir Trontl
• Re: F2C converter
  • From: Arjen Markus
• NAGWare f95 licencing issues...
  • From: Bart Vandewoestyne
• RE: how to know which .o file has the definition of a function/subroutine
  • From: meek
• Re: F2C converter
  • From: Jan Vorbrüggen
• Re: F2C converter
  • From: n o s p a m p l e a s e
• Re: fold the details of program in CVF
  • From: Ian Brown
• Re: Asynchronous parallel computing
  • From: Harold Stevens
• Re: Asynchronous parallel computing
  • From: Ian Bush
• Re: Quickly show the purposes of all programs in a directory
  • From: Catherine Rees Lay
• Re: F2C converter
  • From: Catherine Rees Lay
• Re: Asynchronous parallel computing
  • From: Bil Kleb
• gfortran message
  • From: Bart Vandewoestyne
• F2C converter
  • From: n o s p a m p l e a s e
• Re: Asynchronous parallel computing
  • From: R. P.
• Re: Asynchronous parallel computing
  • From: R. P.
• Re: Asynchronous parallel computing
  • From: Klaus Wacker
• Asynchronous parallel computing
  • From: R. P.
• Re: fold the details of program in CVF
  • From: Mike
• Re: Quickly show the purposes of all programs in a directory
  • From: Mike
• Re: Bounds Check Overhead
  • From: Dave Thompson
• Re: linking c and fortran with pathscale compilers?
  • From: Greg Lindahl
• Re: Version numbers
  • From: bcaller
• Re: Version numbers
  • From: e p chandler
• question with ddd with mixedlanguage,
  • From: yuanliu1
• Re: linking c and fortran with pathscale compilers?
  • From: Richard E Maine
• Version numbers
  • From: Cliff
• Re: Quickly show the purposes of all programs in a directory
  • From: bcaller
• Re: linking c and fortran with pathscale compilers?
  • From: Greg Lindahl
• Re: lahey/phar lap dos-extender help needed
  • From: David Merrill
• Re: linking c and fortran with pathscale compilers?
  • From: OldSchool
• linking c and fortran with pathscale compilers?
  • From: Dan Stromberg
• Re: List-directed input with no <CR> on last record
  • From: gary . l . scott
• Re: List-directed input with no <CR> on last record
  • From: glen herrmannsfeldt
• Re: Re:: IVF continues to delight
  • From: awgreynolds
• Re: dll trouble
  • From: glen herrmannsfeldt
• Re: List-directed input with no <CR> on last record
  • From: Kevin G. Rhoads
• Re: dll trouble
  • From: Kevin G. Rhoads
• Re: dll trouble
  • From: Kevin G. Rhoads
• Re:: IVF continues to delight
  • From: Steve Lionel
• Re: Quickly show the purposes of all programs in a directory
  • From: Bil Kleb
• Re: changing a bit of a real
  • From: e p chandler
• Re: WAS: IVF continues to disappoint (relatively)
  • From: awgreynolds
• Re: Direct access and derived types.
  • From: Paul Van Delst
• Re: changing a bit of a real
  • From: Bart Vandewoestyne
• Re: changing a bit of a real
  • From: e p chandler
• Re: dll trouble
  • From: Jugoslav Dujic
• Re: Quickly show the purposes of all programs in a directory
  • From: beliavsky
• Re: fold the details of program in CVF
  • From: beliavsky
• Re: dll trouble
  • From: Kresimir Trontl
• Re: Quickly show the purposes of all programs in a directory
  • From: Bil Kleb
• Re: changing a bit of a real
  • From: Bart Vandewoestyne
• Re: changing a bit of a real
  • From: Bart Vandewoestyne
• Re: Direct access and derived types.
  • From: Jan Vorbrüggen
• Re: Direct access and derived types.
  • From: Jan Vorbrüggen
• Re: dll trouble
  • From: Jan Vorbrüggen
• Re: Direct access and derived types.
  • From: Jugoslav Dujic
• Re: Derived types containing components of PRIVATE type
  • From: robert . corbett
• fold the details of program in CVF
  • From: Mike
• Re: lahey/phar lap dos-extender help needed
  • From: John Smith
• Quickly show the purposes of all programs in a directory
  • From: Mike
• Re: lahey/phar lap dos-extender help needed
  • From: dave-suehuizenga@xxxxxxxxxxx
• Re: lahey/phar lap dos-extender help needed
  • From: John Smith
• Derived types containing components of PRIVATE type
  • From: Rich Townsend
• lahey/phar lap dos-extender help needed
  • From: dave-suehuizenga@xxxxxxxxxxx
• WAS: IVF continues to disappoint (relatively)
  • From: awgreynolds
• Re: changing a bit of a real
  • From: glen herrmannsfeldt
• Re: Intel Fortan module symbol conflict
  • From: Joe Krahn
• Re: changing a bit of a real
  • From: Richard E Maine
• Re: changing a bit of a real
  • From: glen herrmannsfeldt
• Re: changing a bit of a real
  • From: glen herrmannsfeldt
• Re: Direct access and derived types.
  • From: glen herrmannsfeldt
• Re: Direct access and derived types.
  • From: glen herrmannsfeldt
• Re: changing a bit of a real
  • From: Brooks Moses
• Re: Direct access and derived types.
  • From: Paul Van Delst
• Re: changing a bit of a real
  • From: Richard E Maine
• Re: changing a bit of a real
  • From: Richard E Maine
• Re: changing a bit of a real
  • From: Klaus Wacker
• Re: changing a bit of a real
  • From: Dan Nagle
• changing a bit of a real
  • From: Bart Vandewoestyne
• Re: Direct access and derived types.
  • From: Richard E Maine
• Re: Direct access and derived types.
  • From: Joost
• Re: Direct access and derived types.
  • From: Richard E Maine
• Re: Ada vs Fortran for scientific applications
  • From: Dick Hendrickson
• Re: Beginer needing help
  • From: e p chandler
• Re: dll trouble
  • From: Jugoslav Dujic
• Direct access and derived types.
  • From: L. Johansen
• Re: dll trouble
  • From: Kresimir Trontl
• Re: dll trouble
  • From: David Frank
• dll trouble
  • From: Kresimir Trontl
• Re: Portability of the construction "character(len=len(name))" ...
  • From: Arjen Markus
• Re: List-directed input with no <CR> on last record
  • From: John Harper
• Re: List-directed input with no <CR> on last record
  • From: glen herrmannsfeldt
• Re: What happens when you change subject? Was: List-directed input
  • From: Craig Powers
• Re: Portability of the construction "character(len=len(name))" ...
  • From: Richard E Maine
• Re: List-directed input with no <CR> on last record
  • From: Richard E Maine
• Re: Portability of the construction "character(len=len(name))" ...
  • From: robert . corbett
• Re: List-directed input with no <CR> on last record
  • From: Dan Nagle
• Re: List-directed input with no <CR> on last record
  • From: glen herrmannsfeldt
• List-directed input with no <CR> on last record
  • From: john
• List-directed input with no <CR> on last record
  • From: john
• Re: What happens when you change subject? Was: List-directed input
  • From: Kevin G. Rhoads
• Re: What happens when you change subject? Was: List-directed input
  • From: john
• Re: What happens when you change subject? Was: List-directed input
  • From: Steven G. Kargl
• Re: What happens when you change subject? Was: List-directed input
  • From: john
• Re: What happens when you change subject? Was: List-directed input
  • From: john
• Re: List-directed input with no <CR> on last record
  • From: tholen
• Re: What happens when you change subject? Was: List-directed input
  • From: john
• Re: List-directed input, with no <CR> on last record
  • From: Richard E Maine
• Re: What happens when you change subject? Was: List-directed input
  • From: john
• Re: List-directed input with no <CR> on last record
  • From: glen herrmannsfeldt
• Re: List-directed input, with no <CR> on last record
  • From: john
• Announcement: (partial) F90 Interface to POSIX for gnu Fortran
  • From: Klaus Ramstöck
• List-directed input, with no <CR> on last record
  • From: john
• Inhomogeneous linked lists (was: something else)
  • From: Richard E Maine
• Re: List-directed input with no <CR> on last record
  • From: ben
• Re: List-directed input with no <CR> on last record
  • From: Richard E Maine
• Re: List-directed input with no <CR> on last record
  • From: Dan Nagle
• Re: List-directed input with no <CR> on last record
  • From: glen herrmannsfeldt
• Re: List-directed input with no <CR> on last record
  • From: Richard E Maine
• List-directed input with no <CR> on last record
  • From: john
• Re: Portability of the construction "character(len=len(name))" ...
  • From: Bernhard Enders
• Re: Portability of the construction "character(len=len(name))" ...
  • From: Richard E Maine
• Re: Is there something wrong with array b?
  • From: Richard E Maine
• Re: Inserting data in linked lists
  • From: Richard E Maine
• Re: Inserting data in linked lists
  • From: Jugoslav Dujic
• Re: gfortran handling of subscript triplets
  • From: FX
• Re: Inserting data in linked lists
  • From: deltaquattro
• Portability of the construction "character(len=len(name))" ...
  • From: Arjen Markus
• Re: Is there something wrong with array b？
  • From: Ian Bush
• Re: Is there something wrong with array b？
  • From: David Flower
• Re: gfortran handling of subscript triplets
  • From: FX
• Re: Is there something wrong with array b？
  • From: Jugoslav Dujic
• Is there something wrong with array b？
  • From: sunboy
• Re: gfortran handling of subscript triplets
  • From: Richard Maine
• gfortran handling of subscript triplets
  • From: beliavsky
• Re: Converting fixed-to-free format
  • From: jamesgiles@xxxxxxx
• Re: Thanks!
  • From: Dan Nagle
• Thanks!
  • From: HK
• Re: Converting fixed-to-free format
  • From: robin
• Re: What did I do wrong with "external" ??
  • From: kia
• Re: Intel Fortan module symbol conflict
  • From: Brooks Moses
• Re: Scrolling a dialog window
  • From: gary . l . scott
• Re: gfortran installation breaking other installations
  • From: Steven G. Kargl
• Re: gfortran installation breaking other installations
  • From: Paul Van Delst
• Re: gfortran installation breaking other installations
  • From: Paul Van Delst
• Re: gfortran installation breaking other installations
  • From: Steven G. Kargl
• Re: What did I do wrong with "external" ??
  • From: Richard E Maine
• Re: Coding EOF in FORTRAN 77?
  • From: jwm
• Re: gfortran installation breaking other installations
  • From: glen herrmannsfeldt
• Re: gfortran installation breaking other installations
  • From: FX
• Re: gfortran installation breaking other installations
  • From: FX
• Re: gfortran installation breaking other installations
  • From: Brooks Moses
• gfortran installation breaking other installations
  • From: Paul Van Delst
• Re: What did I do wrong with "external" ??
  • From: Steve Lionel
• Re: What did I do wrong with "external" ??
  • From: Ancient_Hacker
• Re: Coding EOF in FORTRAN 77?
  • From: Jim
• Re: Coding EOF in FORTRAN 77?
  • From: Richard E Maine
• Re: Bounds Check Overhead
  • From: Richard E Maine
• Re: Coding EOF in FORTRAN 77?
  • From: Jim
• Re: Bounds Check Overhead
  • From: glen herrmannsfeldt
• Re: Scrolling a dialog window
  • From: gary . l . scott
• Re: Scrolling a dialog window
  • From: gary . l . scott
• Re: What did I do wrong with "external" ??
  • From: Richard E Maine
• Re: Algorithm help for unique string searching/counting within an array.
  • From: Paul Van Delst
• Re: What did I do wrong with "external" ??
  • From: David Frank
• What did I do wrong with "external" ??
  • From: Ancient_Hacker
• Scrolling a dialog window
  • From: berger@xxxxxx
• Re: Bounds Check Overhead
  • From: Richard E Maine
• Re: Coding EOF in FORTRAN 77?
  • From: Herman D . Knoble
• Re: Coding EOF in FORTRAN 77?
  • From: Jan Vorbrüggen
• Re: g95 gotoBLAS test failed
  • From: James
• Coding EOF in FORTRAN 77?
  • From: HK
• gfortran with OpenMP on Windows
  • From: FX
• Re: how to create a Snapshot of subroutines or functions used in a project
  • From: gkxjgbh
• Re: Intel Fortan module symbol conflict
  • From: robert . corbett
• Re: defacto standard extensions
  • From: robert . corbett
• Re: Bounds Check Overhead
  • From: Jan Vorbrüggen
• RE: Coding EOF in FORTRAN 77?
  • From: meek
• Re: Intel Fortan module symbol conflict
  • From: Jugoslav Dujic
• Re: defacto standard extensions
  • From: glen herrmannsfeldt
• Re: Bounds Check Overhead
  • From: robert . corbett
• Re: defacto standard extensions
  • From: robert . corbett
• Re: Intel Fortan module symbol conflict
  • From: robert . corbett
• Re: Optimizing c1 * conjg(c1)
  • From: robert . corbett
• Re: Optimizing c1 * conjg(c1)
  • From: robert . corbett
• Re: allocatable array *not* equivalent to dynamic allocation?
  • From: glen herrmannsfeldt
• Re: allocatable array *not* equivalent to dynamic allocation?
  • From: jamesgiles@xxxxxxx
• g95 gotoBLAS test failed
  • From: James
• Re: Intel Fortan module symbol conflict
  • From: Dick Hendrickson
• Re: Beginer needing help
  • From: vexx
• Re: Beginer needing help
  • From: Craig Powers
• Re: Beginer needing help
  • From: vexx
• Re: Intel Fortan module symbol conflict
  • From: Joe Krahn
• Re: allocatable array *not* equivalent to dynamic allocation?
  • From: Joe Krahn
• Re: Intel Fortan module symbol conflict
  • From: Richard E Maine
• Intel Fortan module symbol conflict
  • From: Joe Krahn
• Re: Optimizing c1 * conjg(c1)
  • From: glen herrmannsfeldt
• Optimizing c1 * conjg(c1)
  • From: Thomas Koenig
• Re: defacto standard extensions
  • From: Richard E Maine
• Re: Beginer needing help
  • From: Michael Metcalf
• Re: Fortranspeak & Javaspeak
  • From: Ancient_Hacker
• Re: defacto standard extensions
  • From: Steven G. Kargl
• Re: Beginer needing help
  • From: vexx
• Re: defacto standard extensions
  • From: Richard E Maine
• Re: Beginer needing help
  • From: e p chandler
• Re: defacto standard extensions
  • From: Steven G. Kargl
• Re: Beginer needing help
  • From: vexx
• Re: defacto standard extensions
  • From: Richard E Maine
• Re: Bounds Check Overhead
  • From: Richard E Maine
• Re: Converting fixed-to-free format
  • From: tbwright
• Re: Converting fixed-to-free format
  • From: Dan Nagle
• Re: Converting fixed-to-free format
  • From: robin
• Re: defacto standard extensions
  • From: Gordon Sande
• Re: Inserting data in linked lists
  • From: Jugoslav Dujic
• Inserting data in linked lists
  • From: deltaquattro
• defacto standard extensions
  • From: robert . corbett
• Re: Bounds Check Overhead
  • From: Jugoslav Dujic
• Re: Converting fixed-to-free format
  • From: John
• Re: Converting fixed-to-free format
  • From: Gary L. Scott
• Re: Ada vs Fortran for scientific applications
  • From: robert . corbett
• Re: Cannot create import libraries with Microsoft's LIB with the option mixed language Borland C++ (-ml bc) with Lahey v5.7
  • From: gabsata
• Re: Converting fixed-to-free format
  • From: Dan Nagle

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