comp.lang.fortran

• Thread Index

---

• Re: OT: Cicadas (was Re: KISS4691, a potentially top-ranked RNG.)
  • From: Uno
• Re: query the file status: open or close?
  • From: JB
• Re: When to Declare an External Function as EXTERNAL in a Module ??
  • From: Steven Correll
• Re: query the file status: open or close?
  • From: glen herrmannsfeldt
• Re: query the file status: open or close?
  • From: glen herrmannsfeldt
• Re: query the file status: open or close?
  • From: Ron Shepard
• Re: When to Declare an External Function as EXTERNAL in a Module ??
  • From: Richard Maine
• Re: When to Declare an External Function as EXTERNAL in a Module ??
  • From: monir
• Re: non portable - a problem with direct access
  • From: nmm1
• Re: query the file status: open or close?
  • From: nmm1
• Re: When to Declare an External Function as EXTERNAL in a Module ??
  • From: Richard Maine
• Re: When to Declare an External Function as EXTERNAL in a Module ??
  • From: monir
• Re: non portable - a problem with direct access
  • From: Uno
• Re: non portable - a problem with direct access
  • From: e p chandler
• Re: query the file status: open or close?
  • From: glen herrmannsfeldt
• Re: non portable - a problem with direct access
  • From: Sjouke Burry
• Re: If I get "undefined reference to `mp_barrier_'", which MPI library do I need to link with?
  • From: gmail-unlp
• Re: query the file status: open or close?
  • From: Steven Correll
• Re: non portable - a problem with direct access
  • From: Clive Page
• OT: Cicadas (was Re: KISS4691, a potentially top-ranked RNG.)
  • From: Louis Krupp
• Re: non portable - a problem with direct access
  • From: nmm1
• Re: non portable - a problem with direct access
  • From: e p chandler
• Re: non portable - a problem with direct access
  • From: Steve Lionel
• Re: non portable - a problem with direct access
  • From: GaryScott
• non portable - a problem with direct access
  • From: e p chandler
• Re: If I get "undefined reference to `mp_barrier_'", which MPI library do I need to link with?
  • From: nmm1
• Re: If I get "undefined reference to `mp_barrier_'", which MPI library do I need to link with?
  • From: Simon
• If I get "undefined reference to `mp_barrier_'", which MPI library do I need to link with?
  • From: Andrei
• Re: query the file status: open or close?
  • From: nmm1
• Re: query the file status: open or close?
  • From: glen herrmannsfeldt
• Re: Problem to compile with g77 a program which was normally compiled with Absoft compiler
  • From: Simon
• Re: query the file status: open or close?
  • From: nmm1
• Problem to compile with g77 a program which was normally compiled with Absoft compiler
  • From: lappis bike
• Re: query the file status: open or close?
  • From: robert . corbett
• Re: data types inside interface
  • From: Richard Maine
• Re: data types inside interface
  • From: Thomas Robitaille
• data types inside interface
  • From: Thomas Robitaille
• Re: query the file status: open or close?
  • From: Paul van Delst
• Re: query the file status: open or close?
  • From: Richard Maine
• Re: query the file status: open or close?
  • From: dpb
• query the file status: open or close?
  • From: Allamarein
• mazadoco
  • From: kasthuri j
• Re: execution times for Open64 Fortran 95 compiler
  • From: baf
• Re: execution times for Open64 Fortran 95 compiler
  • From: David Duffy
• Re: execution times for Open64 Fortran 95 compiler
  • From: Tobias Burnus
• Re: quest6ion about preceding spaces
  • From: glen herrmannsfeldt
• Re: quest6ion about preceding spaces
  • From: Dave Allured
• Re: execution times for Open64 Fortran 95 compiler
  • From: FX
• execution times for Open64 Fortran 95 compiler
  • From: David Duffy
• Re: quest6ion about preceding spaces
  • From: glen herrmannsfeldt
• solutions books
  • From: solutions for student
• solutions books
  • From: solutions for student
• Re: quest6ion about preceding spaces
  • From: Dave Allured
• Re: quest6ion about preceding spaces
  • From: robin
• Re: quest6ion about preceding spaces
  • From: Ken Fairfield
• Re: When to Declare an External Function as EXTERNAL in a Module ??
  • From: Richard Maine
• Re: When to Declare an External Function as EXTERNAL in a Module ??
  • From: monir
• Re: When to Declare an External Function as EXTERNAL in a Module ??
  • From: Richard Maine
• Re: When to Declare an External Function as EXTERNAL in a Module ??
  • From: steve
• quest6ion about preceding spaces
  • From: Robin
• When to Declare an External Function as EXTERNAL in a Module ??
  • From: monir
• cheap *** hoodies, t-shirts, jeans , shirts ( www.nike-black.com)
  • From: *** jerseys clothes
• designer Christian Louboutin
  • From: www.guomeitrade.com
• Re: This implicit statement is not positioned correctly within the scope unit
  • From: James Van Buskirk
• Re: This implicit statement is not positioned correctly within the scope unit
  • From: Steve Lionel
• Re: gate II
  • From: glen herrmannsfeldt
• Re: This implicit statement is not positioned correctly within the scope unit
  • From: robin
• Re: gate II
  • From: Louis Krupp
• Re: gate II
  • From: glen herrmannsfeldt
• Re: gate II
  • From: Louis Krupp
• Re: Fortran Vs C, C++, C#
  • From: Dick Hendrickson
• Re: gate II
  • From: Louis Krupp
• Re: gate II
  • From: Uno
• Re: gate II
  • From: glen herrmannsfeldt
• Re: gate II
  • From: nmm1
• Re: gate II
  • From: Louis Krupp
• Re: gate II
  • From: Uno
• Re: gate II
  • From: Uno
• Re: Fortran Vs C, C++, C#
  • From: Colin Watters
• Re: This implicit statement is not positioned correctly within the scope unit
  • From: James Van Buskirk
• Re: This implicit statement is not positioned correctly within the scope unit
  • From: Steve Lionel
• Re: This implicit statement is not positioned correctly within the scope unit
  • From: dpb
• Re: This implicit statement is not positioned correctly within the scope unit
  • From: dpb
• This implicit statement is not positioned correctly within the scope unit
  • From: Allamarein
• Re: Free dell laptops offered by bill gates foundation
  • From: robin
• Re: gate II
  • From: Louis Krupp
