Re: [boost] Re: #include <boost/...> to #include "boost/..." transition?

From: Victor A. Wagner, Jr. (vawjr_at_[hidden])
Date: 2002-07-21 21:51:45

I think you missed the point.... NOBODY is suggesting relative paths
At Sunday 2002/07/21 08:22, you wrote:
>[deleted]
>   No, absolutely not.  Neither Boost nor any publically-distributed 
> library should use #include "relativePath" to include files, whether they 
> be "header" files, "source" files, "declaration" files, 
> "definition"/"template noninline function-definition"/"inline 
> function-definition" files, "package" files, or otherwise.  Doing so 
> implies that the C++ code knows what the current working directory of the 
> build environment is (or knows what some other implementation-defined 
> #include-"relativePath"-search directory scheme is).
>[deleted]
>   Beman, for these reasons I expect you to withdraw your request to 
> switch from #include <relativePath> to #include "relativePath".
>
>  Dan'l Miller
>_______________________________________________
>Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost

Victor A. Wagner Jr.      http://rudbek.com
PGP RSA fingerprint = 4D20 EBF6 0101 B069 3817 8DBF C846 E47A
PGP D-H fingerprint = 98BC 65E3 1A19 43EC 3908 65B9 F755 E6F4 63BB 9D93
The five most dangerous words in the English language:
               "There oughta be a law"