Overall tree structure of boost.
— at Version 1
Current tree structure of boost looks like this:
{Root directory}
boost
doc
libs
more
people
status
tools
The boost directory is the directory for header files, but
some implementation header files there as well. This is
good for boost developers. For boost users, it's better to
separate implementation header files from those header
files used by boost users.
The same for libs directory, it's better to separate
implementation file from testing files.
I hope the tree structure of future release of boost
could look like this:
{Root directory}
include // boost user include this directory for
*.h??
include/boost // only subdirectory
libs // boost user include this directory for
*.lib/dll
src
src/include // boost developer need extra *.h??
src/libsrc // implementation source files
test // testing codes
doc
more
people
status
tools
Thanks
Herbert
Change History
(1)
Description: |
modified (diff)
|
Resolution: |
None → wontfix
|
Severity: |
→ Cosmetic
|
Status: |
assigned → closed
|
The fact is that some of the implementation headers are needed by the interface headers, so your suggestion would only mean that users would have to put two #include directories into their include path. A sad consequence of the C++ inclusion model.