comp.lang.fortran

• Thread Index

---

• Re: Module compile order
  • From: James Giles
• Re: Garbage in dead zone
  • From: James Van Buskirk
• Re: warning on running image !!!!!
  • From: Steve Lionel
• Re: Module compile order
  • From: Thomas Robitaille
• Re: Module compile order
  • From: Richard Maine
• Module compile order
  • From: Thomas Robitaille
• Re: Fortran 90 Chess
  • From: dean . menezes
• Re: Fortran 90 Chess
  • From: fj
• Re: Is this legal?
  • From: Salvatore
• Re: NYT disses Fortran
  • From: Michael Metcalf
• Re: Fortran 90 Chess
  • From: robin
• Re: Garbage in dead zone
  • From: Charles Coldwell
• Re: optional or interface
  • From: Arjen Markus
• Re: Binding name
  • From: James Van Buskirk
• Re: CPAN equivalent for fortran?
  • From: Ron Ford
• NYT disses Fortran
  • From: Greg Lindahl
• Re: optional assumed-shape array
  • From: Richard Maine
• Re: warning on running image !!!!!
  • From: nakisa
• Re: .true. help
  • From: Mike
• optional or interface
  • From: Mike
• optional assumed-shape array
  • From: Mike
• Re: format with G descriptor
  • From: glen herrmannsfeldt
• Re: format with G descriptor
  • From: James Giles
• Re: format with G descriptor
  • From: Roman
• Re: format with G descriptor
  • From: Kurt Kallblad
• Re: format with G descriptor
  • From: James Giles
• Re: one-liner for characater replacement
  • From: James Giles
• format with G descriptor
  • From: Roman
• Re: Is this legal?
  • From: Craig Powers
• Re: Problem with file writing
  • From: Craig Powers
• Re: Problem with file writing
  • From: Steven G. Kargl
• Re: Problem with file writing
  • From: e p chandler
• Problem with file writing
  • From: Philippe
• Re: one-liner for characater replacement
  • From: Jan Vorbrüggen
• Re: .true. help
  • From: e p chandler
• Re: Arrays Intersection
  • From: Arjen Markus
• Re: Arrays Intersection
  • From: Paul van Delst
• Re: warning on running image !!!!!
  • From: Steve Lionel
• Re: Arrays Intersection
  • From: Arjen Markus
• Re: Arrays Intersection
  • From: Gordon Sande
• Re: Arrays Intersection
  • From: glen herrmannsfeldt
• Re: Arrays Intersection
  • From: Arjen Markus
• Re: Arrays Intersection
  • From: Gordon Sande
• warning on running image !!!!!
  • From: nakisa
• Re: one-liner for characater replacement
  • From: dpb
• Re: Arrays Intersection
  • From: Arjen Markus
• Re: Is this legal?
  • From: Salvatore
• Re: public/private and overloaded operator
  • From: Steve Lionel
• Re: Fortran 77 alphabet character $
  • From: user1
• Re: newbie: that mapping CHARACTER*2 to INTEGER*2 question
  • From: Steve Lionel
• Arrays Intersection
  • From: Infinity77
• Re: one-liner for characater replacement
  • From: analyst41
• Re: .true. help
  • From: rudra
• Re: one-liner for characater replacement
  • From: analyst41
• Re: .true. help
  • From: rudra
• Re: .true. help
  • From: Arjen Markus
• Re: Interfacing between Fortran and C - a little utility
  • From: Arjen Markus
• Re: .true. help
  • From: Alois Steindl
• Re: Interfacing between Fortran and C - a little utility
  • From: rudra
• .true. help
  • From: rudra
• CPAN equivalent for fortran?
  • From: Thomas Robitaille
• Re: newbie: that mapping CHARACTER*2 to INTEGER*2 question
  • From: Arjen Markus
• Re: one-liner for characater replacement
  • From: Jan Vorbrüggen
• Re: Is this legal?
  • From: robert . corbett
• Re: HPC Considered Harmful
  • From: e p chandler
• Re: Fortran 77 alphabet character $
  • From: Ian Gay
• Re: Fortran 77 alphabet character $
  • From: Terence
• Re: one-liner for characater replacement
  • From: dpb
• Re: one-liner for characater replacement
  • From: James Giles
• Re: one-liner for characater replacement
  • From: analyst41
• Re: Fortran 77 alphabet character $
  • From: Gary Scott
• Re: Fortran 77 alphabet character $
  • From: Terence
• Re: Fortran 77 alphabet character $
  • From: e p chandler
• Re: Fortran 77 alphabet character $
  • From: John Harper
• Re: public/private and overloaded operator
  • From: Richard Maine
• Re: Fortran 90 Chess
  • From: dean . menezes
• public/private and overloaded operator
  • From: mrestelli@xxxxxxxxx
• Re: one-liner for characater replacement
  • From: James Giles
• Re: Slick or Slack
  • From: Bil
• Re: Slick or Slack
  • From: Bil
• Re: Fortran 77 alphabet character $
  • From: GaryScott
• Re: one-liner for characater replacement
  • From: GaryScott
• Re: one-liner for characater replacement
  • From: dpb
• Re: Fortran 77 alphabet character $
  • From: e p chandler
• Re: Fortran 77 alphabet character $
  • From: Herman D . Knoble
• Re: Fortran 77 alphabet character $
  • From: mecej4
• Re: Gfortran 4.4 binary (OpenMP and 64bit capability) for PPC Tiger
  • From: Al Greynolds
• Re: Is this legal?
  • From: Richard Maine
• Re: Fortran 77 alphabet character $
  • From: Richard Maine
• Re: Fortran 77 alphabet character $
  • From: glen herrmannsfeldt
• Re: Fortran 77 alphabet character $
  • From: GaryScott
• Re: Fortran 77 alphabet character $
  • From: Herman D . Knoble
• Re: one-liner for characater replacement
  • From: Tom Micevski
• Re: Is this legal?
  • From: Salvatore
• Re: one-liner for characater replacement
  • From: analyst41
• Is this legal?
  • From: Salvatore
• Re: Fortran 77 alphabet character $
  • From: Arjen Markus
• Fortran 77 alphabet character $
  • From: Herman D . Knoble
• Re: one-liner for characater replacement
  • From: analyst41
• Re: one-liner for characater replacement
  • From: FX
• Re: 1.0d0 stored as integer?
  • From: FX
• Re: problem with very small numbers - g95 versus gfortran
  • From: James Van Buskirk
• Interfacing between Fortran and C - a little utility
  • From: Arjen Markus
• Re: problem with very small numbers - g95 versus gfortran
  • From: Steven G. Kargl
• Re: problem with very small numbers - g95 versus gfortran
  • From: James Van Buskirk
• Re: Slick or Slack
  • From: e p chandler
• Re: problem with very small numbers - g95 versus gfortran
  • From: James Van Buskirk
• Re: problem with very small numbers - g95 versus gfortran
  • From: e p chandler
• Re: problem with very small numbers - g95 versus gfortran
  • From: e p chandler
• Re: problem with very small numbers - g95 versus gfortran
  • From: James Van Buskirk
• Re: Slick or Slack
  • From: Damian
• Re: problem with very small numbers - g95 versus gfortran
  • From: James Van Buskirk
• Re: one-liner for characater replacement
  • From: James Giles
• Re: Validation?
  • From: e p chandler
