Re: [Boost-bugs] [Boost C++ Libraries] #221: Overall tree structure of boost.

Subject: Re: [Boost-bugs] [Boost C++ Libraries] #221: Overall tree structure of boost.
From: Boost C++ Libraries (noreply_at_[hidden])
Date: 2007-07-06 01:27:18


#221: Overall tree structure of boost.
-------------------------------+--------------------------------------------
  Reporter: yuhaian | Owner: nobody
      Type: Feature Requests | Status: closed
 Milestone: | Component: None
   Version: None | Severity: Cosmetic
Resolution: wontfix | Keywords:
-------------------------------+--------------------------------------------
Changes (by dave):

  * status: assigned => closed
  * resolution: None => wontfix
  * severity: => Cosmetic

Old description:

> {{{
> 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
> }}}

New description:

 {{{
 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
 }}}

Comment:

 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.

--
Ticket URL: <http://svn.boost.org/trac/boost/ticket/221#comment:1>
Boost C++ Libraries <http://www.boost.org/>
Boost provides free peer-reviewed portable C++ source libraries.


This archive was generated by hypermail 2.1.7 : 2017-02-16 18:49:56 UTC