comp.lang.fortran

• Thread Index

---

• Re: IF statements
  • From: Gus Gassmann
• Re: re-using fortran dll in VS2005
  • From: ioson
• Re: IF statements
  • From: smurray444
• -byteswapio
  • From: kartadikaria
• -byteswapio
  • From: kartadikaria
• Re: Open64 Not Setting World on Fire: Why?
  • From: steven . bosscher
• Re: compaq visual fortran, process pririty mangement option
  • From: louisJ
• Re: Fortran assumed-shape array problems with MPI
  • From: glen herrmannsfeldt
• Re: Fortran assumed-shape array problems with MPI
  • From: Jane Smith
• Re: unknown problem
  • From: nakisa
• Re: Fortran assumed-shape array problems with MPI
  • From: Michael Metcalf
• Re: Fortran assumed-shape array problems with MPI
  • From: Jane Smith
• Re: Fortran assumed-shape array problems with MPI
  • From: Jane Smith
• Re: Fortran assumed-shape array problems with MPI
  • From: glen herrmannsfeldt
• Re: Running Windows Programs from Fortran
  • From: Tim Prince
• Re: re-using fortran dll in VS2005
  • From: max
• Re: Running Windows Programs from Fortran
  • From: max
• Re: SALFORD ERROR?
  • From: Edward N Bromhead
• Re: Fortran assumed-shape array problems with MPI
  • From: glen herrmannsfeldt
• Re: Fortran assumed-shape array problems with MPI
  • From: Jane Smith
• Re: Running Windows Programs from Fortran
  • From: Beliavsky
• Running Windows Programs from Fortran
  • From: tuli
• Re: overloaded cant be distinguished by return values?
  • From: James Giles
• Re: overloaded cant be distinguished by return values?
  • From: glen herrmannsfeldt
• Fortran assumed-shape array problems with MPI
  • From: Jane Smith
• re-using fortran dll in VS2005
  • From: ioson
• Re: F77 & WIN XP
  • From: Thierry Boudet
• Re: compaq visual fortran, process pririty mangement option
  • From: dpb
• Re: compaq visual fortran, process pririty mangement option
  • From: dpb
• Re: SALFORD ERROR
  • From: Herman D . Knoble
• Re: SALFORD ERROR
  • From: Big D
• compaq visual fortran, process pririty mangement option
  • From: louisJ
• Re: F77 & WIN XP
  • From: Big D
• Re: overloaded cant be distinguished by return values?
  • From: Reinhold Bader
• Re: F77 & WIN XP
  • From: Big D
• Re: F77 & WIN XP
  • From: Hani Ibrahim
• Re: overloaded cant be distinguished by return values?
  • From: gary . l . scott
• Re: strange arguments passing problem (from vba to fortran dll)
  • From: dpb
• Re: overloaded cant be distinguished by return values?
  • From: Richard Edgar
• Re: F77 & WIN XP
  • From: Kevin G. Rhoads
• Re: overloaded cant be distinguished by return values?
  • From: Michael Metcalf
• overloaded cant be distinguished by return values?
  • From: Berthold Höllmann
• Re: strange arguments passing problem (from vba to fortran dll)
  • From: dpb
• Re: trailing double underscores
  • From: Carlie J. Coats
• Re: IF statements
  • From: Terence
• Re: F77 & WIN XP
  • From: Terence
• Re: strange arguments passing problem (from vba to fortran dll)
  • From: Brooks Moses
• Re: strange arguments passing problem (from vba to fortran dll)
  • From: Arjen Markus
• Re: F77 & WIN XP
  • From: jwm
• Re: reading file
  • From: Big D
• Re: strange arguments passing problem (from vba to fortran dll)
  • From: Brooks Moses
• F77 & WIN XP
  • From: Big D
• Re: user-defined alignment in gfortran
  • From: Pierre Asselin
• Re: IF statements
  • From: Terence
• Re: Salford Fortran - Double Precision product
  • From: glen herrmannsfeldt
• Re: IF statements
  • From: Terence
• Re: I am looking for library from Lahey Fortran 95 v.5.5
  • From: Terence
• Re: user-defined alignment in gfortran
  • From: Timo Schneider
• Re: strange arguments passing problem (from vba to fortran dll)
  • From: formulae translator
• Re: Salford Fortran - Double Precision product
  • From: Edward N Bromhead
• Re: user-defined alignment in gfortran
  • From: Louis Krupp
• Re: IF statements
  • From: smurray444
• Re: I am looking for library from Lahey Fortran 95 v.5.5
  • From: marmaz
• Re: I am looking for library from Lahey Fortran 95 v.5.5
  • From: Herman D . Knoble
• Re: IF statements
  • From: dpb
• Re: strange arguments passing problem (from vba to fortran dll)
  • From: Louis Krupp
• I am looking for library from Lahey Fortran 95 v.5.5
  • From: marmaz
• Re: user-defined alignment in gfortran
  • From: Timo Schneider
• Re: strange arguments passing problem (from vba to fortran dll)
  • From: formulae translator
• Re: IF statements
  • From: Gus Gassmann
• RE: IF statements
  • From: meek
• Re: IF statements
  • From: Beliavsky
• IF statements
  • From: smurray444
• Re: user-defined alignment in gfortran
  • From: Steven G. Kargl
• Re: user-defined alignment in gfortran
  • From: Timo Schneider
• OT: Re: newbie question for reading input file
  • From: Paul van Delst
• Re: user-defined alignment in gfortran
  • From: Timo Schneider
• Re: user-defined alignment in gfortran
  • From: Timo Schneider
• Re: user-defined alignment in gfortran
  • From: Richard Maine
• Re: user-defined alignment in gfortran
  • From: Tim Prince
• Re: user-defined alignment in gfortran
  • From: Tim Prince
• Re: user-defined alignment in gfortran
  • From: glen herrmannsfeldt
• Re: user-defined alignment in gfortran
  • From: Timo Schneider
• Re: user-defined alignment in gfortran
  • From: glen herrmannsfeldt
• Re: user-defined alignment in gfortran
  • From: Timo Schneider
• Re: strange arguments passing problem (from vba to fortran dll)
  • From: Arjen Markus
• Re: user-defined alignment in gfortran
  • From: Tim Prince
• Re: user-defined alignment in gfortran
  • From: Dr Ivan D. Reid
• user-defined alignment in gfortran
  • From: Timo Schneider
• strange arguments passing problem (from vba to fortran dll)
  • From: formulae translator
• Re: unknown problem
  • From: Richard Maine
• Re: unknown problem
  • From: e p chandler
• Re: unknown problem
  • From: nakisa
• Re: "init.c: No such file or directory."
  • From: Jane Smith
• Re: Salford Fortran - Double Precision product
  • From: Gordon Sande
• Re: Salford Fortran - Double Precision product
  • From: Richard Maine
• Re: Salford Fortran - Double Precision product
  • From: Edward N Bromhead
• Re: internal read of character array. F/ifort differences
  • From: dpb
• Re: ICEs "normal" in Gfortran
  • From: FX
• RE: reading file
  • From: meek
• Re: "init.c: No such file or directory."
  • From: Louis Krupp
• Re: "init.c: No such file or directory."
  • From: Louis Krupp
• Re: internal read of character array. F/ifort differences
  • From: David Simpson
• Re: unknown problem
  • From: nakisa
• Re: "init.c: No such file or directory."
  • From: Jane Smith
• Re: Segmentation Fault - How can you detect?
  • From: Richard Maine
• Re: unknown problem
  • From: e p chandler
• Re: Segmentation Fault - How can you detect?
  • From: Gary Scott
• Re: Segmentation Fault - How can you detect?
  • From: Terence
• Re: "init.c: No such file or directory."
  • From: Richard Maine
• Re: internal read of character array. F/ifort differences
  • From: Richard Maine
• Re: Salford Fortran - Double Precision product
  • From: Gordon Sande
• Re: Segmentation Fault - How can you detect?
  • From: Richard Maine
• Re: Salford Fortran - Double Precision product
  • From: Richard Maine
• Re: reading file
  • From: dpb
• Re: Salford Fortran - Double Precision product
  • From: Edward N Bromhead
• Re: Speed versus memory
  • From: Gabe
• Re: F90 to C interface
  • From: Sebastian Hanigk
• F90 to C interface
  • From: Tim Springer
• Re: ICEs "normal" in Gfortran
  • From: FX
• Re: "init.c: No such file or directory."
  • From: Louis Krupp
• Re: internal read of character array. F/ifort differences
  • From: David Simpson
• Re: Segmentation Fault - How can you detect?
  • From: Terence
• Re: reading file
  • From: Terence
• Re: "init.c: No such file or directory."
  • From: Terence
• "init.c: No such file or directory."
  • From: Jane Smith
• Re: reading file
  • From: David Frank
• Re: Segmentation Fault - How can you detect?
  • From: claire
• Re: reading file
  • From: gsal
• Re: newbie question for reading input file
  • From: Richard Maine
• Re: newbie question for reading input file
  • From: James Van Buskirk
• Re: compiler flags for gfortran on Intel Xeon 64-bit wkstation
  • From: James Van Buskirk
• Re: Segmentation Fault - How can you detect?
  • From: claire
• Re: Segmentation Fault - How can you detect?
  • From: claire
• Re: Salford Fortran - Double Precision product
  • From: Richard Maine
• Re: Salford Fortran - Double Precision product
  • From: Edward N Bromhead
• Re: Speed versus memory
  • From: Richard Maine
• Re: Speed versus memory
  • From: Beliavsky
• Re: unknown problem
  • From: James Giles