• Re: gate II
  • From: Uno
• Re: Ordinary differential equations system: runge-kutta with adaptive step
  • From: mecej4
• Re: Ordinary differential equations system: runge-kutta with adaptive step
  • From: Allamarein
• Re: Ordinary differential equations system: runge-kutta with adaptive step
  • From: Allamarein
• Ordinary differential equations system: runge-kutta with adaptive step
  • From: Allamarein
• Ordinary differential equations system: runge-kutta with adaptive step
  • From: Red Star
• Re: real kind declaration
  • From: Richard Maine
• Re: real kind declaration
  • From: m_b_metcalf
• real kind declaration
  • From: rudra
• VERSACE jeans (men) (www.nike-black.com)
  • From: *** jerseys clothes
• Re: Code builder
  • From: fj
• Re: Code builder
  • From: Mike Prager
• Re: Code builder
  • From: Mike Prager
• Miss World Aishwarya <***> Videos Taking Her Bath.
  • From: spiderman
• Re: Fortran Vs C, C++, C#
  • From: nmm1
• Re: Fortran Vs C, C++, C#
  • From: Gordon Sande
• Re: Fortran Vs C, C++, C#
  • From: Phillip Helbig---undress to reply
• Re: Fortran Vs C, C++, C#
  • From: Terence
• Re: Pointer Comparison
  • From: robin
• solutions book
  • From: solutions for student
• Re: gate II
  • From: Richard Maine
• Re: Pointer Comparison
  • From: Richard Maine
• Pointer Comparison
  • From: GianLuigi Piacentini
• Re: gate II
  • From: Louis Krupp
• Re: gate II
  • From: Gib Bogle
• Re: gate II
  • From: Dick Hendrickson
• Re: gate II
  • From: Uno
• Re: pack problem with intel 11.1
  • From: Dick Hendrickson
• Re: pack problem with intel 11.1
  • From: glen herrmannsfeldt
• pack problem with intel 11.1
  • From: pcirrus
• Re: Fortran Vs C, C++, C#
  • From: Thomas Koenig
• Re: Integrating executable files in fortran code
  • From: Allamarein
• Re: Integrating executable files in fortran code
  • From: Allamarein
• Re: Integrating executable files in fortran code
  • From: glen herrmannsfeldt
• Re: Integrating executable files in fortran code
  • From: Allamarein
• Re: Integrating executable files in fortran code
  • From: glen herrmannsfeldt
• Re: Integrating executable files in fortran code
  • From: Louis Krupp
• Re: Integrating executable files in fortran code
  • From: steve
• Integrating executable files in fortran code
  • From: Allamarein
• CPA AFFILIATE NETWORKS AWESOME EARNINGS FROM YOUR HOME
  • From: jameser
• Re: Fortran standard question: Aliasing involving dummy arguments
  • From: robert . corbett
• Re: Fortran standard question: Aliasing involving dummy arguments
  • From: robert . corbett
• Re: Fortran standard question: Aliasing involving dummy arguments
  • From: robert . corbett
• Re: Fortran standard question: Aliasing involving dummy arguments
  • From: glen herrmannsfeldt
• Re: Fortran standard question: Aliasing involving dummy arguments
  • From: Tobias Burnus
• Re: Fortran standard question: Aliasing involving dummy arguments
  • From: glen herrmannsfeldt
• Re: Fortran standard question: Aliasing involving dummy arguments
  • From: Tobias Burnus
• Re: Fortran standard question: Aliasing involving dummy arguments
  • From: Dick Hendrickson
• Re: Fortran standard question: Aliasing involving dummy arguments
  • From: Dick Hendrickson
• Re: Fortran standard question: Aliasing involving dummy arguments
  • From: Tobias Burnus
• Re: Fortran standard question: Aliasing involving dummy arguments
  • From: glen herrmannsfeldt
• Fortran standard question: Aliasing involving dummy arguments
  • From: Tobias Burnus
• Re: problems with list directed formatting
  • From: robin
• Re: problems with list directed formatting
  • From: robin
• Re: Windows API programming with gfortran or g95
  • From: Phillip Helbig---undress to reply
• Re: Windows API programming with gfortran or g95
  • From: Gib Bogle
• Re: Windows API programming with gfortran or g95
  • From: Steven Correll
• Re: Windows API programming with gfortran or g95
  • From: James Van Buskirk
• Re: Windows API programming with gfortran or g95
  • From: Gary L. Scott
• Re: Windows API programming with gfortran or g95
  • From: James Van Buskirk
• Re: Windows API programming with gfortran or g95
  • From: FX
• Re: Windows API programming with gfortran or g95
  • From: Steve Lionel
• Re: Functions with side effects
  • From: glen herrmannsfeldt
• Re: problems with list directed formatting
  • From: e p chandler
• Re: problems with list directed formatting
  • From: Richard Maine
• Re: problems with list directed formatting
  • From: e p chandler
• Re: problems with list directed formatting
  • From: Richard Maine
• Re: problems with list directed formatting
  • From: Alois Steindl
• problems with list directed formatting
  • From: e p chandler
• Re: Functions with side effects
  • From: nmm1
• Re: Functions with side effects
  • From: Dick Hendrickson
• Re: Functions with side effects
  • From: Gordon Sande
• Re: Functions with side effects
  • From: glen herrmannsfeldt
• Re: Windows API programming with gfortran or g95
  • From: dpb
• Re: Windows API programming with gfortran or g95
  • From: Phillip Helbig---undress to reply
• Re: Windows API programming with gfortran or g95
  • From: The Star King
• Re: Functions with side effects
  • From: Richard Maine
• Re: Functions with side effects
  • From: Ron Shepard
• Re: Functions with side effects
  • From: robin
• Re: Windows API programming with gfortran or g95
  • From: sturlamolden
• Re: Windows API programming with gfortran or g95
  • From: James Van Buskirk
• Re: Windows API programming with gfortran or g95
  • From: The Star King
• Re: Windows API programming with gfortran or g95
  • From: Steve Lionel
• Re: Functions with side effects
  • From: Dan Nagle
• Re: Windows API programming with gfortran or g95
  • From: GaryScott
• Re: Windows API programming with gfortran or g95
  • From: glen herrmannsfeldt
• Re: Functions with side effects
  • From: glen herrmannsfeldt
