comp.lang.fortran

• Thread Index

---

• Re: sequence points and the execution model
  • From: Richard Maine
• Re: FORTRAN dynamic arrays used as parameters of functions called from C++
  • From: Matthew Della
• Re: New to Fortran on Win XP
  • From: Craig Powers
• Re: sequence points and the execution model
  • From: Craig Powers
• Re: about the order of program units
  • From: hes selex
• Re: about the order of program units
  • From: Richard Maine
• FORTRAN dynamic arrays used as parameters of functions called from C++
  • From: Matthew Della
• Re: about the order of program units
  • From: hes selex
• Re: about the order of program units
  • From: Steve Lionel
• Re: Capitalization style
  • From: robin
• Re: about the order of program units
  • From: Arjen Markus
• Re: about the order of program units
  • From: Arjan
• Re: about the order of program units
  • From: hes selex
• Re: about the order of program units
  • From: Arjen Markus
• Re: about the order of program units
  • From: hes selex
• Re: about the order of program units
  • From: Arjen Markus
• about the order of program units
  • From: hes selex
• Re: Is Co-Array the Future of Parallel Computing?
  • From: Victor Eijkhout
• Re: porting union, map to gfortran
  • From: Gary Scott
• Re: Capitalization style: far off topic!
  • From: Dick Hendrickson
• Re: Is Co-Array the Future of Parallel Computing?
  • From: rusi_pathan
• Re: Capitalization style
  • From: robin
• Re: Is Co-Array the Future of Parallel Computing?
  • From: Victor Eijkhout
• Re: porting union, map to gfortran
  • From: Dr Ivan D. Reid
• Re: Is Co-Array the Future of Parallel Computing?
  • From: Dan Nagle
• Re: porting union, map to gfortran
  • From: dpb
• Re: Is Co-Array the Future of Parallel Computing?
  • From: Victor Eijkhout
• Re: Is Co-Array the Future of Parallel Computing?
  • From: Victor Eijkhout
• Re: porting union, map to gfortran
  • From: ken . fairfield
• Re: porting union, map to gfortran
  • From: dpb
• Re: Is Co-Array the Future of Parallel Computing?
  • From: rusi_pathan
• Re: porting union, map to gfortran
  • From: none
• Re: Is Co-Array the Future of Parallel Computing?
  • From: rusi_pathan
• Re: Capitalization style
  • From: Paul van Delst
• Re: Capitalization style
  • From: Ron Shepard
• Re: Problem
  • From: Dave Allured
• Re: porting union, map to gfortran
  • From: dpb
• Re: Capitalization style
  • From: Richard Maine
• Re: Capitalization style
  • From: Paul van Delst
• Re: porting union, map to gfortran
  • From: Thomas Koenig
• Re: Capitalization style
  • From: Terence
• Re: inputting the ephemerides
  • From: Terence
• Re: Public/Private or gfortran problem?
  • From: Chris Bradley
• Re: inputting the ephemerides
  • From: Arjen Markus
• Re: inputting the ephemerides
  • From: jon
• Re: porting union, map to gfortran
  • From: Arjen Markus
• Re: Is Co-Array the Future of Parallel Computing?
  • From: Tom Micevski
• Re: Is Co-Array the Future of Parallel Computing?
  • From: George
• inputting the ephemerides
  • From: George
• Re: Is Co-Array the Future of Parallel Computing?
  • From: Victor Eijkhout
• Re: Is Co-Array the Future of Parallel Computing?
  • From: Victor Eijkhout
• Re: porting union, map to gfortran
  • From: dpb
• Re: Is Co-Array the Future of Parallel Computing?
  • From: Dan Nagle
• porting union, map to gfortran
  • From: raju
• Re: Capitalization style
  • From: robin
• Re: Is Co-Array the Future of Parallel Computing?
  • From: Gib Bogle
• Re: sequence points and the execution model
  • From: George
• Re: how to link subroutines with main program?
  • From: Terence
• Re: sequence points and the execution model
  • From: Terence
• Re: Is Co-Array the Future of Parallel Computing?
  • From: Dan Nagle
• Re: how to link subroutines with main program?
  • From: dpb
• Re: Is Co-Array the Future of Parallel Computing?
  • From: Victor Eijkhout
• Re: Is Co-Array the Future of Parallel Computing?
  • From: Dan Nagle
• how to link subroutines with main program?
  • From: soms . sharma
• Re: Is Co-Array the Future of Parallel Computing?
  • From: Victor Eijkhout
• Re: Capitalization style
  • From: Damian
• Re: Is Co-Array the Future of Parallel Computing?
  • From: Dan Nagle
• SUPRISE...!
  • From: enteringheaven
• Re: sequence points and the execution model
  • From: glen herrmannsfeldt
• Re: Is Co-Array the Future of Parallel Computing?
  • From: fj
• Re: sequence points and the execution model
  • From: Terence
• Re: Capitalization style
  • From: Terence
• Re: Capitalization style
  • From: George
• sequence points and the execution model
  • From: George
• Re: conjunction junction
  • From: George
• Re: OPTIONAL STRING argument problem
  • From: Terence
• Re: looking for a strategy with segmentation fault
  • From: robin
• Re: OPTIONAL STRING argument problem
  • From: robin
• Re: Problem
  • From: Terence
• Re: Public/Private or gfortran problem?
  • From: paul . richard . thomas
• Emacs' Flymake on-the-fly syntax checking
  • From: BIl Kleb
• Re: Problem
  • From: marek87
• Re: SUPRISE...!
  • From: Sjouke Burry
• Re: Is Co-Array the Future of Parallel Computing?
  • From: Dan Nagle
• Re: Capitalization style
  • From: Peter C. Chapin
• Re: Is Co-Array the Future of Parallel Computing?
  • From: fj
• Re: Is Co-Array the Future of Parallel Computing?
  • From: Richard Maine
• Re: Capitalization style
  • From: Terence
• Re: Problem
  • From: Terence
• Re: Is Co-Array the Future of Parallel Computing?
  • From: Dan Nagle
• Re: Is Co-Array the Future of Parallel Computing?
  • From: no_user
• Re: Capitalization style
  • From: JB
• Re: Is Co-Array the Future of Parallel Computing?
  • From: Dan Nagle
• Re: Is Co-Array the Future of Parallel Computing?
  • From: no_user
• Re: Is Co-Array the Future of Parallel Computing?
  • From: George
• Re: Problem
  • From: marek87
• Re: Capitalization style
  • From: Phillip Helbig---remove CLOTHES to reply
• Re: Capitalization style
  • From: Gordon Sande
• Re: Capitalization style
  • From: Phillip Helbig---remove CLOTHES to reply
• Re: Capitalization style
  • From: Dan Nagle
• Re: Capitalization style
  • From: Gordon Sande
• Re: Capitalization style
  • From: Peter C. Chapin
• Re: Capitalization style
  • From: Dr Ivan D. Reid
• Re: Capitalization style
  • From: makyo
• Re: Capitalization style
  • From: Dick Hendrickson
• Re: Is Co-Array the Future of Parallel Computing?
  • From: Dan Nagle
• Re: Problem
  • From: Dave Allured
• Re: Capitalization style
  • From: Dave Allured
• Is Co-Array the Future of Parallel Computing?
  • From: fortrangroup
• Re: Capitalization style
  • From: Phillip Helbig---remove CLOTHES to reply
• Capitalization style
  • From: Peter C. Chapin
• Re: Problem
  • From: Thomas Koenig
• Re: incorporating an index in a string
  • From: George