• Re: internal read of character array. F/ifort differences
  • From: Beliavsky
• Re: unknown problem
  • From: e p chandler
• Re: Speed versus memory
  • From: Richard Maine
• Re: Speed versus memory
  • From: Gabe
• Re: unknown problem
  • From: James Giles
• Re: internal read of character array. F/ifort differences
  • From: glen herrmannsfeldt
• Re: unknown problem
  • From: e p chandler
• Re: internal read of character array. F/ifort differences
  • From: Richard Maine
• Re: Open64 Not Setting World on Fire: Why?
  • From: max
• Re: Open64 Not Setting World on Fire: Why?
  • From: Steven G. Kargl
• Re: Open64 Not Setting World on Fire: Why?
  • From: Gary Scott
• Re: reading file
  • From: David Simpson
• Re: unknown problem
  • From: nakisa
• Re: reading file
  • From: thinktank
• Re: reading file
  • From: zyf
• reading file
  • From: thinktank
• internal read of character array. F/ifort differences
  • From: David Simpson
• Re: Speed versus memory
  • From: Sebastian Hanigk
• Re: Segmentation Fault - How can you detect?
  • From: Janne Blomqvist
• Re: Segmentation Fault - How can you detect?
  • From: claire
• Re: Open64 Not Setting World on Fire: Why?
  • From: Brooks Moses
• Re: Open64 Not Setting World on Fire: Why?
  • From: Brooks Moses
• Re: Open64 Not Setting World on Fire: Why?
  • From: James Giles
• Re: Open64 Not Setting World on Fire: Why?
  • From: Brooks Moses
• Re: Segmentation Fault - How can you detect?
  • From: claire
• Re: ICEs "normal" in Gfortran
  • From: Steven G. Kargl
• Re: ICEs "normal" in Gfortran
  • From: Steven G. Kargl
• Re: Open64 Not Setting World on Fire: Why?
  • From: James Giles
• Re: Open64 Not Setting World on Fire: Why?
  • From: James Giles
• Re: Open64 Not Setting World on Fire: Why?
  • From: Gary Scott
• Re: Open64 Not Setting World on Fire: Why?
  • From: Quadibloc
• Re: Segmentation Fault - How can you detect?
  • From: claire
• Re: Open64 Not Setting World on Fire: Why?
  • From: Quadibloc
• Re: Open64 Not Setting World on Fire: Why?
  • From: Quadibloc
• Re: Open64 Not Setting World on Fire: Why?
  • From: James Giles
• Re: unknown problem
  • From: e p chandler
• Re: Open64 Not Setting World on Fire: Why?
  • From: Richard Maine
• Re: ICEs "normal" in Gfortran
  • From: Beliavsky
• Re: Segmentation Fault - How can you detect?
  • From: claire
• Re: Open64 Not Setting World on Fire: Why?
  • From: James Giles
• ICEs "normal" in Gfortran
  • From: awgreynolds
• Re: unknown problem
  • From: Terence
• Re: IVF vs CVF on P4; EXE Speed ?
  • From: Terence
• Re: Speed versus memory
  • From: glen herrmannsfeldt
• Re: Lower index bound confusion
  • From: glen herrmannsfeldt
• Re: printing matrix
  • From: Carramba
• Re: IVF vs CVF on P4; EXE Speed ?
  • From: Dr Ivan D. Reid
• Re: Segmentation Fault - How can you detect?
  • From: Beliavsky
• Re: Speed versus memory
  • From: Richard Maine
• Segmentation Fault - How can you detect?
  • From: claire
• Re: Open64 Not Setting World on Fire: Why?
  • From: Gary Scott
• Re: Open64 Not Setting World on Fire: Why?
  • From: Michael Prager
• Re: printing matrix
  • From: glen herrmannsfeldt
• IVF vs CVF on P4; EXE Speed ?
  • From: Jim Klein
• Re: Lower index bound confusion
  • From: James Giles
• Re: printing matrix
  • From: Beliavsky
• printing matrix
  • From: Carramba
• Re: Lower index bound confusion
  • From: glen herrmannsfeldt
• Speed versus memory
  • From: Gabe
• Re: Open64 Not Setting World on Fire: Why?
  • From: Richard Maine
• Re: newbie question for reading input file
  • From: glen herrmannsfeldt
• Re: Open64 Not Setting World on Fire: Why?
  • From: Beliavsky
• Re: Open64 Not Setting World on Fire: Why?
  • From: Gary Scott
• Re: Open64 Not Setting World on Fire: Why?
  • From: Gary Scott
• Re: Segmentation fault caused by write(6,*)
  • From: Richard Maine
• Re: Salford Fortran - Double Precision product
  • From: Jorge Lopez
• Re: Salford Fortran - Double Precision product
  • From: Jorge Lopez
• Re: Salford Fortran - Double Precision product
  • From: Jorge Lopez
• unknown problem
  • From: nakisa
• Re: newbie question for reading input file
  • From: glen herrmannsfeldt
• Re: Lower index bound confusion
  • From: Dick Hendrickson
• Re: Salford Fortran - Double Precision product
  • From: Arjen Markus
• Re: Salford Fortran - Double Precision product
  • From: Ron Shepard
• Re: Salford Fortran - Double Precision product
  • From: glen herrmannsfeldt
• Re: newbie question for reading input file
  • From: Jan Vorbrüggen
• Re: many "ifs" versus linked list of true cases
  • From: Mark Morss
• Re: Lower index bound confusion
  • From: highegg
• Re: Lower index bound confusion
  • From: Kurt
• Re: newbie question for reading input file
  • From: Michael Metcalf
• Re: newbie question for reading input file
  • From: Tim Prince
• Re: newbie question for reading input file
  • From: www
• Re: Lower index bound confusion
  • From: highegg
• Re: Lower index bound confusion
  • From: Kurt
• Re: Salford Fortran - Double Precision product
  • From: Daniel Snouck
• Re: Help with Developing a GUI for Fortran program
  • From: nikhil . kavimandan
• Re: Salford Fortran - Double Precision product
  • From: Michel Olagnon
• Re: Salford Fortran - Double Precision product
  • From: Klaus Wacker
• Re: Salford Fortran - Double Precision product
  • From: highegg
• Salford Fortran - Double Precision product
  • From: Jorge Lopez
• Re: pretty output using Fortran
  • From: Catherine Rees Lay
• Re: Lower index bound confusion
  • From: Arjen Markus
• Re: Lower index bound confusion
  • From: highegg
• Lower index bound confusion
  • From: Kurt
• Re: compiler flags for gfortran on Intel Xeon 64-bit wkstation
  • From: FX
• RE: newbie question for reading input file
  • From: meek
• Re: Segmentation fault caused by write(6,*)
  • From: Patrick Begou
• Re: Neq Max Limit
  • From: glen herrmannsfeldt
• Re: Open64 Not Setting World on Fire: Why?
  • From: Tim Prince
• Re: OpenMP problem
  • From: alesok
• Re: Open64 Not Setting World on Fire: Why?
  • From: stevenb . gcc
• Re: Open64 Not Setting World on Fire: Why?
  • From: robert . corbett
• Re: Neq Max Limit
  • From: e p chandler
• Re: Neq Max Limit
  • From: Hosley
• Re: Open64 Not Setting World on Fire: Why?
  • From: Quadibloc
• Re: Open64 Not Setting World on Fire: Why?
  • From: Quadibloc
• Re: ALLOCATABLE or POINTER
  • From: glen herrmannsfeldt
• Re: "typedef" in F95/2003?
  • From: glen herrmannsfeldt
• Re: Neq Max Limit
  • From: e p chandler
• Re: ALLOCATABLE or POINTER
  • From: James Giles
• Re: Neq Max Limit
  • From: Terence
• Re: ALLOCATABLE or POINTER
  • From: James Giles
• Neq Max Limit
  • From: Hosley
• Re: ALLOCATABLE or POINTER
  • From: glen herrmannsfeldt
• Re: "typedef" in F95/2003?
  • From: Ken Fairfield
• Re: ALLOCATABLE or POINTER
  • From: James Giles
• Re: newbie question for reading input file
  • From: glen herrmannsfeldt
• Re: gcc fortran matmul
  • From: Steven G. Kargl
• Re: newbie question for reading input file
  • From: Richard Maine
• newbie question for reading input file
  • From: www
• Re: linking to cernlib (mathlib) with gfortran
  • From: Dr Ivan D. Reid
• Re: Open64 Not Setting World on Fire: Why?
  • From: Steve Lionel
• Re: Open64 Not Setting World on Fire: Why?
  • From: Beliavsky
• Re: "typedef" in F95/2003?
  • From: Chip Coldwell
• Re: "typedef" in F95/2003?
  • From: Paul van Delst
• Re: Open64 Not Setting World on Fire: Why?
  • From: Brooks Moses
• Re: "typedef" in F95/2003?
  • From: Chip Coldwell
• Re: Open64 Not Setting World on Fire: Why?
  • From: max
• Re: "typedef" in F95/2003?
  • From: ian_d_chivers
• Re: compiler flags for gfortran on Intel Xeon 64-bit wkstation
  • From: Tobias Burnus
• Re: gcc fortran matmul
  • From: max
• Re: compiler flags for gfortran on Intel Xeon 64-bit wkstation
  • From: Rich Townsend
• Re: "typedef" in F95/2003?
  • From: Richard Maine
• compiler flags for gfortran on Intel Xeon 64-bit wkstation
  • From: mjm2114
• Re: "typedef" in F95/2003?
  • From: Chip Coldwell
• Re: "typedef" in F95/2003?
  • From: Jan Vorbrüggen
