🚀 go-pugleaf

In article <GIROD.95Nov23150453@dshp01.trs.ntc.nokia.com>,
Marc Girod <girod@trshp.trs.ntc.nokia.com> wrote:
>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 in the makefile. Extra-linguistic
>features should be used only as few as possible.

Personally, I and my team use "file" for our include files and <file> for
system include files.  It makes it easy to see at a glace to what a specific
include file belongs to.  We also always put system include files first since
we can modify ours to understand them, but not the other way around.

Additionally, we put the "functional group" as part of the pathname in
"files".  For example:

.../coolapp/main.cc:
#include "service/database.h"
#include "coolapp/ui.h"

                                        Brian
                                 ( bcwhite@bnr.ca )

------------------------------------------------------------------------------
    In theory, theory and practice are the same.  In practice, they're not.
---
[ 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. ]