- Boost - lists.boost.org

[Pool] Patches
by DUPUIS Etienne 17 Jul '12

17 Jul '12

Greetings, https://svn.boost.org/svn/boost/sandbox/pool at revision 79460 contains a solution for tickets #3789, #5902, #6561, #6610, #6701, #6718, #6865 and #6867. Related test cases for each ticket are also present. By the way, the Pool tests fail in the trunk; a missing dependency on Boost.System, which I added to the JamFile in sand box. https://svn.boost.org/svn/boost/sandbox/pool at revision 79460 does not contain any other new features or modifications other than those related to the above tickets. As Boost.Pool currently has no maintainer and is thus orphaned, and also since I am leaving the mailing list, I reassigned these tickets to John Maddock since he was the last to commit code changes into Boost.Pool. Regards, Étienne Dupuis Ce message et toutes les pièces jointes sont confidentiels et établis à l'intention exclusive de ses destinataires. Toute modification, édition, utilisation ou diffusion non autorisée est interdite. Si vous avez reçu ce message par erreur, merci de nous en avertir immédiatement. ATEME décline toute responsabilité au titre de ce message s'il a été altéré, déformé, falsifié ou encore édité ou diffusé sans autorisation. This message and any attachments are confidential and intended solely for the addressees. Any unauthorized modification, edition, use or dissemination is prohibited. If you have received this message by mistake, please notify us immediately. ATEME decline all responsibility for this message if it has been altered, deformed, falsified or even edited or disseminated without authorization. Note: To protect against computer viruses, e-mail programs may prevent sending or receiving certain types of file attachments.

2 1

[mpl] std::integral_constant support?
by Eric Niebler 17 Jul '12

17 Jul '12

The following reasonable-seeming use of mpl::plus doesn't compile: #include <utility> #include <boost/mpl/plus.hpp> typedef std::integral_constant<int, 1> one; typedef boost::mpl::plus<one, one>::type two; That's because mpl only works with its own integral constant wrappers, not the standard one. That seems unfortunate to me. Is there any interest in supporting this? Here's the error (from clang trunk with glibc++): 1> In file included from main.cpp:2: 1> In file included from /home/Eric/boost/org/trunk/boost/mpl/plus.hpp:19: 1> In file included from /home/Eric/boost/org/trunk/boost/mpl/aux_/arithmetic_op.hpp:34: 1> In file included from /home/Eric/boost/org/trunk/boost/mpl/aux_/include_preprocessed.hpp:37: 1> /home/Eric/boost/org/trunk/boost/mpl/aux_/preprocessed/gcc/plus.hpp:60:25: error: no type named 'tag' in 'std::integral_constant<int, 1>' 1> typedef typename T::tag type; 1> ~~~~~~~~~~~~^~~ 1> /home/Eric/boost/org/trunk/boost/mpl/aux_/preprocessed/gcc/plus.hpp:111:20: note: in instantiation of template class 'boost::mpl::plus_tag<std::integral_constant<int, 1> >' requested here 1> typename plus_tag<N1>::type 1> ^ -- Eric Niebler BoostPro Computing http://www.boostpro.com

2 1

[Memory][SmartPtr][Interprocess] Is there an interest in a Boost library more or less c++11 compliant?
by Vicente J. Botet Escriba 16 Jul '12

16 Jul '12

Hi, Boost has a lot of pieces of the c++11 header <memory>, shared_ptr, weak_ptr , ... in Boost.SmartPtr, unique_ptr, allocator argument tag, uses_allocator ... in Boost.Interprocess. Other are already in the C++03 <memory> header. Others are missing, as pointer_traits, default_delete, ... I would like we complete all these features and move them to a Boost.Memory library smoothly (something like the Boost.Utility). As these are standard features, I propose to use directly the boost namespace for them. boost memory.hpp memory pointer_traits_hpp ... unique_ptr.hpp shared_ptr.hpp weak_ptr.hpp ... What do you think? Best, Vicente

2 1

[type_traits] has_equal_to< std::vector<T> > always true_
by lcaminiti 15 Jul '12

15 Jul '12

-- View this message in context: http://boost.2283326.n4.nabble.com/boost-type-traits-has-equal-to-std-vecto… Sent from the Boost - Dev mailing list archive at Nabble.com.

11 33

[1.50.0] PDF documentation available
by John Maddock 15 Jul '12

15 Jul '12

With apologies for being so late with these.... The PDF build of Boost's documentation for 1.50 is available from the usual SF site: https://sourceforge.net/projects/boost/files/boost-docs/1.50/ John.

2 1

[atomic] trunk doesn't build with VC++
by Luke Elliott 14 Jul '12

14 Jul '12