• Re: Errrors while debugging in Compaq Visual Fortran 6.6
  • From: dpb
• Re: Windows API programming with gfortran or g95
  • From: The Star King
• Re: Windows API programming with gfortran or g95
  • From: Tobias Burnus
• Re: Errrors while debugging in Compaq Visual Fortran 6.6
  • From: Allamarein
• Re: Windows API programming with gfortran or g95
  • From: The Star King
• Re: Windows API programming with gfortran or g95
  • From: Steve Lionel
• Re: Functions with side effects
  • From: Richard Maine
• Re: Windows API programming with gfortran or g95
  • From: James Van Buskirk
• Re: Functions with side effects
  • From: Richard Maine
• Re: Functions with side effects
  • From: glen herrmannsfeldt
• Re: Windows API programming with gfortran or g95
  • From: The Star King
• Re: Windows API programming with gfortran or g95
  • From: steve
• Windows API programming with gfortran or g95
  • From: The Star King
• Re: Functions with side effects
  • From: Dan Nagle
• Re: Functions with side effects
  • From: gmail-unlp
• Re: Functions with side effects
  • From: Gordon Sande
• Re: Functions with side effects
  • From: nmm1
• Re: Functions with side effects
  • From: Louis Krupp
• Re: Deallocate all
  • From: fj
• Re: Functions with side effects
  • From: Ron Shepard
• Excell calling dll with 100% CPU usage
  • From: senhor
• Re: best way to pass arguments inside dlls
  • From: steve
• best way to pass arguments inside dlls
  • From: Hifi-Comp
• Re: Errrors while debugging in Compaq Visual Fortran 6.6
  • From: dpb
• Re: Errrors while debugging in Compaq Visual Fortran 6.6
  • From: Allamarein
• Re: Errrors while debugging in Compaq Visual Fortran 6.6
  • From: dpb
• Re: Errrors while debugging in Compaq Visual Fortran 6.6
  • From: Gib Bogle
• Re: Errrors while debugging in Compaq Visual Fortran 6.6
  • From: Allamarein
• Re: Errrors while debugging in Compaq Visual Fortran 6.6
  • From: dpb
• Re: Functions with side effects
  • From: Richard Maine
• Re: Functions with side effects
  • From: Dick Hendrickson
• Re: Functions with side effects
  • From: nmm1
• Re: Functions with side effects
  • From: glen herrmannsfeldt
• Re: Functions with side effects
  • From: Richard Maine
• Re: Errrors while debugging in Compaq Visual Fortran 6.6
  • From: dpb
• Re: Errrors while debugging in Compaq Visual Fortran 6.6
  • From: Allamarein
• Re: Errrors while debugging in Compaq Visual Fortran 6.6
  • From: dpb
• Re: Functions with side effects
  • From: Dick Hendrickson
• Re: Functions with side effects
  • From: ttw6687@xxxxxxx
• Errrors while debugging in Compaq Visual Fortran 6.6
  • From: Allamarein
• Functions with side effects
  • From: robin
• Re: OpenMP & MPI
  • From: nmm1
• Re: Functions with side effects
  • From: Richard Maine
• Re: Functions with side effects
  • From: robin
• Re: Deallocate all
  • From: glen herrmannsfeldt
• Re: Functions with side effects
  • From: gmail-unlp
• Re: Deallocate all
  • From: Ron Shepard
• gate II
  • From: Uno
• Re: what memory gets used?
  • From: Jimbo
• Re: what memory gets used?
  • From: glen herrmannsfeldt
• Re: existence of directory
  • From: Jimbo
• what memory gets used?
  • From: JimBo
• Re: OpenMP & MPI
  • From: sturlamolden
• Re: Functions with side effects
  • From: Dick Hendrickson
• Re: OpenMP & MPI
  • From: sturlamolden
• Re: question on ** operator
  • From: glen herrmannsfeldt
• Re: question on ** operator
  • From: Richard Maine
• Re: question on ** operator
  • From: Richard Maine
• Re: question on ** operator
  • From: Gordon Sande
• Re: question on ** operator
  • From: steve
• Re: question on ** operator
  • From: steve
• Re: question on ** operator
  • From: Phillip Helbig---undress to reply
• Re: question on ** operator
  • From: glen herrmannsfeldt
• Re: question on ** operator
  • From: robin
• Re: question on ** operator
  • From: steve
• Re: question on ** operator
  • From: Phillip Helbig---undress to reply
• Re: question on ** operator
  • From: m_b_metcalf
• question on ** operator
  • From: analyst41@xxxxxxxxxxx
• Re: Fortran Vs C, C++, C#
  • From: sturlamolden
• CHANEL handbags (www.nike-black.com)
  • From: *** watches
• Re: Fortran Vs C, C++, C#
  • From: Ron Shepard
• Re: Functions with side effects
  • From: gmail-unlp
• Re: Functions with side effects
  • From: gmail-unlp
• Re: OpenMP & MPI
  • From: gmail-unlp
• Re: Functions with side effects
  • From: robin
• Re: OpenMP & MPI
  • From: gmail-unlp
• Re: MR&C chp 14
  • From: nmm1
• Re: Preaching to the choir
  • From: Robert Myers
• Re: MR&C chp 14
  • From: Richard Maine
• Re: segmentation fault caused by allocate memory in a loop?
  • From: Louis Krupp
• Re: Functions with side effects
  • From: Dick Hendrickson
• Re: Functions with side effects
  • From: nmm1
• Re: Functions with side effects
  • From: mecej4
• Re: segmentation fault caused by allocate memory in a loop?
  • From: Benjamin
• Re: Functions with side effects
  • From: nmm1
• Re: Preaching to the choir
  • From: Uno
• Re: Preaching to the choir
  • From: Gib Bogle
• Re: Preaching to the choir
  • From: Gib Bogle
• Re: MR&C chp 14
  • From: Uno
• Re: MR&C chp 14
  • From: Richard Maine
• Re: segmentation fault caused by allocate memory in a loop?
  • From: robin
• Re: Functions with side effects
  • From: robin
• Re: Preaching to the choir
  • From: Uno
• Re: Functions with side effects
  • From: Dick Hendrickson
• Re: Functions with side effects
  • From: nmm1
• Re: Functions with side effects
  • From: nmm1
• Re: Functions with side effects
  • From: Dick Hendrickson