• Re: "typedef" in F95/2003?
  • From: Chip Coldwell
• Re: "typedef" in F95/2003?
  • From: Bart Vandewoestyne
• Re: Software structure analysis
  • From: David Jones
• Re: Software structure analysis
  • From: Terence
• Re: ALLOCATABLE or POINTER
  • From: fj
• Re: ALLOCATABLE or POINTER
  • From: fj
• Re: "typedef" in F95/2003?
  • From: Jan Vorbrüggen
• Re: ALLOCATABLE or POINTER
  • From: Jan Vorbrüggen
• Re: gcc fortran matmul
  • From: highegg
• Re: trailing double underscores
  • From: Fly Away
• gcc fortran matmul
  • From: Gunnar G
• Re: "typedef" in F95/2003?
  • From: Brooks Moses
• Re: "typedef" in F95/2003?
  • From: Richard Maine
• Re: "typedef" in F95/2003?
  • From: Brooks Moses
• Re: conversion of floating point constants
  • From: Ron Shepard
• Re: "typedef" in F95/2003?
  • From: Brooks Moses
• Re: "typedef" in F95/2003?
  • From: Chip Coldwell
• Re: trailing double underscores
  • From: robert . corbett
• Re: "typedef" in F95/2003?
  • From: Richard Maine
• Re: ALLOCATABLE or POINTER
  • From: James Giles
• Re: "typedef" in F95/2003?
  • From: Chip Coldwell
• Re: Segmentation fault caused by write(6,*)
  • From: Terence
• Re: linking to cernlib (mathlib) with gfortran
  • From: Edelstatist
• Re: linking to cernlib (mathlib) with gfortran
  • From: Edelstatist
• Re: linking to cernlib (mathlib) with gfortran
  • From: Edelstatist
• Re: linking C functions...
  • From: Craig Powers
• Re: trailing double underscores
  • From: Carlie J. Coats
• Re: "typedef" in F95/2003?
  • From: John Harper
• Re: trailing double underscores
  • From: Carlie J. Coats
• Re: "typedef" in F95/2003?
  • From: Chip Coldwell
• Re: "typedef" in F95/2003?
  • From: Richard Maine
• Re: "typedef" in F95/2003?
  • From: Chip Coldwell
• Re: linking to cernlib (mathlib) with gfortran
  • From: Dr Ivan D. Reid
• Re: "typedef" in F95/2003?
  • From: glen herrmannsfeldt
• Re: [g77/x86_64 arch] linking C functions...
  • From: glen herrmannsfeldt
• Re: "typedef" in F95/2003?
  • From: Richard Maine
• Re: ALLOCATABLE or POINTER
  • From: glen herrmannsfeldt
• Re: "typedef" in F95/2003?
  • From: Chip Coldwell
• Re: linking to cernlib (mathlib) with gfortran
  • From: Dr Ivan D. Reid
• Re: "typedef" in F95/2003?
  • From: Richard Maine
• Re: [g77/x86_64 arch] linking C functions...
  • From: James Van Buskirk
• Re: Segmentation fault caused by write(6,*)
  • From: Richard Maine
• Re: ALLOCATABLE or POINTER
  • From: Richard Maine
• "typedef" in F95/2003?
  • From: Chip Coldwell
• Re: conversion of floating point constants
  • From: Ron Shepard
• Re: trailing double underscores
  • From: Steven Correll
• Re: trailing double underscores
  • From: Steven Correll
• Re: linking to cernlib (mathlib) with gfortran
  • From: Edelstatist
• Re: linking to cernlib (mathlib) with gfortran
  • From: Edelstatist
• Re: linking to cernlib (mathlib) with gfortran
  • From: Edelstatist
• Re: ALLOCATABLE or POINTER
  • From: fj
• Re: Segmentation fault caused by write(6,*)
  • From: Nym
• Re: linking to cernlib (mathlib) with gfortran
  • From: Dr Ivan D. Reid
• Re: Software structure analysis
  • From: Arjen Markus
• Re: Segmentation fault caused by write(6,*)
  • From: dpb
• Re: conversion of floating point constants
  • From: dpb
• linking to cernlib (mathlib) with gfortran
  • From: Edelstatist
• Re: Software structure analysis
  • From: Beliavsky
• Re: trailing double underscores
  • From: Beliavsky
• Re: conversion of floating point constants
  • From: Herman D . Knoble
• Re: ALLOCATABLE or POINTER
  • From: Jan Vorbrüggen
• Re: [g77/x86_64 arch] linking C functions...
  • From: glen herrmannsfeldt
• Re: linking C functions...
  • From: glen herrmannsfeldt
• Re: [g77/x86_64 arch] linking C functions...
  • From: glen herrmannsfeldt
• Re: trailing double underscores
  • From: robert . corbett
• Re: linking C functions...
  • From: robert . corbett
• Re: linking C functions...
  • From: robert . corbett
• Re: [g77/x86_64 arch] linking C functions...
  • From: Michel Olagnon
• Re: linking C functions...
  • From: robert . corbett
• Re: linking C functions...
  • From: Arjen Markus
• Re: linking C functions...
  • From: robert . corbett
• Re: linking C functions...
  • From: robert . corbett
• Re: linking C functions...
  • From: robert . corbett
• Re: ALLOCATABLE or POINTER
  • From: fj
• Re: ALLOCATABLE or POINTER
  • From: fj
• Re: linking C functions...
  • From: Michel Olagnon
• Re: linking C functions...
  • From: Arjen Markus
• Re: ALLOCATABLE or POINTER
  • From: Jan Vorbrüggen
• Re: c = inverse(sqrt(epsilon nought *mu nought))
  • From: Jan Vorbrüggen
• Re: linking C functions...
  • From: Arjen Markus
• Re: linking C functions...
  • From: Arjen Markus
• Re: linking C functions...
  • From: Arjen Markus
• Re: linking C functions...
  • From: robert . corbett
• Re: linking C functions...
  • From: robert . corbett
• Re: trailing double underscores
  • From: Jan Vorbrüggen
• Re: ALLOCATABLE or POINTER
  • From: highegg
• Re: ALLOCATABLE or POINTER
  • From: highegg
• Re: ALLOCATABLE or POINTER
  • From: highegg
• Re: ALLOCATABLE or POINTER
  • From: highegg
• Re: ALLOCATABLE or POINTER
  • From: highegg
• Re: OpenMP problem
  • From: fj
• Re: trailing double underscores
  • From: robert . corbett
• Re: trailing double underscores
  • From: robert . corbett
• Re: trailing double underscores
  • From: robert . corbett
• Re: ALLOCATABLE or POINTER
  • From: fj
• Re: trailing double underscores
  • From: Janne Blomqvist
• conversion of floating point constants
  • From: Ron Shepard
• Re: trailing double underscores
  • From: Craig Powers
• Re: c = inverse(sqrt(epsilon nought *mu nought))
  • From: John Harper
• Re: trailing double underscores
  • From: Gary Scott
• Re: trailing double underscores
  • From: Fly Away
• Re: trailing double underscores
  • From: Fly Away
• Re: c = inverse(sqrt(epsilon nought *mu nought))
  • From: glen herrmannsfeldt
• Re: trailing double underscores
  • From: glen herrmannsfeldt
• Re: trailing double underscores
  • From: Tim Prince
• Re: c = inverse(sqrt(epsilon nought *mu nought))
  • From: Wade Ward
• Re: c = inverse(sqrt(epsilon nought *mu nought))
  • From: Wade Ward
• Re: trailing double underscores
  • From: Richard Maine
• Re: Segmentation fault caused by write(6,*)
  • From: Richard Maine
• Re: trailing double underscores
  • From: Craig Powers
• Re: Function sees variables incorrectly.
  • From: Richard Maine
• Re: trailing double underscores
  • From: Fly Away
• Segmentation fault caused by write(6,*)
  • From: Kurda Yon
• Re: Function sees variables incorrectly.
  • From: Dick Hendrickson
• Re: Function sees variables incorrectly.
  • From: Richard Maine
• Re: xlf compiler bug?
  • From: Richard Maine
• Re: trailing double underscores
  • From: mecej4
• Re: Function sees variables incorrectly.
  • From: Rich Townsend
• Function sees variables incorrectly.
  • From: Kurda Yon
• Re: trailing double underscores
  • From: gary . l . scott
• Re: trailing double underscores
  • From: Steve Lionel
• Re: xlf compiler bug?
  • From: Googleer
• Re: xlf compiler bug?
  • From: Googleer
• Re: trailing double underscores
  • From: Steve Lionel
• Re: Software structure analysis
  • From: Arjen Markus
• Re: trailing double underscores
  • From: Richard Maine
• Re: trailing double underscores
  • From: gary . l . scott
• Re: ALLOCATABLE or POINTER
  • From: Richard Maine
• Re: trailing double underscores
  • From: Ian Bush
• Re: Software structure analysis
  • From: Arjen Markus
• Re: Software structure analysis
  • From: Beliavsky
• Re: trailing double underscores
  • From: Tim Prince
• Re: Open64 not setting world on fire
  • From: John Savard
• Open64 Not Setting World on Fire: Why?
  • From: Quadibloc
• Open64 not setting world on fire
  • From: Quadibloc
• Software structure analysis
  • From: G.T.
• Re: how to find IMSL library?
  • From: linuxl4 . fox
• Re: how to find IMSL library?
  • From: linuxl4 . fox
• Re: ALLOCATABLE or POINTER
  • From: highegg
• Re: xlf compiler bug?
  • From: Gib Bogle
• Re: xlf compiler bug?
  • From: Ian Bush
