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

Re: [Boost-users] thread_specific_ptr problem
by Vertleyb, Arkadiy 28 Oct '09

28 Oct '09

Hi all, The following code demonstrates thread_specific_ptr problem while loading/unloading a shared library. Apparently some resource is not cleanned up. Can somebody comment on this? Thanks, Arkadiy lib.cpp: ------- #include <string> #include <boost/thread.hpp> boost::thread_specific_ptr < std::string > tls_with_mmap; main.cpp: ---------- #include <stdint.h> #include <stdlib.h> #include <dlfcn.h> #include <stdio.h> int main( int argc, const char* argv[]) { if( argc < 3 ) { printf("usage %s <dlname> <repeat count>\n", argv[0]); return 1; } const char* dlname = argv[1]; uint16_t iters = atoi(argv[2]); for( uint16_t i = 0; i < iters; ++i ) { printf("attempt %02d\n", i); void* handle = ::dlopen(dlname, RTLD_NOW ); if( handle ) ::dlclose(handle); else { printf("dlopen failed\n"); break; } } return 0; } build.sh: -------- BOOST_VER=38 CCFLAGS="-Wcomment -Wformat -Wmissing-braces -Wparentheses -Wreturn-type -Wsign-compare -Wstrict-aliasing -Wswitch -Wtrigraphs -Wunknown-pragmas -Wunused-function -Wunused-label -Wunused-value -Wunused-variable -Wextra -g -O0 -fno-inline -fexceptions -ftemplate-depth-128 -Wnon-virtual-dtor -I/usr/include/nptl -I/builder/3rdParty/boost/v${BOOST_VER}.0/include -D__NO_INLINE__=1 -D_DEBUG -DDEBUG" g++ -x c++ -m32 ${CCFLAGS} -fPIC -pipe -o "lib.o" -c "lib.cpp" g++ -m32 -o boost_thread_test.so -shared -Wl,-Bsymbolic -Wl,-h -Wl,boost_thread_test.so -Wl,--no-undefined -Wl,--start-group lib.o /builder/3rdParty/boost/v${BOOST_VER}.0/lib32/gcc-3.4.6/libboost_thread-mt-d.a /usr/lib/libpthread.so -lstdc++ -lc -lm -Wl,--end-group g++ -x c++ -m32 ${CCFLAGS} -fPIC -pipe -o "main.o" -c "main.cpp" g++ -m32 -o boost_thread_test.exe -Wl,--start-group main.o /usr/lib/libpthread.so /usr/lib/libdl.so -lstdc++ -lc -lm -Wl,--end-group Linux version: -------------- Red Hat Enterprise Linux ES release 4 (Nahant Update 4) Invocation: ----------- > ./boost_thread_test.exe ./boost_thread_test.so 600 ... attempt 509 attempt 510 attempt 511 boost_thread_test.exe: libs/thread/src/pthread/thread.cpp:102: void boost::detail::<unnamed>::create_current_thread_tls_key(): Assertion `!pthread_key_create(&current_thread_tls_key,&tls_destructor)' failed. Aborted

2 1

linker error with Boost serialization on 64 bit box. Works fine on 32 bit box.
by Mangal 28 Oct '09

28 Oct '09

Hi I am using STLPort 5.2.1 and Boost1_40_0 with MSVC 9.0. I have successfully compiled boost libs with STLPort and am using the Graph, filesystem and DateTime libraries. I use dynamic linking of STLPort libs. All the projects build and run fine. Today I started looking at the serialization library and just compiling the basic demo threw a 100 linker errors. All the paths for boost libs and STLPort binaries are correct. This is on a 64 bit system. When i ran the same code for serialization on a 32 bit box it compiled and ran fine. Is there some setting I am missing for 64 bit systems? Thanks -- View this message in context: http://www.nabble.com/linker-error-with-Boost-serialization-on-64-bit-box.-… Sent from the Boost - Users mailing list archive at Nabble.com.

2 1

[Interprocess] interprocess_upgradable_mutex and recursivity
by Gaetan Gaumer 27 Oct '09

27 Oct '09

Hello, is there a specific raison why the interprocess_upgradable_mutex is non-recursive ? I need the "Sharable lock" functionality of these mutexes but non-recursivity is a big problem for my usage. Is there a solution to have both "sharability" and "recursivity" in an shared memory storable mutex ? Thanks for your help, Gaëtan

1 0

boost & eclipse IDE
by pedro chaparro 27 Oct '09

27 Oct '09

hi, i'd like to know if there is some tutorial or manual about how to use boost libraries with eclipse IDE. thanks -- Ing Pedro Alonso Chaparro Valero Ciudad Politecnica de la Innovación iTEAM - Mobile Communications Group Polytechnic University of Valencia C\ Camino de Vera S/N, Edificio 8G 46022 Valencia, Spain

2 1

[conversion] Release v0.4: Replace function template specialization by ADL
by vicente.botet 27 Oct '09

27 Oct '09

