🚀 go-pugleaf

In article p9r@lhc.nlm.nih.gov, bkline@cortex.nlm.nih.gov (Bob Kline) writes:
>
>Is there any mechanism in place or under consideration for portably
>guaranteeing that a non-reserved header name used by an implementer 
>will not silently override one chosen by the user of the implementation?

No. But you should use <header> for system headers and "header" for
your own headers. The two notations have implementation-defined
semantics, and implementations traditionally use different search
methods so that a system header will not override a project header,
and vice versa.

There isn't much the standard can say about this without getting into
details of directories, files, path names, and so on, none of which
are otherwise mentioned or required by the standard.
---
Steve Clamage, stephen.clamage@eng.sun.com



[ 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://dogbert.lbl.gov/~matt/std-c++/policy.html. ]