comp.lang.fortran

• Date Index

---

• Module compile order, Thomas Robitaille
  • Re: Module compile order, Richard Maine
    • Re: Module compile order, Thomas Robitaille
  • Re: Module compile order, James Giles
• NYT disses Fortran, Greg Lindahl
  • Re: NYT disses Fortran, Michael Metcalf
• optional or interface, Mike
  • Re: optional or interface, Arjen Markus
• optional assumed-shape array, Mike
  • Re: optional assumed-shape array, Richard Maine
• format with G descriptor, Roman
  • Re: format with G descriptor, James Giles
    • Re: format with G descriptor, James Giles
  • Re: format with G descriptor, Kurt Kallblad
    • Re: format with G descriptor, Roman
      • Re: format with G descriptor, glen herrmannsfeldt
• Problem with file writing, Philippe
  • Re: Problem with file writing, e p chandler
  • Re: Problem with file writing, Steven G. Kargl
  • Re: Problem with file writing, Craig Powers
• warning on running image !!!!!, nakisa
  • Re: warning on running image !!!!!, Steve Lionel
    • Re: warning on running image !!!!!, nakisa
      • Re: warning on running image !!!!!, Steve Lionel
• Arrays Intersection, Infinity77
  • Re: Arrays Intersection, Arjen Markus
    • Re: Arrays Intersection, Gordon Sande
      • Re: Arrays Intersection, Arjen Markus
      • Re: Arrays Intersection, Gordon Sande
      • Re: Arrays Intersection, Arjen Markus
      • Re: Arrays Intersection, Paul van Delst
      • Re: Arrays Intersection, Arjen Markus
  • Re: Arrays Intersection, glen herrmannsfeldt
• .true. help, rudra
  • Re: .true. help, Alois Steindl
    • Re: .true. help, rudra
      • Re: .true. help, rudra
    • Re: .true. help, e p chandler
  • Re: .true. help, Arjen Markus
  • Re: .true. help, Mike
• CPAN equivalent for fortran?, Thomas Robitaille
  • Re: CPAN equivalent for fortran?, Ron Ford
• public/private and overloaded operator, mrestelli@xxxxxxxxx
  • Re: public/private and overloaded operator, Richard Maine
    • Re: public/private and overloaded operator, Steve Lionel
• Is this legal?, Salvatore
  • Re: Is this legal?, Salvatore
    • Re: Is this legal?, Richard Maine
    • Re: Is this legal?, robert . corbett
      • Re: Is this legal?, Salvatore
      • Re: Is this legal?, Craig Powers
      • Re: Is this legal?, Salvatore
• Fortran 77 alphabet character $, Herman D . Knoble
  • Re: Fortran 77 alphabet character $, Arjen Markus
    • Re: Fortran 77 alphabet character $, Herman D . Knoble
    • Re: Fortran 77 alphabet character $, glen herrmannsfeldt
      • Re: Fortran 77 alphabet character $, GaryScott
  • Re: Fortran 77 alphabet character $, Richard Maine
    • Re: Fortran 77 alphabet character $, John Harper
      • Re: Fortran 77 alphabet character $, e p chandler
      • Re: Fortran 77 alphabet character $, Terence
      • Re: Fortran 77 alphabet character $, Gary Scott
      • Re: Fortran 77 alphabet character $, Terence
  • Re: Fortran 77 alphabet character $, mecej4
    • Re: Fortran 77 alphabet character $, Herman D . Knoble
      • Re: Fortran 77 alphabet character $, Ian Gay
      • Re: Fortran 77 alphabet character $, user1
  • Re: Fortran 77 alphabet character $, e p chandler
    • Re: Fortran 77 alphabet character $, GaryScott
• Interfacing between Fortran and C - a little utility, Arjen Markus
  • Re: Interfacing between Fortran and C - a little utility, rudra
    • Re: Interfacing between Fortran and C - a little utility, Arjen Markus
• 1.0d0 stored as integer?, David Gunter
  • Re: 1.0d0 stored as integer?, Richard Maine
  • Re: 1.0d0 stored as integer?, glen herrmannsfeldt
    • Re: 1.0d0 stored as integer?, FX
• Slick or Slack, Bil Kleb
  • Re: Slick or Slack, Damian
    • Re: Slick or Slack, e p chandler
      • Re: Slick or Slack, Bil
    • Re: Slick or Slack, Bil
• HPC Considered Harmful, Bil Kleb
  • Re: HPC Considered Harmful, e p chandler
• Gfortran 4.4 binary (OpenMP and 64bit capability) for PPC Tiger, Al Greynolds
  • Re: Gfortran 4.4 binary (OpenMP and 64bit capability) for PPC Tiger, FX
    • Re: Gfortran 4.4 binary (OpenMP and 64bit capability) for PPC Tiger, Al Greynolds
• problem with very small numbers - g95 versus gfortran, e p chandler
  • Re: problem with very small numbers - g95 versus gfortran, James Van Buskirk
    • Re: problem with very small numbers - g95 versus gfortran, James Van Buskirk
      • Re: problem with very small numbers - g95 versus gfortran, e p chandler
      • Re: problem with very small numbers - g95 versus gfortran, James Van Buskirk
      • Re: problem with very small numbers - g95 versus gfortran, e p chandler
      • Re: problem with very small numbers - g95 versus gfortran, James Van Buskirk
      • Re: problem with very small numbers - g95 versus gfortran, Steven G. Kargl
      • Re: problem with very small numbers - g95 versus gfortran, James Van Buskirk
    • Re: problem with very small numbers - g95 versus gfortran, e p chandler
      • Re: problem with very small numbers - g95 versus gfortran, James Van Buskirk
      • Re: problem with very small numbers - g95 versus gfortran, e p chandler
      • Re: problem with very small numbers - g95 versus gfortran, James Van Buskirk
• Foray Build Tool Project Started, drewmccormack
• How to do AINS() and ADEL(), axtens
  • Re: How to do AINS() and ADEL(), Arjen Markus
    • Re: How to do AINS() and ADEL(), axtens
    • Re: How to do AINS() and ADEL(), Gordon Sande
  • Re: How to do AINS() and ADEL(), David Frank
    • Re: How to do AINS() and ADEL(), Steve Lionel
• Validation?, Terence
  • Re: Validation?, e p chandler
    • Re: Validation?, e p chandler
• HDF read example, clay . blankenship
  • Re: HDF read example, fj
    • Re: HDF read example, Paul van Delst
  • Re: HDF read example, Hajo Klingshirn
    • RE: HDF read example, meek
• Error compiling example program with gfortran using lapack95 on win32, Harald Breitkreutz
  • Re: Error compiling example program with gfortran using lapack95 on win32, Richard Maine
• Unsigned in CVF, axtens
  • Re: Unsigned in CVF, Jugoslav Dujic
    • Re: Unsigned in CVF, robert . corbett
      • Re: Unsigned in CVF, Terence
      • Re: Unsigned in CVF, glen herrmannsfeldt
  • Re: Unsigned in CVF, Arjen Markus
    • Re: Unsigned in CVF, axtens
      • Re: Unsigned in CVF, axtens
• Fortran algorithms to look for a maximum over an array of real numbers, octaedro
  • Re: Fortran algorithms to look for a maximum over an array of real numbers, robert . corbett
  • Re: Fortran algorithms to look for a maximum over an array of real numbers, Tim Prince
• GNU gfortran on Mac OSX, breyfogle
  • Re: GNU gfortran on Mac OSX, dominiq
    • Re: GNU gfortran on Mac OSX, breyfogle
      • Re: GNU gfortran on Mac OSX, dominiq
      • Re: GNU gfortran on Mac OSX, breyfogle
  • Re: GNU gfortran on Mac OSX, FX
    • Re: GNU gfortran on Mac OSX, dominiq
• RtlMoveMemory not being found to link in, axtens
  • Re: RtlMoveMemory not being found to link in, axtens
  • Re: RtlMoveMemory not being found to link in, Steve Lionel
    • Re: RtlMoveMemory not being found to link in, axtens
    • Re: RtlMoveMemory not being found to link in, axtens
      • Re: RtlMoveMemory not being found to link in, Jugoslav Dujic
      • Re: RtlMoveMemory not being found to link in, axtens
  • Re: RtlMoveMemory not being found to link in, Jugoslav Dujic
    • Re: RtlMoveMemory not being found to link in, Steve Lionel
    • Re: RtlMoveMemory not being found to link in, Craig Powers
      • Re: RtlMoveMemory not being found to link in, axtens
      • Re: RtlMoveMemory not being found to link in, Jugoslav Dujic
      • Re: RtlMoveMemory not being found to link in, axtens
• newbie: that mapping CHARACTER*2 to INTEGER*2 question, axtens
  • Re: newbie: that mapping CHARACTER*2 to INTEGER*2 question, axtens
    • Re: newbie: that mapping CHARACTER*2 to INTEGER*2 question, Arjen Markus
    • Re: newbie: that mapping CHARACTER*2 to INTEGER*2 question, Steve Lionel
• Garbage in dead zone, James Van Buskirk
  • Re: Garbage in dead zone, Richard Maine
    • Re: Garbage in dead zone, glen herrmannsfeldt
      • Re: Garbage in dead zone, e p chandler
    • Re: Garbage in dead zone, Steve Lionel
  • Re: Garbage in dead zone, Charles Coldwell
    • Re: Garbage in dead zone, James Van Buskirk