• Re: c = inverse(sqrt(epsilon nought *mu nought))
  • From: Jan Vorbrüggen
• Re: ALLOCATABLE or POINTER
  • From: fj
• Re: ALLOCATABLE or POINTER
  • From: Jan Vorbrüggen
• Re: trailing double underscores
  • From: Arjen Markus
• Re: many "ifs" versus linked list of true cases
  • From: Brooks Moses
• trailing double underscores
  • From: robert . corbett
• Re: question about logarithm in fortran
  • From: nakisa
• Re: xlf compiler bug?
  • From: Richard Maine
• Re: c = inverse(sqrt(epsilon nought *mu nought))
  • From: glen herrmannsfeldt
• Re: many "ifs" versus linked list of true cases
  • From: Gib Bogle
• Re: xlf compiler bug?
  • From: Googleer
• Re: xlf compiler bug?
  • From: glen herrmannsfeldt
• Re: ALLOCATABLE or POINTER
  • From: John Harper
• Re: many "ifs" versus linked list of true cases
  • From: Paul van Delst
• Re: c = inverse(sqrt(epsilon nought *mu nought))
  • From: John Harper
• Re: indentation - unbalanced parentheses
  • From: glen herrmannsfeldt
• Re: indentation - unbalanced parentheses
  • From: James Giles
• Re: xlf compiler bug?
  • From: Richard Maine
• Re: many "ifs" versus linked list of true cases
  • From: andy2O
• Re: xlf compiler bug?
  • From: Dick Hendrickson
• Re: xlf compiler bug?
  • From: Googleer
• Re: many "ifs" versus linked list of true cases
  • From: Louis Krupp
• Re: indentation - unbalanced parentheses
  • From: James Giles
• Re: c = inverse(sqrt(epsilon nought *mu nought))
  • From: Paul van Delst
• xlf compiler bug?
  • From: Googleer
• many "ifs" versus linked list of true cases
  • From: Mark Morss
• Re: c = inverse(sqrt(epsilon nought *mu nought))
  • From: Wade Ward
• Re: xlf compiler bug?
  • From: Richard Maine
• Re: ALLOCATABLE or POINTER
  • From: Richard Maine
• xlf compiler bug?
  • From: Googleer
• Re: ALLOCATABLE or POINTER
  • From: glen herrmannsfeldt
• Re: MAX and optional arguments
  • From: Dick Hendrickson
• Re: MAX and optional arguments
  • From: Michael Metcalf
• Re: ALLOCATABLE or POINTER
  • From: Jan Vorbrüggen
• MAX and optional arguments
  • From: FX
• Re: ALLOCATABLE or POINTER
  • From: Richard Maine
• Re: ALLOCATABLE or POINTER
  • From: Michael Metcalf
• Re: ALLOCATABLE or POINTER
  • From: fj
• Re: c = inverse(sqrt(epsilon nought *mu nought))
  • From: Paul van Delst
• Re: ALLOCATABLE or POINTER
  • From: Michael Metcalf
• Re: ALLOCATABLE or POINTER
  • From: Arjen Markus
• Re: indentation - unbalanced parentheses
  • From: glen herrmannsfeldt
• ALLOCATABLE or POINTER
  • From: fj
• Re: Interesting bug in (admittedly old) MS FORTRAN 5.1
  • From: glen herrmannsfeldt
• Re: indentation - unbalanced parentheses
  • From: Jan Vorbrüggen
• Re: indentation - unbalanced parentheses
  • From: Jan Vorbrüggen
• Re: Integral of the bivariate normal distribution over an offset circle
  • From: Gib Bogle
• Re: Starting to doubt fortran
  • From: blmblm
• Re: Interesting bug in (admittedly old) MS FORTRAN 5.1
  • From: David Thompson
• Re: (OT) Re: Reassociation of pointers
  • From: David Thompson
• Re: Sun fortran and trailing underscores
  • From: David Thompson
• Re: Starting to doubt fortran
  • From: David Thompson
• Re: c = inverse(sqrt(epsilon nought *mu nought))
  • From: John Harper
• Re: c = inverse(sqrt(epsilon nought *mu nought))
  • From: John Harper
• Re: Simple DO loops
  • From: John Harper
• Re: c = inverse(sqrt(epsilon nought *mu nought))
  • From: Wade Ward
• Re: Undefined symbol
  • From: Tim Prince
• Re: question about logarithm in fortran
  • From: Michael Metcalf
• question about logarithm in fortran
  • From: nakisa
• Re: returning a string from a C function
  • From: analyst41
• Re: returning a string from a C function
  • From: Reinhold Bader
• Undefined symbol
  • From: hussain.alqahtani@xxxxxxxxx
• Re: Matrix multiplication
  • From: Alfredo Buttari
• Writing RTF files.
  • From: Terence
• Re: please help
  • From: e p chandler
• Re: please help
  • From: Michael Metcalf
• Re: please help
  • From: fake
• Re: Request for ADIFOR 2.0 (windows version preferred)?
  • From: see_address
• Re: please help
  • From: Dr Ivan D. Reid
• Re: pre-processor include vs. F77-MIL-STD include
  • From: Edward N Bromhead
• Re: pretty output using Fortran
  • From: Edward N Bromhead
• Re: OpenMP problem
  • From: John Deas
• Re: please help
  • From: e p chandler
• Re: OpenMP problem
  • From: John Deas
• Re: Request for ADIFOR 2.0 (windows version preferred)?
  • From: glen herrmannsfeldt
• Re: Request for ADIFOR 2.0 (windows version preferred)?
  • From: Richard Maine
• Re: c = inverse(sqrt(epsilon nought *mu nought))
  • From: e p chandler
• Request for ADIFOR 2.0 (windows version preferred)?
  • From: leaf
• Re: OpenMP problem
  • From: glen herrmannsfeldt
• Re: OpenMP problem
  • From: glen herrmannsfeldt
• Re: Integral of the bivariate normal distribution over an offset circle
  • From: Terence
• Re: indentation - unbalanced parentheses
  • From: glen herrmannsfeldt
• Re: OpenMP problem
  • From: Gib Bogle
• Re: OpenMP problem
  • From: John Deas
• Re: OpenMP problem
  • From: John Deas
• Re: OpenMP problem
  • From: Gib Bogle
• Re: please help
  • From: Dr Ivan D. Reid
• Re: please help
  • From: Dr Ivan D. Reid
• Re: indentation - unbalanced parentheses
  • From: glen herrmannsfeldt
• Re: returning a string from a C function
  • From: aerospace1028
• Re: Matrix multiplication
  • From: Carramba
• Re: indentation - unbalanced parentheses
  • From: Richard Maine
• Re: please help
  • From: e p chandler
• Re: indentation - unbalanced parentheses
  • From: Richard Maine
• Re: indentation - unbalanced parentheses
  • From: Dick Hendrickson
• Re: VARYING attribute for dealing with Fortran variable arg list
  • From: Richard Maine
• Matrix multiplication
  • From: Carramba
• Re: indentation - unbalanced parentheses
  • From: Arasaki
• Re: c = inverse(sqrt(epsilon nought *mu nought))
  • From: Michael Metcalf
• Re: Integral of the bivariate normal distribution over an offset circle
  • From: David Jones
• Re: c = inverse(sqrt(epsilon nought *mu nought))
  • From: e p chandler
• Re: Simple DO loops
  • From: Ron Shepard
• Re: Integral of the bivariate normal distribution over an offset circle
  • From: highegg
• Re: indentation - unbalanced parentheses
  • From: Gary Scott
• Re: indentation - unbalanced parentheses
  • From: Gary Scott
• Re: Integral of the bivariate normal distribution over an offset circle
  • From: Gordon Sande
• Re: Integral of the bivariate normal distribution over an offset circle
  • From: Beliavsky
• Re: Simple DO loops
  • From: Beliavsky
• Re: Simple DO loops
  • From: Les
• Re: Simple DO loops
  • From: Les
• Simple DO loops
  • From: smurray444
• Re: OpenMP problem
  • From: John Deas
• Re: indentation - unbalanced parentheses
  • From: Arasaki
• Re: Integral of the bivariate normal distribution over an offset circle
  • From: Gib Bogle
• RE: Matrix multiplication
  • From: meek
• Re: VARYING attribute for dealing with Fortran variable arg list
  • From: abarun22
• Integral of the bivariate normal distribution over an offset circle
  • From: yair999@xxxxxxxxx
• Re: indentation - unbalanced parentheses
  • From: James Giles
• Re: OpenMP problem
  • From: Gib Bogle
• Re: indentation - unbalanced parentheses
  • From: Walter Spector
• Re: indentation - unbalanced parentheses
  • From: analyst41
• Re: indentation - unbalanced parentheses
  • From: James Giles
• Re: indentation - unbalanced parentheses
  • From: Steve Lionel
• Re: indentation - unbalanced parentheses
  • From: glen herrmannsfeldt
• Re: indentation - unbalanced parentheses
  • From: Gary Scott
• Re: indentation - unbalanced parentheses
  • From: Terence
• Re: c = inverse(sqrt(epsilon nought *mu nought))
  • From: Richard Maine
• Re: c = inverse(sqrt(epsilon nought *mu nought))
  • From: Wade Ward
• Re: please help
  • From: Beliavsky
• Re: indentation - unbalanced parentheses
  • From: ghost
• Re: indentation - unbalanced parentheses
  • From: ghost
• Re: indentation - unbalanced parentheses
  • From: Gordon Sande
• Re: indentation - unbalanced parentheses
  • From: Richard Maine
