🚀 go-pugleaf

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

>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?

A second answer to this question:

// filelist.h
#define MYFILE "myfile.h"
#define YOURFILE "../yourfile.h"
#define HISFILE "/root/lib/include/system/project/hisfile.hpp"

// main.cc 
#include "filelist.h" // current directory!
#include MYFILE       // wherever they live
#include YOURFILE
#include HISFILE
#include HERFILE
main() { ..}

This minimises the changes required to the 
file "filelist.h", and imposes only the
requirement that IT be found by 

#include "filelist.h"

Its contents may need to be edited when moving things,
which is a pain, but at least it is a localised pain.

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