• Fortran 2003 questions, jaydub66@xxxxxxxxx
  • Re: Fortran 2003 questions, Tobias Burnus
    • Re: Fortran 2003 questions, James Van Buskirk
    • Re: Fortran 2003 questions, Richard Maine
  • Re: Fortran 2003 questions, Richard Maine
    • Re: Fortran 2003 questions, Tobias Burnus
• about recursion function., alex
  • Re: about recursion function., Mark Westwood
  • Re: about recursion function., Paul van Delst
  • Re: about recursion function., Richard Maine
• allocatable array component with intent(out), Ron Shepard
  • Re: allocatable array component with intent(out), Jugoslav Dujic
    • Fix: allocatable array component with intent(out), Jugoslav Dujic
    • Re: allocatable array component with intent(out), Jugoslav Dujic
      • Re: allocatable array component with intent(out), Steve Lionel
  • Re: allocatable array component with intent(out), mecej4
  • Re: allocatable array component with intent(out), glen herrmannsfeldt
    • Re: allocatable array component with intent(out), Michael Metcalf
    • Re: allocatable array component with intent(out), Ron Shepard
• Array Filtering, Infinity77
  • Re: Array Filtering, Arjen Markus
    • Re: Array Filtering, Ken . Fairfield
      • Re: Array Filtering, glen herrmannsfeldt
      • Re: Array Filtering, Infinity77
  • Re: Array Filtering, alex
    • Re: Array Filtering, alex
  • Re: Array Filtering, Daniel Franke
  • Re: Array Filtering, Michael Metcalf
    • Re: Array Filtering, Infinity77
      • Re: Array Filtering, Mark Westwood
      • Re: Array Filtering, Infinity77
  • Re: Array Filtering, James Van Buskirk
  • Re: Array Filtering, Ken . Fairfield
    • Re: Array Filtering, glen herrmannsfeldt
• transfer filename to subroutine, rudra
  • Re: transfer filename to subroutine, Richard Maine
    • Re: transfer filename to subroutine, rudra
    • Re: transfer filename to subroutine, rudra
      • Re: transfer filename to subroutine, Steven G. Kargl
    • Re: transfer filename to subroutine, e p chandler
      • Re: transfer filename to subroutine, Richard Maine
  • Re: transfer filename to subroutine, glen herrmannsfeldt
• Requirements for FINAL procedures, Daniel Kraft
  • Re: Requirements for FINAL procedures, Richard Maine
    • Re: Requirements for FINAL procedures, Daniel Kraft
• Question about passing arrays to subroutines, Lorents
  • Re: Question about passing arrays to subroutines, Paul van Delst
  • Re: Question about passing arrays to subroutines, Richard Maine
    • Re: Question about passing arrays to subroutines, Lorents
• Reinitialising random number generator, Arjen Markus
  • Re: Reinitialising random number generator, Thomas Koenig
    • Re: Reinitialising random number generator, Arjen Markus
      • Re: Reinitialising random number generator, Thomas Koenig
      • Re: Reinitialising random number generator, Arjen Markus
      • Re: Reinitialising random number generator, Dave Seaman
      • Re: Reinitialising random number generator, Arjen Markus
      • Re: Reinitialising random number generator, Dave Seaman
      • Re: Reinitialising random number generator, Arjen Markus
      • Re: Reinitialising random number generator, FX
      • Re: Reinitialising random number generator, Thomas Koenig
      • Re: Reinitialising random number generator, Thomas Koenig
      • Re: Reinitialising random number generator, Arjen Markus
      • Re: Reinitialising random number generator, robin
      • Re: Reinitialising random number generator, Thomas Koenig
    • Re: Reinitialising random number generator, Richard Maine
      • Re: Reinitialising random number generator, Thomas Koenig
      • Re: Reinitialising random number generator, Richard Maine
• Fortran 90 Chess, dean . menezes
  • Re: Fortran 90 Chess, e p chandler
    • Re: Fortran 90 Chess, Phillip Helbig---remove CLOTHES to reply
  • Re: Fortran 90 Chess, Beliavsky
    • Re: Fortran 90 Chess, dean . menezes
  • Re: Fortran 90 Chess, robin
    • Re: Fortran 90 Chess, Dean Menezes
      • Re: Fortran 90 Chess, robin
      • Re: Fortran 90 Chess, dean . menezes
      • Re: Fortran 90 Chess, samanddeanus
      • Re: Fortran 90 Chess, John
      • Re: Fortran 90 Chess, John Harper
      • Re: Fortran 90 Chess, dean . menezes
      • Re: Fortran 90 Chess, robin
      • Re: Fortran 90 Chess, fj
      • Re: Fortran 90 Chess, dean . menezes
      • Re: Fortran 90 Chess, robin
• Copying data between pointers, Gib Bogle
  • Re: Copying data between pointers, Richard Maine
    • Re: Copying data between pointers, Gib Bogle
      • Re: Copying data between pointers, glen herrmannsfeldt
      • Re: Copying data between pointers, Gib Bogle
      • Re: Copying data between pointers, glen herrmannsfeldt
      • Re: Copying data between pointers, Richard Maine
      • Re: Copying data between pointers, Gib Bogle
      • Re: Copying data between pointers, Paul van Delst
      • Re: Copying data between pointers, Gib Bogle
      • Re: Copying data between pointers, Paul van Delst
  • Re: Copying data between pointers, glen herrmannsfeldt
    • Re: Copying data between pointers, Gib Bogle
• Writing nul characters, f90 formatted output, posol
  • Re: Writing nul characters, f90 formatted output, Michael Metcalf
    • Re: Writing nul characters, f90 formatted output, posol
  • Re: Writing nul characters, f90 formatted output, James Van Buskirk
    • Re: Writing nul characters, f90 formatted output, posol
  • Re: Writing nul characters, f90 formatted output, robert . corbett
• maximum open files and unit numbers, Glenn Forney
  • Re: maximum open files and unit numbers, Paul van Delst
  • Re: maximum open files and unit numbers, Catherine Rees Lay
    • Re: maximum open files and unit numbers, James Giles
      • Re: maximum open files and unit numbers, James Giles
      • Re: maximum open files and unit numbers, James Giles
      • Re: maximum open files and unit numbers, relaxmike
      • Re: maximum open files and unit numbers, Paul van Delst
• newbie: mapping CHARACTER*2 to INTEGER*2, axtens
  • RE: newbie: mapping CHARACTER*2 to INTEGER*2, meek
    • Re: newbie: mapping CHARACTER*2 to INTEGER*2, paul . richard . thomas
      • Re: newbie: mapping CHARACTER*2 to INTEGER*2, glen herrmannsfeldt
  • Re: newbie: mapping CHARACTER*2 to INTEGER*2, James Van Buskirk
    • Re: newbie: mapping CHARACTER*2 to INTEGER*2, axtens
• public comments, Dan Nagle
  • Re: public comments, Craig Powers
    • Re: public comments, Dan Nagle
      • Re: public comments, Greg Lindahl
      • Re: public comments, Dan Nagle
• Using external subroutines in OpenMP: Update, jomarbueyes
  • Re: Using external subroutines in OpenMP: Update, Ron Ford
    • Re: Using external subroutines in OpenMP: Update, jomarbueyes
• Fortran 2003 : no OO constructor ?, relaxmike
  • Re: Fortran 2003 : no OO constructor ?, Richard Maine
    • Re: Fortran 2003 : no OO constructor ?, glen herrmannsfeldt
      • Re: Fortran 2003 : no OO constructor ?, Jan Vorbrüggen
      • Re: Fortran 2003 : no OO constructor ?, Ron Ford
    • Re: Fortran 2003 : no OO constructor ?, John Harper
• Binding name, James Van Buskirk
  • Re: Binding name, FX
    • Re: Binding name, James Van Buskirk
      • Re: Binding name, Steve Lionel
  • Re: Binding name, FX
    • Re: Binding name, James Van Buskirk
      • Re: Binding name, FX
      • Re: Binding name, James Van Buskirk
      • Re: Binding name, Richard Maine
  • Re: Binding name, Tobias Burnus
    • Re: Binding name, James Van Buskirk
      • Re: Binding name, Tim Prince
      • Re: Binding name, FX
      • Re: Binding name, James Van Buskirk
      • Re: Binding name, FX
      • Re: Binding name, James Van Buskirk
      • Re: Binding name, FX
      • Re: Binding name, James Van Buskirk
      • Re: Binding name, FX
      • Re: Binding name, James Van Buskirk
      • Re: Binding name, James Van Buskirk
      • Re: Binding name, James Van Buskirk
      • Re: Binding name, James Van Buskirk
      • Re: Binding name, James Van Buskirk
• I need help about IF command, mah
  • Re: I need help about IF command, Arjen Markus
    • Re: I need help about IF command, glen herrmannsfeldt
      • Re: I need help about IF command, mah
  • Re: I need help about IF command, rudra
    • Re: I need help about IF command, Michael Metcalf
      • Re: I need help about IF command, mah
      • Re: I need help about IF command, rudra
• Variable size component in derived type, Gib Bogle
  • Re: Variable size component in derived type, Arjen Markus
    • Re: Variable size component in derived type, Gib Bogle
    • Re: Variable size component in derived type, Gib Bogle
    • Re: Variable size component in derived type, Gib Bogle
    • Re: Variable size component in derived type, Gib Bogle
  • Re: Variable size component in derived type, James Van Buskirk
    • Re: Variable size component in derived type, dominiq
    • Re: Variable size component in derived type, Gib Bogle
      • Re: Variable size component in derived type, Richard Maine
      • Re: Variable size component in derived type, Gib Bogle
      • Re: Variable size component in derived type, Richard Maine
    • Re: Variable size component in derived type, Gib Bogle
  • Re: Variable size component in derived type, Jim Xia
    • Re: Variable size component in derived type, Gib Bogle
