This is the mail archive of the fortran@gcc.gnu.org mailing list for the GNU Fortran project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: -cpp and 'include'

From: Toon Moene <toon at moene dot org>
To: Tom Browder <tom dot browder at gmail dot com>
Cc: Tobias Burnus <burnus at net-b dot de>, fortran at gcc dot gnu dot org
Date: Thu, 21 May 2009 12:01:31 +0200
Subject: Re: -cpp and 'include'
References: <8bc817ee0905171822h359e1d25k7604a2a3e17c2bf8@mail.gmail.com> <4A10F5A2.8000003@net-b.de> <8bc817ee0905180432r28d349adhdb60b67c649a9a0c@mail.gmail.com>

Tom Browder wrote:

On Mon, May 18, 2009 at 00:44, Tobias Burnus <burnus@net-b.de> wrote:

There was some discussion whether gfortran -cpp also should use CPP for
"include" but the outcome was non-conclusive with inclination to keep
the status quo.

I tested the same code that with g95 and Sun f95 and they also error out there.

However, it seems to me that if pre-processing is going to be done
that it should be done on ALL the code.

(I would like to change my code to solve the problem but unfortunately
it isn't up to me at the moment.)

We (http://hirlam.org) found this out some 15 years ago and switched to #include and never looked back :-)

--
Toon Moene - e-mail: toon@moene.org - phone: +31 346 214290
Saturnushof 14, 3738 XG  Maartensdijk, The Netherlands
At home: http://moene.org/~toon/
Progress of GNU Fortran: http://gcc.gnu.org/gcc-4.4/changes.html

Follow-Ups:
- Re: -cpp and 'include'
  - From: Tom Browder

References:
- -cpp and 'include'
  - From: Tom Browder
- Re: -cpp and 'include'
  - From: Tobias Burnus
- Re: -cpp and 'include'
  - From: Tom Browder

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]