comp.lang.fortran

• Date Index

---

• Derived type function, proximum
  • Re: Derived type function, Richard Maine
• Re: OpenMPI Fortran: 'Error reading module mpi' and unexpected but silent termination [SOLVED], koentjepoppe
• gfortran and matlab symbol problem, Ben
  • Re: gfortran and matlab symbol problem, James Van Buskirk
    • Re: gfortran and matlab symbol problem, Ben
      • Re: gfortran and matlab symbol problem, Tim Prince
      • Re: gfortran and matlab symbol problem, Ben
      • Re: gfortran and matlab symbol problem, Richard Maine
      • Re: gfortran and matlab symbol problem, Greg Lindahl
      • Re: gfortran and matlab symbol problem, Ben
      • Re: gfortran and matlab symbol problem, Richard Maine
• elegant solution for counting runs, analyst41
  • Re: elegant solution for counting runs, Arjen Markus
    • Re: elegant solution for counting runs, Arjen Markus
      • Re: elegant solution for counting runs, David Frank
      • Re: elegant solution for counting runs, David Frank
      • Re: elegant solution for counting runs, Lars Mossberg
      • Re: elegant solution for counting runs, analyst41
• Simple F2008 feature request, Joe Krahn
  • Re: Simple F2008 feature request, Ron Shepard
    • Re: Simple F2008 feature request, Richard Maine
• keyword capitalization -- current practice, Damian
  • Re: keyword capitalization -- current practice, Gary Scott
    • Re: keyword capitalization -- current practice, Gordon Sande
    • Re: keyword capitalization -- current practice, Richard Maine
    • Re: keyword capitalization -- current practice, Craig Dedo
      • Re: keyword capitalization -- current practice, Gary Scott
      • Re: keyword capitalization -- current practice, Kris Kringle
      • Re: keyword capitalization -- current practice, John Harper
      • Re: keyword capitalization -- current practice, Phillip Helbig---remove CLOTHES to reply
      • Re: keyword capitalization -- current practice, jamesgiles@xxxxxxx
  • Re: keyword capitalization -- current practice, jamesgiles@xxxxxxx
  • Re: keyword capitalization -- current practice, Terence
    • Re: keyword capitalization -- current practice, ttw6687
  • Re: keyword capitalization -- current practice, Ron Shepard
    • Re: keyword capitalization -- current practice, Gary Scott
      • Re: keyword capitalization -- current practice, Paul van Delst
    • Re: keyword capitalization -- current practice, Gib Bogle
  • Re: keyword capitalization -- current practice, J. F. Cornwall
  • Re: keyword capitalization -- current practice, tholen
  • Re: keyword capitalization -- current practice, Rich Townsend
  • Re: keyword capitalization -- current practice, Edward N Bromhead
  • Re: keyword capitalization -- current practice, Greg Lindahl
  • Re: keyword capitalization -- current practice, Craig Powers
• gfortran and ifort gave the different result., linuxl4
  • Re: gfortran and ifort gave the different result., linuxl4
  • Re: gfortran and ifort gave the different result., Michel Olagnon
    • Re: gfortran and ifort gave the different result., Arjen Markus
      • Re: gfortran and ifort gave the different result., linuxl4
      • Re: gfortran and ifort gave the different result., Arjen Markus
      • Re: gfortran and ifort gave the different result., linuxl4
      • Re: gfortran and ifort gave the different result., Michel Olagnon
      • Re: gfortran and ifort gave the different result., linuxl4
      • Re: gfortran and ifort gave the different result., linuxl4
      • Re: gfortran and ifort gave the different result., Daniel Platt
• Re: File reading problem, galkas
• Fortran article in Physics World, Beliavsky
  • Re: Fortran article in Physics World, Terence
  • Re: Fortran article in Physics World, Gib Bogle
    • Re: Fortran article in Physics World, David Jones
• Problem with fortran subroutines called from a c program, kingpin
  • Re: Problem with fortran subroutines called from a c program, Tim Prince
    • Re: Problem with fortran subroutines called from a c program, kingpin
• Subset Sum problem (w/ limited scope), Dan
  • Re: Subset Sum problem (w/ limited scope), Dick Hendrickson
    • Re: Subset Sum problem (w/ limited scope), Gerry Ford
    • Re: Subset Sum problem (w/ limited scope), Dick Hendrickson
      • Re: Subset Sum problem (w/ limited scope), Gerry Ford
      • Re: Subset Sum problem (w/ limited scope), deltaseq0
  • Re: Subset Sum problem (w/ limited scope), deltaseq0
  • Re: Subset Sum problem (w/ limited scope), Louis Krupp
• DEC fortran file read problems, doug
  • RE: DEC fortran file read problems, meek
  • Re: DEC fortran file read problems, Terence
  • Re: DEC fortran file read problems, Terence
    • Re: DEC fortran file read problems, doug
      • Re: DEC fortran file read problems, dave weatherall
• ifort and NAG array size limitations, tomguest
  • Re: ifort and NAG array size limitations, Sjouke Burry
    • Re: ifort and NAG array size limitations, John Appleyard
  • Re: ifort and NAG array size limitations, Dr Ivan D. Reid
• F08 support of floating decimal?, David Frank
  • Re: F08 support of floating decimal?, James Giles
    • Re: F08 support of floating decimal?, robin
    • Re: F08 support of floating decimal?, glen herrmannsfeldt
    • Re: F08 support of floating decimal?, Charles Coldwell
      • Re: F08 support of floating decimal?, Gordon Sande
      • Re: F08 support of floating decimal?, jamesgiles@xxxxxxx
      • Re: F08 support of floating decimal?, glen herrmannsfeldt
      • Re: F08 support of floating decimal?, Charles Coldwell
      • Re: F08 support of floating decimal?, Richard Maine
      • Re: F08 support of floating decimal?, Charles Coldwell
      • Re: F08 support of floating decimal?, Charles Coldwell
      • Re: F08 support of floating decimal?, Dick Hendrickson
      • Re: F08 support of floating decimal?, jamesgiles@xxxxxxx
      • Re: F08 support of floating decimal?, glen herrmannsfeldt
      • Re: F08 support of floating decimal?, Gordon Sande
      • Re: F08 support of floating decimal?, glen herrmannsfeldt
      • Message not available
      • Re: F08 support of floating decimal?, Charles Coldwell
      • Re: F08 support of floating decimal?, jamesgiles@xxxxxxx
      • Re: F08 support of floating decimal?, Charles Coldwell
      • Re: F08 support of floating decimal?, glen herrmannsfeldt
      • Re: F08 support of floating decimal?, Charles Coldwell
      • Re: F08 support of floating decimal?, Charles Coldwell
      • Re: F08 support of floating decimal?, glen herrmannsfeldt
      • Message not available
      • Re: F08 support of floating decimal?, jamesgiles@xxxxxxx
      • Re: F08 support of floating decimal?, glen herrmannsfeldt
      • Re: F08 support of floating decimal?, jamesgiles@xxxxxxx
      • Re: F08 support of floating decimal?, James Van Buskirk
      • Re: F08 support of floating decimal?, jamesgiles@xxxxxxx
  • Re: F08 support of floating decimal?, Dick Hendrickson
    • Re: F08 support of floating decimal?, robin
      • Re: F08 support of floating decimal?, Dick Hendrickson
  • Message not available
    • Message not available
      • Message not available
      • Message not available
      • Re: F08 support of floating decimal?, John W. Kennedy
  • Message not available
    • Message not available
      • Message not available
      • Message not available
      • Re: F08 support of floating decimal?, glen herrmannsfeldt
  • Message not available
    • Message not available
      • Message not available
      • Message not available
      • Re: F08 support of floating decimal?, William M. Klein
• Simple loop, Snoopy
  • Re: Simple loop, Arjen Markus
    • Re: Simple loop, Snoopy
      • Re: Simple loop, e p chandler
  • Re: Simple loop, e p chandler
    • Re: Simple loop, Snoopy
      • Re: Simple loop, e p chandler
• Re: [F90] shuffle/permutation function..., deltaseq0
  • <Possible follow-ups>
  • Re: [F90] shuffle/permutation function..., Gib Bogle
• SUM in f95, James Van Buskirk
  • Re: SUM in f95, Thomas Koenig
• Can this be done cutely?, analyst41
  • Re: Can this be done cutely?, James Giles
  • Re: Can this be done cutely?, James Van Buskirk
    • Re: Can this be done cutely?, James Giles
      • Re: Can this be done cutely?, James Van Buskirk
      • Re: Can this be done cutely?, Dieter Britz
      • Re: Can this be done cutely?, analyst41
• Core dump reader, sara_patty
  • Re: Core dump reader, Arjen Markus
• a modest proposal, David Frank
  • Re: a modest proposal, Gary Scott
    • Re: a modest proposal, David Frank
      • Re: a modest proposal, garylscott
      • Re: a modest proposal, Craig Powers
      • Re: a modest proposal, Steven Correll
      • Re: a modest proposal, Craig Powers
    • Re: a modest proposal, robin
      • Re: a modest proposal, Gordon Sande
      • Re: a modest proposal, glen herrmannsfeldt
  • Re: a modest proposal, James Giles
    • Re: a modest proposal, wclodius
      • Re: a modest proposal, jamesgiles@xxxxxxx
  • Re: a modest proposal, Phillip Helbig---remove CLOTHES to reply
    • Re: a modest proposal, robert . corbett
      • Re: a modest proposal, Luka Djigas
      • Re: a modest proposal, Catherine Rees Lay
      • Re: a modest proposal, Luka Djigas
      • Re: a modest proposal, dpb
      • Re: a modest proposal, Luka Djigas
      • Re: a modest proposal, Richard Maine
      • Re: a modest proposal, James Giles
      • Re: a modest proposal, James Giles
      • Re: a modest proposal, Richard Maine
      • Re: a modest proposal, Walter Spector
      • Re: a modest proposal, James Giles
      • Re: a modest proposal, robin
      • Re: a modest proposal, robin
      • Re: a modest proposal, robin
      • Re: a modest proposal, Louis Krupp
      • Re: a modest proposal, James Giles
      • Re: a modest proposal, glen herrmannsfeldt
      • Re: a modest proposal, James Giles
      • Re: a modest proposal, Gordon Sande
      • Re: a modest proposal, James Giles
      • Re: a modest proposal, glen herrmannsfeldt
      • Re: a modest proposal, Richard Maine
      • Re: a modest proposal, glen herrmannsfeldt
      • Re: a modest proposal, Richard Maine
      • Re: a modest proposal, robin
      • Re: a modest proposal, mcalhoun
      • Re: a modest proposal, glen herrmannsfeldt
      • Re: a modest proposal, Thomas Koenig
      • Re: a modest proposal, Louis Krupp
      • Re: a modest proposal, Thomas Koenig
      • Re: a modest proposal, Louis Krupp
      • Re: a modest proposal, Greg Lindahl
      • Re: a modest proposal, Greg Lindahl
    • Re: a modest proposal, Gary Scott
      • Re: a modest proposal, robert . corbett
      • Re: a modest proposal, Gary Scott
  • Re: a modest proposal, James Van Buskirk
    • Re: a modest proposal, robin
  • Re: a modest proposal, robin
• Calling Fortran 90 from C: allocatable arrays and how to set a pointer, klohmuschel
  • Re: Calling Fortran 90 from C: allocatable arrays and how to set a pointer, Azdo
  • Re: Calling Fortran 90 from C: allocatable arrays and how to set a pointer, Jugoslav Dujic
• More experimentation with C-style optional arguments, James Van Buskirk
  • Re: More experimentation with C-style optional arguments, Steve Lionel
    • Re: More experimentation with C-style optional arguments, James Van Buskirk
      • Re: More experimentation with C-style optional arguments, James Van Buskirk
• linking to Fortran libraries from C fails, Ed
  • Re: linking to Fortran libraries from C fails, Arjen Markus
    • Re: linking to Fortran libraries from C fails, Ed
      • Re: linking to Fortran libraries from C fails, Arjen Markus
      • Re: linking to Fortran libraries from C fails, Ed
      • Re: linking to Fortran libraries from C fails, Arjen Markus
• Essential Features, garylscott
  • Re: Essential Features, James Giles
    • Re: Essential Features, James Van Buskirk
    • Re: Essential Features, Gary Scott
      • Re: Essential Features, Richard Maine
      • Re: Essential Features, Gary Scott
      • Re: Essential Features, Gerry Ford
    • Re: Essential Features, Steven Correll
  • Re: Essential Features, Walter Spector
    • Re: Essential Features, Gary Scott
      • Re: Essential Features, Walter Spector
      • Re: Essential Features, garylscott
• Trouble with Hollerith, James Van Buskirk
  • Re: Trouble with Hollerith, FX
  • Re: Trouble with Hollerith, Richard Maine
    • Re: Trouble with Hollerith, John Harper
  • Re: Trouble with Hollerith, Steve Lionel
    • Re: Trouble with Hollerith, Steve Lionel
      • Re: Trouble with Hollerith, James Van Buskirk
      • Re: Trouble with Hollerith, Steve Lionel
      • Re: Trouble with Hollerith, James Van Buskirk
      • Re: Trouble with Hollerith, Richard Maine
    • Re: Trouble with Hollerith, Richard Maine
    • Re: Trouble with Hollerith, FX
      • Re: Trouble with Hollerith, James Van Buskirk
      • Re: Trouble with Hollerith, Steve Lionel
      • Re: Trouble with Hollerith, glen herrmannsfeldt
      • Re: Trouble with Hollerith, James Giles
      • Re: Trouble with Hollerith, Richard Maine
      • Re: Trouble with Hollerith, James Giles
• Re: multi-threaded FFTW segmentation fault with gfortran, Steven G. Kargl
  • Re: multi-threaded FFTW segmentation fault with gfortran, mpbro
  • <Possible follow-ups>
  • Re: multi-threaded FFTW segmentation fault with gfortran, Steven G. Johnson
    • Message not available
      • Re: multi-threaded FFTW segmentation fault with gfortran, mpbro
    • Message not available
      • Re: multi-threaded FFTW segmentation fault with gfortran, Steven G. Johnson
      • Re: multi-threaded FFTW segmentation fault with gfortran, Steven G. Johnson
      • Re: multi-threaded FFTW segmentation fault with gfortran, Steven G. Kargl
      • Re: multi-threaded FFTW segmentation fault with gfortran, Steven G. Johnson
      • Re: multi-threaded FFTW segmentation fault with gfortran, Steven G. Johnson
      • Re: multi-threaded FFTW segmentation fault with gfortran, mpbro
      • Re: multi-threaded FFTW segmentation fault with gfortran, Steven G. Johnson
      • Re: multi-threaded FFTW segmentation fault with gfortran, Steven G. Kargl
    • Re: multi-threaded FFTW segmentation fault with gfortran, glen herrmannsfeldt
      • DOUBLE COMPLEX, robert . corbett
      • Re: DOUBLE COMPLEX, glen herrmannsfeldt
      • Re: DOUBLE COMPLEX, Richard Maine
      • Re: DOUBLE COMPLEX, Paul van Delst
      • Re: DOUBLE COMPLEX, Jan Gerrit Kootstra
      • Re: DOUBLE COMPLEX, Paul van Delst
      • Re: DOUBLE COMPLEX, Richard Maine
• Standardised array descriptors, Sebastian Hanigk
  • Re: Standardised array descriptors, Steve Lionel
    • Re: Standardised array descriptors, Dick Hendrickson
      • Re: Standardised array descriptors, Steve Lionel
      • Re: Standardised array descriptors, Sebastian Hanigk
    • Re: Standardised array descriptors, Sebastian Hanigk
      • Re: Standardised array descriptors, Steve Lionel
      • Re: Standardised array descriptors, Sebastian Hanigk
      • Re: Standardised array descriptors, Greg Lindahl
      • Re: Standardised array descriptors, Steve Lionel
• BBC, Michael Metcalf
  • Re: BBC, Jugoslav Dujic
  • Re: BBC, Bill Gunshannon
    • Re: BBC, Michael Metcalf
      • Re: BBC, Michael Metcalf
      • Re: BBC, Tom Micevski
      • Re: BBC, user1
      • Re: BBC, Walter Spector
      • Re: BBC, Terence
      • Re: BBC, aeroguy
      • Re: BBC, Bill Gunshannon
• Fortran Start Page, J.Verburgt
  • Re: Fortran Start Page, Luka Djigas
    • Re: Fortran Start Page, glen herrmannsfeldt
      • Re: Fortran Start Page, Luka Djigas
      • Re: Fortran Start Page, glen herrmannsfeldt
      • Re: Fortran Start Page, Terence
  • Re: Fortran Start Page, David Jones
    • Re: Fortran Start Page, J.Verburgt
• Re: num.analysis, Eugene Miya
  • Re: num.analysis, Steven G. Kargl
  • Re: num.analysis, Gordon Sande
  • <Possible follow-ups>
  • Re: num.analysis, robin
  • Re: num.analysis, wade
    • Re: num.analysis, Steven G. Kargl
      • Re: num.analysis, Gerry Ford
• moving from ifort to gfortran, merrittr
  • Re: moving from ifort to gfortran, paul . richard . thomas
    • Re: moving from ifort to gfortran, merrittr
      • Re: moving from ifort to gfortran, Steven G. Kargl
      • Re: moving from ifort to gfortran, merrittr
• nopass attribute for type-bound overloaded operators in F2003?, Damian
  • Re: nopass attribute for type-bound overloaded operators in F2003?, Richard Maine
• call a function, Mike
  • Re: call a function, Richard Maine
    • Re: call a function, glen herrmannsfeldt
      • Re: call a function, Mike
      • Re: call a function, Jugoslav Dujic
      • Re: call a function, glen herrmannsfeldt
    • Re: call a function, e p chandler
• :: operator considered harmful?, holst
  • Re: :: operator considered harmful?, fj
    • Re: :: operator considered harmful?, Bil Kleb
  • Re: :: operator considered harmful?, Steven G. Kargl
    • Re: :: operator considered harmful?, holst
      • Re: :: operator considered harmful?, James Van Buskirk
    • Re: :: operator considered harmful?, Jan Vorbrüggen
      • Re: :: operator considered harmful?, John Harper
      • Re: :: operator considered harmful?, Steve Lionel
      • Re: :: operator considered harmful?, John Harper
      • Re: :: operator considered harmful?, Richard Maine
      • Re: :: operator considered harmful?, Toon Moene
      • Re: :: operator considered harmful?, robin
      • Re: :: operator considered harmful?, Dick Hendrickson
  • Re: :: operator considered harmful?, James Giles
    • Re: :: operator considered harmful?, holst
      • Re: :: operator considered harmful?, James Giles
    • Re: :: operator considered harmful?, Gary Scott
      • Re: :: operator considered harmful?, James Giles
      • Re: :: operator considered harmful?, Gary Scott
      • Re: :: operator considered harmful?, Richard Maine
  • Re: :: operator considered harmful?, Richard Maine
  • Re: :: operator considered harmful?, Dave Seaman
  • Re: :: operator considered harmful?, David Flower
  • Re: :: operator considered harmful?, Michael Metcalf
    • Re: :: operator considered harmful?, Dick Hendrickson
      • Re: :: operator considered harmful?, garylscott
      • Re: :: operator considered harmful?, dpb
      • Re: :: operator considered harmful?, Dick Hendrickson
  • Re: :: operator considered harmful?, robin
• thanks to all, David Rowell
  • Re: thanks to all, Élodie
• some help please about "WRITE", Élodie
  • Re: some help please about "WRITE", Dave Seaman
    • Re: some help please about "WRITE", Élodie
      • Re: some help please about "WRITE", Dave Seaman
      • Re: some help please about "WRITE", Élodie
      • Re: some help please about "WRITE", glen herrmannsfeldt
• A simple example on widgets with dislin 9.2, Ed
  • Re: A simple example on widgets with dislin 9.2, baf
    • Re: A simple example on widgets with dislin 9.2, Ed
      • Re: A simple example on widgets with dislin 9.2, paul . richard . thomas
      • Re: A simple example on widgets with dislin 9.2, Ed
      • Re: A simple example on widgets with dislin 9.2, baf
    • Re: A simple example on widgets with dislin 9.2, michels
      • Re: A simple example on widgets with dislin 9.2, Luka Djigas
      • Re: A simple example on widgets with dislin 9.2, michels
  • Re: A simple example on widgets with dislin 9.2, Clive Page
    • Re: A simple example on widgets with dislin 9.2, Ed
• Passing arrays between a module to a subroutine, deltaseq0
  • Re: Passing arrays between a module to a subroutine, Michael Metcalf
    • Re: Passing arrays between a module to a subroutine, deltaseq0
• Does this array constructor follow the standard Fortran90/95?, hermitian
  • Re: Does this array constructor follow the standard Fortran90/95?, Dan Nagle
    • Re: Does this array constructor follow the standard Fortran90/95?, hermitian
      • Re: Does this array constructor follow the standard Fortran90/95?, Michael Metcalf
  • Re: Does this array constructor follow the standard Fortran90/95?, glen herrmannsfeldt
    • Re: Does this array constructor follow the standard Fortran90/95?, Gib Bogle
      • Re: Does this array constructor follow the standard Fortran90/95?, Richard Maine
      • Re: Does this array constructor follow the standard Fortran90/95?, Gib Bogle
      • Re: Does this array constructor follow the standard Fortran90/95?, Richard Maine
      • Re: Does this array constructor follow the standard Fortran90/95?, Gib Bogle
      • Re: Does this array constructor follow the standard Fortran90/95?, John Harper
      • Re: Does this array constructor follow the standard Fortran90/95?, Gib Bogle
      • Re: Does this array constructor follow the standard Fortran90/95?, James Giles
      • Re: Does this array constructor follow the standard Fortran90/95?, glen herrmannsfeldt
      • Re: Does this array constructor follow the standard Fortran90/95?, Gib Bogle
      • Re: Does this array constructor follow the standard Fortran90/95?, David Frank
      • Re: Does this array constructor follow the standard Fortran90/95?, glen herrmannsfeldt
      • Re: Does this array constructor follow the standard Fortran90/95?, hermitian
      • Re: Does this array constructor follow the standard Fortran90/95?, Charles Coldwell
      • Re: Does this array constructor follow the standard Fortran90/95?, Michael Metcalf
      • Re: Does this array constructor follow the standard Fortran90/95?, Tim Prince
• OPTIONAL dummy arguments, Mike
  • Re: OPTIONAL dummy arguments, James Tursa
    • Re: OPTIONAL dummy arguments, Mike
      • Re: OPTIONAL dummy arguments, Richard Maine
      • Re: OPTIONAL dummy arguments, James Giles
• an Invitation to be Involved in a Survey on Developing Scientific Computing Software, Janet93
  • Re: an Invitation to be Involved in a Survey on Developing Scientific Computing Software, Colin Watters
• "actual argument keyword name", Mike
  • "actual argument keyword name", Terence
    • Re: "actual argument keyword name", Richard Maine
      • Re: "actual argument keyword name", Mike
      • Re: "actual argument keyword name", Gary Scott
      • Re: "actual argument keyword name", Richard Maine
      • Re: "actual argument keyword name", Gary Scott
      • Re: "actual argument keyword name", Richard Maine
      • Re: "actual argument keyword name", garylscott
      • Re: "actual argument keyword name", jwm
      • Re: "actual argument keyword name", Richard Maine
      • Re: "actual argument keyword name", jwm
      • Re: "actual argument keyword name", Steve Lionel
      • Re: "actual argument keyword name", jwm
      • Re: "actual argument keyword name", Richard Maine
      • Re: "actual argument keyword name", Steve Lionel
      • Re: "actual argument keyword name", Richard Maine
  • Re: "actual argument keyword name", Craig Dedo
  • Re: "actual argument keyword name", Gary Scott
• Xcode, Intel ifort and opening files, Markus S
  • Re: Xcode, Intel ifort and opening files, FX
  • Re: Xcode, Intel ifort and opening files, Markus S
    • Re: Xcode, Intel ifort and opening files, Dave Seaman
  • Re: Xcode, Intel ifort and opening files, Steve Lionel
• Fortran 2003 abstract type and interface question, Damian
  • Re: Fortran 2003 abstract type and interface question, Reinhold Bader
  • Re: Fortran 2003 abstract type and interface question - correction, Reinhold Bader
  • Re: Fortran 2003 abstract type and interface question, Michael Metcalf
  • Re: Fortran 2003 abstract type and interface question, Reinhold Bader
• Q: File read problem - numbers separated by ;, Luka Djigas
  • Re: Q: File read problem - numbers separated by ;, Richard Maine
• equivalence statement, aeroguy
  • Re: equivalence statement, glen herrmannsfeldt
    • Re: equivalence statement, Bart Vandewoestyne
      • Re: equivalence statement, Jan Vorbrüggen
      • Re: equivalence statement, Bart Vandewoestyne
      • Re: equivalence statement, Arjen Markus
      • Re: equivalence statement, glen herrmannsfeldt
      • Re: equivalence statement, garylscott
      • Re: equivalence statement, Dick Hendrickson
      • Re: equivalence statement, Lynn McGuire
      • Re: equivalence statement, Richard Maine
      • Re: equivalence statement, Lynn McGuire
      • Re: equivalence statement, glen herrmannsfeldt
      • Re: equivalence statement, Terence
      • Re: equivalence statement, Gordon Sande
      • Re: equivalence statement, Lynn McGuire
      • Re: equivalence statement, Gordon Sande
      • Re: equivalence statement, glen herrmannsfeldt
    • Re: equivalence statement, Dick Hendrickson
  • Re: equivalence statement, David Flower
• Orthogonal Wavelet Transforms, NZTideMan
• GPU usesable as CPU, Terence
• f03?, Dieter Britz
  • Re: f03?, Tobias Burnus
  • Re: f03?, Bart Vandewoestyne
    • Re: f03?, andy271828
      • Re: f03?, Tobias Burnus
      • Re: f03?, Bart Vandewoestyne
      • Re: f03?, James Van Buskirk
      • Re: f03?, Richard Maine
      • Re: f03?, Bart Vandewoestyne
      • Re: f03?, Richard Maine
      • Re: f03?, Bart Vandewoestyne
      • Re: f03?, glen herrmannsfeldt
      • Re: f03?, Bart Vandewoestyne
      • Fortran 2003 Test Suite (Was: f03?), Craig Dedo
      • Re: Fortran 2003 Test Suite, Richard Maine
      • Re: Fortran 2003 Test Suite, dpb
      • Re: Fortran 2003 Test Suite, Richard Maine
      • Re: Fortran 2003 Test Suite, Steve Lionel
      • Re: Fortran 2003 Test Suite, dpb
      • Re: Fortran 2003 Test Suite, James Van Buskirk
      • Re: Fortran 2003 Test Suite, Greg Lindahl
      • Re: Fortran 2003 Test Suite, Jan Vorbrüggen
      • Re: f03?, Dick Hendrickson
      • Re: f03?, FX
  • Re: f03?, Dieter Britz
    • Re: f03?, garylscott
    • Re: f03?, Tobias Burnus
      • Re: f03?, James Giles
      • Re: f03?, Steven G. Kargl
    • Re: f03?, Paul van Delst
      • Re: f03?, James Giles
      • Re: f03?, Paul van Delst
      • Re: f03?, Gary Scott
      • Re: f03?, Paul van Delst
      • Re: f03?, garylscott
      • Re: f03?, James Giles
      • Re: f03?, garylscott
      • Re: f03?, Paul van Delst
      • Re: f03?, garylscott
      • Re: f03?, Greg Lindahl
      • Re: f03?, Paul van Delst
      • Re: f03?, garylscott
      • Re: f03?, Craig Powers
      • Re: f03?, James Giles
• Reintroduction to FORTRAN after >30 years, Richard Owlett
  • Re: Reintroduction to FORTRAN after >30 years, Michael Metcalf
    • Re: Reintroduction to FORTRAN after >30 years, Bil Kleb
      • Re: Reintroduction to FORTRAN after >30 years, Richard Owlett
  • Re: Reintroduction to FORTRAN after >30 years, baf
  • Re: Reintroduction to FORTRAN after >30 years, Bart Vandewoestyne
    • Re: Reintroduction to FORTRAN after >30 years, Bil Kleb
    • Re: Reintroduction to FORTRAN after >30 years, Les
      • Re: Reintroduction to FORTRAN after >30 years, Bil Kleb
      • Re: Reintroduction to FORTRAN after >30 years, FX
      • Re: Reintroduction to FORTRAN after >30 years, Ian Bush
      • Re: Reintroduction to FORTRAN after >30 years, Bil Kleb
      • Re: Reintroduction to FORTRAN after >30 years, jwm
      • Re: Reintroduction to FORTRAN after >30 years, Dr Ivan D. Reid
  • Re: Reintroduction to FORTRAN after >30 years, Ian
• A question about NAG Fortran compiler?, li . simula
  • Re: A question about NAG Fortran compiler?, dpb
    • Re: A question about NAG Fortran compiler?, li . simula
      • Re: A question about NAG Fortran compiler?, John Harper
• help me please, gotzz
  • Re: help me please, Jim Backus
  • Re: help me please, Richard Maine
  • Re: help me please, Luka Djigas
    • Re: help me please, gotzz
      • Re: help me please, Luka Djigas
      • Re: help me please, gotzz
      • Re: help me please, pixel
  • Re: help me please, Catherine Rees Lay
• log10 - g95 bug?, Nestor Grion
  • Re: log10 - g95 bug?, James Van Buskirk
    • Re: log10 - g95 bug?, glen herrmannsfeldt
      • Re: log10 - g95 bug?, robin
      • Re: log10 - g95 bug?, glen herrmannsfeldt
      • Re: log10 - g95 bug?, robin
      • Re: log10 - g95 bug?, glen herrmannsfeldt
      • Re: log10 - g95 bug?, John Harper
      • Re: log10 - g95 bug?, robin
      • Re: log10 - g95 bug?, John Harper
      • Re: log10 - g95 bug?, robin
• Problems with unformatted files on mpich + nfs, antok.tm
  • Re: Problems with unformatted files on mpich + nfs, Ron Shepard
    • Re: Problems with unformatted files on mpich + nfs, antok.tm
      • Re: Problems with unformatted files on mpich + nfs, Ken . Fairfield
      • Re: Problems with unformatted files on mpich + nfs, antok.tm
• fseek and unformatted sequential files, huxiankui
  • Re: fseek and unformatted sequential files, Craig Dedo
    • Re: fseek and unformatted sequential files, Richard Maine
      • Re: fseek and unformatted sequential files, william
      • Re: fseek and unformatted sequential files, Richard Maine
      • Re: fseek and unformatted sequential files, Craig Dedo
      • Re: fseek and unformatted sequential files, Richard Maine
  • Re: fseek and unformatted sequential files, Richard Maine
    • Re: fseek and unformatted sequential files, william
      • Re: fseek and unformatted sequential files, Richard Maine
      • Re: fseek and unformatted sequential files, william
      • Re: fseek and unformatted sequential files, william
      • Re: fseek and unformatted sequential files, Richard Maine
      • Re: fseek and unformatted sequential files, william
      • Re: fseek and unformatted sequential files, dpb
  • Re: fseek and unformatted sequential files, David Frank
    • Re: fseek and unformatted sequential files, Tobias Burnus
      • Re: fseek and unformatted sequential files, Richard Maine
      • Re: fseek and unformatted sequential files, David Frank
  • Re: fseek and unformatted sequential files, Jerry DeLisle
• Internal file question, Paul van Delst
  • Re: Internal file question, Dick Hendrickson
  • Re: Internal file question, Michael Metcalf
    • Re: Internal file question, Richard Maine
      • Re: Internal file question, Paul van Delst
      • Re: Internal file question, Richard Maine
      • Re: Internal file question, Dick Hendrickson
      • Re: Internal file question, Paul van Delst
      • Re: Internal file question, Dan Nagle
      • Re: Internal file question, Dick Hendrickson
      • Re: Internal file question, Paul van Delst
      • Re: Internal file question, glen herrmannsfeldt
  • Re: Internal file question, Richard Maine
    • Re: Internal file question, glen herrmannsfeldt
      • Re: Internal file question, Michael Metcalf
      • Re: Internal file question, Paul van Delst
      • Re: Internal file question, Michael Metcalf
      • Re: Internal file question, Richard Maine
      • Re: Internal file question, Paul van Delst
      • Re: Internal file question, Richard Maine
      • Re: Internal file question, Dick Hendrickson
      • Re: Internal file question, Richard Maine
• Portability and kind problems, David Simpson
  • Re: Portability and kind problems, Dan Nagle
    • Re: Portability and kind problems, David Simpson
      • Re: Portability and kind problems, glen herrmannsfeldt
      • Re: Portability and kind problems, James Giles
  • Re: Portability and kind problems, Tobias Burnus
  • Re: Portability and kind problems, glen herrmannsfeldt
    • Re: Portability and kind problems, David Simpson
      • Re: Portability and kind problems, glen herrmannsfeldt
      • Re: Portability and kind problems, robin
      • Re: Portability and kind problems, glen herrmannsfeldt
    • Re: Portability and kind problems, robin
      • Re: Portability and kind problems, glen herrmannsfeldt
      • Re: Portability and kind problems, robin
      • Re: Portability and kind problems, glen herrmannsfeldt
  • Re: Portability and kind problems, Herman D . Knoble
  • Re: Portability and kind problems, James Van Buskirk
  • Re: Portability and kind problems, robin
• Makefile, merrittr
  • Re: Makefile, Tobias Burnus
  • Re: Makefile, Hani
• Re: More gfortran and BIND(C), David Thompson
• Best Command Line Parsers, Gary Scott
  • Re: Best Command Line Parsers, Ken . Fairfield
  • Re: Best Command Line Parsers, Bil Kleb
    • Re: Best Command Line Parsers, Gary Scott
• array argument question, analyst41
  • Re: array argument question, deltaseq0
  • Re: array argument question, paul . richard . thomas
    • Re: array argument question, analyst41
      • Re: array argument question, glen herrmannsfeldt
      • Re: array argument question, Richard Maine
      • Re: array argument question, glen herrmannsfeldt
      • Re: array argument question, Richard Maine
      • Re: array argument question, glen herrmannsfeldt
      • Re: array argument question, Richard Maine
      • Re: array argument question, robin
    • Re: array argument question, robin
  • Re: array argument question, John Harper
  • Re: array argument question, Herman D . Knoble
    • Re: array argument question, analyst41
• Re: Object Oriented Optimization, relaxmike
  • Re: Object Oriented Optimization, glen herrmannsfeldt
• moving fortran code from win32->ifort on unix, merrittr
  • Re: moving fortran code from win32->ifort on unix, SimonG
    • Re: moving fortran code from win32->ifort on unix, tim prince
  • Re: moving fortran code from win32->ifort on unix, Craig Powers
• Salford FTN 95 output window problem, Mathemagician
  • Re: Salford FTN 95 output window problem, Edward N Bromhead
    • Re: Salford FTN 95 output window problem, Mathemagician
• Debugging with g95 on windows, jre
  • Re: Debugging with g95 on windows, Arjen Markus
    • Re: Debugging with g95 on windows, Beliavsky
      • Re: Debugging with g95 on windows, Bart Vandewoestyne
      • Re: Debugging with g95 on windows, Richard Maine
      • Re: Debugging with g95 on windows, Gib Bogle
      • Re: Debugging with g95 on windows, Mike McGinn
      • Re: Debugging with g95 on windows, Pierre Asselin
      • Re: Debugging with g95 on windows, J.F. Cornwall
      • Re: Debugging with g95 on windows, Bart Vandewoestyne
      • Re: Debugging with g95 on windows, Arjen Markus
      • Re: Debugging with g95 on windows, Helge Avlesen
      • Re: Debugging with g95 on windows, Janne Blomqvist
      • Re: Debugging with g95 on windows, Helge Avlesen
    • Re: Debugging with g95 on windows, Steven Correll
      • Re: Debugging with g95 on windows, FX
      • Re: Debugging with g95 on windows, Tobias Burnus
      • Re: Debugging with g95 on windows, David Duffy
      • Re: Debugging with g95 on windows, FX
  • Re: Debugging with g95 on windows, mecej4
  • Re: Debugging with g95 on windows, Bil Kleb
    • Re: Debugging with g95 on windows, jre
