comp.lang.fortran

• Date Index

---

• list of currently ALLOCATED variables, davidgkinniburgh
• How to compile Mopac 7.1 using g77 or gfortran, Jinsong.Zhao@xxxxxxxxx
  • Re: How to compile Mopac 7.1 using g77 or gfortran, Richard Maine
    • Re: How to compile Mopac 7.1 using g77 or gfortran, Jinsong.Zhao@xxxxxxxxx
      • Re: How to compile Mopac 7.1 using g77 or gfortran, Dr Ivan D. Reid
      • Re: How to compile Mopac 7.1 using g77 or gfortran, glen herrmannsfeldt
      • Re: How to compile Mopac 7.1 using g77 or gfortran, Dr Ivan D. Reid
      • Re: How to compile Mopac 7.1 using g77 or gfortran, dpb
      • Re: How to compile Mopac 7.1 using g77 or gfortran, Dick Hendrickson
      • Re: How to compile Mopac 7.1 using g77 or gfortran, dpb
  • Re: How to compile Mopac 7.1 using g77 or gfortran, Sebastian Gallinat
• Fortran Courses in Shrivenham, Swindon UK, Shaun
• MPI beginner, Rick
  • Re: MPI beginner, Arjen Markus
    • Re: MPI beginner, Damian
  • Re: MPI beginner, Herman D . Knoble
  • Re: MPI beginner, Craig Powers
  • Re: MPI beginner, glen herrmannsfeldt
    • Re: MPI beginner, Damian
      • Re: MPI beginner, glen herrmannsfeldt
      • Re: MPI beginner, Herman D . Knoble
• loss of precision, rudra
  • Re: loss of precision, Steven G. Kargl
  • Re: loss of precision, dominiq
  • Re: loss of precision, Richard Maine
    • Re: loss of precision, glen herrmannsfeldt
      • Re: loss of precision, Gary Scott
      • Re: loss of precision, glen herrmannsfeldt
      • Re: loss of precision, rudra
      • Re: loss of precision, Richard Maine
      • Re: loss of precision, dpb
      • Re: loss of precision, James Van Buskirk
  • Re: loss of precision, glen herrmannsfeldt
  • Re: loss of precision, Herman D . Knoble
• OT: Help - Fortranlib.com, Gary Scott
  • Re: OT: Help - Fortranlib.com, JB
    • Re: OT: Help - Fortranlib.com, Gary Scott
      • Re: OT: Help - Fortranlib.com, JB
• allocatable non-dummy local variables and pointers to them, randomaccessiterator
  • Re: allocatable non-dummy local variables and pointers to them, randomaccessiterator
  • Re: allocatable non-dummy local variables and pointers to them, dpb
    • Re: allocatable non-dummy local variables and pointers to them, randomaccessiterator
      • Re: allocatable non-dummy local variables and pointers to them, dpb
      • Re: allocatable non-dummy local variables and pointers to them, dpb
      • Re: allocatable non-dummy local variables and pointers to them, Richard Maine
      • Re: allocatable non-dummy local variables and pointers to them, dpb
      • Re: allocatable non-dummy local variables and pointers to them, Richard Maine
      • Re: allocatable non-dummy local variables and pointers to them, dpb
  • Re: allocatable non-dummy local variables and pointers to them, JB
  • Re: allocatable non-dummy local variables and pointers to them, Richard Maine
    • Re: allocatable non-dummy local variables and pointers to them, e p chandler
      • Re: allocatable non-dummy local variables and pointers to them, Richard Maine
      • Re: allocatable non-dummy local variables and pointers to them, e p chandler
      • Re: allocatable non-dummy local variables and pointers to them, Gary Scott
      • Re: allocatable non-dummy local variables and pointers to them, Richard Maine
      • Re: allocatable non-dummy local variables and pointers to them, e p chandler
      • Re: allocatable non-dummy local variables and pointers to them, Gary Scott
      • Re: allocatable non-dummy local variables and pointers to them, dpb
      • Re: allocatable non-dummy local variables and pointers to them, e p chandler
      • Re: allocatable non-dummy local variables and pointers to them, Steve Lionel
    • Re: allocatable non-dummy local variables and pointers to them, Damian
      • Re: allocatable non-dummy local variables and pointers to them, Richard Maine
• A specification expression error!?, deadpickle
  • Re: A specification expression error!?, Richard Maine
• warnings for lapack routines, Ron Ford
  • Re: warnings for lapack routines, Ian Bush
    • Re: warnings for lapack routines, user1
      • Re: warnings for lapack routines, Ian Bush
      • Re: warnings for lapack routines, dpb
      • Re: warnings for lapack routines, user1
• Segmentation Fault using cron, Marcelo Almeida de Amorim
  • Re: Segmentation Fault using cron, Craig Powers
• Cost of Large Modules Compared to Many Small Modules, brady . m . adams
  • Re: Cost of Large Modules Compared to Many Small Modules, Richard Maine
    • Re: Cost of Large Modules Compared to Many Small Modules, Makis
      • Re: Cost of Large Modules Compared to Many Small Modules, Jan Vorbrüggen
    • Re: Cost of Large Modules Compared to Many Small Modules, Carlie J. Coats
      • Re: Cost of Large Modules Compared to Many Small Modules, Damian
  • Re: Cost of Large Modules Compared to Many Small Modules, Jan Vorbrüggen
• simple graphics for fortran on windows, peter . king
  • Re: simple graphics for fortran on windows, Herman D . Knoble
    • Re: simple graphics for fortran on windows, peter . king
      • Re: simple graphics for fortran on windows, Herman D . Knoble
  • Re: simple graphics for fortran on windows, Michael Prager
  • Re: simple graphics for fortran on windows, Luka Djigas
  • Re: simple graphics for fortran on windows, e p chandler
  • Re: simple graphics for fortran on windows, Michael Prager
    • Re: simple graphics for fortran on windows, Michael Prager
    • Re: simple graphics for fortran on windows, michels
      • Re: simple graphics for fortran on windows, Michael Prager
  • Re: simple graphics for fortran on windows, David Duffy
