comp.lang.fortran

• Thread Index

---

• Re: portable 'sizeof' solution
  • From: Jan Vorbrüggen
• Re: interface blocks
  • From: Jan Vorbrüggen
• Re: interface blocks
  • From: Jan Vorbrüggen
• Re: [CHALLENGE] finding rightmost zero bit - C programmer's take
  • From: Bart Vandewoestyne
• Re: [CHALLENGE] finding rightmost zero bit
  • From: Bart Vandewoestyne
• Re: indexing tags like cscope in fortran?
  • From: jussij
• Re: [CHALLENGE] finding rightmost zero bit - C programmer's take
  • From: James Van Buskirk
• Re: ANN: f95totex: A Fortran-to-LaTeX prettyprinter (of sorts)
  • From: Jussi Jumppanen
• Re: Getting a program to inform you when it's done
  • From: Madhusudan Singh
• Re: Getting a program to inform you when it's done
  • From: Random Programmer
• Re: Getting a program to inform you when it's done
  • From: Janne Blomqvist
• Re: Getting a program to inform you when it's done
  • From: Random Programmer
• Re: [CHALLENGE] finding rightmost zero bit
  • From: Dick Hendrickson
• Re: Getting a program to inform you when it's done
  • From: Random Programmer
• Getting a program to inform you when it's done
  • From: Random Programmer
• CDC peculiarities (was Re: Undefined array elements)
  • From: Walter Spector
• Re: [CHALLENGE] finding rightmost zero bit - C programmer's take
  • From: Dr Ivan D. Reid
• Re: [CHALLENGE] finding rightmost zero bit - C programmer's take
  • From: glen herrmannsfeldt
• Re: Algorithm for "1st Tuesday", "last Saturday", etc.
  • From: David Flower
• Re: [CHALLENGE] finding rightmost zero bit
  • From: Bart Vandewoestyne
• Re: [CHALLENGE] finding rightmost zero bit
  • From: Bart Vandewoestyne
• Re: [CHALLENGE] finding rightmost zero bit
  • From: Bart Vandewoestyne
• Re: [CHALLENGE] finding rightmost zero bit - C programmer's take
  • From: N. Shamsundar
• Re: [CHALLENGE] finding rightmost zero bit
  • From: N. Shamsundar
• Re: [CHALLENGE] finding rightmost zero bit
  • From: Michel OLAGNON
• Re: Undefined array elements
  • From: Dr Ivan D. Reid
• Re: finding rightmost zero bit
  • From: glen herrmannsfeldt
• Re: finding rightmost zero bit
  • From: ttw
• Re: [CHALLENGE] finding rightmost zero bit
  • From: Gib Bogle
• Re: [CHALLENGE] finding rightmost zero bit
  • From: glen herrmannsfeldt
• Re: [CHALLENGE] finding rightmost zero bit
  • From: James Giles
• Re: [CHALLENGE] finding rightmost zero bit
  • From: glen herrmannsfeldt
• Re: little isprime challenge
  • From: e p chandler
• Re: [CHALLENGE] finding rightmost zero bit
  • From: James Giles
• Re: [CHALLENGE] finding rightmost zero bit
  • From: James Van Buskirk
• Re: [CHALLENGE] finding rightmost zero bit
  • From: glen herrmannsfeldt
• Re: NLEQ1 and open source Fortran
  • From: Steven G. Kargl
• Re: [CHALLENGE] finding rightmost zero bit
  • From: Brooks Moses
• Re: [CHALLENGE] finding rightmost zero bit
  • From: Brooks Moses
• Re: NLEQ1 and open source Fortran
  • From: N. Shamsundar
• Re: little isprime challenge
  • From: Brooks Moses
• Re: [CHALLENGE] finding rightmost zero bit
  • From: glen herrmannsfeldt
• Re: [CHALLENGE] finding rightmost zero bit
  • From: Bart Vandewoestyne
• Re: [CHALLENGE] finding rightmost zero bit
  • From: Bart Vandewoestyne
• Re: [CHALLENGE] finding rightmost zero bit
  • From: Bart Vandewoestyne
• Re: [CHALLENGE] finding rightmost zero bit
  • From: Bart Vandewoestyne
• Re: [CHALLENGE] finding rightmost zero bit
  • From: glen herrmannsfeldt
• Re: [CHALLENGE] finding rightmost zero bit
  • From: James Van Buskirk
• Re: find weekdays/dates > 1900
  • From: David Frank
• Re: [CHALLENGE] finding rightmost zero bit
  • From: glen herrmannsfeldt
• Re: [CHALLENGE] finding rightmost zero bit
  • From: Michel OLAGNON
• Re: [CHALLENGE] finding rightmost zero bit
  • From: Bart Vandewoestyne
• Re: [CHALLENGE] finding rightmost zero bit
  • From: Michel OLAGNON
• Re: little isprime challenge
  • From: billyboyer
• Re: jagged parameter arrays
  • From: David Frank
• [CHALLENGE] finding rightmost zero bit
  • From: Bart Vandewoestyne
• Re: Algorithm for "1st Tuesday", "last Saturday", etc.
  • From: David Frank
• Re: ANN: pilib: Platform/Compiler independend RTL
  • From: Martin Hierholzer
• Re: little isprime challenge
  • From: Bart Vandewoestyne
• jagged parameter arrays
  • From: Ron Shepard
• Re: Algorithm for "1st Tuesday", "last Saturday", etc.
  • From: Bob Walton
• Algorithm for "1st Tuesday", "last Saturday", etc.
  • From: mcalhoun
• Re: Fortran write(print) problem
  • From: glen herrmannsfeldt
• Re: Fortran write(print) problem
  • From: Ron Shepard
• Re: NLEQ1 and open source Fortran
  • From: feenberg
• Re: Fortran write(print) problem
  • From: Thomas Koenig
• Re: Fortran write(print) problem
  • From: Wang Jun
• Re: Fortran write(print) problem
  • From: Brooks Moses
• Re: NLEQ1 and open source Fortran
  • From: Rodrigo López Negrete
• Re: Fortran write(print) problem
  • From: Richard E Maine
• Re: maximum array size for g77 compiler
  • From: Dave Thompson
• Re: Fortran write(print) problem
  • From: Gib Bogle
• Re: interface blocks
  • From: Gordon Sande
• Re: interface blocks
  • From: Lynn
• Re: interface blocks
  • From: Gordon Sande
• Re: some fortran 77 language question
  • From: Ken Plotkin
• Re: interface blocks
  • From: Lynn
• Re: indexing tags like cscope in fortran?
  • From: beliavsky
• Re: Fortran write(print) problem
  • From: Brooks Moses
• Fortran write(print) problem
  • From: Wang Jun
• Re: indexing tags like cscope in fortran?
  • From: Harshal
• Re: indexing tags like cscope in fortran?
  • From: kfitch42@xxxxxxxxx
• Re: little isprime challenge
  • From: Bart Vandewoestyne
• Re: little isprime challenge
  • From: Mark B Stucky
• Re: NLEQ1 and open source Fortran
  • From: Kevin G. Rhoads
• Re: portable 'sizeof' solution
  • From: James Van Buskirk
• Re: NLEQ1 and open source Fortran
  • From: Rodrigo López Negrete
• Re: NLEQ1 and open source Fortran
  • From: Rodrigo López Negrete
• indexing tags like cscope in fortran?
  • From: Harshal
• Re: Final Reduce_Blanks function?
  • From: Rich Townsend
• Re: NLEQ1 and open source Fortran
  • From: awgreynolds
• Re: NLEQ1 and open source Fortran
  • From: Steve Kargl
• Re: NLEQ1 and open source Fortran
  • From: Lynn McGuire
• Re: Acceptable Pack args
  • From: [JvO]
• Re: NLEQ1 and open source Fortran
  • From: Steve Kargl
• Re: NLEQ1 and open source Fortran
  • From: awgreynolds
• Re: Acceptable Pack args
  • From: robin
• Re: NLEQ1 and open source Fortran
  • From: Steve Kargl
• Re: portable 'sizeof' solution
  • From: David Frank
• Re: Final Reduce_Blanks function?
  • From: David Frank
• Re: interface blocks
  • From: kfitch42@xxxxxxxxx
• Re: Final Reduce_Blanks function?
  • From: Rich Townsend
• Re: portable 'sizeof' solution
  • From: Rich Townsend
• Re: java -> fortran bindings
  • From: e p chandler
• Re: NLEQ1 and open source Fortran
  • From: Bart Vandewoestyne
• Re: portable 'sizeof' solution
  • From: David Frank
• Re: little isprime challenge
  • From: Bart Vandewoestyne
• Re: Ways to debug Monte Carlo Code ?
  • From: Klemens Barfus
• Re: NLEQ1 and open source Fortran
  • From: Steve Kargl
• Re: NLEQ1 and open source Fortran
  • From: Madhusudan Singh
• Re: little isprime challenge
  • From: Mark B Stucky
• Re: interface blocks
  • From: James Giles
• Re: NLEQ1 and open source Fortran
  • From: Steven G. Kargl
• Re: interface blocks
  • From: Ian Chivers
• Re: interface blocks
  • From: Lynn McGuire
• Re: little isprime challenge
  • From: Ian Chivers
• Re: interface blocks
  • From: Ian Chivers
• NLEQ1 and open source Fortran
  • From: rlopneg
• Re: interface blocks
  • From: kfitch42
• Re: little isprime challenge
  • From: e p chandler
• Re: interface blocks
  • From: beliavsky
• Re: TYPE *, SYSTEM executable statement
  • From: beliavsky
• Re: TYPE *, SYSTEM executable statement
  • From: Richard E Maine
• Re: TYPE *, SYSTEM executable statement
  • From: beliavsky
• Re: TYPE *, SYSTEM executable statement
  • From: Steve Lionel
• Re: interface blocks
  • From: Richard E Maine
• Re: interface blocks
  • From: James Giles
• Re: interface blocks
  • From: Lynn McGuire
• TYPE *, SYSTEM executable statement
  • From: Andy Mai
• ANNOUNCE: SNG, Fortran getopt_long()-ish capability
  • From: Charlie Zender
• Re: little isprime challenge
  • From: Brooks Moses
• Re: Fortran (Linux pgf90)
  • From: Greg Lindahl
• Re: little isprime challenge
  • From: Brooks Moses
• Re: Acceptable Pack args
  • From: David Frank