• Re: OPTIONAL STRING argument problem
  • From: James Van Buskirk
• Re: passing a string
  • From: robin
• OPTIONAL STRING argument problem
  • From: zuying@xxxxxxxxx
• Fortran IV to F77
  • From: Terence
• Re: Problem
  • From: Terence
• Re: Photran compiles but refuses to debug (MinGW-MSYS-g95)
  • From: Arjan
• Re: incorporating an index in a string
  • From: fj
• Re: passing a string
  • From: Luka Djigas
• Re: infinite DO
  • From: David Flower
• Re: passing a string
  • From: George
• Re: Fortran libraries & modules...
  • From: robin
• Re: Newbie F90 Question -- or may not be!
  • From: robin
• Re: infinite DO
  • From: robin
• Re: avoiding trailing zeros
  • From: robin
• Re: avoiding trailing zeros
  • From: robin
• Re: Anybody can help me out on WRITE format?
  • From: robin
• Re: New to Fortran on Win XP
  • From: robin
• Re: infinite DO
  • From: robin
• Re: incorporating an index in a string
  • From: George
• Re: Problem
  • From: Dave Allured
• Photran compiles but refuses to debug (MinGW-MSYS-g95)
  • From: Arjan
• Re: incorporating an index in a string
  • From: Arjan
• passing a string
  • From: Luka Djigas
• Re: incorporating an index in a string
  • From: user1
• Re: incorporating an index in a string
  • From: fj
• incorporating an index in a string
  • From: George
• Re: infinite DO
  • From: George
• Re: New to Fortran on Win XP
  • From: George
• Re: New to Fortran on Win XP
  • From: Matti
• Re: infinite DO
  • From: Pierre Asselin
• infinite DO
  • From: Charles Coldwell
• Re: New to Fortran on Win XP
  • From: Beliavsky
• Re: ice melting
  • From: Terence
• Re: New to Fortran on Win XP
  • From: Gib Bogle
• Re: New to Fortran on Win XP
  • From: Sebastian Gallinat
• Re: New to Fortran on Win XP
  • From: e p chandler
• New to Fortran on Win XP
  • From: Matti
• Re: Problem
  • From: marek87
• Re: Read a line to variables from data file?
  • From: michaelmetcalf
• Re: Read a line to variables from data file?
  • From: Arjen Markus
• Re: Read a line to variables from data file?
  • From: Dr Ivan D. Reid
• Read a line to variables from data file?
  • From: Qiang Zhong
• Re: gfortran binaries for MinGW-Win32?
  • From: e p chandler
• Re: Anybody can help me out on WRITE format?
  • From: George
• Re: gfortran binaries for MinGW-Win32?
  • From: George
• Re: passing by value in Fortran 90
  • From: Damian
• Re: passing by value in Fortran 90
  • From: James Van Buskirk
• passing by value in Fortran 90
  • From: Damian
• Re: iostat usage
  • From: Mike
• Re: populating arrays
  • From: George
• Re: Public/Private or gfortran problem?
  • From: paul . richard . thomas
• Re: Anybody can help me out on WRITE format?
  • From: GaryScott
• Re: Anybody can help me out on WRITE format?
  • From: GaryScott
• Re: Anybody can help me out on WRITE format?
  • From: GaryScott
• Re: Anybody can help me out on WRITE format?
  • From: GaryScott
• Re: Anybody can help me out on WRITE format?
  • From: GaryScott
• Re: Anybody can help me out on WRITE format?
  • From: Jason
• Re: Anybody can help me out on WRITE format?
  • From: GaryScott
• Re: Public/Private or gfortran problem?
  • From: GaryScott
• Anybody can help me out on WRITE format?
  • From: Jason
• Re: Redux: Was there a negative real zero possibility in early Fortran?
  • From: Kevin G. Rhoads
• Re: populating arrays
  • From: user1
• Re: Public/Private or gfortran problem?
  • From: GaryScott
• Re: Public/Private or gfortran problem?
  • From: GaryScott
• Public/Private or gfortran problem?
  • From: Chris Bradley
• Re: populating arrays
  • From: George
• Re: iostat usage
  • From: Arjen Markus
• Re: ice melting
  • From: George
• Re: iostat usage
  • From: Mike
• Re: iostat usage
  • From: Mike
• Re: iostat usage
  • From: Arjen Markus
• Re: iostat usage
  • From: e p chandler
• Re: populating arrays
  • From: e p chandler
• iostat usage
  • From: Mike
• Re: avoiding trailing zeros
  • From: James Van Buskirk
• Re: Fortran sleep function ???
  • From: Gary Scott
• Re: looking for a strategy with segmentation fault
  • From: user1
• Re: avoiding trailing zeros
  • From: Dick Hendrickson
• Re: Fortran sleep function ???
  • From: user1
• Re: avoiding trailing zeros
  • From: Gordon Sande
• Re: avoiding trailing zeros
  • From: Gary Scott
• Re: avoiding trailing zeros
  • From: robin
• Re: avoiding trailing zeros
  • From: robin
• Re: avoiding trailing zeros
  • From: robin
• Re: Problem
  • From: Dave Allured
• Re: Problem
  • From: marek87
• Re: Problem
  • From: marek87
• Problem
  • From: marek87
• Re: populating arrays
  • From: Ron Shepard
• Re: populating arrays
  • From: user1
• Re: populating arrays
  • From: user1
• Re: Allocating/Deallocating memory for pointers (w/ Code Example)
  • From: glen herrmannsfeldt
• Re: Types with mutual references
  • From: Arjen Markus
• Re: gfortran binaries for MinGW-Win32?
  • From: e p chandler
• Re: Allocating/Deallocating memory for pointers (w/ Code Example)
  • From: Richard Otero
• Re: ice melting
  • From: George
• Re: gfortran binaries for MinGW-Win32?
  • From: George
• Re: Allocating/Deallocating memory for pointers (w/ Code Example)
  • From: robert . corbett
• Re: populating arrays
  • From: George
• Re: Types with mutual references
  • From: jel
• Re: Allocating/Deallocating memory for pointers (w/ Code Example)
  • From: Richard Otero
• Re: gfortran binaries for MinGW-Win32?
  • From: Tim Prince
• Re: avoiding trailing zeros
  • From: Michel Olagnon
• Re: Allocating/Deallocating memory for pointers (w/ Code Example)
  • From: Ian
• Re: avoiding trailing zeros
  • From: Dave Allured
• Re: avoiding trailing zeros
  • From: Dave Allured
• Allocating/Deallocating memory for pointers (w/ Code Example)
  • From: Richard Otero
• Re: gfortran binaries for MinGW-Win32?
  • From: James Van Buskirk
• Re: looking for a strategy with segmentation fault
  • From: yairsuari
• gfortran binaries for MinGW-Win32?
  • From: e p chandler
• Re: can ifort produce shared libraries that g95 can use?
  • From: Tim Prince
• Re: max number of continuation lines
  • From: Terence
• Re: avoiding trailing zeros
  • From: Terence
• can ifort produce shared libraries that g95 can use?
  • From: Matthew Halfant
• Re: avoiding trailing zeros
  • From: glen herrmannsfeldt
• Re: avoiding trailing zeros
  • From: Gordon Sande
• avoiding trailing zeros
  • From: norbert9
• Re: looking for a strategy with segmentation fault
  • From: Craig Powers
• Re: populating arrays
  • From: user1
• Re: It is a bug of lapack 3.2 or of gfortran ?
  • From: Julien Langou
• Re: max number of continuation lines
  • From: michaelmetcalf
