Boost release1.45.0 beta 1 is now available from SourceForge. For those who downloaded release candidate 1, note that beta 1 was build from a slightly later release candidate. See http://sourceforge.net/projects/boost/files/ This release contains numerous enhancements and bug fixes for existing libraries. For details of what's in the release, see http://beta.boost.org/users/news/version_1_45_0. Note that the links to files on this web page are for the final release - use the SourceForge link above to get the beta files. Please download the beta, give it a try, and report any problems you encounter. There are still a few serious bugs outstanding, and we will be working on clearing those before the final release. Thanks, -- The Boost Release Team
On Nov 10, 2010, at 5:13 AM, Beman Dawes wrote:
Boost release1.45.0 beta 1 is now available from SourceForge. For those who downloaded release candidate 1, note that beta 1 was build from a slightly later release candidate.
See http://sourceforge.net/projects/boost/files/
This release contains numerous enhancements and bug fixes for existing libraries.
For details of what's in the release, see http://beta.boost.org/users/news/version_1_45_0. Note that the links to files on this web page are for the final release - use the SourceForge link above to get the beta files.
Please download the beta, give it a try, and report any problems you encounter.
Built without errors on Mac OS X 10.6.4 (gcc 4.2.1) -- Marshall
On 10 November 2010 13:13, Beman Dawes
For details of what's in the release, see http://beta.boost.org/users/news/version_1_45_0. Note that the links to files on this web page are for the final release - use the SourceForge link above to get the beta files.
This time I've uploaded the beta docs, with a redirect to fix the links, so they should work for the moment. I'm not sure if I'll do that for future releases as it's a bit of a hassle and the beta site isn't trustworthy enough for normal use. Also, I'll have to break them when I prepare for the full release. Daniel
I just compiled my project with the 1.45 beta and got the following error: boost_1_45_0_beta1/boost/property_tree/string_path.hpp(202): error C3861: 'assert': identifier not found Build info: VC2010 Release Win32 It succeeds in Debug, but not in Release. I didn't encounter this with 1.44. It's a minor issue I can work around. -----Original Message----- From: boost-users-bounces@lists.boost.org [mailto:boost-users-bounces@lists.boost.org] On Behalf Of Beman Dawes Sent: Wednesday, November 10, 2010 8:13 AM To: Boost Developers List; Boost users list Subject: [Boost-users] [1.45.0] Beta 1 available from SourceForge Boost release1.45.0 beta 1 is now available from SourceForge. For those who downloaded release candidate 1, note that beta 1 was build from a slightly later release candidate. See http://sourceforge.net/projects/boost/files/ This release contains numerous enhancements and bug fixes for existing libraries. For details of what's in the release, see http://beta.boost.org/users/news/version_1_45_0. Note that the links to files on this web page are for the final release - use the SourceForge link above to get the beta files. Please download the beta, give it a try, and report any problems you encounter. There are still a few serious bugs outstanding, and we will be working on clearing those before the final release. Thanks, -- The Boost Release Team _______________________________________________ Boost-users mailing list Boost-users@lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users
On 11/11/2010 9:23 AM, Phil Ratzloff wrote:
I just compiled my project with the 1.45 beta and got the following error: boost_1_45_0_beta1/boost/property_tree/string_path.hpp(202): error C3861: 'assert': identifier not found
Build info: VC2010 Release Win32
It succeeds in Debug, but not in Release. I didn't encounter this with 1.44. It's a minor issue I can work around.
Sounds like a simple matter of adding #include <cassert> in the right place. Sebastian, we're going to hold the release for this. Can you please address it ASAP? And a suggestion for release+1: BOOST_ASSERT is to be preferred over assert in Boost code. Thanks, -- Eric Niebler BoostPro Computing http://www.boostpro.com
On 11/11/2010 9:41 AM, Eric Niebler wrote:
On 11/11/2010 9:23 AM, Phil Ratzloff wrote:
I just compiled my project with the 1.45 beta and got the following error: boost_1_45_0_beta1/boost/property_tree/string_path.hpp(202): error C3861: 'assert': identifier not found
Build info: VC2010 Release Win32
It succeeds in Debug, but not in Release. I didn't encounter this with 1.44. It's a minor issue I can work around.
Sounds like a simple matter of adding #include <cassert> in the right place. Sebastian, we're going to hold the release for this. Can you please address it ASAP?
Heck, this one was trivial so I did it myself. Hope nobody takes offense.
And a suggestion for release+1: BOOST_ASSERT is to be preferred over assert in Boost code.
This one still holds, I think. If BOOST_ASSERT is *always* to be preferred over C's assert macro, then we should probably add that to the inspection report, right? -- Eric Niebler BoostPro Computing http://www.boostpro.com
On 11.11.2010, at 21:38, Eric Niebler wrote:
On 11/11/2010 9:41 AM, Eric Niebler wrote:
On 11/11/2010 9:23 AM, Phil Ratzloff wrote:
I just compiled my project with the 1.45 beta and got the following error: boost_1_45_0_beta1/boost/property_tree/string_path.hpp(202): error C3861: 'assert': identifier not found
Build info: VC2010 Release Win32
It succeeds in Debug, but not in Release. I didn't encounter this with 1.44. It's a minor issue I can work around.
Sounds like a simple matter of adding #include <cassert> in the right place. Sebastian, we're going to hold the release for this. Can you please address it ASAP?
Heck, this one was trivial so I did it myself. Hope nobody takes offense.
Awesome, thanks. I couldn't have done it until sometime tomorrow.
And a suggestion for release+1: BOOST_ASSERT is to be preferred over assert in Boost code.
This one still holds, I think. If BOOST_ASSERT is *always* to be preferred over C's assert macro, then we should probably add that to the inspection report, right?
That would probably a good idea. Sebastian
participants (6)
-
Beman Dawes -
Daniel James -
Eric Niebler -
Marshall Clow -
Phil Ratzloff -
Sebastian Redl