• det yesnack, Ron Ford
  • Re: det yesnack, Kurt Kallblad
    • Re: det yesnack, Ron Ford
• Re: [lenny] splashy et lilo.conf..., Ron Ford
• Error Condition Testing, Dan
  • Re: Error Condition Testing, Dan Nagle
  • Re: Error Condition Testing, Richard Maine
• Avoiding nested IF conditionals,and STOP statement, s_siouris
  • Re: Avoiding nested IF conditionals,and STOP statement, dpb
  • Re: Avoiding nested IF conditionals,and STOP statement, e p chandler
  • Re: Avoiding nested IF conditionals,and STOP statement, glen herrmannsfeldt
  • Re: Avoiding nested IF conditionals,and STOP statement, Kurt Kallblad
• Alternative to the STOP statement?, s_siouris
  • Re: Alternative to the STOP statement?, Richard Maine
    • Re: Alternative to the STOP statement?, Phillip Helbig---remove CLOTHES to reply
      • Re: Alternative to the STOP statement?, Richard Maine
      • Re: Alternative to the STOP statement?, Dr Ivan D. Reid
      • Re: Alternative to the STOP statement?, Dick Hendrickson
  • Re: Alternative to the STOP statement?, Paul van Delst
    • Re: Alternative to the STOP statement?, s_siouris
      • Re: Alternative to the STOP statement?, Jugoslav Dujic
      • Re: Alternative to the STOP statement?, Paul van Delst
      • Re: Alternative to the STOP statement?, GaryScott
      • Re: Alternative to the STOP statement?, Jan Vorbrüggen
      • Re: Alternative to the STOP statement?, Arjen Markus
      • Re: Alternative to the STOP statement?, glen herrmannsfeldt
      • Re: Alternative to the STOP statement?, Richard Maine
      • Re: Alternative to the STOP statement?, Walter Spector
      • Re: Alternative to the STOP statement?, Damian
      • Re: Alternative to the STOP statement?, Daniel Kraft
      • Re: Alternative to the STOP statement?, Damian
      • Re: Alternative to the STOP statement?, Walter Spector
      • Re: Alternative to the STOP statement?, Richard Maine
      • Re: Alternative to the STOP statement?, Daniel Kraft
      • Re: Alternative to the STOP statement?, glen herrmannsfeldt
      • Re: Alternative to the STOP statement?, Walter Spector
      • Re: Alternative to the STOP statement?, glen herrmannsfeldt
      • Re: Alternative to the STOP statement?, Gary Scott
      • Re: Alternative to the STOP statement?, Walter Spector
      • Re: Alternative to the STOP statement?, Gary Scott
      • Re: Alternative to the STOP statement?, JB
      • Re: Alternative to the STOP statement?, Phillip Helbig---remove CLOTHES to reply
    • Re: Alternative to the STOP statement?, Arjen Markus
      • Re: Alternative to the STOP statement?, Damian
      • Re: Alternative to the STOP statement?, Richard Maine
      • Re: Alternative to the STOP statement?, Phillip Helbig---remove CLOTHES to reply
      • Re: Alternative to the STOP statement?, Damian
  • Re: Alternative to the STOP statement?, David Simpson
    • Re: Alternative to the STOP statement?, Kurt Kallblad
      • Re: Alternative to the STOP statement?, David Simpson
• Friendfeed room "fortran coding", mcastel
• dimensions and segmentation fault problem, mcastel
  • Re: dimensions and segmentation fault problem, Arjen Markus
  • Re: dimensions and segmentation fault problem, Dr Ivan D. Reid
  • Re: dimensions and segmentation fault problem, rudra
    • Re: dimensions and segmentation fault problem, mcastel
• rounding mode, Bart Vandewoestyne
  • Re: rounding mode, Colin Paul Gloster
  • Re: rounding mode, Arjen Markus
  • Re: rounding mode, Tim Prince
    • IEEE 754r published (Was: Re: rounding mode), JB
    • Re: rounding mode, glen herrmannsfeldt
• segmentation fault, rudra
  • Re: segmentation fault, Steve Lionel
    • Re: segmentation fault, rudra
      • Re: segmentation fault, Richard Maine
      • Re: segmentation fault, rudra
      • Re: segmentation fault, Richard Maine
      • Re: segmentation fault, Richard Maine
      • Re: segmentation fault, rudra
      • Re: segmentation fault, Richard Maine
      • Re: segmentation fault, rudra
      • Re: segmentation fault, David Duffy
      • Re: segmentation fault, rudra
      • Re: segmentation fault, dpb
      • Re: segmentation fault, dpb
      • Re: segmentation fault, rudra
• Write statement in subroutine affecting output of return values, charlie818
  • Re: Write statement in subroutine affecting output of return values, Arjen Markus
    • Re: Write statement in subroutine affecting output of return values, charlie818
      • Re: Write statement in subroutine affecting output of return values, Catherine Rees Lay
      • Re: Write statement in subroutine affecting output of return values, Arjen Markus
      • Re: Write statement in subroutine affecting output of return values, e p chandler
• Efficient way of finding most-significant non-zero bit of integer, Rich Townsend
  • Re: Efficient way of finding most-significant non-zero bit of integer, James Van Buskirk
    • Re: Efficient way of finding most-significant non-zero bit of integer, Rich Townsend
      • Re: Efficient way of finding most-significant non-zero bit of integer, Craig Powers
  • Message not available
    • Re: Efficient way of finding most-significant non-zero bit of integer, Tim Prince
      • Re: Efficient way of finding most-significant non-zero bit of integer, ttw6687
  • Re: Efficient way of finding most-significant non-zero bit of integer, Terence