• simulation by fortran, ramiAIT
  • Re: simulation by fortran, Richard Maine
  • Re: simulation by fortran, Bart Vandewoestyne
  • Re: simulation by fortran, David Flower
  • Re: simulation by fortran, Les
    • Re: simulation by fortran, David Jones
      • Re: simulation by fortran, Les
      • Re: simulation by fortran, Terence
      • Re: simulation by fortran, e p chandler
  • Re: simulation by fortran, Gib Bogle
• anyone have a f77 grammar?, Mathew
  • Re: anyone have a f77 grammar?, glen herrmannsfeldt
    • Re: anyone have a f77 grammar?, wclodius
      • Re: anyone have a f77 grammar?, Mathew
• USE question, merrittr
  • Re: USE question, merrittr
    • Re: USE question, Paul van Delst
      • Re: USE question, merrittr
  • Re: USE question, Richard Maine
• command line arguments, sperry01
  • Re: command line arguments, Steven G. Kargl
  • Re: command line arguments, Craig Dedo
    • Re: command line arguments, Hani Ibrahim
  • Re: command line arguments, e p chandler
• memory and data types, s
  • Re: memory and data types, Michael Metcalf
    • Re: memory and data types, s
      • Re: memory and data types, Michael Metcalf
  • Re: memory and data types, yaqi
  • Re: memory and data types, Richard Maine
    • Re: memory and data types, s
      • Re: memory and data types, Richard Maine
      • [OT] Re: memory and data types, Bart Vandewoestyne
      • Re: [OT] Re: memory and data types, Richard Maine
    • Re: memory and data types, s
      • Re: memory and data types, Ken . Fairfield
      • Re: memory and data types, Dan Nagle
      • Re: memory and data types, Gary Scott
      • Re: memory and data types, jamesgiles@xxxxxxx
      • Re: memory and data types, Gary Scott
      • Re: memory and data types, David Thompson
      • Re: memory and data types, Dick Hendrickson
      • Re: memory and data types, John Harper
      • Re: memory and data types, glen herrmannsfeldt
      • Re: memory and data types, Ken . Fairfield
      • Re: memory and data types, glen herrmannsfeldt
      • Re: memory and data types, Ken . Fairfield
      • Re: memory and data types, glen herrmannsfeldt
  • Re: memory and data types, David Flower
• reading conf file: list directed I/O?, Bart Vandewoestyne
  • Re: reading conf file: list directed I/O?, e p chandler
    • Re: reading conf file: list directed I/O?, Bart Vandewoestyne
  • Re: reading conf file: list directed I/O?, dpb
    • Re: reading conf file: list directed I/O?, Bart Vandewoestyne
      • Re: reading conf file: list directed I/O?, dpb
  • Re: reading conf file: list directed I/O?, Bart Vandewoestyne
    • Re: reading conf file: list directed I/O?, Joseph Huber
      • Re: reading conf file: list directed I/O?, Bart Vandewoestyne
      • Re: reading conf file: list directed I/O?, Joseph Huber
      • Re: reading conf file: list directed I/O?, Bart Vandewoestyne
      • Re: reading conf file: list directed I/O?, Joseph Huber
      • Re: reading conf file: list directed I/O?, Joseph Huber
      • Re: reading conf file: list directed I/O?, Bart Vandewoestyne
      • Re: reading conf file: list directed I/O?, Joseph Huber
      • Re: reading conf file: list directed I/O?, Richard Maine
      • Re: reading conf file: list directed I/O?, Joseph Huber
      • Message not available
      • Re: reading conf file: list directed I/O?, Jugoslav Dujic
  • Re: reading conf file: list directed I/O?, Paul van Delst
• Heap corruption, Michael K. Johnston
  • Re: Heap corruption, Craig Dedo
  • Re: Heap corruption, James Van Buskirk
    • Re: Heap corruption, Michael K. Johnston
      • Re: Heap corruption, Craig Powers
• checking if file exists in user's home directory, Bart Vandewoestyne
  • Re: checking if file exists in user's home directory, Steven G. Kargl
    • Re: checking if file exists in user's home directory, Bart Vandewoestyne
      • Re: checking if file exists in user's home directory, Richard Maine
      • Re: checking if file exists in user's home directory, Dan Nagle
      • Re: checking if file exists in user's home directory, Richard Maine
      • Re: checking if file exists in user's home directory, Bart Vandewoestyne
      • Re: checking if file exists in user's home directory, Craig Dedo
      • Re: checking if file exists in user's home directory, Paul van Delst
      • Re: checking if file exists in user's home directory, Hani Ibrahim
  • Re: checking if file exists in user's home directory, Richard Maine
  • Re: checking if file exists in user's home directory, Joseph Huber
  • Re: checking if file exists in user's home directory, Ron Shepard
• Password security, johnharwood@xxxxxxxxxx
  • Re: Password security, Daniel Snouck
  • Re: Password security, garylscott
  • Re: Password security, deltaseq0
    • Re: Password security, deltaseq0
      • Re: Password security, Daniel Snouck
• Does g77 allows #include directives in FORTRAN 77 applications, ravi
  • Re: Does g77 allows #include directives in FORTRAN 77 applications, Richard Maine
    • Re: Does g77 allows #include directives in FORTRAN 77 applications, glen herrmannsfeldt
      • Re: Does g77 allows #include directives in FORTRAN 77 applications, Richard Maine
  • Re: Does g77 allows #include directives in FORTRAN 77 applications, ravi
    • Re: Does g77 allows #include directives in FORTRAN 77 applications, Ron Shepard
      • Re: Does g77 allows #include directives in FORTRAN 77 applications, ravi
      • Re: Does g77 allows #include directives in FORTRAN 77 applications, ravi
      • Re: Does g77 allows #include directives in FORTRAN 77 applications, Catherine Rees Lay
      • Re: Does g77 allows #include directives in FORTRAN 77 applications, ravi
      • Re: Does g77 allows #include directives in FORTRAN 77 applications, ravi
      • Re: Does g77 allows #include directives in FORTRAN 77 applications, Jugoslav Dujic
      • Re: Does g77 allows #include directives in FORTRAN 77 applications, Les
      • Re: Does g77 allows #include directives in FORTRAN 77 applications, Tim Prince
• gfortran read of hex values, trizzzat
  • Re: gfortran read of hex values, Steven G. Kargl
  • Re: gfortran read of hex values, Tobias Burnus
    • Re: gfortran read of hex values, Richard Maine
      • Re: gfortran read of hex values, trizzzat
      • Re: gfortran read of hex values, James Van Buskirk
      • Re: gfortran read of hex values, FX
      • Re: gfortran read of hex values, James Van Buskirk
      • Re: gfortran read of hex values, Walter Spector
      • Re: gfortran read of hex values, James Van Buskirk
      • Re: gfortran read of hex values, Walter Spector
      • Re: gfortran read of hex values, Walter Spector
      • Re: gfortran read of hex values, James Van Buskirk
      • Re: gfortran read of hex values, Walter Spector
      • Re: gfortran read of hex values, James Van Buskirk
      • Re: gfortran read of hex values, Thomas Koenig
      • Re: gfortran read of hex values, James Van Buskirk
  • Re: gfortran read of hex values, Paul van Delst
    • Re: gfortran read of hex values, glen herrmannsfeldt
      • Re: gfortran read of hex values, Steven G. Kargl
      • Re: gfortran read of hex values, glen herrmannsfeldt
    • Re: gfortran read of hex values, FX
      • Re: gfortran read of hex values, Jugoslav Dujic
      • Re: gfortran read of hex values, trizzzat
      • Re: gfortran read of hex values, Steven G. Kargl
      • Re: gfortran read of hex values, trizzzat
      • Re: gfortran read of hex values, trizzzat
      • Re: gfortran read of hex values, Steven G. Kargl
      • Re: gfortran read of hex values, John Harper
      • Re: gfortran read of hex values, Tobias Burnus
      • Re: gfortran read of hex values, James Van Buskirk
      • Re: gfortran read of hex values, John Harper
    • Re: gfortran read of hex values, Tobias Burnus