• Re: Acceptable Pack args
  • From: Rich Townsend
• Re: Acceptable Pack args
  • From: David Frank
• Re: Acceptable Pack args
  • From: Steve Lionel
• Re: interface blocks
  • From: Richard E Maine
• Re: Acceptable Pack args
  • From: glen herrmannsfeldt
• Re: interface blocks
  • From: Dick Hendrickson
• java -> fortran bindings
  • From: William Z.
• Re: Acceptable Pack args
  • From: David Frank
• interface blocks
  • From: Lynn McGuire
• Re: Acceptable Pack args
  • From: Dick Hendrickson
• Re: Acceptable Pack args
  • From: David Frank
• Re: ANN: f95totex: A Fortran-to-LaTeX prettyprinter (of sorts)
  • From: Madhusudan Singh
• Re: Acceptable Pack args
  • From: Rich Townsend
• Re: Acceptable Pack args
  • From: Dick Hendrickson
• Re: little isprime challenge
  • From: glen herrmannsfeldt
• Re: Fortran (Linux pgf90)
  • From: glen herrmannsfeldt
• Re: comparing chars stored in integers to single character strings
  • From: Jugoslav Dujic
• Fortran (Linux pgf90)
  • From: David Rudack
• Re: little isprime challenge
  • From: e p chandler
• Re: selected integer kind
  • From: Jugoslav Dujic
• Re: selected integer kind
  • From: John Mansell
• Re: selected integer kind
  • From: Bart Vandewoestyne
• Re: little isprime challenge
  • From: e p chandler
• Re: little isprime challenge
  • From: e p chandler
• Re: selected integer kind
  • From: Arjen Markus
• Re: selected integer kind
  • From: Bart Vandewoestyne
• Re: little isprime challenge
  • From: Bart Vandewoestyne
• Re: selected integer kind
  • From: Arjen Markus
• Re: selected integer kind
  • From: Bart Vandewoestyne
• Re: little isprime challenge
  • From: Bart Vandewoestyne
• Re: little isprime challenge
  • From: Janne Blomqvist
• Re: selected integer kind
  • From: Michel OLAGNON
• Re: selected integer kind
  • From: Phillip Helbig---remove CLOTHES to reply
• Re: selected integer kind
  • From: James Van Buskirk
• Re: little isprime challenge
  • From: Bart Vandewoestyne
• selected integer kind
  • From: Bart Vandewoestyne
• Re: little isprime challenge
  • From: Michel OLAGNON
• Re: little isprime challenge
  • From: Bart Vandewoestyne
• Re: little isprime challenge
  • From: Brooks Moses
• Re: little isprime challenge
  • From: e p chandler
• Re: asp .net for fortran
  • From: vesper_carmen
• Re: comparing chars stored in integers to single character strings
  • From: Gordon Sande
• Re: comparing chars stored in integers to single character strings
  • From: James Van Buskirk
• Re: little isprime challenge
  • From: glen herrmannsfeldt
• Re: comparing chars stored in integers to single character strings
  • From: Gordon Sande
• Re: comparing chars stored in integers to single character strings
  • From: Lynn McGuire
• Re: ANN: f95totex: A Fortran-to-LaTeX prettyprinter (of sorts)
  • From: Brooks Moses
• Re: forrtl warning (402)
  • From: Bart Vandewoestyne
• Re: little isprime challenge
  • From: Brooks Moses
• Re: little isprime challenge
  • From: Bart Vandewoestyne
• Re: comparing chars stored in integers to single character strings
  • From: Lynn McGuire
• Re: little isprime challenge
  • From: Brooks Moses
• Re: little isprime challenge
  • From: Bart Vandewoestyne
• Re: comparing chars stored in integers to single character strings
  • From: glen herrmannsfeldt
• Re: comparing chars stored in integers to single character strings
  • From: glen herrmannsfeldt
• Re: little isprime challenge
  • From: Bart Vandewoestyne
• Re: comparing chars stored in integers to single character strings
  • From: Gordon Sande
• Re: comparing chars stored in integers to single character strings
  • From: Lynn McGuire
• Re: little isprime challenge
  • From: Rich Townsend
• Re: little isprime challenge
  • From: Glenn Forney
• Re: little isprime challenge
  • From: Brooks Moses
• Re: comparing chars stored in integers to single character strings
  • From: Lynn McGuire
• Re: little isprime challenge
  • From: Brooks Moses
• help regarding randlib
  • From: student
• Re: help regarding installing randlib
  • From: bwb
• Re: little isprime challenge
  • From: Rich Townsend
• Re: little isprime challenge
  • From: Greg Lindahl
• Re: Acceptable Pack args
  • From: glen herrmannsfeldt
• Re: Undefined array elements
  • From: Dr Ivan D. Reid
• Re: little isprime challenge
  • From: Bart Vandewoestyne
• Re: help regarding installing randlib
  • From: student
• Re: little isprime challenge
  • From: Bart Vandewoestyne
• Re: Acceptable Pack args
  • From: Rich Townsend
• Re: little isprime challenge
  • From: Joost
• Re: little isprime challenge
  • From: Rich Townsend
• Re: Acceptable Pack args
  • From: David Frank
• Re: little isprime challenge
  • From: Joost
• Re: Acceptable Pack args
  • From: Rich Townsend
• Re: asp .net for fortran
  • From: apm
• Re: Acceptable Pack args
  • From: David Frank
• Re: little isprime challenge
  • From: Rich Townsend
• Re: ANN: f95totex: A Fortran-to-LaTeX prettyprinter (of sorts)
  • From: Madhusudan Singh
• Re: little isprime challenge
  • From: James Parsly
• Re: maximum array size for g77 compiler
  • From: e p chandler
• Re: Acceptable Pack args
  • From: Rich Townsend
• Re: forrtl warning (402)
  • From: Steve Lionel
• Re: Acceptable Pack args
  • From: David Frank
• Re: Acceptable Pack args
  • From: Rich Townsend
• Re: help regarding installing randlib
  • From: Dr Ivan D. Reid
• ANN: pilib: Platform/Compiler independend RTL
  • From: Martin Hierholzer
• Re: Acceptable Pack args
  • From: David Frank
• Re: Acceptable Pack args
  • From: Joost
• Acceptable Pack args
  • From: David Frank
• Re: help regarding installing randlib
  • From: Jugoslav Dujic
• Re: help regarding installing randlib
  • From: student
• Re: help regarding installing randlib
  • From: student
• Re: maximum array size for g77 compiler
  • From: Janne Blomqvist
• Re: little isprime challenge
  • From: Bart Vandewoestyne
• Re: little isprime challenge
  • From: Bart Vandewoestyne
• Re: little isprime challenge
  • From: Bart Vandewoestyne
• Re: little isprime challenge
  • From: Arjen Markus
• ANN: f95totex: A Fortran-to-LaTeX prettyprinter (of sorts)
  • From: Brooks Moses
• Re: comparing chars stored in integers to single character strings
  • From: Richard Maine
• Re: comparing chars stored in integers to single character strings
  • From: robin
• Re: dlls remembering allocatable arrays
  • From: Bruce M
• Re: dlls remembering allocatable arrays
  • From: Bruce M
• Re: little isprime challenge
  • From: James Van Buskirk
• Re: little isprime challenge
  • From: e p chandler
• Re: comparing chars stored in integers to single character strings
  • From: Richard Maine
• Re: comparing chars stored in integers to single character strings
  • From: glen herrmannsfeldt
• Re: maximum array size for g77 compiler
  • From: e p chandler
• Re: little isprime challenge
  • From: Steven G. Kargl
• Re: help regarding installing randlib
  • From: glen herrmannsfeldt
• Re: comparing chars stored in integers to single character strings
  • From: Lynn McGuire
• little isprime challenge
  • From: Bart Vandewoestyne
• Re: comparing chars stored in integers to single character strings
  • From: glen herrmannsfeldt
• Re: comparing chars stored in integers to single character strings
  • From: Lynn McGuire
• Re: comparing chars stored in integers to single character strings
  • From: Lynn McGuire
• Re: forrtl warning (402)
  • From: James Van Buskirk
• Re: comparing chars stored in integers to single character strings
  • From: Richard E Maine
• Re: comparing chars stored in integers to single character strings
  • From: James Giles
• comparing chars stored in integers to single character strings
  • From: Lynn McGuire
• Re: help regarding installing randlib
  • From: Richard E Maine
• Re: forrtl warning (402)
  • From: Bart Vandewoestyne
• help regarding installing randlib
  • From: student
• Re: Undefined array elements
  • From: Gordon Sande
• Re: Subroutine question
  • From: glen herrmannsfeldt
• Re: forrtl warning (402)
  • From: Richard E Maine
• Re: Undefined array elements
  • From: glen herrmannsfeldt
• Re: O/T: Wierd FTP interrupts (now memory errors)
  • From: Random Programmer
• Re: forrtl warning (402)
  • From: Bart Vandewoestyne
• Re: O/T: Wierd FTP interrupts - please help
  • From: Random Programmer
• Re: O/T: Wierd FTP interrupts - please help
  • From: Random Programmer
• Re: forrtl warning (402)
  • From: Bart Vandewoestyne
• Re: O/T: Wierd FTP interrupts - please help
  • From: Random Programmer
• Re: O/T: Wierd FTP interrupts - please help
  • From: Random Programmer
• Re: is this program ok?
  • From: Bart Vandewoestyne
• Re: Ways to debug Monte Carlo Code ?
  • From: Dr Ivan D. Reid
• Re: Undefined array elements
  • From: Gordon Sande
• Re: O/T: Wierd FTP interrupts - please help
  • From: [JvO]
• Re: is this program ok?
  • From: [JvO]
• Re: Undefined array elements
  • From: Ian Chivers
• Re: Ways to debug Monte Carlo Code ?
  • From: Steve Lionel
• Re: forrtl warning (402)
  • From: Steve Lionel
• Re: Ways to debug Monte Carlo Code ?
  • From: Nachiket Gokhale
• Re: Ways to debug Monte Carlo Code ?
  • From: Rich Townsend
• Re: maximum array size for g77 compiler
  • From: Gordon Sande
• Re: Undefined array elements
  • From: Gordon Sande
• Re: Final Reduce_Blanks function?
  • From: Herman D . Knoble
• Re: maximum array size for g77 compiler
  • From: Jan Vorbrüggen