• Compilation order (USE assocs), Antoon
  • Re: Compilation order (USE assocs), JayBee
  • Re: Compilation order (USE assocs), Jugoslav Dujic
    • Re: Compilation order (USE assocs), Antoon
      • Re: Compilation order (USE assocs), Kurt Kallblad
      • Re: Compilation order (USE assocs), Jugoslav Dujic
      • Re: Compilation order (USE assocs), Arjan
      • Re: Compilation order (USE assocs), Catherine Rees Lay
      • Re: Compilation order (USE assocs), Antoon
      • Re: Compilation order (USE assocs), Jugoslav Dujic
• Scope of implicit none, Arjen Markus
  • Re: Scope of implicit none, Richard Maine
    • Re: Scope of implicit none, Arjen Markus
      • Re: Scope of implicit none, Reinhold Bader
      • Re: Scope of implicit none, paul . richard . thomas
      • Re: Scope of implicit none, Arjen Markus
  • Re: Scope of implicit none, Cirilo S. Bresolin
    • Re: Scope of implicit none, Richard Maine
      • Re: Scope of implicit none, Arjen Markus
      • Re: Scope of implicit none, GaryScott
      • Re: Scope of implicit none, Arjen Markus
      • Re: Scope of implicit none, Richard Maine
      • Re: Scope of implicit none, Steven Correll
      • Re: Scope of implicit none, Richard Maine
      • Re: Scope of implicit none, Ron Shepard
      • Re: Scope of implicit none, Richard Maine
      • Re: Scope of implicit none, Ron Shepard
      • Re: Scope of implicit none, glen herrmannsfeldt
      • Re: Scope of implicit none, Richard Maine
      • Re: Scope of implicit none, glen herrmannsfeldt
      • Re: Scope of implicit none, Richard Maine
      • Re: Scope of implicit none, Ron Shepard
      • Re: Scope of implicit none, Richard Maine
      • Re: Scope of implicit none, Ron Shepard
      • Re: Scope of implicit none, Richard Maine
      • Re: Scope of implicit none, Phillip Helbig---remove CLOTHES to reply
      • Re: Scope of implicit none, Gary Scott
      • Re: Scope of implicit none, Arjen Markus
      • Re: Scope of implicit none, GaryScott
      • Re: Scope of implicit none, Phillip Helbig---remove CLOTHES to reply
      • Re: Scope of implicit none, Richard Maine
      • Re: Scope of implicit none, Phillip Helbig---remove CLOTHES to reply
      • Re: Scope of implicit none, Gary Scott
      • Re: Scope of implicit none, Gary Scott
      • Re: Scope of implicit none, dpb
      • Re: Scope of implicit none, Gary Scott
• BLOCK WAS VECTORIZED., Fatemeh
  • Re: BLOCK WAS VECTORIZED., Steve Lionel
    • Re: BLOCK WAS VECTORIZED., glen herrmannsfeldt
      • Re: BLOCK WAS VECTORIZED., Steve Lionel
• Passing module procedures to external procedures -- type issues, Rich Townsend
  • Re: Passing module procedures to external procedures -- type issues, robert . corbett
    • Re: Passing module procedures to external procedures -- type issues, robert . corbett
    • Re: Passing module procedures to external procedures -- type issues, robert . corbett
    • Re: Passing module procedures to external procedures -- type issues, Richard Maine
      • Re: Passing module procedures to external procedures -- type issues, paul . richard . thomas
      • Re: Passing module procedures to external procedures -- type issues, stevenb . gcc
      • Re: Passing module procedures to external procedures -- type issues, Rich Townsend
      • Re: Passing module procedures to external procedures -- type issues, Rich Townsend
      • Re: Passing module procedures to external procedures -- type issues, Richard Maine
      • Re: Passing module procedures to external procedures -- type issues, glen herrmannsfeldt
      • Re: Passing module procedures to external procedures -- type issues, Richard Maine
      • Re: Passing module procedures to external procedures -- type issues, glen herrmannsfeldt
      • Re: Passing module procedures to external procedures -- type issues, Richard Maine
      • Re: Passing module procedures to external procedures -- type issues, Rich Townsend
      • Re: Passing module procedures to external procedures -- type issues, robert . corbett
  • Re: Passing module procedures to external procedures -- type issues, glen herrmannsfeldt
  • Re: Passing module procedures to external procedures -- type issues, glen herrmannsfeldt
• "Final" Procedures, Gary Scott
  • Re: "Final" Procedures, Richard Maine
  • Re: "Final" Procedures, e p chandler
    • Re: "Final" Procedures, Gary Scott
      • Re: "Final" Procedures, Terence
      • Re: "Final" Procedures, Gary Scott
      • Re: "Final" Procedures, Terence
      • Re: "Final" Procedures, Gary Scott
• PASSING ARRAY FORTRAN DLL TO/FROM VBA EXCEL, kis
  • Re: PASSING ARRAY FORTRAN DLL TO/FROM VBA EXCEL, e p chandler
    • Re: PASSING ARRAY FORTRAN DLL TO/FROM VBA EXCEL, kis
      • Re: PASSING ARRAY FORTRAN DLL TO/FROM VBA EXCEL, dpb
      • Re: PASSING ARRAY FORTRAN DLL TO/FROM VBA EXCEL, kis
• DATA statement to initialise arrays, bru
  • Re: DATA statement to initialise arrays, Arjen Markus
    • Re: DATA statement to initialise arrays, bru
  • Re: DATA statement to initialise arrays, dpb
    • Re: DATA statement to initialise arrays, Richard Maine
      • Re: DATA statement to initialise arrays, dpb
      • Re: DATA statement to initialise arrays, glen herrmannsfeldt
  • Re: DATA statement to initialise arrays, Kurt Kallblad
    • Re: DATA statement to initialise arrays, bru