• Re: linking to OpenMP run-time library with gfortran, Craig Powers
• Re: reading two separate files, sara_patty
  • Re: reading two separate files, Dick Hendrickson
    • Re: reading two separate files, sara_patty
      • Re: reading two separate files, Richard Maine
      • Re: reading two separate files, Gary Scott
      • Unit Numbers (Was: reading two separate files), Craig Dedo
      • Re: Unit Numbers (Was: reading two separate files), Gary Scott
      • Re: reading two separate files, glen herrmannsfeldt
      • Re: reading two separate files, sara_patty
      • Re: reading two separate files, Gary Scott
      • Re: reading two separate files, Richard Maine
      • Re: reading two separate files, Dan Nagle
      • Re: reading two separate files, sara_patty
      • Re: reading two separate files, Dan Nagle
      • Re: reading two separate files, John Harper
      • Re: reading two separate files, dpb
      • Re: reading two separate files, Michael Metcalf
      • Re: reading two separate files, Gary Scott
      • Re: reading two separate files, glen herrmannsfeldt
      • Re: reading two separate files, dpb
      • Re: reading two separate files, Richard Maine
      • Re: reading two separate files, sara_patty
      • Re: reading two separate files, dpb
      • Re: reading two separate files, Paul van Delst
  • RE: reading two separate files, meek
• Copying common blocks, James Emil Avery
  • Re: Copying common blocks, Salvatore
    • Re: Copying common blocks, Dan Nagle
  • Re: Copying common blocks, glen herrmannsfeldt
    • Re: Copying common blocks, James Emil Avery
      • Re: Copying common blocks, David Jones
• how-to write output in 'n' columns through 'n' access of the output file?, ab
  • Re: how-to write output in 'n' columns through 'n' access of the output file?, glen herrmannsfeldt
    • Re: how-to write output in 'n' columns through 'n' access of the output file?, ab
      • Re: how-to write output in 'n' columns through 'n' access of the output file?, dpb
      • Re: how-to write output in 'n' columns through 'n' access of the output file?, Les
  • Re: how-to write output in 'n' columns through 'n' access of the output file?, fj
  • Re: how-to write output in 'n' columns through 'n' access of the output file?, Dan
• VECTOR data types and intrinsic functions, standwind@xxxxxxxxx
  • Re: VECTOR data types and intrinsic functions, glen herrmannsfeldt
  • Re: VECTOR data types and intrinsic functions, Ian Bush
    • Re: VECTOR data types and intrinsic functions, Sa Liu
  • Re: VECTOR data types and intrinsic functions, Dan Nagle
  • Re: VECTOR data types and intrinsic functions, Paul van Delst
    • Re: VECTOR data types and intrinsic functions, Ken . Fairfield
      • Re: VECTOR data types and intrinsic functions, fj
    • Re: VECTOR data types and intrinsic functions, glen herrmannsfeldt
      • Re: VECTOR data types and intrinsic functions, Steven G. Kargl
      • Re: VECTOR data types and intrinsic functions, glen herrmannsfeldt
      • Re: VECTOR data types and intrinsic functions, FX
      • Re: VECTOR data types and intrinsic functions, Tobias Burnus
      • Re: VECTOR data types and intrinsic functions, Richard Maine
      • Re: VECTOR data types and intrinsic functions, Dan Nagle
      • Re: VECTOR data types and intrinsic functions, glen herrmannsfeldt
      • Re: VECTOR data types and intrinsic functions, Richard Maine
      • Re: VECTOR data types and intrinsic functions, Sa Liu
      • Re: VECTOR data types and intrinsic functions, glen herrmannsfeldt
      • Re: VECTOR data types and intrinsic functions, Sa Liu
      • Re: VECTOR data types and intrinsic functions, robin
      • Re: VECTOR data types and intrinsic functions, glen herrmannsfeldt
      • Re: VECTOR data types and intrinsic functions, robin
  • Re: VECTOR data types and intrinsic functions, Joost
    • Re: VECTOR data types and intrinsic functions, Dan Nagle
      • Re: VECTOR data types and intrinsic functions, glen herrmannsfeldt
      • Re: VECTOR data types and intrinsic functions, Dan Nagle
      • Re: VECTOR data types and intrinsic functions, Sa Liu
      • Re: VECTOR data types and intrinsic functions, Dan Nagle
      • Re: VECTOR data types and intrinsic functions, robin
      • Re: VECTOR data types and intrinsic functions, Sa Liu
      • Re: VECTOR data types and intrinsic functions, robin
      • Re: VECTOR data types and intrinsic functions, glen herrmannsfeldt
      • Re: VECTOR data types and intrinsic functions, Dan Nagle
      • Re: VECTOR data types and intrinsic functions, Sebastian Hanigk
      • Re: VECTOR data types and intrinsic functions, robin
      • Re: VECTOR data types and intrinsic functions, Greg Lindahl
      • Re: VECTOR data types and intrinsic functions, Dan Nagle
      • Re: VECTOR data types and intrinsic functions, Greg Lindahl
      • Re: VECTOR data types and intrinsic functions, Dan Nagle
      • Re: VECTOR data types and intrinsic functions, robin
      • Re: VECTOR data types and intrinsic functions, robin
      • Re: VECTOR data types and intrinsic functions, robin
      • Re: VECTOR data types and intrinsic functions, Joost
      • Re: VECTOR data types and intrinsic functions, Dan Nagle
      • Re: VECTOR data types and intrinsic functions, glen herrmannsfeldt
      • Re: VECTOR data types and intrinsic functions, robin
      • Re: VECTOR data types and intrinsic functions, Tim Prince
      • Re: VECTOR data types and intrinsic functions, robin
      • Re: VECTOR data types and intrinsic functions, Tim Prince
  • Re: VECTOR data types and intrinsic functions, Greg Lindahl
  • Re: VECTOR data types and intrinsic functions, robin
    • Re: VECTOR data types and intrinsic functions, Steven G. Kargl
• Allocatable arrays and shared libraries: help needed, sgiannerini
  • Re: Allocatable arrays and shared libraries: help needed, Tobias Burnus
    • Re: Allocatable arrays and shared libraries: help needed, fj
      • Re: Allocatable arrays and shared libraries: help needed, sgiannerini
      • Re: Allocatable arrays and shared libraries: help needed, James Van Buskirk
      • Re: Allocatable arrays and shared libraries: help needed, Janne Blomqvist
• Conditional Variable Type Declarations, Infinity77
  • Re: Conditional Variable Type Declarations, David Frank
  • Re: Conditional Variable Type Declarations, Craig Dedo
  • Re: Conditional Variable Type Declarations, Reinhold Bader
    • Re: Conditional Variable Type Declarations, fj
      • Re: Conditional Variable Type Declarations, fj
  • Re: Conditional Variable Type Declarations, Colin Watters
    • Re: Conditional Variable Type Declarations, Infinity77