• Re: problem with very small numbers - g95 versus gfortran
  • From: e p chandler
• Re: problem with very small numbers - g95 versus gfortran
  • From: e p chandler
• Re: problem with very small numbers - g95 versus gfortran
  • From: James Van Buskirk
• Re: one-liner for characater replacement
  • From: Gary Scott
• Re: problem with very small numbers - g95 versus gfortran
  • From: James Van Buskirk
• Re: Unsigned in CVF
  • From: glen herrmannsfeldt
• Re: 1.0d0 stored as integer?
  • From: glen herrmannsfeldt
• Re: one-liner for characater replacement
  • From: analyst41
• Re: 1.0d0 stored as integer?
  • From: Richard Maine
• Re: Fortran 90 Chess
  • From: John Harper
• 1.0d0 stored as integer?
  • From: David Gunter
• Re: Gfortran 4.4 binary (OpenMP and 64bit capability) for PPC Tiger
  • From: FX
• Slick or Slack
  • From: Bil Kleb
• HPC Considered Harmful
  • From: Bil Kleb
• Gfortran 4.4 binary (OpenMP and 64bit capability) for PPC Tiger
  • From: Al Greynolds
• problem with very small numbers - g95 versus gfortran
  • From: e p chandler
• Re: How to do AINS() and ADEL()
  • From: Steve Lionel
• Re: Reinitialising random number generator
  • From: robin
• Re: How to do AINS() and ADEL()
  • From: Gordon Sande
• Re: Fortran 90 Chess
  • From: John
• Re: How to do AINS() and ADEL()
  • From: David Frank
• Re: HDF read example
  • From: Hajo Klingshirn
• Re: How to do AINS() and ADEL()
  • From: axtens
• Foray Build Tool Project Started
  • From: drewmccormack
• RE: HDF read example
  • From: meek
• Re: How to do AINS() and ADEL()
  • From: Arjen Markus
• How to do AINS() and ADEL()
  • From: axtens
• Re: Validation?
  • From: e p chandler
• Re: one-liner for characater replacement
  • From: James Giles
• Re: one-liner for characater replacement
  • From: analyst41
• Re: Fortran algorithms to look for a maximum over an array of real numbers
  • From: Tim Prince
• Re: Unsigned in CVF
  • From: axtens
• Re: one-liner for characater replacement
  • From: James Giles
• Re: Unsigned in CVF
  • From: axtens
• Re: one-liner for characater replacement
  • From: glen herrmannsfeldt
• Re: one-liner for characater replacement
  • From: glen herrmannsfeldt
• Validation?
  • From: Terence
• Re: Unsigned in CVF
  • From: Terence
• Re: Unsigned in CVF
  • From: robert . corbett
• Re: HDF read example
  • From: Paul van Delst
• Re: HDF read example
  • From: fj
• Re: one-liner for characater replacement
  • From: dpb
• Re: Error compiling example program with gfortran using lapack95 on win32
  • From: Richard Maine
• HDF read example
  • From: clay . blankenship
• Error compiling example program with gfortran using lapack95 on win32
  • From: Harald Breitkreutz
• Re: one-liner for characater replacement
  • From: dpb
• Re: one-liner for characater replacement
  • From: dpb
• Re: one-liner for characater replacement
  • From: James Giles
• Re: one-liner for characater replacement
  • From: analyst41
• Re: one-liner for characater replacement
  • From: analyst41
• Re: Unsigned in CVF
  • From: Arjen Markus
• Re: Unsigned in CVF
  • From: Jugoslav Dujic
• Unsigned in CVF
  • From: axtens
• Re: Fortran algorithms to look for a maximum over an array of real numbers
  • From: robert . corbett
• Fortran algorithms to look for a maximum over an array of real numbers
  • From: octaedro
• Re: RtlMoveMemory not being found to link in
  • From: axtens
• Re: RtlMoveMemory not being found to link in
  • From: Jugoslav Dujic
• Re: RtlMoveMemory not being found to link in
  • From: axtens
• Re: RtlMoveMemory not being found to link in
  • From: axtens
• Re: RtlMoveMemory not being found to link in
  • From: Jugoslav Dujic
• Re: RtlMoveMemory not being found to link in
  • From: axtens
• Re: one-liner for characater replacement
  • From: dpb
• Re: one-liner for characater replacement
  • From: Gary Scott
• Re: one-liner for characater replacement
  • From: James Giles
• Re: one-liner for characater replacement
  • From: analyst41
• Re: one-liner for characater replacement
  • From: James Giles
• Re: one-liner for characater replacement
  • From: dpb
• Re: one-liner for characater replacement
  • From: James Giles
• Re: one-liner for characater replacement
  • From: analyst41
• Re: RtlMoveMemory not being found to link in
  • From: Craig Powers
• Re: GNU gfortran on Mac OSX
  • From: breyfogle
• Re: GNU gfortran on Mac OSX
  • From: dominiq
• Re: one-liner for characater replacement
  • From: James Giles
• Re: GNU gfortran on Mac OSX
  • From: FX
• Re: one-liner for characater replacement
  • From: dpb
• Re: one-liner for characater replacement
  • From: James Giles
• Re: GNU gfortran on Mac OSX
  • From: dominiq
• Re: RtlMoveMemory not being found to link in
  • From: Steve Lionel
• Re: GNU gfortran on Mac OSX
  • From: breyfogle
• Re: one-liner for characater replacement
  • From: James Giles
• Re: one-liner for characater replacement
  • From: Gary Scott
• Re: one-liner for characater replacement
  • From: analyst41
• Re: GNU gfortran on Mac OSX
  • From: dominiq
• Re: one-liner for characater replacement
  • From: glen herrmannsfeldt
• GNU gfortran on Mac OSX
  • From: breyfogle
• Re: Garbage in dead zone
  • From: e p chandler
• Re: Fortran 90 Chess
  • From: samanddeanus
• Re: Fortran 90 Chess
  • From: dean . menezes
• Re: Fortran 90 Chess
  • From: robin
• Re: RtlMoveMemory not being found to link in
  • From: Jugoslav Dujic
• Re: RtlMoveMemory not being found to link in
  • From: axtens
• Re: RtlMoveMemory not being found to link in
  • From: Steve Lionel
• Re: Garbage in dead zone
  • From: Steve Lionel
• Re: RtlMoveMemory not being found to link in
  • From: axtens
• RtlMoveMemory not being found to link in
  • From: axtens
• Re: one-liner for characater replacement
  • From: James Giles
• Re: Garbage in dead zone
  • From: glen herrmannsfeldt
• Re: one-liner for characater replacement
  • From: glen herrmannsfeldt
• Re: Garbage in dead zone
  • From: Richard Maine
• Re: newbie: that mapping CHARACTER*2 to INTEGER*2 question
  • From: axtens
• newbie: that mapping CHARACTER*2 to INTEGER*2 question
  • From: axtens
• Garbage in dead zone
  • From: James Van Buskirk
• Re: Fortran 90 Chess
  • From: robin
• Re: Fortran 90 Chess
  • From: Dean Menezes
• Re: Fortran 2003 questions
  • From: Tobias Burnus
• Re: one-liner for characater replacement
  • From: James Giles
• Re: one-liner for characater replacement
  • From: analyst41
• Re: one-liner for characater replacement
  • From: James Giles
• Re: I think the standard will be on my side (BOZ)
  • From: Gary Scott