• using a lapack routine, Ron Ford
  • Re: using a lapack routine, e p chandler
    • Re: using a lapack routine, Ron Ford
    • Re: using a lapack routine, Ron Ford
      • Re: using a lapack routine, michael . caracotsios
      • Re: using a lapack routine, e p chandler
      • Re: using a lapack routine, Ron Ford
      • Re: using a lapack routine, user1
      • Re: using a lapack routine, Ron Ford
  • Re: using a lapack routine, JayBee
  • Re: using a lapack routine, teg
• Combining Lua and Fortran, nobat
  • Re: Combining Lua and Fortran, David Duffy
    • Re: Combining Lua and Fortran, nobat
• Praise for Gfortran (finally), Al Greynolds
  • Re: Praise for Gfortran (finally), Damian
    • Re: Praise for Gfortran (finally), paul . richard . thomas
      • Re: Praise for Gfortran (finally), Arjen Markus
      • Re: Praise for Gfortran (finally), Tobias Burnus
      • Re: Praise for Gfortran (finally), paul . richard . thomas
      • Re: Praise for Gfortran (finally), Arjen Markus
      • Re: Praise for Gfortran (finally), tholen@xxxxxxxxxxxx
      • Re: Praise for Gfortran (finally), Tobias Burnus
      • Re: Praise for Gfortran (finally), Phillip Helbig---remove CLOTHES to reply
      • Re: Praise for Gfortran (finally), Richard Maine
      • Re: Praise for Gfortran (finally), Phillip Helbig---remove CLOTHES to reply
      • Re: Praise for Gfortran (finally), Richard Maine
      • Re: Praise for Gfortran (finally), Gary Scott
      • Re: Praise for Gfortran (finally), Richard Maine
      • Re: Praise for Gfortran (finally), Gary Scott
      • Re: Praise for Gfortran (finally), Colin Paul Gloster
      • Re: Praise for Gfortran (finally), Gary Scott
      • Re: Praise for Gfortran (finally), Colin Paul Gloster
      • Re: Praise for Gfortran (finally), Gary Scott
      • Re: Praise for Gfortran (finally), James Van Buskirk
      • Re: Praise for Gfortran (finally), glen herrmannsfeldt
      • Re: Praise for Gfortran (finally), Steve Lionel
      • Re: Praise for Gfortran (finally), steven . bosscher
      • Re: Praise for Gfortran (finally), glen herrmannsfeldt
      • Re: Praise for Gfortran (finally), Richard Maine
      • Re: Praise for Gfortran (finally), steven . bosscher
      • Re: Praise for Gfortran (finally), Damian
      • Re: Praise for Gfortran (finally), Steven G. Kargl
      • Re: Praise for Gfortran (finally), Damian
      • Re: Praise for Gfortran (finally), Arjen Markus
      • Re: Praise for Gfortran (finally), Beliavsky
      • Re: Praise for Gfortran (finally), Tobias Burnus
      • Re: Praise for Gfortran (finally), Colin Paul Gloster
      • Re: Praise for Gfortran (finally), Tobias Burnus
      • Re: Praise for Gfortran (finally), Colin Paul Gloster
  • Not! Praise for Gfortran, Carlie J. Coats
    • Re: Not! Praise for Gfortran, Arjen Markus
      • Re: Not! Praise for Gfortran, Carlie J. Coats
      • Re: Not! Praise for Gfortran, Arjen Markus
      • .NOT. (Re: Not! Praise for Gfortran) :o), Paul van Delst
      • Re: .NOT. (Re: Not! Praise for Gfortran) :o), Ron Ford
      • Re: .NOT. (Re: Not! Praise for Gfortran) :o), Terence
      • Re: .NOT. (Re: Not! Praise for Gfortran) :o), Ron Ford
      • Re: Not! Praise for Gfortran, JayBee
      • Re: Not! Praise for Gfortran, Arjen Markus
      • Re: Not! Praise for Gfortran, fj
      • Re: Not! Praise for Gfortran, Gary Scott
      • Re: Not! Praise for Gfortran, steven . bosscher
      • Re: Not! Praise for Gfortran, Steven G. Kargl
      • Re: Not! Praise for Gfortran, Steven G. Kargl
      • Re: Not! Praise for Gfortran, Tobias Burnus
      • Re: Not! Praise for Gfortran, Carlie J. Coats
      • Re: Not! Praise for Gfortran, Steven G. Kargl
      • Re: Not! Praise for Gfortran, Steven G. Kargl
    • Re: Not! Praise for Gfortran, steven . bosscher
• Problem with array dereferencing during using gdb with gfortran code, beppo_anmeldung
  • Re: Problem with array dereferencing during using gdb with gfortran code, steven . bosscher
    • Re: Problem with array dereferencing during using gdb with gfortran code, Tobias Burnus
• OT: Determining the size of plotting area, Robert Singer
  • Re: OT: Determining the size of plotting area, Richard Maine
  • Re: OT: Determining the size of plotting area, dpb
    • Re: OT: Determining the size of plotting area, Robert Singer
  • Re: OT: Determining the size of plotting area, glen herrmannsfeldt
    • Re: OT: Determining the size of plotting area, James Parsly
  • Re: OT: Determining the size of plotting area, Kevin G. Rhoads
    • Re: OT: Determining the size of plotting area, GaryScott
      • Re: OT: Determining the size of plotting area, dpb
      • Re: OT: Determining the size of plotting area, Robert Singer
      • Re: OT: Determining the size of plotting area, dpb
      • Re: OT: Determining the size of plotting area, Kevin G. Rhoads
      • Re: OT: Determining the size of plotting area, GaryScott
  • Re: OT: Determining the size of plotting area, David Duffy