• Re: OpenMP problem
  • From: glen herrmannsfeldt
• Re: please help
  • From: fake
• Re: indentation - unbalanced parentheses
  • From: Arasaki
• Re: please help
  • From: Dick Hendrickson
• Re: indentation - unbalanced parentheses
  • From: John Harper
• Re: OpenMP problem
  • From: John Deas
• Re: how to find IMSL library?
  • From: Steve Lionel
• OpenMP problem
  • From: John Deas
• Re: how to find IMSL library?
  • From: John B. Coarsey, PE
• please help
  • From: fake
• Re: indentation - unbalanced parentheses
  • From: glen herrmannsfeldt
• Re: indentation - unbalanced parentheses
  • From: Michael Metcalf
• Re: indentation - unbalanced parentheses
  • From: glen herrmannsfeldt
• Re: indentation - unbalanced parentheses
  • From: James Giles
• Re: indentation - unbalanced parentheses
  • From: James Giles
• Re: indentation - unbalanced parentheses
  • From: James Giles
• Re: indentation - unbalanced parentheses
  • From: Richard Maine
• Re: qsort problem with module
  • From: Herman D . Knoble
• Re: indentation - unbalanced parentheses
  • From: Beliavsky
• Re: indentation - unbalanced parentheses
  • From: Michael Metcalf
• Re: indentation - unbalanced parentheses
  • From: e p chandler
• Re: indentation - unbalanced parentheses
  • From: Richard Maine
• Re: VARYING attribute for dealing with Fortran variable arg list
  • From: Ron Shepard
• Re: Fortran to matlab infuriating problem
  • From: Marwan
• Re: indentation - unbalanced parentheses
  • From: Arasaki
• VARYING attribute for dealing with Fortran variable arg list
  • From: Arun Prasath
• Re: qsort problem with module
  • From: Gib Bogle
• Re: indentation - unbalanced parentheses
  • From: robert . corbett
• Re: how to find IMSL library?
  • From: Richard Maine
• Re: passing large arrays to functions
  • From: robin
• how to find IMSL library?
  • From: XYQ
• how to find IMSL library?
  • From: XYQ
• how to find IMSL library?
  • From: XYQ
• Recent book published covering FORTRAN
  • From: yyyc186
• Re: indentation - unbalanced parentheses
  • From: Terence
• Re: [newbie_q] indentation - unbalanced parentheses
  • From: John Harper
• Re: returning a string from a C function
  • From: glen herrmannsfeldt
• Re: [newbie_q] indentation - unbalanced parentheses
  • From: glen herrmannsfeldt
• Re: [newbie_q] indentation - unbalanced parentheses
  • From: glen herrmannsfeldt
• returning a string from a C function
  • From: iglesu
• Re: [newbie_q] indentation - unbalanced parentheses
  • From: James Giles
• Re: Vexing problems arising from mixing F9x and F77 code
  • From: glen herrmannsfeldt
• Re: pretty output using Fortran
  • From: e p chandler
• Re: [newbie_q] indentation - unbalanced parentheses
  • From: Dr Ivan D. Reid
• Re: [newbie_q] indentation - unbalanced parentheses
  • From: Dan Nagle
• Re: [newbie_q] indentation - unbalanced parentheses
  • From: Carramba
• Re: question on polymorphism
  • From: Ben Hetland
• Re: [newbie_q] indentation - unbalanced parentheses
  • From: James Giles
• Re: [newbie_q] indentation - unbalanced parentheses
  • From: Dr Ivan D. Reid
• Re: pretty output using Fortran
  • From: Craig Powers
• Re: [newbie_q] indentation - unbalanced parentheses
  • From: Craig Powers
• Re: Fortran to matlab infuriating problem
  • From: Dr Ivan D. Reid
• Re: Vexing problems arising from mixing F9x and F77 code
  • From: Steven G. Kargl
• Re: [newbie_q] indentation - unbalanced parentheses
  • From: glen herrmannsfeldt
• Re: Vexing problems arising from mixing F9x and F77 code
  • From: glen herrmannsfeldt
• Re: [newbie_q] indentation - unbalanced parentheses
  • From: Carramba
• Re: Vexing problems arising from mixing F9x and F77 code
  • From: Gordon Sande
• Re: [newbie_q] indentation - unbalanced parentheses
  • From: Bob Stryk
• [newbie_q] indentation - unbalanced parentheses
  • From: Carramba
• Re: passing large arrays to functions
  • From: glen herrmannsfeldt
• Re: Vexing problems arising from mixing F9x and F77 code
  • From: Gordon Sande
• Re: Vexing problems arising from mixing F9x and F77 code
  • From: Arjen Markus
• Vexing problems arising from mixing F9x and F77 code
  • From: mecej4
• Re: question on polymorphism
  • From: Norman S. Clerman
• Re: Conversion of Fortran File unit to C File stream
  • From: mecej4
• Re: qsort problem with module
  • From: mecej4
• Re: passing large arrays to functions
  • From: Louis Krupp
• Re: Cray pointer type in Sun's f95
  • From: Sebastian Hanigk
• Re: pretty output using Fortran
  • From: Catherine Rees Lay
• Re: qsort problem with module
  • From: highegg
• Re: qsort problem with module
  • From: Richard Maine
• Re: qsort problem with module
  • From: highegg
• Re: qsort problem with module
  • From: mecej4
• qsort problem with module
  • From: Gib Bogle
• Re: Conversion of Fortran File unit to C File stream
  • From: robert . corbett
• Re: pretty output using Fortran
  • From: analyst41
• Re: c = inverse(sqrt(epsilon nought *mu nought))
  • From: Richard Maine
• Re: pretty output using Fortran
  • From: analyst41
• c = inverse(sqrt(epsilon nought *mu nought))
  • From: Wade Ward
• Re: Fortran to matlab infuriating problem
  • From: dpb
• Re: passing large arrays to functions
  • From: glen herrmannsfeldt
• Re: Cray pointer type in Sun's f95
  • From: robert . corbett
• Re: passing large arrays to functions
  • From: Gabe
• Re: passing large arrays to functions
  • From: Richard Maine
• passing large arrays to functions
  • From: Gabe
• Re: Can I do a timing line by line?
  • From: Craig Powers
• Re: Can I do a timing line by line?
  • From: SullivanZ
• Re: Can I do a timing line by line?
  • From: SullivanZ
• Re: Fortran to matlab infuriating problem
  • From: Marwan
• Re: Can I do a timing line by line?
  • From: Craig Powers
• Re: Fortran to matlab infuriating problem
  • From: Paul van Delst
• Re: operators for matrix
  • From: Johan
• Re: Fortran to matlab infuriating problem
  • From: Marwan
• Re: Fortran to matlab infuriating problem
  • From: Beliavsky
• Re: Fortran to matlab infuriating problem
  • From: Dr Ivan D. Reid
• Re: Fortran to matlab infuriating problem
  • From: Paul van Delst
• Re: Can I do a timing line by line?
  • From: Dick Hendrickson
• Re: pre-processor include vs. F77-MIL-STD include
  • From: Ron Shepard
• Re: pre-processor include vs. F77-MIL-STD include
  • From: Beliavsky
• Re: Fortran to matlab infuriating problem
  • From: Marwan
• Fortran to matlab infuriating problem
  • From: Marwan
• Re: Conversion of Fortran File unit to C File stream
  • From: Ron Shepard
• pre-processor include vs. F77-MIL-STD include
  • From: Richard Archibald
• Re: Can I do a timing line by line?
  • From: Paul van Delst
• Re: Have any compiler compatible with 2003 standards?
  • From: gary . l . scott
• Re: Have any compiler compatible with 2003 standards?
  • From: Beliavsky
• Re: Have any compiler compatible with 2003 standards?
  • From: Gary Scott
• Have any compiler compatible with 2003 standards?
  • From: li . simula
• Re: pretty output using Fortran
  • From: e p chandler
• Re: question on polymorphism
  • From: Ben Hetland
• Re: question on polymorphism
  • From: Reinhold Bader
• Re: operators for matrix
  • From: Janne Blomqvist
• Re: Can I do a timing line by line?
  • From: Janne Blomqvist
• Re: Arpack usage
  • From: lorin
• Re: Can I do a timing line by line?
  • From: Butterseeds
• Re: Can I do a timing line by line?
  • From: glen herrmannsfeldt
• Re: Can I do a timing line by line?
  • From: Craig Powers
• Re: Can I do a timing line by line?
  • From: Butterseeds
• Re: Can I do a timing line by line?
  • From: Kevin G. Rhoads
• Re: Can I do a timing line by line?
  • From: Paul van Delst
• Re: operators for matrix
  • From: Fly Away
• Re: Can I do a timing line by line?
  • From: Beliavsky
• Re: Commutative law in addition in XL Fortran
  • From: glen herrmannsfeldt
• Re: Commutative law in addition in XL Fortran
  • From: glen herrmannsfeldt
• Can I do a timing line by line?
  • From: Butterseeds
• Re: operators for matrix
  • From: Beliavsky
• Re: pretty output using Fortran
  • From: Edward N Bromhead
• question on polymorphism
  • From: Norman S. Clerman
• Re: operators for matrix
  • From: Beliavsky
• Re: Commutative law in addition in XL Fortran
  • From: Michael Metcalf
• Re: Commutative law in addition in XL Fortran
  • From: Greg Lindahl
• Re: operators for matrix
  • From: Michael Metcalf
• Re: Conversion of Fortran File unit to C File stream
  • From: glen herrmannsfeldt
• Re: Commutative law in addition in XL Fortran
  • From: glen herrmannsfeldt