• Re: Fortran 2003 questions
  • From: Richard Maine
• Re: Fortran 2003 questions
  • From: Richard Maine
• Re: Fortran 2003 questions
  • From: James Van Buskirk
• Re: Fortran 90 Chess
  • From: robin
• Re: I think the standard will be on my side (BOZ)
  • From: Charles Coldwell
• Re: Fortran 2003 questions
  • From: Tobias Burnus
• Fortran 2003 questions
  • From: jaydub66@xxxxxxxxx
• Re: one-liner for characater replacement
  • From: Ron Ford
• Re: one-liner for characater replacement
  • From: Gary Scott
• Re: Binding name
  • From: James Van Buskirk
• Re: one-liner for characater replacement
  • From: James Giles
• Re: one-liner for characater replacement
  • From: Gary Scott
• Re: one-liner for characater replacement
  • From: James Giles
• Re: Binding name
  • From: James Van Buskirk
• Re: one-liner for characater replacement
  • From: Gary Scott
• Re: Binding name
  • From: James Van Buskirk
• Re: one-liner for characater replacement
  • From: analyst41
• Re: allocatable array component with intent(out)
  • From: Ron Shepard
• Re: Binding name
  • From: James Van Buskirk
• Re: Array Filtering
  • From: Infinity77
• Re: Binding name
  • From: FX
• Re: Binding name
  • From: James Van Buskirk
• Re: Array Filtering
  • From: glen herrmannsfeldt
• Re: Array Filtering
  • From: glen herrmannsfeldt
• Re: allocatable array component with intent(out)
  • From: Steve Lionel
• Re: Array Filtering
  • From: Ken . Fairfield
• Re: Array Filtering
  • From: Ken . Fairfield
• Re: transfer filename to subroutine
  • From: Richard Maine
• Re: about recursion function.
  • From: Richard Maine
• Re: Array Filtering
  • From: James Van Buskirk
• Re: Array Filtering
  • From: Infinity77
• Re: Array Filtering
  • From: Mark Westwood
• Re: allocatable array component with intent(out)
  • From: glen herrmannsfeldt
• Re: about recursion function.
  • From: Paul van Delst
• Re: about recursion function.
  • From: Mark Westwood
• Re: Array Filtering
  • From: Infinity77
• Re: transfer filename to subroutine
  • From: Steven G. Kargl
• about recursion function.
  • From: alex
• Re: file copy routine
  • From: GaryScott
• Re: allocatable array component with intent(out)
  • From: Michael Metcalf
• Re: Copying data between pointers
  • From: Paul van Delst
• Re: maximum open files and unit numbers
  • From: Paul van Delst
• Re: allocatable array component with intent(out)
  • From: mecej4
• Re: allocatable array component with intent(out)
  • From: Jugoslav Dujic
• Re: Binding name
  • From: FX
• Fix: allocatable array component with intent(out)
  • From: Jugoslav Dujic
• Re: allocatable array component with intent(out)
  • From: Jugoslav Dujic
• Re: Array Filtering
  • From: Michael Metcalf
• Re: Array Filtering
  • From: Daniel Franke
• allocatable array component with intent(out)
  • From: Ron Shepard
• Re: Array Filtering
  • From: alex
• Re: Array Filtering
  • From: alex
• Re: Array Filtering
  • From: Arjen Markus
• Array Filtering
  • From: Infinity77
• Re: Binding name
  • From: James Van Buskirk
• Re: transfer filename to subroutine
  • From: e p chandler
• Re: Binding name
  • From: FX
• Re: Reinitialising random number generator
  • From: Arjen Markus
• Re: Requirements for FINAL procedures
  • From: Daniel Kraft
• Re: Binding name
  • From: James Van Buskirk
• Re: Reinitialising random number generator
  • From: Thomas Koenig
• Re: Reinitialising random number generator
  • From: Thomas Koenig
• Re: transfer filename to subroutine
  • From: rudra
• Re: transfer filename to subroutine
  • From: rudra
• Re: Reinitialising random number generator
  • From: FX
• Re: maximum open files and unit numbers
  • From: relaxmike
• Re: Reinitialising random number generator
  • From: Arjen Markus
• Re: transfer filename to subroutine
  • From: glen herrmannsfeldt
• Re: Copying data between pointers
  • From: Gib Bogle
• Re: transfer filename to subroutine
  • From: Richard Maine
• transfer filename to subroutine
  • From: rudra
• Re: encoding="utf-8" and formatted direct access
  • From: James Giles
• Re: one-liner for characater replacement
  • From: glen herrmannsfeldt
• Re: encoding="utf-8" and formatted direct access
  • From: William Clodius
• Re: ISO 10646 support
  • From: William Clodius
• Re: one-liner for characater replacement
  • From: analyst41
• Re: file copy routine
  • From: andrej . panjkov
• Re: one-liner for characater replacement
  • From: glen herrmannsfeldt
• Re: file copy routine
  • From: glen herrmannsfeldt
• Re: file copy routine
  • From: James Giles
• Re: Copying data between pointers
  • From: glen herrmannsfeldt
• Re: one-liner for characater replacement
  • From: James Giles
• Re: one-liner for characater replacement
  • From: glen herrmannsfeldt
• Re: file copy routine
  • From: GaryScott
• Re: Copying data between pointers
  • From: Paul van Delst
• Re: one-liner for characater replacement
  • From: James Giles
• Requirements for FINAL procedures
  • From: Daniel Kraft
• Re: Copying data between pointers
  • From: Gib Bogle
• Re: Copying data between pointers
  • From: Gib Bogle
• Re: Requirements for FINAL procedures
  • From: Richard Maine
• Re: file copy routine
  • From: James Giles
• Re: Question about passing arrays to subroutines
  • From: Lorents
• Re: file copy routine
  • From: GaryScott
• Re: file copy routine
  • From: James Giles
• Re: KIND optional argument in transformational intrinsics
  • From: James Van Buskirk
• Re: Fortran 90 Chess
  • From: dean . menezes
• Re: one-liner for characater replacement
  • From: James Giles
• Re: one-liner for characater replacement
  • From: James Van Buskirk
• Re: Reinitialising random number generator
  • From: Richard Maine
• Re: one-liner for characater replacement
  • From: Richard Maine
• Re: one-liner for characater replacement
  • From: analyst41
• Re: Reinitialising random number generator
  • From: Thomas Koenig
• Re: one-liner for characater replacement
  • From: James Van Buskirk
• Re: Reinitialising random number generator
  • From: Richard Maine
• Re: Question about passing arrays to subroutines
  • From: Richard Maine
• Re: Copying data between pointers
  • From: Richard Maine
• Re: Reinitialising random number generator
  • From: Thomas Koenig
• Re: Reinitialising random number generator
  • From: Dave Seaman
• Re: Question about passing arrays to subroutines
  • From: Paul van Delst
• Question about passing arrays to subroutines
  • From: Lorents
• Re: Fortran 90 Chess
  • From: Beliavsky
• Re: file copy routine
  • From: GaryScott
• Re: file copy routine
  • From: Paul van Delst
• Re: Reinitialising random number generator
  • From: Arjen Markus
• Re: Reinitialising random number generator
  • From: Dave Seaman
• Re: Reinitialising random number generator
  • From: Arjen Markus
• Re: one-liner for characater replacement
  • From: analyst41
