RE: [boost] Form of inclusion directive

From: Chris Little (cslittle_at_[hidden])
Date: 2000-11-01 16:30:22

My understanding is that it always searchs the folders in the order listed
in the preference dialog.

Chris
> -----Original Message-----
> From: David Abrahams [mailto:abrahams_at_[hidden]]
> Sent: Wednesday, November 01, 2000 2:58 PM
> To: boost_at_[hidden]
> Subject: Re: [boost] Form of inclusion directive
> 
> 
> RE: [boost] Form of inclusion directiveRight, but the big 
> question is, "does
> it look first in the directory of the #include-ing file when 
> you write an
> #include with quotes?"
> 
> ----- Original Message -----
> From: Chris Little
> To: 'boost_at_[hidden]'
> Sent: Wednesday, November 01, 2000 2:02 PM
> Subject: RE: [boost] Form of inclusion directive
> 
> 
> Metrowerks has two sets of searchs path, user and system.  If 
> you write
> #include <> it looks in the system search paths and if you 
> write #include ""
> it looks in the user search paths and then the system paths.
> There is an option "Always Search User Paths" that will force 
> #include <> to
> search in the user paths as well.  It's off by default.
> Chris
> 
> 
> > -----Original Message-----
> > From: David Abrahams [mailto:abrahams_at_[hidden]]
> > Sent: Wednesday, November 01, 2000 1:42 PM
> > To: boost_at_[hidden]
> > Subject: Re: [boost] Form of inclusion directive
> >
> >
> >
> > ----- Original Message -----
> > From: "Ed Brey" <brey_at_[hidden]>
> >
> > > I can't think of any implementation that would makes sense
> > > other than for that initial search to search the current
> > directory, and
> > then
> > > possibly also the main project directory.  As long as the current
> > directory
> > > gets searched first, we're fine.  Can anyone think of a 
> reason to be
> > > concerned that an implementation might not do this?
> >
> > I seem to remember that Metrowerks used a different rule than
> > some other
> > compilers, but I can't be sure.
> >
> > That said, are we solving a real problem that someone had, or
> > is this just
> > the sort of tinkering that requires changing lots of 
> headers and will
> > probably break something? ;->
> >
> > -Dave
> >
> >
> >
> >
> 
> 
> 
>