diff options
Diffstat (limited to 'doc/html/proto/appendices.html')
| -rw-r--r-- | doc/html/proto/appendices.html | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/doc/html/proto/appendices.html b/doc/html/proto/appendices.html index 0e43cfd4fd..c3e1469ed2 100644 --- a/doc/html/proto/appendices.html +++ b/doc/html/proto/appendices.html @@ -97,7 +97,7 @@ <span class="bold"><strong>Behavior Change: proto::as_expr() and proto::as_child()</strong></span> </p> <p> - The functions <code class="computeroutput"><a class="link" href="../boost/proto/as_expr_idp731118320.html" title="Function as_expr">proto::as_expr()</a></code> and <code class="computeroutput"><a class="link" href="../boost/proto/as_child_idp731140288.html" title="Function as_child">proto::as_child()</a></code> + The functions <code class="computeroutput"><a class="link" href="../boost/proto/as_expr_idp712860880.html" title="Function as_expr">proto::as_expr()</a></code> and <code class="computeroutput"><a class="link" href="../boost/proto/as_child_idp712882848.html" title="Function as_child">proto::as_child()</a></code> are used to guarantee that an object is a Proto expression by turning it into one if it is not already, using an optionally specified domain. In previous releases, when these functions were passed a Proto expression in a domain @@ -202,8 +202,8 @@ 1.44, users now have this power. </p> <p> - Users defining their own domain can now specify how <code class="computeroutput"><a class="link" href="../boost/proto/as_expr_idp731118320.html" title="Function as_expr">proto::as_expr()</a></code> - and <code class="computeroutput"><a class="link" href="../boost/proto/as_child_idp731140288.html" title="Function as_child">proto::as_child()</a></code> work in their domain. They + Users defining their own domain can now specify how <code class="computeroutput"><a class="link" href="../boost/proto/as_expr_idp712860880.html" title="Function as_expr">proto::as_expr()</a></code> + and <code class="computeroutput"><a class="link" href="../boost/proto/as_child_idp712882848.html" title="Function as_child">proto::as_child()</a></code> work in their domain. They can do this easily by defining nested class templates named <code class="computeroutput"><span class="identifier">as_expr</span></code> and/or <code class="computeroutput"><span class="identifier">as_child</span></code> within their domain class. </p> @@ -320,7 +320,7 @@ <dl class="variablelist"> <dt><span class="term">August 13, 2010</span></dt> <dd><p> - Boost 1.44: Proto gets sub-domains and per-domain control of <code class="computeroutput"><a class="link" href="../boost/proto/as_expr_idp731118320.html" title="Function as_expr">proto::as_expr()</a></code> and <code class="computeroutput"><a class="link" href="../boost/proto/as_child_idp731140288.html" title="Function as_child">proto::as_child()</a></code> to meet the needs + Boost 1.44: Proto gets sub-domains and per-domain control of <code class="computeroutput"><a class="link" href="../boost/proto/as_expr_idp712860880.html" title="Function as_expr">proto::as_expr()</a></code> and <code class="computeroutput"><a class="link" href="../boost/proto/as_child_idp712882848.html" title="Function as_child">proto::as_child()</a></code> to meet the needs of Phoenix3. </p></dd> <dt><span class="term">August 11, 2008</span></dt> |