• Re: large character strings in MS Fortran 3.31
  • From: Terence
• RE: max number of continuation lines
  • From: meek
• Re: max number of continuation lines
  • From: Terence
• Re: ice melting
  • From: Terence
• Re: WatFor77 -- Re: Command-line argument capture
  • From: Terence
• Re: (OT) old compilers and hardware
  • From: Terence
• Re: making plots
  • From: skip . knoble
• Re: WatFor77 -- Re: Command-line argument capture
  • From: Peter C. Chapin
• Re: looking for a strategy with segmentation fault
  • From: Ian Bush
• Re: looking for a strategy with segmentation fault
  • From: Arjen Markus
• Re: making plots
  • From: Arjen Markus
• Re: It is a bug of lapack 3.2 or of gfortran ?
  • From: Tim Prince
• looking for a strategy with segmentation fault
  • From: yairsuari
• Re: populating arrays
  • From: George
• Re: populating arrays
  • From: George
• It is a bug of lapack 3.2 or of gfortran ?
  • From: hes selex
• Re: ice melting
  • From: George
• Re: (OT) old compilers and hardware
  • From: user1
• Re: making plots
  • From: Luka Djigas
• Re: max number of continuation lines
  • From: jfh
• Re: making plots
  • From: David Duffy
• Re: making plots
  • From: Ian
• Re: max number of continuation lines
  • From: fj
• Re: compiler bug?
  • From: James Van Buskirk
• max number of continuation lines
  • From: Lynn McGuire
• Re: making plots
  • From: GaryScott
• Re: making plots
  • From: baf
• Re: making plots
  • From: KevinK
• making plots
  • From: Wolfi
• Re: Types with mutual references
  • From: Damian
• Re: WatFor77 -- Re: Command-line argument capture
  • From: GaryScott
• Re: Types with mutual references
  • From: jel
• Re: WatFor77 -- Re: Command-line argument capture
  • From: Kevin G. Rhoads
• Re: WatFor77 -- Re: Command-line argument capture
  • From: Kevin G. Rhoads
• Re: WatFor77 -- Re: Command-line argument capture
  • From: Kevin G. Rhoads
• Re: large character strings in MS Fortran 3.31
  • From: user1
• Re: ice melting
  • From: Jan Vorbrüggen
• Re: ice melting
  • From: Terence
• Re: Types with mutual references
  • From: Arjen Markus
• Re: compiler bug?
  • From: paul . richard . thomas
• Re: populating arrays
  • From: George
• Re: ice melting
  • From: George
• Optical Computing: special issue - Natural Computing, Springer
  • From: optical supercomputing
• Re: ice melting
  • From: Terence
• Re: ice melting
  • From: George McBane
• Re: Types with mutual references
  • From: Damian
• Re: ice melting
  • From: George McBane
• Re: populating arrays
  • From: George
• Re: a tokyo photo
  • From: George
• Re: a tokyo photo
  • From: George
• Re: ice melting
  • From: George
• Re: ice melting
  • From: George
• Re: scope of variable
  • From: Mike
• Re: ice melting
  • From: George
• Re: a tokyo photo
  • From: Steve Lionel
• Types with mutual references
  • From: Vic Kelson
• Re: compiler bug?
  • From: James Van Buskirk
• Re: ice melting
  • From: michaelmetcalf
• Re: a tokyo photo
  • From: Dan Nagle
• Re: a tokyo photo
  • From: Ian
• Re: NAG compiler and SYSTEM, ACCESS, FLUSH, etc...
  • From: Thomas Robitaille
• Re: ice melting
  • From: William Asher
• Re: compiler bug?
  • From: paul . richard . thomas
• Re: ice melting
  • From: George McBane
• Re: fmt: read unexpected character
  • From: Dave Allured
• Re: fmt: read unexpected character
  • From: Klaus Wacker
• Re: WatFor77 -- Re: Command-line argument capture
  • From: e p chandler
• Re: a tokyo photo
  • From: George
• a tokyo photo
  • From: George
• Re: ice melting
  • From: William Asher
• Re: ice melting
  • From: George
• Re: ice melting
  • From: George
• Re: WatFor77 -- Re: Command-line argument capture
  • From: user1
• Re: Command-line argument capture
  • From: John
• Re: WatFor77 -- Re: Command-line argument capture
  • From: Gary Scott
• Re: WatFor77 -- Re: Command-line argument capture
  • From: Gary Scott
• Re: WatFor77 -- Re: Command-line argument capture
  • From: Terence
• Re: WatFor77 -- Re: Command-line argument capture
  • From: e p chandler
• Re: NAG compiler and SYSTEM, ACCESS, FLUSH, etc...
  • From: Gordon Sande
• Re: WatFor77 -- Re: Command-line argument capture
  • From: user1
• Re: NAG compiler and SYSTEM, ACCESS, FLUSH, etc...
  • From: jfh
• RE: WatFor77 -- Re: Command-line argument capture
  • From: meek
• Re: Redux: Was there a negative real zero possibility in early Fortran?
  • From: glen herrmannsfeldt
• Re: Newbie F90 Question -- or may not be!
  • From: robert . corbett
• Re: NAG compiler and SYSTEM, ACCESS, FLUSH, etc...
  • From: Thomas Robitaille
• Re: WatFor77 -- Re: Command-line argument capture
  • From: GaryScott
• Re: ice melting
  • From: William Asher
• Re: NAG compiler and SYSTEM, ACCESS, FLUSH, etc...
  • From: Gordon Sande
• NAG compiler and SYSTEM, ACCESS, FLUSH, etc...
  • From: Thomas Robitaille
• ice melting
  • From: George
• Re: WatFor77 -- Re: Command-line argument capture
  • From: e p chandler
• Re: fmt: read unexpected character
  • From: Dave Allured
• Re: Fortran libraries & modules...
  • From: Steven Correll
• Re: fmt: read unexpected character
  • From: Wolfi
• Re: WatFor77 -- Re: Command-line argument capture
  • From: Kevin G. Rhoads
• Re: Fortran libraries & modules...
  • From: Tobias Burnus
• Re: WatFor77 -- Re: Command-line argument capture
  • From: user1
• RE: WatFor77 -- Re: Command-line argument capture
  • From: meek
• RE: WatFor77 -- Re: Command-line argument capture
  • From: meek
• Re: Fortran libraries & modules...
  • From: Paul van Delst
• Re: WatFor77 -- Re: Command-line argument capture
  • From: Kevin G. Rhoads
• Re: WatFor77 -- Re: Command-line argument capture
  • From: user1
• Re: BMD source program errors
  • From: robin
• Re: compiler bug?
  • From: mrestelli@xxxxxxxxx
• Re: Redux: Was there a negative real zero possibility in early Fortran?
  • From: Terence
• Re: compaq visual fortran error while executing .exe file
  • From: Arjen Markus
• Re: Unallocated Allocatable as Dummy Argument to be Allocated inside Subroutine
  • From: Ian Bush
• Re: fmt: read unexpected character
  • From: Dave Allured
• Re: compiler bug?
  • From: George
• Re: Fortran 2003
  • From: George
• Re: Newbie F90 Question -- or may not be!
  • From: Ron Shepard
• Re: Fortran 2003
  • From: George
• Re: Newbie F90 Question -- or may not be!
  • From: robert . corbett
• Re: Redux: Was there a negative real zero possibility in early Fortran?
  • From: robert . corbett
• Re: Fortran libraries & modules...
  • From: Jason Blevins
• compaq visual fortran error while executing .exe file
  • From: naveen