• Re: forrtl warning (402)
  • From: Jan Vorbrüggen
• Re: Undefined array elements
  • From: Jan Vorbrüggen
• Re: Subroutine question
  • From: Jan Vorbrüggen
• Re: some fortran 77 language question
  • From: Jan Vorbrüggen
• Re: How safe is intellectual property in compiled binaries?
  • From: Jan Vorbrüggen
• Re: maximum array size for g77 compiler
  • From: Tim Prince
• Re: O/T: Wierd FTP interrupts - please help
  • From: Jan Vorbrüggen
• Re: Undefined array elements
  • From: Arjen Markus
• Re: Ways to debug Monte Carlo Code ?
  • From: Arjen Markus
• Re: forrtl warning (402)
  • From: Jugoslav Dujic
• Re: forrtl warning (402)
  • From: John Mansell
• Ways to debug Monte Carlo Code ?
  • From: Klemens Barfus
• maximum array size for g77 compiler
  • From: stefan
• forrtl warning (402)
  • From: Bart Vandewoestyne
• RE: Subroutine question
  • From: meek
• Re: Undefined array elements
  • From: John C. Bollinger
• Re: O/T: Wierd FTP interrupts - please help
  • From: dooleys
• Re: dlls remembering allocatable arrays
  • From: Bruce M
• Re: dlls remembering allocatable arrays
  • From: Bruce M
• Re: How safe is intellectual property in compiled binaries?
  • From: Rich Townsend
• Re: How safe is intellectual property in compiled binaries?
  • From: Jim Cornwall
• Re: O/T: Wierd FTP interrupts - please help
  • From: Random Programmer
• Re: ifort to detect undefined variables?
  • From: glen herrmannsfeldt
• Re: O/T: Wierd FTP interrupts - please help
  • From: James Van Buskirk
• Re: How safe is intellectual property in compiled binaries?
  • From: Richard E Maine
• Re: How safe is intellectual property in compiled binaries?
  • From: Dick Hendrickson
• Re: How safe is intellectual property in compiled binaries?
  • From: James Van Buskirk
• Re: [f77] wrong length of a string containing German umlauts
  • From: Michael Prager
• Re: How safe is intellectual property in compiled binaries?
  • From: glen herrmannsfeldt
• Re: some fortran 77 language question
  • From: Duane Bozarth
• Re: some fortran 77 language question
  • From: Richard E Maine
• Re: How safe is intellectual property in compiled binaries?
  • From: Random Programmer
• Re: looking for Plotter Subroutines
  • From: Brian O
• Re: Any other freely available compilers?
  • From: Richard E Maine
• Re: How safe is intellectual property in compiled binaries?
  • From: Richard E Maine
• Re: some fortran 77 language question
  • From: Duane Bozarth
• Re: looking for Plotter Subroutines
  • From: Ken Plotkin
• Re: Subroutine question
  • From: Richard E Maine
• Re: some fortran 77 language question
  • From: Ken Plotkin
• Re: How safe is intellectual property in compiled binaries?
  • From: Duane Bozarth
• is this program ok?
  • From: Bart Vandewoestyne
• Re: How safe is intellectual property in compiled binaries?
  • From: Random Programmer
• Re: O/T: Wierd FTP interrupts - please help
  • From: Random Programmer
• Re: looking for Plotter Subroutines
  • From: Arjen Markus
• Re: ifort to detect undefined variables?
  • From: Gordon Sande
• Re: O/T: Wierd FTP interrupts - please help
  • From: Gordon Sande
• looking for Plotter Subroutines
  • From: Wilfried Philippi
• Re: Subroutine question
  • From: glen herrmannsfeldt
• Re: How safe is intellectual property in compiled binaries?
  • From: glen herrmannsfeldt
• Re: Question about BLAS sgemm function
  • From: glen herrmannsfeldt
• Re: ifort to detect undefined variables?
  • From: glen herrmannsfeldt
• Re: some fortran 77 language question
  • From: glen herrmannsfeldt
• Re: Undefined array elements
  • From: glen herrmannsfeldt
• Re: Bypassing SSH/SCP logins with Fortran/Linux
  • From: Janne Blomqvist
• Re: Any other freely available compilers?
  • From: Brooks Moses
• Re: O/T: Wierd FTP interrupts - please help
  • From: Random Programmer
• Re: O/T: Wierd FTP interrupts - please help
  • From: Random Programmer
• Re: O/T: Wierd FTP interrupts - please help
  • From: Random Programmer
• O/T: Wierd FTP interrupts - please help
  • From: Random Programmer
• Re: Any other freely available compilers?
  • From: Rich Townsend
• Re: endian test
  • From: John Harper
• Re: Fortran 77 vs Fortran 90/95
  • From: jussij
• Re: asp .net for fortran
  • From: Helge Avlesen
• Re: asp .net for fortran
  • From: Madhusudan Singh
• Re: How safe is intellectual property in compiled binaries?
  • From: Random Programmer
• Re: How safe is intellectual property in compiled binaries?
  • From: Richard Maine
• Re: Bypassing SSH/SCP logins with Fortran/Linux
  • From: Rich Townsend
• Re: Bypassing SSH/SCP logins with Fortran/Linux
  • From: David Frank
• Re: Bypassing SSH/SCP logins with Fortran/Linux
  • From: Janne Blomqvist
• Re: Bypassing SSH/SCP logins with Fortran/Linux
  • From: Janne Blomqvist
• Re: How safe is intellectual property in compiled binaries?
  • From: sali0090
• asp .net for fortran
  • From: vesper_carmen
• Re: What has experience with Intel Fortran 9.0 been like?
  • From: Rich Townsend
• Re: What has experience with Intel Fortran 9.0 been like?
  • From: kia
• Re: [OT] Re: fcomp ?
  • From: Dr Ivan D. Reid
• Re: [f77] wrong length of a string containing German umlauts
  • From: Richard Maine
• Re: dlls remembering allocatable arrays
  • From: Jugoslav Dujic
• Re: Any other freely available compilers?
  • From: Rich Townsend
• Re: Any other freely available compilers?
  • From: kia
• Re: [f77] wrong length of a string containing German umlauts
  • From: Hani A. Ibrahim
• Re: Reduce Blanks continued
  • From: David Frank
• Re: Fortran 77 vs Fortran 90/95
  • From: robin
• Re: Fortran 77 vs Fortran 90/95
  • From: robin
• Re: Any other freely available compilers?
  • From: Alex Gibson
• Re: Any other freely available compilers?
  • From: Kevin G. Rhoads
• Re: Reduce Blanks continued
  • From: David Frank
• Re: [f77] wrong length of a string containing German umlauts
  • From: Colin Watters
• Re: some fortran 77 language question
  • From: Richard Maine
• Re: Bypassing SSH/SCP logins with Fortran/Linux
  • From: Random Programmer
• Re: Reduce Blanks continued
  • From: Rich Townsend
• Re: some fortran 77 language question
  • From: Ken Plotkin
• Re: Reduce Blanks continued
  • From: James Van Buskirk
• Re: Reduce Blanks continued
  • From: Rich Townsend
• Re: Bypassing SSH/SCP logins with Fortran/Linux
  • From: Rich Townsend
• Re: Bypassing SSH/SCP logins with Fortran/Linux
  • From: Richard E Maine
• DVF: dlls remembering allocatable arrays
  • From: Bruce M
• Re: [f77] wrong length of a string containing German umlauts
  • From: James Giles
• Re: Reduce Blanks continued
  • From: James Giles
• [OT] Re: fcomp ?
  • From: Bart Vandewoestyne
• Re: Reduce Blanks continued
  • From: David Frank
• Re: Reduce Blanks continued
  • From: [JvO]
• Re: Any other freely available compilers?
  • From: Bart Vandewoestyne
• Re: Any other freely available compilers?
  • From: Bart Vandewoestyne
• Bypassing SSH/SCP logins with Fortran/Linux
  • From: Random Programmer
• Re: Any other freely available compilers?
  • From: Bart Vandewoestyne
• Re: Any other freely available compilers?
  • From: Bart Vandewoestyne
• [f77] wrong length of a string containing German umlauts
  • From: Hani A. Ibrahim
• Re: Reduce Blanks continued
  • From: James Giles
• Re: fcomp ?
  • From: Dr Ivan D. Reid
• Re: Any other freely available compilers?
  • From: Rich Townsend
• Re: Any other freely available compilers?
  • From: Kevin G. Rhoads
• Re: Any other freely available compilers?
  • From: Herman D . Knoble
• Re: Fortran 77 vs Fortran 90/95
  • From: blmblm
• Re: Any other freely available compilers?
  • From: beliavsky
• Re: Any other freely available compilers?
  • From: Duane Bozarth
• Any other freely available compilers?
  • From: Bart Vandewoestyne
• Re: IBM AIX Fortran v7.1.1
  • From: Bart Vandewoestyne
• Re: Undefined array elements
  • From: Herman D . Knoble
• IBM AIX Fortran v7.1.1
  • From: HajoEhlers
• Re: fcomp ?
  • From: Bart Vandewoestyne
• Re: fcomp ?
  • From: Pierre Asselin
• Re: some fortran 77 language question
  • From: Richard E Maine
• Re: some fortran 77 language question
  • From: Rich Townsend
• Re: Undefined array elements
  • From: Rich Townsend
• Re: fcomp ?
  • From: Richard E Maine
• Re: Undefined array elements
  • From: Herman D . Knoble
• Re: some fortran 77 language question
  • From: Richard E Maine
• Undefined array elements
  • From: omorr
• Re: some fortran 77 language question
  • From: beliavsky
• Re: some fortran 77 language question
  • From: Rich Townsend
• Re: some fortran 77 language question
  • From: Tim Prince
• some fortran 77 language question
  • From: consideration
• Re: Reduce Blanks continued
  • From: David Frank
• Re: Reduce Blanks continued
  • From: David Frank
• Re: fcomp ?
  • From: Bart Vandewoestyne
• Re: fcomp ?
  • From: David Frank
• fcomp ?
  • From: Bart Vandewoestyne
• Re: CVF: run-time error
  • From: bv
• Re: Reduce Blanks continued
  • From: James Giles
• Re: interface block and kind parameter
  • From: gtg531e
• Re: Count Items function
  • From: Rich Townsend
• Re: Count Items function
  • From: David Frank
