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

Compilation errors in Boost.Mpl with Microsoft Compiler ver.13.10.2240.8 for IA-64
by Sergey Serokurov 30 Jul '05

30 Jul '05

HI All, I am getting compilation errors using Microsoft (R) C/C++ Optimizing Compiler Version 13.10.2240.8 for IA-64 The compiler is shipped with Windows DDK (WINDDK\3790\bin\ia64). The same code compiles perfectly well with 32 bit Microsoft compiler (13.10.2179.0) The Boost version is 1.32.0 Is it a known issue with the compiler? Is there a workaround? Content of the StdAfx.h file which is being compiled as a the pre-compiled header is: #include <boost/multi_index_container.hpp> #include <boost/multi_index/member.hpp> #include <boost/multi_index/ordered_index.hpp> #include <boost/multi_index/mem_fun.hpp> #include <boost/multi_index/composite_key.hpp> #include <boost/shared_ptr.hpp> #include <boost/intrusive_ptr.hpp> #include <boost/functional.hpp> #include <boost/variant.hpp> #include <boost/ref.hpp> The following is the compiler output: P'nmake.exe /c BUILDMSG=Stop. -i NTTEST= UMTEST= NOLINK=1 NOPASS0=1 IA64=1' cl -nologo -Iia64\ -I. -IC:\WINDDK\3790\inc\mfc42 -IC:\WINDDK\3790\inc\atl30 -I\include -IC:\WINDDK\3790\inc\ddk\wnet IC:\WINDDK\3790\inc\crt C:\WINDDK\3790 \inc\wnet\crt\stl60 -D_WIN64 -D_IA64_=1 -DIA64=1 -DNO_HW_DETECT -D_MSC_EXTENSIONS -DCONDITION_HANDLING=1 -DNT_INST=0 -DWIN32=100 -D_NT1X_=100 -DWINNT=1 -D_WIN32_WINNT=0x0502 /DWINVER=0x0502 -D_WIN32_IE=0x0600 -D_MERCED_A0_=1 -DDEVL=1 -D__BUILDMACHINE__=WinDDK -DFPO=0 -DNDEBUG -D_DLL=1 -D_MT=1 -DUNICODE -D_UNICODE -DNOATLNAMESPACE /D_ATL_DLL /c /Zel /Zp8 /Gy /Gi- /W3 /Wp64 /GX /GR /Zi /Od /d2QIA64_fr32 /FdC:\main\SWSvc\objfre_wnet_IA64\ia64\ - FIC:\WINDDK\3790\inc\wnet\warning.h /YlSWSvc /Ycstdafx.h /Fpobjfre_wnet_IA64\ia64\stdafx.pch /Fo"C:\objfre_wnet_IA64\ia64\_stdafx.obj" /Tp #include "stdafx.h" pch_hdr.src \boost-1_32\boost\mpl\if.hpp(63) : error C2226: syntax error : unexpected type 'value' \boost-1_32\boost\mpl\if.hpp(73) : see reference to class template instantiation 'boost::mpl::if_<T1,T2,T3>' being compiled \boost-1_32\boost\mpl\if.hpp(63) : error C2144: syntax error : 'value' should be preceded by '(' \boost-1_32\boost\mpl\if.hpp(67) : error C2976: 'boost::mpl::if_c' : too few template arguments \boost-1_32\boost\mpl\if.hpp(37) : see declaration of 'boost::mpl::if_c' \boost-1_32\boost\mpl\aux_\preprocessed\plain\less.hpp(21) : error C2143: syntax error : missing ')' before '>' \boost-1_32\boost\mpl\aux_\preprocessed\plain\less.hpp(28) : see reference to class template instantiation 'boost::mpl::less_impl<Tag1,Tag2>' being compiled \boost-1_32\boost\mpl\aux_\preprocessed\plain\less.hpp(21) : error C2059: syntax error : '>' \boost-1_32\boost\mpl\aux_\preprocessed\plain\less.hpp(26) : error C2947: expecting '>' to terminate template-argument-list, found '>' \boost-1_32\boost\mpl\aux_\preprocessed\plain\less.hpp(26) : error C2976: 'boost::mpl::if_c' : too few template arguments \boost-1_32\boost\mpl\if.hpp(37) : see declaration of 'boost::mpl::if_c' \boost-1_32\boost\mpl\aux_\preprocessed\plain\less.hpp(87) : error C2143: syntax error : missing ')' before '>' \boost-1_32\boost\mpl\aux_\preprocessed\plain\less.hpp(89) : see reference to class template instantiation 'boost::mpl::less_impl<Tag1,Tag2>::apply<N1,N2>' being compiled with [ Tag1=boost::mpl::integral_c_tag, Tag2=boost::mpl::integral_c_tag ] \boost-1_32\boost\mpl\aux_\preprocessed\plain\less.hpp(87) : error C2059: syntax error : '>' \boost-1_32\boost\mpl\aux_\preprocessed\plain\less.hpp(88) : error C2143: syntax error : missing ';' before '{' \boost-1_32\boost\mpl\aux_\preprocessed\plain\less.hpp(89) : error C2143: syntax error : missing ';' before '}' \boost-1_32\boost\mpl\aux_\preprocessed\plain\less.hpp(89) : fatal error C1004: unexpected end of file found Thank you, Sergey Serokurov