• Re: Fortran 2003
  • From: Gary Scott
• Newbie F90 Question -- or may not be!
  • From: jgrimmond
• Re: Fortran libraries & modules...
  • From: Paul van Delst
• Re: Fortran 2003
  • From: Paul van Delst
• WatFor77 -- Re: Command-line argument capture
  • From: Kevin G. Rhoads
• Re: Fortran libraries & modules...
  • From: Craig Powers
• Re: Command-line argument capture
  • From: Terence
• Re: fmt: read unexpected character
  • From: Wolfi
• Re: large character strings in MS Fortran 3.31
  • From: Terence
• Fortran libraries & modules...
  • From: Thomas Robitaille
• Re: BMD source program errors
  • From: Terence
• Re: compiler bug?
  • From: paul . richard . thomas
• Re: fmt: read unexpected character
  • From: Richard Maine
• Re: compiler bug?
  • From: George
• Re: Fortran Spec -- Evaluation Order
  • From: Dick Hendrickson
• Re: populating arrays
  • From: Dick Hendrickson
• Re: fmt: read unexpected character
  • From: dpb
• Re: Unallocated Allocatable as Dummy Argument to be Allocated inside Subroutine
  • From: Paul van Delst
• Re: fmt: read unexpected character
  • From: dpb
• Re: Private return type of public functions
  • From: Paul van Delst
• Re: best practices for structuring ASCII input
  • From: Dave Allured
• Re: fmt: read unexpected character
  • From: Wolfi
• Re: fmt: read unexpected character
  • From: Dave Allured
• Re: best practices for structuring ASCII input
  • From: GaryScott
• Re: best practices for structuring ASCII input
  • From: Gordon Sande
• Re: best practices for structuring ASCII input
  • From: GaryScott
• Re: best practices for structuring ASCII input
  • From: Gordon Sande
• Re: best practices for structuring ASCII input
  • From: Gary Scott
• Re: BMD source program errors
  • From: robin
• Re: compiler bug?
  • From: Tobias Burnus
• compiler bug?
  • From: mrestelli@xxxxxxxxx
• fmt: read unexpected character
  • From: Wolfi
• Re: Passing type-bound procedures as arguments?
  • From: Reinhold Bader
• Re: best practices for structuring ASCII input
  • From: Arjan
• Re: COMMON structures and text parsing
  • From: David Thompson
• Re: COMMON structures and text parsing
  • From: David Thompson
• Re: Question about initializing module variables
  • From: David Thompson
• Re: scope of variable
  • From: Jugoslav Dujic
• Re: best practices for structuring ASCII input
  • From: Arjen Markus
• large character strings in MS Fortran 3.31
  • From: e p chandler
• Re: Command-line argument capture
  • From: George
• Re: An update to the venerable command-line parser routine CRACKER() to use GET_COMMAND(3F)
  • From: George
• Re: An update to the venerable command-line parser routine CRACKER() to use GET_COMMAND(3F)
  • From: Jason Blevins
• Re: An update to the venerable command-line parser routine CRACKER() to use GET_COMMAND(3F)
  • From: Beliavsky
• Re: Command-line argument capture
  • From: Terence
• Re: Horror program uncovered from 1965!
  • From: Terence
• Re: Command-line argument capture
  • From: George
• Re: Command-line argument capture
  • From: e p chandler
• Re: best practices for structuring ASCII input
  • From: Gary Scott
• Re: Difficulty with Relatively Simple IF Structure
  • From: robin
• Re: Horror program uncovered from 1965!
  • From: robin
• Re: Difficulty with Relatively Simple IF Structure
  • From: robin
• best practices for structuring ASCII input
  • From: greg . a . fischer
• Re: Command-line argument capture
  • From: Richard Maine
• Re: Redux: Was there a negative real zero possibility in early Fortran?
  • From: Terence
• Re: Redux: Was there a negative real zero possibility in early Fortran?
  • From: Jim
• Re: Command-line argument capture
  • From: Terence
• Re: Command-line argument capture
  • From: Gordon Sande
• Re: Redux: Was there a negative real zero possibility in early Fortran?
  • From: Gordon Sande
• Re: Command-line argument capture
  • From: Terence
• Redux: Was there a negative real zero possibility in early Fortran?
  • From: Terence
• Re: Command-line argument capture
  • From: Richard Maine
• Re: Command-line argument capture
  • From: user1
• Re: Command-line argument capture
  • From: George
• Re: Command-line argument capture
  • From: Gary Scott
• Re: Command-line argument capture
  • From: Jason Blevins
• Re: Autojen määrä Kiinassa/Usa: ssa
  • From: sigvaldi
• Command-line argument capture
  • From: Terence
• Re: populating arrays
  • From: Jason Blevins
• Re: Fortran Spec -- Evaluation Order
  • From: George
• Re: Passing type-bound procedures as arguments?
  • From: Jason Blevins
• Re: populating arrays
  • From: George
• Re: Passing type-bound procedures as arguments?
  • From: Reinhold Bader
• Re: Fortran 2003
  • From: Cliff
• Re: Autojen m?r? Kiinassa/Usa: ssa
  • From: George
• Re: populating arrays
  • From: Jason Blevins
• Re: Autojen määrä Kiinassa/Usa: ssa
  • From: Jan Gerrit Kootstra
• Re: Autojen määrä Kiinassa/Usa: ssa
  • From: JB
• Passing type-bound procedures as arguments?
  • From: Jason Blevins
• Re: Fortran Spec -- Evaluation Order
  • From: Dick Hendrickson
• Re: pointer to a protected variable
  • From: Dick Hendrickson
• Re: Autojen m?r? Kiinassa/Usa: ssa
  • From: Richard Maine
• Re: Fortran 2003
  • From: Gary Scott
• Re: pointer to a protected variable
  • From: mrestelli@xxxxxxxxx
• Re: Autojen m鳵r� Kiinassa/Usa: ssa
  • From: Jan Gerrit Kootstra
• Re: read data form file
  • From: James Van Buskirk
• An update to the venerable command-line parser routine CRACKER() to use GET_COMMAND(3F)
  • From: John
• Re: Fortran 2003
  • From: George
• Re: Fortran 2003
  • From: Richard Maine
• populating arrays
  • From: George
• Re: Fortran 2003
  • From: Cliff
• Re: Fortran 2003
  • From: Damian
• Re: Fortran 2003
  • From: Simulate
• Re: Fortran 2003
  • From: Cliff
• Re: scope of variable
  • From: Richard Maine
• Re: scope of variable
  • From: Mike
• Re: computing gradient
  • From: Mike
• Re: computing gradient
  • From: Mike
• Re: Fortran 2003
  • From: Richard Maine
• Re: Autojen määrä Kiinassa/Usa: ssa
  • From: Terence
• Re: scope of variable
  • From: Richard Maine
• Fortran 2003
  • From: Cliff
• Re: scope of variable
  • From: Mike
• Re: Fortran Spec -- Evaluation Order
  • From: George
• Re: exam REVIEW...can anyone help me?
  • From: George
• Re: pointer to a protected variable
  • From: Richard Maine
• Re: pointer to a protected variable
  • From: Richard Maine
• Re: pointer to a protected variable
  • From: mrestelli@xxxxxxxxx
• Re: read data form file
  • From: Richard Maine
• Re: pointer to a protected variable
  • From: Richard Maine
• Re: exam REVIEW...can anyone help me?
  • From: GaryScott
• pointer to a protected variable
  • From: mrestelli@xxxxxxxxx
