[openbeosstorage] Re: Volume.h?

On Mon, 6 May 2002, Tyler Dauwalder wrote:

> > BTW, I'm a bit surprised, that it compiles. It seems, that the Be headers
> > are in the compilers include path. I think, that should be fixed,
> > otherwise some day strange thing might happen...
> 
> Yeah, I was bit concerned myself when I was first messing with Jam. 
> However, it always seems to use our headers first (when they exist), so I 
> haven't worried about it too much since (mostly because it worked and I had 
> other things to do other than figure out how to yank the standard dirs from 
> the search paths). 

I played a bit around and I was unable to make g++ not find the Be
headers. Must be either compiled in or to be found in any specification
file I don't know of. I'm not a gcc expert though.

Thinking about it, I don't find it too surprising that at least the paths
to the POSIX and STL headers are compiled in, as they somehow belong to
the C/C++ languages (not exactly POSIX, but its ISO C subset). Well, and
usually there is no reason, why one should desire not to have the OS API
headers right at hand... save for a crazy effort like ours. ;-)

However, I don't feel like exploring that item any further. I guess, we
can live very well with the current situation. :-)

CU, Ingo

Other related posts: