From: David Abrahams (dave_at_[hidden])
Date: 2002-09-11 08:24:26
From: "Vladimir Prus" <ghost_at_[hidden]>
> > That rule seems a little too trivial to be correct. Don't you care what
the
> > #include path is?
> > What if that particular a_parser.h wasn't intended?
>
> Ok, you can check if the current dir is in path.
No way, dude: The contents of the header might well depend on the toolset
and build variant!
> I don't think much more
> complexity is needed. User expects everything to work as if the file
> were generated in the current dir.
I don't think so, not at all.
Do you really mean the "current" directory, AKA "./"?
Or do you mean something else?
-----------------------------------------------------------
David Abrahams * Boost Consulting
dave_at_[hidden] * http://www.boost-consulting.com