Re: comment and IBM xlf

Fly Away <victor.prosolin@xxxxxxxxx> wrote:
I don't think it's going to work even if you find a way to run cpp
before compilation. My undersdanding (with regard to Fortran) is that
essentially, all cpp does is adding or removing peices of code (written
in Fortran) based on what instructions you give to it.

A true C preprocessor removes comments first. That is,

/*
#include <xyz.h>
*/

is NOT a prerprocessor #include statement.

I am not sure that either fixed or free field Fortran can survive
the C preprocessor, though, so it might be that only modified
preprocessors are used.

-- glen
.

Relevant Pages

  • Re: COCO and/ior CPP users?
    ... preprocessor standards, but the Fortran standards groups have a hard ... enough time agreeing on the languag that things like preprocessor standards are just outside the current efforts. ... do Fortran programmers just not care that much about such things? ... Behrens) -- but never for portability. ...
    (comp.lang.fortran)
  • Re: COCO and/ior CPP users?
    ... >> preprocessor standards, but the Fortran standards groups have a hard ... OR, do Fortran ... perspectives do find lots of use for preprocessors with Fortran code. ...
    (comp.lang.fortran)
  • Re: derived types with parameter keyword
    ... Fortran Interp guy without duress. ... Since part 3 of the Fortran standard is a preprocessor, ... I would rather see a companion macro language that went way ... beyond conditional compilation with a certain ...
    (comp.lang.fortran)
  • Re: templates - generic programming
    ... > Is there a preprocessor type of tool available that is sophisticated ... "a preprocessor for Fortran 90 code, ... Generic programming in Fortran 90 ...
    (comp.lang.fortran)
  • Re: Preprocessor and conditional compilation
    ... > is it possible to write macroses inside Fortran programs, ... > there any compiler-independent preprocessor for Fortran, ...
    (comp.lang.fortran)