• secnds, rudra
  • Re: secnds, Steven G. Kargl
  • Re: secnds, Kurt Kallblad
• encoding="utf-8" and formatted direct access, Thomas Koenig
  • Re: encoding="utf-8" and formatted direct access, Richard Maine
    • Re: encoding="utf-8" and formatted direct access, Thomas Koenig
      • Re: encoding="utf-8" and formatted direct access, Richard Maine
      • Re: encoding="utf-8" and formatted direct access, James Giles
      • Re: encoding="utf-8" and formatted direct access, glen herrmannsfeldt
      • Re: encoding="utf-8" and formatted direct access, James Giles
      • Re: encoding="utf-8" and formatted direct access, James Giles
      • Re: encoding="utf-8" and formatted direct access, glen herrmannsfeldt
      • Re: encoding="utf-8" and formatted direct access, Thomas Koenig
      • Re: encoding="utf-8" and formatted direct access, James Giles
      • Re: encoding="utf-8" and formatted direct access, James Giles
      • Re: encoding="utf-8" and formatted direct access, FX
      • Re: encoding="utf-8" and formatted direct access, James Giles
      • Re: encoding="utf-8" and formatted direct access, William Clodius
      • Re: encoding="utf-8" and formatted direct access, James Giles
      • Re: encoding="utf-8" and formatted direct access, William Clodius
      • Re: encoding="utf-8" and formatted direct access, James Giles
      • Re: encoding="utf-8" and formatted direct access, Jan Vorbrüggen
      • Re: encoding="utf-8" and formatted direct access, Richard Maine
      • Re: encoding="utf-8" and formatted direct access, William Clodius
      • Re: encoding="utf-8" and formatted direct access, Thomas Koenig
      • Re: encoding="utf-8" and formatted direct access, James Giles
      • Re: encoding="utf-8" and formatted direct access, Gary Scott
      • Re: encoding="utf-8" and formatted direct access, James Giles
      • Re: encoding="utf-8" and formatted direct access, glen herrmannsfeldt
      • Re: encoding="utf-8" and formatted direct access, Richard Maine
      • Re: encoding="utf-8" and formatted direct access, glen herrmannsfeldt
      • Re: encoding="utf-8" and formatted direct access, William Clodius
• Dynamic CHAR length?, Mark Morss
  • Re: Dynamic CHAR length?, Richard Maine
    • Re: Dynamic CHAR length?, Mark Morss
      • Re: Dynamic CHAR length?, alex
      • Re: Dynamic CHAR length?, Richard Maine
  • Re: Dynamic CHAR length?, relaxmike
    • Re: Dynamic CHAR length?, Richard Maine
      • Re: Dynamic CHAR length?, relaxmike
      • Re: Dynamic CHAR length?, Richard Maine
      • Re: Dynamic CHAR length?, relaxmike
  • Re: Dynamic CHAR length?, Jim Xia
• opening files in psuite on NEC SX8, mccabec67
• Parsing gfortran error messages in emacs, honestguvnor
  • Re: Parsing gfortran error messages in emacs, Steven G. Kargl
• one-liner for characater replacement, analyst41
  • Re: one-liner for characater replacement, Sjouke Burry
  • Re: one-liner for characater replacement, James Giles
    • Re: one-liner for characater replacement, Terence
      • Re: one-liner for characater replacement, James Giles
    • line numbers was : one-liner for characater replacement (was: one-liner for characater replacement), Ron Ford
  • Re: one-liner for characater replacement, David Frank
    • Re: one-liner for characater replacement, utab
      • Re: one-liner for characater replacement, David Frank
  • Re: one-liner for characater replacement, Walter Spector
    • Re: one-liner for characater replacement, analyst41
      • Re: one-liner for characater replacement, James Giles
      • Re: one-liner for characater replacement, analyst41
      • Re: one-liner for characater replacement, James Giles
      • Re: one-liner for characater replacement, Jan Vorbrüggen
      • Re: one-liner for characater replacement, analyst41
      • Re: one-liner for characater replacement, James Van Buskirk
      • Re: one-liner for characater replacement, analyst41
      • Re: one-liner for characater replacement, James Van Buskirk
      • Re: one-liner for characater replacement, analyst41
      • Re: one-liner for characater replacement, glen herrmannsfeldt
      • Re: one-liner for characater replacement, analyst41
      • Re: one-liner for characater replacement, Gary Scott
      • Re: one-liner for characater replacement, James Giles
      • Re: one-liner for characater replacement, Gary Scott
      • Re: one-liner for characater replacement, James Giles
      • Re: one-liner for characater replacement, Gary Scott
      • Re: one-liner for characater replacement, Ron Ford
      • Re: one-liner for characater replacement, James Giles
      • Re: one-liner for characater replacement, analyst41
      • Re: one-liner for characater replacement, James Giles
      • Re: one-liner for characater replacement, analyst41
      • Re: one-liner for characater replacement, Gary Scott
      • Re: one-liner for characater replacement, James Giles
      • Re: one-liner for characater replacement, analyst41
      • Re: one-liner for characater replacement, James Giles
      • Re: one-liner for characater replacement, dpb
      • Re: one-liner for characater replacement, James Giles
      • Re: one-liner for characater replacement, analyst41
      • Re: one-liner for characater replacement, James Giles
      • Re: one-liner for characater replacement, dpb
      • Re: one-liner for characater replacement, analyst41
      • Re: one-liner for characater replacement, James Giles
      • Re: one-liner for characater replacement, analyst41
      • Re: one-liner for characater replacement, James Giles
      • Re: one-liner for characater replacement, analyst41
      • Re: one-liner for characater replacement, Gary Scott
      • Re: one-liner for characater replacement, James Giles
      • Re: one-liner for characater replacement, analyst41
      • Re: one-liner for characater replacement, FX
      • Re: one-liner for characater replacement, analyst41
      • Re: one-liner for characater replacement, Tom Micevski
      • Message not available
      • Re: one-liner for characater replacement, dpb
      • Re: one-liner for characater replacement, GaryScott
      • Re: one-liner for characater replacement, James Giles
      • Re: one-liner for characater replacement, analyst41
      • Re: one-liner for characater replacement, James Giles
      • Re: one-liner for characater replacement, analyst41
      • Re: one-liner for characater replacement, dpb
      • Re: one-liner for characater replacement, James Giles
      • Re: one-liner for characater replacement, dpb
      • Re: one-liner for characater replacement, Jan Vorbrüggen
      • Re: one-liner for characater replacement, analyst41
      • Re: one-liner for characater replacement, Jan Vorbrüggen
      • Re: one-liner for characater replacement, dpb
      • Re: one-liner for characater replacement, dpb
      • Re: one-liner for characater replacement, Gary Scott
      • Re: one-liner for characater replacement, analyst41
      • Re: one-liner for characater replacement, dpb
      • Re: one-liner for characater replacement, James Giles
      • Re: one-liner for characater replacement, dpb
      • Re: one-liner for characater replacement, glen herrmannsfeldt
      • Re: one-liner for characater replacement, James Giles
      • Re: one-liner for characater replacement, glen herrmannsfeldt
      • Re: one-liner for characater replacement, James Giles
      • Re: one-liner for characater replacement, glen herrmannsfeldt
      • Re: one-liner for characater replacement, glen herrmannsfeldt
      • Re: one-liner for characater replacement, James Giles
      • Re: one-liner for characater replacement, Richard Maine
      • Re: one-liner for characater replacement, James Giles
      • Re: one-liner for characater replacement, glen herrmannsfeldt
      • Re: one-liner for characater replacement, James Giles
      • Re: one-liner for characater replacement, glen herrmannsfeldt
      • Re: one-liner for characater replacement, James Giles
  • Re: one-liner for characater replacement, rudra
    • Re: one-liner for characater replacement, Steven G. Kargl
• Creating .so file to call from IDL, Sid
  • Re: Creating .so file to call from IDL, Jean H
    • Re: Creating .so file to call from IDL, Tobias Burnus
• DPROD issues, James Van Buskirk
  • Re: DPROD issues, Richard Maine
    • Re: DPROD issues, James Van Buskirk
• Yay!, Bamm
  • Re: Yay!, user1
    • Re: Yay!, Bamm
      • Re: Yay!, Terence
  • Re: Yay!, e p chandler
    • Re: Yay!, Bamm
• Ifort long compilation time, braams@xxxxxxxxxxxxxxxx
  • Re: Ifort long compilation time, Steve Lionel
  • Re: Ifort long compilation time, mecej4
    • Re: Ifort long compilation time, Tim Prince
      • Re: Ifort long compilation time, mecej4
      • Re: Ifort long compilation time, Richard Maine
      • Re: Ifort long compilation time, Tim Prince
      • Re: Ifort long compilation time, Terence
      • Re: Ifort long compilation time, Greg Lindahl
      • Re: Ifort long compilation time, glen herrmannsfeldt
      • Re: Ifort long compilation time, Richard Maine