• Re: newbie: mapping CHARACTER*2 to INTEGER*2
  • From: glen herrmannsfeldt
• Re: Copying data between pointers
  • From: glen herrmannsfeldt
• Re: Reinitialising random number generator
  • From: Thomas Koenig
• Re: Reinitialising random number generator
  • From: Arjen Markus
• Re: Reinitialising random number generator
  • From: Thomas Koenig
• Re: Fortran 90 Chess
  • From: Phillip Helbig---remove CLOTHES to reply
• Reinitialising random number generator
  • From: Arjen Markus
• Re: Writing nul characters, f90 formatted output
  • From: robert . corbett
• Re: file copy routine
  • From: James Giles
• Re: file copy routine
  • From: andrej . panjkov
• Re: Copying data between pointers
  • From: Gib Bogle
• Re: Copying data between pointers
  • From: Gib Bogle
• Re: newbie: mapping CHARACTER*2 to INTEGER*2
  • From: paul . richard . thomas
• Re: file copy routine
  • From: James Giles
• Re: file copy routine
  • From: andrej . panjkov
• Re: Fortran 90 Chess
  • From: e p chandler
• Re: one-liner for characater replacement
  • From: Steven G. Kargl
• Re: one-liner for characater replacement
  • From: rudra
• Re: newbie: mapping CHARACTER*2 to INTEGER*2
  • From: axtens
• Re: Copying data between pointers
  • From: glen herrmannsfeldt
• Re: Copying data between pointers
  • From: Richard Maine
• Fortran 90 Chess
  • From: dean . menezes
• Copying data between pointers
  • From: Gib Bogle
• Re: public comments
  • From: Dan Nagle
• Re: public comments
  • From: Greg Lindahl
• Re: Dynamic CHAR length?
  • From: relaxmike
• Re: public comments
  • From: Dan Nagle
• Re: Creating .so file to call from IDL
  • From: Tobias Burnus
• Re: public comments
  • From: Craig Powers
• Re: newbie: mapping CHARACTER*2 to INTEGER*2
  • From: James Van Buskirk
• Re: Creating .so file to call from IDL
  • From: Jean H
• Re: Writing nul characters, f90 formatted output
  • From: posol
• Re: maximum open files and unit numbers
  • From: James Giles
• Re: file copy routine
  • From: James Van Buskirk
• Re: maximum open files and unit numbers
  • From: James Giles
• Re: maximum open files and unit numbers
  • From: James Giles
• Re: Writing nul characters, f90 formatted output
  • From: James Van Buskirk
• Re: Using external subroutines in OpenMP: Update
  • From: jomarbueyes
• Re: Writing nul characters, f90 formatted output
  • From: posol
• Re: Writing nul characters, f90 formatted output
  • From: Michael Metcalf
• Writing nul characters, f90 formatted output
  • From: posol
• Re: maximum open files and unit numbers
  • From: Catherine Rees Lay
• Re: maximum open files and unit numbers
  • From: Paul van Delst
• maximum open files and unit numbers
  • From: Glenn Forney
• newbie: mapping CHARACTER*2 to INTEGER*2
  • From: axtens
• public comments
  • From: Dan Nagle
• Re: encoding="utf-8" and formatted direct access
  • From: Richard Maine
• Re: encoding="utf-8" and formatted direct access
  • From: Jan Vorbrüggen
• Re: one-liner for characater replacement
  • From: Jan Vorbrüggen
• Re: Fortran 2003 : no OO constructor ?
  • From: Ron Ford
• Re: Fortran 2003 : no OO constructor ?
  • From: Jan Vorbrüggen
• Re: encoding="utf-8" and formatted direct access
  • From: glen herrmannsfeldt
• Re: Variable size component in derived type
  • From: Gib Bogle
• RE: newbie: mapping CHARACTER*2 to INTEGER*2
  • From: meek
• Re: Variable size component in derived type
  • From: Gib Bogle
• Re: ISO 10646 support
  • From: Ron Ford
• Re: encoding="utf-8" and formatted direct access
  • From: James Giles
• Re: encoding="utf-8" and formatted direct access
  • From: James Giles
• Re: Variable size component in derived type
  • From: Jim Xia
• Re: I need help about IF command
  • From: rudra
• Re: encoding="utf-8" and formatted direct access
  • From: William Clodius
• Re: encoding="utf-8" and formatted direct access
  • From: William Clodius
• Re: Dynamic CHAR length?
  • From: Jim Xia
• Re: Using external subroutines in OpenMP: Update
  • From: Ron Ford
• Re: encoding="utf-8" and formatted direct access
  • From: Gary Scott
• Re: Variable size component in derived type
  • From: Gib Bogle
• Re: encoding="utf-8" and formatted direct access
  • From: James Giles
• Re: one-liner for characater replacement
  • From: James Giles
• Re: Variable size component in derived type
  • From: Gib Bogle
• Re: encoding="utf-8" and formatted direct access
  • From: FX
• Re: Variable size component in derived type
  • From: Richard Maine
• Re: Binding name
  • From: FX
• Re: one-liner for characater replacement
  • From: analyst41
• Re: Variable size component in derived type
  • From: Gib Bogle
• Re: Variable size component in derived type
  • From: Gib Bogle
• Re: Binding name
  • From: Tim Prince
• Re: Fortran 2003 : no OO constructor ?
  • From: John Harper
• Re: file copy routine
  • From: John
• Re: encoding="utf-8" and formatted direct access
  • From: glen herrmannsfeldt
• Re: Binding name
  • From: James Van Buskirk
• Re: encoding="utf-8" and formatted direct access
  • From: Richard Maine
• Re: Dynamic CHAR length?
  • From: Richard Maine
• Re: encoding="utf-8" and formatted direct access
  • From: James Giles
• Re: encoding="utf-8" and formatted direct access
  • From: James Giles
• Re: encoding="utf-8" and formatted direct access
  • From: James Giles
• Re: Fortran 2003 : no OO constructor ?
  • From: glen herrmannsfeldt
• Re: encoding="utf-8" and formatted direct access
  • From: Thomas Koenig
• Re: encoding="utf-8" and formatted direct access
  • From: Thomas Koenig
• Re: Dynamic CHAR length?
  • From: relaxmike
• Re: one-liner for characater replacement
  • From: James Giles
• Re: Variable size component in derived type
  • From: Richard Maine
• Re: Binding name
  • From: Tobias Burnus
• Re: Fortran 2003 : no OO constructor ?
  • From: Richard Maine
• Re: Dynamic CHAR length?
  • From: Richard Maine
• Using external subroutines in OpenMP: Update
  • From: jomarbueyes
• Re: Binding name
  • From: Steve Lionel
• Re: Binding name
  • From: Richard Maine
• Re: I need help about IF command
  • From: mah
• Re: I need help about IF command
  • From: mah
• Re: Binding name
  • From: James Van Buskirk
• Re: I need help about IF command
  • From: Michael Metcalf
• Re: file copy routine
  • From: James Van Buskirk
• Fortran 2003 : no OO constructor ?
  • From: relaxmike
• Re: encoding="utf-8" and formatted direct access
  • From: glen herrmannsfeldt
• Re: g95 writes 0.232699336-309 instead of 0.000000000E+00
  • From: e p chandler
• Re: I need help about IF command
  • From: rudra