• Re: Count Items function
  • From: Rich Townsend
• Re: Count Items function
  • From: Rich Townsend
• Re: Intel Fortran licensing issues
  • From: Mark Mackey
• Re: Reduce Blanks continued
  • From: David Frank
• Re: Count Items function
  • From: David Frank
• Re: Count Items function
  • From: David Frank
• Re: Intel Fortran licensing issues
  • From: Brooks Moses
• Re: Intel Fortran licensing issues
  • From: Brooks Moses
• Re: interface block and kind parameter
  • From: James Van Buskirk
• interface block and kind parameter
  • From: gtg531e
• Re: Count Items function
  • From: Rich Townsend
• Re: Intel Fortran licensing issues
  • From: Steve Lionel
• Re: Reduce Blanks continued
  • From: James Giles
• Re: Count Items function
  • From: David Frank
• Re: 'arbitrary precision' arithmetic in Fortran
  • From: Herman D . Knoble
• Re: vim syntax highlighting
  • From: Kamaraju Kusumanchi
• Re: Count Items function
  • From: Rich Townsend
• Re: 'arbitrary precision' arithmetic in Fortran
  • From: beliavsky
• Re: Intel Fortran licensing issues
  • From: Tim Prince
• Re: 'arbitrary precision' arithmetic in Fortran
  • From: Joost
• Re: 'arbitrary precision' arithmetic in Fortran
  • From: beliavsky
• Re: vim syntax highlighting
  • From: Bart Vandewoestyne
• 'arbitrary precision' arithmetic in Fortran
  • From: Jeremy Watts
• Re: Count Items function
  • From: David Frank
• Re: Count Items function
  • From: Arjen Markus
• Re: Count Items function
  • From: David Frank
• Intel Fortran licensing issues
  • From: Mark Mackey
• Re: Count Items function
  • From: Arjen Markus
• Re: Count Items function
  • From: David Frank
• Count Items function
  • From: David Frank
• Re: Jagged arrays
  • From: David Frank
• Re: Reduce Blanks continued
  • From: David Frank
• Re: CVF: run-time error
  • From: Abdul Qat
• Re: Parsing challenge to reduce blanks
  • From: David Frank
• Re: CVF: run-time error
  • From: bv
• Re: Parsing challenge to reduce blanks
  • From: James Giles
• Re: Parsing challenge to reduce blanks
  • From: James Giles
• Re: run-time error
  • From: Colin Watters
• Re: write checks challenge
  • From: Dick Hendrickson
• Re: Fortran 77 vs Fortran 90/95
  • From: Kevin G. Rhoads
• Re: Fortran 77 vs Fortran 90/95
  • From: Kevin G. Rhoads
• Re: number of columns
  • From: Rich Townsend
• Re: number of columns
  • From: beliavsky
• Re: vim syntax highlighting
  • From: Kamaraju Kusumanchi
• Re: CVF: run-time error
  • From: Abdul Qat
• Re: vim syntax highlighting
  • From: Bart Vandewoestyne
• Re: vim syntax highlighting
  • From: Kamaraju Kusumanchi
• Re: O/T: Career advice
  • From: Carlie J. Coats
• Re: vim syntax highlighting
  • From: John Mansell
• Re: Parsing challenge to reduce blanks
  • From: Herman D . Knoble
• Re: Fortran on VMS
  • From: Steve Lionel
• Re: Checking for IEEE Infinity
  • From: Kevin G. Rhoads
• Re: number of columns
  • From: Rich Townsend
• Re: Parsing challenge to reduce blanks
  • From: David Frank
• vim syntax highlighting
  • From: Bart Vandewoestyne
• Re: number of columns
  • From: Herman D . Knoble
• Re: Fortran on VMS
  • From: Volker Englisch
• Re: Fortran on VMS
  • From: Ian Bush
• Re: write checks challenge
  • From: [JvO]
• Fortran on VMS
  • From: Volker Englisch
• Re: Checking for IEEE Infinity
  • From: Arjen Markus
• Re: Checking for IEEE Infinity
  • From: Abdul Qat
• Re: Checking for IEEE Infinity
  • From: Abdul Qat
• Re: CVF: run-time error
  • From: aardpig@xxxxxxxxxxx
• Re: CVF: run-time error
  • From: bv
• Re: write checks challenge
  • From: Clive Page
• Re: Which function should be called?
  • From: Steve Lionel
• Re: Which function should be called?
  • From: Ken Fairfield
• Re: Which function should be called?
  • From: Steve Lionel
• Re: Checking for IEEE Infinity
  • From: Kevin G. Rhoads
• Re: Checking for IEEE Infinity
  • From: Arjen Markus
• Re: External subroutines slow down
  • From: Matthias Möller
• Re: External subroutines slow down
  • From: Jan Vorbrüggen
• External subroutines slow down
  • From: Matthias Möller
• Re: Checking for IEEE Infinity
  • From: Jugoslav Dujic
• Re: number of columns
  • From: Rich Townsend
• Re: number of columns
  • From: Gary L. Scott
• Re: write checks challenge
  • From: Walt Brainerd
• Re: ifort to detect undefined variables?
  • From: Gordon Sande
• Re: write checks challenge
  • From: David Frank
• Jagged arrays
  • From: David Frank
• Re: ifort to detect undefined variables?
  • From: Dave Thompson
• Re: Question about BLAS sgemm function
  • From: Dave Thompson
• Re: write checks challenge
  • From: Rich Townsend
• Re: write checks challenge
  • From: David Frank
• Re: write checks challenge
  • From: Rich Townsend
• Re: write checks challenge
  • From: Walt Brainerd
• Re: write checks challenge
  • From: David Frank
• Re: write checks challenge
  • From: Richard Maine
• Re: write checks challenge
  • From: Walter Spector
• Re: Get name of executable
  • From: Mark Mackey
• Re: How safe is intellectual property in compiled binaries?
  • From: Harold Stevens
• Re: How safe is intellectual property in compiled binaries?
  • From: Dr Ivan D. Reid
• Re: Fortran 77 vs Fortran 90/95
  • From: Dr Ivan D. Reid
• Re: write checks challenge
  • From: David Frank
• Re: write checks challenge
  • From: Walt Brainerd
• Re: write checks challenge
  • From: David Frank
• Re: write checks challenge
  • From: David Frank
• Re: write checks challenge
  • From: Walt Brainerd
• Re: Flux through a boundary
  • From: Wavemaker
• Re: Flux through a boundary
  • From: Gordo
• Re: write checks challenge
  • From: David Frank
• Re: write checks challenge
  • From: David Frank
• Re: CVF: run-time error
  • From: Abdul Qat
• Re: Which function should be called?
  • From: Abdul Qat
• Re: CVF: run-time error
  • From: bv
• Re: CVF: run-time error
  • From: e p chandler
• Re: CVF: run-time error
  • From: Duane Bozarth
• CVF: run-time error
  • From: bv
• Re: DVF: Checking for IEEE Infinity
  • From: James Giles
• Re: DVF: Checking for IEEE Infinity
  • From: Richard E Maine
• DVF: Checking for IEEE Infinity
  • From: Max
• Re: Which function should be called?
  • From: Steven G. Kargl
• Re: Which function should be called?
  • From: Richard E Maine
• Which function should be called?
  • From: Thomas Koenig
• Re: write checks challenge
  • From: [JvO]
• Re: Fortran 77 vs Fortran 90/95
  • From: Bart Vandewoestyne
• Flux through a boundary
  • From: Wavemaker
• Re: write checks challenge
  • From: David Frank
• Re: write checks challenge
  • From: David Frank
• Re: PGF90-S-0087-Non-constant expression where constant expression required
  • From: Janne Blomqvist
• Re: Fortran 77 vs Fortran 90/95
  • From: Jan Vorbrüggen
• Re: Career advice
  • From: Abdul Qat
• Re: Career advice
  • From: Random Programmer
• Re: Fortran 77 vs Fortran 90/95
  • From: Scott Moore
• Re: Parsing challenge to reduce blanks
  • From: Rich Townsend
• Re: Parsing challenge to reduce blanks
  • From: James Giles
• Re: Parsing challenge to reduce blanks
  • From: James Giles
• Re: PGF90-S-0087-Non-constant expression where constant expression required
  • From: Paul Van Delst
• Re: Parsing challenge to reduce blanks
  • From: James Giles
• Re: Career advice
  • From: Brooks Moses
• Re: Parsing challenge to reduce blanks
  • From: David Frank
• Re: Parsing challenge to reduce blanks
  • From: Rich Townsend
• Re: PGF90-S-0087-Non-constant expression where constant expression required
  • From: Richard E Maine
• Re: -Qpath
  • From: FX
• Re: Parsing challenge to reduce blanks
  • From: David Frank
• PGF90-S-0087-Non-constant expression where constant expression required
  • From: Bas Braams
• Re: Parsing challenge to reduce blanks
  • From: David Frank
• Re: How safe is intellectual property in compiled binaries?
  • From: Kevin G. Rhoads
• Re: How safe is intellectual property in compiled binaries?
  • From: Kevin G. Rhoads
• Re: -Qpath
  • From: Bart Vandewoestyne
• Re: -Qpath
  • From: Janne Blomqvist
• Re: Parsing challenge to reduce blanks
  • From: James Giles
• Re: Parsing challenge to reduce blanks
  • From: Rich Townsend
• Re: Parsing challenge to reduce blanks
  • From: David Frank
• Re: Parsing challenge to reduce blanks
  • From: James Giles
• Re: Parsing challenge to reduce blanks
  • From: Rich Townsend
• Re: Using gfortran on mac to create dylib
  • From: Madhusudan Singh
• Re: Get name of executable
  • From: Kevin G. Rhoads
• Re: Parsing challenge to reduce blanks
  • From: Herman D . Knoble
• Re: Career advice
  • From: apm
• Re: Fortran 77 vs Fortran 90/95
  • From: Ron Shepard
• Re: write checks challenge
  • From: Gordon Sande
• Re: Parsing challenge to reduce blanks
  • From: David Frank
• Re: O/T: Career advice
  • From: Kevin G. Rhoads
• Re: write checks challenge
  • From: Dick Russell
• Re: -Qpath
  • From: Bart Vandewoestyne
• Re: Parsing challenge to reduce blanks
  • From: David Frank
• -Qpath
  • From: Bart Vandewoestyne
• Re: Get name of executable
  • From: Erik Edelmann
• Re: Parsing challenge to reduce blanks
  • From: David Frank
• Get name of executable
  • From: Mark Mackey
• Re: Parsing challenge to reduce blanks
  • From: David Frank
• Re: O/T: Career advice
  • From: Brooks Moses
• Re: write checks challenge
  • From: e p chandler
• Re: Using gfortran on mac to create dylib
  • From: peterp
• Re: Subroutine question
  • From: mcalhoun
• Re: ifort to detect undefined variables?
  • From: sarah
• Re: Parsing challenge to reduce blanks
  • From: James Giles
• Re: Random number generators
  • From: FJRA
• Re: Parsing challenge to reduce blanks
  • From: James Giles
• Re: write checks challenge
  • From: Rich Townsend
• Re: write checks challenge
  • From: bvoh
• Re: write checks challenge
  • From: Dick Russell
• Re: O/T: Career advice
  • From: Duane Bozarth
• Re: Fortran 77 vs Fortran 90/95
  • From: Gordon Sande
• Re: O/T: Career advice
  • From: Jim Cornwall
• Re: O/T: Career advice
  • From: Random Programmer
• Re: O/T: Career advice
  • From: Kevin G. Rhoads
• Re: O/T: Career advice
  • From: Random Programmer
• Re: O/T: Career advice
  • From: Duane Bozarth
• Re: Fortran 77 vs Fortran 90/95
  • From: Gareth Owen
• Re: Fortran 77 vs Fortran 90/95
  • From: David Flower
• Re: O/T: Career advice
  • From: Richard E Maine
• Re: O/T: Career advice
  • From: Richard E Maine
• Re: O/T: Career advice
  • From: Richard E Maine
• Re: O/T: Career advice
  • From: Kevin G. Rhoads
• Re: O/T: Career advice
  • From: Kevin G. Rhoads
• Re: O/T: Career advice
  • From: Rich Townsend
• Re: O/T: Career advice
  • From: Kevin G. Rhoads
• Re: O/T: Career advice
  • From: Richard E Maine
• Re: Random number generators
  • From: Duane Bozarth
• Re: Random number generators
  • From: FJRA
• write checks challenge
  • From: David Frank
• Re: O/T: Career advice
  • From: Duane Bozarth
• Re: O/T: Career advice
  • From: Duane Bozarth
• Re: O/T: Career advice
  • From: Duane Bozarth
• Re: O/T: Career advice
  • From: Random Programmer
• Re: O/T: Career advice
  • From: Random Programmer
• Re: O/T: Career advice
  • From: Phillip Helbig---remove CLOTHES to reply
• Re: Random number generators
  • From: Phillip Helbig---remove CLOTHES to reply
• Re: Random number generators
  • From: Phillip Helbig---remove CLOTHES to reply
• Re: O/T: Career advice
  • From: Kevin G. Rhoads
• Re: O/T: Career advice
  • From: Kevin G. Rhoads
• Re: O/T: Career advice
  • From: Kevin G. Rhoads
• Re: O/T: Career advice
  • From: Gordon Sande
• Re: O/T: Career advice
  • From: Gordon Sande
• Re: O/T: Career advice
  • From: Gib Bogle
• Re: O/T: Career advice
  • From: p . kinsler
• Re: Fortran 77 vs Fortran 90/95
  • From: Dr Ivan D. Reid
• Re: How safe is intellectual property in compiled binaries?
  • From: FX
• Re: Fortran Xml library
  • From: Arjen Markus
• Re: O/T: Career advice
  • From: Random Programmer
• Re: O/T: Career advice
  • From: Gib Bogle
• Re: O/T: Career advice
  • From: Brooks Moses
• Re: O/T: Career advice
  • From: Rich Townsend
• Re: O/T: Career advice
  • From: Random Programmer
• Re: O/T: Career advice
  • From: Duane Bozarth
• Re: O/T: Career advice
  • From: Random Programmer
• Re: O/T: Career advice
  • From: Duane Bozarth
• Re: O/T: Career advice
  • From: Random Programmer
• Re: O/T: Career advice
  • From: Random Programmer
• Re: O/T: Career advice
  • From: Thomas Koenig
• Re: O/T: Career advice
  • From: e p chandler
• Re: O/T: Career advice
  • From: Richard E Maine
• Re: BEST ROUTINE
  • From: David Frank
• O/T: Career advice
  • From: Random Programmer
• Re: BEST ROUTINE
  • From: NuclearWizard
• Re: BEST ROUTINE
  • From: NuclearWizard
• Re: BEST ROUTINE
  • From: NuclearWizard
• Re: Random number generators
  • From: Gordon Sande
• Re: Random number generators
  • From: Steven G. Kargl
• Re: BEST ROUTINE
  • From: NuclearWizard
• Re: BEST ROUTINE
  • From: NuclearWizard
• Re: Random number generators
  • From: Random Programmer
• Re: portable 'sizeof' solution
  • From: James Van Buskirk
• Re: Random number generators
  • From: e p chandler
• Re: Random number generators
  • From: Steven G. Kargl
• Re: Random number generators
  • From: Random Programmer
• Re: portable 'sizeof' solution
  • From: David Frank
• Re: portable 'sizeof' solution
  • From: Richard E Maine
• Re: Random number generators
  • From: beliavsky
• Re: Random number generators
  • From: Richard E Maine
• Re: portable 'sizeof' solution
  • From: Steven G. Kargl
• Re: Random number generators
  • From: Rich Townsend
• Re: Random number generators
  • From: Duane Bozarth
• Re: Random number generators
  • From: Random Programmer
• Random number generators
  • From: Random Programmer
• Re: portable 'sizeof' solution
  • From: Rich Townsend
• Re: portable 'sizeof' solution
  • From: Richard E Maine
• Re: Fortran Xml library
  • From: Alexander Poddey
• Re: Fortran Xml library
  • From: beliavsky
• Re: Fortran Xml library
  • From: Rich Townsend
• Re: Subroutine question
  • From: Gordon Sande
• Re: Fortran Xml library
  • From: Alexander Poddey
• Re: BEST ROUTINE
  • From: Herman D . Knoble
• Re: portable 'sizeof' solution
  • From: Arjen Markus
• Re: BEST ROUTINE
  • From: David Frank
• Re: Bug reporting for Intel Fortran
  • From: Gareth Owen
• Re: ifort to detect undefined variables?
  • From: Herman D . Knoble
• Re: How safe is intellectual property in compiled binaries?
  • From: Janne Blomqvist
• Re: portable 'sizeof' solution
  • From: David Frank
• Re: ifort to detect undefined variables?
  • From: Richard Edgar
• Re: ifort to detect undefined variables?
  • From: Peter Browry
• Re: portable 'sizeof' solution
  • From: David Frank
• Re: portable 'sizeof' solution
  • From: David Flower
• Fortran Xml library
  • From: Alexander Poddey
• Re: portable 'sizeof' solution
  • From: Michel OLAGNON
• Re: portable 'sizeof' solution
  • From: Arjen Markus
• portable 'sizeof' solution
  • From: guilhem . bonnefille
• Re: Subroutine question
  • From: glen herrmannsfeldt
• Re: Subroutine question
  • From: bv
• Re: BEST ROUTINE
  • From: NuclearWizard
• Re: ifort to detect undefined variables?
  • From: glen herrmannsfeldt
• Re: Debugging
  • From: Dave Thompson
• Re: ifort to detect undefined variables?
  • From: Richard Maine
• Re: ifort to detect undefined variables?
  • From: glen herrmannsfeldt
• Re: Opening a file with ACTION='READ'
  • From: robert . corbett
• Re: ifort to detect undefined variables?
  • From: Gordon Sande
• Re: How safe is intellectual property in compiled binaries?
  • From: Richard E Maine
• Re: ifort to detect undefined variables?
  • From: Ushnish Basu
• Re: yamq (yet another mystery equation)
  • From: Al
• Re: How safe is intellectual property in compiled binaries?
  • From: Brooks Moses
• Re: BEST ROUTINE
  • From: David Frank
• Re: How safe is intellectual property in compiled binaries?
  • From: Random Programmer
• Re: ifort to detect undefined variables?
  • From: Max
• Re: How safe is intellectual property in compiled binaries?
  • From: Max
• Re: Fortran 77 vs Fortran 90/95
  • From: apm
• Re: How safe is intellectual property in compiled binaries?
  • From: Steven G. Kargl
• Re: How safe is intellectual property in compiled binaries?
  • From: Brooks Moses
• Re: How safe is intellectual property in compiled binaries?
  • From: Max
• Re: How safe is intellectual property in compiled binaries?
  • From: Brooks Moses
• Re: How safe is intellectual property in compiled binaries?
  • From: Max
• Re: How safe is intellectual property in compiled binaries?
  • From: Max
• Re: How safe is intellectual property in compiled binaries?
  • From: Brooks Moses
• Re: How safe is intellectual property in compiled binaries?
  • From: Brooks Moses
• Re: How safe is intellectual property in compiled binaries?
  • From: Brooks Moses
• Re: How safe is intellectual property in compiled binaries?
  • From: Random Programmer
• Re: ifort to detect undefined variables?
  • From: Rich Townsend
• Re: ifort to detect undefined variables?
  • From: Ushnish Basu
• Re: How safe is intellectual property in compiled binaries?
  • From: Random Programmer
• Re: ifort to detect undefined variables?
  • From: e p chandler
• Re: How safe is intellectual property in compiled binaries?
  • From: Random Programmer
• Re: How safe is intellectual property in compiled binaries?
  • From: e p chandler
• Re: How safe is intellectual property in compiled binaries?
  • From: Random Programmer
• Re: BEST ROUTINE
  • From: NuclearWizard
• Re: ifort to detect undefined variables?
  • From: Steve Lionel
• Re: How safe is intellectual property in compiled binaries?
  • From: Rich Townsend
• Re: ifort to detect undefined variables?
  • From: glen herrmannsfeldt
• Re: Fortran 77 vs Fortran 90/95
  • From: Gordon Sande
• Re: How safe is intellectual property in compiled binaries?
  • From: Gordon Sande
• Re: What is the latest version of Intel 9 fortran and c/c++ for linux
  • From: Steve Lionel
• What has experience with Intel Fortran 9.0 been like?
  • From: Max
• Re: How safe is intellectual property in compiled binaries?
  • From: Max
