July 2011 - Boost-users - lists.preview.boost.org

Trying to install 1.47 on Snow Leopard using clang toolset gives error "missing argument parent-requirements"
by doug livesey 14 Jul '11

14 Jul '11

Hi -- I'm trying to install boost 1.47.0 on my Snow Leopard machine, using clang, but I can't seem even to build the b2 tool. The error I get is "missing argument parent-requirements". The full output is here: https://gist.github.com/1081527 If anyone could offer me any advice, I'd be very grateful -- I'm dying to play with Phoenix! :) Cheers, Doug.

3 8

strong_typedef
by Dmitry Vinogradov 14 Jul '11

14 Jul '11

Hi everyone. Is <boost/strong_typedef.hpp> obsolete? Compiling this code: // -- cut --- #include <boost/strong_typedef.hpp> #include <boost/archive/binary_oarchive.hpp> // -- cut --- gives: 1>E:\Libraries\boost\boost/serialization/strong_typedef.hpp(45): warning C4005: 'BOOST_STRONG_TYPEDEF' : macro redefinition 1> E:\Libraries\boost\boost/strong_typedef.hpp(45) : see previous definition of 'BOOST_STRONG_TYPEDEF' Does one need to use <boost/serialization/strong_typedef.hpp> instead?

2 1

Serialization building on VS2010
by Zoltán Lengyel 14 Jul '11

14 Jul '11

Hello, I am having a LINK error when I try to include stuff for serialization: * #include <boost/archive/text_oarchive.hpp> #include <boost/archive/text_iarchive.hpp> 1>LINK : fatal error LNK1104: cannot open file 'libboost_serialization-vc100-mt-gd-1_46_1.lib' *So I am trying to build this, with the libs/serialization/vc7ide/BoostSerializationLibrary.sln using Microsoft Visual Studio 2010 Express on Windows 7 (64 bit). Building the solution finished with: *========== Build: 2 succeeded, 88 failed, 0 up-to-date, 0 skipped ==========* With a lot of: * 90>LINK : fatal error LNK1104: cannot open file 'boost_filesystem-vc100-mt-gd-1_46_1.lib'* So I tried next the libs/filesystem/v3/test/msvc10/filesystem-v3.sln. Building the solution finished with 3 failed, but it was because it didn't find some of the tutorial projects, so leaving those out from the build made: *========== Build: 10 succeeded, 0 failed, 0 up-to-date, 0 skipped ==========* But this doesn't seem to give me *boost_filesystem-vc100-mt-gd-1_46_1.lib *anywhere, so all the problems above remain. What am I doing wrong?

3 2

[random] Cauchy distribution
by Karsten Ahnert 14 Jul '11

14 Jul '11

Hi, I have the following code boost::mt19937 rng; boost::cauchy_distribution< double > cauchy( 0.0 , 0.1 ); for( size_t i=0 ; i<16 ; ++i ) { std::cout << cauchy( rng ) << " "; } which produced this sequence : 76513.4 4.3467e+06 -254805 -1.63299e+06 -6.96405e+06 233243 214884 883827 471904 268253 648798 140314 1.43562e+06 653319 -582905 91567.6 I think these number are much to high. The standard deviation should be 0.1. Does anyone knows what went wrong? Is this my failure? I use boost 1.46 and gcc 4.5.2.

3 4

parsing query
by Sean Farrow 14 Jul '11

14 Jul '11

Hi: I'm working on a project and have a file with lines of the following form: :function AddBrailleColors :Synopsis Provides a method for the user to assign custom colors to be marked in Braille. :Description Brings up a dialog for the user to assign the colors on the screen to Braille marking. :Param String/strForeground Enter the variable containing the RGB string for the foreground color. :Param String/strBackground Enter the RGB string for the background color. :Param String/sApp Enter the value for the app file name to be used. :Category Colors What boost library do people feel is the best one to use to parse this form of input, boost.Regex, boost.proto or boost.spirit? And given the input, what would be the best way of going about doing this? I need the function, Synopsis, Description, and then the parameters ideally placed in separate variables. Any help appreciated. Cheers Sean.

3 2

[1.47.0] Release notice
by Beman Dawes 14 Jul '11

14 Jul '11

Release 1.47.0 of the Boost C++ Libraries is now available. These open-source libraries work well with the C++ Standard Library, and are usable across a broad spectrum of applications. The Boost license encourages both commercial and non-commercial use. This release contains four new libraries (Chrono, Geometry, Phoenix, Ratio) and numerous enhancements and bug fixes for existing libraries. For details, including download links, see http://www.boost.org/users/news/version_1_47_0 The release can also be downloaded directly from SourceForge. See http://sourceforge.net/projects/boost/files/ To install this release on your system, see http://www.boost.org/doc/libs/release/more/getting_started/index.html Thanks, --The Boost release team Beman Dawes Daniel James Eric Niebler Rene Rivera Vladimir Prus

3 2

[serialization] Storing something that could be primitive or non-default constructable.
by Noah Roberts 13 Jul '11

13 Jul '11

