May 2004 - Boost-users - lists.boost.org

Building 1.31.0 with intel-linux for Itanium 2
by Richard Hadsell 10 May '04

10 May '04

I am trying to build the Boost libraries on an Itanium 2 Linux machine using Intel C++ 8.0. The problem is that bjam is creating a directory path for the release versions that uses the string "ebug release" instead of "release". For example: MkDir1 bin/boost/libs/regex/build/libboost_regex.a/intel-linux/ebug release intel-linux-C++-action bin/boost/libs/regex/build/libboost_regex.a/intel-linux/ebug release/c_regex_traits.o ... Despite the directory that it creates with an embedded space, everything actually continues quite well, until it tries to run ranlib: intel-linux-Archive-action bin/boost/libs/regex/build/libboost_regex.a/intel-linux/ebug release/libboost_regex-il-1_31.a Ranlib bin/boost/libs/regex/build/libboost_regex.a/intel-linux/ebug release/libboost_regex-il-1_31.a ranlib: bin/boost/libs/regex/build/libboost_regex.a/intel-linux/ebug: No such file or directory ranlib bin/boost/libs/regex/build/libboost_regex.a/intel-linux/ebug release/libboost_regex-il-1_31.a ...failed Ranlib bin/boost/libs/regex/build/libboost_regex.a/intel-linux/ebug release/libboost_regex-il-1_31.a... I built bjam with this: build.sh intel-linux And I built the libraries with this: bjam -sTOOLS=intel-linux -sINTEL_PATH=/usr/local/intel/compiler80/ia64 --with-python-root=/usr --stagedir=stage -sBUILD="debug release <threading>single" stage Can anyone suggest what might be wrong with my system? It is a loaner, so everything is untested as far as I'm concerned. I have no idea what other tools in addition to Bjam itself might be involved in causing this problem. -- Dick Hadsell 914-259-6320 Fax: 914-259-6499 Reply-to: hadsell(a)blueskystudios.com Blue Sky Studios http://www.blueskystudios.com 44 South Broadway, White Plains, NY 10601

3 5

Re: [Boost-users] Posix extended regexp
by Manish Madan 08 May '04

08 May '04