• operators for matrix
  • From: Johan
• Re: Commutative law in addition in XL Fortran
  • From: Dick Hendrickson
• Re: Commutative law in addition in XL Fortran
  • From: Herman D . Knoble
• Re: Commutative law in addition in XL Fortran
  • From: Herman D . Knoble
• Re: realft
  • From: garba07
• Re: Commutative law in addition in XL Fortran
  • From: Dick Hendrickson
• Re: Conversion of Fortran File unit to C File stream
  • From: Kevin G. Rhoads
• Re: realft
  • From: Beliavsky
• Re: Arpack usage
  • From: Arjen Markus
• Re: Arpack usage
  • From: Beliavsky
• Arpack usage
  • From: lorin
• realft
  • From: garba07
• Re: Conversion of Fortran File unit to C File stream
  • From: Arjen Markus
• Re: pretty output using Fortran
  • From: Terence
• Re: Conversion of Fortran File unit to C File stream
  • From: abarun22
• Re: pretty output using Fortran
  • From: Dr Ivan D. Reid
• Re: pretty output using Fortran
  • From: analyst41
• Re: array of functions...
  • From: John Harper
• Re: pretty output using Fortran
  • From: e p chandler
• Re: Commutative law in addition in XL Fortran
  • From: Gib Bogle
• Re: Commutative law in addition in XL Fortran
  • From: Gib Bogle
• Re: pretty output using Fortran
  • From: Gary Scott
• Re: pretty output using Fortran
  • From: glen herrmannsfeldt
• Re: pretty output using Fortran
  • From: FX
• pretty output using Fortran
  • From: analyst41
• Re: Commutative law in addition in XL Fortran
  • From: robert . corbett
• Re: Commutative law in addition in XL Fortran
  • From: Walter Spector
• Re: g95 procedure pointers as derived-type components
  • From: Walter Spector
• Re: Conversion of Fortran File unit to C File stream
  • From: e p chandler
• Re: Cray pointer type in Sun's f95
  • From: Sebastian Hanigk
• Re: Conversion of Fortran File unit to C File stream
  • From: Kevin G. Rhoads
• Re: Conversion of Fortran File unit to C File stream
  • From: Richard Maine
• Conversion of Fortran File unit to C File stream
  • From: abarun22
• Re: g95 procedure pointers as derived-type components
  • From: Reinhold Bader
• Re: Commutative law in addition in XL Fortran
  • From: Greg Lindahl
• Re: Commutative law in addition in XL Fortran
  • From: Dick Hendrickson
• Re: Cray pointer type in Sun's f95
  • From: robert . corbett
• Cray pointer type in Sun's f95
  • From: Sebastian Hanigk
• Re: Two problems
  • From: glen herrmannsfeldt
• Re: g95 procedure pointers as derived-type components
  • From: Vic . Kelson
• Re: g95 procedure pointers as derived-type components
  • From: Vic . Kelson
• Re: array of functions...
  • From: glen herrmannsfeldt
• Re: g95 procedure pointers as derived-type components
  • From: Reinhold Bader
• Re: Two problems
  • From: Thomas Koenig
• Re: g95 procedure pointers as derived-type components
  • From: Vic . Kelson
• Re: g95 procedure pointers as derived-type components
  • From: linuxl4 . fox
• Re: array of functions...
  • From: James Giles
• g95 procedure pointers as derived-type components
  • From: Vic . Kelson
• Re: array of functions...
  • From: glen herrmannsfeldt
• Re: array of functions...
  • From: Richard Maine
• Re: Auto-handling g77/gfortran transition with automake/autoconf (inc. C++ linking)
  • From: Andy Buckley
• Needed Immediately: Competent attorney with in-depth experience in Fraud
  • From: Maria
• Re: C- Fortran interface - Variable number of arguments
  • From: Jugoslav Dujic
• Re: Auto-handling g77/gfortran transition with automake/autoconf (inc. C++ linking)
  • From: Daniel Franke
• Re: C- Fortran interface - Variable number of arguments
  • From: glen herrmannsfeldt
• Auto-handling g77/gfortran transition with automake/autoconf (inc. C++ linking)
  • From: Andy Buckley
• Re: array of functions...
  • From: Michael Metcalf
• Re: array of functions...
  • From: Arjen Markus
• Re: C- Fortran interface - Variable number of arguments
  • From: Arjen Markus
• C- Fortran interface - Variable number of arguments
  • From: abarun22
• Re: Two problems
  • From: Brooks Moses
• Re: Commutative law in addition in XL Fortran
  • From: Brooks Moses
• Re: Commutative law in addition in XL Fortran
  • From: Jugoslav Dujic
• Re: Two problems
  • From: Greg Lindahl
• Re: Commutative law in addition in XL Fortran
  • From: insun.song@xxxxxxxxx
• Re: Commutative law in addition in XL Fortran
  • From: James Giles
• Re: Commutative law in addition in XL Fortran
  • From: robert . corbett
• Re: Two problems
  • From: Rich Townsend
• Re: Commutative law in addition in XL Fortran
  • From: Richard Maine
• Re: Two problems
  • From: Richard Maine
• Re: array of functions...
  • From: glen herrmannsfeldt
• Re: array of functions...
  • From: Richard Maine
• Re: Commutative law in addition in XL Fortran
  • From: sureal
• Re: Commutative law in addition in XL Fortran
  • From: ejkost
• Re: Commutative law in addition in XL Fortran
  • From: James Giles
• Re: Two problems
  • From: glen herrmannsfeldt
• Re: Commutative law in addition in XL Fortran
  • From: glen herrmannsfeldt
• Re: Commutative law in addition in XL Fortran
  • From: glen herrmannsfeldt
• Re: Commutative law in addition in XL Fortran
  • From: Paul van Delst
• Re: Commutative law in addition in XL Fortran
  • From: insun.song@xxxxxxxxx
• Re: Commutative law in addition in XL Fortran
  • From: insun.song@xxxxxxxxx
• Re: Help for a FORTRAN N00b
  • From: glen herrmannsfeldt
• Re: Commutative law in addition in XL Fortran
  • From: James Giles
• Re: Commutative law in addition in XL Fortran
  • From: Paul van Delst
• Re: Commutative law in addition in XL Fortran
  • From: Tim Prince
• Re: Commutative law in addition in XL Fortran
  • From: highegg
• Re: Commutative law in addition in XL Fortran
  • From: Steven G. Kargl
• Re: Commutative law in addition in XL Fortran
  • From: Michael Metcalf
• Re: Commutative law in addition in XL Fortran
  • From: insun.song@xxxxxxxxx
• Re: Commutative law in addition in XL Fortran
  • From: insun.song@xxxxxxxxx
• Re: Commutative law in addition in XL Fortran
  • From: Paul van Delst
• Re: Commutative law in addition in XL Fortran
  • From: Michael Metcalf
• Re: Help for a FORTRAN N00b
  • From: Steve Lionel
• Commutative law in addition in XL Fortran
  • From: insun.song@xxxxxxxxx
• Re: Help for a FORTRAN N00b
  • From: Richard Maine
• Re: Help for a FORTRAN N00b
  • From: Tim Prince
• Re: Help for a FORTRAN N00b
  • From: e p chandler
• Re: Help for a FORTRAN N00b
  • From: glen herrmannsfeldt
• Re: Help for a FORTRAN N00b
  • From: Richard Maine
• Re: Can "Microsoft Visual Studio .NET 2003" hide the code of Fortran?
  • From: Tim Prince
• Re: Bilinear Interpolation on Grid
  • From: Brendan
• Can "Microsoft Visual Studio .NET 2003" hide the code of Fortran?
  • From: li . simula
• Re: GUI interface for fortran 77 under linux (using gfortran so fortran 95 is a possiblity)
  • From: David Simpson
• Re: Bilinear Interpolation on Grid
  • From: highegg
• Bilinear Interpolation on Grid
  • From: smurray444
• Re: GUI interface for fortran 77 under linux (using gfortran so fortran 95 is a possiblity)
  • From: Hani Ibrahim
• Re: Help for a FORTRAN N00b
  • From: Ron Shepard
• Re: Help for a FORTRAN N00b
  • From: Richard Maine
• Re: Help for a FORTRAN N00b
  • From: e p chandler
• Re: which is efficient
  • From: Greg Lindahl
• Re: Program to convert binary <-> gray
  • From: Richard Maine
• Re: GUI interface for fortran 77 under linux (using gfortran so fortran 95 is a possiblity)
  • From: Bil Kleb
• Re: Circular module dependencies
  • From: Bil Kleb
• Re: which is efficient
  • From: Janne Blomqvist
• Re: GUI interface for fortran 77 under linux (using gfortran so fortran 95 is a possiblity)
  • From: baf
• Re: utility to replace "end" with "end subroutine foo"
  • From: glen herrmannsfeldt
• Re: Program to convert binary <-> gray
  • From: Kevin G. Rhoads
• Re: GUI interface for fortran 77 under linux (using gfortran so fortran 95 is a possiblity)
  • From: Beliavsky
• GUI interface for fortran 77 under linux (using gfortran so fortran 95 is a possiblity)
  • From: me
• Re: how to compile code on linux(32bit) for linux(64bit)
  • From: Greg Lindahl
• Re: utility to replace "end" with "end subroutine foo"
  • From: Beliavsky
• Re: Program to convert binary <-> gray
  • From: Dick Hendrickson
• Re: which is efficient
  • From: Thomas Koenig
• Re: Program to convert binary <-> gray
  • From: Thomas Koenig
• Re: which is efficient
  • From: glen herrmannsfeldt
