September 2005 - Boost-users

Documentation links home
by Andy Little 26 Sep '05

26 Sep '05

Hi, I was looking at http://www.boost.org/libs/smart_ptr/smart_ptr.htm and I was surprised to find that there was no link to the main boost page. There are many other doc pages that dont have a link either to their own index pages or the boost index page. (Though many others do e.g http://www.boost.org/doc/html/date_time.html .) Anyone arriving at pages with no link to their parents has no direct way to find e.g what is boost or how/ where to download the boost libraries. That aside it is annoying when browsing that one has no means to get back up the tree. URLs such as smart pointer above are frequently posted on eg comp.lang.++, but the lack of any simple means to get up the tree must leave many potential users stranded and frustrated. Shouldnt it possible at least to get from any page in a libraries documentation to its main index page (e.g http://www.boost.org/libs/smart_ptr/shared_ptr.htm) and ideally http://www.boost.org/ too? (FWIW You could at least make the boost logo a link to http://www.boost.org/) Just a thought. Andy Little

3 5

[xpressive] multiple matches for a group
by Cory Nelson 26 Sep '05

26 Sep '05

I'm attempting to learn xpressive by writing a simple IRC regex. The IRC protocol goes like: :prefix numericreplyorcommandstring param1 param2 :trailing param The regex looks like this (ignore comments and newlines): ^ (?::(\S+)\s)? // prefix (?:(\d+)|(\S+)) // command (?:\s([^:]\S*))* // parameters (?:\s:(.+))? // trailing parameter $ And my static xpressive looks like this: bos >> optional(':' >> (s1=+~_s) >> _s) >> // prefix ((s2=+_d)|(s3=+~_s)) >> // command *(_s >> (s4 = ~as_xpr(':') >> *~_s)) >> // parameters optional(_s >> ':' >> (s5=+_)) >> // trailing parameter eos I'm not sure how to retrieve the multiple matches for s4 - any help? -- Cory Nelson http://www.int64.org

3 2

[serialization] vector deserialization problem
by Sergey Filippov 26 Sep '05

26 Sep '05

Hi, all. I'm using boost 1.33.0 and I have a problem deserializing from an archive (I'm using VC 7.1). To reproduce the problem I wrote a sample program listed below. #include <sstream> #include <boost/archive/binary_oarchive.hpp> #include <boost/archive/binary_iarchive.hpp> #include <boost/serialization/export.hpp> #include <boost/serialization/vector.hpp> struct A { virtual ~A() {} friend class boost::serialization::access; template<class Archive> void serialize(Archive & ar, const unsigned int version) {} }; struct B: A { friend class boost::serialization::access; template<class Archive> void serialize(Archive & ar, const unsigned int version) { ar & boost::serialization::base_object<A>(*this); } }; BOOST_CLASS_EXPORT(A); BOOST_CLASS_EXPORT(B); int main(int argc, char* argv[]) { std::string str; { std::stringstream stream; boost::archive::binary_oarchive ar(stream); B b; std::vector<int> v(10); ar & b; ar & v; str = stream.rdbuf()->str(); } { std::stringstream stream; stream.rdbuf()->str(str); boost::archive::binary_iarchive ar(stream); B b; std::vector<int> v; ar & b; ar & v; // causes an assert } return 0; } During deserialization of the vector (a line with "// causes an assert"), an assert occurs in the line 266 in basic_iarchive.cpp. I don't understand the library source code well, but it looks something strange for me. As far as I understood the reset_object_address function supposed to be called with addresses of tracked objects. In my case the new_address parameter is the address of an element in the vector. But the vector elements are of a primitive type and must not be tracked. Maybe reset_object_address supposed to handle such a situation, but in the provided sample something goes wrong. If I skip the line with reset_object_address in archive_input_seq (collections_load_impl.hpp, line 91) in debugger, the sample works as expected. Also with 1.32 (in which archive_input_seq almost identical with one in 1.33 except the call to reset_object_address) the sample works as well. So I'm considering to patch the library by commenting this line. What side effects will it have? I as understood from previous posts in this forum reset_object_address was added as a bugfix to loading of containers with pointers to trackable objects. Is it safe to comment out the reset_object_address call, if I do not serialize such containers? Or maybe I'm just using the serialization library in a wrong way? Then where is the problem in my code? Thanks in advance. Sergey

2 1

Re: [Boost-users] [BBv2] getting started problem with headers
by Tino S. 26 Sep '05

26 Sep '05