• random ints on symmetric interval, Ron Ford
  • Re: random ints on symmetric interval, e p chandler
    • Re: random ints on symmetric interval, Ron Ford
      • Re: random ints on symmetric interval, glen herrmannsfeldt
      • Re: random ints on symmetric interval, Ron Ford
      • Re: random ints on symmetric interval, glen herrmannsfeldt
      • Re: random ints on symmetric interval, Ron Ford
      • Re: random ints on symmetric interval, glen herrmannsfeldt
      • Re: random ints on symmetric interval, Ron Ford
      • Re: random ints on symmetric interval, glen herrmannsfeldt
    • Re: random ints on symmetric interval, Ron Ford
      • Re: random ints on symmetric interval, e p chandler
      • Re: random ints on symmetric interval, Ron Ford
      • Re: random ints on symmetric interval, e p chandler
      • Re: random ints on a large symmetric interval, Ron Ford
      • Re: random ints on a large symmetric interval, e p chandler
      • Re: random ints on a large symmetric interval, Ron Ford
      • Re: random ints on a large symmetric interval, Ron Ford
• traverse linked list (Fortran 90), e p chandler
  • Re: traverse linked list (Fortran 90), Ron Ford
    • Re: traverse linked list (Fortran 90), glen herrmannsfeldt
      • Re: traverse linked list (Fortran 90), Gary Scott
  • Re: traverse linked list (Fortran 90), Kurt Kallblad
  • Re: traverse linked list (Fortran 90), Ron Ford
    • Re: traverse linked list (Fortran 90), e p chandler
      • Re: traverse linked list (Fortran 90), Ron Ford
• pointer components and memory leaks, mrestelli@xxxxxxxxx
  • Re: pointer components and memory leaks, Richard Maine
    • Re: pointer components and memory leaks, Paul van Delst
      • Re: pointer components and memory leaks, Richard Maine
      • Re: pointer components and memory leaks, mrestelli@xxxxxxxxx
      • Re: pointer components and memory leaks, Damian
      • Re: pointer components and memory leaks, Damian
      • Re: pointer components and memory leaks, rusi_pathan
      • Re: pointer components and memory leaks, Richard Maine
      • Re: pointer components and memory leaks, Paul van Delst
      • Re: pointer components and memory leaks, Richard Maine
      • Re: pointer components and memory leaks, James Van Buskirk
      • Re: pointer components and memory leaks, Richard Maine
      • Re: pointer components and memory leaks, rusi_pathan
  • Re: pointer components and memory leaks, Arjen Markus
• Reading external variables from a library (BIND), Raúl
  • Re: Reading external variables from a library (BIND), Arjen Markus
    • Re: Reading external variables from a library (BIND), glen herrmannsfeldt
      • Re: Reading external variables from a library (BIND), Arjen Markus
      • Re: Reading external variables from a library (BIND), Arjen Markus
      • Re: Reading external variables from a library (BIND), glen herrmannsfeldt
      • Re: Reading external variables from a library (BIND), Richard Maine
      • Re: Reading external variables from a library (BIND), Gary Scott
      • Re: Reading external variables from a library (BIND), Ian Bush
      • Re: Reading external variables from a library (BIND), Raúl
      • Re: Reading external variables from a library (BIND), glen herrmannsfeldt
  • Re: Reading external variables from a library (BIND), glen herrmannsfeldt
    • Re: Reading external variables from a library (BIND), Steven G. Kargl
      • Re: Reading external variables from a library (BIND), glen herrmannsfeldt
      • Re: Reading external variables from a library (BIND), Steven G. Kargl
    • Re: Reading external variables from a library (BIND), Richard Maine
• Possible ambiguity with continuation lines and comments, Arjen Markus
  • Re: Possible ambiguity with continuation lines and comments, Steven G. Kargl
    • Re: Possible ambiguity with continuation lines and comments, Arjen Markus
• Passing an allocatable array to a subroutine, deadpickle
  • Re: Passing an allocatable array to a subroutine, fj
  • Re: Passing an allocatable array to a subroutine, Richard Maine
• cheap sale fendi and prada bags, ff
• gfortran compiler, daibid
  • Re: gfortran compiler, fj
• type-bound procedures and type extension, Damian
  • Re: type-bound procedures and type extension, Simulate
    • Re: type-bound procedures and type extension, Simulate
    • Re: type-bound procedures and type extension, Gary Scott
    • Re: type-bound procedures and type extension, Steve Lionel
      • Re: type-bound procedures and type extension, Richard Maine
      • Re: type-bound procedures and type extension, Simulate
• calculation of bessel functions j_l(x), Fatemeh
  • Re: calculation of bessel functions j_l(x), ralf.schaa
    • Re: calculation of bessel functions j_l(x), Fatemeh
      • Re: calculation of bessel functions j_l(x), Fatemeh
      • Re: calculation of bessel functions j_l(x), Fatemeh
      • Re: calculation of bessel functions j_l(x), Fatemeh
      • Re: calculation of bessel functions j_l(x), Dan Nagle
• LAPACK95, Ron Ford
  • Re: LAPACK95, Tim Prince
    • Re: LAPACK95, Ron Ford
      • Re: LAPACK95, user1
      • Re: LAPACK95, Ian
  • Re: LAPACK95, Steven G. Kargl
    • Re: LAPACK95, Ron Ford
      • Re: LAPACK95, Steven G. Kargl
      • Re: LAPACK95, Ron Ford
      • Re: LAPACK95, Richard Maine
      • Re: LAPACK95, Harold Stevens
      • Re: LAPACK95, Ron Ford
      • Re: LAPACK95, glen herrmannsfeldt
      • Re: LAPACK95, Steven G. Kargl
      • Re: LAPACK95, glen herrmannsfeldt
  • Re: LAPACK95, none
    • Re: LAPACK95, Ron Ford
      • Re: LAPACK95, Ian