• Re: g95 writes 0.232699336-309 instead of 0.000000000E+00
  • From: glen herrmannsfeldt
• Re: file copy routine
  • From: John
• Re: I need help about IF command
  • From: glen herrmannsfeldt
• Re: file copy routine
  • From: John
• Re: one-liner for characater replacement
  • From: analyst41
• Re: Binding name
  • From: FX
• Re: Binding name
  • From: James Van Buskirk
• Re: Binding name
  • From: James Van Buskirk
• Re: Binding name
  • From: FX
• Re: Binding name
  • From: FX
• Re: Dynamic CHAR length?
  • From: relaxmike
• Binding name
  • From: James Van Buskirk
• Re: Variable size component in derived type
  • From: Gib Bogle
• Re: I need help about IF command
  • From: Arjen Markus
• Re: Variable size component in derived type
  • From: dominiq
• I need help about IF command
  • From: mah
• Re: Variable size component in derived type
  • From: James Van Buskirk
• Re: Variable size component in derived type
  • From: Gib Bogle
• Re: Variable size component in derived type
  • From: Arjen Markus
• Re: secnds
  • From: Kurt Kallblad
• Variable size component in derived type
  • From: Gib Bogle
• Re: secnds
  • From: Steven G. Kargl
• secnds
  • From: rudra
• Re: encoding="utf-8" and formatted direct access
  • From: William Clodius
• Re: file copy routine
  • From: GaryScott
• Re: Ifort long compilation time
  • From: Richard Maine
• Re: Dynamic CHAR length?
  • From: Richard Maine
• Re: Dynamic CHAR length?
  • From: alex
• Re: Ifort long compilation time
  • From: glen herrmannsfeldt
• Re: encoding="utf-8" and formatted direct access
  • From: James Giles
• Re: DPROD issues
  • From: James Van Buskirk
• Re: encoding="utf-8" and formatted direct access
  • From: James Giles
• Re: encoding="utf-8" and formatted direct access
  • From: glen herrmannsfeldt
• Re: Ifort long compilation time
  • From: Greg Lindahl
• Re: encoding="utf-8" and formatted direct access
  • From: James Giles
• Re: encoding="utf-8" and formatted direct access
  • From: Richard Maine
• Re: KIND optional argument in transformational intrinsics
  • From: Dick Hendrickson
• Re: encoding="utf-8" and formatted direct access
  • From: Thomas Koenig
• Re: encoding="utf-8" and formatted direct access
  • From: Richard Maine
• Re: file copy routine
  • From: David Frank
• Re: one-liner for characater replacement
  • From: David Frank
• encoding="utf-8" and formatted direct access
  • From: Thomas Koenig
• Re: file copy routine
  • From: James Giles
• Re: Dynamic CHAR length?
  • From: Mark Morss
• Re: Dynamic CHAR length?
  • From: Richard Maine
• Re: one-liner for characater replacement
  • From: utab
• Dynamic CHAR length?
  • From: Mark Morss
• Re: g95 writes 0.232699336-309 instead of 0.000000000E+00
  • From: Richard Maine
• Re: Yay!
  • From: Bamm
• Re: Parsing gfortran error messages in emacs
  • From: Steven G. Kargl
• Re: g95 writes 0.232699336-309 instead of 0.000000000E+00
  • From: Steven G. Kargl
• Re: file copy routine
  • From: Les
• Re: one-liner for characater replacement
  • From: Walter Spector
• Re: g95 writes 0.232699336-309 instead of 0.000000000E+00
  • From: Ron Ford
• Re: file copy routine
  • From: John
• Re: file copy routine
  • From: David Frank
• Re: file copy routine
  • From: John
• opening files in psuite on NEC SX8
  • From: mccabec67
• Re: one-liner for characater replacement
  • From: David Frank
• Re: g95 writes 0.232699336-309 instead of 0.000000000E+00
  • From: Alois Steindl
• Parsing gfortran error messages in emacs
  • From: honestguvnor
• Re: g95 writes 0.232699336-309 instead of 0.000000000E+00
  • From: louisJ
• Re: using gdb on windows
  • From: Ron Ford
• line numbers was : one-liner for characater replacement (was: one-liner for characater replacement)
  • From: Ron Ford
• Re: Yay!
  • From: e p chandler
• Re: one-liner for characater replacement
  • From: James Giles
• Re: gfortran ---problem with random umber
  • From: Ron Ford
• Re: Yay!
  • From: Terence
• Re: Ifort long compilation time
  • From: Terence
• Re: one-liner for characater replacement
  • From: Terence
• Re: gfortran ---problem with random umber
  • From: e p chandler
• Re: one-liner for characater replacement
  • From: James Giles
• Re: one-liner for characater replacement
  • From: Sjouke Burry
• Re: Ifort long compilation time
  • From: Tim Prince
• one-liner for characater replacement
  • From: analyst41
• Re: KIND optional argument in transformational intrinsics
  • From: James Giles
• Re: Ifort long compilation time
  • From: Richard Maine
• Re: Ifort long compilation time
  • From: mecej4
• Re: Yay!
  • From: Bamm
• Re: DPROD issues
  • From: Richard Maine
• Re: Ifort long compilation time
  • From: Tim Prince
• Re: Yay!
  • From: user1
• Re: KIND optional argument in transformational intrinsics
  • From: Dick Hendrickson
• Re: fl32 vs df in cvf6.6
  • From: Ron Ford
• Creating .so file to call from IDL
  • From: Sid
• DPROD issues
  • From: James Van Buskirk
• Re: CMPLX, REAL, and INT -- almost done
  • From: FX
• Re: gfortran ---problem with random umber
  • From: FX
• Yay!
  • From: Bamm
• Re: CMPLX, REAL, and INT -- almost done
  • From: James Van Buskirk
• Re: using gdb on windows
  • From: Ron Ford
• Re: KIND optional argument in transformational intrinsics
  • From: glen herrmannsfeldt
• Re: gfortran ---problem with random umber
  • From: Ron Ford
• Re: file copy routine
  • From: Terence
• Re: fl32 vs df in cvf6.6
  • From: Gary Scott
• Re: file copy routine
  • From: Gary Scott
• Re: Ifort long compilation time
  • From: mecej4
• Re: Ifort long compilation time
  • From: Steve Lionel
• Re: fl32 vs df in cvf6.6
  • From: mecej4
• Re: KIND optional argument in transformational intrinsics
  • From: James Giles
• Re: file copy routine
  • From: glen herrmannsfeldt
• Re: file copy routine
  • From: James Giles
• Ifort long compilation time
  • From: braams@xxxxxxxxxxxxxxxx
• Re: file copy routine
  • From: James Giles
• Re: file copy routine
  • From: James Giles
• Re: file copy routine
  • From: Richard Maine
• Re: using gdb on windows
  • From: Arjan
• Re: file copy routine
  • From: James Giles
• Re: fl32 vs df in cvf6.6
  • From: glen herrmannsfeldt
• Re: fl32 vs df in cvf6.6
  • From: Gary Scott
• Re: fl32 vs df in cvf6.6
  • From: Kurt Kallblad
• Re: file copy routine
  • From: Richard Maine
• Re: Bad start on complex tests
  • From: James Van Buskirk
• Re: file copy routine
  • From: John
• Re: using gdb on windows
  • From: Ron Ford
• Re: file copy routine
  • From: Tim Prince