Hi Volodya, after checking the "bin\msvc\release\hello.obj.rsp" file i saw that the backslashes was removed from the path name. Input in Jamfile : <include>D:\Temp\boost_1_33_0 Ouput in hello.obj.rsp: -I"D:Tempboost_1_33_0" Should the path substitution fixed in bjam? I changed the backslashes to slashes in Jamfile, removed the bin folder and invoked bjam ... and now it works!!! :) I tryed again the exe hello3 : hello.cpp : <include>$(BOOST_ROOT) ; after removing the bin folder and this works to!!! ..hmmm..??? Thanks a lot Volodya for fast help!! Tino ___________________________________________________________ Was denken Sie über E-Mail? Wir hören auf Ihre Meinung: http://surveylink.yahoo.com/wix/p0379378.aspx

2 1

Re: [Boost-users] [BBv2] getting started problem with headers
by Tino S. 26 Sep '05

26 Sep '05

>To begin with, try: > > exe hello : hello.cpp : <include>FULL_PATH_TO_BOOST ; > >If that builds, we can go on to solve you problem with >project constant. >If not, tell me what specific problem you have? Are >boost headers not found? >Or you get an error from Boost.Build? Or something >else? Hi Volody, thanks for the helping, but it would'nt work... The compliler could'nt find the boost header file. bjam should add -I$(BOOST_ROOT) to the command line invocation for compiling. Again my Jamfile ECHO " Build :\"" $(__name__) " boost dir: " $(BOOST_ROOT) ; exe hello1 : hello.cpp : <include>D:\Temp\boost_1_33_0 ; # hard coded... bad And this is my cmd output: D:\Temp\my_prj>bjam -d4 release Build :" Jamfile</D:/Temp/my_prj> boost dir: D:\Temp\boost_1_33_0 make -- all make -- all time -- all: unbound make -- <pbin\msvc\release>hello1.exe make -- <pbin\msvc\release>hello1.exe bind -- <pbin\msvc\release>hello1.exe: bin\msvc\release\hello1.exe time -- <pbin\msvc\release>hello1.exe: missing make -- bin\msvc\release make -- bin\msvc\release time -- bin\msvc\release: Thu Sep 22 20:47:40 2005 make -- bin\msvc make -- bin\msvc time -- bin\msvc: Thu Sep 22 20:47:40 2005 make -- bin make -- bin time -- bin: Thu Sep 22 20:47:40 2005 made stable bin made stable bin\msvc made stable bin\msvc\release make -- <pbin\msvc\release>hello.obj make -- <pbin\msvc\release>hello.obj bind -- <pbin\msvc\release>hello.obj: bin\msvc\release\hello.obj time -- <pbin\msvc\release>hello.obj: missing make -- <p.-object(c-scanner)@1>hello.cpp make -- <p.-object(c-scanner)@1>hello.cpp bind -- <p.-object(c-scanner)@1>hello.cpp: hello.cpp time -- <p.-object(c-scanner)@1>hello.cpp: Thu Sep 22 20:37:12 2005 make -- <p.>hello.cpp make -- <p.>hello.cpp bind -- <p.>hello.cpp: hello.cpp time -- <p.>hello.cpp: Thu Sep 22 20:37:12 2005 made stable <p.>hello.cpp make -- <p.-object(c-scanner)@1>hello.cpp make -- <p.-object(c-scanner)@1>hello.cpp time -- <p.-object(c-scanner)@1>hello.cpp: unbound make -- <object(c-scanner)@1>boost/array.hpp make -- <object(c-scanner)@1>boost/array.hpp bind -- <object(c-scanner)@1>boost/array.hpp: boost/array.hpp time -- <object(c-scanner)@1>boost/array.hpp: missing made stable <object(c-scanner)@1>boost/array.hpp make -- <object(c-scanner)@1>iostream make -- <object(c-scanner)@1>iostream bind -- <object(c-scanner)@1>iostream: iostream time -- <object(c-scanner)@1>iostream: missing made stable <object(c-scanner)@1>iostream made* newer <p.-object(c-scanner)@1>hello.cpp make -- <pbin\msvc\release>hello.obj.rsp make -- <pbin\msvc\release>hello.obj.rsp bind -- <pbin\msvc\release>hello.obj.rsp: bin\msvc\release\hello.obj. rsp time -- <pbin\msvc\release>hello.obj.rsp: Thu Sep 22 20:47:40 2005 made+ temp <pbin\msvc\release>hello.obj.rsp made+ update <pbin\msvc\release>hello.obj make -- <pbin\msvc\release>hello1.exe.rsp make -- <pbin\msvc\release>hello1.exe.rsp bind -- <pbin\msvc\release>hello1.exe.rsp: bin\msvc\release\hello1.exe .rsp time -- <pbin\msvc\release>hello1.exe.rsp: missing made+ update <pbin\msvc\release>hello1.exe.rsp made+ update <pbin\msvc\release>hello1.exe made update all ...found 12 targets... ...using 1 temp target... ...updating 3 targets... ...using <pbin\msvc\release>hello.obj.rsp... msvc.compile.c++ bin\msvc\release\hello.obj call "C:\Programme\Microsoft Visual Studio .NET 2003\Vc7\bin\vcvars32.bat" > nul cl /Zm800 -nologo -TP /Ob2 /GR /MD /Ogity /O2 /Gs /wd4675 /EHs @"bin\msvc\r elease\hello.obj.rsp" -c -Fo"bin\msvc\release\hello.obj" && del /f "bin\msvc\ release\hello.obj.rsp" Executing through .bat file Executing command [cmd.exe] [/Q/C] [C:\DOKUME~1\Tino\LOKALE~1\Temp\jam672-00.bat ] hello.cpp hello.cpp(9) : fatal error C1083: Include-Datei kann nicht geöffnet werden: 'boo st/array.hpp': No such file or directory 0.015625 sec system; 0.015625 sec user ...failed msvc.compile.c++ bin\msvc\release\hello.obj... ...skipped <pbin\msvc\release>hello1.exe.rsp for lack of <pbin\msvc\release>hell o.obj... ...skipped <pbin\msvc\release>hello1.exe for lack of <pbin\msvc\release>hello.ob j... ...failed updating 1 target... ...skipped 2 targets... Should i use the current cvs version? Tino ___________________________________________________________ Gesendet von Yahoo! Mail - Jetzt mit 1GB Speicher kostenlos - Hier anmelden: http://mail.yahoo.de