• what's wrong with "make check-fortran"'s result of gfortran 20071130?, linuxl4
  • Re: what's wrong with "make check-fortran"'s result of gfortran 20071130?, Tobias Burnus
• Re: Challenge: reading ascii data, robin
  • <Possible follow-ups>
  • Re: Challenge: reading ascii data, robin
• Can somebody Help me??, DooZer
  • Re: Can somebody Help me??, Jan Gerrit Kootstra
    • Re: Can somebody Help me??, DooZer
      • Re: Can somebody Help me??, Jan Gerrit Kootstra
      • Re: Can somebody Help me??, Jan Gerrit Kootstra
      • Re: Can somebody Help me??, dpb
      • Re: Can somebody Help me??, David Frank
      • Re: Can somebody Help me??, James Van Buskirk
      • Re: Can somebody Help me??, Jan Gerrit Kootstra
      • Re: Can somebody Help me??, dpb
      • Re: Can somebody Help me??, Jan Gerrit Kootstra
      • Re: Can somebody Help me??, dpb
      • Re: Can somebody Help me??, John Harper
      • Re: Can somebody Help me??, Richard Maine
      • Re: Can somebody Help me??, Jan Gerrit Kootstra
      • Re: Can somebody Help me??, dpb
      • Re: Can somebody Help me??, Steven G. Kargl
      • Re: Can somebody Help me??, DooZer
      • Re: Can somebody Help me??, Jan Gerrit Kootstra
      • Re: Can somebody Help me??, Michael Metcalf
      • Re: Can somebody Help me??, Tobias Burnus
      • Re: Can somebody Help me??, Terence
      • Re: Can somebody Help me??, john . collins
  • Re: Can somebody Help me??, tianyf@xxxxxxxxx
    • Re: Can somebody Help me??, user1
    • Re: Can somebody Help me??, DooZer
      • Re: Can somebody Help me??, dpb
      • Re: Can somebody Help me??, Jan Gerrit Kootstra
      • Re: Can somebody Help me??, Jan Gerrit Kootstra
      • Re: Can somebody Help me??, DooZer
  • Re: Can somebody Help me??, Craig Dedo
• Kind of new to cray pointers, James Van Buskirk
  • Re: Kind of new to cray pointers, Steve Lionel
    • Re: Kind of new to cray pointers, James Van Buskirk
      • Re: Kind of new to cray pointers, Richard Maine
      • Re: Kind of new to cray pointers, James Van Buskirk
      • Re: Kind of new to cray pointers, Richard Maine
      • Re: Kind of new to cray pointers, James Van Buskirk
      • Re: Kind of new to cray pointers, Richard Maine
• Formatted stream I/O, Thomas Koenig
  • Re: Formatted stream I/O, Gary Scott
    • Re: Formatted stream I/O, Terence
    • Re: Formatted stream I/O, Craig Dedo
      • Re: Formatted stream I/O, Thomas Koenig
      • Re: Formatted stream I/O, fj
      • Re: Formatted stream I/O, Steve Lionel
• Some question to 'sequence' and deallocating arrays, klohmuschel
  • Re: Some question to 'sequence' and deallocating arrays, Richard Maine
    • Re: Some question to 'sequence' and deallocating arrays, Gary Scott
      • Re: Some question to 'sequence' and deallocating arrays, Ron Shepard
      • Re: Some question to 'sequence' and deallocating arrays, Richard Maine
      • Re: Some question to 'sequence' and deallocating arrays, Chip Coldwell
      • Re: Some question to 'sequence' and deallocating arrays, Richard Maine
      • Re: Some question to 'sequence' and deallocating arrays, FX
      • Re: Some question to 'sequence' and deallocating arrays, Chip Coldwell
      • Re: Some question to 'sequence' and deallocating arrays, glen herrmannsfeldt
      • Re: Some question to 'sequence' and deallocating arrays, Chip Coldwell
      • Re: Some question to 'sequence' and deallocating arrays, glen herrmannsfeldt
      • Re: Some question to 'sequence' and deallocating arrays, Charles Coldwell
      • Re: Some question to 'sequence' and deallocating arrays, glen herrmannsfeldt
      • Re: Some question to 'sequence' and deallocating arrays, glen herrmannsfeldt
      • Re: Some question to 'sequence' and deallocating arrays, klohmuschel
      • Re: Some question to 'sequence' and deallocating arrays, Richard Maine
      • Re: Some question to 'sequence' and deallocating arrays, garylscott
      • Re: Some question to 'sequence' and deallocating arrays, Richard Maine
      • Re: Some question to 'sequence' and deallocating arrays, Paul van Delst
      • Re: Some question to 'sequence' and deallocating arrays, Dick Hendrickson
  • Re: Some question to 'sequence' and deallocating arrays, Michael Metcalf
    • Re: Some question to 'sequence' and deallocating arrays, Richard Maine
• Re: gfortran diagnostics and so on, FX Coudert
  • New gfortran Windows builds, James Van Buskirk
    • Re: New gfortran Windows builds, stepanko
      • Re: New gfortran Windows builds, FX
      • Re: New gfortran Windows builds, Doug
      • Re: New gfortran Windows builds, stepanko
• Re: Read DOS or Unix files with the same fortran code, feenberg
• Can someone explain this to me? function func(a, i, j, a) bind(c), James Tursa
  • Re: Can someone explain this to me? function func(a, i, j, a) bind(c), Richard Maine
  • Re: Can someone explain this to me? function func(a, i, j, a) bind(c), Dan Nagle
    • Re: Can someone explain this to me? function func(a, i, j, a) bind(c), James Tursa
  • Re: Can someone explain this to me? function func(a, i, j, a) bind(c), Michael Metcalf
• when substring equals string, tholen
  • Re: when substring equals string, fj
    • Re: when substring equals string, James Van Buskirk
      • Re: when substring equals string, fj
      • Re: when substring equals string, robin
      • Re: when substring equals string, tholen
      • Re: when substring equals string, robin
      • Re: when substring equals string, tholen
    • Re: when substring equals string, tholen
  • Re: when substring equals string, rjkematick@xxxxxxxxxxx
    • Re: when substring equals string, tholen
• Re: Fortran Error Reporting Requirements, Dan Nagle
  • Re: Fortran Error Reporting Requirements, Greg Lindahl
    • Re: Fortran Error Reporting Requirements, Dan Nagle
      • Re: Fortran Error Reporting Requirements, Greg Lindahl
    • Re: Fortran Error Reporting Requirements, Gordon Sande
      • Re: Fortran Error Reporting Requirements, Craig Dedo
      • Re: Fortran Error Reporting Requirements, Paul van Delst
    • Re: Fortran Error Reporting Requirements, Craig Dedo
      • Re: Fortran Error Reporting Requirements, Greg Lindahl
      • Re: Fortran Error Reporting Requirements, Gordon Sande
      • Re: Fortran Error Reporting Requirements, Craig Powers
      • Re: Fortran Error Reporting Requirements, Steven Correll
      • Re: Fortran Error Reporting Requirements, Greg Lindahl
    • Re: Fortran Error Reporting Requirements, Paul van Delst
  • Re: Fortran Error Reporting Requirements, glen herrmannsfeldt
    • Re: Fortran Error Reporting Requirements, Craig Dedo
  • <Possible follow-ups>
  • Re: Fortran Error Reporting Requirements, Greg Lindahl
• RE: metacommand $debug, meek

• Security
• UNIX
• Linux
• Coding
• Usenet

• Archive
• About
• Privacy
• Search
• Imprint

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