• file copy routine, John
  • Re: file copy routine, Richard Maine
    • Re: file copy routine, Tim Prince
    • Re: file copy routine, John
      • Re: file copy routine, Richard Maine
      • Re: file copy routine, James Giles
      • Re: file copy routine, Richard Maine
      • Re: file copy routine, James Giles
      • Re: file copy routine, James Giles
      • Re: file copy routine, andrej . panjkov
      • Re: file copy routine, James Giles
      • Re: file copy routine, andrej . panjkov
      • Re: file copy routine, James Giles
      • Re: file copy routine, andrej . panjkov
      • Re: file copy routine, Paul van Delst
      • Re: file copy routine, GaryScott
      • Re: file copy routine, James Giles
      • Re: file copy routine, GaryScott
      • Re: file copy routine, James Giles
      • Re: file copy routine, GaryScott
      • Re: file copy routine, James Giles
      • Re: file copy routine, GaryScott
      • Re: file copy routine, glen herrmannsfeldt
      • Re: file copy routine, James Giles
      • Re: file copy routine, glen herrmannsfeldt
      • Re: file copy routine, Gary Scott
      • Re: file copy routine, Terence
  • Re: file copy routine, John
    • Re: file copy routine, David Frank
      • Re: file copy routine, John
      • Re: file copy routine, David Frank
      • Re: file copy routine, GaryScott
      • Re: file copy routine, John
      • Re: file copy routine, James Van Buskirk
      • Re: file copy routine, John
      • Re: file copy routine, James Van Buskirk
    • Re: file copy routine, Les
      • Re: file copy routine, James Giles
      • Re: file copy routine, John
• g95 writes 0.232699336-309 instead of 0.000000000E+00, louisJ
  • Re: g95 writes 0.232699336-309 instead of 0.000000000E+00, Michael Metcalf
    • Re: g95 writes 0.232699336-309 instead of 0.000000000E+00, louisJ
      • Re: g95 writes 0.232699336-309 instead of 0.000000000E+00, Michael Metcalf
  • Re: g95 writes 0.232699336-309 instead of 0.000000000E+00, Dick Hendrickson
    • Re: g95 writes 0.232699336-309 instead of 0.000000000E+00, Richard Maine
    • Re: g95 writes 0.232699336-309 instead of 0.000000000E+00, louisJ
      • Re: g95 writes 0.232699336-309 instead of 0.000000000E+00, Alois Steindl
      • Re: g95 writes 0.232699336-309 instead of 0.000000000E+00, Alois Steindl
      • Re: g95 writes 0.232699336-309 instead of 0.000000000E+00, Herman D . Knoble
      • Re: g95 writes 0.232699336-309 instead of 0.000000000E+00, Gib Bogle
      • Re: g95 writes 0.232699336-309 instead of 0.000000000E+00, Michael Metcalf
      • Re: g95 writes 0.232699336-309 instead of 0.000000000E+00, louisJ
      • Re: g95 writes 0.232699336-309 instead of 0.000000000E+00, Alois Steindl
      • Re: g95 writes 0.232699336-309 instead of 0.000000000E+00, Ron Ford
      • Re: g95 writes 0.232699336-309 instead of 0.000000000E+00, Steven G. Kargl
      • Re: g95 writes 0.232699336-309 instead of 0.000000000E+00, Richard Maine
  • Re: g95 writes 0.232699336-309 instead of 0.000000000E+00, glen herrmannsfeldt
    • Re: g95 writes 0.232699336-309 instead of 0.000000000E+00, e p chandler
• Bad start on complex tests, James Van Buskirk
  • Re: Bad start on complex tests, Steven G. Kargl
    • Re: Bad start on complex tests, Anony
      • Re: Bad start on complex tests, Anony
      • Re: Bad start on complex tests, Steven G. Kargl
      • Re: Bad start on complex tests, FX
      • Re: Bad start on complex tests, Anony
      • Re: Bad start on complex tests, James Van Buskirk
      • Re: Bad start on complex tests, Anony
      • Re: Bad start on complex tests, Steven G. Kargl
      • Re: Bad start on complex tests, Anony
      • Re: Bad start on complex tests, Steven G. Kargl
      • Re: Bad start on complex tests, Anony
      • Re: Bad start on complex tests, Tim Prince
      • Re: Bad start on complex tests, FX
      • Re: Bad start on complex tests, James Van Buskirk
      • Re: Bad start on complex tests, James Van Buskirk
• KIND optional argument in transformational intrinsics, James Van Buskirk
  • Re: KIND optional argument in transformational intrinsics, FX
  • Re: KIND optional argument in transformational intrinsics, James Giles
    • Re: KIND optional argument in transformational intrinsics, James Van Buskirk
      • Re: KIND optional argument in transformational intrinsics, Thomas Koenig
      • Re: KIND optional argument in transformational intrinsics, James Van Buskirk
      • Re: KIND optional argument in transformational intrinsics, James Van Buskirk
      • Re: KIND optional argument in transformational intrinsics, James Giles
      • Re: KIND optional argument in transformational intrinsics, James Van Buskirk
      • Re: KIND optional argument in transformational intrinsics, James Giles
      • Re: KIND optional argument in transformational intrinsics, James Van Buskirk
      • Re: KIND optional argument in transformational intrinsics, James Giles
      • Re: KIND optional argument in transformational intrinsics, James Giles
      • Re: KIND optional argument in transformational intrinsics, glen herrmannsfeldt
      • Re: KIND optional argument in transformational intrinsics, Dick Hendrickson
      • Re: KIND optional argument in transformational intrinsics, James Giles
      • Re: KIND optional argument in transformational intrinsics, Dick Hendrickson
• Keyword arguments in intrinsics, James Van Buskirk
  • Re: Keyword arguments in intrinsics, Tom Micevski
    • Re: Keyword arguments in intrinsics, James Van Buskirk
      • Re: Keyword arguments in intrinsics, Steven G. Kargl
• gfortran ---problem with random umber, rudra
  • Re: gfortran ---problem with random umber, Steven G. Kargl
    • Re: gfortran ---problem with random umber, Ron Ford
      • Re: gfortran ---problem with random umber, Steven G. Kargl
      • Re: gfortran ---problem with random umber, Ron Ford
      • Re: gfortran ---problem with random umber, steven . bosscher
      • Re: gfortran ---problem with random umber, FX
      • Re: gfortran ---problem with random umber, Ron Ford
      • Re: gfortran ---problem with random umber, FX
      • Re: gfortran ---problem with random umber, Ron Ford
  • Re: gfortran ---problem with random umber, e p chandler
    • Re: gfortran ---problem with random umber, Richard Maine
      • Re: gfortran ---problem with random umber, e p chandler
      • Re: gfortran ---problem with random umber, e p chandler
      • Re: gfortran ---problem with random umber, rudra
      • Re: gfortran ---problem with random umber, Richard Maine
  • Re: gfortran ---problem with random umber, e p chandler
    • Re: gfortran ---problem with random umber, Gib Bogle
    • Re: gfortran ---problem with random umber, Thomas Koenig
  • Re: gfortran ---problem with random umber, e p chandler
• using gdb on windows, Ron Ford
  • Re: using gdb on windows, FX
    • Re: using gdb on windows, Ron Ford
      • Re: using gdb on windows, Arjan
      • Re: using gdb on windows, Ron Ford
    • Re: using gdb on windows, Ron Ford
• IBM XLFortran 8.1 on MacOSX 10.5 (Leopard), Al Greynolds
• fl32 vs df in cvf6.6, formulae translator
  • Re: fl32 vs df in cvf6.6, Michael Metcalf
    • Re: fl32 vs df in cvf6.6, Jugoslav Dujic
      • Re: fl32 vs df in cvf6.6, Michael Metcalf
      • Re: fl32 vs df in cvf6.6, formulae translator
      • Re: fl32 vs df in cvf6.6, formulae translator
      • Re: fl32 vs df in cvf6.6, Richard Maine
      • Re: fl32 vs df in cvf6.6, e p chandler
      • Re: fl32 vs df in cvf6.6, glen herrmannsfeldt
      • Re: fl32 vs df in cvf6.6, Terence
      • Re: fl32 vs df in cvf6.6, glen herrmannsfeldt
      • Re: fl32 vs df in cvf6.6, Steve Lionel
  • Re: fl32 vs df in cvf6.6, GaryScott
  • Re: fl32 vs df in cvf6.6, James Parsly
  • Re: fl32 vs df in cvf6.6, alex
    • Re: fl32 vs df in cvf6.6, Ron Ford
      • Re: fl32 vs df in cvf6.6, glen herrmannsfeldt
      • Re: fl32 vs df in cvf6.6, Richard Maine
      • Re: fl32 vs df in cvf6.6, Ron Ford
    • Re: fl32 vs df in cvf6.6, glen herrmannsfeldt
  • Re: fl32 vs df in cvf6.6, Kurt Kallblad
    • Re: fl32 vs df in cvf6.6, glen herrmannsfeldt
      • Re: fl32 vs df in cvf6.6, Gary Scott
      • Re: fl32 vs df in cvf6.6, mecej4
      • Re: fl32 vs df in cvf6.6, Gary Scott
• fl32 vs df, formulae translator
  • <Possible follow-ups>
  • fl32 vs df, formulae translator
• Pointers question, tomguest
  • Re: Pointers question, glen herrmannsfeldt
    • Re: Pointers question, tomguest
      • Re: Pointers question, Ron Ford
      • Re: Pointers question, alex
  • Re: Pointers question, Michel Olagnon