• EigenValues and EigenVectors with LAPACK, michael . caracotsios
  • Re: EigenValues and EigenVectors with LAPACK, glen herrmannsfeldt
    • Re: EigenValues and EigenVectors with LAPACK, Tim Prince
      • Re: EigenValues and EigenVectors with LAPACK, glen herrmannsfeldt
      • Re: EigenValues and EigenVectors with LAPACK, Richard Maine
      • Re: EigenValues and EigenVectors with LAPACK, Ron Ford
      • Re: EigenValues and EigenVectors with LAPACK, glen herrmannsfeldt
      • Re: EigenValues and EigenVectors with LAPACK, Richard Maine
      • Re: EigenValues and EigenVectors with LAPACK, Steve Lionel
      • Re: EigenValues and EigenVectors with LAPACK, dpb
• unprotected_pointer => protected_pointer, Steven Correll
  • Re: unprotected_pointer => protected_pointer, Richard Maine
    • Re: unprotected_pointer => protected_pointer, Tobias Burnus
• where and non-conformable arrays, ralf.schaa
  • Re: where and non-conformable arrays, Arjen Markus
    • Re: where and non-conformable arrays, ralf.schaa
  • Re: where and non-conformable arrays, ralf.schaa
  • Re: where and non-conformable arrays, Yura
  • Re: where and non-conformable arrays, Richard Maine
  • Re: where and non-conformable arrays, Dan
    • Re: where and non-conformable arrays, michaelmetcalf
      • Re: where and non-conformable arrays, glen herrmannsfeldt
    • Re: where and non-conformable arrays, Kurt Kallblad
      • Re: where and non-conformable arrays, ralf.schaa
• F, Ron Ford
  • Re: F, Dan Nagle
    • Re: F, dpb
      • Re: F, Ron Ford
  • Re: F, Jan Vorbrüggen
• Source code beautifier for f90 and f77, Arjan
  • Re: Source code beautifier for f90 and f77, Ragu
    • Re: Source code beautifier for f90 and f77, Tim Prince
  • Re: Source code beautifier for f90 and f77, Dan Nagle
    • Re: Source code beautifier for f90 and f77, Arjan
  • Re: Source code beautifier for f90 and f77, Lynn McGuire
  • Re: Source code beautifier for f90 and f77, Luka Djigas
• Date representation, Marin Brkic
  • Re: Date representation, Arjen Markus
  • Re: Date representation, David Jones
    • Re: Date representation, Marin Brkic
      • Re: Date representation, michels
  • Re: Date representation, Gary Scott
    • Re: Date representation, Gary Scott
  • Re: Date representation, feenberg
  • Re: Date representation, Kurt Kallblad
    • Re: Date representation, Arjan
      • Re: Date representation, Marin Brkic
    • Re: Date representation, Marin Brkic
• Returning a dynamic character array based on input length, Ragu
  • Re: Returning a dynamic character array based on input length, Richard Maine
    • Re: Returning a dynamic character array based on input length, GaryScott
      • Re: Returning a dynamic character array based on input length, Richard Maine
    • Re: Returning a dynamic character array based on input length, Ragu
      • Re: Returning a dynamic character array based on input length, Richard Maine
      • Re: Returning a dynamic character array based on input length, George McBane
      • Re: Returning a dynamic character array based on input length, Gary Scott
      • Re: Returning a dynamic character array based on input length, Richard Maine
      • Re: Returning a dynamic character array based on input length, Gary Scott
      • Re: Returning a dynamic character array based on input length, George McBane
      • Re: Returning a dynamic character array based on input length, Richard Maine
      • Re: Returning a dynamic character array based on input length, George McBane
      • Re: Returning a dynamic character array based on input length, glen herrmannsfeldt
      • Re: Returning a dynamic character array based on input length, James Parsly
      • Re: Returning a dynamic character array based on input length, Sjouke Burry
  • Re: Returning a dynamic character array based on input length, Arjen Markus
    • Re: Returning a dynamic character array based on input length, Ragu
      • Re: Returning a dynamic character array based on input length, Ragu
      • Re: Returning a dynamic character array based on input length, Arjen Markus
• Robustness checkers for Fortran code., Toon Moene
  • Re: Robustness checkers for Fortran code., dpb
    • Re: Robustness checkers for Fortran code., dpb
• Fortran equivalent to Matlab's eig() function, Dave
  • Re: Fortran equivalent to Matlab's eig() function, Jörgen Tegnér
    • Re: Fortran equivalent to Matlab's eig() function, Dave
    • Re: Fortran equivalent to Matlab's eig() function, Gary Scott
      • Re: Fortran equivalent to Matlab's eig() function, Ron Ford
      • Re: Fortran equivalent to Matlab's eig() function, Gordon Sande
      • Re: Fortran equivalent to Matlab's eig() function, Ron Ford
      • Re: Fortran equivalent to Matlab's eig() function, Gordon Sande
      • Re: Fortran equivalent to Matlab's eig() function, Richard Maine
      • Re: Fortran equivalent to Matlab's eig() function, Ron Ford
      • Re: Fortran equivalent to Matlab's eig() function, dpb
      • Re: Fortran equivalent to Matlab's eig() function, Ron Ford
      • Re: Fortran equivalent to Matlab's eig() function, glen herrmannsfeldt
      • Re: Fortran equivalent to Matlab's eig() function, Gary Scott
      • Re: Fortran equivalent to Matlab's eig() function, dpb
  • Re: Fortran equivalent to Matlab's eig() function, paya
• Did NAG fortran complier support OPENMP?, Simulate
  • Re: Did NAG fortran complier support OPENMP?, Richard Maine
    • Re: Did NAG fortran complier support OPENMP?, Tobias Burnus
      • Re: Did NAG fortran complier support OPENMP?, Ron Ford
      • Re: Did NAG fortran complier support OPENMP?, Tobias Burnus
      • Re: Did NAG fortran complier support OPENMP?, Ron Ford
      • Re: Did NAG fortran complier support OPENMP?, Tobias Burnus
      • Re: Did NAG fortran complier support OPENMP?, Ron Ford
      • Re: Did NAG fortran complier support OPENMP?, Tobias Burnus
      • Re: Did NAG fortran complier support OPENMP?, Colin Paul Gloster
