[boost-doc-zh] r358 committed - property_tree 库译文。...

From: boost-doc-zh@xxxxxxxxxxxxxx
To: boost-doc-zh-notify@xxxxxxxxxxxxx
Date: Fri, 25 Dec 2009 01:59:59 +0000

Revision: 358
Author: alai04
Date: Thu Dec 24 17:59:33 2009
Log: property_tree 库译文。
首次采用翻译qbk文件后生成html文档的方式，reference部分不译。
http://code.google.com/p/boost-doc-zh/source/detail?r=358

Added:
 /trunk/doc/html/boost_propertytree
 /trunk/doc/html/boost_propertytree/accessing.html
 /trunk/doc/html/boost_propertytree/container.html
 /trunk/doc/html/boost_propertytree/parsers.html
 /trunk/doc/html/boost_propertytree/synopsis.html
 /trunk/doc/html/boost_propertytree/tutorial.html
 /trunk/doc/html/property_tree/appendices_______.html
 /trunk/libs/property_tree/doc/Jamfile.v2
 /trunk/libs/property_tree/doc/accessing.qbk
 /trunk/libs/property_tree/doc/cmd_line_parser.qbk
 /trunk/libs/property_tree/doc/container.qbk
 /trunk/libs/property_tree/doc/info_parser.qbk
 /trunk/libs/property_tree/doc/ini_parser.qbk
 /trunk/libs/property_tree/doc/intro.qbk
 /trunk/libs/property_tree/doc/json_parser.qbk
 /trunk/libs/property_tree/doc/parsers.qbk
 /trunk/libs/property_tree/doc/property_tree.qbk
 /trunk/libs/property_tree/doc/synopsis.qbk
 /trunk/libs/property_tree/doc/system_environment_parser.qbk
 /trunk/libs/property_tree/doc/tutorial.qbk
 /trunk/libs/property_tree/doc/windows_registry_parser.qbk
 /trunk/libs/property_tree/doc/xml_parser.qbk
Deleted:
 /trunk/doc/html/property_tree/appendices.html
Modified:
 /trunk/doc/html/property_tree/reference.html
 /trunk/doc/html/property_tree.html

=======================================
--- /dev/null

+++ /trunk/doc/html/boost_propertytree/accessing.html Thu Dec 24 17:59:332009

Binary file, no diff available.
=======================================
--- /dev/null

+++ /trunk/doc/html/boost_propertytree/container.html Thu Dec 24 17:59:332009

@@ -0,0 +1,82 @@
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">

+<title>Property Tree as a Container作为容器的属性树</title>

+<link rel="stylesheet" href="../boostbook.css" type="text/css">
+<meta name="generator" content="DocBook XSL Stylesheets V1.73.2">

+<link rel="start" href="../index.html" title="Boost C++库 BoostBook文档子集">+<link rel="up" href="../property_tree.html"title="Chapter 14. Boost.PropertyTree">+<link rel="prev" href="tutorial.html" title="Five Minute Tutorial五分钟教程">+<link rel="next" href="synopsis.html" title="Property Tree Synopsis属性树概要">

+</head>

+<body bgcolor="white" text="black" link="#0000FF" vlink="#840084"alink="#0000FF">

+<table cellpadding="2" width="100%"><tr>

+<td valign="top"><img alt="Boost C++ Libraries" width="277" height="86"src="../../../boost.png"></td>

+<td align="center"><a href="../../../index.html">Home</a></td>
+<td align="center"><a href="../../../libs/libraries.htm">Libraries</a></td>

+<td align="center"><ahref="http://www.boost.org/users/people.html";>People</a></td>+<td align="center"><ahref="http://www.boost.org/users/faq.html";>FAQ</a></td>

+<td align="center"><a href="../../../more/index.htm">More</a></td>
+</tr></table>
+<hr>
+<div class="spirit-nav">

+<a accesskey="p" href="tutorial.html"><imgsrc="../../../doc/html/images/prev.png" alt="Prev"></a><a accesskey="u"href="../property_tree.html"><img src="../../../doc/html/images/up.png"alt="Up"></a><a accesskey="h" href="../index.html"><imgsrc="../../../doc/html/images/home.png" alt="Home"></a><a accesskey="n"href="synopsis.html"><img src="../../../doc/html/images/next.png"alt="Next"></a>

+</div>
+<div class="section" lang="en">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">

+<a name="boost_propertytree.container"></a><a class="link"href="container.html" title="Property Tree as a Container作为容器的属性树"> PropertyTree as a Container

+    &#20316;&#20026;&#23481;&#22120;&#30340;&#23646;&#24615;&#26641;</a>
+</h2></div></div></div>
+<p>

+ Every property tree node models the ReversibleSequence concept,providing access+ to its immediate children. This means that iterating over a <codeclass="computeroutput"><a class="link"href="../boost/property_tree/ptree.html" title="Type definitionptree">ptree</a></code>+ (which is the same as its root node - every <codeclass="computeroutput"><a class="link"href="../boost/property_tree/ptree.html" title="Type definitionptree">ptree</a></code>+ node is also the subtree it starts) iterates only a single level ofthe hierarchy.

+      There is no way to iterate over the entire tree.
+    </p>
+<p>

+每一个属性树节点都符合可逆序列概念，提供对其直接子节点的访问。这意味着遍历一个+ <code class="computeroutput"><a class="link"href="../boost/property_tree/ptree.html" title="Type definitionptree">ptree</a></code> (与根节点一样+ - 每个 <code class="computeroutput"><a class="link"href="../boost/property_tree/ptree.html" title="Type definitionptree">ptree</a></code>节点同时也是从它开始的子树)只是遍历单个层级。+没有方法直接遍历整棵树。

+    </p>
+<p>

+ It is very important to remember that the property sequence is <spanclass="bold">not+ ordered by the key. It preserves the order of insertion. It closelyresembles+ a std::list. Fast access to children by name is provided via aseparate lookup+ structure. Do not attempt to use algorithms that expect an orderedsequence

+      (like binary_search) on a node's children.
+    </p>
+<p>

+有一点很重要必须要记住，属性序列*并不是*按其键值排序的。它保留了插入的顺序。+ 它更接近于std::list。按名字对子节点的快速访问，是通过一个独立的查找结构来提供的。+不要试图对一个节点的子节点使用那些要求有序序列的算法(如

+      binary_search)&#12290;
+    </p>
+<p>

+ There may be multiple children with the same key value in a node.However,+ these children are not necessarily sequential. The iterator returnedby <code class="computeroutput"><a class="link"href="../boost/property_tree/basic_ptree.html#id5212679-bb">find</a></code>may refer to+ any of these, and there are no guarantees about the relativeposition of the

+      other equally named children.
+    </p>
+<p>

+一个节点中可能会有多个子节点带有相同的键值。但是这些子节点间是没有先后顺序的。+ <code class="computeroutput"><a class="link"href="../boost/property_tree/basic_ptree.html#id5212679-bb">find</a></code>+所返回的迭代器可能指向它们中的任意一个，而且对于其它相同名字的+子节点的相对位置，也是没有保证的。

+    </p>
+</div>

+<table xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision";width="100%"><tr>

+<td align="left"></td>