2 1

Python 'in' keyword-like in C++
by Tzu-Chien Chiu 25 Sep '05

25 Sep '05

Any boost library can make me write the expression like int x = 3; if ( x in list(3, 5, 6, 7) ) { ... } -- Tzu-Chien Chiu, 3D Graphics Hardware Architect <URL:http://www.csie.nctu.edu.tw/~jwchiu>

4 8

Re: [Boost-users] Newbie questions - regex namespace issue
by Charlton, Paul 25 Sep '05

25 Sep '05

Problem solved -- as for some shared learning -- the msvc.jam file was always stomping my <carefully> set Environment variables by calling "vcvars32.bat" as a setup, and placing MSVC/Includes ahead of STLPORT in the include search path. Msvc.jam has logic for "user setup|vcvars32", but does not have logic for "user setup|vcvars32|<do nothing, use env>" -- of course, providing a stubbed "setup.bat" will do the trick of keeping the env vars pristine. -----Original Message----- From: boost-users-bounces(a)lists.boost.org [mailto:boost-users-bounces@lists.boost.org] On Behalf Of John Maddock Sent: Sunday, September 25, 2005 2:27 AM To: boost-users(a)lists.boost.org Subject: Re: [Boost-users] Newbie questions - regex namespace issue >I just downloaded and built boost 1.33 for VC-8_0 and STLPORT 5.0. >(which required adding a jam file for vc-8_0) the build seems to have >gone fine, and a lot of things work, but I get the following link >error which seems to indicate that at least part of boost builds for >a client application with the wrong namespace on >stlpd_std::allocator<signature>. The library actually has exports for >std::allocator<signature> If the library has symbols with std:: in them, then it was *not* built against STLport. Double check all your bjam build options (do we have a toolset for VC8 and STLport anyway?), and if all else fails, I suggest you treat the regex lib as "just a bunch of sources" and build from your IDE, taking care to ensure that build options are the same as for your application. John. _______________________________________________ Boost-users mailing list Boost-users(a)lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users

1 0

Newbie questions - regex namespace issue
by Charlton, Paul 25 Sep '05

25 Sep '05