• CMPLX, REAL, and INT -- almost done, James Van Buskirk
  • Re: CMPLX, REAL, and INT -- almost done, Steven G. Kargl
    • Re: CMPLX, REAL, and INT -- almost done, James Van Buskirk
      • Re: CMPLX, REAL, and INT -- almost done, Steven G. Kargl
      • Re: CMPLX, REAL, and INT -- almost done, James Van Buskirk
      • Re: CMPLX, REAL, and INT -- almost done, James Van Buskirk
      • Re: CMPLX, REAL, and INT -- almost done, Steven G. Kargl
      • Re: CMPLX, REAL, and INT -- almost done, Steven G. Kargl
      • Re: CMPLX, REAL, and INT -- almost done, James Van Buskirk
      • Re: CMPLX, REAL, and INT -- almost done, FX
• [ifort] Opening too much time files cause a segmentation fault, Jonathan
  • Re: [ifort] Opening too much time files cause a segmentation fault, mecej4
  • Re: [ifort] Opening too much time files cause a segmentation fault, Steve Lionel
    • [fixed] Opening too much time files cause a segmentation fault, Jonathan
• Sorting arrays, tomguest
  • Re: Sorting arrays, e p chandler
    • Re: Sorting arrays, Terence
    • Re: Sorting arrays, James Van Buskirk
      • Re: Sorting arrays, Ron Ford
      • Re: Sorting arrays, Richard Maine
      • Re: Sorting arrays, Ron Ford
      • Re: Sorting arrays, Ron Ford
  • Re: Sorting arrays, Mark Westwood
    • Re: Sorting arrays, e p chandler
• Array sections and F90/95 Standard, Herman D . Knoble
  • Re: Array sections and F90/95 Standard, Michael Metcalf
    • Re: Array sections and F90/95 Standard, Herman D . Knoble
      • Re: Array sections and F90/95 Standard, Michael Metcalf
      • Re: Array sections and F90/95 Standard, Herman D . Knoble
      • Re: Array sections and F90/95 Standard, James Van Buskirk
      • Re: Array sections and F90/95 Standard, Herman D . Knoble
• Recursive function (with allocatable inside), relaxmike
  • Re: Recursive function (with allocatable inside), Michael Metcalf
    • Re: Recursive function (with allocatable inside), relaxmike
      • Re: Recursive function (with allocatable inside), Michael Metcalf
      • Re: Recursive function (with allocatable inside), relaxmike
      • Re: Recursive function (with allocatable inside), Richard Maine
  • Re: Recursive function (with allocatable inside), James Van Buskirk
    • Re: Recursive function (with allocatable inside), relaxmike
    • Re: Recursive function (with allocatable inside), Ron Ford
      • Re: Recursive function (with allocatable inside), Gib Bogle
• Bitwise logical functions in gfortran, James Van Buskirk
  • Re: Bitwise logical functions in gfortran, Terence
    • Re: Bitwise logical functions in gfortran, glen herrmannsfeldt
  • Re: Bitwise logical functions in gfortran, Steven G. Kargl
  • Re: Bitwise logical functions in gfortran, Steven G. Kargl
    • Re: Bitwise logical functions in gfortran, James Van Buskirk
• GFortran - OpenMP problem with Windows XP memory, Cirilo S. Bresolin
  • Re: GFortran - OpenMP problem with Windows XP memory, Anony
  • Re: GFortran - OpenMP problem with Windows XP memory, glen herrmannsfeldt
    • Re: GFortran - OpenMP problem with Windows XP memory, Anony
      • Re: GFortran - OpenMP problem with Windows XP memory, Steven G. Kargl
      • Re: GFortran - OpenMP problem with Windows XP memory, Anony
      • Re: GFortran - OpenMP problem with Windows XP memory, Steven G. Kargl
      • Re: GFortran - OpenMP problem with Windows XP memory, Anony
      • Message not available
      • Re: GFortran - OpenMP problem with Windows XP memory, Cirilo S. Bresolin
      • Re: GFortran - OpenMP problem with Windows XP memory, Anony
      • Re: GFortran - OpenMP problem with Windows XP memory, Tobias Burnus
      • Re: GFortran - OpenMP problem with Windows XP memory, Anony
      • Re: GFortran - OpenMP problem with Windows XP memory, glen herrmannsfeldt
  • Re: GFortran - OpenMP problem with Windows XP memory, Greg Lindahl
• How to determine whether or not there exists a directory, ziven
  • Re: How to determine whether or not there exists a directory, Terence
    • Re: How to determine whether or not there exists a directory, Steve Lionel
      • Re: How to determine whether or not there exists a directory, Ron Ford
      • Re: How to determine whether or not there exists a directory, Terence
      • Re: How to determine whether or not there exists a directory, Ron Ford
      • Re: How to determine whether or not there exists a directory, glen herrmannsfeldt
      • Re: How to determine whether or not there exists a directory, ziven
      • Re: How to determine whether or not there exists a directory, Catherine Rees Lay
      • Re: How to determine whether or not there exists a directory, ziven
      • Re: How to determine whether or not there exists a directory, Steve Lionel
  • Re: How to determine whether or not there exists a directory, Arjen Markus
    • Re: How to determine whether or not there exists a directory, relaxmike
  • Re: How to determine whether or not there exists a directory, Reinhold Bader
  • Re: How to determine whether or not there exists a directory, David Jones
    • Re: How to determine whether or not there exists a directory, Steve Lionel
      • Re: How to determine whether or not there exists a directory, Terence
      • Re: How to determine whether or not there exists a directory, Terence
• How to distinguish between numerical data and alphanumeric title, bru
  • Re: How to distinguish between numerical data and alphanumeric title, e p chandler
    • Re: How to distinguish between numerical data and alphanumeric title, Terence
  • Re: How to distinguish between numerical data and alphanumeric title, glen herrmannsfeldt
    • Re: How to distinguish between numerical data and alphanumeric title, Arjen Markus
      • Re: How to distinguish between numerical data and alphanumeric title, bru
      • Re: How to distinguish between numerical data and alphanumeric title, Arjen Markus
      • Re: How to distinguish between numerical data and alphanumeric title, bru
      • Re: How to distinguish between numerical data and alphanumeric title, John Harper
      • Re: How to distinguish between numerical data and alphanumeric title, glen herrmannsfeldt
      • Re: How to distinguish between numerical data and alphanumeric title, e p chandler
      • Re: How to distinguish between numerical data and alphanumeric title, glen herrmannsfeldt
      • Re: How to distinguish between numerical data and alphanumeric title, Arjen Markus
  • Re: How to distinguish between numerical data and alphanumeric title, GaryScott
    • Re: How to distinguish between numerical data and alphanumeric title, glen herrmannsfeldt
• advance=no problem, rudra
  • Re: advance=no problem, rudra
  • Re: advance=no problem, Gordon Sande
    • Re: advance=no problem, John Harper
  • Re: advance=no problem, tholen
    • Re: advance=no problem, glen herrmannsfeldt
      • Re: advance=no problem, tholen
      • Re: advance=no problem, James Giles
      • Re: advance=no problem, Janne Blomqvist
      • Message not available
      • Re: advance=no problem, glen herrmannsfeldt
      • Re: advance=no problem, Janne Blomqvist
      • Re: advance=no problem, Richard Maine
      • Re: advance=no problem, glen herrmannsfeldt
  • Re: advance=no problem, robert . corbett
    • Re: advance=no problem, GaryScott
      • Re: advance=no problem, Richard Maine
      • Re: advance=no problem, GaryScott
      • Re: advance=no problem, robert . corbett
      • Re: advance=no problem, James Giles
      • Re: advance=no problem, robert . corbett
      • Re: advance=no problem, James Giles
      • Re: advance=no problem, James Giles
      • Re: advance=no problem, Richard Maine
      • Re: advance=no problem, James Giles
      • Re: advance=no problem, robert . corbett
      • Re: advance=no problem, Richard Maine
      • Re: advance=no problem, robert . corbett
      • Re: advance=no problem, Jugoslav Dujic
      • Re: advance=no problem, robert . corbett
      • Re: advance=no problem, GaryScott
      • Re: advance=no problem, Richard Maine
      • Re: advance=no problem, Ron Shepard
      • Re: advance=no problem, Richard Maine
      • Re: advance=no problem, glen herrmannsfeldt
      • Re: advance=no problem, GaryScott
      • Re: advance=no problem, James Giles
      • Re: advance=no problem, Richard Maine
      • Re: advance=no problem, Gary Scott
      • Re: advance=no problem, James Giles
      • Re: advance=no problem, Richard Maine
      • Re: advance=no problem, glen herrmannsfeldt
      • Re: advance=no problem, robert . corbett
      • Re: advance=no problem, GaryScott
      • Re: advance=no problem, Steve Lionel
  • Re: advance=no problem, dongyuanxun
• Identifier name length in g77, Łukasz
  • Re: Identifier name length in g77, Dr Ivan D. Reid
  • Re: Identifier name length in g77, Dick Hendrickson
  • Re: Identifier name length in g77, Greg Lindahl
• Subroutine header, Stefan
  • Re: Subroutine header, e p chandler
  • Re: Subroutine header, Mark Westwood
• ISO_C_BINDING and BLAS/LAPACK, Jason Nielsen
  • Re: ISO_C_BINDING and BLAS/LAPACK, Damian
• ISO 10646 support, FX
  • Re: ISO 10646 support, Ron Ford
  • Re: ISO 10646 support, Ron Ford
    • Re: ISO 10646 support, William Clodius