• some flags for optimization?? ( run with higher speed)??, Fatemeh
  • Re: some flags for optimization?? ( run with higher speed)??, Dr Ivan D. Reid
    • Re: some flags for optimization?? ( run with higher speed)??, Fatemeh
      • Re: some flags for optimization?? ( run with higher speed)??, Fatemeh
      • Re: some flags for optimization?? ( run with higher speed)??, michaelmetcalf
      • Re: some flags for optimization?? ( run with higher speed)??, Steve Lionel
      • Re: some flags for optimization?? ( run with higher speed)??, Dr Ivan D. Reid
  • Re: some flags for optimization?? ( run with higher speed)??, Steve Lionel
  • Re: some flags for optimization?? ( run with higher speed)??, Richard Maine
  • Re: some flags for optimization?? ( run with higher speed)??, Craig Powers
  • Re: some flags for optimization?? ( run with higher speed)??, Leclerc
  • Re: some flags for optimization?? ( run with higher speed)??, Ian Bush
• Re: [ANN] binary of gcc 4.3.2 for Windows is available for download, Gary Scott
  • Re: [ANN] binary of gcc 4.3.2 for Windows is available for download, Ron Ford
    • Re: [ANN] binary of gcc 4.3.2 for Windows is available for download, Gary Scott
• Re: Implementing JAVA interfaces in FORTRAN 20xx, David Thompson
  • Re: Implementing JAVA interfaces in FORTRAN 20xx, Gary Scott
    • Re: Implementing JAVA interfaces in FORTRAN 20xx, glen herrmannsfeldt
      • Re: Implementing JAVA interfaces in FORTRAN 20xx, Gary Scott
• Re: Surprise, David Thompson
  • Re: Surprise, glen herrmannsfeldt
    • Re: Surprise, David Thompson
    • Re: Surprise, Craig Powers
  • <Possible follow-ups>
  • Re: Surprise, Terence
• Auto-testing for memory leaks., Paul van Delst
  • Re: Auto-testing for memory leaks., rusi_pathan
    • Re: Auto-testing for memory leaks., rusi_pathan
  • Re: Auto-testing for memory leaks., George Trojan
  • Re: Auto-testing for memory leaks., Paul van Delst
  • Re: Auto-testing for memory leaks., JayBee
    • Re: Auto-testing for memory leaks., Gib Bogle
  • Re: Auto-testing for memory leaks., Jan Vorbrüggen
• Re: How to create a new folder in FORTRAN 77?, Catherine Rees Lay
  • Re: How to create a new folder in FORTRAN 77?, Gary Scott
  • <Possible follow-ups>
  • Re: How to create a new folder in FORTRAN 77?, Nathan Seese
    • Re: How to create a new folder in FORTRAN 77?, Gary Scott
      • Re: How to create a new folder in FORTRAN 77?, Richard Maine
      • Re: How to create a new folder in FORTRAN 77?, glen herrmannsfeldt
      • Re: How to create a new folder in FORTRAN 77?, Gary Scott
      • Re: How to create a new folder in FORTRAN 77?, Richard Maine
      • Re: How to create a new folder in FORTRAN 77?, Gary Scott
      • Re: How to create a new folder in FORTRAN 77?, Nathan Seese
• Re: Fortran vs. Matlab on linear algebra, tyler . thessin
• How to make a function work with different type and kind type argument, deltaquattro
  • Re: How to make a function work with different type and kind type argument, Paul van Delst
    • Re: How to make a function work with different type and kind type argument, deltaquattro
      • Re: How to make a function work with different type and kind type argument, Paul van Delst
      • Re: How to make a function work with different type and kind type argument, Craig Powers
      • Re: How to make a function work with different type and kind type argument, Ron Shepard
      • Re: How to make a function work with different type and kind type argument, Craig Powers
      • Re: How to make a function work with different type and kind type argument, James Van Buskirk
  • Re: How to make a function work with different type and kind type argument, Herman D . Knoble
• internal write rounds wrong, phantasmus
  • Re: internal write rounds wrong, Tim Prince
    • Re: internal write rounds wrong, glen herrmannsfeldt
  • Re: internal write rounds wrong, Kurt Kallblad
  • Re: internal write rounds wrong, Herman D . Knoble
    • Re: internal write rounds wrong, Michel Olagnon
      • Re: internal write rounds wrong, Herman D . Knoble
  • Re: internal write rounds wrong, Leslie Ballentine
    • Re: internal write rounds wrong, Richard Maine
    • Re: internal write rounds wrong, Kurt Kallblad
      • Re: internal write rounds wrong, Arjen Markus
      • Re: internal write rounds wrong, Kurt Kallblad
      • Re: internal write rounds wrong, Gary Scott
      • Re: internal write rounds wrong, glen herrmannsfeldt
• read binary file written in fortran from another language, utab
  • Re: read binary file written in fortran from another language, dpb
    • Message not available
      • Re: read binary file written in fortran from another language, AnotherSquid
  • Re: read binary file written in fortran from another language, e p chandler
• doxygen, rudra
  • Re: doxygen (Just a workaround, because the software is not meaned to run for fortran)., Jan Gerrit Kootstra
    • Re: doxygen (Just a workaround, because the software is not meaned to run for fortran)., rudra
• Parallel in Fortran90, Fatemeh
  • Re: Parallel in Fortran90, Arjen Markus
    • Re: Parallel in Fortran90, Damian
  • Re: Parallel in Fortran90, Dr Ivan D. Reid
  • Re: Parallel in Fortran90, Colin Paul Gloster
    • Re: Parallel in Fortran90, Fatemeh
      • Re: Parallel in Fortran90, Colin Paul Gloster
  • Re: Parallel in Fortran90, Gib Bogle
