comp.lang.fortran

• Date Index

---

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

• Security
• UNIX
• Linux
• Coding
• Usenet

• Archive
• About
• Privacy
• Search
• Imprint

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