• Re: ranlux, Phillip Helbig---remove CLOTHES to reply
• derived type as argument, GeoGarfield
  • Re: derived type as argument, Tim Prince
  • Re: derived type as argument, Richard Maine
    • Re: derived type as argument, Ron Shepard
      • Re: derived type as argument, GeoGarfield
• I think the standard will be on my side (BOZ), James Van Buskirk
  • Re: I think the standard will be on my side (BOZ), Gary Scott
    • Re: I think the standard will be on my side (BOZ), Greg Lindahl
      • Re: I think the standard will be on my side (BOZ), Gary Scott
  • Re: I think the standard will be on my side (BOZ), Steven G. Kargl
    • Re: I think the standard will be on my side (BOZ), Greg Lindahl
      • Re: I think the standard will be on my side (BOZ), Steven G. Kargl
      • Re: I think the standard will be on my side (BOZ), glen herrmannsfeldt
      • Re: I think the standard will be on my side (BOZ), Gary Scott
      • Re: I think the standard will be on my side (BOZ), glen herrmannsfeldt
      • Re: I think the standard will be on my side (BOZ), John Harper
      • Re: I think the standard will be on my side (BOZ), Terence
    • Re: I think the standard will be on my side (BOZ), James Giles
      • Message not available
      • Re: I think the standard will be on my side (BOZ), James Giles
      • Re: I think the standard will be on my side (BOZ), glen herrmannsfeldt
      • Re: I think the standard will be on my side (BOZ), James Giles
      • Re: I think the standard will be on my side (BOZ), glen herrmannsfeldt
      • Re: I think the standard will be on my side (BOZ), James Giles
      • Re: I think the standard will be on my side (BOZ), glen herrmannsfeldt
      • Re: I think the standard will be on my side (BOZ), James Giles
      • Re: I think the standard will be on my side (BOZ), glen herrmannsfeldt
      • Re: I think the standard will be on my side (BOZ), James Giles
      • Re: I think the standard will be on my side (BOZ), glen herrmannsfeldt
      • Re: I think the standard will be on my side (BOZ), James Giles
      • Re: I think the standard will be on my side (BOZ), Ken . Fairfield
      • Re: I think the standard will be on my side (BOZ), Ken . Fairfield
      • Re: I think the standard will be on my side (BOZ), James Giles
      • Message not available
      • Re: I think the standard will be on my side (BOZ), James Van Buskirk
      • Re: I think the standard will be on my side (BOZ), Charles Coldwell
      • Re: I think the standard will be on my side (BOZ), Gary Scott
    • Re: I think the standard will be on my side (BOZ), glen herrmannsfeldt
      • Re: I think the standard will be on my side (BOZ), Steven G. Kargl
      • Re: I think the standard will be on my side (BOZ), glen herrmannsfeldt
      • Re: I think the standard will be on my side (BOZ), Richard Maine
      • Re: I think the standard will be on my side (BOZ), James Giles
• Protect yourself against Operation Sudden Fall, Walter . Heiting
• Perverse G77 syntax extension, Dr Ivan D. Reid
  • Re: Perverse G77 syntax extension, Michael Metcalf
  • Re: Perverse G77 syntax extension, glen herrmannsfeldt
    • Re: Perverse G77 syntax extension, John Harper
• Can "Final subroutines" in F2003 delete pointer components in a class?, Simulate
  • Re: Can "Final subroutines" in F2003 delete pointer components in a class?, Reinhold Bader
    • Re: Can "Final subroutines" in F2003 delete pointer components in a class?, Simulate
      • Re: Can "Final subroutines" in F2003 delete pointer components in a class?, Jim Xia
      • Message not available
      • Re: Can "Final subroutines" in F2003 delete pointer components in a class?, Jim Xia
      • Message not available
      • Re: Can "Final subroutines" in F2003 delete pointer components in a class?, Jim Xia
      • Re: Can "Final subroutines" in F2003 delete pointer components in a class?, James Giles
      • Re: Can "Final subroutines" in F2003 delete pointer components in a class?, glen herrmannsfeldt
      • Re: Can "Final subroutines" in F2003 delete pointer components in a class?, Reinhold Bader
• CMPLX and constant folding, James Van Buskirk
  • Re: CMPLX and constant folding, FX
    • Re: CMPLX and constant folding, glen herrmannsfeldt
      • Re: CMPLX and constant folding, FX
      • Re: CMPLX and constant folding, James Van Buskirk
      • Re: CMPLX and constant folding, John Harper
      • Re: CMPLX and constant folding, Richard Maine
    • Re: CMPLX and constant folding, James Van Buskirk
    • Re: CMPLX and constant folding, FX
      • Re: CMPLX and constant folding, James Van Buskirk
• circular module dependency, Gene Wagenbreth
  • Re: circular module dependency, Richard Maine
  • Re: circular module dependency, Steven G. Kargl
  • Re: circular module dependency, jamesgiles@xxxxxxx
  • Re: circular module dependency, Bil Kleb
    • Re: circular module dependency, Richard Maine
  • Re: circular module dependency, Damian
• compiler problem, rudra
  • Re: compiler problem, Steven G. Kargl
    • Re: compiler problem, rudra
      • Re: compiler problem, Steven G. Kargl
  • Re: compiler problem, Craig Powers
    • Re: compiler problem, glen herrmannsfeldt
      • Re: compiler problem, Michael Metcalf
      • Re: compiler problem, glen herrmannsfeldt
      • Re: compiler problem, Craig Powers
      • Re: compiler problem, Greg Lindahl
      • Re: compiler problem, rudra
      • Re: compiler problem, Craig Powers
      • Re: compiler problem, Dick Hendrickson
      • Re: compiler problem, Michael Metcalf
• hillary's files, Ron Ford
  • Re: hillary's files, Me
    • Re: hillary's files, Ron Ford
• MPI code error raises a question, Gib Bogle
  • Re: MPI code error raises a question, Steve Lionel
    • Re: MPI code error raises a question, Gib Bogle
      • Re: MPI code error raises a question, Richard Maine
      • Re: MPI code error raises a question, Greg Lindahl
      • Re: MPI code error raises a question, Richard Maine
      • Re: MPI code error raises a question, Janne Blomqvist
      • Re: MPI code error raises a question, Dan Nagle
      • Re: MPI code error raises a question, glen herrmannsfeldt
      • Re: MPI code error raises a question, Dan Nagle
      • Re: MPI code error raises a question, glen herrmannsfeldt
      • Re: MPI code error raises a question, Dick Hendrickson
      • Re: MPI code error raises a question, Dan Nagle
      • Re: MPI code error raises a question, Dick Hendrickson
      • Re: MPI code error raises a question, glen herrmannsfeldt
      • Re: MPI code error raises a question, Dan Nagle
      • Re: MPI code error raises a question, GaryScott
      • Re: MPI code error raises a question, glen herrmannsfeldt
      • Re: MPI code error raises a question, Richard Maine
      • Re: MPI code error raises a question, glen herrmannsfeldt
      • Re: MPI code error raises a question, Richard Maine
      • Re: MPI code error raises a question, Dick Hendrickson
      • Re: MPI code error raises a question, glen herrmannsfeldt
      • Re: MPI code error raises a question, Gary Scott
      • Re: MPI code error raises a question, Dan Nagle
      • Re: MPI code error raises a question, Ron Shepard
      • Re: MPI code error raises a question, Richard Maine
      • Re: MPI code error raises a question, Dan Nagle
      • Re: MPI code error raises a question, Gordon Sande
      • Re: MPI code error raises a question, Greg Lindahl
      • Re: MPI code error raises a question, Gib Bogle
  • Re: MPI code error raises a question, Herman D . Knoble
    • Re: MPI code error raises a question, Herman D . Knoble
    • Re: MPI code error raises a question, Gib Bogle
      • Re: MPI code error raises a question, Herman D . Knoble
• Compiler writer questions, Bil Kleb
  • Re: Compiler writer questions, John Harper
    • Re: Compiler writer questions, fj
  • Re: Compiler writer questions, Beliavsky
  • Re: Compiler writer questions, William Clodius
  • Re: Compiler writer questions, Thomas Koenig
    • Re: Compiler writer questions, Bil Kleb
    • Re: Compiler writer questions, Greg Lindahl
  • Re: Compiler writer questions, Jim Xia
  • <Possible follow-ups>
  • Re: Compiler writer questions, Ron Ford
• Derived types and allocatable, Gib Bogle
  • Re: Derived types and allocatable, Gib Bogle
    • Re: Derived types and allocatable, James Van Buskirk
      • Re: Derived types and allocatable, Steven Correll
      • Re: Derived types and allocatable, James Giles
      • Re: Derived types and allocatable, Jan Vorbrüggen
      • Re: Derived types and allocatable, James Giles
      • Re: Derived types and allocatable, glen herrmannsfeldt
      • Re: Derived types and allocatable, James Giles
      • Re: Derived types and allocatable, glen herrmannsfeldt
      • Re: Derived types and allocatable, James Giles
      • Re: Derived types and allocatable, Jan Vorbrüggen
      • Re: Derived types and allocatable, James Van Buskirk
      • Re: Derived types and allocatable, James Giles
    • Re: Derived types and allocatable, Kurt Kallblad
      • Re: Derived types and allocatable, Richard Maine
      • Re: Derived types and allocatable, Damian
      • Re: Derived types and allocatable, Steve Lionel
      • Re: Derived types and allocatable, Damian
      • Re: Derived types and allocatable, Steve Lionel
      • Re: Derived types and allocatable, Damian
      • Re: Derived types and allocatable, Steve Lionel
      • Re: Derived types and allocatable, Damian
      • Re: Derived types and allocatable, Gib Bogle
  • Re: Derived types and allocatable, James Van Buskirk
  • Re: Derived types and allocatable, Gib Bogle