• Re: read data form file
  • From: e p chandler
• Re: exam REVIEW...can anyone help me?
  • From: Craig Powers
• Re: exam REVIEW...can anyone help me?
  • From: Richard Maine
• Re: gfortran compiler error: pointer arguments
  • From: paul . richard . thomas
• Re: gfortran compiler error: pointer arguments
  • From: paul . richard . thomas
• Re: read data form file
  • From: Dr Ivan D. Reid
• Re: exam REVIEW...can anyone help me?
  • From: GaryScott
• Re: read data form file
  • From: Jim
• Re: read data form file
  • From: Dave Allured
• Re: exam REVIEW...can anyone help me?
  • From: e p chandler
• Re: read data form file
  • From: Gordon Sande
• Re: Autojen määrä Kiinassa/Usa: ssa
  • From: Jan Gerrit Kootstra
• Re: read data form file
  • From: Richard Maine
• Re: read data form file
  • From: nakisa
• Re: exam REVIEW...can anyone help me?
  • From: Richard Maine
• Re: computing gradient
  • From: Fred
• Re: exam REVIEW...can anyone help me?
  • From: ucfjohn11
• Re: read data form file
  • From: Richard Maine
• Re: read data form file
  • From: Gordon Sande
• Re: gfortran compiler error: pointer arguments
  • From: Steven Correll
• Re: exam REVIEW...can anyone help me?
  • From: ucfjohn11
• Re: F2003 standard question: Generic resolution and passing a "string" to a character(len=1), dimension(*) dummy
  • From: Reinhold Bader
• Re: read data form file
  • From: nakisa
• Re: read data form file
  • From: Gordon Sande
• Re: read data form file
  • From: nakisa
• Re: read data form file
  • From: Alois Steindl
• Re: read data form file
  • From: nakisa
• Re: read data form file
  • From: nakisa
• Re: read data form file
  • From: Dan Nagle
• Re: read data form file
  • From: nakisa
• Re: Was there a negative real zero possibility in early Fortran?
  • From: Ron Shepard
• Re: Was there a negative real zero possibility in early Fortran?
  • From: robin
• Re: read data form file
  • From: Arjen Markus
• F2003 standard question: Generic resolution and passing a "string" to a character(len=1), dimension(*) dummy
  • From: Tobias Burnus
• read data form file
  • From: nakisa
• Re: exam REVIEW...can anyone help me?
  • From: user1
• Re: exam REVIEW...can anyone help me?
  • From: Arjen Markus
• Re: exam REVIEW...can anyone help me?
  • From: Tobias Burnus
• Re: exam REVIEW...can anyone help me?
  • From: user1
• Re: scope of variable
  • From: Jan Vorbrüggen
• Re: scope of variable
  • From: Jan Vorbrüggen
• Re: computing gradient
  • From: Dr Ivan D. Reid
• Re: gfortran compiler error: pointer arguments
  • From: sudeep
• Re: scope of variable
  • From: Mike
• Re: exam REVIEW...can anyone help me?
  • From: e p chandler
• Re: scope of variable
  • From: Mike
• Re: scope of variable
  • From: Mike
• Re: scope of variable
  • From: Mike
• computing gradient
  • From: Mike
• Re: exam REVIEW...can anyone help me?
  • From: Sjouke Burry
• Re: exam REVIEW...can anyone help me?
  • From: ucfjohn11
• Re: exam REVIEW...can anyone help me?
  • From: Gib Bogle
• Re: exam REVIEW...can anyone help me?
  • From: robin
• Re: exam REVIEW...can anyone help me?
  • From: ucfjohn11
• Re: exam REVIEW...can anyone help me?
  • From: ucfjohn11
• Re: gfortran compiler error: pointer arguments
  • From: jfh
• Re: gfortran compiler error: pointer arguments
  • From: Glen Herrmannsfeldt
• Re: scope of variable
  • From: Jan Vorbrüggen
• Re: gfortran compiler error: pointer arguments
  • From: Jan Vorbrüggen
• Re: exam REVIEW...can anyone help me?
  • From: ucfjohn11
• Re: scope of variable
  • From: AnotherSquid
• Re: gfortran compiler error: pointer arguments
  • From: fj
• Re: Passing string from fortran 90 to cpp dll
  • From: Jugoslav Dujic
• Re: exam REVIEW...can anyone help me?
  • From: e p chandler
• Re: gfortran compiler error: pointer arguments
  • From: Tobias Burnus
• Re: BMD source program errors
  • From: George
• Re: null argument
  • From: Arjen Markus
• Re: exam REVIEW...can anyone help me?
  • From: George
• Re: null argument
  • From: Richard Maine
• Re: Passing string from fortran 90 to cpp dll
  • From: Shilosh
• Re: St. Venants equation
  • From: George
• Re: exam REVIEW...can anyone help me?
  • From: Gib Bogle
• Re: scope of variable
  • From: Arjen Markus
• Re: Passing string from fortran 90 to cpp dll
  • From: Arjen Markus
• Re: scope of variable
  • From: michaelmetcalf
• scope of variable
  • From: Mike
• Re: null argument
  • From: Arjen Markus
• exam REVIEW...can anyone help me?
  • From: ucfjohn11
• Re: gfortran compiler error: pointer arguments
  • From: adda
• Re: null argument
  • From: Mike
• Re: BMD source program errors
  • From: Terence
• Passing string from fortran 90 to cpp dll
  • From: Chorev Info
• Re: FORTRAN 77 blank lines in formatted write
  • From: Terence
• Re: FORTRAN 77 blank lines in formatted write
  • From: Richard Maine
• FORTRAN 77 blank lines in formatted write
  • From: kilter
• Re: Unallocated Allocatable as Dummy Argument to be Allocated inside Subroutine
  • From: reubendb
• Re: null argument
  • From: Arjen Markus
• Re: null argument
  • From: Mike
• Re: null argument
  • From: Catherine Rees Lay
• Re: [OT] Re: null argument
  • From: Catherine Rees Lay
• Re: null argument
  • From: Mike
• Re: null argument
  • From: Mike
• Re: null argument
  • From: Mike
• Re: Private return type of public functions
  • From: Bálint Aradi
• Re: gfortran compiler error: pointer arguments
  • From: Tobias Burnus
• [OT] Re: null argument
  • From: Jugoslav Dujic
• Re: null argument
  • From: Catherine Rees Lay
• Re: Tokyo meeting
  • From: Jan Vorbrüggen
• Re: Unallocated Allocatable as Dummy Argument to be Allocated inside Subroutine
  • From: Tobias Burnus
• gfortran compiler error: pointer arguments
  • From: sudeep
• Re: Private return type of public functions
  • From: Jugoslav Dujic
• Re: null argument
  • From: Arjen Markus
• Re: null argument
  • From: Mike
• Re: null argument
  • From: Arjen Markus
• Re: null argument
  • From: Mike
• Re: BMD source program errors
  • From: e p chandler
• Re: null argument
  • From: Arjen Markus
• Re: Unallocated Allocatable as Dummy Argument to be Allocated inside Subroutine
  • From: reubendb
• null argument
  • From: Mike
• Re: general F90/F95 code to read netCDF 4.x files?
  • From: rusi_pathan
• BMD source program errors
  • From: Terence
• Unallocated Allocatable as Dummy Argument to be Allocated inside Subroutine
  • From: reubendb
• Re: why were these intrinsics in FORTRAN?
  • From: Glen Herrmannsfeldt
• Re: IOSTAT=127
  • From: nmm1
• Re: IOSTAT=127
  • From: jfh