Hi, I have just released the version 0.4 of Boost.Conversion , which includes since my last publicly announced version 0.3: Replace function template specialization by ADL A Source class is convertible to a Target class if: * Either: A function with the signature convert_to<Target>(Source const&, boost::dummy::type_tag<To> const&) is available via argument dependent lookup * Or: A template specialization of boost::conversion::convert_to<Target, Source> exists for Target and Source * Or: Target is copy constructible from Source (default implementation) The template function convert_to allows to convert a source type to a target type, using argument dependent lookup to select a specialized convert_to function if available. If no specialized convert_to function is available, boost::conversion::convert_to is used. The generic convert_to function requires that the elements to be converted are assignable and copy constructible. It is implemented using the Target copy construction from a Source or the Source conversion operator Target - this is sometimes unavailable. For standard types, we can not add a specialized convert_to function on the namespace std. The alternative to using argument dependent lookup in this situation is to provide a template specialization of boost::conversion::convert_to for every pair of standard types that requires a specialized convert_to. You can found all the detail for dowloading, documentation, ... in http://svn.boost.org/trac/boost/wiki/LibrariesUnderConstruction#Boost.Conve… I'd appreciate it if people could take a look, test it on their compiler and give me some feedback. Thanks to Edward Diener for showing me that multiple assignments should be taken in account. Thanks also to Jeffrey Hellrung and Robert Stewart for showing me that Boost.Conversion should use also ADL. BTW, I'm looking for a review manager. Anyone around here who would like to volunteer? Best regards, _____________________ Vicente Juan Botet Escribá

1 0

Boost.Tree at sandbox - status
by Josue Andrade Gomes 27 Oct '09

27 Oct '09

Hi all, What is the status of Boost.Tree at sandbox (SOC/2006/tree) ? Is there someone working on or using it ? regards, -- Josue Andrade Gomes http://www.josuegomes.com/

1 0

Re: [Boost-users] Use of ccache with Boost
by Dalton, Tom 27 Oct '09

27 Oct '09