• Re: Keyword arguments in intrinsics
  • From: Steven G. Kargl
• Re: Keyword arguments in intrinsics
  • From: James Van Buskirk
• Re: Keyword arguments in intrinsics
  • From: Tom Micevski
• Re: file copy routine
  • From: Richard Maine
• file copy routine
  • From: John
• Re: CMPLX, REAL, and INT -- almost done
  • From: Steven G. Kargl
• Re: CMPLX, REAL, and INT -- almost done
  • From: Steven G. Kargl
• Re: CMPLX, REAL, and INT -- almost done
  • From: James Van Buskirk
• Re: weird g77 and gfortran
  • From: stevenb . gcc
• Re: KIND optional argument in transformational intrinsics
  • From: James Giles
• Re: KIND optional argument in transformational intrinsics
  • From: James Van Buskirk
• Re: KIND optional argument in transformational intrinsics
  • From: James Giles
• Re: gfortran ---problem with random umber
  • From: Thomas Koenig
• Re: g95 writes 0.232699336-309 instead of 0.000000000E+00
  • From: Michael Metcalf
• Re: g95 writes 0.232699336-309 instead of 0.000000000E+00
  • From: Alois Steindl
• Re: g95 writes 0.232699336-309 instead of 0.000000000E+00
  • From: Gib Bogle
• Re: gfortran ---problem with random umber
  • From: Gib Bogle
• Re: gfortran ---problem with random umber
  • From: e p chandler
• Re: KIND optional argument in transformational intrinsics
  • From: James Van Buskirk
• Re: KIND optional argument in transformational intrinsics
  • From: James Giles
• Re: KIND optional argument in transformational intrinsics
  • From: James Van Buskirk
• Re: KIND optional argument in transformational intrinsics
  • From: Thomas Koenig
• Re: KIND optional argument in transformational intrinsics
  • From: James Van Buskirk
• Re: Bad start on complex tests
  • From: FX
• Re: Bad start on complex tests
  • From: James Van Buskirk
• Re: KIND optional argument in transformational intrinsics
  • From: James Giles
• Re: Bad start on complex tests
  • From: Tim Prince
• Re: Bad start on complex tests
  • From: Anony
• Re: Bad start on complex tests
  • From: Steven G. Kargl
• Re: Bad start on complex tests
  • From: Anony
• Re: Bad start on complex tests
  • From: James Van Buskirk
• Re: gfortran ---problem with random umber
  • From: Richard Maine
• Re: Bad start on complex tests
  • From: Steven G. Kargl
• Re: Bad start on complex tests
  • From: Anony
• Re: Bad start on complex tests
  • From: Anony
• Re: gfortran ---problem with random umber
  • From: rudra
• Re: gfortran ---problem with random umber
  • From: e p chandler
• Re: g95 writes 0.232699336-309 instead of 0.000000000E+00
  • From: Herman D . Knoble
• Re: gfortran ---problem with random umber
  • From: e p chandler
• Re: g95 writes 0.232699336-309 instead of 0.000000000E+00
  • From: Alois Steindl
• Re: Bad start on complex tests
  • From: FX
• Re: g95 writes 0.232699336-309 instead of 0.000000000E+00
  • From: louisJ
• Re: g95 writes 0.232699336-309 instead of 0.000000000E+00
  • From: Richard Maine
• Re: Bad start on complex tests
  • From: Steven G. Kargl
• Re: g95 writes 0.232699336-309 instead of 0.000000000E+00
  • From: Dick Hendrickson
• Re: gfortran ---problem with random umber
  • From: Richard Maine
• Re: compiler problem
  • From: Dick Hendrickson
• Re: Bad start on complex tests
  • From: Anony
• Re: Bad start on complex tests
  • From: Anony
• Re: Bad start on complex tests
  • From: Steven G. Kargl
• Re: g95 writes 0.232699336-309 instead of 0.000000000E+00
  • From: Michael Metcalf
• Re: g95 writes 0.232699336-309 instead of 0.000000000E+00
  • From: louisJ
• Re: g95 writes 0.232699336-309 instead of 0.000000000E+00
  • From: Michael Metcalf
• g95 writes 0.232699336-309 instead of 0.000000000E+00
  • From: louisJ
• Re: ISO_C_BINDING and BLAS/LAPACK
  • From: Damian
• Re: using gdb on windows
  • From: FX
• Bad start on complex tests
  • From: James Van Buskirk
• Re: gfortran ---problem with random umber
  • From: e p chandler
• Re: KIND optional argument in transformational intrinsics
  • From: FX
• Re: gfortran ---problem with random umber
  • From: FX
• Re: gfortran ---problem with random umber
  • From: steven . bosscher
• Re: weird g77 and gfortran
  • From: Ingo Thies
• KIND optional argument in transformational intrinsics
  • From: James Van Buskirk
• Keyword arguments in intrinsics
  • From: James Van Buskirk
• Re: Pointers question
  • From: Michel Olagnon
• Re: fl32 vs df in cvf6.6
  • From: Richard Maine
• Re: fl32 vs df in cvf6.6
  • From: glen herrmannsfeldt
• Re: gfortran ---problem with random umber
  • From: Ron Ford
• Re: compiler problem
  • From: Craig Powers
• Re: gfortran ---problem with random umber
  • From: Steven G. Kargl
• Re: gfortran ---problem with random umber
  • From: Ron Ford
• Re: gfortran ---problem with random umber
  • From: Steven G. Kargl
• gfortran ---problem with random umber
  • From: rudra
• Re: compiler problem
  • From: rudra
• Re: fl32 vs df in cvf6.6
  • From: Terence
• using gdb on windows
  • From: Ron Ford
• Re: fl32 vs df in cvf6.6
  • From: glen herrmannsfeldt
• Re: fl32 vs df in cvf6.6
  • From: Ron Ford
• Re: fl32 vs df in cvf6.6
  • From: alex
• Re: Pointers question
  • From: alex
• Re: Pointers question
  • From: Ron Ford
• [fixed] Opening too much time files cause a segmentation fault
  • From: Jonathan
• Re: CMPLX, REAL, and INT -- almost done
  • From: James Van Buskirk
• Re: fl32 vs df in cvf6.6
  • From: James Parsly
• Re: CMPLX, REAL, and INT -- almost done
  • From: Steven G. Kargl
• Re: fl32 vs df in cvf6.6
  • From: glen herrmannsfeldt
• Re: Pointers question
  • From: tomguest
• Re: Pointers question
  • From: glen herrmannsfeldt
• Re: fl32 vs df in cvf6.6
  • From: e p chandler
• Re: Sorting arrays
  • From: e p chandler
• Re: GFortran - OpenMP problem with Windows XP memory
  • From: Anony
• Re: weird g77 and gfortran
  • From: Thomas Koenig
• Re: fl32 vs df in cvf6.6
  • From: glen herrmannsfeldt
• Re: fl32 vs df in cvf6.6
  • From: Richard Maine
• Re: fl32 vs df in cvf6.6
  • From: Steve Lionel
• Re: fl32 vs df in cvf6.6
  • From: formulae translator
• Re: GFortran - OpenMP problem with Windows XP memory
  • From: Tobias Burnus
• Re: fl32 vs df in cvf6.6
  • From: formulae translator
• Re: fl32 vs df in cvf6.6
  • From: Michael Metcalf
• Re: fl32 vs df in cvf6.6
  • From: GaryScott
• Re: fl32 vs df in cvf6.6
  • From: Jugoslav Dujic
• Re: fl32 vs df in cvf6.6
  • From: Michael Metcalf
• IBM XLFortran 8.1 on MacOSX 10.5 (Leopard)
  • From: Al Greynolds
• fl32 vs df in cvf6.6
  • From: formulae translator
• fl32 vs df
  • From: formulae translator
• fl32 vs df
  • From: formulae translator
• Pointers question
  • From: tomguest
• Re: advance=no problem
  • From: GaryScott
• Re: Array sections and F90/95 Standard
  • From: Herman D . Knoble
• Re: Recursive function (with allocatable inside)
  • From: Gib Bogle
• Re: Sorting arrays
  • From: Mark Westwood
• Re: Derived types and allocatable
  • From: Jan Vorbrüggen
• Re: advance=no problem
  • From: dongyuanxun
• Re: advance=no problem
  • From: robert . corbett
• Re: Sorting arrays
  • From: Ron Ford
• Re: CMPLX, REAL, and INT -- almost done
  • From: James Van Buskirk
• Re: Sorting arrays
  • From: Ron Ford
• Re: CMPLX, REAL, and INT -- almost done
  • From: Steven G. Kargl
• Re: How to determine whether or not there exists a directory
  • From: Terence
• Re: Sorting arrays
  • From: Richard Maine
• Re: How to determine whether or not there exists a directory
  • From: Terence
• Re: Sorting arrays
  • From: Ron Ford
• Re: advance=no problem
  • From: Richard Maine
• Re: Sorting arrays
  • From: James Van Buskirk
• Re: advance=no problem
  • From: James Giles
• Re: advance=no problem
  • From: Gary Scott
• CMPLX, REAL, and INT -- almost done
  • From: James Van Buskirk
• Re: [ifort] Opening too much time files cause a segmentation fault
  • From: Steve Lionel
• Re: [ifort] Opening too much time files cause a segmentation fault
  • From: mecej4
• Re: Recursive function (with allocatable inside)
  • From: Ron Ford
• Re: Sorting arrays
  • From: Terence
• Re: GFortran - OpenMP problem with Windows XP memory
  • From: Anony
• Re: GFortran - OpenMP problem with Windows XP memory
  • From: Cirilo S. Bresolin
• [ifort] Opening too much time files cause a segmentation fault
  • From: Jonathan
• Re: Derived types and allocatable
  • From: James Giles
• Re: Derived types and allocatable
  • From: glen herrmannsfeldt
• Re: advance=no problem
  • From: glen herrmannsfeldt
• Re: Derived types and allocatable
  • From: James Giles
• Re: Derived types and allocatable
  • From: glen herrmannsfeldt
• Re: Sorting arrays
  • From: e p chandler
• Re: Derived types and allocatable
  • From: James Giles
• Re: Derived types and allocatable
  • From: James Giles
• Re: advance=no problem
  • From: Richard Maine
• Re: advance=no problem
  • From: Richard Maine
• Re: advance=no problem
  • From: glen herrmannsfeldt
• Re: I think the standard will be on my side (BOZ)
  • From: James Giles
• Re: advance=no problem
  • From: James Giles
• Re: How to determine whether or not there exists a directory
  • From: Steve Lionel
• Re: How to determine whether or not there exists a directory
  • From: Steve Lionel
• Re: I think the standard will be on my side (BOZ)
  • From: Ken . Fairfield
• Re: Derived types and allocatable
  • From: James Van Buskirk
• Re: I think the standard will be on my side (BOZ)
  • From: Ken . Fairfield
• Re: Array sections and F90/95 Standard
  • From: James Van Buskirk
• Re: Recursive function (with allocatable inside)
  • From: relaxmike
• Re: How to determine whether or not there exists a directory
  • From: David Jones
• Re: Recursive function (with allocatable inside)
  • From: James Van Buskirk
• Re: advance=no problem
  • From: GaryScott
• Re: advance=no problem
  • From: Ron Shepard
• Re: Recursive function (with allocatable inside)
  • From: Richard Maine
• Re: advance=no problem
  • From: Richard Maine
• Re: How to determine whether or not there exists a directory
  • From: ziven
• Re: advance=no problem
  • From: GaryScott
• Re: advance=no problem
  • From: Steve Lionel
• Re: Array sections and F90/95 Standard
  • From: Herman D . Knoble
• Re: Recursive function (with allocatable inside)
  • From: relaxmike
• Re: Array sections and F90/95 Standard
  • From: Michael Metcalf
• Re: Array sections and F90/95 Standard
  • From: Herman D . Knoble
• Sorting arrays
  • From: tomguest
• Re: Array sections and F90/95 Standard
  • From: Michael Metcalf
• Re: weird g77 and gfortran
  • From: Ingo Thies
• Re: Recursive function (with allocatable inside)
  • From: Michael Metcalf
• Array sections and F90/95 Standard
  • From: Herman D . Knoble
• Re: Recursive function (with allocatable inside)
  • From: relaxmike
• Re: Recursive function (with allocatable inside)
  • From: Michael Metcalf
• Re: How to distinguish between numerical data and alphanumeric title
  • From: bru
• Recursive function (with allocatable inside)
  • From: relaxmike
• Re: Derived types and allocatable
  • From: Jan Vorbrüggen
• Re: How to determine whether or not there exists a directory
  • From: relaxmike
• Re: How to determine whether or not there exists a directory
  • From: Catherine Rees Lay
• Re: advance=no problem
  • From: robert . corbett
• Re: advance=no problem
  • From: Jugoslav Dujic
• Re: advance=no problem
  • From: robert . corbett
• Re: How to distinguish between numerical data and alphanumeric title
  • From: Arjen Markus
• Re: Bitwise logical functions in gfortran
  • From: James Van Buskirk
• Re: advance=no problem
  • From: Richard Maine
• Re: advance=no problem
  • From: robert . corbett
• Re: advance=no problem
  • From: James Giles
• Re: How to determine whether or not there exists a directory
  • From: Ron Ford
• Re: advance=no problem
  • From: Richard Maine
• Re: How to determine whether or not there exists a directory
  • From: ziven
• Re: advance=no problem
  • From: James Giles
• Re: I think the standard will be on my side (BOZ)
  • From: James Giles
• Re: advance=no problem
  • From: James Giles
• Re: GFortran - OpenMP problem with Windows XP memory
  • From: Anony
• Re: How to distinguish between numerical data and alphanumeric title
  • From: glen herrmannsfeldt
• Re: How to determine whether or not there exists a directory
  • From: glen herrmannsfeldt
• Re: Bitwise logical functions in gfortran
  • From: glen herrmannsfeldt
• Re: Bitwise logical functions in gfortran
  • From: Steven G. Kargl
• Re: advance=no problem
  • From: robert . corbett
• Re: GFortran - OpenMP problem with Windows XP memory
  • From: Steven G. Kargl
• Re: I think the standard will be on my side (BOZ)
  • From: glen herrmannsfeldt
• Re: GFortran - OpenMP problem with Windows XP memory
  • From: glen herrmannsfeldt
• Re: GFortran - OpenMP problem with Windows XP memory
  • From: Anony
• Re: Bitwise logical functions in gfortran
  • From: Steven G. Kargl
• Re: How to determine whether or not there exists a directory
  • From: Terence