• Re: Functions with side effects
  • From: Dick Hendrickson
• Re: Functions with side effects
  • From: Dick Hendrickson
• Re: Functions with side effects
  • From: glen herrmannsfeldt
• Re: Fortran Vs C, C++, C#
  • From: Colin Watters
• Re: administrator of this comp.lang.fortran
  • From: louis
• Re: Functions with side effects
  • From: nmm1
• Re: Functions with side effects
  • From: Thomas Koenig
• Re: administrator of this comp.lang.fortran
  • From: dpb
• Re: MR&C chp 14
  • From: Uno
• Re: Fortran Vs C, C++, C#
  • From: Lynn McGuire
• Re: creating shared libraries from Fortran code
  • From: Eli Osherovich
• Re: creating shared libraries from Fortran code
  • From: peruron
• Re: Fortran Vs C, C++, C#
  • From: Colin Watters
• administrator of this comp.lang.fortran
  • From: louis
• Re: creating shared libraries from Fortran code
  • From: Barron
• Re: Functions with side effects
  • From: Dick Hendrickson
• Re: segmentation fault caused by allocate memory in a loop?
  • From: Louis Krupp
• Re: creating shared libraries from Fortran code
  • From: Barron
• Re: creating shared libraries from Fortran code
  • From: Eli Osherovich
• Re: segmentation fault caused by allocate memory in a loop?
  • From: dpb
• Re: creating shared libraries from Fortran code
  • From: gmail-unlp
• Re: creating shared libraries from Fortran code
  • From: Eli Osherovich
• Re: segmentation fault caused by allocate memory in a loop?
  • From: dpb
• Re: creating shared libraries from Fortran code
  • From: gmail-unlp
• Re: creating shared libraries from Fortran code
  • From: dpb
• Re: creating shared libraries from Fortran code
  • From: Barron
• Re: creating shared libraries from Fortran code
  • From: Eli Osherovich
• Re: segmentation fault caused by allocate memory in a loop?
  • From: Benjamin
• Re: creating shared libraries from Fortran code
  • From: gmail-unlp
• creating shared libraries from Fortran code
  • From: Eli Osherovich
• creating shared library from Fortran
  • From: Eli Osherovich
• Re: Deallocate all
  • From: Gordon Sande
• Re: Deallocate all
  • From: Arjen Markus
• Re: Functions with side effects
  • From: gmail-unlp
• Re: Deallocate all
  • From: Philipp E. Weidmann
• Re: Deallocate all
  • From: robin
• Re: Fortran Vs C, C++, C#
  • From: nmm1
• Re: Fortran Vs C, C++, C#
  • From: glen herrmannsfeldt
• Re: Functions with side effects
  • From: nmm1
• Re: Functions with side effects
  • From: Richard Maine
• Re: Functions with side effects
  • From: nmm1
• Re: Functions with side effects
  • From: nmm1
• Re: Deallocate all
  • From: robert . corbett
• Deallocate all
  • From: A Watcher
• Re: Functions with side effects
  • From: Richard Maine
• Re: Functions with side effects
  • From: gmail-unlp
• Re: Functions with side effects
  • From: gmail-unlp
• Re: Functions with side effects
  • From: robin
• Re: segmentation fault caused by allocate memory in a loop?
  • From: robin
• Re: Fortran Vs C, C++, C#
  • From: Richard Maine
• Re: Fortran Vs C, C++, C#
  • From: dpb
• Re: Fortran Vs C, C++, C#
  • From: Richard Maine
• Re: Fortran Vs C, C++, C#
  • From: dpb
• Re: OpenMP & MPI
  • From: Tobias Burnus
• Re: Fortran Vs C, C++, C#
  • From: dpb
• Re: Functions with side effects
  • From: Richard Maine
• Re: OpenMP & MPI
  • From: nmm1
• Re: MATLAB chrashes when loading FORTRAN dynamic library
  • From: Eli Osherovich
• Re: Functions with side effects
  • From: Dick Hendrickson
• Re: Functions with side effects
  • From: Richard Maine
• Re: Functions with side effects
  • From: Richard Maine
• Re: OpenMP & MPI
  • From: Victor Eijkhout
• Re: MR&C chp 14
  • From: steve
• Re: Functions with side effects
  • From: Jan Gerrit Kootstra
• Re: MR&C chp 14
  • From: Uno
• Re: Functions with side effects
  • From: mecej4
• Re: Fortran Vs C, C++, C#
  • From: Lynn McGuire
• Re: Fortran Vs C, C++, C#
  • From: Lynn McGuire
• Re: Functions with side effects
  • From: Richard Maine
• Re: Fortran Vs C, C++, C#
  • From: dpb
• Re: Fortran Vs C, C++, C#
  • From: dpb
• Functions with side effects
  • From: Thomas Koenig
• Re: Fortran Vs C, C++, C#
  • From: Giorgio Pastore
• Re: segmentation fault caused by allocate memory in a loop?
  • From: dpb
• Re: Fortran Vs C, C++, C#
  • From: Richard Maine
• Re: Fortran Vs C, C++, C#
  • From: nmm1
• Re: Fortran Vs C, C++, C#
  • From: nmm1
• Re: segmentation fault caused by allocate memory in a loop?
  • From: robin
• Re: Fortran Vs C, C++, C#
  • From: Lynn McGuire
• Re: Fortran Vs C, C++, C#
  • From: Lynn McGuire
• Re: Fortran Vs C, C++, C#
  • From: Richard Maine
• Re: Fortran Vs C, C++, C#
  • From: nmm1
• Re: Fortran Vs C, C++, C#
  • From: Lynn McGuire
• Re: OpenMP & MPI
  • From: nmm1
• Re: OpenMP & MPI
  • From: sturlamolden
• Re: OpenMP & MPI
  • From: sturlamolden
• Re: OpenMP & MPI
  • From: nmm1
• Re: OpenMP & MPI
  • From: nmm1
• Re: OpenMP & MPI
  • From: Victor Eijkhout
• Re: OpenMP & MPI
  • From: sturlamolden
• Re: Fortran Vs C, C++, C#
  • From: sturlamolden
• Re: Runge-Kutta method for solving IVPs
  • From: Arjen Markus
• Re: Runge-Kutta method for solving IVPs
  • From: Arjan
• Re: segmentation fault caused by allocate memory in a loop?
  • From: Louis Krupp