• weird g77 and gfortran, K-9
  • Re: weird g77 and gfortran, e p chandler
    • Re: weird g77 and gfortran, K-9
      • Re: weird g77 and gfortran, Greg Lindahl
      • Re: weird g77 and gfortran, Charles Coldwell
      • Re: weird g77 and gfortran, Catherine Rees Lay
    • Re: weird g77 and gfortran, Craig Powers
      • Re: weird g77 and gfortran, Steven G. Kargl
    • Re: weird g77 and gfortran, Ingo Thies
      • Re: weird g77 and gfortran, stevenb . gcc
      • Re: weird g77 and gfortran, Ingo Thies
      • Re: weird g77 and gfortran, Steven G. Kargl
      • Re: weird g77 and gfortran, Thomas Koenig
      • Re: weird g77 and gfortran, Ingo Thies
      • Re: weird g77 and gfortran, Greg Lindahl
      • Re: weird g77 and gfortran, Thomas Koenig
      • Re: weird g77 and gfortran, Ingo Thies
      • Re: weird g77 and gfortran, stevenb . gcc
• C preprocessor, James Van Buskirk
  • Re: C preprocessor, glen herrmannsfeldt
  • Re: C preprocessor, glen herrmannsfeldt
    • Re: C preprocessor, glen herrmannsfeldt
• A Faster/Better way?, Infinity77
  • Re: A Faster/Better way?, glen herrmannsfeldt
    • Re: A Faster/Better way?, Janne Blomqvist
      • Re: A Faster/Better way?, glen herrmannsfeldt
  • Re: A Faster/Better way?, Janne Blomqvist
• module or interface, Klemens
  • Re: module or interface, Richard Maine
    • Re: module or interface, Klemens
      • Re: module or interface, Arjen Markus
      • Re: module or interface, Klemens
      • Re: module or interface, rudra
• Re: curious about 8 byte LOGICAL..., David Thompson
  • <Possible follow-ups>
  • Re: curious about 8 byte LOGICAL..., David Thompson
    • Re: curious about 8 byte LOGICAL..., glen herrmannsfeldt
      • Re: curious about 8 byte LOGICAL..., Thomas Koenig
      • Re: curious about 8 byte LOGICAL..., glen herrmannsfeldt
• Re: Doubt about formula transcription, e p chandler
  • Re: Doubt about formula transcription, glen herrmannsfeldt
    • Re: Doubt about formula transcription, Terence
• Treacherous Behavior of "gfortran" Compiler?, qquito
  • Re: Treacherous Behavior of "gfortran" Compiler?, Thomas Koenig
  • Re: Treacherous Behavior of "gfortran" Compiler?, Gordon Sande
    • Re: Treacherous Behavior of "gfortran" Compiler?, qquito
      • Re: Treacherous Behavior of "gfortran" Compiler?, Ron Ford
      • Re: Treacherous Behavior of "gfortran" Compiler?, Gordon Sande
      • Re: Treacherous Behavior of "gfortran" Compiler?, Dan Nagle
      • Re: Treacherous Behavior of "gfortran" Compiler?, Ron Ford
      • Re: Treacherous Behavior of "gfortran" Compiler?, Kurt Kallblad
      • Re: Treacherous Behavior of "gfortran" Compiler?, Ron Ford
    • Re: Treacherous Behavior of "gfortran" Compiler?, jamesgiles@xxxxxxx
• deepening into fortran 90,95, 2003, octaedro
  • Re: deepening into fortran 90,95, 2003, Mark Westwood
    • Re: deepening into fortran 90,95, 2003, Michael Metcalf
  • Re: deepening into fortran 90,95, 2003, James Van Buskirk
    • Re: deepening into fortran 90,95, 2003, Dan Nagle
      • Re: deepening into fortran 90,95, 2003, glen herrmannsfeldt
      • Re: deepening into fortran 90,95, 2003, GaryScott
      • Re: deepening into fortran 90,95, 2003, glen herrmannsfeldt
      • Re: deepening into fortran 90,95, 2003, Terence
      • Re: deepening into fortran 90,95, 2003, glen herrmannsfeldt
      • Re: deepening into fortran 90,95, 2003, e p chandler
      • Re: deepening into fortran 90,95, 2003, glen herrmannsfeldt
      • Re: deepening into fortran 90,95, 2003, Terence
      • Re: deepening into fortran 90,95, 2003, Greg Lindahl
      • Re: deepening into fortran 90,95, 2003, William Clodius
      • Re: deepening into fortran 90,95, 2003, Greg Lindahl
      • Re: deepening into fortran 90,95, 2003, glen herrmannsfeldt
      • Re: deepening into fortran 90,95, 2003, Richard Maine
      • Re: deepening into fortran 90,95, 2003, glen herrmannsfeldt
      • Re: deepening into fortran 90,95, 2003, John Harper
      • Re: deepening into fortran 90,95, 2003, Richard Maine
      • Re: deepening into fortran 90,95, 2003, Gordon Sande
      • Re: deepening into fortran 90,95, 2003, Gary Scott
      • Re: deepening into fortran 90,95, 2003, jamesgiles@xxxxxxx
      • Re: deepening into fortran 90,95, 2003, James Van Buskirk
      • Re: deepening into fortran 90,95, 2003, Richard Maine
      • Re: deepening into fortran 90,95, 2003, glen herrmannsfeldt
      • Re: deepening into fortran 90,95, 2003, Gary Scott
      • Re: deepening into fortran 90,95, 2003, Janne Blomqvist
      • Re: deepening into fortran 90,95, 2003, Greg Lindahl
      • Re: deepening into fortran 90,95, 2003, Charles Coldwell
      • Re: deepening into fortran 90,95, 2003, James Van Buskirk
  • Re: deepening into fortran 90,95, 2003, rusi_pathan
    • Re: deepening into fortran 90,95, 2003, octaedro
      • Re: deepening into fortran 90,95, 2003, Damian
  • Re: deepening into fortran 90,95, 2003, John Harper
• Re: gfortran produces huge executables, Anony
• Standard input, Tim Springer
  • Re: Standard input, Charles Coldwell
    • Re: Standard input, Arjen Markus
      • Re: Standard input, Charles Coldwell
      • Re: Standard input, Arjen Markus
      • Re: Standard input, Charles Coldwell
• Build project in CVF6.6c by using hotkey, Mike
  • Re: Build project in CVF6.6c by using hotkey, dpb
    • Re: Build project in CVF6.6c by using hotkey, Mike
      • Re: Build project in CVF6.6c by using hotkey, dpb
      • Re: Build project in CVF6.6c by using hotkey, Craig Powers
      • Re: Build project in CVF6.6c by using hotkey, dpb
      • Re: Build project in CVF6.6c by using hotkey, Craig Powers
      • Re: Build project in CVF6.6c by using hotkey, dpb
      • Re: Build project in CVF6.6c by using hotkey, dpb
      • Re: Build project in CVF6.6c by using hotkey, Craig Powers
      • Re: Build project in CVF6.6c by using hotkey, Steve Lionel
      • Re: Build project in CVF6.6c by using hotkey, Craig Powers
  • Re: Build project in CVF6.6c by using hotkey, Craig Powers
    • Re: Build project in CVF6.6c by using hotkey, Mike
• Intel Fortran compiler for Windows crashing, Jon Harrop
  • Re: Intel Fortran compiler for Windows crashing, Tim Prince
    • Re: Intel Fortran compiler for Windows crashing, Greg Lindahl
      • Re: Intel Fortran compiler for Windows crashing, Gary Scott
      • Re: Intel Fortran compiler for Windows crashing, Jon Harrop
    • Re: Intel Fortran compiler for Windows crashing, Jon Harrop
      • Re: Intel Fortran compiler for Windows crashing, Ron Ford
      • Re: Intel Fortran compiler for Windows crashing, Jon Harrop
      • Re: Intel Fortran compiler for Windows crashing, Gary Scott
      • Re: Intel Fortran compiler for Windows crashing, Jon Harrop
      • Re: Intel Fortran compiler for Windows crashing, Steve Lionel
      • Re: Intel Fortran compiler for Windows crashing, Ron Ford
      • Re: Intel Fortran compiler for Windows crashing, Steve Lionel
      • Re: Intel Fortran compiler for Windows crashing, Jon Harrop
      • Re: Intel Fortran compiler for Windows crashing, Steve Lionel
      • Re: Intel Fortran compiler for Windows crashing, Jon Harrop
  • Re: Intel Fortran compiler for Windows crashing, Ron Ford
    • Re: Intel Fortran compiler for Windows crashing, Jon Harrop
  • Re: Intel Fortran compiler for Windows crashing, Catherine Rees Lay
    • Re: Intel Fortran compiler for Windows crashing, Jon Harrop
  • Re: Intel Fortran compiler for Windows crashing, Steve Lionel
    • Re: Intel Fortran compiler for Windows crashing, Jon Harrop
• Deallocate Breakpoint in Library Code, Michael
  • Re: Deallocate Breakpoint in Library Code, Richard Maine
  • Re: Deallocate Breakpoint in Library Code, Michael
    • Re: Deallocate Breakpoint in Library Code, Greg Lindahl
    • Re: Deallocate Breakpoint in Library Code, glen herrmannsfeldt
  • Re: Deallocate Breakpoint in Library Code, Greg Lindahl
  • Re: Deallocate Breakpoint in Library Code, Michael Metcalf
