mirror of
https://github.com/boostorg/function.git
synced 2025-07-29 12:27:15 +02:00
Import of BoostBook documentation for any, array, bind, function, ref, and
signals libraries. [SVN r17866]
This commit is contained in:
87
doc/history.xml
Normal file
87
doc/history.xml
Normal file
@ -0,0 +1,87 @@
|
||||
<?xml version="1.0" encoding="utf-8"?>
|
||||
<!DOCTYPE library PUBLIC "-//Boost//DTD BoostBook XML V1.0//EN"
|
||||
"http://www.boost.org/tools/boostbook/dtd/boostbook.dtd">
|
||||
<section id="function.history" last-revision="$Date$">
|
||||
<title>History & Compatibility Notes</title>
|
||||
|
||||
<itemizedlist spacing="compact">
|
||||
<listitem><para><emphasis role="bold">Version 1.30.0</emphasis>: </para>
|
||||
<itemizedlist spacing="compact">
|
||||
<listitem><para>All features deprecated in version 1.29.0 have
|
||||
been removed from Boost.Function.</para></listitem>
|
||||
|
||||
<listitem><para><code><classname>boost::function</classname></code>
|
||||
and <code><classname>boost::functionN</classname></code> objects
|
||||
can be assigned to 0 (semantically equivalent to calling
|
||||
<code><methodname
|
||||
alt="boost::function::clear">clear</methodname>()</code>) and
|
||||
compared against 0 (semantically equivalent to calling
|
||||
<code><methodname
|
||||
alt="boost::function::empty">empty</methodname>()</code>).</para></listitem>
|
||||
|
||||
<listitem><para>The Boost.Function code is now generated
|
||||
entirely by the <libraryname>Preprocessor</libraryname> library,
|
||||
so it is now possible to generate
|
||||
<code><classname>boost::function</classname></code> and
|
||||
<code><classname>boost::functionN</classname></code> class
|
||||
templates for any number of arguments.</para></listitem>
|
||||
|
||||
<listitem><para>The
|
||||
<classname>boost::bad_function_call</classname> exception class
|
||||
was introduced.</para></listitem>
|
||||
</itemizedlist>
|
||||
</listitem>
|
||||
|
||||
<listitem><para><emphasis role="bold">Version 1.29.0</emphasis>:
|
||||
Boost.Function has been partially redesigned to minimize the
|
||||
interface and make it cleaner. Several seldom- or never-used
|
||||
features of the older Boost.Function have been deprecated and will
|
||||
be removed in the near future. Here is a list of features that have
|
||||
been deprecated, the likely impact of the deprecations, and how to
|
||||
adjust your code:
|
||||
|
||||
<itemizedlist spacing="compact">
|
||||
<listitem><para>The <computeroutput>boost::function</computeroutput> class template syntax has
|
||||
changed. The old syntax, e.g., <computeroutput>boost::function<int, float,
|
||||
double, std::string></computeroutput>, has been changed to a more natural
|
||||
syntax <computeroutput>boost::function<int (float, double,
|
||||
std::string)></computeroutput>, where all return and argument types are
|
||||
encoded in a single function type parameter. Any other template
|
||||
parameters (e.g., the <computeroutput>Allocator</computeroutput>) follow this single
|
||||
parameter.</para>
|
||||
|
||||
<para> The resolution to this change depends on the
|
||||
abilities of your compiler: if your compiler supports template
|
||||
partial specialization and can parse function types (most do), modify
|
||||
your code to use the newer
|
||||
syntax (preferable) or directly use one of the
|
||||
<computeroutput>functionN</computeroutput> classes whose syntax has not
|
||||
changed. If your compiler does not support template partial
|
||||
specialization or function types, you must take the latter option and
|
||||
use the numbered Boost.Function classes. This option merely requires
|
||||
changing types such as <computeroutput>boost::function<void, int, int></computeroutput>
|
||||
to <computeroutput>boost::function2<void, int, int></computeroutput> (adding the number of
|
||||
function arguments to the end of the class name).</para>
|
||||
|
||||
<para> Support for the old syntax with the
|
||||
<computeroutput>boost::function</computeroutput> class template will persist for a short
|
||||
while, but will eventually be removed so that we can provide better
|
||||
error messages and link compatibility. </para></listitem>
|
||||
|
||||
<listitem><para>The invocation
|
||||
policy template parameter (<computeroutput>Policy</computeroutput>) has been deprecated
|
||||
and will be removed. There is no direct equivalent to this rarely
|
||||
used feature.</para></listitem>
|
||||
|
||||
<listitem><para>The mixin template parameter
|
||||
(<computeroutput>Mixin</computeroutput>) has been deprecated and will be removed. There
|
||||
is not direct equivalent to this rarely used feature.</para></listitem>
|
||||
|
||||
<listitem><para>The
|
||||
<computeroutput>set</computeroutput> methods have been deprecated and will be
|
||||
removed. Use the assignment operator instead.</para></listitem>
|
||||
</itemizedlist>
|
||||
</para>
|
||||
</listitem>
|
||||
</itemizedlist>
|
||||
</section>
|
Reference in New Issue
Block a user