• Re: Runge-Kutta method for solving IVPs
  • From: Florian Buerzle
• Re: Runge-Kutta method for solving IVPs
  • From: Philipp E. Weidmann
• Re: segmentation fault caused by allocate memory in a loop?
  • From: Benjamin
• Re: segmentation fault caused by allocate memory in a loop?
  • From: nmm1
• Re: segmentation fault caused by allocate memory in a loop?
  • From: Richard Maine
• segmentation fault caused by allocate memory in a loop?
  • From: Benjamin
• Re: Fortran Vs C, C++, C#
  • From: nmm1
• Re: Fortran Vs C, C++, C#
  • From: card
• Re: Preaching to the choir
  • From: viper-2
• Re: Preaching to the choir
  • From: e p chandler
• Fortran 2003 Dependency Issues (and beyond) in Babel
  • From: Dietmar Ebner
• Re: Runge-Kutta method for solving IVPs
  • From: Gib Bogle
• Re: OpenMP & MPI
  • From: nmm1
• Re: OpenMP & MPI
  • From: Victor Eijkhout
• Re: MR&C chp 14
  • From: steve
• Re: Preaching to the choir
  • From: nmm1
• Re: Preaching to the choir
  • From: viper-2
• Re: Preaching to the choir
  • From: e p chandler
• Re: Runge-Kutta method for solving IVPs
  • From: mecej4
• Re: Preaching to the choir
  • From: viper-2
• Re: Preaching to the choir
  • From: nmm1
• Preaching to the choir
  • From: m_b_metcalf
• Re: Runge-Kutta method for solving IVPs
  • From: Philipp E. Weidmann
• Re: Runge-Kutta method for solving IVPs
  • From: Les Neilson
• Re: Runge-Kutta method for solving IVPs
  • From: Philipp E. Weidmann
• Re: Runge-Kutta method for solving IVPs
  • From: Simon
• Runge-Kutta method for solving IVPs
  • From: Philipp E. Weidmann
• Re: MR&C chp 14
  • From: Uno
• Re: MR&C chp 14
  • From: steve
• MR&C chp 14
  • From: Uno
• Re: MATLAB chrashes when loading FORTRAN dynamic library
  • From: Gib Bogle
• Re: Coarray Fortran
  • From: Gib Bogle
• Re: IDE for ifort on Linux
  • From: jfh
• Re: Fortran Vs C, C++, C#
  • From: jfh
• Re: Compaq Visual Fortran 6.6 on Vista
  • From: Ian
• A note on two Fortran related projects
  • From: Abraham Abraham
• Re: Compaq Visual Fortran 6.6 on Vista
  • From: dpb
• Re: Coarray Fortran
  • From: nmm1
• Re: Coarray Fortran
  • From: Ian Bush
• Re: Compaq Visual Fortran 6.6 on Vista
  • From: Allamarein
• Re: Compaq Visual Fortran 6.6 on Vista
  • From: Steve Lionel
• Re: Compaq Visual Fortran 6.6 on Vista
  • From: dpb
• Re: Compaq Visual Fortran 6.6 on Vista
  • From: Allamarein
• Re: Compaq Visual Fortran 6.6 on Vista
  • From: dpb
• Compaq Visual Fortran 6.6 on Vista
  • From: Allamarein
• Re: removing /save fortran compiler option
  • From: Lynn McGuire
• Re: Neato: F2003 Handbook
  • From: Lynn McGuire
• Re: Random number in Fortran 90/95
  • From: nmm1
• Re: Random number in Fortran 90/95
  • From: Jason Riedy
• Re: Coarray Fortran
  • From: nmm1
• Re: Coarray Fortran
  • From: Ian Bush
• Re: Fortran Vs C, C++, C#
  • From: mecej4
• Re: Fortran Vs C, C++, C#
  • From: mecej4
• Re: Coarray Fortran
  • From: nmm1
• Re: Coarray Fortran
  • From: nmm1
• Re: Random number in Fortran 90/95
  • From: nmm1
• Job opportunity for Fortran developer
  • From: Steven Correll
• Re: Fortran Vs C, C++, C#
  • From: robin
• Re: IDE for ifort on Linux
  • From: Ian Harvey
• Re: a weird COMMON fact
  • From: robin
• Re: IDE for ifort on Linux
  • From: dpb
• Re: IDE for ifort on Linux
  • From: Louis Krupp
• Re: IDE for ifort on Linux
  • From: steve
• Re: a weird COMMON fact
  • From: Phillip Helbig---undress to reply
• Re: a weird COMMON fact
  • From: dpb
• Re: IDE for ifort on Linux
  • From: mariano mendez
• Re: problem with linking calcomp library
  • From: mecej4
• Re: a weird COMMON fact
  • From: mecej4
• Re: IDE for ifort on Linux
  • From: mariano mendez
• Re: Coarray Fortran
  • From: Dick Hendrickson
• Re: IDE for ifort on Linux
  • From: steve
• Re: IDE for ifort on Linux
  • From: Dan Nagle
• Re: a weird COMMON fact
  • From: analyst41@xxxxxxxxxxx
• Re: a weird COMMON fact
  • From: dpb
• Re: a weird COMMON fact
  • From: dpb
• Re: a weird COMMON fact
  • From: analyst41@xxxxxxxxxxx
• Re: a weird COMMON fact
  • From: Gordon Sande
• Re: a weird COMMON fact
  • From: dpb
• Re: a weird COMMON fact
  • From: Gordon Sande
• Re: IDE for ifort on Linux
  • From: Gordon Sande
• Re: IDE for ifort on Linux
  • From: dpb
• Re: a weird COMMON fact
  • From: dpb
• a weird COMMON fact
  • From: analyst41@xxxxxxxxxxx
• Re: problem with linking calcomp library
  • From: parto
• Stephen Wolfram's book, "A New Kind of Science" gives us three (3) very important facts:
  • From: fitz
• Re: Reason to deallocate out array
  • From: Richard Maine
• Re: Reason to deallocate out array
  • From: Eli Osherovich
• Re: Reason to deallocate out array
  • From: Eli Osherovich
• Re: IDE for ifort on Linux
  • From: Philipp E. Weidmann
• Re: removing /save fortran compiler option
  • From: Louis Krupp
• Re: IDE for ifort on Linux
  • From: Lurkos
• Re: where can i type this line?
  • From: mecej4
• Re: IDE for ifort on Linux
  • From: mariano mendez
• Re: removing /save fortran compiler option
  • From: Lynn McGuire
• Re: Reason to deallocate out array
  • From: Richard Maine
• Re: Reason to deallocate out array
  • From: Eli Osherovich
• Reason to deallocate out array
  • From: Eli Osherovich
• Re: IDE for ifort on Linux
  • From: Philipp E. Weidmann
• Re: removing /save fortran compiler option
  • From: Louis Krupp
• Re: removing /save fortran compiler option
  • From: dpb
• IDE for ifort on Linux
  • From: Robert Myers
• Re: Neato: F2003 Handbook
  • From: Colin Watters
• Re: removing /save fortran compiler option
  • From: Lynn McGuire
• Re: where can i type this line?
  • From: Uno
• Sale Casio watches（www.nike-black.com）
  • From: *** football clothes
• Re: Fortran Vs C, C++, C#
  • From: blmblm
• Re: where can i type this line?
  • From: Dr Ivan D. Reid
• where can i type this line?
  • From: bahar
• Re: gui fortran
  • From: e p chandler
• Re: calling a real from C
  • From: Richard Maine
• Re: calling a real from C
  • From: Uno
• Re: calling a real from C
  • From: Uno
• Re: Fortran 2003 Handbook
  • From: Uno
• Re: gui fortran
  • From: Gib Bogle
• Re: Neato: F2003 Handbook
  • From: Richard Maine
• Neato: F2003 Handbook
  • From: GaryScott
• Re: calling a real from C
  • From: Richard Maine
• Re: calling a real from C
  • From: Uno
• Re: problem with linking calcomp library
  • From: mecej4
• Re: problem with linking calcomp library
  • From: user1
• Re: Automatic generation of Jacobian matrices
  • From: Philipp E. Weidmann
• Re: Automatic generation of Jacobian matrices
  • From: Philipp E. Weidmann
• Re: Automatic generation of Jacobian matrices
  • From: Paul van Delst
• Re: Automatic generation of Jacobian matrices
  • From: Richard Maine
• Automatic generation of Jacobian matrices
  • From: Philipp E. Weidmann
• Re: problem with linking calcomp library
  • From: dpb
• Re: How to dump/read user-defined types with allocatable components?
  • From: Arjan
• problem with linking calcomp library
  • From: bahar
• sale Red Bull Baseball Hats ( www.nike-black.com )
  • From: *** football clothes
• Re: calling a real from C
  • From: Uno
• Re: How to dump/read user-defined types with allocatable components?
  • From: Richard Maine
• Re: How to dump/read user-defined types with allocatable components?
  • From: Paul van Delst
• How to dump/read user-defined types with allocatable components?
  • From: Arjan
• Re: Problem dynamically loading a library
  • From: Arjen Markus
• Re: MATLAB chrashes when loading FORTRAN dynamic library
  • From: Eli Osherovich
• Re: Multi dimension char array
  • From: Fortran_follower
• Re: Open Scientific Library - libosl.org down
  • From: Reinhold Bader
• Re: calling a real from C
  • From: Tobias Burnus
• Re: calling a real from C
  • From: user1
• Re: Passing overloaded function as argument to subroutine
  • From: Ian Harvey
• Re: Coarray Fortran
  • From: Reinhold Bader
• Re: calling a real from C
  • From: Erik Toussaint
• Re: Passing overloaded function as argument to subroutine
  • From: Richard Maine
• Re: MATLAB chrashes when loading FORTRAN dynamic library
  • From: Ian Harvey
• Re: calling a real from C
  • From: Uno
• Re: Passing overloaded function as argument to subroutine
  • From: Nick Fort
• Re: Coarray Fortran
  • From: Dick Hendrickson
• Re: Coarray Fortran
  • From: Ian Bush
• Re: Passing overloaded function as argument to subroutine
  • From: Richard Maine
• Passing overloaded function as argument to subroutine
  • From: Nick Fort
• Re: Open Scientific Library - libosl.org down
  • From: Nick Fort
• Re: Problem dynamically loading a library
  • From: fj
• Re: gui fortran
  • From: Nick Fort
• Re: Multi dimension char array
  • From: Richard Maine
• Re: Multi dimension char array
  • From: m_b_metcalf
• Multi dimension char array
  • From: Fortran_follower
• Re: Coarray Fortran
  • From: Reinhold Bader
• Re: Coarray Fortran
  • From: Dick Hendrickson
• Re: calling a real from C
  • From: m_b_metcalf
• MATLAB chrashes when loading FORTRAN dynamic library
  • From: Eli Osherovich
• Re: calling a real from C
  • From: Erik Toussaint
• Re: Problem dynamically loading a library
  • From: Arjen Markus
• Re: calling a real from C
  • From: Uno
• Re: calling a real from C
  • From: Tobias Burnus
• Re: Fortran problem
  • From: Gib Bogle
• Re: calling a real from C
  • From: Uno
• Fortran problem
  • From: mortain
• Re: calling a real from C
  • From: e p chandler
• calling a real from C
  • From: Uno
• Re: removing /save fortran compiler option
  • From: dpb
• Re: removing /save fortran compiler option
  • From: Lynn McGuire
• Re: removing /save fortran compiler option
  • From: dpb
• Re: removing /save fortran compiler option
  • From: Lynn McGuire
• Re: Fortran Vs C, C++, C#
  • From: viper-2
• Re: removing /save fortran compiler option
  • From: dpb
• Re: gfortran/ifort format issues in files
  • From: glen herrmannsfeldt
• Re: non printing characters
  • From: Arjan
• Re: gfortran/ifort format issues in files
  • From: Philipp E. Weidmann
• Re: Problem dynamically loading a library
  • From: Arjen Markus
• Re: gfortran/ifort format issues in files
  • From: Jerry DeLisle
• Re: non printing characters
  • From: Phillip Helbig---undress to reply
• Re: non printing characters
  • From: Tobias Burnus
• Re: removing /save fortran compiler option
  • From: Lynn McGuire
• Re: removing /save fortran compiler option
  • From: Lynn McGuire
• Re: gfortran/ifort format issues in files
  • From: William Clodius
• Re: Why not 0?
  • From: robin
• Re: non printing characters
  • From: Richard Maine