• maine@summertriangle.net, glen herrmannsfeldt
  • Re: maine@summertriangle.net, Richard Maine
    • Re: maine@summertriangle.net, Ron Ford
• f77 nostalgia, Steven G. Kargl
  • Re: f77 nostalgia, Terence
  • Re: f77 nostalgia, Thomas Koenig
    • Re: f77 nostalgia, Steven G. Kargl
      • Re: f77 nostalgia, Thomas Koenig
      • Re: f77 nostalgia, Steven G. Kargl
• Lahey Compiler, Jean H
  • Re: Lahey Compiler, Terence
    • Re: Lahey Compiler, Steve Lionel
      • Re: Lahey Compiler, Gary Scott
      • Re: Lahey Compiler, Terence
      • Re: Lahey Compiler, Gary Scott
      • Re: Lahey Compiler, Tim Prince
• Avoided "set but never used" warnings for dummy variable reads, Bil Kleb
  • Re: Avoided "set but never used" warnings for dummy variable reads, Jan Gerrit Kootstra
    • Re: Avoided "set but never used" warnings for dummy variable reads, Bil Kleb
  • Re: Avoided "set but never used" warnings for dummy variable reads, Richard Maine
    • Re: Avoided "set but never used" warnings for dummy variable reads, Bil Kleb
  • Re: Avoided "set but never used" warnings for dummy variable reads, glen herrmannsfeldt
    • Re: Avoided "set but never used" warnings for dummy variable reads, Bil Kleb
    • Re: Avoided "set but never used" warnings for dummy variable reads, John
    • Re: Avoided "set but never used" warnings for dummy variable reads, Dick Hendrickson
  • Re: Avoided "set but never used" warnings for dummy variable reads, Dan Nagle
    • Re: Avoided "set but never used" warnings for dummy variable reads, glen herrmannsfeldt
  • Re: Avoided "set but never used" warnings for dummy variable reads, Bil Kleb
    • Re: Avoided "set but never used" warnings for dummy variable reads, Richard Maine
      • Re: Avoided "set but never used" warnings for dummy variable reads, Gordon Sande
  • Re: Avoided "set but never used" warnings for dummy variable reads, David Flower
    • Re: Avoided "set but never used" warnings for dummy variable reads, Bil Kleb
• Re: Interpretation of RECL resolution; help file in CVF, Kevin G. Rhoads
  • Re: Interpretation of RECL resolution; help file in CVF, dpb
• ENCODING I/O specifier, FX
  • Re: ENCODING I/O specifier, FX
    • Re: ENCODING I/O specifier, Ian Bush
      • Re: ENCODING I/O specifier, FX
      • Re: ENCODING I/O specifier, Tobias Burnus
      • Re: ENCODING I/O specifier, FX
      • Re: ENCODING I/O specifier, Ian Bush
      • Re: ENCODING I/O specifier, FX
      • Re: ENCODING I/O specifier, Ian Bush
      • Re: ENCODING I/O specifier, Richard Maine
      • Re: ENCODING I/O specifier, FX
      • Re: ENCODING I/O specifier, Richard Maine
      • Re: ENCODING I/O specifier, robert . corbett
      • Re: ENCODING I/O specifier, FX
      • Re: ENCODING I/O specifier, Dan Nagle
      • Re: ENCODING I/O specifier, David Muxworthy
      • Re: ENCODING I/O specifier, jamesgiles@xxxxxxx
      • Re: ENCODING I/O specifier, glen herrmannsfeldt
      • Re: ENCODING I/O specifier, Richard Maine
      • Re: ENCODING I/O specifier, Terence
      • Re: ENCODING I/O specifier, glen herrmannsfeldt
  • Re: ENCODING I/O specifier, FX
    • Re: ENCODING I/O specifier, jamesgiles@xxxxxxx
• Reading complex data with DECIMAL='COMMA', SimonG
  • Re: Reading complex data with DECIMAL='COMMA', Tobias Burnus
    • Re: Reading complex data with DECIMAL='COMMA', SimonG
      • Re: Reading complex data with DECIMAL='COMMA', Richard Maine
      • Re: Reading complex data with DECIMAL='COMMA', SimonG
      • Re: Reading complex data with DECIMAL='COMMA', Terence
      • Re: Reading complex data with DECIMAL='COMMA', Janne Blomqvist
• Re: Allocatable arrays in derived types, paul . richard . thomas
  • <Possible follow-ups>
  • Re: Allocatable arrays in derived types, Gib Bogle
• Re: reminder of Public Comments for Fortran 2008, andrej . panjkov
  • <Possible follow-ups>
  • Re: reminder of Public Comments for Fortran 2008, robert . corbett
• Re: Fortran templates, Damian
  • Re: Fortran templates, Damian
    • Re: Fortran templates, Ron Ford
  • Re: Fortran templates, Jim Xia
    • Re: Fortran templates, Craig Powers
    • Re: Fortran templates, James Van Buskirk
      • Re: Fortran templates, James Van Buskirk
      • Re: Fortran templates, Tobias Burnus
      • Re: Fortran templates, Jim Xia
      • Re: Fortran templates, Jim Xia
  • <Possible follow-ups>
  • Re: Fortran templates, Bálint Aradi
    • Re: Fortran templates, Richard Maine
      • Re: Fortran templates, Jim Xia
      • Re: Fortran templates, Terence
    • Re: Fortran templates, James Van Buskirk
• F2C "Polisher", Gary Scott
  • Re: F2C "Polisher", Horand . Gassmann
    • Re: F2C "Polisher", Gary Scott
      • Re: F2C "Polisher", Tom Micevski
• Re: Can someone know the time for a oo implemented F2003 complier release under the window platform?, angelv
  • Re: Can someone know the time for a oo implemented F2003 complier release under the window platform?, James Van Buskirk
    • Re: Can someone know the time for a oo implemented F2003 complier release under the window platform?, angelv
• Re: Are f.p. manipulation functions only used in initialization?, Dan Nagle
  • Re: Are f.p. manipulation functions only used in initialization?, FX
    • Re: Are f.p. manipulation functions only used in initialization?, Dan Nagle
      • Re: Are f.p. manipulation functions only used in initialization?, FX
    • Re: Are f.p. manipulation functions only used in initialization?, Greg Lindahl
  • Re: Are f.p. manipulation functions only used in initialization?, James Van Buskirk
    • Re: Are f.p. manipulation functions only used in initialization?, Steven G. Kargl
    • Re: Are f.p. manipulation functions only used in initialization?, Dan Nagle
  • <Possible follow-ups>
  • Re: Are f.p. manipulation functions only used in initialization?, Dan Nagle
  • Re: Are f.p. manipulation functions only used in initialization?, FX
    • Re: Are f.p. manipulation functions only used in initialization?, James Van Buskirk
      • Re: Are f.p. manipulation functions only used in initialization?, FX
      • Re: Are f.p. manipulation functions only used in initialization?, James Van Buskirk
      • Re: Are f.p. manipulation functions only used in initialization?, James Van Buskirk
      • Re: Are f.p. manipulation functions only used in initialization?, Janne Blomqvist
      • Re: Are f.p. manipulation functions only used in initialization?, James Van Buskirk
      • Re: Are f.p. manipulation functions only used in initialization?, Janne Blomqvist
      • Re: Are f.p. manipulation functions only used in initialization?, James Van Buskirk
      • Re: Are f.p. manipulation functions only used in initialization?, James Van Buskirk
      • Re: Are f.p. manipulation functions only used in initialization?, FX
      • Re: Are f.p. manipulation functions only used in initialization?, James Van Buskirk
      • Re: Are f.p. manipulation functions only used in initialization?, Ron Ford
      • Re: Are f.p. manipulation functions only used in initialization?, James Van Buskirk
• Re: Index of array from mask, hiphop
  • Re: Index of array from mask, Terence
• Re: Pointers to derived type objects in COMMON, Walter Spector
• Re: Derived Type Pointer Allocation Issue, fj
  • <Possible follow-ups>
  • Re: Derived Type Pointer Allocation Issue, Dick Hendrickson
    • Re: Derived Type Pointer Allocation Issue, Michael
  • Re: Derived Type Pointer Allocation Issue, Richard Maine
    • Re: Derived Type Pointer Allocation Issue, Michael
      • Re: Derived Type Pointer Allocation Issue, Michael
      • Re: Derived Type Pointer Allocation Issue, Richard Maine
      • Re: Derived Type Pointer Allocation Issue, Michael
      • Re: Derived Type Pointer Allocation Issue, Steve Lionel
      • Re: Derived Type Pointer Allocation Issue, Michael
      • Re: Derived Type Pointer Allocation Issue, Michael
      • Re: Derived Type Pointer Allocation Issue, Michael
      • Re: Derived Type Pointer Allocation Issue, Steve Lionel
      • Re: Derived Type Pointer Allocation Issue, Michael
      • Re: Derived Type Pointer Allocation Issue, Dick Hendrickson
      • Re: Derived Type Pointer Allocation Issue, Michael

• Security
• UNIX
• Linux
• Coding
• Usenet

• Archive
• About
• Privacy
• Search
• Imprint

coding.derkeiler.com  > Archive  > Fortran  > comp.lang.fortran  > 2008-05