• Re: Generic interfaces
  • From: Reinhold Bader
• Generic interfaces
  • From: Gus Gassmann
• Re: Circular module dependencies
  • From: Paul van Delst
• Re: problem reading REALs from *
  • From: J
• Circular module dependencies
  • From: Mick Maier
• Re: which is efficient
  • From: Paul van Delst
• Re: which is efficient
  • From: Mark Morss
• Re: which is efficient
  • From: Tim Prince
• Re: which is efficient
  • From: Mark Morss
• Re: Help with Developing a GUI for Fortran program
  • From: Gary Scott
• Re: Help with Developing a GUI for Fortran program
  • From: Catherine Rees Lay
• Re: how to compile code on linux(32bit) for linux(64bit)
  • From: FX
• RE: Help with Developing a GUI for Fortran program
  • From: meek
• Re: how to compile code on linux(32bit) for linux(64bit)
  • From: Arjen Markus
• how to compile code on linux(32bit) for linux(64bit)
  • From: isanjay4u
• Re: Epsilon, Precision or Tiny ???
  • From: Steven G. Kargl
• Re: Epsilon, Precision or Tiny ???
  • From: subspace
• Re: Looking for some Fortran analysis tools
  • From: Beliavsky
• Re: Looking for some Fortran analysis tools
  • From: ian_d_chivers
• Re: Epsilon, Precision or Tiny ???
  • From: Richard Maine
• Re: Looking for some Fortran analysis tools
  • From: Bil Kleb
• Looking for some Fortran analysis tools
  • From: Joe Willmann
• Re: Epsilon, Precision or Tiny ???
  • From: Arjen Markus
• Re: Program to convert binary <-> gray
  • From: Beliavsky
• Re: Epsilon, Precision or Tiny ???
  • From: monir
• Re: Program to convert binary <-> gray
  • From: nobat
• Re: Program to convert binary <-> gray
  • From: Richard Maine
• Re: Epsilon, Precision or Tiny ???
  • From: Bob Stryk
• Re: add a0 format to language to print trimmed character variables
  • From: Beliavsky
• Re: Program to convert binary <-> gray
  • From: Kevin G. Rhoads
• Re: Epsilon, Precision or Tiny ???
  • From: Michael Metcalf
• Epsilon, Precision or Tiny ???
  • From: monir
• Re: Program to convert binary <-> gray
  • From: Beliavsky
• Re: Program to convert binary <-> gray
  • From: Michael Metcalf
• Re: Program to convert binary <-> gray
  • From: Herman D . Knoble
• PHAML 1.0 available
  • From: william . mitchell
• Re: Program to convert binary <-> gray
  • From: Michael Metcalf
• Re: Program to convert binary <-> gray
  • From: Herman D . Knoble
• Re: Two problems
  • From: Leslie Ballentine
• Re: I/O in PURE and ELEMENTAL procedures in Fortran 2008
  • From: Jan Vorbrüggen
• Re: which is efficient
  • From: Tim Prince
• Re: Program to convert binary <-> gray
  • From: Michael Metcalf
• Re: Program to convert binary <-> gray
  • From: Beliavsky
• Re: Program to convert binary <-> gray
  • From: Michael Metcalf
• Custom software development
  • From: VB
• Re: which is efficient
  • From: aeroguy
• Re: Problem linking with Fortran NAG library
  • From: prynhart
• Re: Problem linking with Fortran NAG library
  • From: Beliavsky
• Re: Help for a FORTRAN N00b
  • From: e p chandler
• Re: Problem linking with Fortran NAG library
  • From: prynhart
• Re: Help for a FORTRAN N00b
  • From: e p chandler
• Re: Help for a FORTRAN N00b
  • From: Richard Maine
• Re: Problem linking with Fortran NAG library
  • From: Beliavsky
• Problem linking with Fortran NAG library
  • From: prynhart
• Re: problem reading REALs from *
  • From: John Harper
• Re: Help for a FORTRAN N00b
  • From: Wade Ward
• Re: compile/linking problem, undefined symbol
  • From: gsal
• Re: problem reading REALs from *
  • From: Beliavsky
• Re: compile/linking problem, undefined symbol
  • From: Tim Prince
• Re: problem reading REALs from *
  • From: Wade Ward
• problem reading REALs from *
  • From: J
• Re: compile/linking problem, undefined symbol
  • From: Louis Krupp
• Re: compile/linking problem, undefined symbol
  • From: FX
• Re: sort & SVRGN
  • From: dpb
• Re: sort & SVRGN
  • From: Wade Ward
• Re: I/O in PURE and ELEMENTAL procedures in Fortran 2008
  • From: Brooks Moses
• Re: I/O in PURE and ELEMENTAL procedures in Fortran 2008
  • From: jamesgiles@xxxxxxx
• Re: I/O in PURE and ELEMENTAL procedures in Fortran 2008
  • From: Ron Shepard
• Re: I/O in PURE and ELEMENTAL procedures in Fortran 2008
  • From: jamesgiles@xxxxxxx
• Re: compile/linking problem, undefined symbol
  • From: Tim Prince
• compile/linking problem, undefined symbol
  • From: gsal
• Re: sort & SVRGN
  • From: David Frank
• Re: I/O in PURE and ELEMENTAL procedures in Fortran 2008
  • From: Gary Scott
• sort & SVRGN
  • From: nakisa
• Re: I/O in PURE and ELEMENTAL procedures in Fortran 2008
  • From: Ron Shepard
• Re: I/O in PURE and ELEMENTAL procedures in Fortran 2008
  • From: Brooks Moses
• Re: Accessing Oracle 10g database on Solaris 9
  • From: robert . corbett
• Re: question about initializing variables to 0
  • From: Gordon Sande
• Re: I/O in PURE and ELEMENTAL procedures in Fortran 2008
  • From: Gary Scott
• Re: question about initializing variables to 0
  • From: Gary Scott
• Re: Help for a FORTRAN N00b
  • From: e p chandler
• Re: Help for a FORTRAN N00b
  • From: Wade Ward
• Re: I/O in PURE and ELEMENTAL procedures in Fortran 2008
  • From: Steve Lionel
• Re: question about initializing variables to 0
  • From: Gordon Sande
• Re: fortran maintenance tools
  • From: MattR
• Re: question about initializing variables to 0
  • From: Richard Maine
• Re: question about initializing variables to 0
  • From: jamesgiles@xxxxxxx
• Re: fortran maintenance tools
  • From: Beliavsky
• Re: question about initializing variables to 0
  • From: robin
• Re: Help for a FORTRAN N00b
  • From: e p chandler
• Re: Bundling multiple objects into a single module?
  • From: Arno
• Re: question about initializing variables to 0
  • From: Brooks Moses
• Re: question about initializing variables to 0
  • From: David Flower
• Re: I/O in PURE and ELEMENTAL procedures in Fortran 2008
  • From: Sebastian Hanigk
• Re: generic routines, to what end?
  • From: Ron Shepard
• Re: Help for a FORTRAN N00b
  • From: Richard Maine
• Re: Help for a FORTRAN N00b
  • From: thogy
• Re: Help for a FORTRAN N00b
  • From: Gary Scott
• Re: fortran maintenance tools
  • From: MattR
• Re: question about initializing variables to 0
  • From: subspace
• Re: Help for a FORTRAN N00b
  • From: Wade Ward
• Re: Help for a FORTRAN N00b
  • From: Richard Maine
• Re: (OT) Re: Reassociation of pointers
  • From: Richard Maine
• Re: Help for a FORTRAN N00b
  • From: Terence
• Re: I/O in PURE and ELEMENTAL procedures in Fortran 2008
  • From: Gary Scott
• Re: (OT) Re: Reassociation of pointers
  • From: John Harper
• Re: fortran maintenance tools
  • From: Greg Lindahl
• Re: fortran maintenance tools
  • From: Fly Away
• Re: question about initializing variables to 0
  • From: glen herrmannsfeldt
• Re: fortran maintenance tools
  • From: MattR
• Re: (OT) Re: Reassociation of pointers
  • From: Craig Powers
• Re: fortran maintenance tools
  • From: George N. White III
• Re: question about initializing variables to 0
  • From: jamesgiles@xxxxxxx
• Re: question about initializing variables to 0
  • From: glen herrmannsfeldt
• Re: question about initializing variables to 0
  • From: glen herrmannsfeldt
• Re: question about initializing variables to 0
  • From: jamesgiles@xxxxxxx
• Re: question about initializing variables to 0
  • From: Randall Mackie
• Re: question about initializing variables to 0
  • From: jamesgiles@xxxxxxx
• Re: question about initializing variables to 0
  • From: Steven G. Kargl
• Re: question about initializing variables to 0
  • From: Beliavsky
• Re: question about initializing variables to 0
  • From: jamesgiles@xxxxxxx
• question about initializing variables to 0
  • From: Randall Mackie
• Re: fortran maintenance tools
  • From: Greg Lindahl
• Accessing Oracle 10g database on Solaris 9
  • From: James Parsly
• Re: Bundling multiple objects into a single module?
  • From: jamesgiles@xxxxxxx
• Re: Problem to pass complex array between subroutine and main program
  • From: Richard Maine
• Re: Help for a FORTRAN N00b
  • From: Richard Maine
• Re: (OT) Re: Reassociation of pointers
  • From: Rich Townsend
• Re: (OT) Re: Reassociation of pointers
  • From: Richard Maine
• Re: Bundling multiple objects into a single module?
  • From: Craig Powers
• Re: (OT) Re: Reassociation of pointers
  • From: Jugoslav Dujic
• Re: generic routines, to what end?
  • From: highegg
