🚀 go-pugleaf

In article <48ta6u$5c2@engnews1.eng.sun.com> clamage@Eng.sun.com (Steve Clamage) writes:

>>>>> "SC" == Steve Clamage <clamage@Eng.sun.com> writes:

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

I was myself recommending to users in my project to resort to one and
only one include syntax (that is #include <...>), under the rationale
that:

The location of the included files is a configuration management
concern and should be taken care inthe makefile. Extra-linguistic
features should be used only as few as possible.

Would you comment on that?
-- 
+---------------------------------------------------------------------------+
| Marc Girod - Nokia Telecommunications     Phone: +358-0-511 27703         |
| Kilo RD 4 - P.O. Box 12                     Fax: +358-0-511 27432         |
| SF-02611 Espoo 61 - Finland            Internet: marc.girod@ntc.nokia.com |
|        X.400: C=FI, A=Elisa, P=Nokia Telecom, SUR=Girod, GIV=Marc         |
+---------------------------------------------------------------------------+

[ 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. ]