Further to my questions from last week: I've tried both methods - first I tried changing the toolset to make the gcc toolset use "ccache g++" as the compiler executable. I had some problems with that, so I tried the symlink approach suggested by Roland. This is also failing, with some seemingly very subtle bug that I can't suss out. The build progresses a little way, until it gets to libs/program_options/src/cmdline.cpp When g++ isn't a symlink to ccache, I get the following output as shown by the attachment build.log.1.fragment. When I have gcc & g++ symlinks in the ccache bin dir pointing to ccache (the PATH is ccache/bin:real_gcc/bin), the output is like the second attachment and the file fails. The build logs diverge from that point onwards as more and more stuff either fails, or is skipped due to previous failures. There are 2 issues that I can see from those logs. Firstly the line numbering on the .hpp includes is one-out on the ccache-enabled build. Does this mean the preprocessor is behaving strangely? Secondly, on line 15 of the failing fragment file, it looks like part of the output is cut off (at the end of the line, it gets "boost::_bi::list2<boost::_bi::v0.000008 sec system; 0.000164 sec user". Can anyone help me? I don't know what would cause either of these issues. Tom PS Using gcc 4.4.1, ccache 2.4 and tried boost 1.39.0 and 1.40.0, with the same results. -----Original Message----- From: boost-users-bounces(a)lists.boost.org [mailto:boost-users-bounces@lists.boost.org] On Behalf Of Dalton, Tom Sent: 29 September 2009 16:20 To: boost-users(a)lists.boost.org Subject: Re: [Boost-users] Use of ccache with Boost Daniel and Roland, Thanks guys, that gives me some good avenues to explore. Tom -----Original Message----- From: boost-users-bounces(a)lists.boost.org [mailto:boost-users-bounces@lists.boost.org] On Behalf Of Daniel James Sent: 29 September 2009 16:07 To: boost-users(a)lists.boost.org Subject: Re: [Boost-users] Use of ccache with Boost 2009/9/29 Dalton, Tom <tom.dalton(a)eds.com>: > > I'm using Boost on Linux however for various reasons I need to rebuild > parts of it occasionally. For other C/C++-based tools that are built > with autoconf/automake, I've started to use ccache > (http://ccache.samba.org/) to speed up recompilation. This is done > simply by setting the CC / CXX environment variables to "ccache gcc" / > "ccache g++" respectively. I have had a look through the Jam > documentation but I can't see an easy way to achieve the same thing > when building the Boost distribution. The closest I came was a bit on > the trac that simply said I can add a new toolset, but had no real instructions as to how. Create a file called 'user-config.jam' in your home directory, containing something like: using gcc : : ccache g++ ; Or possibly with the version number: using gcc : 4.4 : ccache g++-4.4 ; For more information see: http://www.boost.org/doc/libs/1_40_0/doc/html/bbv2/advanced.html#bbv2.ad vanced.configuration Daniel _______________________________________________ Boost-users mailing list Boost-users(a)lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users _______________________________________________ Boost-users mailing list Boost-users(a)lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users

3 8

program_options bad_any_cast in XCode
by Thijs Koerselman 27 Oct '09

27 Oct '09

Hi, Somehow I keep getting exceptions related to the use of strings when I compile my program in Xcode. If I use strings in my program arguments I get an bad_any_cast exception from the store() method. If I compile the same program from the command line directly it works fine, but I can't seem to figure out what the difference is between the two build commands that is causing this behavior. I compiled the program from the command line like this: g++-4.2 -arch i386 -I/opt/local/include -L/opt/local/lib -lboost_program_options-mt -o waveform_manbuild main.cpp Xcode uses the following: CompileC build/waveform.build/Release/waveform.build/Objects-normal/i386/main.o main.cpp normal i386 c++ com.apple.compilers.gcc.4_2 cd /Users/foo/waveform setenv LANG en_US.US-ASCII /Developer/usr/bin/gcc-4.2 -x c++ -arch i386 -fmessage-length=0 -pipe -Wno-trigraphs -fpascal-strings -fasm-blocks -Os -mdynamic-no-pic -Wreturn-type -Wunused-variable -isysroot /Developer/SDKs/MacOSX10.5.sdk -fvisibility=hidden -fvisibility-inlines-hidden -mmacosx-version-min=10.5 -gdwarf-2 -iquote /Users/foo/waveform/build/waveform.build/Release/waveform.build/waveform-generated-files.hmap -I/Users/foo/waveform/build/waveform.build/Release/waveform.build/waveform-own-target-headers.hmap -I/Users/foo/waveform/build/waveform.build/Release/waveform.build/waveform-all-target-headers.hmap -iquote /Users/foo/waveform/build/waveform.build/Release/waveform.build/waveform-project-headers.hmap -F/Users/foo/waveform/build/Release -I/Users/foo/waveform/build/Release/include -I/opt/local/include -I/Users/foo/waveform/build/waveform.build/Release/waveform.build/DerivedSources/i386 -I/Users/foo/waveform/build/waveform.build/Release/waveform.build/DerivedSources -c /Users/foo/waveform/main.cpp -o /Users/foo/waveform/build/waveform.build/Release/waveform.build/Objects-normal/i386/main.o The (very simple) test program is listed below. I hope someone can spot the problem. It's driving me nuts. Cheers, Thijs PS: I'm using OS10.6.1 and Xcode 3.2.1 #include <iostream> #include <boost/shared_ptr.hpp> #include <boost/program_options.hpp> using namespace std; namespace po = boost::program_options; int main (int ac, char * av[]) { po::options_description desc("Allowed options"); desc.add_options() ("help", "produce help message") ("input-file,i", po::value< vector<string> >(), "input file") ; po::variables_map vm; po::store(po::parse_command_line(ac, av, desc), vm); /// << exception thrown here po::notify(vm); if (vm.count("help")) { cout << desc << "\n"; return 1; } if (vm.count("input-file")) { vector<string> input_files = vm["input-file"].as< vector<string> >(); vector<string>::const_iterator it = input_files.begin(); for(; it!=input_files.end(); ++it) cout<< *it << endl; } else { cout << "No input file(s).\n"; } return 0; }

3 4

[rfc] a library for gesture recognition, speech recognition, and synthesis
by Stjepan Rajko 27 Oct '09

27 Oct '09

Hello, For the past few years I've been working on the AME Patterns library - a generic library for modeling, recognition and synthesis of sequential patterns. So far it's been applied mostly to gesture recognition (e.g., recognition of mouse gestures, full body gestures from video or motion capture data, accelerometer gestures), but recently it has also shown some good results on speech datasets. It can also be used to synthesize the same kinds of patterns it can recognize (e.g., you could use it to synthesize a gesture or speech, or purely numerical patterns). The library provides support for hidden Markov models and other related models. The design is concept-based, and the library uses the Boost Graph Library, Boost.Range (including the RangeEx extension), Boost.Fusion, Boost.Math, Boost.Random, and other boost libraries. The documentation for the library is available here: http://ame4.hc.asu.edu/amelia/patterns/ However, the documentation is lacking, so I'm curious to know which parts of the functionality (if any) are of interest to the boost community, so I know what parts of the documentation to focus on. I am also considering proposing a presentation of this library to BoostCon. The library is currently released under the GPL, which I realize is not acceptable to some. Please let me know your thoughts. If anyone is interested in using this library, please let me know what you'd like to use it for and I'd be happy to help you get started. Kind regards, Stjepan

2 5

Information about create_only and open_or_create
by manish4gupta 26 Oct '09

26 Oct '09

Hi, I am working on shared memory. I am successful in using it but I am trying to optimize my code. I just want to know the differences between create_only and open_or_create. As far as i know, create_only creates the shared memory with given size, while open_or_create can open and create both. But If I use open_or_create instead of create-only, i am getting interprocess exception. Why? Please help. Thanks in advance. -- View this message in context: http://www.nabble.com/Information-about-create_only-and-open_or_create-tp25… Sent from the Boost - Users mailing list archive at Nabble.com.

3 7

'class' : missing tag name - compilation errors in two boost headers (shared_ptr and is_function_ptr_tester.hpp) in my project
by BKnoth 26 Oct '09

26 Oct '09

I'm stuck on basic compilation issues in boost files that get included in my source code. The errors turn up in boost headers. Any help is appreciated! Thanks. I'm using Boost 1.40.0 MSVC Version 2008 - V 9.0.30729.1 SP In both shared_ptr.hpp and is_function_ptr_tester.hpp I get the same compilation error: MSVC error: error C2332: 'class' : missing tag name Here are the specific lines from the two files (I inserted a "Error Here!!! comment on the offending lines): ---------------- in shared_ptr.hpp (line 146): #if !defined( BOOST_NO_SFINAE ) && !defined( BOOST_NO_TEMPLATE_PARTIAL_SPECIALIZATION ) && !defined( BOOST_NO_AUTO_PTR ) // rvalue auto_ptr support based on a technique by Dave Abrahams template< class T, class R > struct sp_enable_if_auto_ptr // Error Here!!! { }; ---------------- in is_function_ptr_tester.hpp (line 37): #if !defined(BOOST_TT_PREPROCESSING_MODE) // pre-processed code, don't edit, try GNU cpp with // cpp -I../../../ -DBOOST_TT_PREPROCESSING_MODE -x c++ -P filename template <class R > // Error Here!!! yes_type is_function_ptr_tester(R (*)()); ------------------- The second error traces back to boost_1_40_0/boost/exception/all.hpp as shown in the extensive include hierarchy list below: > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/exception/all.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/exception/diagnostic_information.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/config.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/exception/get_error_info.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/exception/exception.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/exception/detail/error_info_impl.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/exception/detail/type_info.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/shared_ptr.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/exception/detail/exception_ptr_base.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/utility/enable_if.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/config.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/exception/current_exception_cast.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/exception/error_info.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/exception/exception.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/exception/get_error_info.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/exception/info.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/exception/exception.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/exception/to_string_stub.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/exception/to_string.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/utility/enable_if.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/exception/detail/is_output_streamable.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/exception/detail/object_hex_dump.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/exception/detail/type_info.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/assert.hpp > Note: including file: C:\Program Files\Microsoft Visual Studio 9.0\VC\include\assert.h > Note: including file: C:\Program Files\Microsoft Visual Studio 9.0\VC\include\crtdefs.h > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/exception/detail/error_info_impl.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/shared_ptr.hpp > Note: including file: C:\Program Files\Microsoft Visual Studio 9.0\VC\include\map > Note: including file: C:\Program Files\Microsoft Visual Studio 9.0\VC\include\xtree > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/exception/info_tuple.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/exception/info.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/tuple/tuple.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/config.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/static_assert.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/config.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/detail/workaround.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/ref.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/config.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/utility/addressof.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/config.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/detail/workaround.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/mpl/bool.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/mpl/bool_fwd.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/mpl/aux_/adl_barrier.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/mpl/aux_/config/adl.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/mpl/aux_/config/msvc.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/config.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/mpl/aux_/config/intel.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/config.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/mpl/aux_/config/gcc.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/mpl/aux_/config/workaround.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/detail/workaround.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/mpl/aux_/config/gcc.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/mpl/aux_/config/workaround.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/mpl/integral_c_tag.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/mpl/aux_/adl_barrier.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/mpl/aux_/config/static_constant.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/config.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/mpl/aux_/config/static_constant.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/detail/workaround.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/tuple/detail/tuple_basic.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/type_traits/cv_traits.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/type_traits/add_const.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/config.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/type_traits/detail/type_trait_def.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/type_traits/detail/template_arity_spec.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/mpl/int.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/mpl/int_fwd.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/mpl/aux_/adl_barrier.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/mpl/aux_/nttp_decl.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/mpl/aux_/config/nttp.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/mpl/aux_/config/msvc.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/mpl/aux_/config/workaround.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/mpl/aux_/integral_wrapper.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/mpl/integral_c_tag.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/mpl/aux_/static_cast.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/mpl/aux_/config/workaround.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/mpl/aux_/nttp_decl.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/mpl/aux_/config/static_constant.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/mpl/aux_/config/workaround.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/preprocessor/cat.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/preprocessor/config/config.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/mpl/aux_/template_arity_fwd.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/mpl/aux_/preprocessor/params.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/mpl/aux_/config/preprocessor.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/mpl/aux_/config/workaround.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/preprocessor/comma_if.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/preprocessor/punctuation/comma_if.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/preprocessor/config/config.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/preprocessor/control/if.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/preprocessor/config/config.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/preprocessor/control/iif.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/preprocessor/config/config.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/preprocessor/logical/bool.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/preprocessor/config/config.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/preprocessor/facilities/empty.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/preprocessor/punctuation/comma.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/preprocessor/repeat.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/preprocessor/repetition/repeat.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/preprocessor/cat.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/preprocessor/config/config.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/preprocessor/debug/error.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/preprocessor/cat.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/preprocessor/config/config.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/preprocessor/detail/auto_rec.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/preprocessor/config/config.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/preprocessor/control/iif.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/preprocessor/tuple/eat.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/preprocessor/config/config.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/preprocessor/inc.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/preprocessor/arithmetic/inc.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/preprocessor/config/config.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/preprocessor/cat.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/mpl/aux_/config/lambda.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/mpl/aux_/config/ttp.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/mpl/aux_/config/msvc.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/mpl/aux_/config/gcc.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/mpl/aux_/config/workaround.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/mpl/aux_/config/ctps.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/mpl/aux_/config/workaround.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/config.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/mpl/aux_/config/overload_resolution.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/mpl/aux_/config/workaround.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/mpl/aux_/lambda_support.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/mpl/aux_/config/lambda.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/type_traits/detail/type_trait_undef.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/type_traits/add_volatile.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/config.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/type_traits/detail/type_trait_def.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/type_traits/detail/template_arity_spec.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/mpl/int.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/mpl/aux_/template_arity_fwd.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/mpl/aux_/preprocessor/params.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/mpl/aux_/config/lambda.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/mpl/aux_/config/overload_resolution.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/mpl/aux_/lambda_support.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/type_traits/detail/type_trait_undef.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/type_traits/add_cv.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/config.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/type_traits/detail/type_trait_def.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/type_traits/detail/template_arity_spec.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/mpl/int.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/mpl/aux_/template_arity_fwd.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/mpl/aux_/preprocessor/params.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/mpl/aux_/config/lambda.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/mpl/aux_/config/overload_resolution.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/mpl/aux_/lambda_support.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/type_traits/detail/type_trait_undef.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/type_traits/is_const.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/config.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/detail/workaround.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/type_traits/detail/cv_traits_impl.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/config.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/detail/workaround.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/type_traits/detail/bool_trait_def.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/type_traits/detail/template_arity_spec.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/mpl/int.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/mpl/aux_/template_arity_fwd.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/mpl/aux_/preprocessor/params.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/mpl/aux_/config/lambda.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/mpl/aux_/config/overload_resolution.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/type_traits/integral_constant.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/config.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/mpl/bool.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/mpl/integral_c.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/mpl/integral_c_fwd.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/mpl/aux_/config/workaround.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/mpl/aux_/adl_barrier.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/mpl/aux_/config/ctps.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/mpl/aux_/config/static_constant.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/mpl/aux_/config/workaround.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/mpl/aux_/integral_wrapper.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/mpl/integral_c_tag.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/mpl/aux_/static_cast.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/mpl/aux_/nttp_decl.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/mpl/aux_/config/static_constant.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/mpl/aux_/config/workaround.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/preprocessor/cat.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/mpl/bool.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/mpl/aux_/lambda_support.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/config.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/type_traits/detail/bool_trait_undef.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/type_traits/is_volatile.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/config.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/detail/workaround.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/type_traits/detail/cv_traits_impl.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/type_traits/detail/bool_trait_def.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/type_traits/detail/template_arity_spec.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/mpl/int.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/mpl/aux_/template_arity_fwd.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/mpl/aux_/preprocessor/params.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/mpl/aux_/config/lambda.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/mpl/aux_/config/overload_resolution.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/type_traits/integral_constant.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/mpl/bool.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/mpl/aux_/lambda_support.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/config.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/type_traits/detail/bool_trait_undef.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/type_traits/remove_const.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/type_traits/is_volatile.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/type_traits/broken_compiler_spec.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/mpl/aux_/lambda_support.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/config.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/type_traits/detail/cv_traits_impl.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/config.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/detail/workaround.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/type_traits/detail/type_trait_def.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/type_traits/detail/template_arity_spec.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/mpl/int.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/mpl/aux_/template_arity_fwd.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/mpl/aux_/preprocessor/params.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/mpl/aux_/config/lambda.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/mpl/aux_/config/overload_resolution.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/mpl/aux_/lambda_support.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/type_traits/detail/type_trait_undef.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/type_traits/remove_volatile.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/type_traits/is_const.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/type_traits/broken_compiler_spec.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/type_traits/detail/cv_traits_impl.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/config.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/detail/workaround.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/type_traits/detail/type_trait_def.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/type_traits/detail/template_arity_spec.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/mpl/int.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/mpl/aux_/template_arity_fwd.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/mpl/aux_/preprocessor/params.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/mpl/aux_/config/lambda.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/mpl/aux_/config/overload_resolution.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/mpl/aux_/lambda_support.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/type_traits/detail/type_trait_undef.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/type_traits/remove_cv.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/type_traits/broken_compiler_spec.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/type_traits/detail/cv_traits_impl.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/config.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/detail/workaround.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/type_traits/detail/type_trait_def.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/type_traits/detail/template_arity_spec.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/mpl/int.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/mpl/aux_/template_arity_fwd.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/mpl/aux_/preprocessor/params.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/mpl/aux_/config/lambda.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/mpl/aux_/config/overload_resolution.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/mpl/aux_/lambda_support.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/type_traits/detail/type_trait_undef.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/type_traits/function_traits.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/config.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/type_traits/is_function.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/type_traits/is_reference.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/type_traits/config.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/detail/workaround.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/type_traits/detail/bool_trait_def.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/type_traits/detail/template_arity_spec.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/mpl/int.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/mpl/aux_/template_arity_fwd.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/mpl/aux_/preprocessor/params.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/mpl/aux_/config/lambda.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/mpl/aux_/config/overload_resolution.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/type_traits/integral_constant.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/mpl/bool.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/mpl/aux_/lambda_support.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/config.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/type_traits/detail/bool_trait_undef.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/type_traits/detail/false_result.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/config.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/config.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/type_traits/detail/is_function_ptr_tester.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/type_traits/detail/yes_no_type.hpp > Note: including file: C:\Program Files\boost\boost_1_40_0\boost/type_traits/config.hpp > c:\program files\boost\boost_1_40_0\boost\type_traits\detail\is_function_ptr_tester.hpp(37) : error C2332: 'class' : missing tag name

3 6

circular_buffer::erase in constant time
by Luca Cappa 26 Oct '09

26 Oct '09

Hello, is it possible to remove the first bunch of elements of a circular_buffer with constant complexity time? Unfortunately using any (r)erase function the complexity is linear. To give an idea, it could be implemented like this: /// Erase the first pCount element from the buffer void begin_erase (size_t pCount) { BOOST_ASSERT(pCount <= size ()); circular_buffer<Type>::add (m_first, pCount); m_size -= pCount;; } but this is not taking into account deletion of the deleted items (could they be deleted when they are overwritten? Or the stored type does not need to be destroyed at all), and many other details which are known to me. I am asking this 'cause I would like to make my circular_buffer class to be STL compliant container, but before doing it myself, I would like to evaluate if I could derive (or use aggregation) directly from circular_buffer and save me a lot of work. Thanks, Luca

2 3

[Asio] Problem with streambuf example code
by Dylan Klomparens 26 Oct '09

26 Oct '09

Hello, I've attempted to compile a portion of the example source code for the Asio streambuf class. The code attempts to convert a streambuf to a const_buffers_type, to be used in receiving data from a UDP socket. The example can be found at " http://www.boost.org/doc/libs/1_40_0/doc/html/boost_asio/reference/streambu…". The code in question is as follows: boost::asio::streambuf b; // reserve 512 bytes in output sequence boost::asio::streambuf::const_buffers_type bufs = b.prepare(512); For simplicity, I tried compiling only these two lines but I receive this compilation error: error C2440: 'initializing' : cannot convert from 'boost::asio::basic_streambuf<>::mutable_buffers_type' to 'boost::asio::const_buffers_1' Am I missing something obvious? It's my understanding that mutable buffers can always be converted to constant buffers. Why is the second line problematic? -- Dylan

2 1

[Boost.Python] Using Weak Ptrs with Boost Python?
by Dan Bailey 26 Oct '09

26 Oct '09

Trying to set up a dependency in C++ with a parent-child relationship. The parent contains the child and the child has a weak pointer to the parent. I would also like to be able to derive from the parent in Python. However, when I do this, I get a weak pointer error connecting up this parent-child relationship. C++ code: #include <boost/python.hpp> #include <boost/shared_ptr.hpp> #include <boost/enable_shared_from_this.hpp> using namespace boost; using namespace boost::python; struct Child; struct Parent : public enable_shared_from_this<Parent> { void initialize(); shared_ptr<Child> m_child; }; struct Child: public enable_shared_from_this<Child> { void setParent(shared_ptr<Parent> ptr); weak_ptr<Parent> m_parent; }; void Parent::initialize() { shared_ptr<Child> ptr(new Child); m_child = ptr; m_child->setParent(shared_from_this()); } void Child::setParent(shared_ptr<Parent> ptr) { m_parent = ptr; } static PyObject* create(PyObject* object) { PyObject* instance = PyObject_CallObject(object, NULL); Parent* parent = extract<Parent*>(instance); parent->initialize(); return instance; } Python binding: BOOST_PYTHON_MODULE(test_module) { class_<Parent>("Parent"); def("create", &create); } Python code: from test_module import * class Test(Parent): def __init__(self): Parent.__init__(self) n = create(Test) Error: Traceback (most recent call last): File "main.py", line 8, in <module> n = create(Test) RuntimeError: tr1::bad_weak_ptr If I try and convert the extracted pointer to Parent into a shared_ptr, I get a free() invalid pointer error in Python. Is there a way of getting round this problem or should I give up using weak pointers with Boost Python?

2 1

[result_of]
by er 26 Oct '09

26 Oct '09

Hi All, I've noticed that if do, class A: F{ template<typename S> struct result{}; template<typename A1,typename X> struct result<A1(X)>{ typedef ... type; }; }; result_of<A(X)>::type tries to deduce the result type from F (not accessible because private), so I'm left with having to keep F in a variable: class A{ // ... private: F f; }; Any suggestion for keeping F as a private base?

2 3

Re: [Boost-users] [Proto] Bug in 1.40 : uncomplete type in matches
by christophe henry 26 Oct '09

26 Oct '09

Hi Joel, I think I got bitten by this one and Eric corrected it in the trunk. Try to add in traits.hpp after BOOST_PROTO_DEFINE_UNARY_METAFUNCTION(complement) the following line: BOOST_PROTO_DEFINE_UNARY_METAFUNCTION(address_of) Christophe _________________________________________________________________ Windows Live: Make it easier for your friends to see what you’re up to on Facebook. http://www.microsoft.com/middleeast/windows/windowslive/see-it-in-action/so…

3 2

seg fault
by John Robertson 26 Oct '09

26 Oct '09

I tried typedef string Colour; struct edge_properties { vector < set< Colour > & > eColours; } But it did not compile. Shouldn't it ? Thanks -JR

3 3

[fusion] vector slicing (sort of)
by Jean-Louis Leroy 26 Oct '09

26 Oct '09

I am a bit surprised that this compiles: vector<char, int> v2; vector<char> v1(v2); v1 = v2; J-L

3 3

[Boost.Test]: output_test_stream and wchar_t (i.e. woutput_test_stream)?
by Boris Dušek 25 Oct '09

25 Oct '09

Hi, I am using Boost.Test and wanted to use the output_test_stream, however found out that it's stream of chars and my app uses strictly wchar_t. I also found that the output_test_stream inherits from basic_wrap_stringstream<char>::wrapped_stream - is there any plan to templatize output_test_stream itself? For now I have resorted to simply using std::wstringstream as a workaround. Thanks, Boris

2 1

function calling convensions
by Sean Farrow 25 Oct '09

25 Oct '09

Hi: I need to use the stdcall calling convension for a dll that I'm writing. When ever I do this with boost, I get the following errors: ... Creating library d:\Work\Access For Everyone\GHG\TPProductsZW\Debug\TPProductsZW.lib and object d:\Work\Access For Everyone\GHG\TPProductsZW\Debug\TPProductsZW.exp TPProductsZW.obj : error LNK2019: unresolved external symbol "class boost::system::error_category const & __stdcall boost::system::get_system_category(void)" (?get_system_category@system@boost@@YGABVerror_category@12@XZ) referenced in function "void __cdecl boost::system::`dynamic initializer for 'system_category''(void)" (??__Esystem_category@system@boost@@YAXXZ) TPProductsZW.obj : error LNK2019: unresolved external symbol "class boost::system::error_category const & __stdcall boost::system::get_generic_category(void)" (?get_generic_category@system@boost@@YGABVerror_category@12@XZ) referenced in function "void __cdecl boost::system::`dynamic initializer for 'generic_category''(void)" (??__Egeneric_category@system@boost@@YAXXZ) d:\Work\Access For Everyone\GHG\TPProductsZW\Debug\TPProductsZW.dll : fatal error LNK1120: 2 unresolved externals Does anyone know how to solve this issue? I'm building statically, and using visual studio c++ 2008, I'm also using __declspec(dllexport) Regards Sean. Results

2 1

[Proto] Bug in 1.40 : uncomplete type in matches
by joel 25 Oct '09

25 Oct '09

I just switched from 39 to 40 and my proto code that was working doesn't anymore. I define a grammar that matches any terminal, any nary functions except for address_of and comma like this : struct grammar : bp::or_< bp::terminal< block<bp::_,bp::_> > , meta::lambda_term< boost::is_arithmetic > , bp::and_< bp::nary_expr< bp::_, bp::vararg< grammar > > , bp::not_< meta::low_level<bp::_> > , bp::not_< meta::stream<bp::_,bp::_> > > > {}; where lambda_term is : template< template<class> class Lambda > struct lambda_term : boost::proto::and_< boost::proto::terminal<boost::proto::_> , boost::proto::if_<Lambda<boost::proto::_value>()> > {}; When i compile any code that instanciate my grammar, i got : /usr/local/include/boost-1_40/boost/proto/matches.hpp:304: error: invalid use of incomplete type ‘struct boost::proto::op::address_of<boost::proto::wildcardns_::_>’ While I got no error in 1.39 Do I miss some include of core proto file that wasn't needed before ? -- ___________________________________________ Joel Falcou - Assistant Professor PARALL Team - LRI - Universite Paris Sud XI Tel : (+33)1 69 15 66 35

1 1

[exception] array tags
by Diederick C. Niehorster 25 Oct '09

25 Oct '09

Hi, I have just discovered boost::exception and am very happy I did. One thing i would like to do, but haven't yet figure out: I have a matrix class for which I want to throw exceptions when out_of_range requests are made. One of the extra tags I want to attach is the dimensions of the matrix and it would be neat if i can put those in an array. Defining the tag is no problem, getting the info in there is: defining: typedef boost::error_info<struct tag_std_range_size,size_t[2]> std_range_size; I have tried: << std_range_size({m_nRows, m_nCols}); size_t a[2] = {m_nRows, m_nCols}; << std_range_size(a); and desperately even << std_range_size() = {m_nRows, m_nCols}; which doesn't make much sense Can I do such a thing, should I use something else than a plain array or do i have to resort to two separate tags for nRows adn nCols respectively? Thank you for your help and advice! Best, Diederick

3 11

GIL documentation
by Valmor de Almeida 24 Oct '09

24 Oct '09

Hello, Is there a printable version of the flash video tutorial at http://opensource.adobe.com/gil/presentation/index.htm for the Generic Image Library? Thanks, -- Valmor

1 0

Re: [Boost-users] Boost-users Digest, Vol 2158, Issue 1
by Ben 24 Oct '09

24 Oct '09

> Ahhh - so try > > ar >> static_cast<A* &>(a2p); > > Robert Ramey > > troy d. straszheim wrote: >> Ben wrote: >>> { >>> std::ifstream ifs(fname); >>> boost::archive::binary_iarchive ar(ifs); >>> ar >> static_cast<A*>(a2p); >>> } >> >> You're trying to write to an rvalue. Note that >> >> int *ip = 0; >> static_cast<int*>(ip) = 0; // lvalue required as >> // left operand of assignment >> >> doesn't compile either... Wow, that was silly of me. Thanks for the quick response. Any clue to the main question I had (repeated below) about serializing classes with references? I don't think it's an rvalue thing, as the problem occurs even in the save_construct_data bit. Generally, I'm trying to copy what the documentation says to do. Best, Ben Date: Fri, 23 Oct 2009 15:27:48 -0700 From: Ben <midfield(a)gmail.com> To: boost-users(a)lists.boost.org Subject: [Boost-users] [serialization] Serializing a reference Message-ID: <9157df230910231527x686ff3b4n16ec1e9eabc9515(a)mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1 Hello Boost Experts -- And now for my real question. Again, g++ 4.2.1, OS X 10.6.1, boost 1.40. I'm trying to follow the instructions in the document for serializing classes with reference members, which suggests I serialize them as pointers. First, a program which works, that uses pointers and not references: #include <iostream> #include <fstream> #include <boost/archive/binary_oarchive.hpp> #include <boost/archive/binary_iarchive.hpp> struct A { int v; template<class Ar> void serialize(Ar & ar, const unsigned int ver) { ar & v; } }; struct B { A *ap; B(A *ap_) : ap(ap_) {} template<class Ar> void serialize(Ar & ar, const unsigned int ver) {} }; template<class Ar> void save_construct_data(Ar & ar, const B * b, const unsigned int ver) { ar << b->ap; } template<class Ar> void load_construct_data(Ar & ar, B * b, const unsigned int ver) { A * ap_; ar >> ap_; ::new(b)B(ap_); } int main(int ac, char ** argv) { A a; a.v = 10; B * b1p; b1p = new B(&a); const char * fname = "test.bin"; { std::ofstream ofs(fname); boost::archive::binary_oarchive ar(ofs); ar << b1p; } B * b2p; { std::ifstream ifs(fname); boost::archive::binary_iarchive ar(ifs); ar >> b2p; } std::cout << b2p->ap->v << std::endl; return 0; } What I would really like to do is to modify this program so that class B has a reference to class A instead of a pointer. The documentation suggests I do the following: "This raises the question of how and where the objects being referred to are stored and how are they created. Also there is the question about references to polymorphic base classes. Basically, these are the same questions that arise regarding pointers. This is no surprise as references are really a special kind of pointer. We address these questions by serializing references as though they were pointers." The example given after this serializes the address of the referenced object, similar to the above. My translation of that code is: #include <iostream> #include <fstream> #include <boost/archive/binary_oarchive.hpp> #include <boost/archive/binary_iarchive.hpp> struct A { int v; template<class Ar> void serialize(Ar & ar, const unsigned int ver) { ar & v; } }; struct B { A &a; B(A &a_) : a(a_) {} template<class Ar> void serialize(Ar & ar, const unsigned int ver) {} }; template<class Ar> void save_construct_data(Ar & ar, const B * b, const unsigned int ver) { ar << (&(b->a)); } template<class Ar> void load_construct_data(Ar & ar, B * b, const unsigned int ver) { A * ap_; ar >> ap_; ::new(b)B(*ap_); } int main(int ac, char ** argv) { A a; a.v = 10; B * b1p; b1p = new B(a); const char * fname = "test.bin"; { std::ofstream ofs(fname); boost::archive::binary_oarchive ar(ofs); ar << b1p; } B * b2p; { std::ifstream ifs(fname); boost::archive::binary_iarchive ar(ifs); ar >> b2p; } std::cout << b2p->a.v << std::endl; return 0; } This however fails to compile, with the message: Compilation started at Fri Oct 23 15:25:29 make -k debug make all "CXX_FLAGS = -g -fno-inline -m64 -I. -I.. -I/opt/local/include -Wall -Wextra -Wpointer-arith -Wcast-align -Wwrite-strings -Wconversion -Woverloaded-virtual -Wno-sign-compare -Wno-unused -fno-nonansi-builtins" \ "LD_FLAGS = -g -m64" g++ -g -fno-inline -m64 -I. -I.. -I/opt/local/include -Wall -Wextra -Wpointer-arith -Wcast-align -Wwrite-strings -Wconversion -Woverloaded-virtual -Wno-sign-compare -Wno-unused -fno-nonansi-builtins -c test.cc -o test.o test.cc: In function 'void save_construct_data(Ar&, const B*, unsigned int) [with Ar = boost::archive::binary_oarchive]': /opt/local/include/boost/serialization/serialization.hpp:148: instantiated from 'void boost::serialization::save_construct_data_adl(Archive&, const T*, unsigned int) [with Archive = boost::archive::binary_oarchive, T = B]' /opt/local/include/boost/archive/detail/oserializer.hpp:179: instantiated from 'void boost::archive::detail::pointer_oserializer<Archive, T>::save_object_ptr(boost::archive::detail::basic_oarchive&, const void*) const [with Archive = boost::archive::binary_oarchive, T = B]' test.cc:60: instantiated from here test.cc:27: error: no match for 'operator<<' in 'ar << (A*)b->B::a' /opt/local/include/boost/archive/detail/interface_oarchive.hpp:63: note: candidates are: Archive& boost::archive::detail::interface_oarchive<Archive>::operator<<(T&) [with T = A*, Archive = boost::archive::binary_oarchive] make[1]: *** [test.o] Error 1 make[1]: Target `all' not remade because of errors. make: *** [debug] Error 2 Compilation exited abnormally with code 2 at Fri Oct 23 15:25:30 What am I doing wrong? Best regards, Ben

1 0

compiling boost with mpi support
by Sean Farrow 24 Oct '09

24 Oct '09

Hi: I'm looking to compile boost with mpi support. I am using visual c++ 2008, what mpi libraries are supported. Where should I place the mpi library I wish to wrap, any pointers appreciated. Sean.

2 2