• general F90/F95 code to read netCDF 4.x files?
  • From: Ben
• Re: why were these intrinsics in FORTRAN?
  • From: Kevin G. Rhoads
• Re: St. Venants equation
  • From: OldSchool
• Re: IOSTAT=127
  • From: tholen
• Re: St. Venants equation
  • From: fj
• Re: Does deallocate also nullify a pointer ?
  • From: nmm1
• Re: Does deallocate also nullify a pointer ?
  • From: reubendb
• Re: Private return type of public functions
  • From: Reinhold Bader
• Re: 77 to 90/95 assignment question.
  • From: B
• Re: Does deallocate also nullify a pointer ?
  • From: Richard Maine
• Re: Does deallocate also nullify a pointer ?
  • From: reubendb
• Re: Private return type of public functions
  • From: Richard Maine
• Re: Private return type of public functions
  • From: Reinhold Bader
• Re: Private return type of public functions
  • From: Bálint Aradi
• Re: Private return type of public functions
  • From: Reinhold Bader
• Re: INCLUDEing subroutines in modules
  • From: Jugoslav Dujic
• INCLUDEing subroutines in modules
  • From: deltaquattro
• Private return type of public functions
  • From: Bálint Aradi
• Private returning type of public functions
  • From: Bálint Aradi
• Re: 77 to 90/95 assignment question.
  • From: Dave Allured
• Re: 77 to 90/95 assignment question.
  • From: David Flower
• Re: Tokyo meeting
  • From: Ian Bush
• Re: 77 to 90/95 assignment question.
  • From: Dave Allured
• Re: St. Venants equation
  • From: Arjen Markus
• Re: 77 to 90/95 assignment question.
  • From: B
• Re: St. Venants equation
  • From: Richard Maine
• Re: St. Venants equation
  • From: George
• Re: Tokyo meeting
  • From: Gary Scott
• Re: 77 to 90/95 assignment question.
  • From: Richard Maine
• St. Venants equation
  • From: Mask
• 77 to 90/95 assignment question.
  • From: B
• Re: COMMON structures and text parsing
  • From: nmm1
• Re: COMMON structures and text parsing
  • From: James Van Buskirk
• Re: COMMON structures and text parsing
  • From: nmm1
• Re: why were these intrinsics in FORTRAN?
  • From: Phillip Helbig---remove CLOTHES to reply
• Re: COMMON structures and text parsing
  • From: Craig Powers
• Re: COMMON structures and text parsing
  • From: James Van Buskirk
• Re: Tokyo meeting
  • From: Steve Lionel
• Re: Wrong FORMAT statement
  • From: Steve Lionel
• Re: why were these intrinsics in FORTRAN?
  • From: Glen Herrmannsfeldt
• Re: IOSTAT=127
  • From: Glen Herrmannsfeldt
• Re: IOSTAT=127
  • From: Luksa
• Re: IOSTAT=127
  • From: tholen
• Re: why were these intrinsics in FORTRAN?
  • From: jfh
• Re: Fortran Spec -- Evaluation Order
  • From: Dave Allured
• Re: Fortran Spec -- Evaluation Order
  • From: dean . menezes
• Re: Fortran Spec -- Evaluation Order
  • From: Richard Maine
• Re: Fortran Spec -- Evaluation Order
  • From: Ron Shepard
• Re: Fortran Spec -- Evaluation Order
  • From: Dick Hendrickson
• Re: COMMON structures and text parsing
  • From: Dick Hendrickson
• Re: Fortran Spec -- Evaluation Order
  • From: dean . menezes
• Re: Wrong FORMAT statement
  • From: W. Brenig
• Re: Wrong FORMAT statement
  • From: nmm1
• Re: Wrong FORMAT statement
  • From: michaelmetcalf
• Re: Wrong FORMAT statement
  • From: Tim Prince
• Re: Wrong FORMAT statement
  • From: W. Brenig
• Re: IOSTAT=127
  • From: Charles Coldwell
• Re: IOSTAT=127
  • From: Charles Coldwell
• Re: Fortran Spec -- Evaluation Order
  • From: michaelmetcalf
• Fortran Spec -- Evaluation Order
  • From: dean . menezes
• Re: Wrong FORMAT statement
  • From: Tim Prince
• Re: Wrong FORMAT statement
  • From: michaelmetcalf
• Re: why were these intrinsics in FORTRAN?
  • From: nmm1
• Re: Wrong FORMAT statement
  • From: W. Brenig
• Re: why were these intrinsics in FORTRAN?
  • From: Dan Nagle
• Re: why were these intrinsics in FORTRAN?
  • From: nmm1
• Re: Wrong FORMAT statement
  • From: michaelmetcalf
• Re: why were these intrinsics in FORTRAN?
  • From: Dan Nagle
• Wrong FORMAT statement
  • From: W. Brenig
• Re: COMMON structures and text parsing
  • From: nmm1
• Re: why were these intrinsics in FORTRAN?
  • From: nmm1
• Re: BLOCK/END BLOCK F2008
  • From: nmm1
• Re: why were these intrinsics in FORTRAN?
  • From: Ron Shepard
• Re: BLOCK/END BLOCK F2008
  • From: Gary Scott
• Re: COMMON structures and text parsing
  • From: Ron Shepard
• Re: why were these intrinsics in FORTRAN?
  • From: George
• Re: COMMON structures and text parsing
  • From: James Van Buskirk
• Re: why were these intrinsics in FORTRAN?
  • From: Tim Prince
• Re: why were these intrinsics in FORTRAN?
  • From: Glen Herrmannsfeldt
• why were these intrinsics in FORTRAN?
  • From: e p chandler
• Re: BLOCK/END BLOCK F2008
  • From: e p chandler
• Re: fortran standard
  • From: Gary Scott
• Re: fortran standard
  • From: George
• BLOCK/END BLOCK F2008
  • From: Gary Scott
• Re: COMMON structures and text parsing
  • From: nmm1
• Re: COMMON structures and text parsing
  • From: James Van Buskirk
• Re: COMMON structures and text parsing
  • From: James Van Buskirk
• Re: IOSTAT=127
  • From: tholen
• Re: IOSTAT=127
  • From: tholen
• Re: COMMON structures and text parsing
  • From: Richard Maine
• Re: COMMON structures and text parsing
  • From: Richard Maine
• Re: COMMON structures and text parsing
  • From: Ron Shepard
• Re: COMMON structures and text parsing
  • From: nmm1
• Re: COMMON structures and text parsing
  • From: Glen Herrmannsfeldt
• Re: COMMON structures and text parsing
  • From: nmm1
• Re: COMMON structures and text parsing
  • From: Steve Lionel
• Re: COMMON structures and text parsing
  • From: Steve Lionel
• Re: COMMON structures and text parsing
  • From: Ron Shepard
• Re: COMMON structures and text parsing
  • From: nmm1
• Re: COMMON structures and text parsing
  • From: nmm1
• Re: Question about initializing module variables
  • From: nmm1
• Re: fortran standard
  • From: George
• Re: fortran standard
  • From: George
• Re: allocatable scalar in f2003
  • From: Damian
• Re: COMMON structures and text parsing
  • From: James Van Buskirk
• Re: COMMON structures and text parsing
  • From: James Van Buskirk
• Re: allocatable scalar in f2003
  • From: Richard Maine
• Re: allocatable scalar in f2003
  • From: Damian
• Re: link f77 compiled routines with f95
  • From: robert . corbett
• Re: CLASS Terminology
  • From: George