• Re: C++ wrapper for fortran functions, Gary Scott
  • <Possible follow-ups>
  • Re: C++ wrapper for fortran functions, Ron Ford
  • Re: C++ wrapper for fortran functions, Jugoslav Dujic
    • Re: C++ wrapper for fortran functions, utab
      • Re: C++ wrapper for fortran functions, Jugoslav Dujic
      • Re: C++ wrapper for fortran functions, utab
  • Re: C++ wrapper for fortran functions, JayBee
• Re: adapting a quicksort, glen herrmannsfeldt
  • <Possible follow-ups>
  • Re: adapting a quicksort, David Thompson
    • Re: adapting a quicksort, ttw6687
• Any suggested workarounds for writing wrappers for functions that are to be passed as arguments?, Will W.
  • Re: Any suggested workarounds for writing wrappers for functions that are to be passed as arguments?, Arjen Markus
    • Re: Any suggested workarounds for writing wrappers for functions that are to be passed as arguments?, Arjen Markus
      • Re: Any suggested workarounds for writing wrappers for functions that are to be passed as arguments?, Will W.
    • Re: Any suggested workarounds for writing wrappers for functions that are to be passed as arguments?, Steve Lionel
      • Re: Any suggested workarounds for writing wrappers for functions that are to be passed as arguments?, Dick Hendrickson
      • Re: Any suggested workarounds for writing wrappers for functions that are to be passed as arguments?, Richard Maine
      • Re: Any suggested workarounds for writing wrappers for functions that are to be passed as arguments?, glen herrmannsfeldt
      • Re: Any suggested workarounds for writing wrappers for functions that are to be passed as arguments?, Ron Ford
      • Re: Any suggested workarounds for writing wrappers for functions that are to be passed as arguments?, Richard Maine
      • Re: Any suggested workarounds for writing wrappers for functions that are to be passed as arguments?, Ron Ford
      • Re: Any suggested workarounds for writing wrappers for functions that are to be passed as arguments?, Gordon Sande
      • Re: Any suggested workarounds for writing wrappers for functions that are to be passed as arguments?, glen herrmannsfeldt
      • Re: Any suggested workarounds for writing wrappers for functions that are to be passed as arguments?, Arjen Markus
      • Message not available
      • Re: Any suggested workarounds for writing wrappers for functions that are to be passed as arguments?, glen herrmannsfeldt
      • Re: Any suggested workarounds for writing wrappers for functions that are to be passed as arguments?, Richard Maine
  • Re: Any suggested workarounds for writing wrappers for functions that are to be passed as arguments?, Steve Lionel
    • Re: Any suggested workarounds for writing wrappers for functions that are to be passed as arguments?, Will W.
  • Message not available
    • Re: Any suggested workarounds for writing wrappers for functions that are to be passed as arguments?, Will W.
      • Re: Any suggested workarounds for writing wrappers for functions that are to be passed as arguments?, Will W.
      • Re: Any suggested workarounds for writing wrappers for functions that are to be passed as arguments?, Will W.
      • Re: Any suggested workarounds for writing wrappers for functions that are to be passed as arguments?, glen herrmannsfeldt
      • Re: Any suggested workarounds for writing wrappers for functions that are to be passed as arguments?, Ron Ford
  • Re: Any suggested workarounds for writing wrappers for functions that are to be passed as arguments?, Arjen Markus
• array constructor syntax, Cornelis
  • Re: array constructor syntax, rusi_pathan
    • Re: array constructor syntax, Richard Maine
      • Re: array constructor syntax, Cornelis
  • Re: array constructor syntax, Steven G. Kargl
• Re: odd compiler complaints with large numbers, e p chandler
  • Re: odd compiler complaints with large numbers, glen herrmannsfeldt
• Re: novice needs help, Arjen Markus
• Re: size of space to be allocated, David Thompson
  • <Possible follow-ups>
  • Re: size of space to be allocated, Steven Correll
    • Re: size of space to be allocated, Richard Maine
      • Re: size of space to be allocated, Steven Correll
      • Re: size of space to be allocated, glen herrmannsfeldt
• Re: Fortran Forum Recommendation, David Thompson
  • Re: Fortran Forum Recommendation, Gary Scott
    • Re: Fortran Forum Recommendation, dpb
      • Re: Fortran Forum Recommendation, Gary Scott
      • Re: Fortran Forum Recommendation, Richard Maine
    • Re: Fortran Forum Recommendation, Ian Bush
      • Re: Fortran Forum Recommendation, Gary Scott
      • Re: Fortran Forum Recommendation, Gary Scott
• Re: Project dependency of CVF 6.6c, Mike
  • <Possible follow-ups>
  • Re: Project dependency of CVF 6.6c, ianbush . throwaway . account
• Re: C Interoperability - Strings, Ron Ford
  • Re: C Interoperability - Strings, Gary Scott
  • <Possible follow-ups>
  • Re: C Interoperability - Strings, ianbush . throwaway . account
    • Re: C Interoperability - Strings, Gary Scott
      • Re: C Interoperability - Strings, Richard Maine
      • Re: C Interoperability - Strings, Ian Bush
      • Message not available
      • Re: C Interoperability - Strings, Gary Scott
      • Re: C Interoperability - Strings, David Thompson
      • Message not available
      • Re: C Interoperability - Strings, LR
      • Message not available
      • Re: C Interoperability - Strings, glen herrmannsfeldt
      • Message not available
      • Re: C Interoperability - Strings, LR
      • Message not available
      • Re: C Interoperability - Strings, Gary Scott
• Re: Conversion from int to char, Ron Ford
  • Re: Conversion from int to char, fm2766
    • Re: Conversion from int to char, Ron Ford
  • <Possible follow-ups>
  • Re: Conversion from int to char, glen herrmannsfeldt
• Re: busting sp datatypes, Ron Ford
  • <Possible follow-ups>
  • Re: busting sp datatypes, David Thompson

• Security
• UNIX
• Linux
• Coding
• Usenet

• Archive
• About
• Privacy
• Search
• Imprint

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