Thanks a lot for the help John, it works now regards Manish >>> john(a)johnmaddock.co.uk 5/6/2004 1:58:27 AM >>> > What am I doing wrong? > > Here's my short matching function: > > bool MatchRegExp(const std::string& matchThis, const std::string& > againstThis) > { > try > { > const boost::regex e(againstThis);//, > boost::regex_constants::icase); > return boost::regex_match(matchThis, e, > boost::regex_constants::extended); > } > catch(boost::bad_expression be) > { > return false; > } > > } You're passing the wrong constants in all the wrong places, it should have been: const boost::regex e(againstThis, boost::regex::extended); return boost::regex_match(matchThis, e, boost::match_default); You can omit the match_default flag (since it's the default anyway), and if you wanted case insensitive matching it would have been: const boost::regex e(againstThis, boost::regex::extended | boost::regex::icase); Oh, and don't forget to check the difference between regex_match and regex_search (the match version requires all of the text to match). John. _______________________________________________ Boost-users mailing list Boost-users(a)lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users

2 2

RE: [Boost-users] Re: shared_ptrs with std::mem_fn
by Mark Storer 08 May '04

08 May '04

> boost::mem_fn erases the need for a separate mem_fn_ref. If > http://www.boost.org/libs/bind/mem_fn.html fails to explain it to you, > please ask more specific questions. I thought I'd been pretty specific... guess not. Allow me to reiterate: Why doesn't std::mem_fun work with a container of boost::shared_ptr? I fiddled around with my compiler for a while (vc6), but ended up with a wildly unhelpful error message. Given the following lines of code (among others): --- typedef std::vector<boost::shared_ptr<std::string> > Strings; Strings strings; std::for_each( strings.begin(), strings.end(), std::mem_fun(std::string::size) ); --- my compiler puked up the following wildly useless error message: --- error C2664: 'mem_fun' : cannot convert parameter 1 from 'unsigned int (__thiscall std::basic_string<char,struct std::char_traits<char>,class std::allocator<char> >::*' to 'unsigned int (__thisca ll std::basic_string<char,struct std::char_traits<char>,class std::allocator<char> >::*' Types pointed to are unrelated; conversion requires reinterpret_cast, C-style cast or function-style cast --- Allow me to pull out those two types for easier viewing: unsigned int (__thiscall std::basic_string<char,struct std::char_traits<char>,class std::allocator<char> >::* unsigned int (__thiscall std::basic_string<char,struct std::char_traits<char>,class std::allocator<char> >::* Golly. Those 'two' types are about as related as you can get. So why won't std::mem_fun work through boost::shared_ptr's operator->? Here's the mem_fun that ships with VC6: --- template<class _R, class _Ty> class mem_fun_t : public unary_function<_Ty *, _R> { public: explicit mem_fun_t(_R (_Ty::*_Pm)()) : _Ptr(_Pm) {} _R operator()(_Ty *_P) const {return ((_P->*_Ptr)()); } private: _R (_Ty::*_Ptr)(); }; --- The relevant portion to our discussion is: "{return ((_P->*_Ptr()); }" which can be further boiled down to: return _P->_Ptr(); This looks an awful lot like it should work with a shared_ptr's operator->(). So why doesn't it? I admit that this is more of a C++ question than a boost one, but it's not too much of a tangent and I *am* curious. Mentioning mem_fun_ref in my previous post only served to muddy the waters. My apologies. --Mark Storer Senior Software Engineer Verity, Inc.

2 1

shared_ptrs with std::mem_fn
by Steve Folly 07 May '04

07 May '04

Hi, I've converted a container to use shared_ptrs instead of regular pointers, now my for_each algorithm doesn't work: Before: class Attr; std::vector< Attr* > mAttributes; . . . std::for_each( mAttributes.begin(), mAttributes.end(), std::bind2nd( std::mem_fn( &Attr::Write ), output ) ); After: std::vector< shared_ptr<Attr> > mAttributes; Now it doesn't compile because (of course) Attr::Write is not a method of shared_ptr<Attr>. Do I have to use boost's bind and mem_fn objects instead of std? Thanks for any help. -- Regards, Steve.

3 2

RE: [Boost-users] Re: shared_ptrs with std::mem_fn
by Mark Storer 07 May '04

07 May '04

> > Now it doesn't compile because (of course) Attr::Write is > not a method of > > shared_ptr<Attr>. > > > > Do I have to use boost's bind and mem_fn objects instead of std? > > Yes; bind and mem_fn handle this problem (and quite a few > others) automatically. Why is this a problem? I thought std::mem_fn called the function through the -> operator, which 'should' work (but obviously doesn't). I would think this would only crop up through mem_fun_ref, but then you wouldn't have a container of shared_ptr<Attr>, but Attr. --Baffled --Mark Storer Senior Software Engineer Verity, Inc.

2 1

RE: [Boost-users] date_time clocks, microsec_clock, etc
by Darryl Green 07 May '04

07 May '04

> For those that need something portable we should be able to > get microsecond > resolution for Windows, Linux, and probably a few more... > > Jeff Microsecond resolution on linux? What interface provides this? I have a linux platform or 2 that I'm pretty sure won't provide it at present, but probably could with some kernel hacking, if only there was some sensible interface to connect it to user space. Darryl. ########################################################################## This e-mail is for the use of the intended recipient(s) only. If you have received this e-mail in error, please notify the sender immediately and then delete it. If you are not the intended recipient, you must not use, disclose or distribute this e-mail without the author's prior permission. We have taken precautions to minimise the risk of transmitting software viruses, but we advise you to carry out your own virus checks on any attachment to this message. We cannot accept liability for any loss or damage caused by software viruses. ##########################################################################

3 2

how to install library in msvc
by kason aung 07 May '04

07 May '04

Dear all, I'm trying to install BGL on win 2k, vc++ 6 machine. I can't install BGL now. So if u have already successfully installed on msvc, i would like to know step-by-step installation procedure. I am looking forward to hearing good news from all of you. Thanks a lot for ur help and kindness. Regards, Kason _________________________________________________________________ Download games, logos, wallpapers and lots more at MSN Mobile! http://www.msn.com.sg/mobile/

1 0

date_time clocks, microsec_clock, etc
by Aaron W. LaFramboise 07 May '04

07 May '04

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, I'm a little curious whats in the works for date_time clock support. Specifically, there still doesn't seem to be anything better than a second-granularity clock for Win32. In addition, the UNIX clock is not always as precise as it could be. In particular, the popular Pentium and and some other architectures have some sorts of cycle-granularity hardware clock or similar that can exceed the usual operating system clock used for time. Really--and I have no idea what work is presently being done on this--it might do people in some problem domains (including myself, at times) a lot of good to have clocks with separate notions of precision and accuracy. For example, on a Pentium, operating systems I care about tend to have a maximum system clock accuracy around about a millisecond plus or minus some, and its probably difficult or tricky to get better than that. However, if the system clock was used in combination with the Pentium cycle counter, we could probably get precision in excess of a nanosecond. Perhaps an interface for such a clock system might be: typedef boost::date_time::clock<type_of_accuracy_you_need_here, type_of_precision_you_need_here> myclock; To get the above imagined clock, I might use: clock<microsecond_accuracy, cycle_precision> If the clock requested was unavailable on the platform, a compile time error might result. Of course, oftentimes we know the characteristics of a clock's accuracy or precision, such as the Pentium cycle counter, but we don't know exactly how precise it is, so it might be inappropriate to refer to that clock as nanosecond_precision when it really might not be. In summary, a reliable cross-platform sub second clock is one of the features I miss most in date_time, and one of the features I can afford to miss least. Is anyone working on remedying this right now? Aaron W. LaFramboise OpenPGP fingerprint: CFB4 D883 17ED E9BE 6F16 1BF7 969F E586 75AC 33C4 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFAlZuhxDYk2wAn5+8RAg5jAJ0XINhLFb4KikH+oK286PQfu6iMaQCgnTe5 SlmNLXTitPUWuUYMKrHIQgY= =bJvg -----END PGP SIGNATURE-----

5 12

Using pool_alloc with std::map
by Kevin Lin 06 May '04

06 May '04

I am using boost::pool_alloc with std::map like this: typedef map<int, int, less<int>, pool_alloc<pair<int, int> > > MapT; MapT myMap; After myMap passes out of scope, I want to release unused memory from the pool. To do that, I need to get the type used to request chunks from the pool. pair<int, int> is not the answer since map uses rebind to get a different allocator. So how do I go about obtaining the correct singleton_pool interface? Your help is appreciated. -- Kevin Lin

1 0

Question about compiling boost.1.31.0 on Solaris
by Wenning Qiu 06 May '04

06 May '04

I was trying to build the regex library from boost.1.31.0 on a Solaris 7 box using STLport.4.6.2. I have a couple of STLport versions installed in /opt. Here's how I built: o cd boost_1_31_0/libs/regex/build o /export/home/qiuw01/research/boost-jam-3.1.9/bin.solaris/bjam "-sTOOLS=sunpro-stlport" -sSTLPORT_PATH=/opt I was expecting STLport.4.6.2 to be used. However when I used ldd on the generated .so library, it shows a dependency on an old version of STLport in /usr/lib qiuw01$ ldd libboost_regex-sw-p-1_31.so librt.so.1 => /usr/lib/librt.so.1 libstlport_sunpro.so.4.5 => /usr/lib/libstlport_sunpro.so.4.5 libaio.so.1 => /usr/lib/libaio.so.1 libc.so.1 => /usr/lib/libc.so.1 libdl.so.1 => /usr/lib/libdl.so.1 /usr/platform/SUNW,Ultra-4/lib/libc_psr.so.1 <ethos:~/research/boost_1_31_0/bin/boost/libs/regex/build/libboost_regex.so/ sunpro-stlport/release> This doesn't seem to be right. Any comments? Thanks, Wenning Qiu

1 0