• Re: ISO 10646 support
  • From: Ron Ford
• Re: Bitwise logical functions in gfortran
  • From: Terence
• Re: How to determine whether or not there exists a directory
  • From: Ron Ford
• Re: How to distinguish between numerical data and alphanumeric title
  • From: e p chandler
• Bitwise logical functions in gfortran
  • From: James Van Buskirk
• Re: advance=no problem
  • From: James Giles
• Re: advance=no problem
  • From: robert . corbett
• Re: GFortran - OpenMP problem with Windows XP memory
  • From: Steven G. Kargl
• Re: GFortran - OpenMP problem with Windows XP memory
  • From: Anony
• Re: I think the standard will be on my side (BOZ)
  • From: James Giles
• Re: How to distinguish between numerical data and alphanumeric title
  • From: glen herrmannsfeldt
• Re: How to distinguish between numerical data and alphanumeric title
  • From: John Harper
• Re: I think the standard will be on my side (BOZ)
  • From: glen herrmannsfeldt
• Re: GFortran - OpenMP problem with Windows XP memory
  • From: Greg Lindahl
• Re: I think the standard will be on my side (BOZ)
  • From: James Giles
• Re: GFortran - OpenMP problem with Windows XP memory
  • From: glen herrmannsfeldt
• Re: GFortran - OpenMP problem with Windows XP memory
  • From: Anony
• GFortran - OpenMP problem with Windows XP memory
  • From: Cirilo S. Bresolin
• Re: I think the standard will be on my side (BOZ)
  • From: glen herrmannsfeldt
• Re: How to distinguish between numerical data and alphanumeric title
  • From: Arjen Markus
• Re: weird g77 and gfortran
  • From: Greg Lindahl
• Re: I think the standard will be on my side (BOZ)
  • From: James Giles
• Re: weird g77 and gfortran
  • From: Thomas Koenig
• Re: How to distinguish between numerical data and alphanumeric title
  • From: glen herrmannsfeldt
• Re: MPI code error raises a question
  • From: Herman D . Knoble
• Re: advance=no problem
  • From: GaryScott
• Re: advance=no problem
  • From: Richard Maine
• Re: weird g77 and gfortran
  • From: Steven G. Kargl
• Re: How to determine whether or not there exists a directory
  • From: Reinhold Bader
• Re: How to determine whether or not there exists a directory
  • From: Arjen Markus
• Re: advance=no problem
  • From: GaryScott
• Re: weird g77 and gfortran
  • From: Ingo Thies
• Re: How to distinguish between numerical data and alphanumeric title
  • From: GaryScott
• Re: How to distinguish between numerical data and alphanumeric title
  • From: bru
• Re: How to determine whether or not there exists a directory
  • From: Steve Lionel
• Re: weird g77 and gfortran
  • From: stevenb . gcc
• Re: How to distinguish between numerical data and alphanumeric title
  • From: Arjen Markus
• Re: weird g77 and gfortran
  • From: Ingo Thies
• Re: How to distinguish between numerical data and alphanumeric title
  • From: glen herrmannsfeldt
• Re: I think the standard will be on my side (BOZ)
  • From: glen herrmannsfeldt
• Re: How to distinguish between numerical data and alphanumeric title
  • From: Terence
• Re: How to determine whether or not there exists a directory
  • From: Terence
• How to determine whether or not there exists a directory
  • From: ziven
• Re: How to distinguish between numerical data and alphanumeric title
  • From: e p chandler
• How to distinguish between numerical data and alphanumeric title
  • From: bru
• Re: advance=no problem
  • From: robert . corbett
• Re: MPI code error raises a question
  • From: Gib Bogle
• Re: I think the standard will be on my side (BOZ)
  • From: glen herrmannsfeldt
• Re: advance=no problem
  • From: John Harper
• Re: advance=no problem
  • From: glen herrmannsfeldt
• Re: advance=no problem
  • From: Richard Maine
• Re: compiler problem
  • From: Greg Lindahl
• Re: compiler problem
  • From: Michael Metcalf
• Re: advance=no problem
  • From: Janne Blomqvist
• Re: compiler problem
  • From: Craig Powers
• Re: compiler problem
  • From: glen herrmannsfeldt
• Re: advance=no problem
  • From: glen herrmannsfeldt
• Re: advance=no problem
  • From: Janne Blomqvist
• Re: advance=no problem
  • From: James Giles
• Re: advance=no problem
  • From: tholen
• Re: compiler problem
  • From: Michael Metcalf
• Re: advance=no problem
  • From: glen herrmannsfeldt
• Re: advance=no problem
  • From: tholen
• Re: compiler problem
  • From: glen herrmannsfeldt
• Re: Identifier name length in g77
  • From: Greg Lindahl
• Re: compiler problem
  • From: Steven G. Kargl
• Re: compiler problem
  • From: Craig Powers
• Re: derived type as argument
  • From: GeoGarfield
• Re: Subroutine header
  • From: Mark Westwood
• Re: Identifier name length in g77
  • From: Dick Hendrickson
• Re: advance=no problem
  • From: Gordon Sande
• Re: advance=no problem
  • From: rudra
• advance=no problem
  • From: rudra
• Re: Identifier name length in g77
  • From: Dr Ivan D. Reid
• Identifier name length in g77
  • From: Łukasz
• Re: CMPLX and constant folding
  • From: James Van Buskirk
• Re: Subroutine header
  • From: e p chandler
• Re: CMPLX and constant folding
  • From: Richard Maine
• Re: derived type as argument
  • From: Ron Shepard
• Re: CMPLX and constant folding
  • From: John Harper
• Re: I think the standard will be on my side (BOZ)
  • From: Terence
• Re: I think the standard will be on my side (BOZ)
  • From: John Harper
• Subroutine header
  • From: Stefan
• Re: Perverse G77 syntax extension
  • From: John Harper
• ISO_C_BINDING and BLAS/LAPACK
  • From: Jason Nielsen
• Re: derived type as argument
  • From: Richard Maine
• ISO 10646 support
  • From: FX
• Re: derived type as argument
  • From: Tim Prince
• Re: ranlux
  • From: Phillip Helbig---remove CLOTHES to reply
• derived type as argument
  • From: GeoGarfield
• Re: CMPLX and constant folding
  • From: FX
• Re: I think the standard will be on my side (BOZ)
  • From: James Giles
• Re: I think the standard will be on my side (BOZ)
  • From: Richard Maine
• Re: I think the standard will be on my side (BOZ)
  • From: James Giles
• Re: I think the standard will be on my side (BOZ)
  • From: Gary Scott
• Re: I think the standard will be on my side (BOZ)
  • From: glen herrmannsfeldt
• Re: I think the standard will be on my side (BOZ)
  • From: Steven G. Kargl
• Re: I think the standard will be on my side (BOZ)
  • From: glen herrmannsfeldt
• Re: I think the standard will be on my side (BOZ)
  • From: glen herrmannsfeldt
• Re: I think the standard will be on my side (BOZ)
  • From: James Van Buskirk
• Re: I think the standard will be on my side (BOZ)
  • From: glen herrmannsfeldt
• Re: I think the standard will be on my side (BOZ)
  • From: James Giles
• Re: compiler problem
  • From: rudra
• Re: I think the standard will be on my side (BOZ)
  • From: Steven G. Kargl
• Re: I think the standard w