🚀 go-pugleaf

In article <4fukhs$fc3@hermes.acs.unt.edu> johnw@jove.acs.unt.edu
(John R. Williams) writes:

   devitto@ferndown.ate.slb.com wrote:
   > What about Bjarne's idea of "include" as a keyword that only has the
   > effect of a #include if the file has not been "include"d already.

   > I suppose the idea is that the compiler builds a table (like gcc does for
   > wrapped includes) - pretty simple really.

   > Ideas about why this won't work ???

   Personally I'll continue to advocate "#once" to prevent multiple 
   inclusion of a header for these reasons:

So instead of adding yet another preprocessor directive, why not use
Objective C's #import which does exactly that? (I know this is also a
reason for *not* using it in order to make clear that the header file
is a C++ one, but I don't tjink it will be sooo confusing).

YA.
--
Yves Arrouye       |  arrouye@marin.fdn.fr | http://www-scope.imag.fr/~arrouye
7, av. Leon Bollee +-----------------------+---------+------------------------
75013 Paris        |  Home voice: +33 1 53 61 09 55  |  Fax: +33 1 53 61 09 55
France             |  Please use these only between 8:00 AM and 11:00 PM, MET!
---
[ comp.std.c++ is moderated.  Submission address: std-c++@ncar.ucar.edu.
  Contact address: std-c++-request@ncar.ucar.edu.  Moderation policy:
  http://reality.sgi.com/employees/austern_mti/std-c++/policy.html. ]