+<td align="right"><div class="copyright-footer">Copyright (c) 2008 MarcinKalicinski+ Distributed under the Boost Software License, Version 1.0. (Seeaccompanying+ file LICENSE_1_0.txt or copy at <ahref="http://www.boost.org/LICENSE_1_0.txt";target="_top">http://www.boost.org/LICENSE_1_0.txt</a>)

+      </p>
+</div></td>
+</tr></table>
+<hr>
+<div class="spirit-nav">

+</div>
+</body>
+</html>
=======================================
--- /dev/null
+++ /trunk/doc/html/boost_propertytree/parsers.html     Thu Dec 24 17:59:33 2009
@@ -0,0 +1,419 @@
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">

+<title>How to Populate a Property Tree如何填充属性树</title>

+<link rel="stylesheet" href="../boostbook.css" type="text/css">
+<meta name="generator" content="DocBook XSL Stylesheets V1.73.2">

+<link rel="start" href="../index.html" title="Boost C++库 BoostBook文档子集">+<link rel="up" href="../property_tree.html"title="Chapter 14. Boost.PropertyTree">+<link rel="prev" href="synopsis.html" title="Property Tree Synopsis属性树概要">+<link rel="next" href="accessing.html" title="How to Access Data in aProperty Tree如何访问属性树中的数据">

+</head>

+<body bgcolor="white" text="black" link="#0000FF" vlink="#840084"alink="#0000FF">

+<table cellpadding="2" width="100%"><tr>

+<td valign="top"><img alt="Boost C++ Libraries" width="277" height="86"src="../../../boost.png"></td>

+<td align="center"><a href="../../../index.html">Home</a></td>
+<td align="center"><a href="../../../libs/libraries.htm">Libraries</a></td>

+<td align="center"><ahref="http://www.boost.org/users/people.html";>People</a></td>+<td align="center"><ahref="http://www.boost.org/users/faq.html";>FAQ</a></td>

+<td align="center"><a href="../../../more/index.htm">More</a></td>
+</tr></table>
+<hr>
+<div class="spirit-nav">

+<a accesskey="p" href="synopsis.html"><imgsrc="../../../doc/html/images/prev.png" alt="Prev"></a><a accesskey="u"href="../property_tree.html"><img src="../../../doc/html/images/up.png"alt="Up"></a><a accesskey="h" href="../index.html"><imgsrc="../../../doc/html/images/home.png" alt="Home"></a><a accesskey="n"href="accessing.html"><img src="../../../doc/html/images/next.png"alt="Next"></a>

+</div>
+<div class="section" lang="en">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">

+<a name="boost_propertytree.parsers"></a><a class="link"href="parsers.html" title="How to Populate a Property Tree如何填充属性树"> How to Populatea Property

+    Tree &#22914;&#20309;&#22635;&#20805;&#23646;&#24615;&#26641;</a>
+</h2></div></div></div>
+<div class="toc"><dl>

+<dt><ahref="parsers.html#boost_propertytree.parsers.xml_parser__xml_________">XML

+      Parser XML&#20998;&#26512;&#22120;</a></span></dt>

+<dt><ahref="parsers.html#boost_propertytree.parsers.json_parser__json_________">JSON

+      Parser JSON&#20998;&#26512;&#22120;</a></span></dt>

+<dt><ahref="parsers.html#boost_propertytree.parsers.ini_parser__ini_________">INI

+      Parser INI&#20998;&#26512;&#22120;</a></span></dt>

+<dt><ahref="parsers.html#boost_propertytree.parsers.info_parser__info_________">INFO

+      Parser INFO&#20998;&#26512;&#22120;</a></span></dt>
+</dl></div>
+<div class="section" lang="en">
+<div class="titlepage"><div><div><h3 class="title">

+<a name="boost_propertytree.parsers.xml_parser__xml_________"></a><aclass="link"href="parsers.html#boost_propertytree.parsers.xml_parser__xml_________"title="XML Parser XML分析器">XML

+      Parser XML&#20998;&#26512;&#22120;</a>
+</h3></div></div></div>
+<p>

+ The <a href="http://en.wikipedia.org/wiki/XML"; target="_top">XMLformat</a> is an+ industry standard for storing information in textual form.Unfortunately,+ there is no XML parser in <a href="http://www.boost.org";target="_top">Boost</a>+ as of the time of this writing. The library therefore contains thefast and+ tiny <a href="http://rapidxml.sourceforge.net/";target="_top">RapidXML</a> parser+ (currently in version 1.13) to provide XML parsing support.RapidXML does+ not fully support the XML standard; it is not capable of parsingDTDs and

+        therefore cannot do full entity substitution.
+      </p>
+<p>

+ <a href="http://en.wikipedia.org/wiki/XML"; target="_top">XMLformat</a>是以文本方式保存信息的工业标准。不幸的是，目前在+ <a href="http://www.boost.org"; target="_top">Boost</a>还没有XML分析器。+因此，本库包含了一个小而快的<a href="http://rapidxml.sourceforge.net/"; target="_top">RapidXML</a>+ 分析器(当前版本为1.13)以提供XML分析的支持。RapidXML并不完全支持XML标准；它不能分析DTDs，因此不能实现完全的实体替换。

+      </p>
+<p>

+ By default, the parser will preserve most whitespace, but removeelement+ content that consists only of whitespace. Encoded whitespaces(e.g. &#32;)+ does not count as whitespace in this regard. You can pass thetrim_whitespace+ flag if you want all leading and trailing whitespace trimmed andall continuous

+        whitespace collapsed into a single space.
+      </p>
+<p>

+缺省情况下，这个分析器会保留最多的空白符，但会删掉仅包含空白符的元素内容。+在此，编码的空白符(如&#32;)并不被算作空白符。如果你想去掉所有前置和后置的空白符，+且将所有连续的空白符压缩为单个空格，可以传入trim_whitespace

+        &#26631;&#24535;&#12290;
+      </p>
+<p>

+ Please note that RapidXML does not understand the encodingspecification.+ If you pass it a character buffer, it assumes the data is alreadycorrectly+ encoded; if you pass it a filename, it will read the file usingthe character+ conversion of the locale you give it (or the global locale if yougive it+ none). This means that, in order to parse a UTF-8-encoded XML fileinto a+ wptree, you have to supply an alternate locale, either directly orby replacing

+        the global one.
+      </p>
+<p>

+ 请注意，RapidXML并不了解编码规范。如果你传入一个字符缓冲区，它会假定其中的数据已正确编码；+如果你传入一个文件名，它将使用你给定的locale(如果你没有给定，则使用全局locale)的字符转换。+这意味着，为了分析一个UTF-8编码的XML文件并存入wptree，你必须提供一个替代locale，+或者直接提供，或者替换掉全局locale。

+      </p>
+<p>

+ XML / property tree conversion schema (<codeclass="computeroutput"><a class="link"href="../boost/property_tree/xml_parser/read_xml_id5271168.html"title="Function template read_xml">read_xml</a></code>+ and <code class="computeroutput"><a class="link"href="../boost/property_tree/xml_parser/write_xml_id4884059.html"title="Function template write_xml">write_xml</a></code>):

+      </p>
+<p>

+ XML/属性树转换机制(<codeclass="computeroutput"><a class="link"href="../boost/property_tree/xml_parser/read_xml_id5271168.html"title="Function template read_xml">read_xml</a></code>+ and <code class="computeroutput"><a class="link"href="../boost/property_tree/xml_parser/write_xml_id4884059.html"title="Function template write_xml">write_xml</a></code>)：

+      </p>
+<div class="itemizedlist"><ul type="disc">
+<li>

+ Each XML element corresponds to a property tree node. The childelements+ correspond to the children of the node. 每个XML元素对应于一个属性树节点。子元素对应于该节点的子节点。

+        </li>
+<li>

+ The attributes of an XML element are stored in the subkey <codeclass="literal"><xmlattr></code>.+ There is one child node per attribute in the attribute node.Existence+ of the <code class="literal"><xmlattr></code> node is notguaranteed or necessary+ when there are no attributes. 一个XML元素的属性被保存于子键+ <code class="literal"><xmlattr></code>中。在属性节点中每个属性有一个子节点。+当没有属性时，并不保证也不需要一定有<code class="literal"><xmlattr></code>

+          &#33410;&#28857;&#12290;
+        </li>
+<li>

+ XML comments are stored in nodes named <codeclass="literal"><xmlcomment></code>,+ unless comment ignoring is enabled via the flags. XML注释被保存于名为+ <code class="literal"><xmlcomment></code>的节点中，除非用标志位激活了忽略注释。

+        </li>
+<li>

+ Text content is stored in one of two ways, depending on theflags. The+ default way concatenates all text nodes and stores them in asingle node+ called <code class="literal"><xmltext></code>. This way,the entire content+ can be conveniently read, but the relative ordering of text andchild elements+ is lost. The other way stores each text content as a separatenode, all+ called <code class="literal"><xmltext></code>. 文本内容以两种方法中的一种进行保存，由标志位决定。缺省的方法是将所有文本节点串接起来，+将它们保存在单个名为<code class="literal"><xmltext></code>的节点中。这种方法方便读取整个内容，但文本的相对顺序+以及子元素全部丢失。另一种方法是，将每个文本内容保存为单个节点，均命名为

+          <code class="literal">&lt;xmltext&gt;</code>&#12290;
+        </li>
+</ul></div>
+<p>

+ The XML storage encoding does not round-trip perfectly. Aread-write cycle+ loses trimmed whitespace, low-level formatting information, andthe distinction+ between normal data and CDATA nodes. Comments are only preservedwhen enabled.+ A write-read cycle loses trimmed whitespace; that is, if theorigin tree+ has string data that starts or ends with whitespace, thatwhitespace is lost.

+      </p>
+<p>

+XML的存储编码并不是一个完美的循环。一次读-写循环会丢失前置和后置的空白符、+低级的格式化信息，以及普通数据与CDATA节点间的差异。注释仅在激活时被保留。+一次写-读循环则会丢失前置和后置的空白符；即，如果原树中有以空白符开头或结尾+的字符串数据，则空白符会丢掉。

+      </p>
+</div>
+<div class="section" lang="en">
+<div class="titlepage"><div><div><h3 class="title">

+<a name="boost_propertytree.parsers.json_parser__json_________"></a><aclass="link"href="parsers.html#boost_propertytree.parsers.json_parser__json_________"title="JSON Parser JSON分析器">JSON

+      Parser JSON&#20998;&#26512;&#22120;</a>
+</h3></div></div></div>
+<p>

+ The <a href="http://en.wikipedia.org/wiki/JSON"; target="_top">JSONformat</a> is+ a data interchange format derived from the object literal notationof JavaScript.+ (JSON stands for JavaScript Object Notation.) JSON is a simple,compact format+ for loosely structured node trees of any depth, very similar tothe property+ tree dataset. It is less stuctured than XML and has no schemasupport, but+ has the advantage of being simpler, smaller and typed without theneed for

+        a complex schema.
+      </p>
+<p>

+ <a href="http://en.wikipedia.org/wiki/JSON"; target="_top">JSONformat</a> 是派生自+ JavaScript的对象文字记法的一种数据交换格式(JSON意为 JavaScript+ Object Notation)。 JSON是针对松散结构的、任意深度的节点树的一种简单、紧凑的格式，非常类似于属性树数据集。+与XML相比，它具有更少的结构性，且不支持schema，但却具有更简单、更小、带类型、+不需要复杂schema的优点。

+      </p>
+<p>

+ The property tree dataset is not typed, and does not supportarrays as such.

+        Thus, the following JSON / property tree mapping is used:
+      </p>
+<p>

+属性树数据集是无类型的，且不支持数组。因此，要用到以下JSON/属性树映射：

+      </p>
+<div class="itemizedlist"><ul type="disc">
+<li>

+ JSON objects are mapped to nodes. Each property is a childnode. + JSON对象映射至节点。每个属性是一个子节点。

+        </li>
+<li>

+ JSON arrays are mapped to nodes. Each element is a child nodewith an empty+ name. If a node has both named and unnamed child nodes, itcannot be mapped+ to a JSON representation. JSON数组映射至节点。每个元素是一个无名的子节点。如果一个节点既有命名的子节点，+也有无名的子节点，则它不能被映射至JSON表示法。

+        </li>
+<li>

+ JSON values are mapped to nodes containing the value. However,all type

+          information is lost; numbers, as well as the literals "null",
+          "true" and "false" are simply mapped to their string

+ form. JSON值被映射至含有值的节点。但是，所有类型信息会丢失；数字以及字面值+ "null", "true" 和 "false"被映射至它们的字符串形式。

+        </li>
+<li>

+ Property tree nodes containing both child nodes and data cannotbe mapped. +属性树节点同时包含子节点和不能被映射的数据。

+        </li>
+</ul></div>
+<p>
+        JSON round-trips, except for the type information loss.
+      </p>
+<p>

+ JSON是可循环的，除了类型信息会丢失。

+      </p>
+<p>
+        For example this JSON:
+      </p>
+<p>
+        &#20363;&#22914;&#65292;&#20197;&#19979;JSON&#65306;
+      </p>
+<pre class="programlisting"><span class="special">{</span>
+   <span class="string">"menu"</span><span class="special">:</span>
+   <span class="special">{</span>

+ "foo":true,+ "bar":"true",+ "value":102.3E+06,

+      <span class="string">"popup"</span><span class="special">:</span>
+      <span class="special">[</span>

+ {<spanclass="string">"value": <spanclass="string">"New", <spanclass="string">"onclick": <spanclass="string">"CreateNewDoc()"},+ {<spanclass="string">"value": <spanclass="string">"Open", <spanclass="string">"onclick": <spanclass="string">"OpenDoc()"},

+      <span class="special">]</span>
+   <span class="special">}</span>
+<span class="special">}</span>
+</pre>
+<p>
+        will be translated into the following property tree:
+      </p>
+<p>

+将被翻译为如下属性树：

+      </p>
+<pre class="programlisting"><span class="identifier">menu</span>
+<span class="special">{</span>
+   <span class="identifier">foo</span> <span class="keyword">true</span>
+   <span class="identifier">bar</span> <span class="keyword">true</span>

+ value <spanclass="number">102.3E+06

+   <span class="identifier">popup</span>
+   <span class="special">{</span>
+      <span class="string">""</span>
+      <span class="special">{</span>

+ value <spanclass="identifier">New+ onclick <spanclass="identifier">CreateNewDoc()

+      <span class="special">}</span>
+      <span class="string">""</span>
+      <span class="special">{</span>

+ value <spanclass="identifier">Open+ onclick <spanclass="identifier">OpenDoc()

+      <span class="special">}</span>
+   <span class="special">}</span>
+<span class="special">}</span>
+</pre>
+</div>
+<div class="section" lang="en">
+<div class="titlepage"><div><div><h3 class="title">

+<a name="boost_propertytree.parsers.ini_parser__ini_________"></a><aclass="link"href="parsers.html#boost_propertytree.parsers.ini_parser__ini_________"title="INI Parser INI分析器">INI

+      Parser INI&#20998;&#26512;&#22120;</a>
+</h3></div></div></div>
+<p>

+ The <a href="http://en.wikipedia.org/wiki/INI"; target="_top">INIformat</a> was+ once widely used in the world of Windows. It is now deprecated,but is still+ used by a surprisingly large number of applications. The reason isprobably+ its simplicity, plus that Microsoft recommends using the registryas a replacement,

+        which not all developers want to do.
+      </p>
+<p>

+ <a href="http://en.wikipedia.org/wiki/INI"; target="_top">INIformat</a>曾经在Windows世界中被广泛使用。现在已经不建议使用，但仍然被大量应用程序使用。+原因可能是由于它的简单性，加上Microsoft建议使用registry作为替代，但不是所有开发都愿意。

+      </p>
+<p>

+ INI is a simple key-value format with a single level ofsectioning. It is+ thus less rich than the property tree dataset, which means thatnot all property

+        trees can be serialized as INI files.
+      </p>
+<p>

+ INI是一种简单的键-值格式，只有section一个层级。因此，它不如属性树数据集，+这意味着不是所有属性树都可以序列化为INI文件。

+      </p>
+<p>

+ The INI parser creates a tree node for every section, and a childnode for+ every property in that section. All properties not in a sectionare directly+ added to the root node. Empty sections are ignored. (They don'tround-trip,

+        as described below.)
+      </p>
+<p>

+INI分析器为每个section创建一个树节点，section中的每个属性成为一个子节点。+所有不在section中的属性被直接添加至根节点。空的section被略过。+(它不是可循环的，如后所述)。

+      </p>
+<p>

+ The INI serializer reverses this process. It first writes outevery child+ of the root that contains data, but no child nodes, as properties.Then it+ creates a section for every child that contains child nodes, butno data.+ The children of the sections must only contain data. It is anerror if the+ root node contains data, or any child of the root contains bothdata and+ content, or there's more than three levels of hierarchy. Theremust also

+        not be any duplicate keys.
+      </p>
+<p>

+INI序列化器则将此过程逆转。它首先写出根的每个带有数据而没有子节点的子节点，作为属性。+然后为每个带有子节点而没有数据的子节点创建一个section。section的子节点则只能包含数据。+如果根节点包含数据，或者根的子节点同时包含数据和内容，或者超过三层，则为错误。+此外，还必须没有重复的键。

+      </p>
+<p>

+ An empty tree node is assumed to be an empty property. There is noway to

+        create empty sections.
+      </p>
+<p>

+空的树节点被假定为一个空的属性。没有办法创建一个空的section。

+      </p>
+<p>

+ Since the Windows INI parser discards trailing spaces and does notsupport+ quoting, the property tree parser follows this example. This meansthat property

+        values containing trailing spaces do not round-trip.
+      </p>
+<p>

+ 由于WindowsINI分析器忽略后随空格，且不支持引号，所以属性树分析器也遵循此例。+这意味着包含后随空格的属性值将不能完全恢复。

+      </p>
+</div>
+<div class="section" lang="en">
+<div class="titlepage"><div><div><h3 class="title">

+<a name="boost_propertytree.parsers.info_parser__info_________"></a><aclass="link"href="parsers.html#boost_propertytree.parsers.info_parser__info_________"title="INFO Parser INFO分析器">INFO

+      Parser INFO&#20998;&#26512;&#22120;</a>
+</h3></div></div></div>
+<p>

+ The INFO format was created specifically for the property treelibrary. It+ provides a simple, efficient format that can be used to serializeproperty+ trees that are otherwise only stored in memory. It can also beused for any+ other purpose, although the lack of widespread existing use mayprove to

+        be an impediment.
+      </p>
+<p>

+INFO格式是专为这个属性树库创建的。它提供一个简单、高效的格式，可用于对属性树进行序列化，+而不是仅仅保存在内存中。它还可用于其它目的，虽然目前缺乏广泛的使用可能会被证明是一个障碍。

+      </p>
+<p>

+ INFO provides several features that make it familiar to C++programmers and+ efficient for medium-sized datasets, especially those used fortest input.+ It supports C-style character escapes, nesting via curly braces,and file

+        inclusion via #include.
+      </p>
+<p>

+INFO提供了几个特性，更贴近于C++程序员且对中型数据集更高效，尤其是那些用于测试输入的数据。+它支持C风格的字符转义、大括号的嵌套，和#include的文件包含。

+      </p>
+<p>

+ INFO is also used for visualization of property trees in thisdocumentation.

+      </p>
+<p>

+INFO也被用于本文档中的属性树展示。

+      </p>
+<p>
+        A typical INFO file might look like this:
+      </p>
+<p>

+一个典型的INFO文件看起来象这样：

+      </p>

+<pre class="programlisting">key1 <spanclass="identifier">value1

+<span class="identifier">key2</span>
+<span class="special">{</span>

+ key3 <spanclass="identifier">value3

+   <span class="special">{</span>

+ key4 "value4with spaces"

+   <span class="special">}</span>

+ key5 <spanclass="identifier">value5

+<span class="special">}</span>
+</pre>
+<p>

+ Here's a more complicated file demonstrating all of INFO'sfeatures:

+      </p>
+<p>

+以下是一个更为复杂的文件，示范了INFO的所有特性：

+      </p>

+<pre class="programlisting">; <spanclass="identifier">A comment+key1 <spanclass="identifier">value1 ; <spanclass="identifier">Another comment+key2 "value withspecial characters in it {};#\n\t\"\0"

+<span class="special">{</span>

+ subkey "valuesplit "\+ "over three"<spanclass="special">\

+          <span class="string">"lines"</span>
+   <span class="special">{</span>

+ a_key_without_value <spanclass="string">""+ "a key with special characters in it{};#\n\t\"\0" ""+ "" <spanclass="identifier">value ; <spanclass="identifier">Empty key <spanclass="identifier">with a <spanclass="identifier">value+ "" ""; Empty <spanclass="identifier">key with <spanclass="identifier">empty value<spanclass="special">!

+   <span class="special">}</span>
+<span class="special">}</span>

+#include <spanclass="string">"file.info" ; <spanclass="identifier">included file

+</pre>
+<p>

+ INFO round-trips except for the loss of comments and includedirectives.

+      </p>
+<p>

+INFO是可循环的，除了会丢失注释以及include指令。

+      </p>
+</div>
+<div class="orderedlist"><ol type="1">
+<li>
+        These parsers will be dropped for now.
+      </li>
+<li>
+        [include cmd_line_parser.qbk]
+      </li>
+<li>
+        [include windows_registry_parser.qbk]
+      </li>
+<li>
+        [include system_environment_parser.qbk]
+      </li>
+</ol></div>
+</div>

+<table xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision";width="100%"><tr>

+<td align="left"></td>

+      </p>
+</div></td>
+</tr></table>
+<hr>
+<div class="spirit-nav">

+</div>
+</body>
+</html>
=======================================
--- /dev/null

+++ /trunk/doc/html/boost_propertytree/synopsis.html Thu Dec 24 17:59:332009

@@ -0,0 +1,84 @@
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">

+<title>Property Tree Synopsis属性树概要</title>

+<link rel="stylesheet" href="../boostbook.css" type="text/css">
+<meta name="generator" content="DocBook XSL Stylesheets V1.73.2">

+<link rel="start" href="../index.html" title="Boost C++库 BoostBook文档子集">+<link rel="up" href="../property_tree.html"title="Chapter 14. Boost.PropertyTree">+<link rel="prev" href="container.html" title="Property Tree as a Container作为容器的属性树">+<link rel="next" href="parsers.html" title="How to Populate a PropertyTree 如何填充属性树">

+</head>

+<body bgcolor="white" text="black" link="#0000FF" vlink="#840084"alink="#0000FF">

+<table cellpadding="2" width="100%"><tr>

+<td valign="top"><img alt="Boost C++ Libraries" width="277" height="86"src="../../../boost.png"></td>

+<td align="center"><a href="../../../index.html">Home</a></td>
+<td align="center"><a href="../../../libs/libraries.htm">Libraries</a></td>

+<td align="center"><ahref="http://www.boost.org/users/people.html";>People</a></td>+<td align="center"><ahref="http://www.boost.org/users/faq.html";>FAQ</a></td>

+<td align="center"><a href="../../../more/index.htm">More</a></td>
+</tr></table>
+<hr>
+<div class="spirit-nav">

+<a accesskey="p" href="container.html"><imgsrc="../../../doc/html/images/prev.png" alt="Prev"></a><a accesskey="u"href="../property_tree.html"><img src="../../../doc/html/images/up.png"alt="Up"></a><a accesskey="h" href="../index.html"><imgsrc="../../../doc/html/images/home.png" alt="Home"></a><a accesskey="n"href="parsers.html"><img src="../../../doc/html/images/next.png"alt="Next"></a>

+</div>
+<div class="section" lang="en">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">

+<a name="boost_propertytree.synopsis"></a><a class="link"href="synopsis.html" title="Property Tree Synopsis属性树概要"> Property Tree Synopsis属性树概要</a>

+</h2></div></div></div>
+<p>

+ The central component of the library is the <codeclass="computeroutput"><a class="link"href="../boost/property_tree/basic_ptree.html" title="Class templatebasic_ptree">basic_ptree</a></code>+ class template. Instances of this class are property trees. It isparametrized+ on key and data type, and key comparison policy; <codeclass="computeroutput"><a class="link"href="../boost/property_tree/ptree.html" title="Type definitionptree">ptree</a></code>,+ <code class="computeroutput"><a class="link"href="../boost/property_tree/wptree.html" title="Type definitionwptree">wptree</a></code>, <code class="computeroutput"><a class="link"href="../boost/property_tree/iptree.html" title="Type definitioniptree">iptree</a></code> and <code class="computeroutput"><a class="link"href="../boost/property_tree/wiptree.html" title="Type definitionwiptree">wiptree</a></code>+ are typedefs of <code class="computeroutput"><a class="link"href="../boost/property_tree/basic_ptree.html" title="Class templatebasic_ptree">basic_ptree</a></code>+ using predefined combinations of template parameters. Property treeis basically+ a somewhat simplified standard container (the closest beingstd::list), plus+ a bunch of extra member functions. These functions allow easy andeffective+ access to the data stored in property tree. They are variousvariants of <code class="computeroutput"><a class="link"href="../boost/property_tree/basic_ptree.html#id4952447-bb">get</a></code>,<code class="computeroutput"><a class="link"href="../boost/property_tree/basic_ptree.html#id5224647-bb">put</a></code>,<code class="computeroutput"><a class="link"href="../boost/property_tree/basic_ptree.html#id4900427-bb">get_value</a></code>,+ <code class="computeroutput"><a class="link"href="../boost/property_tree/basic_ptree.html#id4626767-bb">put_value</a></code>,+ <code class="computeroutput"><a class="link"href="../boost/property_tree/basic_ptree.html#id4892379-bb">get_child</a></code>,+ <code class="computeroutput"><a class="link"href="../boost/property_tree/basic_ptree.html#id4900339-bb">put_child</a></code>.+ Additionally, there is <code class="computeroutput"><a class="link"href="../boost/property_tree/basic_ptree.html#id4718615-bb">data</a></code>

+      function to access node data directly.
+    </p>
+<p>

+ 本库的核心组件是<code class="computeroutput"><a class="link"href="../boost/property_tree/basic_ptree.html" title="Class templatebasic_ptree">basic_ptree</a></code>+类模板。该类的实例就是属性树。它按键类型和数据类型，+以及键值比较策略进行参数化；<codeclass="computeroutput"><a class="link"href="../boost/property_tree/ptree.html" title="Type definitionptree">ptree</a></code>,+ <code class="computeroutput"><a class="link"href="../boost/property_tree/wptree.html" title="Type definitionwptree">wptree</a></code>, <code class="computeroutput"><a class="link"href="../boost/property_tree/iptree.html" title="Type definitioniptree">iptree</a></code> 和<code class="computeroutput"><aclass="link" href="../boost/property_tree/wiptree.html" title="Typedefinition wiptree">wiptree</a></code>+ 分别为各个模板参数的不同预定义组合的<code class="computeroutput"><a class="link"href="../boost/property_tree/basic_ptree.html" title="Class templatebasic_ptree">basic_ptree</a></code>+ 的typedef。基本上，属性树是一个简化的标准容器(最接近于+std::list)，加上一组额外的成员函数。这些函数可以让你方便且快速地+访问保存在属性树中的数据。它们分别是<code class="computeroutput"><a class="link"href="../boost/property_tree/basic_ptree.html#id4952447-bb">get</a></code>,+ <code class="computeroutput"><a class="link"href="../boost/property_tree/basic_ptree.html#id5224647-bb">put</a></code>,+ <code class="computeroutput"><a class="link"href="../boost/property_tree/basic_ptree.html#id4900427-bb">get_value</a></code>,+ <code class="computeroutput"><a class="link"href="../boost/property_tree/basic_ptree.html#id4626767-bb">put_value</a></code>,+ <code class="computeroutput"><a class="link"href="../boost/property_tree/basic_ptree.html#id4892379-bb">get_child</a></code>,+ <code class="computeroutput"><a class="link"href="../boost/property_tree/basic_ptree.html#id4900339-bb">put_child</a></code>+的各种变体。另外，还有一个<code class="computeroutput"><a class="link"href="../boost/property_tree/basic_ptree.html#id4718615-bb">data</a></code>+函数用于直接访问节点数据。

+    </p>
+<p>

+ See the <code class="computeroutput"><a class="link"href="../boost/property_tree/basic_ptree.html" title="Class templatebasic_ptree">basic_ptree class

+      template synopsis</a></code> for more information.
+    </p>
+<p>

+ 更多信息请参见 <codeclass="computeroutput"><a class="link"href="../boost/property_tree/basic_ptree.html" title="Class templatebasic_ptree">basic_ptree

+      &#31867;&#27169;&#26495;&#27010;&#35201;</a></code>&#12290;
+    </p>
+</div>

+<table xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision";width="100%"><tr>

+<td align="left"></td>

+      </p>
+</div></td>
+</tr></table>
+<hr>
+<div class="spirit-nav">

+</div>
+</body>
+</html>
=======================================
--- /dev/null

+++ /trunk/doc/html/boost_propertytree/tutorial.html Thu Dec 24 17:59:332009

@@ -0,0 +1,196 @@
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">

+<title>Five Minute Tutorial五分钟教程</title>

+<link rel="stylesheet" href="../boostbook.css" type="text/css">
+<meta name="generator" content="DocBook XSL Stylesheets V1.73.2">

+<link rel="start" href="../index.html" title="Boost C++库 BoostBook文档子集">+<link rel="up" href="../property_tree.html"title="Chapter 14. Boost.PropertyTree">+<link rel="prev" href="../property_tree.html"title="Chapter 14. Boost.PropertyTree">+<link rel="next" href="container.html" title="Property Tree as a Container作为容器的属性树">

+</head>

+<body bgcolor="white" text="black" link="#0000FF" vlink="#840084"alink="#0000FF">

+<table cellpadding="2" width="100%"><tr>

+<td valign="top"><img alt="Boost C++ Libraries" width="277" height="86"src="../../../boost.png"></td>

+<td align="center"><a href="../../../index.html">Home</a></td>
+<td align="center"><a href="../../../libs/libraries.htm">Libraries</a></td>

+<td align="center"><ahref="http://www.boost.org/users/people.html";>People</a></td>+<td align="center"><ahref="http://www.boost.org/users/faq.html";>FAQ</a></td>

+<td align="center"><a href="../../../more/index.htm">More</a></td>
+</tr></table>
+<hr>
+<div class="spirit-nav">

+<a accesskey="p" href="../property_tree.html"><imgsrc="../../../doc/html/images/prev.png" alt="Prev"></a><a accesskey="u"href="../property_tree.html"><img src="../../../doc/html/images/up.png"alt="Up"></a><a accesskey="h" href="../index.html"><imgsrc="../../../doc/html/images/home.png" alt="Home"></a><a accesskey="n"href="container.html"><img src="../../../doc/html/images/next.png"alt="Next"></a>

+</div>
+<div class="section" lang="en">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">

+<a name="boost_propertytree.tutorial"></a><a class="link"href="tutorial.html" title="Five Minute Tutorial五分钟教程"> Five Minute Tutorial五分钟教程</a>

+</h2></div></div></div>
+<p>

+ This tutorial uses XML. Note that the library is not specificallybound to+ XML, and any other supported format (such as INI or JSON) could beused instead.+ XML was chosen because the author thinks that wide range of peopleis familiar

+      with it.
+    </p>
+<p>

+本教程使用XML。注意，本库并不是特别与XML绑定的，你可以使用其它可支持的格式+(如INI或JSON)来代替。选择XML只是因为作者认为大多数人比较熟悉它。

+    </p>
+<p>

+ Suppose we are writing a logging system for some application, andneed to read+ log configuration from a file when the program starts. The file withthe log

+      configuration looks like this:
+    </p>
+<p>

+假设我们正在为某个应用程序编写一个日志系统，需要在程序启动时从某个文件读入日志的配置。+日志配置文件看起来可能会象这样：

+    </p>
+<pre class="programlisting">&lt;debug&gt;
+    &lt;filename&gt;debug.log&lt;/filename&gt;
+    &lt;modules&gt;
+        &lt;module&gt;Finance&lt;/module&gt;
+        &lt;module&gt;Admin&lt;/module&gt;
+        &lt;module&gt;HR&lt;/module&gt;
+    &lt;/modules&gt;
+    &lt;level&gt;2&lt;/level&gt;
+&lt;/debug&gt;
+</pre>
+<p>

+ It contains the log filename, a list of modules where logging isenabled, and+ the debug level value. To store the logging configuration in theprogram we

+      created a debug_settings structure:
+    </p>
+<p>

+它包含日志文件名，一串由要打开日志功能的模块所组成的列表，以及调试级别值。+为了在程序中保存这些日志配置信息，我们创建一个debug_settings

+      &#32467;&#26500;&#65306;
+    </p>

+<pre class="programlisting">struct <spanclass="identifier">debug_settings

+<span class="special">{</span>

+ std<spanclass="special">::string <spanclass="identifier">m_file;// log filename日志文件名+ int <spanclass="identifier">m_level<spanclass="special">; // debuglevel 调试级别+ std<spanclass="special">::set<spanclass="special"><string<spanclass="special">> m_modules<spanclass="special">; // modules where logging isenabled要打开日志功能的模块+ void <spanclass="identifier">load(<spanclass="keyword">const std<spanclass="special">::string <spanclass="special">&filename<spanclass="special">);+ void <spanclass="identifier">save(<spanclass="keyword">const std<spanclass="special">::string <spanclass="special">&filename<spanclass="special">);

+<span class="special">};</span>
+</pre>
+<p>

+ All that needs to be done now is to write implementations of load()and save()+ member functions. Let's first deal with load(). It contains just 7lines of+ code, although it does all the necessary things, including errorreporting:

+    </p>
+<p>

+现在要做的就是，编写load() 和 save()成员函数的实现。我们首先来看+ load()。它只包含7行代码，就可以完成所有必要的工作，包括错误报告：

+    </p>

+<pre class="programlisting"> #include<boost<spanclass="special">/property_tree<spanclass="special">/ptree<spanclass="special">.hpp<spanclass="special">>+ #include <spanclass="special"><boost<spanclass="special">/property_tree<spanclass="special">/xml_parser<spanclass="special">.hpp<spanclass="special">>

+ // Loads debug_settings structure from thespecified XML file+//从指定的XML文件中导入debug_settings 结构+ void <spanclass="identifier">debug_settings<spanclass="special">::load<spanclass="special">(const <spanclass="identifier">std::<spanclass="identifier">string &<spanclass="identifier">filename)

+   <span class="special">{</span>

+ // Create an empty property tree object创建一个空的属性树对象+ using <spanclass="identifier">boost::<spanclass="identifier">property_tree::<codeclass="computeroutput"><a class="link"href="../boost/property_tree/ptree.html" title="Type definitionptree">ptree</a></code>;+ <code class="computeroutput"><a class="link"href="../boost/property_tree/ptree.html" title="Type definitionptree">ptree</a></code> pt<spanclass="special">;

+ // Load the XML file into the property tree.If reading fails+ // (cannot open file, parse error), anexception is thrown.+ //将XML文件导入属性树。如果读入失败(不能打开文件，或分析错误)，则抛出异常+ <code class="computeroutput"><a class="link"href="../boost/property_tree/xml_parser/read_xml_id5271168.html"title="Function template read_xml">read_xml</a></code><spanclass="special">(filename<spanclass="special">, pt<spanclass="special">);

+ // Get the filename and store it in them_file variable.+ // Note that we construct the path tothe value by separating+ // the individual keys with dots. Ifdots appear in the keys,+ // a path type with a differentseparator can be used.+ // If the debug.filename key is notfound, an exception is thrown.+ //获得文件名并将它保存到m_file变量。注意，我们用以点号分隔的键值+ //来构建访问该值的路径。如果在键值中有点号，则需使用其它分隔符。+ // 如果 debug.filename键值没有被找到，则抛出异常。+ m_file <spanclass="special">= pt<spanclass="special">.<code class="computeroutput"><a class="link"href="../boost/property_tree/basic_ptree.html#id4952447-bb">get</a></code><spanclass="special"><std<spanclass="special">::string<spanclass="special">>(<spanclass="string">"debug.filename");

+ // Get the debug level and store it in them_level variable.+ // This is another version of the getmethod: if the value is+ // not found, the default value(specified by the second+ // parameter) is returned instead. Thetype of the value+ // extracted is determined by the typeof the second parameter,+ // so we can simply write get(...)instead of get<int>(...).+ //获得调试级别并将它保存到m_level 变量。这是 get方法的另一个版本：+ //如果要获取的值没有找到，则返回缺省值(由第二个参数指定)代替。+ //获取的值的类型由第二个参数的类型决定，所以我们只要写get(...)，+ // 而不用写get<int>(...).+ m_level <spanclass="special">= pt<spanclass="special">.<code class="computeroutput"><a class="link"href="../boost/property_tree/basic_ptree.html#id4952447-bb">get</a></code><spanclass="special">("debug.level"<spanclass="special">, 0<spanclass="special">);

+ // Iterate over the debug.modules section andstore all found+ // modules in the m_modules set. Theget_child() function+ // returns a reference to the child atthe specified path; if+ // there is no such child, it throws.Property tree iterators

+</span>       <span class="comment">// are models of BidirectionalIterator.

+ // 遍历 debug.modules节并将所有找到的模块保存至m_modules 集合中。+ // 函数 get_child()返回指定路径上的子节点的引用；如果该子节点不存在，+ //则抛出异常。属性树迭代器为双向迭代器。+ BOOST_FOREACH<spanclass="special">(<code class="computeroutput"><a class="link"href="../boost/property_tree/ptree.html" title="Type definitionptree">ptree</a></code>::<codeclass="computeroutput"><a class="link"href="../boost/property_tree/basic_ptree.html#boost.property_tree.basic_ptree.value_type">value_type</a></code>&v<spanclass="special">,+ pt<spanclass="special">.<code class="computeroutput"><a class="link"href="../boost/property_tree/basic_ptree.html#id4892379-bb">get_child</a></code><spanclass="special">("debug.modules"<spanclass="special">))+ m_modules<spanclass="special">.<code class="computeroutput"><a class="link"href="../boost/property_tree/basic_ptree.html#id5270779-bb">insert</a></code><spanclass="special">(v<spanclass="special">.second<spanclass="special">.data<spanclass="special">());

+   <span class="special">}</span>
+</pre>
+<p>
+      Now the save() function. It is also 7 lines of code:
+    </p>
+<p>

+ 接下来是 save()函数。它也是7行代码：

+    </p>

+<pre class="programlisting">// Saves thedebug_settings structure to the specified XML file+// 将 debug_setting结构保存至指定的XML文件+void <spanclass="identifier">debug_settings<spanclass="special">::save<spanclass="special">(const <spanclass="identifier">std::<spanclass="identifier">string &<spanclass="identifier">filename)

+<span class="special">{</span>

+ // Put log filename in property tree将日志文件名存入属性树+ pt<spanclass="special">.<code class="computeroutput"><a class="link"href="../boost/property_tree/basic_ptree.html#id5224647-bb">put</a></code><spanclass="special">("debug.filename"<spanclass="special">, m_file<spanclass="special">);

+ // Put debug level in property tree将调试级别存入属性树+ pt<spanclass="special">.<code class="computeroutput"><a class="link"href="../boost/property_tree/basic_ptree.html#id5224647-bb">put</a></code><spanclass="special">("debug.level"<spanclass="special">, m_level<spanclass="special">);

+ // Iterate over the modules in the set and putthem in the+ // property tree. Note that the putfunction places the new+ // key at the end of the list of keys.This is fine most of+ // the time. If you want to place an itemat some other place+ // (i.e. at the front or somewhere in themiddle), this can+ // be achieved using a combination of theinsert and put_own

+</span>   <span class="comment">// functions.

+//遍历集合中的模块并将它们存入属性树中。注意，函数put 将新插入的+//键值置于列表的尾端。多数时候这样很好。如果你想将某一项置于其它位+//置(例如在前端或中间)，可以用insert 和 put_own函数的组合来解决。+ BOOST_FOREACH<spanclass="special">(const <spanclass="identifier">std::<spanclass="identifier">string &<spanclass="identifier">name, <spanclass="identifier">m_modules)+ pt<spanclass="special">.<code class="computeroutput"><a class="link"href="../boost/property_tree/basic_ptree.html#id5224647-bb">put</a></code><spanclass="special">(<spanclass="string">"debug.modules.module",name, <spanclass="keyword">true);

+ // Write the property tree to the XML file.将属性树写出至XML文件。+ <code class="computeroutput"><a class="link"href="../boost/property_tree/xml_parser/write_xml_id4884059.html"title="Function template write_xml">write_xml</a></code><spanclass="special">(filename<spanclass="special">, pt<spanclass="special">);

+<span class="special">}</span>
+</pre>
+<p>

+ The full program <ahref="../../../libs/property_tree/examples/debug_settings.cpp"target="_top">debug_settings.cpp</a>

+      is included in the examples directory.
+    </p>
+<p>

+ 完整的程序 <ahref="../../../libs/property_tree/examples/debug_settings.cpp"target="_top">debug_settings.cpp</a>

+      &#22312; examples &#30446;&#24405;&#19979;&#12290;
+    </p>
+</div>

+<table xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision";width="100%"><tr>

+<td align="left"></td>

+      </p>
+</div></td>
+</tr></table>
+<hr>
+<div class="spirit-nav">

+</div>
+</body>
+</html>
=======================================
--- /dev/null

+++ /trunk/doc/html/property_tree/appendices_______.html Thu Dec 2417:59:33 2009

@@ -0,0 +1,149 @@
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<title>Appendices &#38468;&#24405;</title>
+<link rel="stylesheet" href="../boostbook.css" type="text/css">
+<meta name="generator" content="DocBook XSL Stylesheets V1.73.2">

+<link rel="start" href="../index.html" title="Boost C++库 BoostBook文档子集">+<link rel="up" href="../property_tree.html"title="Chapter 14. Boost.PropertyTree">+<link rel="prev" href="../boost_propertytree/accessing.html" title="How toAccess Data in a Property Tree如何访问属性树中的数据">

+<link rel="next" href="reference.html" title="Reference">
+</head>

+<body bgcolor="white" text="black" link="#0000FF" vlink="#840084"alink="#0000FF">

+<table cellpadding="2" width="100%"><tr>

+<td valign="top"><img alt="Boost C++ Libraries" width="277" height="86"src="../../../boost.png"></td>

+<td align="center"><a href="../../../index.html">Home</a></td>
+<td align="center"><a href="../../../libs/libraries.htm">Libraries</a></td>

+<td align="center"><ahref="http://www.boost.org/users/people.html";>People</a></td>+<td align="center"><ahref="http://www.boost.org/users/faq.html";>FAQ</a></td>

+<td align="center"><a href="../../../more/index.htm">More</a></td>
+</tr></table>
+<hr>
+<div class="spirit-nav">

+<a accesskey="p" href="../boost_propertytree/accessing.html"><imgsrc="../../../doc/html/images/prev.png" alt="Prev"></a><a accesskey="u"href="../property_tree.html"><img src="../../../doc/html/images/up.png"alt="Up"></a><a accesskey="h" href="../index.html"><imgsrc="../../../doc/html/images/home.png" alt="Home"></a><a accesskey="n"href="reference.html"><img src="../../../doc/html/images/next.png"alt="Next"></a>

+</div>
+<div class="section" lang="en">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">

+<a name="property_tree.appendices_______"></a><a class="link"href="appendices_______.html" title="Appendices附录">Appendices 附录</a>

+</h2></div></div></div>
+<a name="property_tree.appendices_______.compatibility__________"></a><h4>
+<a name="id5743978"></a>

+ <a class="link"href="appendices_______.html#property_tree.appendices_______.compatibility__________">Compatibility

+      &#20860;&#23481;&#24615;</a>
+    </h4>
+<p>

+ Property tree uses partial class template specialization. There hasbeen no+ attempt to work around lack of support for this. The library willtherefore

+      most probably not work with Visual C++ 7.0 or earlier, or gcc 2.x.
+    </p>
+<p>

+属性树使用了类模板偏特化。并且没有试图对不支持此特性的编译器采用变通方法。+因此本库很可能不能用于Visual C++ 7.0及其更早的版本，或者

+      gcc 2.x&#12290;
+    </p>
+<p>

+ Property tree has been tested (regressions successfully compiled andrun) with

+      the following compilers:
+    </p>
+<p>

+属性树已在以下编译器下通过测试(回归测试编译及运行成功)：

+    </p>
+<div class="itemizedlist"><ul type="disc">
+<li>
+        Visual C++ 8.0
+      </li>
+<li>
+        gcc 3.4.2 (MinGW)
+      </li>
+<li>
+        gcc 3.3.5 (Linux)
+      </li>
+<li>
+        gcc 3.4.4 (Linux)
+      </li>
+<li>
+        gcc 4.3.3 (Linux)
+      </li>
+<li>
+        Intel C++ 9.0 (Linux)
+      </li>
+</ul></div>
+<a name="property_tree.appendices_______.rationale_______"></a><h4>
+<a name="id5744058"></a>

+ <a class="link"href="appendices_______.html#property_tree.appendices_______.rationale_______">Rationale

+      &#21407;&#29702;</a>
+    </h4>
+<div class="orderedlist"><ol type="1">
+<li>

+Why are there 3 versions of <codeclass="computeroutput"><a class="link"href="../boost/property_tree/basic_ptree.html#id4952447-bb">get</a></code>?+ Couldn't there be just one? The three versionsreflect experience+ gathered during several of years of using property tree in severaldifferent+ applications. During that time I tried hard to come up with one,proper form+ of the get function, and failed. I know of these three basicpatterns of+ usage: <spanclass="bold">为什么有3个版本的<code class="computeroutput"><a class="link"href="../boost/property_tree/basic_ptree.html#id4952447-bb">get</a></code>?能否只有一个?+这三个版本体现了这几年在不同应用程序中使用属性树所得到的一些经验。+在这段时间内，我努力尝试得到一个适当形式的get 函数，都失败了。+我知道有三种基本的使用模式：

+        <div class="itemizedlist"><ul type="disc">
+<li>

+Just get the data and I do not care if itcannot be done.+ This is used when the programmer is fairly sure that dataexists. Or+ in homework assignments. Or when tomorrow is final deadlinefor your+ project. <spanclass="emphasis">只要获取数据而不关心它是否不可行。+这通常用于程序员相当肯定数据会存在的情况。或是功课任务的情况。或是明天是项目最后限期的情况。

+          </li>
+<li>

+Get the data and revert to default value if itcannot be done.+ Used when you want to allow omitting the key in question.Implemented+ by some similar tools (windows INI file accessfunctions). <spanclass="emphasis">获取数据且在数据不可用时使用缺省值。+适用于想要允许忽略键值的情况。某些类似工具已实现(windows

+            INI &#25991;&#20214;&#35775;&#38382;&#20989;&#25968;)&#12290;
+          </li>
+<li>

+Get the data, but I care more whether yousucceeded than I+ do for the data itself. Used when you want to varycontrol+ flow depending on get success/failure. Or to check forpresence of a+ key. <spanclass="emphasis">获取数据，但与数据本身相比，更关注是否成功获取。+适用于需要根据数据获取的成功/失败来调整控制流的情况。或是检查某个键是否存在的情况。

+          </li>
+</ul></div>
+</li>
+<li>

+Why does the separator character come beforethe path+ and not after as one would expect? It helps withoverload resolution+ in some cases. <spanclass="bold">为什么分隔符在路径之前而非之后?+在某些情形下，这有助于重载决议。

+      </li>
+</ol></div>

+<aname="property_tree.appendices_______.future_development________________"></a><h4>

+<a name="id5744232"></a>

+ <a class="link"href="appendices_______.html#property_tree.appendices_______.future_development________________">Future

+      Development &#26410;&#26469;&#30340;&#24320;&#21457;</a>
+    </h4>
+<div class="itemizedlist"><ul type="disc">
+<li>

+ More parsers: YAML, environment strings. 更多分析器：YAML,环境变量字符串。

+      </li>
+<li>

+ More robust XML parser. 更健全的XML分析器。

+      </li>
+<li>

+ Mathematical relations: ptree difference, union, intersection.Useful for+ finding configuration file changes etc. 数学运算：ptree的差集、并集、交集。用于查找配置文件的变化等。

+      </li>
+</ul></div>
+</div>

+<table xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision";width="100%"><tr>

+<td align="left"></td>

+      </p>
+</div></td>
+</tr></table>
+<hr>
+<div class="spirit-nav">

+</div>
+</body>
+</html>
=======================================
--- /dev/null
+++ /trunk/libs/property_tree/doc/Jamfile.v2    Thu Dec 24 17:59:33 2009
@@ -0,0 +1,54 @@
+# Boost.PropertyTree
+#
+# Copyright (c) 2006-2007 Matias Capeletto
+#
+# Distributed under the Boost Software License, Version 1.0.
+# (See accompanying file LICENSE_1_0.txt or copy at
+# http://www.boost.org/LICENSE_1_0.txt)
+
+
+# Quickbook

+#-----------------------------------------------------------------------------

+
+import doxygen ;
+import quickbook ;
+doxygen autodoc
+    :
+        [ glob ../../../boost/property_tree/*.hpp ]
+    :
+        <doxygen:param>EXTRACT_ALL=YES

+ <doxygen:param>"PREDEFINED=\"BOOST_PROPERTY_TREE_DOXYGEN_INVOKED\"\\

+                                   \"BOOST_DEDUCED_TYPENAME=typename\""
+        <doxygen:param>HIDE_UNDOC_MEMBERS=NO
+        <doxygen:param>EXTRACT_PRIVATE=NO
+        <doxygen:param>ENABLE_PREPROCESSING=YES
+        <doxygen:param>MACRO_EXPANSION=YES
+        <doxygen:param>EXPAND_ONLY_PREDEF=YES
+        <doxygen:param>SEARCH_INCLUDES=YES
+        <doxygen:param>INCLUDE_PATH=$(BOOST_ROOT)

+<doxygen:param>EXAMPLE_PATH=$(BOOST_ROOT)/libs/property_tree/examples

+        <doxygen:param>BRIEF_MEMBER_DESC=YES
+        <doxygen:param>REPEAT_BRIEF=YES
+        <doxygen:param>ALWAYS_DETAILED_SEC=YES
+        <doxygen:param>MULTILINE_CPP_IS_BRIEF=YES
+    ;
+
+xml property_tree : property_tree.qbk ;
+
+boostbook standalone
+    : property_tree
+    : <xsl:param>html.stylesheet=../../../../doc/html/boostbook.css
+      <xsl:param>boost.root=../../../..
+      <xsl:param>boost.libraries=../../../libraries.htm
+      <xsl:param>toc.max.depth=3
+      <xsl:param>toc.section.depth=2
+      <xsl:param>chunk.section.depth=3
+      <dependency>autodoc

+<format>pdf:<xsl:param>boost.url.prefix=http://www.boost.org/doc/libs/release/libs/functional/hash/doc/html

+    ;
+
+#install ../
+#    : ../../../boost.png
+#      ../../../next.png
+#      ../../../prev.png
+#    ;
=======================================
--- /dev/null
+++ /trunk/libs/property_tree/doc/accessing.qbk Thu Dec 24 17:59:33 2009
@@ -0,0 +1,126 @@
+[/

+ /

+ / Distributed under the Boost Software License, Version 1.0. (Seeaccompanying

+ / file LICENSE_1_0.txt or copy at http://www.boost.org/LICENSE_1_0.txt)
+ /]

+[section:accessing How to Access Data in a Property Tree 如何访问属性树中的数据]

+[/ __ptree_*__ macros expected from property_tree.qbk]
+[def __pi__ ['pi]] [/ mathematical constant]
+

+Property tree resembles (almost is) a standard container with value typeof `pair<string, ptree>`. It has the usual member functions, such as__ptree_insert__, __ptree_push_back__, __ptree_find__, __ptree_erase__,etc. These can of course be used to populate and access the tree. Forexample the following code adds key `"pi"` with data (almost) equal tomathematical __pi__ value:

+属性树类似于(几乎就是)一个值类型为 `pair<string, ptree>` 的标准容器。它具有通常的成员函数，+如 __ptree_insert__, __ptree_push_back__, __ptree_find__, __ptree_erase__,等等。+这些函数当然都可以用于填充和访问树中的数据。例如以下代码增加一个键值`"pi"`，

+所带的数据(几乎)等于数学的 __pi__ 值：
+
+ __ptree__ pt;

+ pt.__ptree_push_back__(__ptree__::__ptree_value_type__("pi",__ptree__("3.14159")));

+
+To find the value of `pi` we might do the following:
+
+要查找 `pi` 的值，我们可以这样做：
+
+ __ptree__::__ptree_const_iterator__ it = pt.__ptree_find__("pi");
+ double pi = boost::lexical_cast<double>(it->second._ptree_data__());
+

+This looks quite cumbersome, and would be even more so if `pi` value wasnot stored so near the top of the tree, and we cared just a little bit moreabout errors. Fortunately, there is another, correct way of doing it:

+
+这看起来非常笨重，而且如果 `pi` 值不是被存储在靠近树的顶端位置则更是如此，
+而我们关心的只比错误多一点。幸好，我们有另一个正确的方法来做这件事：
+
+ ptree pt;
+ pt.__ptree_put__("pi", 3.14159);                // put double
+ double pi = pt.__ptree_get__<double>("pi");     // get double
+

+It doesn't get simpler than that. Basically, there are 2 families ofmember functions, __ptree_get__ and __ptree_put__, which allow intuitiveaccess to data stored in the tree (direct children or not).

+没有什么比这更简单了。基本上，我们有2个成员函数族，__ptree_get__ 和__ptree_put__,

+它们可以直观地访问树中的数据(直接或非直接的子节点)。
+
+[heading Three Ways of Getting Data 获取数据的三种方法]
+

+There are three versions of get: get, get (default-value version), andget_optional, which differ by failure handling strategy. All versions takepath specifier, which determines in which key to search for a value. It canbe a single key, or a path to key, where path elements are separated with aspecial character (a '.' if not specified differently). For exampledebug.logging.errorlevel might be a valid path with dot as a separator.

+有三个版本的 get: get, get (缺省值版本), 以及 get_optional, 它的失败处理策略有所不同。+所有版本均接受路径指定符，用于确定在哪个键中查找值。它可以是单个键值，或是到键值的路径，+路径中的各元素用一个特定字符(若未特别指定就是'.')分隔。例如debug.logging.errorlevel

+就可能是一个以点号作为分隔符的有效路径。
+
+# The throwing version (__ptree_get__) 抛出版本的(__ptree_get__):
+``
+__ptree__ pt;
+/* ... */
+float v = pt.__ptree_get__<float>("a.path.to.float.value");
+``

+This call locates the proper node in the tree and tries to translate itsdata string to a float value. If that fails, exception is thrown. If pathdoes not exist, it will be __ptree_bad_path__ exception. If value could notbe translated, it will be __ptree_bad_data__. Both of them derive from__ptree_error__ to make common handling possible.[br]+这个调用定位至树中的正确节点，并尝试将其数据字符串翻译为浮点值。如果失败则抛出异常。+如果路径不存在，则是 __ptree_bad_path__ 异常。如果值不能被翻译，则是__ptree_bad_data__ 异常。

+这两个异常均派生自 __ptree_error__，可以一同处理。

+# The default-value version (__ptree_get_defaulted__) 缺省值版本的(__ptree_get_defaulted__):

+``
+__ptree__ pt;
+/* ... */
+float v = pt.__ptree_get_defaulted__("a.path.to.float.value", -1.f);
+``

+It will do the same as above, but if it fails, it will return the defaultvalue specified by second parameter (here -1.f) instead of throwing. Thisis very useful in common situations where one wants to allow omitting ofsome keys. Note that type specification needed in throwing version isnormally not necessary here, because type is determined by the defaultvalue parameter.[br]+其作用与上一个版本相同，不过如果操作失败将返回由第二个参数所指定的缺省值(在这里是-1.f)，

+而非抛出异常。在那些允许忽略某些键的一般情况下，这个版本非常有用。

+注意，在抛出版本中必须指定类型而在此版本中则不必，因为类型可以通过缺省值参数来推断。+# The optional version (__ptree_get_optional__) 可选版本的(__ptree_get_optional__):

+``
+__ptree__ pt;
+/* ... */

+boost::optional<float> v =pt.__ptree_get_optional__<float>("a.path.to.float.value");

+``

+This version uses boost::optional class to handle extraction failure. Onsuccessful extraction, it will return boost::optional initialized withextracted value. Otherwise, it will return uninitializedboost::optional.[br]

+这个版本使用 boost::optional 类来处理获取数据的失败。当成功获取时，

+它将返回由获得值初始化的 boost::optional。否则，它将返回未初始化的boost::optional。

+To retrieve value from this tree (not some subkey), use__ptree_get_value__, __ptree_get_value__ (default-value version), and__ptree_get_value_optional__. They have identical semantics to__ptree_get__ functions, except they don't take the __path__ parameter.Don't call __ptree_get__ with and empty __path__ to do this as it will tryto extract contents of subkey with empty name.

+要从树中(不是某个子键)获取值，请用 __ptree_get_value__,__ptree_get_value__ (缺省值版本)，+和 __ptree_get_value_optional__。它们具有与 __ptree_get__ 函数相同的语义，除了一点，+它们不接受 __path__ 参数。不要用空的 __path__ 来调用 __ptree_get__，这样做将会取出带有空名的子键的内容。

+To use separator character other than default '[^.]', each of the__ptree_get__ versions has another form, which takes an additionalparameter in front of path. This parameter of type `char/wchar_t` specifiesthe separating character. This is a lifesaving device for those who mayhave dots in their keys:

+要使用缺省分隔符 '[^.]' 以外的其它分隔符，则每个 __ptree_get__ 版本都有一个其它的格式，+它在路径之前接受多一个参数。该参数的类型为 `char/wchar_t`，给定用于分隔的字符。

+以下适用于那些在键名中带有点号的情况：
+
+ pt.get<float>('/', "p.a.t.h/t.o/v.a.l.u.e");
+ pt.get('/', "p.a.t.h/t.o/v.a.l.u.e", 0, NULL);
+ pt.get_optional<std::string>('/', "p.a.t.h/t.o/v.a.l.u.e");
+
+[heading One Way of Putting Data 写入数据的一种方法]
+

+To complement __ptree_get__, there is a __ptree_put__ function. Contraryto __ptree_get__, it has only one variant. The reason is, there is no needto handle put failures so often (normally, __ptree_put__ will only fail ifconversion of the supplied value to __ptree_data_type__ fails or the systemruns out of memory. In the former case, __ptree_put__ will throw__ptree_bad_data__). Sample usage of __ptree_put__ might appear as:

+相对于 __ptree_get__，有一个 __ptree_put__ 函数。与 __ptree_get__ 相比，它只有一个版本。+原因是，通常没有必要处理写入的失败(通常，__ptree_put__ 仅当从给定值到__ptree_data_type__+的转换失败，或系统内存溢出时才会失败。对于前一种情况，__ptree_put__ 将抛出__ptree_bad_data__)。

+以下为 __ptree_put__ 的使用例子：
+
+ __ptree__ pt;
+ pt.__ptree_put__("a.path.to.float.value", 3.14f);
+

+Calling __ptree_put__ will insert a new value at specified path, so that acall to __ptree_get__ specifying the same path will retrieve it. Further,__ptree_put__ will insert any missing path elements during path traversal.For example, calling `__ptree_put__("key1.key2.key3", 3.14f)` on an emptytree will insert three new children: `key1`, `key1.key2` and`key1.key2.key3`. The last one will receive a string `"3.14"` as data,while the two former ones will have empty data strings. __ptree_put__always inserts new keys at the back of the existing sequences.

+调用 __ptree_put__ 将在指定路径插入一个新值，此后对同一路径调用__ptree_get__ 将取回该值。+而且，__ptree_put__ 会在路径遍历期间插入所有不存在的路径。例如，对一棵空树调用+`__ptree_put__("key1.key2.key3", 3.14f)` 将插入三个新的子节点：`key1`,`key1.key2`+和 `key1.key2.key3`。最后一个子节点将接收一个字符串 `"3.14"` 作为数据，而前两个则为空数据串。

+__ptree_put__ 总是将新的键插入到已有序列的末端。
+

+Similar to __ptree_get_value__, there is also a __ptree_put_value__function. It does the same for this property tree what __ptree_put__ doesfor its children. Thus, it does not require __path__:

+
+类似于 __ptree_get_value__，也有一个 __ptree_put_value__ 函数。

+它对于属性树的作用与 __ptree_put__ 对于子节点的作用一样。因此，它不需要__path__：

+
+ __ptree__ pt;
+ pt.__ptree_put_own__(3.14f);
+
+[endsect]
=======================================
--- /dev/null

+++ /trunk/libs/property_tree/doc/cmd_line_parser.qbk Thu Dec 24 17:59:332009

@@ -0,0 +1,80 @@
+[/

+ /

+ / Distributed under the Boost Software License, Version 1.0. (Seeaccompanying

+ / file LICENSE_1_0.txt or copy at http://www.boost.org/LICENSE_1_0.txt)
+ /]
+[section:cmdline_parser Command Line Parser]

+[def __read_cmdline__ [funcrefboost::property_tree::cmdline_parser::read_cmdline read_cmdline]]+This is a simple parser that converts command line parameters (in form ofstandard `argc` and `argv` arguments) into a property tree. There is nowrite function. The parser correctly recognizes simple command line styles,both from Unix and Windows worlds.

+During parse, parameters are converted to __ptree__ keys and grouped bytheir prefix, if any. Grouping means that they are inserted as children ofa key representing appropriate group. Prefix is a single character thatcomes directly after so called "metacharacter", which is usually a dash '-'(on Unix) or a slash '/' (on Windows). For example, parameter[^-I/usr/include/foobar] has prefix [^I] after metacharacter '[^-]'.Parameters that do not start with a metacharacter (e.g. source files givento gcc), are inserted as children of a special, unnamed group.Additionally, data of each group contains value of last parameter assignedto that group. For example, this command line:

+[pre myprogram.exe -c -I/usr/include -Lm -I/home/mammamia/stuff foo.cbar.c -g]

+
+will result in the following property tree being created:
+
+ "" bar.c                    ;"unnamed" group
+ {
+    "0" myprogram.exe        ;first argument is name of program
+    "1" foo.c
+    "2" bar.c
+ }
+ c                           ;no data
+ {
+    "0" ""                  ;no value associated with 'c' option
+ }
+ I /home/mammamia/stuff
+ {
+    "0" /usr/include
+    "1" /home/mammamia/stuff
+ }
+ L m
+ {
+    "0" m
+ }
+
+Within each group, parameters are numbered, starting from zero.
+

+Metacharacters can be specified as a parameter to read function. This codewill parse command line using both dash and slash as metachatacters:

+
+ __ptree__ pt;
+ __read_cmdline__(argc, argv, "-/", pt);
+

+Once the command line is parsed into a __ptree__, the power of the__ptree_get__, __ptree_get_child__, and __ptree_get_value__ interfaces canbe used to conveniently extract the values of options needed. In thesimplest case, user only needs to query key with name of option to get itsvalue. For example:

+
+ // default to 0 if -Nxx or /Nxx not specified on command line
+ int n = pt.__ptree_get_defaulted__("N", 0);
+
+or
+
+ // throw if -Nxx or /Nxx not specified on command line
+ int n = pt.__ptree_get__<int>("N");
+

+If there is more than one instance of 'N' in command line, they can beaccessed as:

+
+ // Copy values of all -N arguments to vector
+ std::vector<int> vec;

+ BOOST_FOREACH(const __ptree__::__ptree_value_type__ &v,pt.__ptree_get_child__("N", empty_ptree()))

+    vec.push_back(v.second.__ptree_get_value__<int>());
+
+or:
+
+ // Use numbering to access specific instances of parameter -N
+ int first_n = pt.__ptree_get_defaulted__("N.0", default_n_value);
+ int second_n = pt.__ptree_get_defaulted__("N.1", default_n_value);
+ /* ... */
+ int tenth_n = pt.__ptree_get_defaulted__("N.9", default_n_value);
+
+If you want to know how many [^-N]'s were specified:
+
+ // Count -N parameters
+ size_t count = pt.__ptree_get_child__("N", empty_ptree<ptree>()).size();
+

+First argument, `argv[0]`, normally contains path to executable, which israrely used for arguments parsing. To skip it, invoke the parser like inthe following manner:

+
+ // Skip program path
+ __read_cmdline__(argc - 1, argv + 1, "-", pt)
+
+[endsect] [/cmd_line_parser]
=======================================
--- /dev/null
+++ /trunk/libs/property_tree/doc/container.qbk Thu Dec 24 17:59:33 2009
@@ -0,0 +1,38 @@
+[/

+ /

+ / Distributed under the Boost Software License, Version 1.0. (Seeaccompanying

+ / file LICENSE_1_0.txt or copy at http://www.boost.org/LICENSE_1_0.txt)
+ /]
+[section:container Property Tree as a Container 作为容器的属性树]
+[/ __ptree_*__ macros expected from property_tree.qbk]
+Every property tree node models the ReversibleSequence concept, providing

+access to its immediate children. This means that iterating over a__ptree__

+(which is the same as its root node - every __ptree__ node is also the

+subtree it starts) iterates only a single level of the hierarchy. There isno

+way to iterate over the entire tree.
+

+每一个属性树节点都符合可逆序列概念，提供对其直接子节点的访问。这意味着遍历一个+__ptree__ (与根节点一样 - 每个 __ptree__ 节点同时也是从它开始的子树)只是遍历单个层级。

+没有方法直接遍历整棵树。
+

+It is very important to remember that the property sequence is *not*ordered by+the key. It preserves the order of insertion. It closely resembles astd::list.+Fast access to children by name is provided via a separate lookupstructure. Do not+attempt to use algorithms that expect an ordered sequence (likebinary_search)

+on a node's children.
+

+有一点很重要必须要记住，属性序列*并不是*按其键值排序的。它保留了插入的顺序。+它更接近于 std::list。按名字对子节点的快速访问，是通过一个独立的查找结构来提供的。

+不要试图对一个节点的子节点使用那些要求有序序列的算法(如 binary_search)。
+

+There may be multiple children with the same key value in a node. However,these+children are not necessarily sequential. The iterator returned by__ptree_find__

+may refer to any of these, and there are no guarantees about the relative
+position of the other equally named children.
+

+一个节点中可能会有多个子节点带有相同的键值。但是这些子节点间是没有先后顺序的。+__ptree_find__ 所返回的迭代器可能指向它们中的任意一个，而且对于其它相同名字的

+子节点的相对位置，也是没有保证的。
+[endsect] [/container]
=======================================
--- /dev/null
+++ /trunk/libs/property_tree/doc/info_parser.qbk       Thu Dec 24 17:59:33 2009
@@ -0,0 +1,68 @@
+[/

+ /

+ / Distributed under the Boost Software License, Version 1.0. (Seeaccompanying

+ / file LICENSE_1_0.txt or copy at http://www.boost.org/LICENSE_1_0.txt)
+ /]
+[section INFO Parser  INFO分析器]
+The INFO format was created specifically for the property tree library. It
+provides a simple, efficient format that can be used to serialize property
+trees that are otherwise only stored in memory. It can also be used for any

+other purpose, although the lack of widespread existing use may prove tobe an

+impediment.
+

+
+INFO provides several features that make it familiar to C++ programmers and

+efficient for medium-sized datasets, especially those used for test input.It+supports C-style character escapes, nesting via curly braces, and fileinclusion

+via #include.
+

+INFO提供了几个特性，更贴近于C++程序员且对中型数据集更高效，尤其是那些用于测试输入的数据。

+它支持C风格的字符转义、大括号的嵌套，和#include的文件包含。
+

+INFO is also used for visualization of property trees in thisdocumentation.

+
+INFO也被用于本文档中的属性树展示。
+
+A typical INFO file might look like this:
+
+一个典型的INFO文件看起来象这样：
+
+ key1 value1
+ key2
+ {
+    key3 value3
+    {
+       key4 "value4 with spaces"
+    }
+    key5 value5
+ }
+
+Here's a more complicated file demonstrating all of INFO's features:
+
+以下是一个更为复杂的文件，示范了INFO的所有特性：
+
+ ; A comment
+ key1 value1   ; Another comment
+ key2 "value with special characters in it {};#\n\t\"\0"
+ {
+    subkey "value split "\
+           "over three"\
+           "lines"
+    {
+       a_key_without_value ""
+       "a key with special characters in it {};#\n\t\"\0" ""
+       "" value    ; Empty key with a value
+       "" ""       ; Empty key with empty value!
+    }
+ }
+ #include "file.info"    ; included file
+
+INFO round-trips except for the loss of comments and include directives.
+
+INFO是可循环的，除了会丢失注释以及include指令。
+
+[endsect] [/info_parser]
=======================================
--- /dev/null
+++ /trunk/libs/property_tree/doc/ini_parser.qbk        Thu Dec 24 17:59:33 2009
@@ -0,0 +1,57 @@
+[/

+ /

+ / Distributed under the Boost Software License, Version 1.0. (Seeaccompanying

+ / file LICENSE_1_0.txt or copy at http://www.boost.org/LICENSE_1_0.txt)
+ /]
+[section INI Parser  INI分析器]
+[def __ini__ [@http://en.wikipedia.org/wiki/INI INI format]]

+The __ini__ was once widely used in the world of Windows. It is nowdeprecated,+but is still used by a surprisingly large number of applications. Thereason is+probably its simplicity, plus that Microsoft recommends using the registryas

+a replacement, which not all developers want to do.
+

+__ini__ 曾经在Windows世界中被广泛使用。现在已经不建议使用，但仍然被大量应用程序使用。+原因可能是由于它的简单性，加上Microsoft建议使用registry作为替代，但不是所有开发都愿意。

+INI is a simple key-value format with a single level of sectioning. It isthus

+less rich than the property tree dataset, which means that not all property
+trees can be serialized as INI files.
+
+INI 是一种简单的键-值格式，只有section一个层级。因此，它不如属性树数据集，
+这意味着不是所有属性树都可以序列化为INI文件。
+
+The INI parser creates a tree node for every section, and a child node for

+every property in that section. All properties not in a section aredirectly+added to the root node. Empty sections are ignored. (They don'tround-trip, as

+described below.)
+
+INI分析器为每个section创建一个树节点，section中的每个属性成为一个子节点。
+所有不在section中的属性被直接添加至根节点。空的section被略过。
+(它不是可循环的，如后所述)。
+

+The INI serializer reverses this process. It first writes out every childof the+root that contains data, but no child nodes, as properties. Then itcreates a+section for every child that contains child nodes, but no data. Thechildren of+the sections must only contain data. It is an error if the root nodecontains+data, or any child of the root contains both data and content, or there'smore

+than three levels of hierarchy. There must also not be any duplicate keys.
+

+INI序列化器则将此过程逆转。它首先写出根的每个带有数据而没有子节点的子节点，作为属性。+然后为每个带有子节点而没有数据的子节点创建一个section。section的子节点则只能包含数据。+如果根节点包含数据，或者根的子节点同时包含数据和内容，或者超过三层，则为错误。

+此外，还必须没有重复的键。
+

+An empty tree node is assumed to be an empty property. There is no way tocreate

+empty sections.
+
+空的树节点被假定为一个空的属性。没有办法创建一个空的section。
+
+Since the Windows INI parser discards trailing spaces and does not support
+quoting, the property tree parser follows this example. This means that
+property values containing trailing spaces do not round-trip.
+

+由于Windows INI分析器忽略后随空格，且不支持引号，所以属性树分析器也遵循此例。

+这意味着包含后随空格的属性值将不能完全恢复。
+[endsect] [/ini_parser]
=======================================
--- /dev/null
+++ /trunk/libs/property_tree/doc/intro.qbk     Thu Dec 24 17:59:33 2009
@@ -0,0 +1,54 @@
+[/

+ /

+ / Distributed under the Boost Software License, Version 1.0. (Seeaccompanying

+ / file LICENSE_1_0.txt or copy at http://www.boost.org/LICENSE_1_0.txt)
+ /]
+[template ptree2codeImage[] [$images/ptree2code.png]]
+[section:intro What is Property Tree? 属性树是什么？]

+The Property Tree library provides a data structure that stores anarbitrarily+deeply nested tree of values, indexed at each level by some key. Each nodeof+the tree stores its own value, plus an ordered list of its subnodes andtheir+keys. The tree allows easy access to any of its nodes by means of a path,which

+is a concatenation of multiple keys.
+

+Property Tree库提供了一种数据结构，用于保存任意嵌套层数的由值组成的树，每一层以+某个键值来索引。树的每个节点保存了它本身的值，以及一个由该节点的子节点及其键值+组成的有序列表。这种树可以通过类似于路径的方式很方便地访问任一节点，这个路径由

+多个键值串接而成。
+

+In addition, the library provides parsers and generators for a number ofdata+formats that can be represented by such a tree, including XML, INI, andJSON.

+此外，这个库还提供了一些分析器和生成器，对应于多种可用于表示一棵树的数据格式，

+如 XML, INI 和 JSON。
+

+Property trees are versatile data structures, but are particularly suitedfor+holding configuration data. The tree provides its own, tree-specificinterface,

+and each node is also an STL-compatible Sequence for its child nodes.
+

+属性树是多功能的数据结构，尤其适合用于保存配置数据。该树提供了它自己本身、树专用

+的接口，而且每个节点都是其子节点的一个STL兼容序列。
+
+Conceptually, then, a node can be thought of as the following structure:
+
+在概念上，一个节点可以想象为以下结构：
+
+   struct ptree
+   {

+ data_type data; // data associated with thenode 与节点相关联的数据+ list< pair<key_type, ptree> > children; // ordered list of namedchildren 命名子节点的有序列表

+   };
+

+Both key_type and data_type are configurable, but will usually bestd::string.

+
+key_type 和 data_type 都是可配置的，但通常都是 std::string。
+

+Many software projects develop a similar tool at some point of theirlifetime,+and property tree originated the same way. We hope the library can savemany

+from reinventing the wheel.
+

+许多软件项目都在它们生命周期中的某个时候开发过类似的工具，属性树正源自于此。

+我们希望这个库可以节省重复发明轮子的时间。
+[endsect] [/intro]
=======================================
--- /dev/null
+++ /trunk/libs/property_tree/doc/json_parser.qbk       Thu Dec 24 17:59:33 2009
@@ -0,0 +1,88 @@
+[/

+ /

+ / Distributed under the Boost Software License, Version 1.0. (Seeaccompanying

+ / file LICENSE_1_0.txt or copy at http://www.boost.org/LICENSE_1_0.txt)
+ /]
+[section JSON Parser  JSON分析器]
+[def __json__ [@http://en.wikipedia.org/wiki/JSON JSON format]]
+The __json__ is a data interchange format derived from the object literal
+notation of JavaScript. (JSON stands for JavaScript Object Notation.)

+JSON is a simple, compact format for loosely structured node trees of anydepth,+very similar to the property tree dataset. It is less stuctured than XMLand has+no schema support, but has the advantage of being simpler, smaller andtyped

+without the need for a complex schema.
+

+__json__ 是派生自 JavaScript 的对象文字记法的一种数据交换格式(JSON 意为JavaScript Object Notation)。+JSON 是针对松散结构的、任意深度的节点树的一种简单、紧凑的格式，非常类似于属性树数据集。+与XML相比，它具有更少的结构性，且不支持schema，但却具有更简单、更小、带类型、

+不需要复杂schema的优点。
+

+The property tree dataset is not typed, and does not support arrays assuch.

+Thus, the following JSON / property tree mapping is used:
+
+属性树数据集是无类型的，且不支持数组。因此，要用到以下JSON/属性树映射：
+
+* JSON objects are mapped to nodes. Each property is a child node.[br]
+  JSON 对象映射至节点。每个属性是一个子节点。

+* JSON arrays are mapped to nodes. Each element is a child node with anempty+ name. If a node has both named and unnamed child nodes, it cannot bemapped

+  to a JSON representation.[br]

+ JSON 数组映射至节点。每个元素是一个无名的子节点。如果一个节点既有命名的子节点，

+  也有无名的子节点，则它不能被映射至JSON表示法。
+* JSON values are mapped to nodes containing the value. However, all type
+  information is lost; numbers, as well as the literals "null", "true" and
+  "false" are simply mapped to their string form.[br]

+ JSON 值被映射至含有值的节点。但是，所有类型信息会丢失；数字以及字面值 "null",

+  "true" 和 "false" 被映射至它们的字符串形式。

+* Property tree nodes containing both child nodes and data cannot bemapped.[br]

+  属性树节点同时包含子节点和不能被映射的数据。
+
+JSON round-trips, except for the type information loss.
+
+JSON 是可循环的，除了类型信息会丢失。
+
+For example this JSON:
+
+例如，以下JSON：
+
+ {
+    "menu":
+    {
+       "foo": true,
+       "bar": "true",
+       "value": 102.3E+06,
+       "popup":
+       [
+          {"value": "New", "onclick": "CreateNewDoc()"},
+          {"value": "Open", "onclick": "OpenDoc()"},
+       ]
+    }
+ }
+
+will be translated into the following property tree:
+
+将被翻译为如下属性树：
+
+ menu
+ {
+    foo true
+    bar true
+    value 102.3E+06
+    popup
+    {
+       ""
+       {
+          value New
+          onclick CreateNewDoc()
+       }
+       ""
+       {
+          value Open
+          onclick OpenDoc()
+       }
+    }
+ }
+
+[endsect] [/json_parser]
=======================================
--- /dev/null
+++ /trunk/libs/property_tree/doc/parsers.qbk   Thu Dec 24 17:59:33 2009
@@ -0,0 +1,24 @@
+[/

+ /

+ / Distributed under the Boost Software License, Version 1.0. (Seeaccompanying

+ / file LICENSE_1_0.txt or copy at http://www.boost.org/LICENSE_1_0.txt)
+ /]
+[section:parsers How to Populate a Property Tree 如何填充属性树]
+[include xml_parser.qbk]
+
+[include json_parser.qbk]
+
+[include ini_parser.qbk]
+
+[include info_parser.qbk]
+
+# These parsers will be dropped for now.
+#[include cmd_line_parser.qbk]
+
+#[include windows_registry_parser.qbk]
+
+#[include system_environment_parser.qbk]
+
+[endsect] [/parsers]
=======================================
--- /dev/null
+++ /trunk/libs/property_tree/doc/property_tree.qbk     Thu Dec 24 17:59:33 2009
@@ -0,0 +1,139 @@
+[/

+ /

+ / Distributed under the Boost Software License, Version 1.0. (Seeaccompanying

+ / file LICENSE_1_0.txt or copy at http://www.boost.org/LICENSE_1_0.txt)
+ /]
+
+[library Boost.PropertyTree
+    [quickbook 1.4]
+    [copyright 2008 Marcin Kalicinski]
+    [purpose Property Tree library]
+    [license
+        Distributed under the Boost Software License, Version 1.0.
+        (See accompanying file LICENSE_1_0.txt or copy at
+        [@http://www.boost.org/LICENSE_1_0.txt])
+    ]
+    [authors [Kalicinski, Marcin]]
+    [id property_tree]
+    [dirname property_tree]
+    [category container]
+    [category template]
+]
+

+[/ Tried to use templates here but got errors expanding them in[classref ...] etc.]

+[/ types]
+[def __ptree__ [classref boost::property_tree::ptree ptree]]

+[def __ptree_value_type__ [classrefboost::property_tree::basic_ptree::value_type value_type]]+[def __ptree_data_type__ [classrefboost::property_tree::basic_ptree::data_type data_type]]+[def __ptree_iterator__ [classrefboost::property_tree::basic_ptree::iterator iterator]]+[def __ptree_const_iterator__ [classrefboost::property_tree::basic_ptree::const_iterator const_iterator]]

+[def __path__ [classref boost::property_tree::path path]]

+[def __ptree_error__ [classref boost::property_tree::ptree_errorptree_error]]+[def __ptree_bad_data__ [classref boost::property_tree::ptree_bad_dataptree_bad_data]]+[def __ptree_bad_path__ [classref boost::property_tree::ptree_bad_pathptree_bad_path]]

+
+[/ members]

+[def __ptree_insert__ [memberref boost::property_tree::basic_ptree::insertinsert]]+[def __ptree_push_back__ [memberrefboost::property_tree::basic_ptree::push_back push_back]]+[def __ptree_find__ [memberref boost::property_tree::basic_ptree::findfind]]+[def __ptree_erase__ [memberref boost::property_tree::basic_ptree::eraseerase]]+[def __ptree_find__ [memberref boost::property_tree::basic_ptree::findfind]]+[def __ptree_data__ [memberref boost::property_tree::basic_ptree::datadata]]+[def __ptree_push_front__ [memberrefboost::property_tree::basic_ptree::push_front push_front]]+[def __ptree_sort__ [memberref boost::property_tree::basic_ptree::sortsort]]

+[def __ptree_get__ [memberref boost::property_tree::basic_ptree::get get]]
+[/ XXX: Don't know how to specify overloads]

+[def __ptree_get_defaulted__ [memberrefboost::property_tree::basic_ptree::get get]]+[def __ptree_get_optional__ [memberrefboost::property_tree::basic_ptree::get_optional get_optional]]+[def __ptree_get_value__ [memberrefboost::property_tree::basic_ptree::get_value get_value]]

+[/ XXX: Don't know how to specify overloads]

+[def __ptree_get_value_defaulted__ [memberrefboost::property_tree::basic_ptree::get_value get_value]]+[def __ptree_get_value_optional__ [memberrefboost::property_tree::basic_ptree::get_value_optional get_value_optional]]+[def __ptree_get_child__ [memberrefboost::property_tree::basic_ptree::get_child get_child]]

+[def __ptree_put__ [memberref boost::property_tree::basic_ptree::put put]]

+[def __ptree_put_value__ [memberrefboost::property_tree::basic_ptree::put_value put_value]]

+
+[/ free-functions]

+[def __read_xml__ [funcref boost::property_tree::xml_parser::read_xmlread_xml]]+[def __write_xml__ [funcref boost::property_tree::xml_parser::write_xmlwrite_xml]]

+
+[include intro.qbk]
+
+[include tutorial.qbk]
+
+[include container.qbk]
+
+[include synopsis.qbk]
+
+[include parsers.qbk]
+
+[include accessing.qbk]
+
+[section Appendices 附录]
+[heading Compatibility 兼容性]
+Property tree uses partial class template specialization. There has been no
+attempt to work around lack of support for this. The library will therefore
+most probably not work with Visual C++ 7.0 or earlier, or gcc 2.x.
+
+属性树使用了类模板偏特化。并且没有试图对不支持此特性的编译器采用变通方法。
+因此本库很可能不能用于 Visual C++ 7.0 及其更早的版本，或者 gcc 2.x。
+
+Property tree has been tested (regressions successfully compiled and run)
+with the following compilers:
+
+属性树已在以下编译器下通过测试(回归测试编译及运行成功)：
+
+* Visual C++ 8.0
+* gcc 3.4.2 (MinGW)
+* gcc 3.3.5 (Linux)
+* gcc 3.4.4 (Linux)
+* gcc 4.3.3 (Linux)
+* Intel C++ 9.0 (Linux)
+
+[heading Rationale 原理]

+# [*Why are there 3 versions of __ptree_get__? Couldn't there be just one?]+The three versions reflect experience gathered during several of years ofusing+property tree in several different applications. During that time I triedhard

+to come up with one, proper form of the get function, and failed. I know of
+these three basic patterns of usage:[br]
+[*为什么有3个版本的 __ptree_get__? 能否只有一个?]
+这三个版本体现了这几年在不同应用程序中使用属性树所得到的一些经验。
+在这段时间内，我努力尝试得到一个适当形式的 get 函数，都失败了。
+我知道有三种基本的使用模式：
+

+ * ['Just get the data and I do not care if it cannot be done.] This isused

+   when the programmer is fairly sure that data exists. Or in homework
+   assignments. Or when tomorrow is final deadline for your project.[br]

+ ['只要获取数据而不关心它是否不可行。] 这通常用于程序员相当肯定数据会存在的情况。

+   或是功课任务的情况。或是明天是项目最后限期的情况。

+ * ['Get the data and revert to default value if it cannot be done.] Usedwhen+ you want to allow omitting the key in question. Implemented by somesimilar

+   tools (windows INI file access functions).[br]
+   ['获取数据且在数据不可用时使用缺省值。]  适用于想要允许忽略键值的情况。
+   某些类似工具已实现(windows INI 文件访问函数)。

+ * ['Get the data, but I care more whether you succeeded than I do for thedata

+   itself.] Used when you want to vary control flow depending on get
+   success/failure. Or to check for presence of a key.[br]

+ ['获取数据，但与数据本身相比，更关注是否成功获取。] 适用于需要根据数据获取的成功/失败

+   来调整控制流的情况。或是检查某个键是否存在的情况。
+
+# [*Why does the separator character come before the path and not after
+    as one would expect? ]
+It helps with overload resolution in some cases.[br]
+[*为什么分隔符在路径之前而非之后?]
+在某些情形下，这有助于重载决议。
+
+[heading Future Development 未来的开发]
+* More parsers:  YAML, environment strings.[br]
+  更多分析器：YAML, 环境变量字符串。
+* More robust XML parser.[br]
+  更健全的XML分析器。
+* Mathematical relations:  ptree difference, union, intersection.
+  Useful for finding configuration file changes etc.[br]
+  数学运算：ptree 的差集、并集、交集。用于查找配置文件的变化等。
+
+[endsect] [/ Appendices]
+
+[xinclude autodoc.xml]
=======================================
--- /dev/null
+++ /trunk/libs/property_tree/doc/synopsis.qbk  Thu Dec 24 17:59:33 2009
@@ -0,0 +1,45 @@
+[/

+ /

+ / Distributed under the Boost Software License, Version 1.0. (Seeaccompanying

+ / file LICENSE_1_0.txt or copy at http://www.boost.org/LICENSE_1_0.txt)
+ /]
+[section:synopsis Property Tree Synopsis 属性树概要]

+[def __basic_ptree__ [classref boost::property_tree::basic_ptreebasic_ptree]]

+[def __ptree__ [classref boost::property_tree::ptree ptree]]
+[def __wptree__ [classref boost::property_tree::wptree wptree]]
+[def __iptree__ [classref boost::property_tree::iptree iptree]]
+[def __wiptree__ [classref boost::property_tree::wiptree wiptree]]
+[/ basic_ptree members]
+[def __ptree_get__ [memberref boost::property_tree::basic_ptree::get get]]
+[def __ptree_put__ [memberref boost::property_tree::basic_ptree::put put]]

+[def __ptree_get_value__ [memberrefboost::property_tree::basic_ptree::get_value get_value]]+[def __ptree_put_value__ [memberrefboost::property_tree::basic_ptree::put_value put_value]]+[def __ptree_get_child__ [memberrefboost::property_tree::basic_ptree::get_child get_child]]+[def __ptree_put_child__ [memberrefboost::property_tree::basic_ptree::put_child put_child]]+[def __ptree_data__ [memberref boost::property_tree::basic_ptree::datadata]]

+The central component of the library is the __basic_ptree__ class template.

+Instances of this class are property trees. It is parametrized on key anddata

+type, and key comparison policy; __ptree__, __wptree__, __iptree__ and

+__wiptree__ are typedefs of __basic_ptree__ using predefined combinationsof+template parameters. Property tree is basically a somewhat simplifiedstandard

+container (the closest being std::list), plus a bunch of extra member

+functions. These functions allow easy and effective access to the datastored+in property tree. They are various variants of __ptree_get__,__ptree_put__,

+__ptree_get_value__, __ptree_put_value__, __ptree_get_child__,

+__ptree_put_child__. Additionally, there is __ptree_data__ function toaccess

+node data directly.
+

+本库的核心组件是 __basic_ptree__ 类模板。该类的实例就是属性树。它按键类型和数据类型，+以及键值比较策略进行参数化；__ptree__, __wptree__, __iptree__ 和__wiptree__ 分别为+各个模板参数的不同预定义组合的 __basic_ptree__ 的 typedef。基本上，属性树是一个简化的+标准容器(最接近于 std::list)，加上一组额外的成员函数。这些函数可以让你方便且快速地+访问保存在属性树中的数据。它们分别是 __ptree_get__, __ptree_put__,__ptree_get_value__,+__ptree_put_value__, __ptree_get_child__, __ptree_put_child__ 的各种变体。另外，还有一个

+__ptree_data__ 函数用于直接访问节点数据。
+

+See the [classref boost::property_tree::basic_ptree basic_ptree classtemplate synopsis] for more information.

+更多信息请参见 [classref boost::property_tree::basic_ptree basic_ptree 类模板概要]。

+[endsect]
=======================================
--- /dev/null

+++ /trunk/libs/property_tree/doc/system_environment_parser.qbk Thu Dec 2417:59:33 2009

@@ -0,0 +1,10 @@
+[/

+ /

+ / Distributed under the Boost Software License, Version 1.0. (Seeaccompanying

+ / file LICENSE_1_0.txt or copy at http://www.boost.org/LICENSE_1_0.txt)
+ /]
+[section System Environment Parser]
+[note The system environment parser is not yet implemented.]
+[endsect] [/env_parser]
=======================================
--- /dev/null
+++ /trunk/libs/property_tree/doc/tutorial.qbk  Thu Dec 24 17:59:33 2009
@@ -0,0 +1,149 @@
+[/

+ /

+ / Distributed under the Boost Software License, Version 1.0. (Seeaccompanying

+ / file LICENSE_1_0.txt or copy at http://www.boost.org/LICENSE_1_0.txt)
+ /]
+[section:tutorial Five Minute Tutorial 五分钟教程]

+This tutorial uses XML. Note that the library is not specifically bound toXML,

+and any other supported format (such as INI or JSON) could be used instead.

+XML was chosen because the author thinks that wide range of people isfamiliar

+with it.
+
+本教程使用XML。注意，本库并不是特别与XML绑定的，你可以使用其它可支持的格式
+(如INI或JSON)来代替。选择XML只是因为作者认为大多数人比较熟悉它。
+

+Suppose we are writing a logging system for some application, and need toread+log configuration from a file when the program starts. The file with thelog

+configuration looks like this:
+

+假设我们正在为某个应用程序编写一个日志系统，需要在程序启动时从某个文件读入日志的配置。

+日志配置文件看起来可能会象这样：
+
+[pre
+<debug>
+    <filename>debug.log</filename>
+    <modules>
+        <module>Finance</module>
+        <module>Admin</module>
+        <module>HR</module>
+    </modules>
+    <level>2</level>
+</debug>
+]
+

+It contains the log filename, a list of modules where logging is enabled,and

+the debug level value. To store the logging configuration in the program we
+created a debug_settings structure:
+
+它包含日志文件名，一串由要打开日志功能的模块所组成的列表，以及调试级别值。
+为了在程序中保存这些日志配置信息，我们创建一个 debug_settings 结构：
+
+   struct debug_settings
+   {
+       std::string m_file;          // log filename 日志文件名
+       int m_level;                 // debug level 调试级别

+ std::set<string> m_modules; // modules where logging is enabled 要打开日志功能的模块

+       void load(const std::string &filename);
+       void save(const std::string &filename);
+   };
+

+All that needs to be done now is to write implementations of load() andsave()

+member functions. Let's first deal with load(). It contains just 7 lines of
+code, although it does all the necessary things, including error reporting:
+
+现在要做的就是，编写 load() 和 save() 成员函数的实现。我们首先来看 load()。
+它只包含7行代码，就可以完成所有必要的工作，包括错误报告：
+
+    #include <boost/property_tree/ptree.hpp>
+    #include <boost/property_tree/xml_parser.hpp>
+
+    // Loads debug_settings structure from the specified XML file
+       // 从指定的XML文件中导入 debug_settings 结构
+    void debug_settings::load(const std::string &filename)
+    {
+        // Create an empty property tree object 创建一个空的属性树对象
+        using boost::property_tree::__ptree__;
+        __ptree__ pt;
+
+        // Load the XML file into the property tree. If reading fails
+        // (cannot open file, parse error), an exception is thrown.

+ // 将XML文件导入属性树。如果读入失败(不能打开文件，或分析错误)，则抛出异常

+        __read_xml__(filename, pt);
+
+        // Get the filename and store it in the m_file variable.
+        // Note that we construct the path to the value by separating
+        // the individual keys with dots. If dots appear in the keys,
+        // a path type with a different separator can be used.
+        // If the debug.filename key is not found, an exception is thrown.
+               // 获得文件名并将它保存到 m_file 变量。注意，我们用以点号分隔的键值
+               // 来构建访问该值的路径。如果在键值中有点号，则需使用其它分隔符。
+               // 如果 debug.filename 键值没有被找到，则抛出异常。
+        m_file = pt.__ptree_get__<std::string>("debug.filename");
+
+        // Get the debug level and store it in the m_level variable.
+        // This is another version of the get method: if the value is
+        // not found, the default value (specified by the second
+        // parameter) is returned instead. The type of the value
+        // extracted is determined by the type of the second parameter,
+        // so we can simply write get(...) instead of get<int>(...).
+               // 获得调试级别并将它保存到 m_level 变量。这是 get 方法的另一个版本：
+               // 如果要获取的值没有找到，则返回缺省值(由第二个参数指定)代替。
+               // 获取的值的类型由第二个参数的类型决定，所以我们只要写 get(...)，
+               // 而不用写 get<int>(...).
+        m_level = pt.__ptree_get__("debug.level", 0);
+
+        // Iterate over the debug.modules section and store all found
+        // modules in the m_modules set. The get_child() function
+        // returns a reference to the child at the specified path; if
+        // there is no such child, it throws. Property tree iterators
+        // are models of BidirectionalIterator.
+               // 遍历 debug.modules 节并将所有找到的模块保存至 m_modules 集合中。
+               // 函数 get_child() 返回指定路径上的子节点的引用；如果该子节点不存在，
+               // 则抛出异常。属性树迭代器为双向迭代器。
+        BOOST_FOREACH(__ptree__::__ptree_value_type__ &v,
+                pt.__ptree_get_child__("debug.modules"))
+            m_modules.__ptree_insert__(v.second.data());
+    }
+
+Now the save() function. It is also 7 lines of code:
+
+接下来是 save() 函数。它也是7行代码：
+
+   // Saves the debug_settings structure to the specified XML file
+   // 将 debug_setting 结构保存至指定的XML文件
+   void debug_settings::save(const std::string &filename)
+   {
+      // Create an empty property tree object 创建一个空的属性树对象
+      using boost::property_tree::__ptree__;
+      __ptree__ pt;
+
+      // Put log filename in property tree 将日志文件名存入属性树
+      pt.__ptree_put__("debug.filename", m_file);
+
+      // Put debug level in property tree 将调试级别存入属性树
+      pt.__ptree_put__("debug.level", m_level);
+
+      // Iterate over the modules in the set and put them in the
+      // property tree. Note that the put function places the new
+      // key at the end of the list of keys. This is fine most of
+      // the time. If you want to place an item at some other place
+      // (i.e. at the front or somewhere in the middle), this can
+      // be achieved using a combination of the insert and put_own
+      // functions.
+         // 遍历集合中的模块并将它们存入属性树中。注意，函数 put 将新插入的
+         // 键值置于列表的尾端。多数时候这样很好。如果你想将某一项置于其它位
+         // 置(例如在前端或中间)，可以用 insert 和 put_own 函数的组合来解决。
+      BOOST_FOREACH(const std::string &name, m_modules)
+         pt.__ptree_put__("debug.modules.module", name, true);
+
+      // Write the property tree to the XML file. 将属性树写出至XML文件。
+      __write_xml__(filename, pt);
+   }
+

+The full program [@boost:/libs/property_tree/examples/debug_settings.cppdebug_settings.cpp] is

+included in the examples directory.
+

+完整的程序 [@boost:/libs/property_tree/examples/debug_settings.cppdebug_settings.cpp] 在 examples 目录下。

+[endsect] [/tutorial]
=======================================
--- /dev/null

+++ /trunk/libs/property_tree/doc/windows_registry_parser.qbk Thu Dec 2417:59:33 2009

@@ -0,0 +1,45 @@
+[/

+ /

+ / Distributed under the Boost Software License, Version 1.0. (Seeaccompanying

+ / file LICENSE_1_0.txt or copy at http://www.boost.org/LICENSE_1_0.txt)
+ /]
+[section:registry_parser Windows Registry Parser]

+[def __registry_parser.hpp__ [headerrefboost/property_tree/registry_parser.hpp registry_parser.hpp]]+[def __read_registry__ [funcrefboost::property_tree::registry_parser::read_registry read_registry]]+[def __translate__ [funcrefboost::property_tree::registry_parser::translate translate]]+[def __write_registry__ [funcrefboost::property_tree::registry_parser::write_registry write_registry]]+This parser supports reading and writing data from Windows registry. Thereis only a subset of registry functionality implemented, because propertytree is not intended to replace registry API. For example, access rightsare not supported, as well as some exotic value formats. Registry is a richdata source, providing hierarchy of keys, each of whose can have any numberof named and typed values attached to it. Because of that - like in XML -some translation is necessary.

+[important This parser will only work on a Windows system because it usesWindows API to access the registry. You will need to link with[^advapi32.lib]. A minimalist version of the [^windows.h] Windows headerfile is included by __registry_parser.hpp__. If you want to include[^windows.h] header on your own, do it before including__registry_parser.hpp__.]

+[heading How Registry Keys are Translated to Property Trees(__read_registry__):]

+* Values of each registry key are stored in a subkey with name [^\values].The preceding backslash is there to prevent name clashes with regular keys.Each subkey of [^\values] is one registry value. If [^\values] subkey doesnot exist or is empty, there are no values attached to that key.+* Types of values of each registry key are stored in a subkey with name[^\types]. These subkeys contain an integer equal to type of data stored inits corresponding entry in [^\values] (correspondence is by name, notposition).+* So called "default value" (value attached to key itself), is translateddirectly to key data and is always assumed to be of type [^REG_SZ].+* [^REG_BINARY] values are translated to textual format before placing inproperty tree. The format is the same as the one displayed by regeditapplication: a series of two-digit hexadecimal numbers representing bytesseparated with spaces. To translate from this format to binary data, orvice versa, use the __translate__ function.+* Supported value types are: [^REG_NONE], [^REG_SZ], [^REG_EXPAND_SZ],[^REG_DWORD], [^REG_QWORD], [^REG_BINARY].

+Translation of property tree back into registry (__write_registry__)assumes the same structure as outlined above. That means if you want tohave named values, you need to create [^\values] and [^\types] subkeys, andput them there. Also, you have to convert all [^REG_BINARY] values totextual format. Passing "normal" property tree (i.e. not containing[^\types] and [^\values] keys) to the __write_registry__ function will putall data in "default value" section of each key. This is fine, especiallyif you intend to read this data using property tree, but is probably not astandard way of storing things in the registry.

+For example, when you read registry key[^HKEY_CURRENT_USER\Software\Microsoft\Notepad], under Windows XP, you willget property tree containing Notepad font settings (among other things):

+
+ Notepad
+ {
+    \values
+    {
+       lfFaceName  Courier
+       lfItalic    0
+       lfWeight    190
+    }
+    \types
+    {
+       lfFaceName  1  ; REG_SZ
+       lfItalic    4  ; REG_DWORD
+       lfWeight    4  ; REG_DWORD
+    }
+ }
+
+[endsect] [/win_reg_parser]
=======================================
--- /dev/null
+++ /trunk/libs/property_tree/doc/xml_parser.qbk        Thu Dec 24 17:59:33 2009
@@ -0,0 +1,81 @@
+[/

+ /

+ / Distributed under the Boost Software License, Version 1.0. (Seeaccompanying

+ / file LICENSE_1_0.txt or copy at http://www.boost.org/LICENSE_1_0.txt)
+ /]
+[section XML Parser  XML分析器]
+[def __xml__ [@http://en.wikipedia.org/wiki/XML XML format]]

+[def __xml_parser.hpp__ [headerref boost/property_tree/xml_parser.hppxml_parser.hpp]]

+[def __RapidXML__ [@http://rapidxml.sourceforge.net/ RapidXML]]
+[def __boost__ [@http://www.boost.org Boost]]
+The __xml__ is an industry standard for storing information in textual
+form. Unfortunately, there is no XML parser in __boost__ as of the
+time of this writing. The library therefore contains the fast and tiny

+__RapidXML__ parser (currently in version 1.13) to provide XML parsingsupport.+RapidXML does not fully support the XML standard; it is not capable ofparsing

+DTDs and therefore cannot do full entity substitution.
+

+__xml__ 是以文本方式保存信息的工业标准。不幸的是，目前在 __boost__ 还没有XML分析器。+因此，本库包含了一个小而快的 __RapidXML__ 分析器(当前版本为 1.13)以提供XML分析的支持。

+RapidXML 并不完全支持XML标准；它不能分析DTDs，因此不能实现完全的实体替换。
+

+By default, the parser will preserve most whitespace, but remove elementcontent

+that consists only of whitespace. Encoded whitespaces (e.g. &#32;) does not

+count as whitespace in this regard. You can pass the trim_whitespace flagif you+want all leading and trailing whitespace trimmed and all continuouswhitespace

+collapsed into a single space.
+
+缺省情况下，这个分析器会保留最多的空白符，但会删掉仅包含空白符的元素内容。

+在此，编码的空白符(如  )并不被算作空白符。如果你想去掉所有前置和后置的空白符，

+且将所有连续的空白符压缩为单个空格，可以传入 trim_whitespace 标志。
+

+Please note that RapidXML does not understand the encoding specification.If

+you pass it a character buffer, it assumes the data is already correctly

+encoded; if you pass it a filename, it will read the file using thecharacter+conversion of the locale you give it (or the global locale if you give itnone).+This means that, in order to parse a UTF-8-encoded XML file into a wptree,you+have to supply an alternate locale, either directly or by replacing theglobal

+one.
+

+请注意，RapidXML 并不了解编码规范。如果你传入一个字符缓冲区，它会假定其中的数据已正确编码；+如果你传入一个文件名，它将使用你给定的locale (如果你没有给定，则使用全局locale)的字符转换。+这意味着，为了分析一个UTF-8编码的XML文件并存入 wptree，你必须提供一个替代locale，

+或者直接提供，或者替换掉全局locale。
+
+XML / property tree conversion schema (__read_xml__ and __write_xml__):
+
+XML/属性树转换机制(__read_xml__ and __write_xml__)：
+
+* Each XML element corresponds to a property tree node. The child elements
+  correspond to the children of the node.[br]
+  每个XML元素对应于一个属性树节点。子元素对应于该节点的子节点。

+* The attributes of an XML element are stored in the subkey [^<xmlattr>].There

+  is one child node per attribute in the attribute node. Existence of the

+ [^<xmlattr>] node is not guaranteed or necessary when there are noattributes.[br]+ 一个XML元素的属性被保存于子键 [^<xmlattr>] 中。在属性节点中每个属性有一个子节点。

+  当没有属性时，并不保证也不需要一定有 [^<xmlattr>] 节点。
+* XML comments are stored in nodes named [^<xmlcomment>], unless comment
+  ignoring is enabled via the flags.[br]

+ XML注释被保存于名为 [^<xmlcomment>] 的节点中，除非用标志位激活了忽略注释。+* Text content is stored in one of two ways, depending on the flags. Thedefault

+  way concatenates all text nodes and stores them in a single node called

+ [^<xmltext>]. This way, the entire content can be conveniently read, butthe+ relative ordering of text and child elements is lost. The other waystores

+  each text content as a separate node, all called [^<xmltext>].[br]

+ 文本内容以两种方法中的一种进行保存，由标志位决定。缺省的方法是将所有文本节点串接起来，+ 将它们保存在单个名为 [^<xmltext>] 的节点中。这种方法方便读取整个内容，但文本的相对顺序+ 以及子元素全部丢失。另一种方法是，将每个文本内容保存为单个节点，均命名为[^<xmltext>]。

+The XML storage encoding does not round-trip perfectly. A read-write cycleloses

+trimmed whitespace, low-level formatting information, and the distinction

+between normal data and CDATA nodes. Comments are only preserved whenenabled.+A write-read cycle loses trimmed whitespace; that is, if the origin treehas

+string data that starts or ends with whitespace, that whitespace is lost.
+
+XML的存储编码并不是一个完美的循环。一次读-写循环会丢失前置和后置的空白符、
+低级的格式化信息，以及普通数据与CDATA节点间的差异。注释仅在激活时被保留。
+一次写-读循环则会丢失前置和后置的空白符；即，如果原树中有以空白符开头或结尾
+的字符串数据，则空白符会丢掉。
+[endsect] [/xml_parser]
=======================================
--- /trunk/doc/html/property_tree/appendices.html       Sun Dec 20 18:38:58 2009
+++ /dev/null
@@ -1,130 +0,0 @@
-<html>
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<title>Appendices</title>
-<link rel="stylesheet" href="../boostbook.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.75.2">

-<link rel="home" href="../index.html" title="The Boost C++ LibrariesBoostBook Documentation Subset">-<link rel="up" href="../property_tree.html"title="Chapter 14. Boost.PropertyTree">-<link rel="prev" href="../boost_propertytree/accessing.html" title="How toAccess Data in a Property Tree">

-<link rel="next" href="reference.html" title="Reference">
-</head>

-<body bgcolor="white" text="black" link="#0000FF" vlink="#840084"alink="#0000FF">

-<table cellpadding="2" width="100%"><tr>

-<td valign="top"><img alt="Boost C++ Libraries" width="277" height="86"src="../../../boost.png"></td>

-<td align="center"><a href="../../../index.html">Home</a></td>
-<td align="center"><a href="../../../libs/libraries.htm">Libraries</a></td>

-<td align="center"><ahref="http://www.boost.org/users/people.html";>People</a></td>-<td align="center"><ahref="http://www.boost.org/users/faq.html";>FAQ</a></td>

-<td align="center"><a href="../../../more/index.htm">More</a></td>
-</tr></table>
-<hr>
-<div class="spirit-nav">

-<a accesskey="p" href="../boost_propertytree/accessing.html"><imgsrc="../../../doc/html/images/prev.png" alt="Prev"></a><a accesskey="u"href="../property_tree.html"><img src="../../../doc/html/images/up.png"alt="Up"></a><a accesskey="h" href="../index.html"><imgsrc="../../../doc/html/images/home.png" alt="Home"></a><a accesskey="n"href="reference.html"><img src="../../../doc/html/images/next.png"alt="Next"></a>

-</div>
-<div class="section" title="Appendices">
-<div class="titlepage"><div><div><h2 class="title" style="clear: both">

-<a name="property_tree.appendices"></a><a class="link"href="appendices.html" title="Appendices">Appendices</a>

-</h2></div></div></div>
-<a name="property_tree.appendices.compatibility"></a><h4>
-<a name="id1426614"></a>

- <a class="link"href="appendices.html#property_tree.appendices.compatibility">Compatibility</a>

-    </h4>
-<p>

- Property tree uses partial class template specialization. There hasbeen no- attempt to work around lack of support for this. The library willtherefore

-      most probably not work with Visual C++ 7.0 or earlier, or gcc 2.x.
-    </p>
-<p>

- Property tree has been tested (regressions successfully compiled andrun) with

-      the following compilers:
-    </p>
-<div class="itemizedlist"><ul class="itemizedlist" type="disc">
-<li class="listitem">
-        Visual C++ 8.0
-      </li>
-<li class="listitem">
-        gcc 3.4.2 (MinGW)
-      </li>
-<li class="listitem">
-        gcc 3.3.5 (Linux)
-      </li>
-<li class="listitem">
-        gcc 3.4.4 (Linux)
-      </li>
-<li class="listitem">
-        gcc 4.3.3 (Linux)
-      </li>
-<li class="listitem">
-        Intel C++ 9.0 (Linux)
-      </li>
-</ul></div>
-<a name="property_tree.appendices.rationale"></a><h4>
-<a name="id1426674"></a>

- <a class="link"href="appendices.html#property_tree.appendices.rationale">Rationale</a>

-    </h4>
-<div class="orderedlist"><ol class="orderedlist" type="1">
-<li class="listitem">

-Why are there 3 versions of <codeclass="computeroutput"><a class="link"href="../boost/property_tree/basic_ptree.html#id947644-bb">get</a></code>?- Couldn't there be just one? The three versionsreflect experience- gathered during several of years of using property tree in severaldifferent- applications. During that time I tried hard to come up with one,proper form- of the get function, and failed. I know of these three basicpatterns of

-        usage:
-        <div class="itemizedlist"><ul class="itemizedlist" type="disc">
-<li class="listitem">

-Just get the data and I do not care if itcannot be done.- This is used when the programmer is fairly sure that dataexists. Or- in homework assignments. Or when tomorrow is final deadlinefor your

-            project.
-          </li>
-<li class="listitem">

-Get the data and revert to default value if itcannot be done.- Used when you want to allow omitting the key in question.Implemented

-            by some similar tools (windows INI file access functions).
-          </li>
-<li class="listitem">

-Get the data, but I care more whether yousucceeded than I- do for the data itself. Used when you want to varycontrol- flow depending on get success/failure. Or to check forpresence of a

-            key.
-          </li>
-</ul></div>
-</li>
-<li class="listitem">

-Why does the separator character come beforethe path- and not after as one would expect? It helps withoverload resolution

-        in some cases.
-      </li>
-</ol></div>
-<a name="property_tree.appendices.future_development"></a><h4>
-<a name="id1426774"></a>

- <a class="link"href="appendices.html#property_tree.appendices.future_development">FutureDevelopment</a>

-    </h4>
-<div class="itemizedlist"><ul class="itemizedlist" type="disc">
-<li class="listitem">
-        More parsers: YAML, environment strings.
-      </li>
-<li class="listitem">
-        More robust XML parser.
-      </li>
-<li class="listitem">

- Mathematical relations: ptree difference, union, intersection.Useful for

-        finding configuration file changes etc.
-      </li>
-</ul></div>
-</div>

-<table xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision";width="100%"><tr>

-<td align="left"></td>

-<td align="right"><div class="copyright-footer">Copyright (c) 2008 MarcinKalicinski- Distributed under the Boost Software License, Version 1.0. (Seeaccompanying- file LICENSE_1_0.txt or copy at <ahref="http://www.boost.org/LICENSE_1_0.txt";target="_top">http://www.boost.org/LICENSE_1_0.txt</a>)

-      </p>
-</div></td>
-</tr></table>
-<hr>
-<div class="spirit-nav">

-</div>
-</body>
-</html>
=======================================
--- /trunk/doc/html/property_tree/reference.html        Sun Dec 20 18:38:58 2009
+++ /trunk/doc/html/property_tree/reference.html        Thu Dec 24 17:59:33 2009
@@ -3,10 +3,10 @@
 <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
 <title>Reference</title>
 <link rel="stylesheet" href="../boostbook.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.75.2">

-<link rel="home" href="../index.html" title="The Boost C++ LibrariesBoostBook Documentation Subset">

+<meta name="generator" content="DocBook XSL Stylesheets V1.73.2">

+<link rel="start" href="../index.html" title="Boost C++库 BoostBook文档子集"><link rel="up" href="../property_tree.html"title="Chapter 14. Boost.PropertyTree">

-<link rel="prev" href="appendices.html" title="Appendices">

+<link rel="prev" href="appendices_______.html" title="Appendices附录"><link rel="next" href="../boost/property_tree/ptree_error.html"title="Class ptree_error">

 </head>

<body bgcolor="white" text="black" link="#0000FF" vlink="#840084"alink="#0000FF">

@@ -20,9 +20,9 @@
 </tr></table>
 <hr>
 <div class="spirit-nav">

-<a accesskey="p" href="appendices.html"><imgsrc="../../../doc/html/images/prev.png" alt="Prev"></a><a accesskey="u"href="../property_tree.html"><img src="../../../doc/html/images/up.png"alt="Up"></a><a accesskey="h" href="../index.html"><imgsrc="../../../doc/html/images/home.png" alt="Home"></a><a accesskey="n"href="../boost/property_tree/ptree_error.html"><imgsrc="../../../doc/html/images/next.png" alt="Next"></a>+<a accesskey="p" href="appendices_______.html"><imgsrc="../../../doc/html/images/prev.png" alt="Prev"></a><a accesskey="u"href="../property_tree.html"><img src="../../../doc/html/images/up.png"alt="Up"></a><a accesskey="h" href="../index.html"><imgsrc="../../../doc/html/images/home.png" alt="Home"></a><a accesskey="n"href="../boost/property_tree/ptree_error.html"><imgsrc="../../../doc/html/images/next.png" alt="Next"></a>

 </div>
-<div class="section" title="Reference">
+<div class="section" lang="en">
 <div class="titlepage"><div><div><h2 class="title" style="clear: both">
 <a name="property_tree.reference"></a>Reference</h2></div></div></div>
 <div class="toc"><dl>
@@ -38,7 +38,7 @@

<dt><ahref="reference.html#header.boost.property_tree.string_path_hpp">Header<boost/property_tree/string_path.hpp></a></dt><dt><ahref="reference.html#header.boost.property_tree.xml_parser_hpp">Header<boost/property_tree/xml_parser.hpp></a></dt>

 </dl></div>

-<div class="section" title="Header<boost/property_tree/exceptions.hpp>">

+<div class="section" lang="en">
 <div class="titlepage"><div><div><h3 class="title">

<a name="header.boost.property_tree.exceptions_hpp"></a>Header <<ahref="../../../boost/property_tree/exceptions.hpp"target="_top">boost/property_tree/exceptions.hpp</a>></h3></div></div></div><pre class="synopsis">namespaceboost {

@@ -49,47 +49,47 @@
   }
 }</pre>
 </div>

-<div class="section" title="Header<boost/property_tree/id_translator.hpp>">

+<div class="section" lang="en">
 <div class="titlepage"><div><div><h3 class="title">

<a name="header.boost.property_tree.id_translator_hpp"></a>Header <<ahref="../../../boost/property_tree/id_translator.hpp"target="_top">boost/property_tree/id_translator.hpp</a>></h3></div></div></div><pre class="synopsis">namespaceboost {

   <span class="bold"><strong>namespace</strong></span> property_tree {

template<<spanclass="bold">typename T> <spanclass="bold">struct <a class="link"href="../boost/property_tree/id_translator.html" title="Struct templateid_translator">id_translator</a>;

- template<<spanclass="bold">typename T> <spanclass="bold">struct <a class="link"href="../boost/property_tree/translator_between_T__T_id983289.html"title="Struct template translator_between<T,T>">translator_between</a><T, T>;+ template<<spanclass="bold">typename T> <spanclass="bold">struct <a class="link"href="../boost/property_tree/translator_between_T__T_id4725792.html"title="Struct template translator_between<T,T>">translator_between</a><T, T>;template<<spanclass="bold">typename Ch, <spanclass="bold">typename Traits, <spanclass="bold">typename Alloc>- struct <a class="link"href="../boost/property_tree/translator_between_std__id879891.html"title="Struct template translator_between<std::basic_string< Ch,Traits, Alloc >, std::basic_string< Ch, Traits, Alloc>>">translator_between</a><std::basic_string< Ch, Traits, Alloc>, std::basic_string< Ch, Traits, Alloc >>;+ struct <a class="link"href="../boost/property_tree/translator_between_std__id4725816.html"title="Struct template translator_between<std::basic_string< Ch,Traits, Alloc >, std::basic_string< Ch, Traits, Alloc>>">translator_between</a><std::basic_string< Ch, Traits, Alloc>, std::basic_string< Ch, Traits, Alloc >>;

   }
 }</pre>
 </div>

-<div class="section" title="Header<boost/property_tree/info_parser.hpp>">

+<div class="section" lang="en">
 <div class="titlepage"><div><div><h3 class="title">

<a name="header.boost.property_tree.info_parser_hpp"></a>Header <<ahref="../../../boost/property_tree/info_parser.hpp"target="_top">boost/property_tree/info_parser.hpp</a>></h3></div></div></div><pre class="synopsis">namespaceboost {

   <span class="bold"><strong>namespace</strong></span> property_tree {
     <span class="bold"><strong>namespace</strong></span> info_parser {

template<<spanclass="bold">typename Ptree, <spanclass="bold">typename Ch>- <spanclass="bold">void <a class="link"href="../boost/property_tree/info_parser/read_info_id879942.html"title="Function template read_info">read_info</a>(std::basic_istream< Ch> &, Ptree &);+ <spanclass="bold">void <a class="link"href="../boost/property_tree/info_parser/read_info_id5226282.html"title="Function template read_info">read_info</a>(std::basic_istream< Ch> &, Ptree &);template<<spanclass="bold">typename Ptree, <spanclass="bold">typename Ch>- <spanclass="bold">void <a class="link"href="../boost/property_tree/info_parser/read_info_id879982.html"title="Function template read_info">read_info</a>(std::basic_istream< Ch> &, Ptree &, constPtree &);+ <spanclass="bold">void <a class="link"href="../boost/property_tree/info_parser/read_info_id5226325.html"title="Function template read_info">read_info</a>(std::basic_istream< Ch> &, Ptree &, constPtree &);template<<spanclass="bold">typename Ptree>- <spanclass="bold">void <a class="link"href="../boost/property_tree/info_parser/read_info_id880025.html"title="Function template read_info">read_info</a>(<spanclass="bold">const std::string &, Ptree &,+ <spanclass="bold">void <a class="link"href="../boost/property_tree/info_parser/read_info_id4707516.html"title="Function template read_info">read_info</a>(<spanclass="bold">const std::string &, Ptree &,conststd::locale & = std::locale());template<<spanclass="bold">typename Ptree>- <spanclass="bold">void <a class="link"href="../boost/property_tree/info_parser/read_info_id880070.html"title="Function template read_info">read_info</a>(<spanclass="bold">const std::string &, Ptree &,const Ptree &,+ <spanclass="bold">void <a class="link"href="../boost/property_tree/info_parser/read_info_id4707564.html"title="Function template read_info">read_info</a>(<spanclass="bold">const std::string &, Ptree &,const Ptree &,conststd::locale & = std::locale());template<<spanclass="bold">typename Ptree, <spanclass="bold">typename Ch>- <spanclass="bold">void <a class="link"href="../boost/property_tree/info_parser/write_info_id880119.html"title="Function template write_info">write_info</a>(std::basic_ostream<Ch > &, const Ptree &,+ <spanclass="bold">void <a class="link"href="../boost/property_tree/info_parser/write_info_id4707617.html"title="Function template write_info">write_info</a>(std::basic_ostream<Ch > &, const Ptree &,constinfo_writer_settings< Ch > & = info_writer_settings< Ch>());template<<spanclass="bold">typename Ptree>- <spanclass="bold">void <a class="link"href="../boost/property_tree/info_parser/write_info_id941712.html"title="Function template write_info">write_info</a>(<spanclass="bold">const std::string &, <spanclass="bold">const Ptree &,+ <spanclass="bold">void <a class="link"href="../boost/property_tree/info_parser/write_info_id4934840.html"title="Function template write_info">write_info</a>(<spanclass="bold">const std::string &, <spanclass="bold">const Ptree &,conststd::locale & = std::locale(),constinfo_writer_settings< <spanclass="bold">typename Ptree::key_type::value_type> & = info_writer_make_settings< typenamePtree::key_type::value_type >());

     }
   }
 }</pre>
 </div>

-<div class="section" title="Header<boost/property_tree/ini_parser.hpp>">

+<div class="section" lang="en">
 <div class="titlepage"><div><div><h3 class="title">

<a name="header.boost.property_tree.ini_parser_hpp"></a>Header <<ahref="../../../boost/property_tree/ini_parser.hpp"target="_top">boost/property_tree/ini_parser.hpp</a>></h3></div></div></div><pre class="synopsis">namespaceboost {

@@ -98,44 +98,44 @@

class <a class="link"href="../boost/property_tree/ini_parser/ini_parser_error.html" title="Classini_parser_error">ini_parser_error</a>;<spanclass="bold">bool <a class="link"href="../boost/property_tree/ini_parser/validate_flags.html"title="Function validate_flags">validate_flags</a>(<spanclass="bold">int);template<<spanclass="bold">typename Ptree>- <spanclass="bold">void <a class="link"href="../boost/property_tree/ini_parser/read_ini_id946845.html"title="Function template read_ini">read_ini</a>(std::basic_istream<typenamePtree::key_type::value_type > &,+ <spanclass="bold">void <a class="link"href="../boost/property_tree/ini_parser/read_ini_id4953809.html"title="Function template read_ini">read_ini</a>(std::basic_istream<typenamePtree::key_type::value_type > &,

                       Ptree &amp;);

     }
   }
 }</pre>
 </div>

-<div class="section" title="Header<boost/property_tree/json_parser.hpp>">

+<div class="section" lang="en">
 <div class="titlepage"><div><div><h3 class="title">

<a name="header.boost.property_tree.json_parser_hpp"></a>Header <<ahref="../../../boost/property_tree/json_parser.hpp"target="_top">boost/property_tree/json_parser.hpp</a>></h3></div></div></div><pre class="synopsis">namespaceboost {

   <span class="bold"><strong>namespace</strong></span> property_tree {
     <span class="bold"><strong>namespace</strong></span> json_parser {

                        Ptree &amp;);

     }
   }
 }</pre>
 </div>
-<div class="section" title="Header &lt;boost/property_tree/ptree.hpp&gt;">
+<div class="section" lang="en">
 <div class="titlepage"><div><div><h3 class="title">

<a name="header.boost.property_tree.ptree_hpp"></a>Header <<ahref="../../../boost/property_tree/ptree.hpp"target="_top">boost/property_tree/ptree.hpp</a>></h3></div></div></div><pre class="synopsis">namespaceboost {

@@ -145,7 +145,7 @@
   }
 }</pre>
 </div>

-<div class="section" title="Header<boost/property_tree/ptree_fwd.hpp>">

+<div class="section" lang="en">
 <div class="titlepage"><div><div><h3 class="title">

<a name="header.boost.property_tree.ptree_fwd_hpp"></a>Header <<ahref="../../../boost/property_tree/ptree_fwd.hpp"target="_top">boost/property_tree/ptree_fwd.hpp</a>></h3></div></div></div><pre class="synopsis">namespaceboost {

@@ -157,11 +157,11 @@

typedef <a class="link"href="../boost/property_tree/basic_ptree.html" title="Class templatebasic_ptree">basic_ptree</a>< std::wstring, std::wstring > <aclass="link" href="../boost/property_tree/wptree.html" title="Typedefinition wptree">wptree</a>;typedef <spanclass="emphasis">unspecified <a class="link"href="../boost/property_tree/wiptree.html" title="Type definitionwiptree">wiptree</a>;template<<spanclass="bold">typename K, <spanclass="bold">typename D, <spanclass="bold">typename C>- <spanclass="bold">void <a class="link"href="../boost/property_tree/swap_id948315.html" title="Function templateswap">swap</a>(<a class="link"href="../boost/property_tree/basic_ptree.html" title="Class templatebasic_ptree">basic_ptree</a>< K, D, C > &, <a class="link"href="../boost/property_tree/basic_ptree.html" title="Class templatebasic_ptree">basic_ptree</a>< K, D, C > &);+ <spanclass="bold">void <a class="link"href="../boost/property_tree/swap_id5215967.html" title="Function templateswap">swap</a>(<a class="link"href="../boost/property_tree/basic_ptree.html" title="Class templatebasic_ptree">basic_ptree</a>< K, D, C > &, <a class="link"href="../boost/property_tree/basic_ptree.html" title="Class templatebasic_ptree">basic_ptree</a>< K, D, C > &);

   }
 }</pre>
 </div>

-<div class="section" title="Header<boost/property_tree/ptree_serialization.hpp>">

+<div class="section" lang="en">
 <div class="titlepage"><div><div><h3 class="title">

<a name="header.boost.property_tree.ptree_serialization_hpp"></a>Header<<a href="../../../boost/property_tree/ptree_serialization.hpp"target="_top">boost/property_tree/ptree_serialization.hpp</a>></h3></div></div></div><pre class="synopsis">namespaceboost {

@@ -171,11 +171,11 @@

template<<spanclass="bold">typename Archive, <spanclass="bold">typename K, <spanclass="bold">typename D, <spanclass="bold">typename C><spanclass="bold">void <a class="link"href="../boost/property_tree/load.html" title="Function templateload">load</a>(Archive &, <a class="link"href="../boost/property_tree/basic_ptree.html" title="Class templatebasic_ptree">basic_ptree</a>< K, D, C > &, <spanclass="bold">const <spanclass="bold">unsigned <spanclass="bold">int);template<<spanclass="bold">typename Archive, <spanclass="bold">typename K, <spanclass="bold">typename D, <spanclass="bold">typename C>- <spanclass="bold">void <a class="link"href="../boost/property_tree/serialize_id948534.html" title="Functiontemplate serialize">serialize</a>(Archive &, <a class="link"href="../boost/property_tree/basic_ptree.html" title="Class templatebasic_ptree">basic_ptree</a>< K, D, C > &, <spanclass="bold">const <spanclass="bold">unsigned <spanclass="bold">int);+ <spanclass="bold">void <a class="link"href="../boost/property_tree/serialize_id4868444.html" title="Functiontemplate serialize">serialize</a>(Archive &, <a class="link"href="../boost/property_tree/basic_ptree.html" title="Class templatebasic_ptree">basic_ptree</a>< K, D, C > &, <spanclass="bold">const <spanclass="bold">unsigned <spanclass="bold">int);

   }
 }</pre>
 </div>

-<div class="section" title="Header<boost/property_tree/stream_translator.hpp>">

+<div class="section" lang="en">
 <div class="titlepage"><div><div><h3 class="title">

<a name="header.boost.property_tree.stream_translator_hpp"></a>Header<<a href="../../../boost/property_tree/stream_translator.hpp"target="_top">boost/property_tree/stream_translator.hpp</a>></h3></div></div></div><pre class="synopsis">namespaceboost {

@@ -185,25 +185,25 @@

struct <a class="link"href="../boost/property_tree/customize_stream.html" title="Struct templatecustomize_stream">customize_stream</a>;

template<<spanclass="bold">typename Ch, <spanclass="bold">typename Traits>- struct <a class="link"href="../boost/property_tree/customize_stream_Ch__Tr_id948676.html"title="Struct template customize_stream<Ch, Traits, Ch,void>">customize_stream</a><Ch, Traits, Ch, <spanclass="bold">void>;+ struct <a class="link"href="../boost/property_tree/customize_stream_Ch__Tr_id4868586.html"title="Struct template customize_stream<Ch, Traits, Ch,void>">customize_stream</a><Ch, Traits, Ch, <spanclass="bold">void>;template<<spanclass="bold">typename Ch, <spanclass="bold">typename Traits, <spanclass="bold">typename F>- struct <a class="link"href="../boost/property_tree/customize_stream_Ch__Tr_id948744.html"title="Struct template customize_stream<Ch, Traits, F, typenameboost::enable_if< detail::is_inexact< F >>::type>">customize_stream</a><Ch, Traits, F, <spanclass="bold">typename boost::enable_if<detail::is_inexact< F > >::type>;+ struct <a class="link"href="../boost/property_tree/customize_stream_Ch__Tr_id4919206.html"title="Struct template customize_stream<Ch, Traits, F, typenameboost::enable_if< detail::is_inexact< F >>::type>">customize_stream</a><Ch, Traits, F, <spanclass="bold">typename boost::enable_if<detail::is_inexact< F > >::type>;template<<spanclass="bold">typename Ch, <spanclass="bold">typename Traits>- struct <a class="link"href="../boost/property_tree/customize_stream_Ch__Tr_id948818.html"title="Struct template customize_stream<Ch, Traits, bool,void>">customize_stream</a><Ch, Traits, <spanclass="bold">bool, <spanclass="bold">void>;+ struct <a class="link"href="../boost/property_tree/customize_stream_Ch__Tr_id4919280.html"title="Struct template customize_stream<Ch, Traits, bool,void>">customize_stream</a><Ch, Traits, <spanclass="bold">bool, <spanclass="bold">void>;template<<spanclass="bold">typename Ch, <spanclass="bold">typename Traits>- struct <a class="link"href="../boost/property_tree/customize_stream_Ch__Tr_id948886.html"title="Struct template customize_stream<Ch, Traits, signed char,void>">customize_stream</a><Ch, Traits, <spanclass="bold">signed <spanclass="bold">char, <spanclass="bold">void>;+ struct <a class="link"href="../boost/property_tree/customize_stream_Ch__Tr_id4866784.html"title="Struct template customize_stream<Ch, Traits, signed char,void>">customize_stream</a><Ch, Traits, <spanclass="bold">signed <spanclass="bold">char, <spanclass="bold">void>;template<<spanclass="bold">typename Ch, <spanclass="bold">typename Traits>- struct <a class="link"href="../boost/property_tree/customize_stream_Ch__Tr_id948954.html"title="Struct template customize_stream<Ch, Traits, unsigned char,void>">customize_stream</a><Ch, Traits, <spanclass="bold">unsigned <spanclass="bold">char, <spanclass="bold">void>;+ struct <a class="link"href="../boost/property_tree/customize_stream_Ch__Tr_id4866852.html"title="Struct template customize_stream<Ch, Traits, unsigned char,void>">customize_stream</a><Ch, Traits, <spanclass="bold">unsigned <spanclass="bold">char, <spanclass="bold">void>;

template<<spanclass="bold">typename Ch, <spanclass="bold">typename Traits, <spanclass="bold">typename Alloc, <spanclass="bold">typename E>class <a class="link"href="../boost/property_tree/stream_translator.html" title="Class templatestream_translator">stream_translator</a>;

template<<spanclass="bold">typename Ch, <spanclass="bold">typename Traits, <spanclass="bold">typename Alloc, <spanclass="bold">typename E>- struct <a class="link"href="../boost/property_tree/translator_between_std__id949101.html"title="Struct template translator_between<std::basic_string< Ch,Traits, Alloc >, E>">translator_between</a><std::basic_string<Ch, Traits, Alloc >, E>;+ struct <a class="link"href="../boost/property_tree/translator_between_std__id4665228.html"title="Struct template translator_between<std::basic_string< Ch,Traits, Alloc >, E>">translator_between</a><std::basic_string<Ch, Traits, Alloc >, E>;

   }
 }</pre>
 </div>

-<div class="section" title="Header<boost/property_tree/string_path.hpp>">

+<div class="section" lang="en">
 <div class="titlepage"><div><div><h3 class="title">

<a name="header.boost.property_tree.string_path_hpp"></a>Header <<ahref="../../../boost/property_tree/string_path.hpp"target="_top">boost/property_tree/string_path.hpp</a>></h3></div></div></div><pre class="synopsis">namespaceboost {

@@ -211,40 +211,40 @@

template<<spanclass="bold">typename String, <spanclass="bold">typename Translator> <spanclass="bold">class <a class="link"href="../boost/property_tree/string_path.html" title="Class templatestring_path">string_path</a>;

template<<spanclass="bold">typename Ch, <spanclass="bold">typename Traits, <spanclass="bold">typename Alloc>- struct <a class="link"href="../boost/property_tree/path_of_std_basic_strin_id949413.html"title="Struct template path_of<std::basic_string< Ch, Traits, Alloc>>">path_of</a><std::basic_string< Ch, Traits, Alloc >>;+ struct <a class="link"href="../boost/property_tree/path_of_std_basic_strin_id4648730.html"title="Struct template path_of<std::basic_string< Ch, Traits, Alloc>>">path_of</a><std::basic_string< Ch, Traits, Alloc >>;template<<spanclass="bold">typename String, <spanclass="bold">typename Translator><a class="link"href="../boost/property_tree/string_path.html" title="Class templatestring_path">string_path</a>< String, Translator >- <a name="boost.property_tree.operator/_id949458"></a><spanclass="bold">operator/(<a class="link"href="../boost/property_tree/string_path.html" title="Class templatestring_path">string_path</a>< String, Translator > p1,+ <a name="boost.property_tree.operator/_id4648775"></a><spanclass="bold">operator/(<a class="link"href="../boost/property_tree/string_path.html" title="Class templatestring_path">string_path</a>< String, Translator > p1,const <aclass="link" href="../boost/property_tree/string_path.html" title="Classtemplate string_path">string_path</a>< String, Translator > & p2);template<<spanclass="bold">typename String, <spanclass="bold">typename Translator><a class="link"href="../boost/property_tree/string_path.html" title="Class templatestring_path">string_path</a>< String, Translator >- <a name="boost.property_tree.operator/_id949496"></a><spanclass="bold">operator/(<a class="link"href="../boost/property_tree/string_path.html" title="Class templatestring_path">string_path</a>< String, Translator > p1,+ <a name="boost.property_tree.operator/_id5271086"></a><spanclass="bold">operator/(<a class="link"href="../boost/property_tree/string_path.html" title="Class templatestring_path">string_path</a>< String, Translator > p1,const <spanclass="bold">typename String::value_type * p2);template<<spanclass="bold">typename String, <spanclass="bold">typename Translator><a class="link"href="../boost/property_tree/string_path.html" title="Class templatestring_path">string_path</a>< String, Translator >- <a name="boost.property_tree.operator/_id949530"></a><spanclass="bold">operator/(<spanclass="bold">const <spanclass="bold">typename String::value_type * p1,+ <a name="boost.property_tree.operator/_id5271120"></a><spanclass="bold">operator/(<spanclass="bold">const <spanclass="bold">typename String::value_type * p1,const <aclass="link" href="../boost/property_tree/string_path.html" title="Classtemplate string_path">string_path</a>< String, Translator > & p2);

   }
 }</pre>
 </div>

-<div class="section" title="Header<boost/property_tree/xml_parser.hpp>">

+<div class="section" lang="en">
 <div class="titlepage"><div><div><h3 class="title">

<a name="header.boost.property_tree.xml_parser_hpp"></a>Header <<ahref="../../../boost/property_tree/xml_parser.hpp"target="_top">boost/property_tree/xml_parser.hpp</a>></h3></div></div></div><pre class="synopsis">namespaceboost {

   <span class="bold"><strong>namespace</strong></span> property_tree {
     <span class="bold"><strong>namespace</strong></span> xml_parser {

template<<spanclass="bold">typename Ptree>- <spanclass="bold">void <a class="link"href="../boost/property_tree/xml_parser/read_xml_id954816.html"title="Function template read_xml">read_xml</a>(std::basic_istream<typenamePtree::key_type::value_type > &,+ <spanclass="bold">void <a class="link"href="../boost/property_tree/xml_parser/read_xml_id5271168.html"title="Function template read_xml">read_xml</a>(std::basic_istream<typenamePtree::key_type::value_type > &,Ptree &, <spanclass="bold">int = 0);template<<spanclass="bold">typename Ptree>- <spanclass="bold">void <a class="link"href="../boost/property_tree/xml_parser/read_xml_id960538.html"title="Function template read_xml">read_xml</a>(<spanclass="bold">const std::string &, Ptree &,int = 0,+ <spanclass="bold">void <a class="link"href="../boost/property_tree/xml_parser/read_xml_id4883958.html"title="Function template read_xml">read_xml</a>(<spanclass="bold">const std::string &, Ptree &,int = 0,conststd::locale & = std::locale());template<<spanclass="bold">typename Ptree>- <spanclass="bold">void <a class="link"href="../boost/property_tree/xml_parser/write_xml_id960643.html"title="Function template write_xml">write_xml</a>(std::basic_ostream<typenamePtree::key_type::value_type > &,+ <spanclass="bold">void <a class="link"href="../boost/property_tree/xml_parser/write_xml_id4884059.html"title="Function template write_xml">write_xml</a>(std::basic_ostream<typenamePtree::key_type::value_type > &,constPtree &,constxml_writer_settings< typenamePtree::key_type::value_type > & = xml_writer_settings< typenamePtree::key_type::value_type >());template<<spanclass="bold">typename Ptree>- <spanclass="bold">void <a class="link"href="../boost/property_tree/xml_parser/write_xml_id957066.html"title="Function template write_xml">write_xml</a>(<spanclass="bold">const std::string &, <spanclass="bold">const Ptree &,+ <spanclass="bold">void <a class="link"href="../boost/property_tree/xml_parser/write_xml_id4643605.html"title="Function template write_xml">write_xml</a>(<spanclass="bold">const std::string &, <spanclass="bold">const Ptree &,conststd::locale & = std::locale(),constxml_writer_settings< typenamePtree::key_type::value_type > & = xml_writer_settings< typenamePtree::key_type::value_type >());

     }
@@ -262,7 +262,7 @@
 </tr></table>
 <hr>
 <div class="spirit-nav">

 </div>
 </body>
 </html>
=======================================
--- /trunk/doc/html/property_tree.html  Sun Dec 20 18:38:58 2009
+++ /trunk/doc/html/property_tree.html  Thu Dec 24 17:59:33 2009
@@ -3,11 +3,11 @@
 <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
 <title>Chapter 14. Boost.PropertyTree</title>
 <link rel="stylesheet" href="boostbook.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.75.2">

-<link rel="home" href="index.html" title="The Boost C++ LibrariesBoostBook Documentation Subset">-<link rel="up" href="libraries.html" title="Part I. The Boost C++Libraries (BoostBook Subset)">

+<meta name="generator" content="DocBook XSL Stylesheets V1.73.2">

+<link rel="start" href="index.html" title="Boost C++库 BoostBook文档子集">+<link rel="up" href="libraries.html" title="Part I. Boost C++库(BoostBook 子集)"><link rel="prev" href="BOOST_PROGRAM_OPTIONS_VERSION.html" title="MacroBOOST_PROGRAM_OPTIONS_VERSION">-<link rel="next" href="boost_propertytree/tutorial.html" title="FiveMinute Tutorial">+<link rel="next" href="boost_propertytree/tutorial.html" title="FiveMinute Tutorial 五分钟教程">

 </head>

<body bgcolor="white" text="black" link="#0000FF" vlink="#840084"alink="#0000FF">

 <table cellpadding="2" width="100%"><tr>
@@ -22,7 +22,7 @@
 <div class="spirit-nav">

<a accesskey="p" href="BOOST_PROGRAM_OPTIONS_VERSION.html"><imgsrc="../../doc/html/images/prev.png" alt="Prev"></a><a accesskey="u"href="libraries.html"><img src="../../doc/html/images/up.png"alt="Up"></a><a accesskey="h" href="index.html"><imgsrc="../../doc/html/images/home.png" alt="Home"></a><a accesskey="n"href="boost_propertytree/tutorial.html"><imgsrc="../../doc/html/images/next.png" alt="Next"></a>

 </div>
-<div class="chapter" title="Chapter 14. Boost.PropertyTree">
+<div class="chapter" lang="en">
 <div class="titlepage"><div>
 <div><h2 class="title">
 <a name="property_tree"></a>Chapter 14. Boost.PropertyTree</h2></div>
@@ -30,8 +30,8 @@

Marcin <spanclass="surname">Kalicinski

 </h3></div></div>
 <div><p class="copyright">Copyright (c) 2008 Marcin Kalicinski</p></div>
-<div><div class="legalnotice" title="Legal Notice">
-<a name="id1422040"></a><p>
+<div><div class="legalnotice">
+<a name="id5737636"></a><p>

Distributed under the Boost Software License, Version 1.0. (Seeaccompanyingfile LICENSE_1_0.txt or copy at <ahref="http://www.boost.org/LICENSE_1_0.txt";target="_top">http://www.boost.org/LICENSE_1_0.txt</a>)

       </p>
@@ -40,21 +40,26 @@
 <div class="toc">
 <p><b>Table of Contents</b></p>
 <dl>

-<dt><ahref="property_tree.html#boost_propertytree.intro"> What is PropertyTree?</a></dt>-<dt><a href="boost_propertytree/tutorial.html"> FiveMinute Tutorial</a></dt>-<dt><a href="boost_propertytree/container.html">Property Tree as a Container</a></dt>-<dt><a href="boost_propertytree/synopsis.html">Property Tree Synopsis</a></dt>+<dt><ahref="property_tree.html#boost_propertytree.intro"> What is Property Tree?属性树是什么？</a></dt>+<dt><a href="boost_propertytree/tutorial.html"> FiveMinute Tutorial 五分钟教程</a></dt>+<dt><a href="boost_propertytree/container.html">Property Tree as a Container+作为容器的属性树</a></dt>+<dt><a href="boost_propertytree/synopsis.html">Property Tree Synopsis属性树概要</a></dt><dt><a href="boost_propertytree/parsers.html"> Howto Populate a Property

-    Tree</a></span></dt>

+ Tree如何填充属性树</a></dt>

 <dd><dl>

-<dt><ahref="boost_propertytree/parsers.html#boost_propertytree.parsers.xml_parser">XMLParser</a></dt>-<dt><ahref="boost_propertytree/parsers.html#boost_propertytree.parsers.json_parser">JSONParser</a></dt>-<dt><ahref="boost_propertytree/parsers.html#boost_propertytree.parsers.ini_parser">INIParser</a></dt>-<dt><ahref="boost_propertytree/parsers.html#boost_propertytree.parsers.info_parser">INFOParser</a></dt>+<dt><ahref="boost_propertytree/parsers.html#boost_propertytree.parsers.xml_parser__xml_________">XML

+      Parser XML&#20998;&#26512;&#22120;</a></span></dt>

+<dt><ahref="boost_propertytree/parsers.html#boost_propertytree.parsers.json_parser__json_________">JSON

+      Parser JSON&#20998;&#26512;&#22120;</a></span></dt>

+<dt><ahref="boost_propertytree/parsers.html#boost_propertytree.parsers.ini_parser__ini_________">INI

+      Parser INI&#20998;&#26512;&#22120;</a></span></dt>

+<dt><ahref="boost_propertytree/parsers.html#boost_propertytree.parsers.info_parser__info_________">INFO

+      Parser INFO&#20998;&#26512;&#22120;</a></span></dt>
 </dl></dd>

<dt><a href="boost_propertytree/accessing.html"> Howto Access Data in a

-    Property Tree</a></span></dt>

-<dt><ahref="property_tree/appendices.html">Appendices</a></dt>+ Property Tree如何访问属性树中的数据</a></dt>+<dt><ahref="property_tree/appendices_______.html">Appendices附录</a></dt><dt><ahref="property_tree/reference.html">Reference</a></dt>

 <dd><dl>

<dt><ahref="property_tree/reference.html#header.boost.property_tree.exceptions_hpp">Header<boost/property_tree/exceptions.hpp></a></dt>

@@ -71,9 +76,9 @@
 </dl></dd>
 </dl>
 </div>
-<div class="section" title="What is Property Tree?">
+<div class="section" lang="en">
 <div class="titlepage"><div><div><h2 class="title" style="clear: both">

-<a name="boost_propertytree.intro"></a><a class="link"href="property_tree.html#boost_propertytree.intro" title="What is PropertyTree?"> What is Property Tree?</a>+<a name="boost_propertytree.intro"></a><a class="link"href="property_tree.html#boost_propertytree.intro" title="What is PropertyTree? 属性树是什么？"> What isProperty Tree? 属性树是什么？</a>

 </h2></div></div></div>
 <p>

The Property Tree library provides a data structure that stores anarbitrarily

@@ -83,35 +88,59 @@
       which is a concatenation of multiple keys.
     </p>
 <p>

+ PropertyTree库提供了一种数据结构，用于保存任意嵌套层数的由值组成的树，每一层以+某个键值来索引。树的每个节点保存了它本身的值，以及一个由该节点的子节点及其键值+组成的有序列表。这种树可以通过类似于路径的方式很方便地访问任一节点，这个路径由+多个键值串接而成。

+    </p>
+<p>

In addition, the library provides parsers and generators for anumber of dataformats that can be represented by such a tree, including XML, INI,and JSON.

     </p>
 <p>

+此外，这个库还提供了一些分析器和生成器，对应于多种可用于表示一棵树的数据格式，

+      &#22914; XML, INI &#21644; JSON&#12290;
+    </p>
+<p>

Property trees are versatile data structures, but are particularlysuited forholding configuration data. The tree provides its own, tree-specificinterface,

       and each node is also an STL-compatible Sequence for its child nodes.
     </p>
 <p>

+属性树是多功能的数据结构，尤其适合用于保存配置数据。该树提供了它自己本身、树专用+的接口，而且每个节点都是其子节点的一个STL兼容序列。

+    </p>
+<p>

Conceptually, then, a node can be thought of as the followingstructure:

     </p>
+<p>

+在概念上，一个节点可以想象为以下结构：

+    </p>

<pre class="programlisting">struct <spanclass="identifier">ptree

 <span class="special">{</span>

- data_type <spanclass="identifier">data<spanclass="special">; //data associated with the node- list<spanclass="special">< pair<spanclass="special"><key_type<spanclass="special">, ptree<spanclass="special">> > <spanclass="identifier">children; <spanclass="comment">// ordered list of named children+ data_type <spanclass="identifier">data<spanclass="special">; //data associated with the node与节点相关联的数据+ list<spanclass="special">< pair<spanclass="special"><key_type<spanclass="special">, ptree<spanclass="special">> > <spanclass="identifier">children; <spanclass="comment">// ordered list of named children命名子节点的有序列表

 </span><span class="special">};</span>
 </pre>
 <p>

Both key_type and data_type are configurable, but will usually bestd::string.

     </p>
 <p>

+ key_type 和 data_type都是可配置的，但通常都是std::string。

+    </p>
+<p>

Many software projects develop a similar tool at some point of theirlifetime,and property tree originated the same way. We hope the library cansave many

       from reinventing the wheel.
     </p>
+<p>

+许多软件项目都在它们生命周期中的某个时候开发过类似的工具，属性树正源自于此。+我们希望这个库可以节省重复发明轮子的时间。

+    </p>
 </div>
 </div>

<table xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision";width="100%"><tr>-<td align="left">Last revised: November 14, 2009 at 10:40:12GMT</td>+<td align="left">Last revised: December 24, 2009 at 08:38:50GMT</td>

 <td align="right"><div class="copyright-footer"></div></td>
 </tr></table>
 <hr>

[boost-doc-zh] r358 committed - property_tree 库译文。...

Other related posts: