Re: gfortran and cpp
- From: kargl@xxxxxxxxxxxxxxxxxxxxxxxxxxxx (Steven G. Kargl)
- Date: Fri, 5 Jan 2007 06:33:50 +0000 (UTC)
In article <2N6dnZqbvoEBcwDYnZ2dnUVZ_sapnZ2d@xxxxxxxxxxx>,
glen herrmannsfeldt <gah@xxxxxxxxxxxxxxxx> writes:
Brooks Moses wrote:
(snip)
He is, but then, so do the source-form options in GFortran. "-x f77"
means fixed form, "-x f95" means free form. This could definitely be
improved, but I don't know of a good short way to say "fixed-form
fortran" to fit in the option to replace it with. Much less "fixed-form
fortran with cpp". Suggestions?
How about -x fixed and -x free? Slightly longer, but more obvious.
This is a generic option from GCC. Your suggestions would need to
be something like -x fortran-fixed-form and -x fortran-free-form.
`-x LANGUAGE'
Specify explicitly the LANGUAGE for the following input files
(rather than letting the compiler choose a default based on the
file name suffix). This option applies to all following input
files until the next `-x' option. Possible values for LANGUAGE
are:
c c-header c-cpp-output
c++ c++-header c++-cpp-output
objective-c objective-c-header objective-c-cpp-output
objective-c++ objective-c++-header objective-c++-cpp-output
assembler assembler-with-cpp
ada
f95 f95-cpp-input
java
treelang
An alternative is to read the gfortran documentation, and then rename
the file with a .F or .F90 suffix.
--
Steve
http://troutmask.apl.washington.edu/~kargl/
.
- Follow-Ups:
- Re: gfortran and cpp
- From: glen herrmannsfeldt
- Re: gfortran and cpp
- References:
- gfortran and cpp
- From: Fly Away
- Re: gfortran and cpp
- From: Richard E Maine
- Re: gfortran and cpp
- From: Fly Away
- Re: gfortran and cpp
- From: Brooks Moses
- Re: gfortran and cpp
- From: glen herrmannsfeldt
- gfortran and cpp
- Prev by Date: Re: gfortran and cpp
- Next by Date: Re: gfortran and cpp
- Previous by thread: Re: gfortran and cpp
- Next by thread: Re: gfortran and cpp
- Index(es):
Relevant Pages
|