|
Boost-Commit : |
Subject: [Boost-commit] svn:boost r81227 - in website/public_html/live: feed/news generated generated/state users/news
From: dnljms_at_[hidden]
Date: 2012-11-06 15:39:31
Author: danieljames
Date: 2012-11-06 15:39:30 EST (Tue, 06 Nov 2012)
New Revision: 81227
URL: http://svn.boost.org/trac/boost/changeset/81227
Log:
Website: Rob Stewart's editing suggestions.
Plus mark up code a bit more consistently.
Text files modified:
website/public_html/live/feed/news/result_of_1_52_0.qbk | 25 +++++++++++------------
website/public_html/live/generated/news.rss | 41 ++++++++++++++++++++-------------------
website/public_html/live/generated/state/feed-pages.txt | 4 +-
website/public_html/live/users/news/a_special_note_for_boost_1_52_0_and_higher.html | 41 ++++++++++++++++++++-------------------
4 files changed, 56 insertions(+), 55 deletions(-)
Modified: website/public_html/live/feed/news/result_of_1_52_0.qbk
==============================================================================
--- website/public_html/live/feed/news/result_of_1_52_0.qbk (original)
+++ website/public_html/live/feed/news/result_of_1_52_0.qbk 2012-11-06 15:39:30 EST (Tue, 06 Nov 2012)
@@ -5,9 +5,9 @@
[last-revision Tue 6 Nov 2012 09:27:25 GMT]
]
-Starting in Boost 1.52.0, the `boost::result_of` component defaults to an
-implementation that uses the C++11 decltype keyword to deduce the return
-type of callables on compilers with strong decltype support. As
+Starting with Boost 1.52.0, the `boost::result_of` component defaults to an
+implementation that uses the C++11 `decltype` keyword to deduce the return
+type of callables on compilers with strong `decltype` support. As
`boost::result_of` is a key piece of library infrastructure, we at Boost
have found this change to be moderately disruptive. You should be aware
of the issue when making the decision to upgrade from an older version
@@ -15,17 +15,16 @@
[section Why the Change Was Made]
-In C++11, `std::result_of` is required to use decltype. Boost has decided
-to change its implementation to minimize the differences between
-boost::result_of and std::result_of. Also, the use of decltype should
-help to improve compile times and increase the accuracy of the type
-computation.
+`boost::result_of` has been changed to use `decltype` to make it more
+consistent with `std::result_of` (when sufficient compiler support is
+available). Also, the use of `decltype` should help to improve compile times and
+increase the accuracy of the type computation.
[endsect]
[section Who is Affected]
-If you use a compiler with sufficiently bug-free decltype support
+If you use a compiler with sufficiently bug-free `decltype` support
(including
[@http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2011/n3276.pdf N3276]),
then you will get the new behavior. At the time of writing (Nov 4,
@@ -37,7 +36,7 @@
[section What Problems Can the Change Cause?]
The use of `decltype` in `result_of` can result in a different type being
-computed than if the now-obsolete TR1 result_of protocol. This will
+computed than with the now-obsolete TR1 `result_of` protocol. This will
often be the case for incorrectly written TR1-style function objects
that misreport their result types. This is unfortunately too common. But
it can even happen for some correctly written function objects.
@@ -47,9 +46,9 @@
[section Where Can I Learn More?]
Please see the documentation for
-[@http://www.boost.org/doc/libs/1_52_0/libs/utility/utility.htm#result_of boost::result_of]
-to understand the differences between TR1 result_of and decltype
-result_of, and to find out how you can write your code to accommodate
+[@http://www.boost.org/doc/libs/1_52_0/libs/utility/utility.htm#result_of `boost::result_of`]
+to understand the differences between TR1 `result_of` and `decltype`
+`result_of`, and to find out how you can write your code to accommodate
both.
[endsect]
Modified: website/public_html/live/generated/news.rss
Modified: website/public_html/live/generated/state/feed-pages.txt
Modified: website/public_html/live/users/news/a_special_note_for_boost_1_52_0_and_higher.html
Boost-Commit list run by bdawes at acm.org, david.abrahams at rcn.com, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk
==============================================================================
--- website/public_html/live/generated/news.rss (original)
+++ website/public_html/live/generated/news.rss 2012-11-06 15:39:30 EST (Tue, 06 Nov 2012)
@@ -10,30 +10,30 @@
<p>
- Starting in Boost 1.52.0, the <code><span class="identifier">boost</span><span class="special">::</span><span class="identifier">result_of</span></code>
- component defaults to an implementation that uses the C++11 decltype keyword
- to deduce the return type of callables on compilers with strong decltype support.
- As <code><span class="identifier">boost</span><span class="special">::</span><span class="identifier">result_of</span></code> is a key piece of library infrastructure,
- we at Boost have found this change to be moderately disruptive. You should be
- aware of the issue when making the decision to upgrade from an older version
- of Boost.
+ Starting with Boost 1.52.0, the <code><span class="identifier">boost</span><span class="special">::</span><span class="identifier">result_of</span></code>
+ component defaults to an implementation that uses the C++11 <code><span class="identifier">decltype</span></code>
+ keyword to deduce the return type of callables on compilers with strong <code><span class="identifier">decltype</span></code> support. As <code><span class="identifier">boost</span><span class="special">::</span><span class="identifier">result_of</span></code>
+ is a key piece of library infrastructure, we at Boost have found this change
+ to be moderately disruptive. You should be aware of the issue when making the
+ decision to upgrade from an older version of Boost.
</p>
<div id="a_special_note_for_boost_1_52_0_and_higher.why_the_change_was_made">
<h3><span class="link">Why
the Change Was Made</span></h3>
<p>
- In C++11, <code><span class="identifier">std</span><span class="special">::</span><span class="identifier">result_of</span></code> is required to use decltype. Boost
- has decided to change its implementation to minimize the differences between
- boost::result_of and std::result_of. Also, the use of decltype should help
- to improve compile times and increase the accuracy of the type computation.
+ <code><span class="identifier">boost</span><span class="special">::</span><span class="identifier">result_of</span></code> has been changed to use <code><span class="identifier">decltype</span></code> to make it more consistent with
+ <code><span class="identifier">std</span><span class="special">::</span><span class="identifier">result_of</span></code> (when sufficient compiler support
+ is available). Also, the use of <code><span class="identifier">decltype</span></code>
+ should help to improve compile times and increase the accuracy of the type
+ computation.
</p>
</div>
<div id="a_special_note_for_boost_1_52_0_and_higher.who_is_affected">
<h3><span class="link">Who
is Affected</span></h3>
<p>
- If you use a compiler with sufficiently bug-free decltype support (including
- <a href="http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2011/n3276.pdf">N3276</a>),
+ If you use a compiler with sufficiently bug-free <code><span class="identifier">decltype</span></code>
+ support (including <a href="http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2011/n3276.pdf">N3276</a>),
then you will get the new behavior. At the time of writing (Nov 4, 2012), the
only compiler in that category is Clang 3.1, but as other compilers improve,
this will change.
@@ -44,19 +44,20 @@
Problems Can the Change Cause?</span></h3>
<p>
The use of <code><span class="identifier">decltype</span></code> in <code><span class="identifier">result_of</span></code> can result in a different type
- being computed than if the now-obsolete TR1 result_of protocol. This will often
- be the case for incorrectly written TR1-style function objects that misreport
- their result types. This is unfortunately too common. But it can even happen
- for some correctly written function objects.
+ being computed than with the now-obsolete TR1 <code><span class="identifier">result_of</span></code>
+ protocol. This will often be the case for incorrectly written TR1-style function
+ objects that misreport their result types. This is unfortunately too common.
+ But it can even happen for some correctly written function objects.
</p>
</div>
<div id="a_special_note_for_boost_1_52_0_and_higher.where_can_i_learn_more_">
<h3><span class="link">Where
Can I Learn More?</span></h3>
<p>
- Please see the documentation for <a href="http://www.boost.org/doc/libs/1_52_0/libs/utility/utility.htm#result_of">boost::result_of</a>
- to understand the differences between TR1 result_of and decltype result_of,
- and to find out how you can write your code to accommodate both.
+ Please see the documentation for <a href="http://www.boost.org/doc/libs/1_52_0/libs/utility/utility.htm#result_of"><code><span class="identifier">boost</span><span class="special">::</span><span class="identifier">result_of</span></code></a>
+ to understand the differences between TR1 <code><span class="identifier">result_of</span></code>
+ and <code><span class="identifier">decltype</span></code> <code><span class="identifier">result_of</span></code>, and to find out how you can write
+ your code to accommodate both.
</p>
</div>
</description></item><item><title>Version 1.52.0</title><link>http://www.boost.org/users/history/version_1_52_0.html><guid>http://www.boost.org/users/history/version_1_52_0.html><pubDate>Mon, 5 Nov 2012 08:05:58 -0800</pubDate><description>
==============================================================================
--- website/public_html/live/generated/state/feed-pages.txt (original)
+++ website/public_html/live/generated/state/feed-pages.txt 2012-11-06 15:39:30 EST (Tue, 06 Nov 2012)
@@ -2033,10 +2033,10 @@
" Important information for users of boost::result_of.
"
-qbk_hash
-"ea59372ceca7dc53ef72162204dcbeeb08481296a266cf6ee1fa200da4d3d571
+"13982f0efac8036dc03adbfe7f0d428604d69fe005fd65965ba4f0d85e267451
-release_status
-rss_hash
-"5432fa606f2251d9d7f8e073c036882e3b4c1e729ad12cd91503ecad9694ac52
+"03f70871d3f17740bcf54a1cbae505b7e8f85ef267c99470b94c45ff930ad65e
-title
"A Special Note for Boost 1.52.0 and Higher
-type
==============================================================================
--- website/public_html/live/users/news/a_special_note_for_boost_1_52_0_and_higher.html (original)
+++ website/public_html/live/users/news/a_special_note_for_boost_1_52_0_and_higher.html 2012-11-06 15:39:30 EST (Tue, 06 Nov 2012)
@@ -36,30 +36,30 @@
<p>
- Starting in Boost 1.52.0, the <code><span class="identifier">boost</span><span class="special">::</span><span class="identifier">result_of</span></code>
- component defaults to an implementation that uses the C++11 decltype keyword
- to deduce the return type of callables on compilers with strong decltype support.
- As <code><span class="identifier">boost</span><span class="special">::</span><span class="identifier">result_of</span></code> is a key piece of library infrastructure,
- we at Boost have found this change to be moderately disruptive. You should be
- aware of the issue when making the decision to upgrade from an older version
- of Boost.
+ Starting with Boost 1.52.0, the <code><span class="identifier">boost</span><span class="special">::</span><span class="identifier">result_of</span></code>
+ component defaults to an implementation that uses the C++11 <code><span class="identifier">decltype</span></code>
+ keyword to deduce the return type of callables on compilers with strong <code><span class="identifier">decltype</span></code> support. As <code><span class="identifier">boost</span><span class="special">::</span><span class="identifier">result_of</span></code>
+ is a key piece of library infrastructure, we at Boost have found this change
+ to be moderately disruptive. You should be aware of the issue when making the
+ decision to upgrade from an older version of Boost.
</p>
<div id="a_special_note_for_boost_1_52_0_and_higher.why_the_change_was_made">
<h3><span class="link">Why
the Change Was Made</span></h3>
<p>
- In C++11, <code><span class="identifier">std</span><span class="special">::</span><span class="identifier">result_of</span></code> is required to use decltype. Boost
- has decided to change its implementation to minimize the differences between
- boost::result_of and std::result_of. Also, the use of decltype should help
- to improve compile times and increase the accuracy of the type computation.
+ <code><span class="identifier">boost</span><span class="special">::</span><span class="identifier">result_of</span></code> has been changed to use <code><span class="identifier">decltype</span></code> to make it more consistent with
+ <code><span class="identifier">std</span><span class="special">::</span><span class="identifier">result_of</span></code> (when sufficient compiler support
+ is available). Also, the use of <code><span class="identifier">decltype</span></code>
+ should help to improve compile times and increase the accuracy of the type
+ computation.
</p>
</div>
<div id="a_special_note_for_boost_1_52_0_and_higher.who_is_affected">
<h3><span class="link">Who
is Affected</span></h3>
<p>
- If you use a compiler with sufficiently bug-free decltype support (including
- N3276),
+ If you use a compiler with sufficiently bug-free <code><span class="identifier">decltype</span></code>
+ support (including N3276),
then you will get the new behavior. At the time of writing (Nov 4, 2012), the
only compiler in that category is Clang 3.1, but as other compilers improve,
this will change.
@@ -70,19 +70,20 @@
Problems Can the Change Cause?</span></h3>
<p>
The use of <code><span class="identifier">decltype</span></code> in <code><span class="identifier">result_of</span></code> can result in a different type
- being computed than if the now-obsolete TR1 result_of protocol. This will often
- be the case for incorrectly written TR1-style function objects that misreport
- their result types. This is unfortunately too common. But it can even happen
- for some correctly written function objects.
+ being computed than with the now-obsolete TR1 <code><span class="identifier">result_of</span></code>
+ protocol. This will often be the case for incorrectly written TR1-style function
+ objects that misreport their result types. This is unfortunately too common.
+ But it can even happen for some correctly written function objects.
</p>
</div>
<div id="a_special_note_for_boost_1_52_0_and_higher.where_can_i_learn_more_">
<h3><span class="link">Where
Can I Learn More?</span></h3>
<p>
- Please see the documentation for boost::result_of
- to understand the differences between TR1 result_of and decltype result_of,
- and to find out how you can write your code to accommodate both.
+ Please see the documentation for boost::result_of
+ to understand the differences between TR1 <code><span class="identifier">result_of</span></code>
+ and <code><span class="identifier">decltype</span></code> <code><span class="identifier">result_of</span></code>, and to find out how you can write
+ your code to accommodate both.
</p>
</div>
</div>