• Re: gui fortran
  • From: e p chandler
• Re: gui fortran
  • From: e p chandler
• Re: non printing characters
  • From: e p chandler
• Re: removing /save fortran compiler option
  • From: dpb
• Re: removing /save fortran compiler option
  • From: dpb
• Re: removing /save fortran compiler option
  • From: Lynn McGuire
• Re: removing /save fortran compiler option
  • From: Richard Maine
• Re: removing /save fortran compiler option
  • From: Lynn McGuire
• Re: removing /save fortran compiler option
  • From: dpb
• Re: removing /save fortran compiler option
  • From: Lynn McGuire
• Re: removing /save fortran compiler option
  • From: dpb
• Re: gui fortran
  • From: steve
• Re: removing /save fortran compiler option
  • From: dpb
• Re: removing /save fortran compiler option
  • From: Lynn McGuire
• Re: removing /save fortran compiler option
  • From: Lynn McGuire
• Re: gui fortran
  • From: Lynn McGuire
• Re: gui fortran
  • From: Clive Page
• Re: non printing characters
  • From: Richard Maine
• non printing characters
  • From: e p chandler
• Re: Why not 0?
  • From: e p chandler
• Re: Why not 0?
  • From: Louis Krupp
• Re: Problem dynamically loading a library
  • From: Ian Harvey
• Re: Why not 0?
  • From: e p chandler
• Re: Why not 0?
  • From: mecej4
• Re: Why not 0?
  • From: Gordon Sande
• Why not 0?
  • From: Felipe Abrão
• Re: Fortran Vs C, C++, C#
  • From: Steven Correll
• Re: Problem dynamically loading a library
  • From: James Van Buskirk
• Re: Fortran Vs C, C++, C#
  • From: Gordon Sande
• Re: Fortran Vs C, C++, C#
  • From: dpb
• Re: Fortran Vs C, C++, C#
  • From: Robert Myers
• Re: Fortran Vs C, C++, C#
  • From: viper-2
• Re: Fortran Vs C, C++, C#
  • From: viper-2
• Availables : More that 3500 Solutions manuals and Test Banks (Part 3)
  • From: claudeh
• Availables : More that 3500 Solutions manuals and Test Banks (Part 2)
  • From: claudeh
• Availables : More that 3500 Solutions manuals and Test Banks (Part 1)
  • From: claudeh
• Re: Problem dynamically loading a library
  • From: James Van Buskirk
• Re: Fortran Vs C, C++, C#
  • From: Gordon Sande
• Re: Problem dynamically loading a library
  • From: Arjen Markus
• Re: Fortran Vs C, C++, C#
  • From: viper-2
• Re: removing /save fortran compiler option
  • From: mecej4
• Re: Problem dynamically loading a library
  • From: dpb
• Re: Problem dynamically loading a library
  • From: James Van Buskirk
• Re: removing /save fortran compiler option
  • From: Gordon Sande
• Re: Problem dynamically loading a library
  • From: Arjen Markus
• Re: Problem dynamically loading a library
  • From: dpb
• Re: Problem dynamically loading a library
  • From: Arjen Markus
• Re: Problem dynamically loading a library
  • From: Arjen Markus
• Re: Problem dynamically loading a library
  • From: Ian Harvey
• Re: Problem dynamically loading a library
  • From: Arjen Markus
• Re: Problem dynamically loading a library
  • From: Arjen Markus
• Re: Problem dynamically loading a library
  • From: Arjen Markus
• Re: Problem dynamically loading a library
  • From: Simon
• Problem dynamically loading a library
  • From: Arjen Markus
• Re: removing /save fortran compiler option
  • From: Louis Krupp
• Re: gfortran/ifort format issues in files
  • From: Dave Allured
• Re: Open Scientific Library - libosl.org down
  • From: Dave Allured
• Re: removing /save fortran compiler option
  • From: Lynn McGuire
• Re: gfortran/ifort format issues in files
  • From: Gib Bogle
• Re: removing /save fortran compiler option
  • From: Richard Maine
• Re: removing /save fortran compiler option
  • From: Ron Shepard
• removing /save fortran compiler option
  • From: Lynn McGuire
• Re: gfortran/ifort format issues in files
  • From: Richard Maine
• Re: gfortran/ifort format issues in files
  • From: Richard Maine
• Re: gfortran/ifort format issues in files
  • From: Dave Allured
• Re: gfortran/ifort format issues in files
  • From: Tobias Burnus
• Re: gfortran/ifort format issues in files
  • From: Richard Maine
• Re: Code builder
  • From: fj
• Re: gui fortran
  • From: e p chandler
• Re: Fortran Vs C, C++, C#
  • From: Robert Myers
• Re: gui fortran
  • From: James Van Buskirk
• Re: gui fortran
  • From: Gary L. Scott
• Re: Fortran Vs C, C++, C#
  • From: viper-2
• Re: gui fortran
  • From: feenberg
• Re: gfortran/ifort format issues in files
  • From: fj
• Re: gfortran/ifort format issues in files
  • From: Philipp E. Weidmann
• Re: Fortran Vs C, C++, C#
  • From: Louis Krupp
• Re: gui fortran
  • From: Gib Bogle
• Re: gfortran/ifort format issues in files
  • From: fj
• Re: gfortran/ifort format issues in files
  • From: Philipp E. Weidmann
• Re: gfortran/ifort format issues in files
  • From: Tobias Burnus
• gfortran/ifort format issues in files
  • From: Philipp E. Weidmann
• Re: gui fortran
  • From: Philipp E. Weidmann
• gui fortran
  • From: Robin
• Re: Fortran Vs C, C++, C#
  • From: Richard Maine
• Re: Fortran Vs C, C++, C#
  • From: Louis Krupp
• Re: Fortran Vs C, C++, C#
  • From: Robert Myers
• Re: Fortran Vs C, C++, C#
  • From: e p chandler
• Re: From Scripting to Scaling: Multi-core is challenging even the most battle-scared programmer
  • From: rusi_pathan
• Re: Fortran Vs C, C++, C#
  • From: Harald Anlauf
• Re: VMS Open Keyed access
  • From: rfengineer55
• Re: Fortran Vs C, C++, C#
  • From: FX
• Re: Fortran Vs C, C++, C#
  • From: Harald Anlauf
• Re: Fortran Vs C, C++, C#
  • From: FX