• Re: How safe is intellectual property in compiled binaries?
  • From: Random Programmer
• ifort to detect undefined variables?
  • From: sarah
• Re: How safe is intellectual property in compiled binaries?
  • From: Jim
• Re: What is the latest version of Intel 9 fortran and c/c++ for linux
  • From: Herman D . Knoble
• Re: How safe is intellectual property in compiled binaries?
  • From: Richard E Maine
• Re: yamq (yet another mystery equation)
  • From: Steven G. Kargl
• Re: How safe is intellectual property in compiled binaries?
  • From: Rich Townsend
• Re: How safe is intellectual property in compiled binaries?
  • From: Michael Prager
• Re: Fortran 77 vs Fortran 90/95
  • From: sali0090
• Re: How safe is intellectual property in compiled binaries?
  • From: Random Programmer
• Re: How safe is intellectual property in compiled binaries?
  • From: Richard E Maine
• Re: How safe is intellectual property in compiled binaries?
  • From: Random Programmer
• Re: What is the latest version of Intel 9 fortran and c/c++ for linux
  • From: Steve Lionel
• Re: Fortran 77 vs Fortran 90/95
  • From: Charles Russell
• Re: yamq (yet another mystery equation)
  • From: Al
• Re: yamq (yet another mystery equation)
  • From: Al
• Re: yamq (yet another mystery equation)
  • From: Herman D . Knoble
• Re: How safe is intellectual property in compiled binaries?
  • From: Rich Townsend
• Re: What is the latest version of Intel 9 fortran and c/c++ for linux
  • From: Herman D . Knoble
• Re: How safe is intellectual property in compiled binaries?
  • From: Joost
• How safe is intellectual property in compiled binaries?
  • From: Random Programmer
• yamq (yet another mystery equation)
  • From: Al
• Re: Subroutine question
  • From: Sarah Bergstrom
• Re: Question about BLAS sgemm function
  • From: Jan Vorbrüggen
• Re: What is the latest version of Intel 9 fortran and c/c++ for linux
  • From: Steve Lionel
• Re: Unsupported Intel Fortran compiler for Linux
  • From: Steve Lionel
• Re: What is the latest version of Intel 9 fortran and c/c++ for linux
  • From: Joe Hill
• Re: Fortran 77 vs Fortran 90/95
  • From: Herman D . Knoble
• Re: BEST ROUTINE
  • From: David Frank
• Re: BEST ROUTINE
  • From: David Frank
• BEST ROUTINE
  • From: NuclearWizard
• Re: Opening a file with ACTION='READ'
  • From: [JvO]
• Re: Opening a file with ACTION='READ'
  • From: Richard Maine
• Re: Opening a file with ACTION='READ'
  • From: Dave Weatherall
• Re: Fortran 77 vs Fortran 90/95
  • From: Rich Townsend
• Re: Fortran 77 vs Fortran 90/95
  • From: Richard Maine
• Re: Fortran 77 vs Fortran 90/95
  • From: Richard Maine
• Re: Do loops until HUGE?
  • From: robert . corbett
• Re: Fortran 77 vs Fortran 90/95
  • From: BrownSugar
• Re: What is the latest version of Intel 9 fortran and c/c++ for linux
  • From: Tim Prince
• Re: Do loops until HUGE?
  • From: glen herrmannsfeldt
• Re: Fortran 77 vs Fortran 90/95
  • From: John Halpenny
• Re: Do loops until HUGE?
  • From: robert . corbett
• What is the latest version of Intel 9 fortran and c/c++ for linux
  • From: Joe Hill
• Re: Fortran 77 vs Fortran 90/95
  • From: Louis Krupp
• Re: Question about BLAS sgemm function
  • From: kia
• Re: Fortran 77 vs Fortran 90/95
  • From: Richard Maine
• Re: Fortran 77 vs Fortran 90/95
  • From: kia
• Re: Fortran 77 vs Fortran 90/95
  • From: Brooks Moses
• Re: Fortran 77 vs Fortran 90/95
  • From: Brooks Moses
• Re: Fortran 77 vs Fortran 90/95
  • From: e p chandler
• Re: Fortran 77 vs Fortran 90/95
  • From: Steven G. Kargl
• Re: Fortran 77 vs Fortran 90/95
  • From: crash_zero
• Re: Fortran 77 vs Fortran 90/95
  • From: Rich Townsend
• Re: Fortran 77 vs Fortran 90/95
  • From: BrownSugar
• Re: Fortran 77 vs Fortran 90/95
  • From: Rich Townsend
• Re: Fortran 77 vs Fortran 90/95
  • From: Charles Russell
• Re: Fortran 77 vs Fortran 90/95
  • From: Rich Townsend
• Re: Question about BLAS sgemm function
  • From: Ron Shepard
• Re: Fortran 77 vs Fortran 90/95
  • From: Gordon Sande
• Re: Do loops until HUGE?
  • From: Gordon Sande
• Re: Fortran 77 vs Fortran 90/95
  • From: David Flower
• Re: Do loops until HUGE?
  • From: glen herrmannsfeldt
• Re: Fortran 77 vs Fortran 90/95
  • From: robert . corbett
• Re: Do loops until HUGE?
  • From: robert . corbett
• Re: advance="no" & position="append"
  • From: robert . corbett
• Re: Unsupported Intel Fortran compiler for Linux
  • From: Rich Townsend
• Re: Unsupported Intel Fortran compiler for Linux
  • From: Peter Browry
• Re: Unsupported Intel Fortran compiler for Linux
  • From: Kamaraju Kusumanchi
• Re: Question about BLAS sgemm function
  • From: glen herrmannsfeldt
• Re: Unsupported Intel Fortran compiler for Linux
  • From: Peter Browry
• Re: Question about BLAS sgemm function
  • From: Sandra-24
• Re: Question about BLAS sgemm function
  • From: Richard Maine
• Question about BLAS sgemm function
  • From: Sandra-24
• Re: Unsupported Intel Fortran compiler for Linux
  • From: Tim Prince
• Re: Fortran 77 vs Fortran 90/95
  • From: Thomas Koenig
• Re: Fortran 77 vs Fortran 90/95
  • From: Richard Maine
• Re: Fortran 77 vs Fortran 90/95
  • From: David Flower
• Re: Fortran 77 vs Fortran 90/95
  • From: Duane Bozarth
• Unsupported Intel Fortran compiler for Linux
  • From: Peter Browry
• Re: Fortran 77 vs Fortran 90/95
  • From: Peter Browry
• Re: Fortran 77 vs Fortran 90/95
  • From: Walter Spector
• Re: Fortran 77 vs Fortran 90/95
  • From: Steven G. Kargl
• Re: Fortran 77 vs Fortran 90/95
  • From: Richard Maine
• Re: Fortran 77 vs Fortran 90/95
  • From: Richard Maine
• Re: Subroutine question
  • From: Richard Maine
• Re: Fortran 77 vs Fortran 90/95
  • From: e p chandler
• Re: Fortran 77 vs Fortran 90/95
  • From: crash_zero
• Re: Subroutine question
  • From: glen herrmannsfeldt
• Re: Do loops until HUGE?
  • From: glen herrmannsfeldt
• Re: Fortran 77 vs Fortran 90/95
  • From: Duane Bozarth
• advance="no" & position="append"
  • From: Joost
• Re: Illegal varying string syntax
  • From: David Frank
• Re: Illegal varying string syntax
  • From: David Frank
• Fortran 77 vs Fortran 90/95
  • From: crash_zero
• Re: Subroutine question
  • From: Dan Nagle
• Opening a file with ACTION='READ'
  • From:
• Re: Do loops until HUGE?
  • From: robert . corbett
• Re: Do loops until HUGE?
  • From: robert . corbett
• Re: Do loops until HUGE?
  • From: Richard Maine
• Re: Parsing challenge to reduce blanks
  • From: Gary L. Scott
• Re: Do loops until HUGE?
  • From: James Giles
• Re: Do loops until HUGE?
  • From: Richard E Maine
• Re: Do loops until HUGE?
  • From: James Giles
• Re: Can input file names become variables?
  • From: Dr Ivan D. Reid
• Re: Do loops until HUGE?
  • From: Richard E Maine
• Re: Do loops until HUGE?
  • From: glen herrmannsfeldt
• Re: Do loops until HUGE?
  • From: Richard E Maine
• Re: Parsing challenge to reduce blanks
  • From: David Frank
• Re: Do loops until HUGE?
  • From: Rich Townsend
• Do loops until HUGE?
  • From: Thomas Koenig
• Re: Illegal varying string syntax
  • From: Rich Townsend
• Re: Illegal varying string syntax
  • From: David Frank
• Re: Can input file names become variables?
  • From: Random Programmer
• Re: Subroutine question
  • From: Sarah Bergstrom
• Re: Illegal varying string syntax
  • From: Rich Townsend
• Re: Parsing challenge to reduce blanks
  • From: David Frank
• Re: Illegal varying string syntax
  • From: Rich Townsend
• Re: Can input file names become variables?
  • From: Pierre Asselin
• Re: Parsing challenge -- Replace text
  • From: Rich Townsend
• Re: Can input file names become variables?
  • From: Arjen Markus
• Can input file names become variables?
  • From: Random Programmer
• Re: Illegal varying string syntax
  • From: David Frank
• Illegal varying string syntax
  • From: David Frank
• RE: Subroutine question
  • From: meek
• Re: Parsing challenge -- Replace text
  • From: David Frank
• Re: Parsing challenge to reduce blanks
  • From: David Frank
• Re: Subroutine question
  • From: Arjen Markus
• Re: Parsing challenge to reduce blanks
  • From: FJRA
• Re: Parsing challenge to reduce blanks
  • From: Gary L. Scott
• Re: Subroutine question
  • From: mcalhoun
• Re: Subroutine question
  • From: bv
• Re: Subroutine question
  • From: bv
• Re: Can't Find dll Entry Point: Run-time error (453) -- Please Help!
  • From: Abdul Qat
• Re: Parsing challenge to reduce blanks
  • From: David Frank
• Re: Can't Find dll Entry Point: Run-time error (453) -- Please Help!
  • From: SteveParker007
• Re: Parsing challenge to reduce blanks
  • From: Rich Townsend
• Re: Subroutine question
  • From: Richard E Maine
• Re: Subroutine question
  • From: Dick Russell