• Re: Question about initializing module variables
  • From: Glen Herrmannsfeldt
• Re: Question about initializing module variables
  • From: B
• Re: IOSTAT=127
  • From: Luksa
• Re: COMMON structures and text parsing
  • From: Dan Nagle
• Re: IOSTAT=127
  • From: nmm1
• Re: IOSTAT=127
  • From: tholen
• Re: IOSTAT=127
  • From: tholen
• Re: Using a 2-D Array
  • From: e p chandler
• Re: COMMON structures and text parsing
  • From: nmm1
• Re: COMMON structures and text parsing
  • From: Glen Herrmannsfeldt
• Re: Question about initializing module variables
  • From: nmm1
• Re: Question about initializing module variables
  • From: Arjan
• Re: Using a 2-D Array
  • From: Bobbyj124
• Re: COMMON structures and text parsing
  • From: Dick Hendrickson
• Re: Using Definition Files w/ Subroutines in a Module
  • From: brady . m . adams
• BMD07M.FOR now working!
  • From: Terence
• Re: COMMON structures and text parsing
  • From: nmm1
• Re: IOSTAT=127
  • From: Tobias Burnus
• Re: Question about initializing module variables
  • From: Gordon Sande
• Re: COMMON structures and text parsing
  • From: Steve Lionel
• Re: COMMON structures and text parsing
  • From: Steve Lionel
• Re: IOSTAT=127
  • From: nmm1
• IOSTAT=127
  • From: tholen
• Re: fortran standard
  • From: robert . corbett
• Re: Question about initializing module variables
  • From: B
• Re: Warnings and GETENV routine when using ABSOFT Fortran
  • From: bru
• Re: COMMON structures and text parsing
  • From: nmm1
• Re: fortran standard
  • From: Glen Herrmannsfeldt
• Re: fortran standard
  • From: Tobias Burnus
• fortran standard
  • From: George
• Re: Question about initializing module variables
  • From: Richard Maine
• Re: Question about initializing module variables
  • From: Glen Herrmannsfeldt
• Re: Question about initializing module variables
  • From: B
• Re: allocatable scalar in f2003
  • From: George
• Re: Using Definition Files w/ Subroutines in a Module
  • From: John Keenan
• Re: Question about initializing module variables
  • From: Richard Maine
• Re: Tokyo meeting
  • From: George
• Question about initializing module variables
  • From: B
• Re: Tokyo meeting
  • From: George
• Re: allocatable scalar in f2003
  • From: Richard Maine
• Re: Fortran 2003 Handbook
  • From: Gary Scott
• Re: Fortran 2003 Handbook
  • From: George
• Re: allocatable scalar in f2003
  • From: James Van Buskirk
• Duplicated (ignore)
  • From: Terence
• allocatable scalar in f2003
  • From: jfh
• Appeal for alternate version of BMD07M.FOR source
  • From: Terence
• Appeal for alternative source of BMD07M.FOR
  • From: Terence
• Using Definition Files w/ Subroutines in a Module
  • From: brady . m . adams
• Re: COMMON structures and text parsing
  • From: Glen Herrmannsfeldt
• Re: COMMON structures and text parsing
  • From: Steve Lionel
• Re: Random Number Generator compling
  • From: Craig Powers
• Re: Using a 2-D Array
  • From: Bobbyj124
• Re: Random Number Generator compling
  • From: Gordon Sande
• Re: Random Number Generator compling
  • From: Fred
• Random Number Generator compling
  • From: eunj
• Re: Installing Intel Fortran 90/95
  • From: Tim Prince
• Installing Intel Fortran 90/95
  • From: Dieter Britz
• Re: Installing Intel Fortran 90/95
  • From: Luksa
• Re: COMMON structures and text parsing
  • From: Charles Coldwell
• Re: COMMON structures and text parsing
  • From: robin
• Re: Horror program uncovered from 1965!
  • From: robin
• Re: calling a function once works, calling it twice fails
  • From: robin
• Re: Using a 2-D Array
  • From: Arno
• Re: COMMON structures and text parsing
  • From: nmm1
• Re: COMMON structures and text parsing
  • From: nmm1
• Re: Horror program uncovered from 1965!
  • From: Terence
• Re: COMMON structures and text parsing
  • From: Jan Vorbrüggen
• Re: COMMON structures and text parsing
  • From: Glen Herrmannsfeldt
• Re: COMMON structures and text parsing
  • From: Gary Scott
• Re: COMMON structures and text parsing
  • From: Steve Lionel
• Re: Difficulty with Relatively Simple IF Structure
  • From: e p chandler
• Re: Fortran 2003 Handbook
  • From: Dick Hendrickson
• Re: ASA Carriage Control Characters
  • From: Thomas Koenig
• Re: COMMON structures and text parsing
  • From: Glen Herrmannsfeldt
• Re: ASA Carriage Control Characters
  • From: OldSchool
• Re: COMMON structures and text parsing
  • From: GaryScott
• Re: Fortran 2003 Handbook
  • From: jfh
• Re: COMMON structures and text parsing
  • From: dpb
• Re: ASA Carriage Control Characters
  • From: Glen Herrmannsfeldt
• Re: COMMON structures and text parsing
  • From: dpb
• Re: COMMON structures and text parsing
  • From: nmm1
• Re: compiler option for local variables to default to automatic not working
  • From: Glen Herrmannsfeldt
• ASA Carriage Control Characters
  • From: McKinldj
• Re: COMMON structures and text parsing
  • From: Jan Vorbrüggen
• Re: COMMON structures and text parsing
  • From: nmm1
• Re: compiler option for local variables to default to automatic not working
  • From: Thomas Koenig
• Re: Difficulty with Relatively Simple IF Structure
  • From: monir
• Re: Horror program uncovered from 1965!
  • From: Glen Herrmannsfeldt
• Re: COMMON structures and text parsing
  • From: Glen Herrmannsfeldt
• Re: Horror program uncovered from 1965!
  • From: mecej4
• Re: Difficulty with Relatively Simple IF Structure
  • From: e p chandler
• Re: Fortran 2003 Handbook
  • From: Dick Hendrickson
• Re: Difficulty with Relatively Simple IF Structure
  • From: monir
• Procedure pointer syntax question (F2003 interpretation)
  • From: Tobias Burnus
• Re: Horror program uncovered from 1965!
  • From: James Parsly
• Re: COMMON structures and text parsing
  • From: e p chandler
• Re: g++?
  • From: Tim Prince
• Re: g++?
  • From: rusi_pathan
• Re: compiler option for local variables to default to automatic not working
  • From: Steven Correll
• Re: link f77 compiled routines with f95
  • From: user1
• Re: Difficulty with Relatively Simple IF Structure
  • From: robin
• Re: COMMON structures and text parsing
  • From: Terence
• Re: Horror program uncovered from 1965!
  • From: Terence
• Re: COMMON structures and text parsing
  • From: nmm1
• Re: link f77 compiled routines with f95
  • From: markus_helfer
• Re: calling a function once works, calling it twice fails
  • From: Catherine Rees Lay
• g++?
  • From: Dieter Britz
• Re: COMMON structures and text parsing
  • From: Glen Herrmannsfeldt
• Re: COMMON structures and text parsing
  • From: nmm1
• Re: Does deallocate also nullify a pointer ?
  • From: Richard Maine
• Re: Improving multi-dimension array access performance
  • From: Gary Scott
• Re: COMMON structures and text parsing
  • From: Gary Scott
• Re: COMMON structures and text parsing
  • From: Gary Scott