• Re: VMS Open Keyed access
  • From: glen herrmannsfeldt
• VMS Open Keyed access
  • From: rfengineer55
• Re: Fortran Vs C, C++, C#
  • From: Richard Maine
• Re: Fortran Vs C, C++, C#
  • From: glen herrmannsfeldt
• Re: Fortran Vs C, C++, C#
  • From: Thomas Koenig
• Re: Fortran Vs C, C++, C#
  • From: Thomas Koenig
• Open Scientific Library - libosl.org down
  • From: Nick Fort
• Re: "-assume byterecl" in gfortran
  • From: Philipp E. Weidmann
• Re: "-assume byterecl" in gfortran
  • From: Tobias Burnus
• Re: "-assume byterecl" in gfortran
  • From: Philipp E. Weidmann
• Re: "-assume byterecl" in gfortran
  • From: Philipp E. Weidmann
• Re: Pointer or (allocatable) array list ?
  • From: robin
• Re: Pointer or (allocatable) array list ?
  • From: robin
• Re: "-assume byterecl" in gfortran
  • From: robin
• Re: "-assume byterecl" in gfortran
  • From: Tobias Burnus
• Re: "-assume byterecl" in gfortran
  • From: dumashu
• "-assume byterecl" in gfortran
  • From: Philipp E. Weidmann
• Re: OpenMP & MPI
  • From: Ron Shepard
• Re: OpenMP & MPI
  • From: glen herrmannsfeldt
• Re: OpenMP & MPI
  • From: Friedrich
• Re: OpenMP & MPI
  • From: Friedrich
• Re: Overloading an existing overloaded subroutine
  • From: Walt Brainerd
• Re: Overloading an existing overloaded subroutine
  • From: Richard Maine
• Overloading an existing overloaded subroutine
  • From: Thomas Robitaille
• Re: OpenMP & MPI
  • From: glen herrmannsfeldt
• Re: OpenMP & MPI
  • From: Gib Bogle
• Re: OpenMP & MPI
  • From: Tim Prince
• Re: OpenMP & MPI
  • From: Richard Maine
• Coarray Fortran
  • From: GaryScott
• Re: OpenMP & MPI
  • From: glen herrmannsfeldt
• Re: OpenMP & MPI
  • From: Colin Watters
• Re: OpenMP & MPI
  • From: Tobias Burnus
• Re: Code builder
  • From: fj
• Re: OpenMP & MPI
  • From: Friedrich
• Re: From Scripting to Scaling: Multi-core is challenging even the most battle-scared programmer
  • From: Ian Bush
• Re: OpenMP & MPI
  • From: Tim Prince
• OpenMP & MPI
  • From: Friedrich
• Re: From Scripting to Scaling: Multi-core is challenging even the most battle-scared programmer
  • From: Friedrich
• From Scripting to Scaling: Multi-core is challenging even the most battle-scared programmer
  • From: Beliavsky
• Re: OT: PLPLOT binary Windows 64bit
  • From: ralf.schaa
• Re: OT: PLPLOT binary Windows 64bit
  • From: ralf.schaa
• OT: PLPLOT binary Windows 64bit
  • From: ralf.schaa
• Re: Fortran Vs C, C++, C#
  • From: Gib Bogle
• Re: Pointer or (allocatable) array list ?
  • From: glen herrmannsfeldt
• Re: Pointer or (allocatable) array list ?
  • From: Ian Bush
• Re: Fortran Vs C, C++, C#
  • From: glen herrmannsfeldt
• Re: Fortran Vs C, C++, C#
  • From: Phillip Helbig---undress to reply
• Re: Fortran Vs C, C++, C#
  • From: Robert Myers
• Re: PR1ME OPERATING SYSTEM
  • From: Mark Stevens
• Re: Fortran Vs C, C++, C#
  • From: Mark Stevens
• Re: Fortran Vs C, C++, C#
  • From: glen herrmannsfeldt
• Re: Fortran Vs C, C++, C#
  • From: glen herrmannsfeldt
• Pointer or (allocatable) array list ?
  • From: GianLuigi Piacentini
• Re: Fortran Vs C, C++, C#
  • From: glen herrmannsfeldt
• Re: Fortran Vs C, C++, C#
  • From: Louis Krupp
• Re: Fortran Vs C, C++, C#
  • From: Steven Correll
• Re: Fortran Vs C, C++, C#
  • From: Robert Myers
• Re: Fortran Vs C, C++, C#
  • From: Dave Allured
• Re: Fortran Vs C, C++, C#
  • From: Lynn McGuire
• Re: Fortran Vs C, C++, C#
  • From: Lynn McGuire
• Re: Fortran Vs C, C++, C#
  • From: Dogstar
• Re: Fortran Vs C, C++, C#
  • From: Robert Myers
• Re: Fortran Vs C, C++, C#
  • From: dpb
• Re: Fortran Vs C, C++, C#
  • From: Colin Paul Gloster
• Re: Fortran Vs C, C++, C#
  • From: Colin Paul Gloster
• Re: Fortran Vs C, C++, C#
  • From: Colin Paul Gloster
• Re: Fortran Vs C, C++, C#
  • From: robin
• Re: Fortran Vs C, C++, C#
  • From: robin
• Re: Fortran Vs C, C++, C#
  • From: blmblm
• Re: Fortran Vs C, C++, C#
  • From: blmblm
• Re: Fortran Vs C, C++, C#
  • From: Jugoslav Dujic
• Re: Code builder
  • From: Mike Prager
• Re: Fortran Vs C, C++, C#
  • From: glen herrmannsfeldt
• Re: Fortran Vs C, C++, C#
  • From: glen herrmannsfeldt
• Re: Fortran Vs C, C++, C#
  • From: robin
• Re: Fortran Vs C, C++, C#
  • From: Gib Bogle
• Re: Fortran Vs C, C++, C#
  • From: Dan Nagle
• Re: Fortran Vs C, C++, C#
  • From: Tim Prince
• Re: Fortran Vs C, C++, C#
  • From: Paul van Delst
• Re: Fortran Vs C, C++, C#
  • From: Gib Bogle

• Security
• UNIX
• Linux
• Coding
• Usenet

• Archive
• About
• Privacy
• Search
• Imprint

coding.derkeiler.com  > Archive  > Fortran  > comp.lang.fortran  > 2010-07