• Re: generic routines, to what end?
  • From: Mark Morss
• Re: generic routines, to what end?
  • From: Mark Morss
• Re: generic routines, to what end?
  • From: Beliavsky
• Re: generic routines, to what end?
  • From: Arjen Markus
• generic routines, to what end?
  • From: Mark Morss
• Re: Problem to pass complex array between subroutine and main program
  • From: Beliavsky
• Re: Problem to pass complex array between subroutine and main program
  • From: Michael Metcalf
• Re: Problem to pass complex array between subroutine and main program
  • From: marcomarco76
• Re: Problem to pass complex array between subroutine and main program
  • From: Michael Metcalf
• Re: add a0 format to language to print trimmed character variables
  • From: Clive Page
• Re: Problem to pass complex array between subroutine and main program
  • From: Arjen Markus
• Re: Problem to pass complex array between subroutine and main program
  • From: marcomarco76
• Re: I/O in PURE and ELEMENTAL procedures in Fortran 2008
  • From: Sebastian Hanigk
• Re: Problem to pass complex array between subroutine and main program
  • From: Arjen Markus
• Problem to pass complex array between subroutine and main program
  • From: marcomarco76
• Re: Bundling multiple objects into a single module?
  • From: Brooks Moses
• Re: What does this error mean?
  • From: Terence
• Re: What does this error mean?
  • From: Arjen Markus
• Re: Help for a FORTRAN N00b
  • From: Terence
• Re: I/O in PURE and ELEMENTAL procedures in Fortran 2008
  • From: Wade Ward
• What does this error mean?
  • From: Wenbin Hu
• Re: I/O in PURE and ELEMENTAL procedures in Fortran 2008
  • From: Sebastian Hanigk
• Re: Help with Developing a GUI for Fortran program
  • From: Arjen Markus
• Re: Help with Developing a GUI for Fortran program
  • From: Gib Bogle
• Re: Help for a FORTRAN N00b
  • From: Richard Maine
• Re: Help for a FORTRAN N00b
  • From: thogy
• Re: fortran is more popular
  • From: Tim Prince
• Re: fortran is more popular
  • From: Greg Lindahl
• Re: fortran maintenance tools
  • From: MattR
• Re: fortran is more popular
  • From: Wade Ward
• Re: fortran is more popular
  • From: Greg Lindahl
• fortran is more popular
  • From: Wade Ward
• Re: fortran maintenance tools
  • From: MattR
• Re: JPG image size
  • From: Wade Ward
• Re: fortran maintenance tools
  • From: Bil Kleb
• Re: fortran maintenance tools
  • From: George N. White III
• Re: JPG image size
  • From: rrr7rrr
• Re: Bundling multiple objects into a single module?
  • From: Gus Gassmann
• Re: fortran maintenance tools
  • From: Fly Away
• Re: fortran maintenance tools
  • From: MattR
• Re: fortran maintenance tools
  • From: Gary Scott
• Re: fortran maintenance tools
  • From: Bil Kleb
• Re: I/O in PURE and ELEMENTAL procedures in Fortran 2008
  • From: Gary Scott
• Re: I/O in PURE and ELEMENTAL procedures in Fortran 2008
  • From: jamesgiles@xxxxxxx
• Re: I/O in PURE and ELEMENTAL procedures in Fortran 2008
  • From: jamesgiles@xxxxxxx
• Re: I/O in PURE and ELEMENTAL procedures in Fortran 2008
  • From: jamesgiles@xxxxxxx
• fortran maintenance tools
  • From: MattR
• Re: I/O in PURE and ELEMENTAL procedures in Fortran 2008
  • From: jamesgiles@xxxxxxx
• Re: I/O in PURE and ELEMENTAL procedures in Fortran 2008
  • From: Ron Shepard
• Re: I/O in PURE and ELEMENTAL procedures in Fortran 2008
  • From: jamesgiles@xxxxxxx
• Re: I/O in PURE and ELEMENTAL procedures in Fortran 2008
  • From: Jan Vorbrüggen
• Re: Bundling multiple objects into a single module?
  • From: Dick Hendrickson
• Re: Bundling multiple objects into a single module?
  • From: Richard Maine
• Re: I/O in PURE and ELEMENTAL procedures in Fortran 2008
  • From: Dick Hendrickson
• Re: Bundling multiple objects into a single module?
  • From: highegg
• Re: Bundling multiple objects into a single module?
  • From: Michael Metcalf
• Re: JPG image size
  • From: rrr7rrr
• Short-circuiting (was Re: I/O in PURE and ELEMENTAL procedures in Fortran 2008)
  • From: Beliavsky
• [CFP] EuroPVM/MPI'07 -- submission deadline extended to May 14th
  • From: Morfys
• Re: Bundling multiple objects into a single module?
  • From: Gus Gassmann
• Re: I/O in PURE and ELEMENTAL procedures in Fortran 2008
  • From: Beliavsky
• Re: I/O in PURE and ELEMENTAL procedures in Fortran 2008
  • From: Sebastian Hanigk
• Re: JPG image size
  • From: rrr7rrr
• Re: Bundling multiple objects into a single module?
  • From: Michael Metcalf
• Re: Bundling multiple objects into a single module?
  • From: Bil Kleb
• Re: problem with NEQNF
  • From: nakisa
• Bundling multiple objects into a single module?
  • From: Gus Gassmann
• Re: Help with Developing a GUI for Fortran program
  • From: Beliavsky
• Re: I/O in PURE and ELEMENTAL procedures in Fortran 2008
  • From: Gary Scott
• Re: Help with Developing a GUI for Fortran program
  • From: Gary Scott
• Re: Help with Developing a GUI for Fortran program
  • From: Tobias Burnus
• Re: I/O in PURE and ELEMENTAL procedures in Fortran 2008
  • From: Steve Lionel
• Re: Help with Developing a GUI for Fortran program
  • From: Bil Kleb
• Re: JPG image size
  • From: Edward N Bromhead
• Re: Help with Developing a GUI for Fortran program
  • From: Catherine Rees Lay
• Re: I/O in PURE and ELEMENTAL procedures in Fortran 2008
  • From: jamesgiles@xxxxxxx
• Re: I/O in PURE and ELEMENTAL procedures in Fortran 2008
  • From: Jan Vorbrüggen
• Re: Help with Developing a GUI for Fortran program
  • From: Jan Vorbrüggen
• Re: problem with NEQNF
  • From: mecej4
• Re: problem with NEQNF
  • From: nakisa
• Re: JPG image size
  • From: Wade Ward
• Re: I/O in PURE and ELEMENTAL procedures in Fortran 2008
  • From: Wade Ward
• Re: add a0 format to language to print trimmed character variables
  • From: gary . l . scott
• Re: add a0 format to language to print trimmed character variables
  • From: Clive Page
• Re: Help with Developing a GUI for Fortran program
  • From: Edward N Bromhead
• Re: problem with NEQNF
  • From: Steve Lionel
• Re: JPG image size
  • From: Edward N Bromhead
• Re: I/O in PURE and ELEMENTAL procedures in Fortran 2008
  • From: jamesgiles@xxxxxxx
• Re: JPG image size
  • From: gary . l . scott
• Re: JPG image size
  • From: rrr7rrr
• Re: JPG image size
  • From: e p chandler
• Re: problem with NEQNF
  • From: Herman D . Knoble
• Re: problem with NEQNF
  • From: dpb
• Re: I/O in PURE and ELEMENTAL procedures in Fortran 2008
  • From: Richard Maine
• Re: I/O in PURE and ELEMENTAL procedures in Fortran 2008
  • From: Craig Powers
• Re: I/O in PURE and ELEMENTAL procedures in Fortran 2008
  • From: jamesgiles@xxxxxxx
• Re: I/O in PURE and ELEMENTAL procedures in Fortran 2008
  • From: jamesgiles@xxxxxxx
• Re: Fortran DINT help
  • From: jon
• Re: Help with Developing a GUI for Fortran program
  • From: Arjen Markus
• problem with NEQNF
  • From: nakisa
• Re: error with "if" !!!
  • From: nakisa
• JPG image size
  • From: rrr7rrr
• Re: Help with Developing a GUI for Fortran program
  • From: Beliavsky
• Re: Help with Developing a GUI for Fortran program
  • From: Arjen Markus
• Re: Help with Developing a GUI for Fortran program
  • From: SimonG
• Re: Fortran DINT help
  • From: mustafaalperkoc
• Re: Help with Developing a GUI for Fortran program
  • From: Georg
• Re: I/O in PURE and ELEMENTAL procedures in Fortran 2008
  • From: glen herrmannsfeldt
• Re: Question about KIND
  • From: Ron Shepard
• Re: I/O in PURE and ELEMENTAL procedures in Fortran 2008
  • From: Richard Maine
• Re: I/O in PURE and ELEMENTAL procedures in Fortran 2008
  • From: Beliavsky
• Re: I/O in PURE and ELEMENTAL procedures in Fortran 2008
  • From: Wade Ward
• Re: Help with Developing a GUI for Fortran program
  • From: Gary Scott
• Re: About Migrating from F77 to F95
  • From: John Harper
• Re: I/O in PURE and ELEMENTAL procedures in Fortran 2008
  • From: Richard Maine
• Re: Help with Developing a GUI for Fortran program
  • From: Terence
• Re: Help with Developing a GUI for Fortran program
  • From: Wade Ward
• Re: I/O in PURE and ELEMENTAL procedures in Fortran 2008
  • From: jamesgiles@xxxxxxx
• Re: Help with Developing a GUI for Fortran program
  • From: e p chandler

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