• Re: Subroutine question
  • From: apm
• Re: Bug reporting for Intel Fortran
  • From: Steve Lionel
• Re: Parsing challenge -- Replace text
  • From: Rich Townsend
• Re: Subroutine question
  • From: Jugoslav Dujic
• Re: Subroutine question
  • From: Joost
• Re: Parsing challenge to reduce blanks
  • From: David Frank
• Re: Subroutine question
  • From: Random Programmer
• Re: Subroutine question
  • From: Arjen Markus
• Re: Bug reporting for Intel Fortran
  • From: Herman D . Knoble
• Subroutine question
  • From: Random Programmer
• Re: Bug reporting for Intel Fortran
  • From: Arjen Markus
• Bug reporting for Intel Fortran
  • From: Gareth Owen
• Re: Parsing challenge -- Replace text
  • From: David Frank
• RE: Subroutine question
  • From: meek
• Re: Parsing challenge to reduce blanks
  • From: David Frank
• Re: Spaghetti code
  • From: Nestor
• Re: Spaghetti code
  • From: e p chandler
• Re: Spaghetti code
  • From: Nestor
• Re: Spaghetti code
  • From: Nestor
• Re: Can't Find dll Entry Point: Run-time error (453) -- Please Help!
  • From: e p chandler
• Re: Spaghetti code
  • From: e p chandler
• Re: Can't Find dll Entry Point: Run-time error (453) -- Please Help!
  • From: Abdul Qat
• Re: Spaghetti code
  • From: e p chandler
• Re: Spaghetti code
  • From: Pierre Asselin
• Re: Can't Find dll Entry Point: Run-time error (453) -- Please Help!
  • From: e p chandler
• Can't Find dll Entry Point: Run-time error (453) -- Please Help!
  • From: SteveParker007
• Re: Spaghetti code
  • From: Richard E Maine
• Re: Parsing challenge to reduce blanks
  • From: Rich Townsend
• Re: Parsing challenge to reduce blanks
  • From: Duane Bozarth
• Re: Parsing challenge to reduce blanks
  • From: David Frank
• Re: Parsing challenge to reduce blanks
  • From: FJRA
• Re: Parsing challenge to reduce blanks
  • From: e p chandler
• Re: Parsing challenge to reduce blanks
  • From: Rich Townsend
• Re: Parsing challenge to reduce blanks
  • From: David Frank
• Re: Parsing challenge to reduce blanks
  • From: FJRA
• Re: Parsing challenge to reduce blanks
  • From: Herman D . Knoble
• Parsing challenge -- Replace text
  • From: David Frank
• Re: Parsing challenge to reduce blanks
  • From: Rich Townsend
• Re: Parsing challenge to reduce blanks
  • From: David Frank
• Re: Spaghetti code
  • From: Pierre Asselin
• Re: Overloading
  • From: Pierre Asselin
• Re: Parsing challenge to reduce blanks
  • From: David Frank
• Re: Parsing challenge to reduce blanks
  • From: David Frank
• Re: Parsing challenge to reduce blanks
  • From: David Frank
• Re: Parsing challenge to reduce blanks
  • From: John Harper
• Re: Parsing challenge to reduce blanks
  • From: glen herrmannsfeldt
• Re: Overloading
  • From: glen herrmannsfeldt
• Re: Overloading
  • From: apm
• Re: Parsing challenge to reduce blanks
  • From: Gordon Sande
• Re: Parsing challenge to reduce blanks
  • From: James Giles
• Re: Parsing challenge to reduce blanks
  • From: glen herrmannsfeldt
• Re: Parsing challenge to reduce blanks
  • From: James Giles
• Re: Parsing challenge to reduce blanks
  • From: Gary L. Scott
• Re: Parsing challenge to reduce blanks
  • From: Rich Townsend
• Re: Parsing challenge to reduce blanks
  • From: FJRA
• Re: Parsing challenge to reduce blanks
  • From: James Giles
• Re: Parsing challenge to reduce blanks
  • From: James Van Buskirk
• Re: Parsing challenge to reduce blanks
  • From: James Van Buskirk
• Re: Parsing challenge to reduce blanks
  • From: David Frank
• Re: Parsing challenge to reduce blanks
  • From: David Frank
• Re: Parsing challenge to reduce blanks
  • From: James Van Buskirk
• Re: Parsing challenge to reduce blanks
  • From: David Frank
• Re: Parsing challenge to reduce blanks
  • From: David Frank
• Re: Spaghetti code
  • From: Richard E Maine
• Re: Spaghetti code
  • From: James Van Buskirk
• Re: How to generate dynamic formats
  • From: Kamaraju Kusumanchi
• Re: Spaghetti code
  • From: Random Programmer
• Re: Parsing challenge to reduce blanks
  • From: James Van Buskirk
• Re: Parsing challenge to reduce blanks
  • From: James Van Buskirk
• Re: Spaghetti code
  • From: Richard E Maine
• Re: Spaghetti code
  • From: James Van Buskirk
• Re: Spaghetti code
  • From: David Flower
• Re: Spaghetti code
  • From: Paul Van Delst
• Re: Debugging
  • From: jg
• Re: Array indexing algorithm/question
  • From: Paul Van Delst
• Re: Array indexing algorithm/question
  • From: Paul Van Delst
• Spaghetti code
  • From: Random Programmer
• Re: Parsing challenge to reduce blanks
  • From: David Frank
• Re: Parsing challenge to reduce blanks
  • From: FJRA
• Re: Parsing challenge to reduce blanks
  • From: Herman D . Knoble
• Re: Parsing challenge to reduce blanks
  • From: Rich Townsend
• Re: Parsing challenge to reduce blanks
  • From: Herman D . Knoble
• Re: Debugging
  • From: jg
• Re: How to generate dynamic formats
  • From: David Flower
• Re: Parsing challenge to reduce blanks
  • From: David Frank
• Re: Parsing challenge to reduce blanks
  • From: David Frank
• Re: Layhey77 to Compaq
  • From: Simon
• Re: Parsing challenge to reduce blanks
  • From: James Van Buskirk
• Re: Parsing challenge to reduce blanks
  • From: David Frank
• Re: How to generate dynamic formats
  • From: Ron Shepard
• Re: Array indexing algorithm/question
  • From: James Giles
• Re: Array indexing algorithm/question
  • From: James Giles
• Re: How to generate dynamic formats
  • From: Richard Maine
• Re: Array indexing algorithm/question
  • From: Richard Maine
• Re: Array indexing algorithm/question
  • From: glen herrmannsfeldt
• Re: how to define a dummy argument derived-Type array?thanks
  • From: Daipeng1997@xxxxxxxxx
• Re: How to generate dynamic formats
  • From: Gordon Sande
• Re: Array indexing algorithm/question
  • From: Rich Townsend
• Re: How to generate dynamic formats
  • From: bv
• Re: Parsing challenge to reduce blanks
  • From: James Van Buskirk
• Re: Array indexing algorithm/question
  • From: glen herrmannsfeldt
• Re: Parsing challenge to reduce blanks
  • From: Rich Townsend
• Re: Parsing challenge to reduce blanks
  • From: James Giles
• Re: How to generate dynamic formats
  • From: Steven G. Kargl
• Re: Parsing challenge to reduce blanks
  • From: Rich Townsend
• Re: Parsing challenge to reduce blanks
  • From: Rich Townsend
• Re: How to generate dynamic formats
  • From: Kamaraju Kusumanchi
• Re: How to generate dynamic formats
  • From: Richard E Maine
• Re: Parsing challenge to reduce blanks
  • From: FJRA
• How to generate dynamic formats
  • From: Kamaraju Kusumanchi
• Re: Parsing challenge to reduce blanks
  • From: James Van Buskirk
• Re: writing characters using Z edit descriptors
  • From: robert . corbett
• Re: iso_varying_string in f2003?
  • From: James Giles
• Re: number of columns
  • From: slyi.ath.cx
• Re: iso_varying_string in f2003?
  • From: James Van Buskirk
• Re: Parsing challenge to reduce blanks
  • From: Rich Townsend
• Re: Parsing challenge to reduce blanks
  • From: David Frank
• Re: iso_varying_string in f2003?
  • From: Richard E Maine
• Re: iso_varying_string in f2003?
  • From: Richard E Maine
• Re: Layhey77 to Compaq
  • From: Richard E Maine
• Re: Layhey77 to Compaq
  • From: FJRA
• Array indexing algorithm/question
  • From: Paul Van Delst
• Re: Layhey77 to Compaq
  • From: Duane Bozarth
• Re: Layhey77 to Compaq
  • From: Simon
• Re: Parsing challenge to reduce blanks
  • From: Rich Townsend
• Re: iso_varying_string in f2003?
  • From: Joost
• Parsing challenge to reduce blanks
  • From: David Frank
• Re: iso_varying_string in f2003?
  • From: David Frank
• Re: iso_varying_string in f2003?
  • From: Steve Lionel
• Re: iso_varying_string in f2003?
  • From: Richard E Maine
• Re: iso_varying_string in f2003?
  • From: James Van Buskirk
• Re: iso_varying_string in f2003?
  • From: David Frank
• Re: iso_varying_string in f2003?
  • From: David Frank
• Re: iso_varying_string in f2003?
  • From: Rich Townsend
• Re: Layhey77 to Compaq
  • From: Richard E Maine
• Re: iso_varying_string in f2003?
  • From: David Frank
• Re: iso_varying_string in f2003?
  • From: Richard E Maine
• Re: iso_varying_string in f2003?
  • From: Joost
• Re: iso_varying_string in f2003?
  • From: Richard E Maine
• Re: Why I can't build the release version with cxml
  • From: hollowspook
• Re: iso_varying_string in f2003?
  • From: James Van Buskirk
• Re: iso_varying_string in f2003?
  • From: Steve Lionel
• Re: iso_varying_string in f2003?
  • From: Joost
• Re: iso_varying_string in f2003?
  • From: Rich Townsend
• Re: how to define a dummy argument derived-Type array?thanks
  • From: Michael Metcalf
• Re: iso_varying_string in f2003?
  • From: Steve Lionel
• Re: writing characters using Z edit descriptors
  • From: Steve Lionel
• Re: iso_varying_string in f2003?
  • From: Rich Townsend
• Re: writing characters using Z edit descriptors
  • From: Jan Vorbrüggen
• Re: what does this error code mean?
  • From: Steve Lionel
