Re: [boost] Form of inclusion directive

From: Ed Brey (brey_at_[hidden])
Date: 2000-11-01 13:58:00

From: "David Abrahams" <abrahams_at_[hidden]>
> 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? ;->

Mostly the latter.  I have had sincere requests/laments resulting from my
boost evangelism for the ability to #include <something/boost/header.hpp>.
It wasn't a big deal, though, since I managed to successfully evangelize
updating the project search path.

I think a more pragmatic reason to figure out the best solution is so that
we can start using it, so that later, when we have a much larger number of
files, we aren't in the position to make a huge change then.  If we decide a
change is in order, I don't think an across the board change would be
necessary.  The change could be phased in with all new files, and existing
files could be changed whenever they happened to be changed for another
reason (as long there is a note somewhere explaining the temporary
inconsistency).  Either way - all at once or piecemeal - would be OK.

This definitely is a low priority issue, bordering on pedantic.  I was
hoping that the right answer was easy and straightforward, but I was
probably being optimistic.  Gary's comment about only using brackets for
standard includes is an interesting point.  A look at the relevant section
in "The C++ Programming Language" fits with Gary's comment.  Too bad the
Standard doesn't provide a clear pictures on where #include flexibility
starts and stops.