compile-c-c++ ..\..\..\bin.v2\libs\atomic\build\msvc-9.0\debug\threading-multi\lockpool.obj lockpool.cpp D:\dev\checkouts\boost-trunk\boost/atomic/detail/interlocked.hpp(125) : error C2039: 'platform_cmpxchg32' : is not a member of 'boost::atomics::detail' D:\dev\checkouts\boost-trunk\boost/atomic/detail/interlocked.hpp(125) : error C3861: 'platform_cmpxchg32': identifier not found D:\dev\checkouts\boost-trunk\boost/atomic/detail/interlocked.hpp(127) : warning C4800: 'boost::uint32_t' : forcing value to bool 'true' or 'false' (performance warning) Should it be using platform_cmpxchg32_strong at line 125 of interlocked.hpp? And return (0 != expected) (or something) on line 127 to clean up the warning? Best regards Luke Elliott.

1 0

Clang Darwin trunk Cray 8.0 and max_digits10 support - problem in config?
by Paul A. Bristow 14 Jul '12

14 Jul '12

I note that the test of ztest_max_digits10 and zztest_max_digits10 in http://www.boost.org/development/tests/trunk/developer/math.html both fail for these platforms. ztest_max_digits10 tests of native std::numeric_limits<>::max_digits10 is supported. zztest_max_digits10 test if BOOST_NO_NUMERIC_LIMITS_LOWEST is a proxy to signal support. where using std::numeric_limits<>::max_digits10 should be possible using BOOST_NO_NUMERIC_LIMITS_LOWEST as a proxy for Clang the messages are In file included from ../libs/math/test/zztest_max_digits10.cpp:27: In file included from ../boost/config.hpp:40: ../boost/config/select_stdlib_config.hpp:18:12: fatal error: 'cstddef' file not found # include <cstddef> In file included from ../libs/math/test/ztest_max_digits10.cpp:27: In file included from ../boost/config.hpp:40: ../boost/config/select_stdlib_config.hpp:18:12: fatal error: 'cstddef' file not found or for Cray CC-1353 crayc++: INTERNAL File = /opt/gcc/4.4.4/snos/include/g++/bits/move.h, Line = 34 CIF Error #include <cstddef> ^ This appears to be a problem in the config - a missing include. Suggestions? Paul --- Paul A. Bristow, Prizet Farmhouse, Kendal LA8 8AB UK +44 1539 561830 07714330204 pbristow(a)hetp.u-net.com

4 24

[asio] boost::asio::read with empty input vector leads to an infinite loop
by Michael Kochetkov 13 Jul '12

13 Jul '12

Hello, In the code bellow I have forgotten to set the input vector (request) size. Is the code really supposed to react as an infinite loop (no errors, length is always 0, boost::asio::read returns immediately) or such behavior is a defect? for (;;) { std::vector<uint8_t> request; boost::system::error_code error; size_t length = boost::asio::read(sock, boost::asio::buffer(request), error); if (error == boost::asio::error::eof) break; else if (error) throw my_exception(L"Socket error"); ... } Thank you in advance, -- Michael Kochetkov

4 5

[filesystem] 1.49 linking with c++0x
by Daniel Larimer 13 Jul '12

13 Jul '12

Given: // cp.cpp #include <boost/filesystem.hpp> int main( int argc, char** argv ) { if( argc < 3 ) return -1; boost::filesystem::copy_file( argv[1], argv[2] ); return 0; } g++ -o cp cp.cpp -std=c++0x -I /usr/local/include /usr/local/lib/libboost_filesystem.a /usr/local/lib/libboost_system.a Undefined symbols for architecture x86_64: "boost::filesystem3::detail::copy_file(boost::filesystem3::path const&, boost::filesystem3::path const&, boost::filesystem3::copy_option, boost::system::error_code*)", referenced from: boost::filesystem3::copy_file(boost::filesystem3::path const&, boost::filesystem3::path const&) in ccUAyvBD.o ld: symbol(s) not found for architecture x86_64 collect2: error: ld returned 1 exit status If I remove the -std=c++0x flag then it links just fine. g++ --version g++ (MacPorts gcc47 4.7.0_3) 4.7.0 Copyright (C) 2012 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. Dan

6 9

Boost.config limits_test testcase and qnan checks.
by Matthew Markland 13 Jul '12

13 Jul '12

First an introduction; my name is Matt Markland and I support the Cray Compiling Environment (CCE) C/C++ compiler for Cray, Inc. We (Cray) are in the process of improving our Boost support and currently have an intern doing some work for us on this path. While working on Boost.config, he has run into a testcase failure with the limits_test function test_float_limits(). With default options, CCE fails the qnan tests due to the fact that we do not conform to the IEEE specification. CCE is a little different here in that by default it runs at a higher optimization level then other compilers. Gcc will fail this portion of the test if you compile with optimization on and -ffast-math. My question is whether it is valid to test the qnan behavior when a platform does not claim compliance? It seems to me that these checks should be wrapped in an is_iec559 check. Thoughts? Thanks for your time! Matt ---- Matthew Markland Compiler Front-End and Libraries C/C++ Front-End markland(a)cray.com 651-605-9186

3 2