feedc0de/boost_fusion
1
0
Fork 0
forked from boostorg/fusion
Code Pull Requests Activity

added copyright and license info for each page.

Browse Source 
[SVN r40863]
This commit is contained in:
Joel de Guzman
2007-11-07 02:12:28 +00:00
parent 0acc783f19
commit e10f3e17b3
280 changed files with 3238 additions and 2282 deletions
Download Patch File Download Diff File Expand all files Collapse all files

36
doc/html/fusion/organization.html
View File

@ -34,7 +34,7 @@
The library is organized in three layers:
</p>
<a name="fusion.organization.layers"></a><h3>
<a name="id458976"></a>
<a name="id459044"></a>
<a href="organization.html#fusion.organization.layers">Layers</a>
</h3>
<div class="blockquote"><blockquote class="blockquote">
@ -47,24 +47,25 @@
</p>
</blockquote></div>
<p>
The entire library is found in the "boost/fusion" directory. Modules
are organized in directories. Each module has its own header file placed in
the same directory with the actual module-directory. For example, there exists
"boost/fusion/support.hpp" in the same directory as "boost/fusion/support".
Everything, except those found inside "detail" directories, is public.
The entire library is found in the <tt class="computeroutput"><span class="string">"boost/fusion"</span></tt>
directory. Modules are organized in directories. Each module has its own header
file placed in the same directory with the actual module-directory. For example,
there exists <tt class="computeroutput"><span class="string">"boost/fusion/support.hpp"</span></tt>
in the same directory as "boost/fusion/support". Everything, except
those found inside "detail" directories, is public.
</p>
<p>
There is also a "boost/fusion<span class="emphasis"><em>include</em></span>" directory
that contains all the headers to all the components and modules. If you are
unsure where to find a specific component or module, or don't want to fuss
with hierarchy and nesting, use this.
There is also a <tt class="computeroutput"><span class="string">"boost/fusion/include/"</span></tt>
directory that contains all the headers to all the components and modules.
If you are unsure where to find a specific component or module, or don't want
to fuss with hierarchy and nesting, use this.
</p>
<p>
The library is header-only. There is no need to build object files to link
against.
</p>
<a name="fusion.organization.directory"></a><h3>
<a name="id459042"></a>
<a name="id459143"></a>
<a href="organization.html#fusion.organization.directory">Directory</a>
</h3>
<div class="itemizedlist"><ul type="disc">
@ -185,7 +186,7 @@
</li>
</ul></div>
<a name="fusion.organization.example"></a><h3>
<a name="id459222"></a>
<a name="id459322"></a>
<a href="organization.html#fusion.organization.example">Example</a>
</h3>
<p>
@ -201,12 +202,12 @@
</pre>
<p>
The first includes all containers The second includes only <tt class="computeroutput"><span class="identifier">list</span></tt>
<sup>[<a name="id459518" href="#ftn.id459518">3</a>]</sup>
<sup>[<a name="id459620" href="#ftn.id459620">3</a>]</sup>
.
</p>
<div class="footnotes">
<br><hr width="100" align="left">
<div class="footnote"><p><sup>[<a name="ftn.id459518" href="#id459518">3</a>] </sup>
<div class="footnote"><p><sup>[<a name="ftn.id459620" href="#id459620">3</a>] </sup>
Modules may contain smaller components. Header file information for each
component will be provided as part of the component's documentation.
</p></div>
@ -214,8 +215,11 @@
</div>
<table xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" width="100%"><tr>
<td align="left"></td>
<td align="right"><small>Copyright <20> 2001-2007 Joel de Guzman, Dan Marsden, Tobias
Schwinger</small></td>
<td align="right"><div class="copyright-footer"><small>Copyright <20> 2001-2007 Joel de Guzman, Dan Marsden, Tobias
Schwinger<p>
Distributed under the Boost Software License, Version 1.0. (See accompanying
file LICENSE_1_0.txt or copy at <a href="http://www.boost.org/LICENSE_1_0.txt" target="_top">http://www.boost.org/LICENSE_1_0.txt</a>)
</p></small></div></td>
</tr></table>
<hr>
<div class="spirit-nav">