• Re: Why I can't build the release version with cxml
  • From: Steve Lionel
• Re: iso_varying_string in f2003?
  • From: Steve Lionel
• Re: writing characters using Z edit descriptors
  • From: Steve Lionel
• how to define a dummy argument derived-Type array?thanks
  • From: Daipeng1997@xxxxxxxxx
• Re: Intel Fortran 9 - visual studio requirements
  • From: Steve Lionel
• Re: T edit descriptor and ADVANCE="NO"
  • From: Steve Lionel
• Re: iso_varying_string in f2003?
  • From: David Frank
• Re: writing characters using Z edit descriptors
  • From: Jan Vorbrüggen
• Re: writing characters using Z edit descriptors
  • From: Jan Vorbrüggen
• Re: iso_varying_string in f2003?
  • From: Rich Townsend
• Re: Layhey77 to Compaq
  • From: David Jones
• Re: Layhey77 to Compaq
  • From: beliavsky
• Re: iso_varying_string in f2003?
  • From: David Frank
• Re: writing characters using Z edit descriptors
  • From: glen herrmannsfeldt
• Re: writing characters using Z edit descriptors
  • From: glen herrmannsfeldt
• Re: Re: random_number
  • From: David Jones
• Re: writing characters using Z edit descriptors
  • From: glen herrmannsfeldt
• Re: writing characters using Z edit descriptors
  • From: glen herrmannsfeldt
• Re: writing characters using Z edit descriptors
  • From: robert . corbett
• Layhey77 to Compaq
  • From: Simon
• Re: passing argument to the main program
  • From: Dave Thompson
• Re: writing characters using Z edit descriptors
  • From: robert . corbett
• Re: does this compile on your machine??
  • From: Christoph Arns
• Re: Why I can't build the release version with cxml
  • From: hollowspook
• Re: Why I can't build the release version with cxml
  • From: hollowspook
• Re: O/T: Finite element analysis speed tweaks?
  • From: Tim Prince
• Re: O/T: Finite element analysis speed tweaks?
  • From: Random Programmer
• Re: O/T: Finite element analysis speed tweaks?
  • From: Tim Prince
• Re: passing argument to the main program
  • From: bv
• Re: How can I link against a VF dll with IFC?
  • From: bv
• Re: How can I link against a VF dll with IFC?
  • From: bv
• Re: iso_varying_string in f2003?
  • From: Richard Maine
• Re: Why I can't build the release version with cxml
  • From: Greg Lindahl
• Re: iso_varying_string in f2003?
  • From: Rich Townsend
• Re: random_number
  • From: James Giles
• Re: iso_varying_string in f2003?
  • From: Richard Maine
• Re: Why I can't build the release version with cxml
  • From: Rich Townsend
• Re: iso_varying_string in f2003?
  • From: Rich Townsend
• Re: random_number
  • From: Random Programmer
• O/T: Finite element analysis speed tweaks?
  • From: Random Programmer
• what does this error code mean?
  • From: hollowspook
• Re: iso_varying_string in f2003?
  • From: David Frank
• Re: writing characters using Z edit descriptors
  • From: Gary L. Scott
• Why I can't build the release version with cxml
  • From: hollowspook
• iso_varying_string in f2003?
  • From: Rich Townsend
• Re: number of columns
  • From: David Frank
• Re: writing characters using Z edit descriptors
  • From: Dave Weatherall
• Re: writing characters using Z edit descriptors
  • From: Phillip Helbig---remove CLOTHES to reply
• Re: writing characters using Z edit descriptors
  • From: James Giles
• Re: writing characters using Z edit descriptors
  • From: Ken Plotkin
• Re: writing characters using Z edit descriptors
  • From: robert . corbett
• Re: writing characters using Z edit descriptors
  • From: James Giles
• Re: writing characters using Z edit descriptors
  • From: robert . corbett
• Re: writing characters using Z edit descriptors
  • From: Gary L. Scott
• Re: writing characters using Z edit descriptors
  • From: Ken Plotkin
• Re: writing characters using Z edit descriptors
  • From: James Giles
• Re: writing characters using Z edit descriptors
  • From: Ken Plotkin
• Re: writing characters using Z edit descriptors
  • From: Greg Lindahl
• Re: writing characters using Z edit descriptors
  • From: James Giles
• Re: writing characters using Z edit descriptors
  • From: Rich Townsend
• Re: writing characters using Z edit descriptors
  • From: Phillip Helbig---remove CLOTHES to reply
• Re: number of columns
  • From: Rich Townsend
• Re: writing characters using Z edit descriptors
  • From: glen herrmannsfeldt
• Re: fftw3 accepts extra options during compile time
  • From: Kamaraju Kusumanchi
• Re: T edit descriptor and ADVANCE="NO"
  • From: Richard Maine
• Re: fftw3 accepts extra options during compile time
  • From: Richard Maine
• Re: number of columns
  • From: David Frank
• Re: How to compile the example_itsol_1.f , and why always meets these errors.
  • From: hollowspook
• Re: writing characters using Z edit descriptors
  • From: Phillip Helbig---remove CLOTHES to reply
• Re: VF6.6 file process?
  • From: Wang Jun
• writing characters using Z edit descriptors
  • From: robert . corbett
• Re: T edit descriptor and ADVANCE="NO"
  • From: Joost
• Re: T edit descriptor and ADVANCE="NO"
  • From: glen herrmannsfeldt
• Re: does this compile on your machine??
  • From: James Van Buskirk
• Re: does this compile on your machine??
  • From: robert . corbett
• does this compile on your machine??
  • From: Christoph Arns
• Re: fftw3 accepts extra options during compile time
  • From: Kamaraju Kusumanchi
• Re: number of columns
  • From: David Frank
• Re: T edit descriptor and ADVANCE="NO"
  • From: Richard Maine
• Re: fftw3 accepts extra options during compile time
  • From: Chris Hulbert
• Re: Intel Fortran 9 - visual studio requirements
  • From: Tim Prince
• Intel Fortran 9 - visual studio requirements
  • From: Joe Hill
• Re: fftw3 accepts extra options during compile time
  • From: Richard E Maine
• Re: fftw3 accepts extra options during compile time
  • From: Richard E Maine
• fftw3 accepts extra options during compile time
  • From: Kamaraju Kusumanchi
• Re: number of columns
  • From: Colin Watters
• Re: T edit descriptor and ADVANCE="NO"
  • From: Richard E Maine
• Re: T edit descriptor and ADVANCE="NO"
  • From: glen herrmannsfeldt
• Re: T edit descriptor and ADVANCE="NO"
  • From: Joost
• Re: T edit descriptor and ADVANCE="NO"
  • From: Richard E Maine
• Re: T edit descriptor and ADVANCE="NO"
  • From: Steve Lionel
• Re: T edit descriptor and ADVANCE="NO"
  • From: James Giles
• Re: F77: Different COMMON blocks with same variable names
  • From: Richard E Maine
• Re: T edit descriptor and ADVANCE="NO"
  • From: Joost
• Re: T edit descriptor and ADVANCE="NO"
  • From: Richard E Maine
• Re: T edit descriptor and ADVANCE="NO"
  • From: Richard E Maine
• Re: T edit descriptor and ADVANCE="NO"
  • From: Joost
• Re: T edit descriptor and ADVANCE="NO"
  • From: James Giles
• Re: real-trouble
  • From: Tillmann Wegst
• Re: T edit descriptor and ADVANCE="NO"
  • From: Richard E Maine
• Re: real-trouble
  • From: Tillmann Wegst
• Re: real-trouble
  • From: Duane Bozarth
• Re: real-trouble
  • From: Tillmann Wegst
• Re: T edit descriptor and ADVANCE="NO"
  • From: Steve Lionel
• Re: T edit descriptor and ADVANCE="NO"
  • From: Joost
• Re: real-trouble
  • From: Duane Bozarth
• Re: F77: Different COMMON blocks with same variable names
  • From: Ingo Thies
• Re: F77: Different COMMON blocks with same variable names
  • From: Richard E Maine
• Re: real-trouble
  • From: Tillmann Wegst
• Re: real-trouble
  • From: Tillmann Wegst
• F77: Different COMMON blocks with same variable names
  • From: Ingo Thies
• Re: real-trouble
  • From: Steven G. Kargl
• Re: Tried to run hello-world example from tutorial, got compiler warning
  • From: Steven G. Kargl
• Re: T edit descriptor and ADVANCE="NO"
  • From: Richard E Maine
• Re: T edit descriptor and ADVANCE="NO"
  • From: Joost
• Re: Main program, function, module - it does not work.
  • From: Richard E Maine
• Re: T edit descriptor and ADVANCE="NO"
  • From: Joost
• Re: T edit descriptor and ADVANCE="NO"
  • From: Richard E Maine
• Re: How can I link against a VF dll with IFC?
  • From: Steve Lionel
• Re: Flushing output stream
  • From: Richard E Maine
• Main program, function, module - it does not work.
  • From: kurdayon
• Re: T edit descriptor and ADVANCE="NO"
  • From: Steve Lionel
• real-trouble
  • From: Tillmann Wegst
• Re: Flushing output stream
  • From: Pierre Asselin
• Re: Tried to run hello-world example from tutorial, got compiler warning
  • From: Tim Prince
• Re: How can I link against a VF dll with IFC?
  • From: Tim Prince
• Re: How can I link against a VF dll with IFC?
  • From: N. Shamsundar
• How can I link against a VF dll with IFC?
  • From: Philippe
• Re: Debugging
  • From: Chris Hulbert
• Re: Debugging
  • From: Bart Vandewoestyne
• Re: VF6.6 file process?
  • From: 王明筠
• Debugging
  • From: jg
• Re: Tried to run hello-world example from tutorial, got compiler warning
  • From: glen herrmannsfeldt
• Re: T edit descriptor and ADVANCE="NO"
  • From: glen herrmannsfeldt
• T edit descriptor and ADVANCE="NO"
  • From: Joost
• the storage format in direct solver for sparse matrix
  • From: hollowspook
• Re: Tried to run hello-world example from tutorial, got compiler warning
  • From: Bart Vandewoestyne
• Re: Tried to run hello-world example from tutorial, got compiler warning
  • From: Abdul Qat
• Tried to run hello-world example from tutorial, got compiler warning
  • From: Robert Maas, see http://tinyurl.com/uh3t

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