🚀 go-pugleaf

In article <1996Feb1.092058.4745@iiasa.ac.at> marek@iiasa.ac.at (Marek
MAKOWSKI) writes:

> Would not it be sensible to add to the preprocessing a directive
> that would stop processing the current file ? Something like
> 
> #ifdef XXXX
> #exit
> 
> this would safe processing (sometimes very long) file in the common
> situations:
> 
> #ifdef XXXX
> // a (possibly) long header file hear
> #endif  /* ifdef XXXX*/

Why bother?  The usual procedure is for the compiler to recognize the
pattern the first time it reads the file, and not even open it in
further include declarations.

(I know that g++ does this, but I seem to recall from some earlier
discussion someone at Sun claiming that they had done measurements, and
it wasn't worth the bother.  Given that it sometimes takes close to a
second to open a file on one customer's network, I'm rather sceptical of
these results.)

-- 
James Kanze           (+33) 88 14 49 00          email: kanze@gabi-soft.fr
GABI Software, Sarl., 8 rue des Francs Bourgeois, 67000 Strasbourg, France
Conseils, études et réalisations en logiciel orienté objet --
              -- A la recherche d'une activité dans une region francophone

[ comp.std.c++ is moderated.  Submission address: std-c++@ncar.ucar.edu.
  Contact address: std-c++-request@ncar.ucar.edu.  The moderation policy is
  summarized in http://reality.sgi.com/employees/austern_mti/std-c++/policy.html
]