Re: I have Intel Fortran 2011 XE Composer - but how do i compile a F95 program



Hi Richard

As usual, your reply to the OP is helpful and solves their problem. I just
have a small nit to pick, if you don't mind. :-)

While the advice of renaming the file might be ok for the Intel compiler,
and you're right that F95 is not that different from F90, I'd like to
caution that it's not a good general practice to always use .f90. Some
compilers, like XL Fortran, see the file extension as a hint from the user
about the language version. For example, XLF defaults to enabling signed
zero, automatic deallocation, and PAD='undefined' in INQUIRE for .f95 files
and defaults to disabling them for .f90 files.

The difference is even bigger once one uses .f03 files, since F2003 was a
major revision of the standard.

Regards

Rafik
Visit the Fortran Cafe at http://ibm.com/rational/cafe

"Richard Maine" <nospam@xxxxxxxxxxxxx> wrote in message
news:1kbusnt.hzv3lf12qsjx2N%nospam@xxxxxxxxxxxxxxxx
Paul Anton Letnes <paul.anton.letnes@xxxxxxxxxxxxxxxxxxxxxxxx> wrote:

On 06.12.11 14:16, e p chandler wrote:

---> Try compiling your F95 program as you did with your F90 program. I
suspect that Intel Fortran does not need a different filename extension
or a different command invocation to handle F95 instead of F90. Or do
you need some command line option to check for conformance to F95 as
opposed to F90 standards?

I have had issues with getting intel fortran to compile files named
something.f95. There is a command line flag to get it to take *.f95
files. You'll find it in the manual - I don't remember off the top of my
head.

But an easier solution is to just not do that in the first place. Then
you won't have to go digging through the manual to figure out how to
force the compiler to accept it.

Not to speak of the fact that, Fortran 95 being so liitle changed from
Fortran 90, odds are reasonably high that most files that you might
label as .f95 are probably valid Fortran 90 anyway. If that might not
happen to be true of your particular files, I'd bet it sure is for many
people's.

--
Richard Maine | Good judgment comes from experience;
email: last name at domain . net | experience comes from bad judgment.
domain: summertriangle | -- Mark Twain



.



Relevant Pages

  • Re: finding available kind values, precisions and exponent ranges
    ... my files an extension that indicates in what Fortran standard ... If my intention was to write a Fortran 95 ... conforming source file, then i add .f95. ... to write Fortran 90, then I use .f90. ...
    (comp.lang.fortran)
  • Re: Crazy Problem
    ... > It's not in the standard anywhere - the standard does not talk about how the ... I would still use an .f95 suffix ... unlike the Lahey f95 compiler and also, soon, the PGI f95 compiler. ... Fortran has two incompatible source forms and does not define a way ...
    (comp.lang.fortran)
  • Re: I have Intel Fortran 2011 XE Composer - but how do i compile a F95 program
    ... allowed for older file extensions, like .f90. ... the f95 behavior won't change its results. ... The F95 implementation predates my time on the Fortran compiler, ...
    (comp.lang.fortran)
  • Re: Sunperf library, pure functions?
    ... F95 compilers often were typically evolutionary ... developments from f90 compilers, rather than wholy new from scratch. ... As such, if compiler internals included f90 in their names, these ...
    (comp.lang.fortran)
  • Re: I have Intel Fortran 2011 XE Composer - but how do i compile a F95 program
    ... I am rather new to this MS VS2010 and XE 2011 Fortran Composer so I try ... I wonder how I can use the command-line to compile my small F95 ... I do indeed know how to do it with F90 prgs. ... I have had issues with getting intel fortran to compile files named something.f95. ...
    (comp.lang.fortran)