template < typename T > struct storing { storing(T const& t) : val(t) {} T val; }; namespace boost { namespace serialization { template < typename Archive, typename T > void save_construct_data(Archive & ar, storing<T> const* ptr, unsigned int const) { // what to put here? } template < typename Archive, typename T > void load_construct_data(Archive & ar, storing<T> * ptr, unsigned int const) { // what here? } }} If I try to store val as a pointer then I can't instantiate with anything serialization considers "primitive". For instance, if I try to serialize a storing<std::string> then I'll get errors about std::string not having a serialization routine even if I include boost/serialization/string.hpp. If I try to load into a temporary variable then I run into the problem of having to construct one, and sometimes I need extra information to do so (I have the serialization routines dealing with this in such cases). Any ideas?

1 0

Re: [Boost-users] [Range] sub_range and list not working together
by Brian Wood 13 Jul '11

13 Jul '11

Neil Groves: > This compiler error is to be expected because your code is calling the > size() member function. The size() member function requires that the > underlying range is a model of the RandomAccessRange Concept. Since you are > using a sub_range of a std::list and the std::list has bidirectional > iterators, the sub_range is a model of the BidirectionalRange Concept. > > This has changed between boost versions. The boost::size(Range&) function > was modified to only work with ranges that model the RandomAccessRange > Concept because the performance complexity was inconsistent with typical > expectations. For example, in your case the sub_range size would have been > O(N) despite the container probably having an O(1) implementation of size(). > The complexity of std::list size() is not mandated by the standard to be > O(1), even though it is recommended. If one wishes to pay the price and > wishes to have a more general 'size' calculation I recommend using > boost::distance(Range&). Thanks. I found this thread which is closely related to what I'm wondering. http://boost.2283326.n4.nabble.com/Distance-size-of-boost-ranges-for-std-se… I haven't checked into this much, but would using boost::distance when the underlying container is a deque or vector, be slower than using the container's size? Regards, Brian Wood Ebenezer Enterprises http://webEbenezer.net

2 1

[io::streams] Using array device and std::output_iterator
by Ovanes Markarian 13 Jul '11

13 Jul '11

Hello *, I tried to use an array-device based stream and wantet to pass the stream to std::output_iterator or std::istream_iterator, but unfortunately, I get a compilation error with gcc 4.3.5. Boost::IOStreams docu states that the io::stream is either derived from std::basic_istream or std::basic_ostream or both dependent on the underlying device category. array has seekable category, so I'd expect io::stream to derive from both and be compatible with ostream_iterator or istream_iterator. Here is the code snippet: typedef unsigned char byte; typedef io::basic_array<byte> array_device; typedef io::stream<array_device> array_stream; array_stream ios_(ptr_to_byte_array); std::istream_iterator<byte> in(ios_); And the last line results in the error stating: src/chunk_reading_iterator_test.cpp: In member function 'void chunk_reading_iterator_suite::ctor::test_method()': src/chunk_reading_iterator_test.cpp:86: error: no matching function for call to 'std::istream_iterator<unsigned char, char, std::char_traits<char>, int>::istream_iterator(chunk_reading_iterator_suite::<unnamed>::array_stream&)' Thanks for any suggestions, Ovanes

1 0

[regex] Segmentation fault on regex_search only on CentOS
by Alessandro Candini 13 Jul '11

13 Jul '11

I have compiled the same C++ source on two machines: 1 - Ubuntu 11.04, 2.6.38-10-generic #46-Ubuntu SMP Tue Jun 28 15:07:17 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux 2 - CentOS release 5.3, 2.6.18-128.1.14.el5 #1 SMP Wed Jun 17 06:40:54 EDT 2009 i686 i686 i386 GNU/Linux On Ubuntu I have g++-4.5.2, on CentOs g++-4.4.4 and on both I have boost-1.42.0. My source compiles perfectly on both machines, but on the CentOS one I get a Segmentetion Fault during the execution. Using some prints, I found out where it happens: ... boost::regex grepGPP("Monthly Ecosystem GPP", boost::regex::egrep); cerr << "DEBUG BEFORE!" << endl; boost::regex_search (currGPP, grepGPP) cerr << "DEBUG AFTER!" << endl; ... The segmentation fault comes during the execution of regex_search, beacause "DEBUG AFTER" is not printed. Any ideas on how to solve this problem? Thanks in advance. -- Alessandro Candini MEEO S.r.l. Via Saragat 9 I-44122 Ferrara, Italy Tel: +39 0532 1861501 Fax: +39 0532 1861637 http://www.meeo.it ======================================== "ATTENZIONE:le informazioni contenute in questo messaggio sono da considerarsi confidenziali ed il loro utilizzo è riservato unicamente al destinatario sopra indicato. Chi dovesse ricevere questo messaggio per errore è tenuto ad informare il mittente ed a rimuoverlo definitivamente da ogni supporto elettronico o cartaceo." "WARNING:This message contains confidential and/or proprietary information which may be subject to privilege or immunity and which is intended for use of its addressee only. Should you receive this message in error, you are kindly requested to inform the sender and to definitively remove it from any paper or electronic format."

3 2