• Re: Fortran 2003 Handbook
  • From: jfh
• Re: compiler option for local variables to default to automatic not working
  • From: Craig Powers
• Re: COMMON structures and text parsing
  • From: pixel
• Re: compiler option for local variables to default to automatic not working
  • From: Glen Herrmannsfeldt
• Does deallocate also nullify a pointer ?
  • From: reubendb
• Re: Improving multi-dimension array access performance
  • From: Glen Herrmannsfeldt
• Re: COMMON structures and text parsing
  • From: dpb
• Re: Horror program uncovered from 1965!
  • From: Richard Maine
• Re: compiler option for local variables to default to automatic not working
  • From: Richard Maine
• Re: COMMON structures and text parsing
  • From: Glen Herrmannsfeldt
• Re: compiler option for local variables to default to automatic not working
  • From: Thomas Koenig
• Re: Passing Strings from C#
  • From: Vic
• Re: COMMON structures and text parsing
  • From: Terence
• Horror program uncovered from 1965!
  • From: Terence
• Re: Passing Strings from C#
  • From: Gary Scott
• Re: good intro book?
  • From: thepixelfreak
• Re: Deleting a byte at the end of a file
  • From: Dr Ivan D. Reid
• Re: Deleting a byte at the end of a file
  • From: user1
• Re: Passing Strings from C#
  • From: Vic
• Re: Passing Strings from C#
  • From: Vic
• Re: Passing Strings from C#
  • From: Vic
• Re: Passing Strings from C#
  • From: Gary Scott
• Re: Passing Strings from C#
  • From: Vic
• Re: Deleting a byte at the end of a file
  • From: nmm1
• Re: Deleting a byte at the end of a file
  • From: Gary Scott
• Re: Deleting a byte at the end of a file
  • From: Richard Maine
• Re: Deleting a byte at the end of a file
  • From: Lorents
• Re: Deleting a byte at the end of a file
  • From: Lorents
• Re: Passing Strings from C#
  • From: Gary Scott
• Passing Strings from C#
  • From: Vic
• Re: Fortran 2003 Handbook
  • From: Dick Hendrickson
• Re: Deleting a byte at the end of a file
  • From: Gary Scott
• Re: Deleting a byte at the end of a file
  • From: Luksa
• Re: Deleting a byte at the end of a file
  • From: Gary Scott
• Re: COMMON structures and text parsing
  • From: nmm1
• Re: Deleting a byte at the end of a file
  • From: Gary Scott
• Deleting a byte at the end of a file
  • From: Lorents
• Re: COMMON structures and text parsing
  • From: Gary Scott
• Re: Tokyo meeting
  • From: Gary Scott
• Re: COMMON structures and text parsing
  • From: Gary Scott
• Re: COMMON structures and text parsing
  • From: nmm1
• Re: COMMON structures and text parsing
  • From: Glen Herrmannsfeldt
• Re: COMMON structures and text parsing
  • From: e p chandler
• Re: COMMON structures and text parsing
  • From: Glen Herrmannsfeldt
• Re: COMMON structures and text parsing
  • From: Terence
• Re: COMMON structures and text parsing
  • From: Glen Herrmannsfeldt
• Re: Tokyo meeting
  • From: nmm1
• Re: link f77 compiled routines with f95
  • From: robert . corbett
• Re: COMMON structures and text parsing
  • From: e p chandler
• COMMON structures and text parsing
  • From: Terence
• Re: Tokyo meeting
  • From: Gary Scott
• Re: Tokyo meeting
  • From: George
• Re: good intro book?
  • From: rudra
• Re: reducing the size of an array w/o using twice the memory ?
  • From: Terence
• Re: The Fortran 2003 Handbook
  • From: Gary Scott
• conjunction junction
  • From: George
• Re: Fortran 2003 Handbook
  • From: George
• Re: The Fortran 2003 Handbook
  • From: George
• Re: CLASS Terminology
  • From: Reinhold Bader
• good intro book?
  • From: thepixelfreak
• Re: CLASS Terminology
  • From: George
• Re: Using a 2-D Array
  • From: dpb
• Re: link f77 compiled routines with f95
  • From: George
• Re: The Fortran 2003 Handbook
  • From: dpb
• Re: Using a 2-D Array
  • From: George
• Re: The Fortran 2003 Handbook
  • From: George
• Fortran 2003 Handbook
  • From: jfh
• Re: The Fortran 2003 Handbook
  • From: Gary Scott
• Re: CLASS Terminology
  • From: Gary Scott
• Re: CLASS Terminology
  • From: George
• Re: Tokyo meeting
  • From: Steve Lionel
• Re: The Fortran 2003 Handbook
  • From: George
• Re: CLASS Terminology
  • From: George
• Re: Threads [was Re: Final Procedure]
  • From: Gary Scott
• Re: Threads [was Re: Final Procedure]
  • From: nmm1
• Re: Using a 2-D Array
  • From: Bobbyj124
• Re: link f77 compiled routines with f95
  • From: user1
• Re: Threads [was Re: Final Procedure]
  • From: Gary Scott
• Re: Threads [was Re: Final Procedure]
  • From: Gary Scott
• Re: Threads [was Re: Final Procedure]
  • From: Dan Nagle
• Re: Using a 2-D Array
  • From: Mark Westwood
• Using a 2-D Array
  • From: Bobbyj124
• Re: Tokyo meeting
  • From: Walter Spector
• Re: link f77 compiled routines with f95
  • From: Richard Maine
• Re: Threads [was Re: Final Procedure]
  • From: Richard Maine
• Re: reducing the size of an array w/o using twice the memory ?
  • From: Glen Herrmannsfeldt
• Re: Threads [was Re: Final Procedure]
  • From: Gary Scott
• Re: Threads [was Re: Final Procedure]
  • From: nmm1
• Re: reducing the size of an array w/o using twice the memory ?
  • From: robin
• Re: Threads [was Re: Final Procedure]
  • From: Dan Nagle
• Re: subroytine not linking
  • From: nmm1
• Re: subroytine not linking
  • From: e p chandler
• Re: subroytine not linking
  • From: Arjen Markus
• Re: subroytine not linking
  • From: Tobias Burnus
• Re: calling a function once works, calling it twice fails
  • From: henadas81
• subroytine not linking
  • From: henadas81
• link f77 compiled routines with f95
  • From: markus_helfer
• Re: fortran and hex readers
  • From: e p chandler
• Re: Array declaration in files
  • From: Arjen Markus
• Re: PROCEDURE with implicit interface as actual argument
  • From: Glen Herrmannsfeldt
• Re: PROCEDURE with implicit interface as actual argument
  • From: paul . richard . thomas
• Re: fortran and hex readers
  • From: Glen Herrmannsfeldt
• Re: The Fortran 2003 Handbook
  • From: Richard Maine
• The Fortran 2003 Handbook
  • From: Gary Scott
• Re: PROCEDURE with implicit interface as actual argument
  • From: Richard Maine
• Re: PROCEDURE with implicit interface as actual argument
  • From: Richard Maine
• Re: RAM access limits under 64bit
  • From: Steve Lionel
• Re: Square root of a negative real value and other war stories
  • From: Terence
• Re: PROCEDURE with implicit interface as actual argument
  • From: Glen Herrmannsfeldt
• Re: PROCEDURE with implicit interface as actual argument
  • From: Tobias Burnus
• Re: RAM access limits under 64bit
  • From: rrr7rrr

• Security
• UNIX
• Linux
• Coding
• Usenet

• Archive
• About
• Privacy
• Search
• Imprint

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