🚀 go-pugleaf

In message <DMBrxn.GAB@falcon.daytonoh.attgis.com> - Dick Menninger <Dick.Menni
nger@daytonoh.attgis.com> writes:
:>
[...]
:>>name techniques are needed to do other semantics.  But an
:>include file can be a form of template for source construction
:>that could be included many times on purpose.  That is what
:>you are proposing to eliminate.  
[...]

I don't see it eliminating old operation just adding a feature which is used 
frequently and is time consuming.
The author of an included file knows if including beyond a point produces 
anything that is redundant and can tell the compiler to stop looking at it.

I would even go farther and propose something like:

#invariant

which would tell the compiler to stop scanning this file if it already had 
scanned it before.  This is not as efficient as not including it at all, but 
then the programmer doesn't need to know if the results are different each 
time.

Ken Walter

* All the above is hearsay and the opinion of nobody in particular
---
[ comp.std.c++ is moderated.  Submission address: std-c++@ncar.ucar.edu.
  Contact address: std-c++-request@ncar.ucar.edu.  The moderation policy is
  in http://reality.sgi.com/employees/austern_mti/std-c++/policy.html. ]