3 3

Re: [Boost-users] MultiIndex Hashed indicies
by JOAQUIN LOPEZ MU?Z 29 Jul '05

29 Jul '05

Hi Sohail, Hashed indices will be available in 1.33 (due to be released in a matter of days). boost-consulting.com/boost shows the documentation as in the current CVS, so what you're seeing is really a preview of the release to come. The official docs are at boost.org. Regards, Joaquín M López Muñoz Telefónica, Investigación y Desarrollo Is this a new feature (http://boost-consulting.com/boost/libs/multi_index/doc/reference/index. html)? I don't seem to have it in my 1.3.2 installation. Thanks Sohail _______________________________________________ Boost-users mailing list Boost-users(a)lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users

1 0

MultiIndex Hashed indicies
by Sohail Somani 29 Jul '05

29 Jul '05

Is this a new feature (http://boost-consulting.com/boost/libs/multi_index/doc/reference/index. html)? I don't seem to have it in my 1.3.2 installation. Thanks Sohail

1 0

Re: [Boost-users] How to manually lock and unlock a mutex?
by Sohail Somani 29 Jul '05

29 Jul '05

You're not supposed to know about detail... :D > -----Original Message----- > From: boost-users-bounces(a)lists.boost.org > [mailto:boost-users-bounces@lists.boost.org] On Behalf Of > Christian Henning > Sent: Friday, July 29, 2005 11:29 AM > To: boost-users(a)lists.boost.org > Subject: Re: [Boost-users] How to manually lock and unlock a mutex? > > > Seems to me that I should take a look at the detail folder in > the thread lib. ;-) > > Thanks you all for helpful suggestions, > Christian > > On 7/29/05, Sohail Somani <s.somani(a)fincad.com> wrote: > > scoped_ptr would be more appropriate I think. > > > > > -----Original Message----- > > > From: boost-users-bounces(a)lists.boost.org > > > [mailto:boost-users-bounces@lists.boost.org] On Behalf Of Jason > > > Stewart > > > Sent: Friday, July 29, 2005 10:01 AM > > > To: boost-users(a)lists.boost.org > > > Subject: Re: [Boost-users] How to manually lock and > unlock a mutex? > > > > > > > > > Try > > > > > > void foo() > > > { > > > shared_ptr<scoped_lock> lk; > > > if (condition) > > > lk.reset(new scoped_lock(mutex)); > > > > > > do something > > > } > > > > > > The smart pointer will automatically unlock when it goes out of > > > scope. > > > > > > _______________________________________________ > > > 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 > > > > _______________________________________________ > Boost-users mailing list > Boost-users(a)lists.boost.org > http://lists.boost.org/mailman/listinfo.cgi/boost-users >

1 0

Re: [Boost-users] How to manually lock and unlock a mutex?
by Sohail Somani 29 Jul '05

29 Jul '05

scoped_ptr would be more appropriate I think. > -----Original Message----- > From: boost-users-bounces(a)lists.boost.org > [mailto:boost-users-bounces@lists.boost.org] On Behalf Of > Jason Stewart > Sent: Friday, July 29, 2005 10:01 AM > To: boost-users(a)lists.boost.org > Subject: Re: [Boost-users] How to manually lock and unlock a mutex? > > > Try > > void foo() > { > shared_ptr<scoped_lock> lk; > if (condition) > lk.reset(new scoped_lock(mutex)); > > do something > } > > The smart pointer will automatically unlock when it goes out of scope. > > _______________________________________________ > Boost-users mailing list > Boost-users(a)lists.boost.org > http://lists.boost.org/mailman/listinfo.cgi/boost-users >

2 1

shared_array EXC_BAD_ACCESS
by Christopher Hunt 29 Jul '05

29 Jul '05

Hi there, I'm attempting to use a shared_array as member of a class that I have. Something akin to the following: class UTFStringHolder { ... boost::shared_array<unsigned short> mStrBufferP; }; When UTFStringHolder is instantiated, I get an EXC_BAD_ACCESS and my stack trace shows that pthread_mutex_init is being called. Here's the complete stack trace: #0 0x90012730 in _pthread_mutex_init #1 0x00088424 in boost::detail::lightweight_mutex::lightweight_mutex() at lwm_pthreads.hpp:47 #2 0x00088024 in boost::detail::lightweight_mutex::lightweight_mutex() at lwm_pthreads.hpp:49 #3 0x00087bc4 in boost::detail::sp_counted_base::sp_counted_base() at shared_count.hpp:98 #4 0x00086614 in boost::detail::sp_counted_base::sp_counted_base() at shared_count.hpp:99 #5 0x00098be0 in boost::detail::sp_counted_base_impl<unsigned short*, boost::checked_array_deleter<unsigned short> >::sp_counted_base_impl(unsigned short*, boost::checked_array_deleter<unsigned short>) at shared_count.hpp:253 #6 0x00098b8c in boost::detail::sp_counted_base_impl<unsigned short*, boost::checked_array_deleter<unsigned short> >::sp_counted_base_impl(unsigned short*, boost::checked_array_deleter<unsigned short>) at shared_count.hpp:253 #7 0x00098ac4 in boost::detail::shared_count::shared_count<unsigned short*, boost::checked_array_deleter<unsigned short> >(unsigned short*, boost::checked_array_deleter<unsigned short>) at shared_count.hpp:340 #8 0x00098a48 in boost::detail::shared_count::shared_count<unsigned short*, boost::checked_array_deleter<unsigned short> >(unsigned short*, boost::checked_array_deleter<unsigned short>) at shared_count.hpp:345 #9 0x00098900 in boost::shared_array<unsigned short>::shared_array(unsigned short*) at shared_array.hpp:57 #10 0x0009889c in boost::shared_array<unsigned short>::shared_array(unsigned short*) at shared_array.hpp:57 #11 0x00029f34 in Classee::UTFStringHolder::UTFStringHolder() at UTFString.cpp:20 Any ideas/pointers? I'm using boost v.1.32. Thanks for any help as I'm going bonkers. :-P Cheers, -C

2 1

How to manually lock and unlock a mutex?
by Christian Henning 29 Jul '05

29 Jul '05

Hi there, I'm converting over our codebase to make use of the boost libs. Is there a way to manually lock and unlock a boost:mutex? Or, is there a conditional lock available? I know there is boost::mutex::scoped_lock that does it automatically. Here is code example that, I think, requires manual locking: void foo() { if( condition ) oMutex.lock; do something if( condition ) oMutex.unlock; } It might be that our code isn't designed very well for using boost::mutex. One solution would be: void foo() { if( condition ) { boost::mutex::scoped oLock( oMutex ); do something } else { do something } } Thanks, Christian

4 3

questions concerning optional + date_time + serialize
by Jasper, Alexander 29 Jul '05

29 Jul '05

Hi All! I've got few questions concerning the date_time, optional and serialization libs (1.32) and how they work together. I'm trying to serialize a optional<posix_time::time_duration> using a binary Archive. Unfortunately the extraction code fails to compile. This is because the optional<T> requires T to have a default constructor, when extraction from an archive (see code take from optional.hpp below). I changed the code ( see blow) to work around this. I know that is neither efficient (heap usage) nor exception safe but it works for me. Also it requires operator=. But ptime has got this. Does any body have more advanced suggestions to solve this? Another thing is that I'm unable to serialize not_a_date_time ptimes. The extractions fails here. I'm using the binary archive. Is that supported? The documentation of date time only states compatibility with text and XML archive... Any hints are greatly appreciated and thanks in advance. kind regards Alex template<class Archive, class T> void save( Archive & ar, const boost::optional<T> & t, const unsigned int /*version*/ ){ bool tflag = t; ar << boost::serialization::make_nvp("initialized", tflag); if (tflag) //ar << boost::serialization::make_nvp("value", &(*t)); ar << &(*t); } template<class Archive, class T> void load( Archive & ar, boost::optional<T> & t, const unsigned int /*version*/ ){ bool tflag; ar >> boost::serialization::make_nvp("initialized", tflag); if (tflag){ T* p; ar >> p;// boost::serialization::make_nvp("value", p); t.reset(*p); //T aux; //ar >> boost::serialization::make_nvp("value", aux); //t.reset(aux); delete p; } else { t.reset(); } }

2 1

Re: [Boost-users] Test Tools Linking Problem
by Merrill Cornish 29 Jul '05

29 Jul '05

John, <sound of head banging on the keyboard> Yes, I knew the order was important, but I remembered the wrong order. :-( Thanks, Merrill

1 0

Re: [Boost-users] Test Tools Linking Problem
by Merrill Cornish 29 Jul '05

29 Jul '05

Gennadiy, I re-built the libs just as you said. I then copied the newly built static library to the stage/lib directory where I have all of the others. Unfortunately, I still got the same undefined. HOWEVER!... This is the first time I've noticed the boost_1_32_0/bin directory. I tried copying test_tools.obj into the directory with my own object files, added test_tools.obj to the list of my own object files in my make, and the link WORKED! To me, that says the Boost code if OK, but I've messed up makefile. (It's been many years since I've had to do battle with a raw makefile, and it wasn't GCC's make then.) I've appended an excerpt from my makefile. The "test" target is the one that gets the undefined referenced UNLESS test_tools.obj is included in the ${testobjs} list. (Yes, there is a TAB before ${CXX}.) What's wrong with the makefile? Merrill ---------------------------------------------------------------- basedir = E:/DigS boostdir = E:/boost_1_32_0 boostlibdir = ${boostdir}/stage/lib boostlibtype = -mgw-mt-1_32 boostlibs = ${boostlibdir}/boost_regex${boostlibtype}.dll boosttestlibs = ${boostlibdir}/libboost_unit_test_framework${boostlibtype}.lib . . . test : ${testobjs} ${CXX} -o test ${boosttestlibs} ${boostlibs} test.o ${testobjs}

3 2