I just downloaded and built boost 1.33 for VC-8_0 and STLPORT 5.0. (which required adding a jam file for vc-8_0) the build seems to have gone fine, and a lot of things work, but I get the following link error which seems to indicate that at least part of boost builds for a client application with the wrong namespace on stlpd_std::allocator<signature>. The library actually has exports for std::allocator<signature> I realize that it could easily be operator error <mine>, but I don't have the tools handy to backtrack through miles of templates and #define configuration variables to grok the underlying cause yet. Any pointers would be appreciated. ============================================================================ ========== FileUtils.obj : error LNK2019: unresolved external symbol "public: bool __thiscall boost::re_detail::perl_matcher<char const *,class stlpd_std::allocator<struct boost::sub_match<char const *> >,struct boost::regex_traits<char,class boost::w32_regex_traits<char> > >::match(void)" (?match@?$perl_matcher@PBDV?$allocator@U?$sub_match@PBD@boost@@@stlpd_std@@U ?$regex_traits@DV?$w32_regex_traits@D@boost@@@boost@@@re_detail@boost@@QAE_N XZ) referenced in function "bool __cdecl boost::regex_match<char const *,class stlpd_std::allocator<struct boost::sub_match<char const *> >,char,struct boost::regex_traits<char,class boost::w32_regex_traits<char> > >(char const *,char const *,class boost::match_results<char const *,class stlpd_std::allocator<struct boost::sub_match<char const *> > > &,class boost::basic_regex<char,struct boost::regex_traits<char,class boost::w32_regex_traits<char> > > const &,enum boost::regex_constants::_match_flags)" (??$regex_match@PBDV?$allocator@U?$sub_match@PBD@boost@@@stlpd_std@@DU?$rege x_traits@DV?$w32_regex_traits@D@boost@@@boost@@@boost@@YA_NPBD0AAV?$match_re sults@PBDV?$allocator@U?$sub_match@PBD@boost@@@stlpd_std@@@0@ABV?$basic_rege x@DU?$regex_traits@DV?$w32_regex_traits@D@boost@@@boost@@@0@W4_match_flags@r egex_constants@0@@Z) FileUtils.obj : error LNK2019: unresolved external symbol "public: __thiscall boost::re_detail::perl_matcher<char const *,class stlpd_std::allocator<struct boost::sub_match<char const *> >,struct boost::regex_traits<char,class boost::w32_regex_traits<char> > >::perl_matcher<char const *,class stlpd_std::allocator<struct boost::sub_match<char const *> >,struct boost::regex_traits<char,class boost::w32_regex_traits<char> > >(char const *,char const *,class boost::match_results<char const *,class stlpd_std::allocator<struct boost::sub_match<char const *> > > &,class boost::basic_regex<char,struct boost::regex_traits<char,class boost::w32_regex_traits<char> > > const &,enum boost::regex_constants::_match_flags)" (??0?$perl_matcher@PBDV?$allocator@U?$sub_match@PBD@boost@@@stlpd_std@@U?$re gex_traits@DV?$w32_regex_traits@D@boost@@@boost@@@re_detail@boost@@QAE@PBD0A AV?$match_results@PBDV?$allocator@U?$sub_match@PBD@boost@@@stlpd_std@@@2@ABV ?$basic_regex@DU?$regex_traits@DV?$w32_regex_traits@D@boost@@@boost@@@2@W4_m atch_flags@regex_constants@2@@Z) referenced in function "bool __cdecl boost::regex_match<char const *,class stlpd_std::allocator<struct boost::sub_match<char const *> >,char,struct boost::regex_traits<char,class boost::w32_regex_traits<char> > >(char const *,char const *,class boost::match_results<char const *,class stlpd_std::allocator<struct boost::sub_match<char const *> > > &,class boost::basic_regex<char,struct boost::regex_traits<char,class boost::w32_regex_traits<char> > > const &,enum boost::regex_constants::_match_flags)" (??$regex_match@PBDV?$allocator@U?$sub_match@PBD@boost@@@stlpd_std@@DU?$rege x_traits@DV?$w32_regex_traits@D@boost@@@boost@@@boost@@YA_NPBD0AAV?$match_re sults@PBDV?$allocator@U?$sub_match@PBD@boost@@@stlpd_std@@@0@ABV?$basic_rege x@DU?$regex_traits@DV?$w32_regex_traits@D@boost@@@boost@@@0@W4_match_flags@r egex_constants@0@@Z) QBUtilities.DLL : fatal error LNK1120: 2 unresolved externals

2 1

Re: [Boost-users] Boost.Thread memory leak reported
by Will Bryant 25 Sep '05

25 Sep '05

Continuing on the thread about the threadmon singleton: > In addition, there is no good place to put the delete. You have to play > games with atexit and then deal with the possibily of resurrection > (singleton access after it's been deleted.) Can we not just use a static instance of a small deleter class whose destructor frees the singleton? (Note that I'm not suggesting that we use the static instance to also _create_ the singleton, nor to be the singleton itself - as already discussed, that's insufficient as there's no general way to specify initialization order so using call_once remains the best option there IMHO - but we _can_, I believe, fix the problem that's causing Visual C++ programs to spew out memory leak errors every time we run them.) -- Will Bryant http://carcino.gen.nz/ will(a)core-dev.co.nz +64 21 655 443

1 0

[mpl] bug in mpl::at?
by Geoffrey Romer 24 Sep '05

24 Sep '05

I'm trying to use the 3-argument version of the mpl::at metafunction, as described in the on-line manual[1], but I'm getting a compile error (using gcc 4.0.2): --- error: wrong number of template arguments (3, should be 2) /usr/include/boost/mpl/at_fwd.hpp:20: error: provided for 'template<class Sequence, class N> struct boost::mpl::at' --- Looking at at.hpp, at_fwd.hpp, and aux_/at_fwd.hpp, I don't see any sign of a 3-argument version of at; everything seems to be defined in terms of a 2-argument template. Am I doing something wrong, or is this a bug? [1] http://www.boost.org/libs/mpl/doc/refmanual/at.html

1 0