Merged revisions 49339-49341,49541 via svnmerge from
https://svn.boost.org/svn/boost/trunk
........
r49339 | danieljames | 2008-10-15 11:25:07 +0100 (Wed, 15 Oct 2008) | 1 line
Note about change in boost 1.37.
........
r49340 | danieljames | 2008-10-15 11:26:55 +0100 (Wed, 15 Oct 2008) | 4 lines
Changed the warnings in the deprecated headers from 1.34.0 to errors. These
will be removed in a future version of Boost (probably 1.39.0).
........
r49341 | danieljames | 2008-10-15 11:34:15 +0100 (Wed, 15 Oct 2008) | 2 lines
Add note about changes to deprecated headers. Refs #2412.
........
r49541 | danieljames | 2008-11-02 22:32:00 +0000 (Sun, 02 Nov 2008) | 3 lines
Slightly more accurated comment - now that the headers cause errors, they've
moved past the deprecation stage (I think).
........
[SVN r49597]
Fixes#2392.
Change includes of <cmath> to <boost/config/no_tr1/config.hpp>.
Previously if Boost.TR1 was in the include path then including <cmath> pulls in all the new TR1 math functions, which in turn also requires linking to an external library. With auto-linking support this requires that library to have been built and be present in the library search path, even if the actual library under use is header only.
[SVN r49314]
as it doesn't always have the C++ overloads. Fixes#2264.
Merged revisions 48529,48674 via svnmerge from
https://svn.boost.org/svn/boost/trunk
........
r48529 | danieljames | 2008-09-02 11:31:26 +0100 (Tue, 02 Sep 2008) | 1 line
Always use c99 float function overloads on Dinkumware, as it doesn't always
have the C++ overloads. Refs #2264.
........
r48674 | danieljames | 2008-09-08 22:06:16 +0100 (Mon, 08 Sep 2008) | 7 lines
Reinstate the old choice of float functions on Dinkumware for all compilers
other than Visual C++.
It turns out that Borland uses Dinkumware but doesn't have the C99 float
overloads, so it only seems realistic to assume their existence on Visual C++.
Refs #2264.
........
[SVN r48739]
For the record: I removed the overload because it was causing an ambiguity that I was too lazy to work out at the time. It turned out this was because wchar_t was defined as unsigned short - using BOOST_NO_INTRINSIC_WCHAR_T was the right way to deal with this so the overload no longer needs to be disabled.
[SVN r33114]
1. hash_float is no longer dependent on the main hash header.
2. hash_float(0) == 0 which makes it easier to implement hash<complex>(),
although this might lead to users assuming that it can be expected even though
it isn't part of the documented interface.
[SVN r32780]
Daniel James
John Maddock
Beman Dawes
Rene Rivera
Douglas Gregor
nobody
Thomas Witt