🚀 go-pugleaf

matt@cyclops5.berkeley.edu (Matt Austern) wrote:
>
>Consider a project that spans several directories.  

[directory lookup problems]

>So my challenge: can anyone think of an acceptable replacement for
>"The named source file is searched for in an implementation-defined
>manner" that would provide a bit more of a guarantee of reasonable
>behavior?

Yes. GET RID OF #include ALTOGETHER. <grin>

The way to do this is to have a system
where you can "use" modules in the source code.

To _find_ the modules, an implementation specific
control file, menu, or whatever is used: I'd
start with a file of pairs (module name, filename)
plus some defaults and autosearch instructions.

The point is that editing this control file
is INDEPENDENT of the code source files.
So it means the source code does NOT
have to be edited when files are moved around
(including on the developers system)

For a given (working) project, one can produce a list
of all the modules and their files -- which
aids in porting the project (How do you know
you shipped ALL the source files needed??)

-- 
John Max Skaller               voice: 61-2-566-2189
81 Glebe Point Rd              fax:   61-2-660-0850
GLEBE NSW 2037                 email: maxtal@suphys.physics.oz.au
AUSTRALIA                      email: skaller@maxtal.com.au
---
[ 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. ]