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

problem with serialization
by Benjamin Lau 05 Sep '05

05 Sep '05

Hello all, I'm new to the serialization library and new to Boost in general and as many newbies do, have some problems using them. I'm trying to serialize an object in my program but the compiler keeps on reporting errors about the types. Specifically, it trips on the BOOST_STATIC_ASSERT(check_tracking<T>::value); in oserializer.hpp in include/archive/detail. The exact compiler message is: C:/Boost/include/boost-1_33/boost/archive/detail/oserializer.hpp: In function `void boost::archive::save(Archive&, T&) [with Archive = boost::archive::text_oarchive, T = std::vector<Builder, std::allocator<Builder> >]': C:/Boost/include/boost-1_33/boost/archive/basic_text_oarchive.hpp:78: instantiated from `void boost::archive::basic_text_oarchive<Archive>::save_override(T&, int) [with T = std::vector<Builder, std::allocator<Builder> >, Archive = boost::archive::text_oarchive]' C:/Boost/include/boost-1_33/boost/archive/detail/interface_oarchive.hpp:85: instantiated from `Archive& boost::archive::detail::interface_oarchive<Archive>::operator<<(T&) [with T = std::vector<Builder, std::allocator<Builder> >, Archive = boost::archive::text_oarchive]' sconbuild.cpp:557: instantiated from here C:/Boost/include/boost-1_33/boost/archive/detail/oserializer.hpp:566: error: incomplete type `boost::STATIC_ASSERTION_FAILURE< false>' used in nested name specifier C:/Boost/include/boost-1_33/boost/archive/detail/oserializer.hpp:566: error: size of array has non-integral type `<type error>' Basically, I'm trying to serialize a std::vector<Builder>. Builder is a class that employs selective serialization, it only serializes certain members depending on what type this Builder is. I use a switch-case statement for that: switch(type) { case 0: ar & program; break; case 1: ar & object; break; case 2: ar & java; break; case 3: ar & comment; break; case 4: ar & print; break; case 5: ar & variable; break; case 6: ar & library; break; case 7: ar & sharedLibrary; break; case 8: ar & node; break; case 9: ar & import; break; case 10: ar & code; break; case 11: ar & sourceSignatures; break; case 12: ar & targetSignatures; break; case 13: ar & setOption; break; case 14: ar & ignore; break; case 15: ar & depend; break; case 16: ar & environmentVariable; break; } These members I am serializing are shared pointers of class types, and each of these class types has a serialize member function that serializes primitive/standard library data types, i.e.: template<class Archive> void serialize(Archive & ar, const unsigned int version) { ar & indent; //std::string ar & target; // std::string ar & file; //std::string } That said, ALL of my serializations in these subtypes, i.e. ar & environmentVariable all serialize booleans and std::string. Here is a summary of what I am doing: 1. serialize a vector of Builder objects 2. Builder objects have their shared_ptr selectively serialized 3. The types used to instantiate shared_ptr in my program all serialize booleans and/or std::string I read up on modifying object tracking to track_never but it still doesn't work. Is there something I am doing wrong here? Thank you Benjamin Lau (Windows XP SP2, MinGW with no STLPort) P/s If there is insufficient information, or it is not clear, my most sincere apologies, because the last time I posted whole code on a mailing list, the mailing list program rejected my post. I'll try and get a program that can replicate this behaviour, but so far nothing seems to replicate this behaviour. Thanks you.

1 0

VC++2005 B2: x64 issues
by Cory Nelson 05 Sep '05

05 Sep '05

I get a bunch of warnings from boost filesystem about abi_prefix/suffix "alignment changed after including header, may be due to missing #pragma pack(pop)". But I'm getting one linker error from boost thread: libboost_thread-vc80-mt-s-1_33.lib(once.obj) : error LNK2001: unresolved external symbol _InterlockedCompareExchange I changed compare_exchange's body in once.cpp from: ice_wrapper(&InterlockedCompareExchange, dest, exch, cmp); to: return InterlockedCompareExchange(dest, exch, cmp); and it worked. -- Cory Nelson http://www.int64.org

2 1

Boost serialization storage question
by Leon Mergen 04 Sep '05

04 Sep '05

Hello, I wondered how the Boost.Serialization library determines how many bytes to read from an input stream to "fill" a class with data. That is, does it read an entire input stream until the end of the stream and use that as the data to fill a class with, or does it perform a sizeof(class) and read that from the stream ? If it is the latter, then out of curiosity, how does it determine the size of an object with different class versions ( so if an object version 1 has been saved and then tries to load version 2 ) ? Does it write some sort of object size at the beginning of the file ? If it reads the entire stream until the end, what would be a good approach to save multiple objects in a single file, and be able to read just a few objects out of the file ? Thanks in advance for any responses. Regards, Leon Mergen

2 3

Compilation problem with date_time and iostream gzip (and bzip2) filters
by tonton 04 Sep '05

04 Sep '05

This simple test fails to compile with gcc 4.0.1 (or 4.0.2, it's the debian unstable version) and boost 1.33.0 if the date_time include is uncommented. Is there any known incompatibility between the two libraries ? #include <boost/iostreams/filtering_stream.hpp> #include <boost/iostreams/filter/gzip.hpp> // #include <boost/date_time/local_time/local_time.hpp> int main() { boost::iostreams::filtering_istream in; in.push(boost::iostreams::gzip_compressor()); return 0; } The full error is attached /usr/include/boost/iostreams/filter/symmetric.hpp: In member function ‘std::streamsize boost::iostreams::symmetric_filter<SymmetricFilter, Alloc>::read(Source&, typename boost::iostreams::char_type_of<T>::type*, std::streamsize) [with Source = boost::iostreams::detail::linked_streambuf<char, std::char_traits<char> >, SymmetricFilter = boost::iostreams::detail::zlib_compressor_impl<std::allocator<char> >, Alloc = std::allocator<char>]’: /usr/include/boost/iostreams/filter/gzip.hpp:199: instantiated from ‘std::streamsize boost::iostreams::basic_gzip_compressor<Alloc>::read(Source&, char*, std::streamsize) [with Source = boost::iostreams::detail::linked_streambuf<char, std::char_traits<char> >, Alloc = std::allocator<char>]’ /usr/include/boost/iostreams/read.hpp:215: instantiated from ‘static std::streamsize boost::iostreams::detail::read_filter_impl<boost::iostreams::multichar_tag>::read(T&, Source&, typename boost::iostreams::char_type_of<T>::type*, std::streamsize) [with T = boost::iostreams::basic_gzip_compressor<std::allocator<char> >, Source = boost::iostreams::detail::linked_streambuf<char, std::char_traits<char> >]’ /usr/include/boost/iostreams/read.hpp:56: instantiated from ‘std::streamsize boost::iostreams::read(T&, Source&, typename boost::iostreams::char_type_of<T>::type*, std::streamsize) [with T = boost::iostreams::basic_gzip_compressor<std::allocator<char> >, Source = boost::iostreams::detail::linked_streambuf<char, std::char_traits<char> >]’ /usr/include/boost/iostreams/detail/adapter/concept_adapter.hpp:247: instantiated from ‘static std::streamsize boost::iostreams::detail::flt_wrapper_impl<boost::iostreams::input>::read(Filter&, Source*, typename boost::iostreams::char_type_of<T>::type*, std::streamsize) [with Filter = boost::iostreams::basic_gzip_compressor<std::allocator<char> >, Source = boost::iostreams::detail::linked_streambuf<char, std::char_traits<char> >]’ /usr/include/boost/iostreams/detail/adapter/concept_adapter.hpp:74: instantiated from ‘std::streamsize boost::iostreams::detail::concept_adapter<T>::read(typename boost::iostreams::char_type_of<T>::type*, std::streamsize, Source*) [with Source = boost::iostreams::detail::linked_streambuf<char, std::char_traits<char> >, T = boost::iostreams::basic_gzip_compressor<std::allocator<char> >]’ /usr/include/boost/iostreams/detail/streambuf/indirect_streambuf.hpp:250: instantiated from ‘typename boost::iostreams::detail::indirect_streambuf<T, Tr, Alloc, Mode>::int_type boost::iostreams::detail::indirect_streambuf<T, Tr, Alloc, Mode>::underflow() [with T = boost::iostreams::basic_gzip_compressor<std::allocator<char> >, Tr = std::char_traits<char>, Alloc = std::allocator<char>, Mode = boost::iostreams::input]’ test.cpp:10: instantiated from here /usr/include/boost/iostreams/filter/symmetric.hpp:112: error: ‘boost::iostreams::symmetric_filter<boost::iostreams::detail::zlib_compressor_impl<std::allocator<char> >, std::allocator<char> >::<anonymous enum>’ is/uses anonymous type /usr/include/boost/iostreams/filter/symmetric.hpp:112: error: trying to instantiate ‘template<class T> struct boost::is_integral’ /usr/include/boost/iostreams/filter/symmetric.hpp:124: error: ‘boost::iostreams::symmetric_filter<boost::iostreams::detail::zlib_compressor_impl<std::allocator<char> >, std::allocator<char> >::<anonymous enum>’ is/uses anonymous type /usr/include/boost/iostreams/filter/symmetric.hpp:124: error: trying to instantiate ‘template<class T> struct boost::is_integral’ /usr/include/boost/iostreams/filter/symmetric.hpp:131: error: ‘boost::iostreams::symmetric_filter<boost::iostreams::detail::zlib_compressor_impl<std::allocator<char> >, std::allocator<char> >::<anonymous enum>’ is/uses anonymous type /usr/include/boost/iostreams/filter/symmetric.hpp:131: error: trying to instantiate ‘template<class T> struct boost::is_integral’

5 7

Renaming boost libraries
by Matt 04 Sep '05

04 Sep '05

Heya Guys, Just wondering if it's possible to rename the boost libraries after they've been built. Specifically, I want to remove the boost version (-1_33) that is appended to all the lib and dll libraries. The reason is twofold; a) our source control system will mark the libs with a label to indicate the version and b) it should make migrating to a new boost version easier. I'm pretty sure it's fine to just physically rename the static libraries but seem to remember that for dynamic libs you can't do that because the matching .lib file indicates which .dll the application should load. Am I mistaken? If not is there any other way to specify that you don't want the boost version appended to the end of the filename? Cheers, Matt

4 6

Re: [Boost-users] Same thing: dynamic bitset as member of struct!?
by Fujinobu Takahashi 04 Sep '05

04 Sep '05

Hello Bronek-san, YATTA! Multi bitsets Works very well. Very helpful suggestion for me and our colleagues. ARIGATOU GOZAIMASU. Fuji On Sat, 03 Sep 2005 22:33:32 +0100 Bronek Kozicki <brok(a)rubikon.pl> wrote: > Hello > > your constructor is incorrectly defined. Following should work: > > #include <iostream> > #include <boost/timer.hpp> > #include <boost/dynamic_bitset.hpp> > using namespace std; > using namespace boost; > > struct multi_bitsets{ > multi_bitsets() : db1(10,1ul), db2(10,2ul) {} > dynamic_bitset<> db1; > dynamic_bitset<> db2; > }; > > int main() > { > multi_bitsets mb1; > cout << "mb1.db1:" << mb1.db1 << endl; > cout << "mb1.db2:" << mb1.db2 << endl; > } > > > Best regards > > > B.

1 0

How to use dynamic bitset as member data of class?
by Fujinobu Takahashi 04 Sep '05

04 Sep '05

Hello again, I enjoy to use the dynamic_bitset for the 1 bit correlation of radio interferometor. Very useful. But how to use the dynamic bitsets as the member data of the class? class multi_bitsets{ const boost::dynamic_bitset<> db1(20,1ul); const boost::dynamic_bitset<> db2(20,1ul); this kind of code always gives me the following errors: $ g++ multi_bitset_test00.cpp multi_bitset_test00.cpp:19: error: expected identifier before numeric constant multi_bitset_test00.cpp:19: error: expected `,' or `...' before numeric constant multi_bitset_test00.cpp:19: error: ISO C++ forbids declaration of `parameter' with no type Please let me know how to use the dynamic bitsets as the member data of the class, thank you. fuji

3 5

[Boost.Python] How is shared_ptr<SubClass> matched with shared_ptr<Base> in signature?
by Nat Goodspeed 03 Sep '05

03 Sep '05

We have a smart_ptr template of our own, sort of cloned from intrusive_ptr. But I'm having trouble with Python code passing subclass objects managed by this smart_ptr to C++ methods accepting smart_ptr<base class>. Consider: class Base: { ... }; class SubClass: public Base { ... }; class Interface { public: void method(smart_ptr<Base> arg) const; }; Of course SubClass* is implicitly convertible to Base*. In C++ code, smart_ptr<SubClass> is even implicitly convertible to smart_ptr<Base>. That is, given the definitions above, this C++ code compiles and runs correctly: Interface worker; smart_ptr<SubClass> objp = new SubClass(); worker.method(objp); We can inform Boost.Python that Base objects -- and, by implication, SubClass as well -- are to be managed using smart_ptr<>. class_<Base, smart_ptr<Base>, boost::noncopyable>("Base", no_init) ... ; class_<SubClass, bases<Base> >("SubClass") ... ; We have many methods that accept smart_ptr<Base> and do appropriately polymorphic things to SubClass and its siblings. However, if a Python caller attempts to pass a SubClass object to a method accepting smart_ptr<Base>: obj = Extension.SubClass() worker = Extension.Interface() worker.method(obj) we get the following runtime error: Boost.Python.ArgumentError: Python argument types in Interface.method(Interface, SubClass) did not match C++ signature: method(class Interface {lvalue}, class smart_ptr<class Base>) That's true for both Boost 1.31 and Boost 1.32. We have not yet tried this with Boost 1.33. We're using MSVC 7.1 on Windows XP Pro. Okay, I know this is our fault, something's wrong with our smart_ptr template definition. I know that because if I recompile with this: #define smart_ptr boost::shared_ptr instead of our own smart_ptr definition, it works just fine! As noted earlier, our smart_ptr is a variant of boost::intrusive_ptr. But it appears that either there's a mysterious requirement on the smart_ptr template that we're not fulfilling, or there's special recognition of boost::shared_ptr and possibly boost::intrusive_ptr in Boost.Python. What must we add to allow Boost.Python to recognize the legal conversion from smart_ptr<SubClass> to smart_ptr<Base> when it does its argument matching? [Your next question is: why not just use one of the Boost smart pointers? Short answer: that's what we WANTED to do! We tried shared_ptr and ran afoul of the second-conversion-from-same-dumb-pointer problem; we tried intrusive_ptr and got completely entangled in new cross-DLL dependencies because intrusive_ptr doesn't deal well with incomplete pointee types. Our smart_ptr is an attempt to trade away both issues, at the cost of a mandatory pointee base class. It almost works, too, except for this baffling bug...] Thanks for your help.

1 0

boost.interval for tracking floating point rounding errors
by Frank Hess 02 Sep '05

02 Sep '05

Hi, I'm curious if it is possible to make boost.interval more convenient to use for tracking floating point rounding errors. Currently, you run into problems if you do naive things like boost::numeric::interval<double> x(0.1); since the 0.1 value gets rounded once by the compiler before the interval constructor ever sees it. Also, things like boost::numeric::interval<double> y(2), z; z = 0.1 * y; have similar problems. -- Frank

2 1

Operators with boost::reference_wrapper
by Edson Tadeu 02 Sep '05

02 Sep '05

Although boost::reference_wrapper has a casting operator to T&, when I use any operator on a reference_wrapper, I get a compiler error stating that "boost::reference_wrapper<T> does not define this operator or a conversion to a type acceptable to the predefined operator". E.g, this should compile, but doesn't: #include <string> #include <iostream> #include <boost/ref.hpp> using namespace std; using namespace boost; void main() { string s1 = "alfa"; string s2 = "beta"; reference_wrapper<string> rs1 (s1); reference_wrapper<string> rs2 (s2); bool test = rs1 < rs2; // Error here cout << rs1; // Error here too } Why is that? I'm using MSVC 7.1.

1 0

Using bind / lambda to create a functor that (1) ignores arguments, and (2) returns a constant
by Stephen Gross 02 Sep '05

02 Sep '05

Is there a way to use bind and/or lambda to create a functor that: (1) Takes as input a single argument (that is ignored), and (2) Returns a constant value. Ideally, something along the lines of: bind(constant(5), _1) // _1 is passed but ignored. Thanks, --Steve Stephen Gross Case Western School of Medicine Cleveland, OH "By Grabthar's hammer, by the sons of Worvan, you shall be avenged." - Dr. Lazarus

2 1

Reference information for lamba
by Stephen Gross 02 Sep '05

02 Sep '05

I'm trying to find reference documentation for the lambda library. I've found the main documentation on boost's website, but not reference information. Is it available somewhere? --Steve

1 0

Error using boost_serialization
by Sebastien Gerega 02 Sep '05

02 Sep '05

Can anyone tell me what is wrong with the following code: #include <iomanip> #include <iostream> #include <fstream> #include <string> #include <boost/archive/tmpdir.hpp> #include <boost/archive/text_iarchive.hpp> #include <boost/archive/text_oarchive.hpp> #include <boost/serialization/base_object.hpp> #include <boost/serialization/utility.hpp> #include <boost/serialization/list.hpp> #include <boost/serialization/string.hpp> *class* ResData{ *friend* *class* boost::serialization::access; *friend* std::ostream& *operator*<<(std::ostream &os, const ResData& rD); *private*: std::string resName; int seqNum; int insNum; float sAS; *public*: ResData(); ResData(std::string, int, int); std::string getResName() const { *return* resName;} int getSeqNum() const { *return* seqNum;} int getInsNum() const { *return* insNum;} float getSAS() const { *return* sAS;} void setSAS(float sASP) { sAS = sASP;} *template*<*class* Archive> void serialize(Archive&, const unsigned int); }; std::ostream& *operator*<<(std::ostream& os, const ResData& rD){ *return* os << rD.getResName() << rD.getSeqNum() << rD.getInsNum() << rD.getSAS(); } int main(){ std::ofstream oFSBS("/home/Seb/Code/testData/results.dat"); boost::archive::text_oarchive oA(oFSBS); ResData temp("TEST", 1, 1); temp.setSAS(5555); oA << temp; oFSBS.close(); } I get the following error upon compilation: /usr/include/boost/archive/detail/oserializer.hpp: In function ‘void boost::archive::save(Archive&, T&) [with Archive = boost::archive::text_oarchive, T = ResData]’: /usr/include/boost/archive/basic_text_oarchive.hpp:78: instantiated from ‘void boost::archive::basic_text_oarchive<Archive>::save_override(T&, int) [with T = ResData, Archive = boost::archive::text_oarchive]’ /usr/include/boost/archive/detail/interface_oarchive.hpp:85: instantiated from ‘Archive& boost::archive::detail::interface_oarchive<Archive>::operator<<(T&) [with T = ResData, Archive = boost::archive::text_oarchive]’ test.cpp:54: instantiated from here /usr/include/boost/archive/detail/oserializer.hpp:566: error: invalid application of ‘sizeof’ to incomplete type ‘boost::STATIC_ASSERTION_FAILURE<false I am running FC4 with gcc4.0.1 thanks, Sebastien

2 3

Regex compilation failure with MSVC .NET 2002 and bjam
by Ovanes Markarian 02 Sep '05

02 Sep '05

Dear all, I am trying to build the regex library from boost 1.33 release with Visual C++ .NET 2002 and bjam. I constantly get this error (while trying to build it with ICU and without). my command line is: bjam "--with-regex" "-sTOOLS=vc7" "--prefix=E:\projects\Automation\thirdparty\boost" "--builddir=E:\projects\Automation\thirdparty\boost\build" "-sHAVE_ICU=0" "-sICU_PATH=E:\projects\Automation\thirdparty\icu\source" install I was trying to switch -sHAVE_ICU option between 0 and 1 and always got this output for regex cpp files. The error(s) is in German (I don't know why MS decided to translate C++ compiler to German, but I have no other alternative at the moment and suffer very much with it as well...). The error means: cannot form a qualified name (=Ein qualifizierter Name kann nicht gebildet werden) see reference to class template instantiation boost::re_detail::regex_iterator_traits<T>' being compiled (=Siehe Verweis auf Instantiierung der kompilierten Klassenvorlage) Full output is: vc-C++ E:\projects\Automation\thirdparty\boost\build\bin\boost\libs\regex\build\ libboost_regex.lib\vc7\release\threading-multi\icu.obj cl : Befehlszeile warning D4029 : Die Optimierung ist im Standardcompiler nicht verf?gbar. icu.cpp E:\projects\Automation\thirdparty\boost_1_33_0\boost\regex\v4\iterator_traits.hp p(34) : error C2825: 'T::iterator_category': Ein qualifizierter Name kann nicht gebildet werden E:\projects\Automation\thirdparty\boost_1_33_0\boost\regex\v4\sub_match. hpp(31) : Siehe Verweis auf Instantiierung der kompilierten Klassenvorlage 'boos t::re_detail::regex_iterator_traits<T>' with [ T=const int * ] C:\Program Files\Microsoft Visual Studio .NET\Vc7\include\vector(259) : Siehe Verweis auf Instantiierung der kompilierten Klassenvorlage 'boost::sub_mat ch<BidiIterator>' with [ BidiIterator=const int * ] E:\projects\Automation\thirdparty\boost_1_33_0\boost\regex\v4\regex_form at.hpp(34) : Siehe Verweis auf Instantiierung der kompilierten Klassenvorlage 's td::vector<_Ty,_Ax>' with [ _Ty=boost::sub_match<const int *>, _Ax=std::allocator<boost::sub_match<const int *>> ] Does someone know what is the problem and how I can fix it? With Kind Regards, Ovanes Markarian

2 2

[Test] Template specialization problems with BOOST_CHECK_EQUAL_COLLECTIONS
by Will Bryant 02 Sep '05

02 Sep '05

Hi all, I've been using Boost.Test lately and in general it's working well (thanks Gennadiy!). However, I'm having trouble with BOOST_CHECK_EQUAL_COLLECTIONS when my collections are of non-primitive types. For example, if I try: vector<wstring> test1, test2; BOOST_CHECK_EQUAL_COLLECTIONS(test1.begin(), test1.end(), test2.begin(), test2.end()); I get a compiler error along the lines of "h:\libraries\boost\boost\test\utils\wrap_stringstream.hpp(66) : error C2679: binary '<<' : no operator found which takes a right-hand operand of type 'const std::basic_string<_Elem,_Traits,_Ax>' (or there is no acceptable conversion)" (with _Elem being wchar_t in this case, and _Traits and _Ax having the usual defaults). Looking at the source I see that BOOST_CHECK_EQUAL_COLLECTIONS is using equal_coll_impl, which is creating a predicate_result and using the stream insertion operator on the wrap_stripstream returned by its message() method. wrap_stringstream has an unspecialized template which delegates to the << operator of the backing ostringstream/ostrstream: template <typename CharT, typename T> inline basic_wrap_stringstream<CharT>& operator<<( basic_wrap_stringstream<CharT>& targ, T const& t ) { targ.stream() << t; return targ; } Since that backing ostringstream descends from ostream, I would have thought that all I needed to do was to ensure that there is a operator << (ostream&, wstring const&) defined, like this: ostream& operator << (ostream& ostr, wstring const& str) { ostr << "I'd put a wstring-to-string function here instead of this constant"; return ostr; } Hower this doesn't work - although I can now compile: ostringstream oss; oss << wstring(L"test"); successfully, if I try: boost::wrap_stringstream wss; wss << wstring(L"test"); or: boost::test_tools::predicate_result res(true); res.message() << wstring(L"test"); I get the same error as above. Interestingly, if I change that << operator implementation so that it takes and returns a wrap_stringstream, instead of an ostream: boost::wrap_stringstream& operator << (boost::wrap_stringstream& ostr, const wstring& str) { ostr << "I'd put a wstring-to-string function here instead of this constant"; return ostr; } then I can compile 'wss << wstring(L"test")' and ' res.message() << wstring(L"test")' OK. This is weird because it suggests to me that that unspecialized wrap_stringstream template that delegates to the ostringstream's << isn't working properly. But weirder is that even having done that, using BOOST_CHECK_EQUAL_COLLECTIONS still produces the same compilation error, even though it's making the same operator call - I can't see why. Am I missing something here? I also tried specializing print_log_value: namespace boost { namespace test_tools { namespace tt_detail { template<> struct print_log_value<std::wstring> { void operator()(std::ostream& ostr, const std::wstring& str) { ostr << "I'd put a wstring-to-string function here instead of this constant"; } }; }}} But that didn't help either - same error. I'm primarily using Visual Studio 2005, but I have exactly the same problems under gcc 3.3.5 too. Any suggestions? Cheers, Will -- Will Bryant http://carcino.gen.nz/ will(a)core-dev.co.nz +64 21 655 443

2 2

[serialization] bug with new_cid != cid
by Sergey Skorniakov 01 Sep '05

01 Sep '05

Following code produced assert at line 444 in libs/serializatin/src/basic_iarchive with version 1.32.0, 1.33.0 and with every archive that's headers are included: #define BOOST_SERIALIZATION_DYN_LINK #include <boost/archive/polymorphic_iarchive.hpp> #include <boost/archive/polymorphic_oarchive.hpp> #include <boost/archive/polymorphic_text_iarchive.hpp> #include <boost/archive/polymorphic_text_oarchive.hpp> #include <boost/archive/polymorphic_xml_iarchive.hpp> #include <boost/archive/polymorphic_xml_oarchive.hpp> #include <boost/archive/polymorphic_binary_iarchive.hpp> #include <boost/archive/polymorphic_binary_oarchive.hpp> #include <boost/archive/xml_iarchive.hpp> #include <boost/archive/xml_oarchive.hpp> #include <boost/archive/binary_iarchive.hpp> #include <boost/archive/binary_oarchive.hpp> #include <boost/archive/text_iarchive.hpp> #include <boost/archive/text_oarchive.hpp> #include <iostream> #include <sstream> #include <boost/serialization/map.hpp> int main(int argc, char* argv[]) { std::pair<int, int> a(11, 22); std::map<int, int> b; b[0] = 0; b[-1] = -1; b[1] = 1; std::stringstream ss; { std::pair<int, int> *pa = &a; std::map<int, int> *pb = &b; boost::archive::binary_oarchive oa(ss); oa << boost::serialization::make_nvp("B1", pb); oa << boost::serialization::make_nvp("A1", pa); } std::cout << ss.str(); { std::pair<int, int> *pa = 0; std::map<int, int> *pb = 0; boost::archive::binary_iarchive ia(ss); ia >> boost::serialization::make_nvp("B1", pb); ia >> boost::serialization::make_nvp("A1", pa); delete pa; delete pb; } return 0; } Similar program without nvp's has the same problem: int main(int argc, char* argv[]) { std::pair<int, int> a(11, 22); std::map<int, int> b; b[0] = 0; b[-1] = -1; b[1] = 1; std::stringstream ss; { std::pair<int, int> * const pa = &a; std::map<int, int> * const pb = &b; boost::archive::text_oarchive oa(ss); oa << pb; oa << pa; } std::cout << ss.str(); { std::pair<int, int> *pa = 0; std::map<int, int> *pb = 0; boost::archive::text_iarchive ia(ss); ia >> pb; ia >> pa; delete pa; delete pb; } return 0; }

2 1

[boost.lambda] Problem with combining if_then_else_return and bind?
by Stuart Dootson 01 Sep '05

01 Sep '05

Hi - I've been trying to use the if_then_else_return feature of Boost.Lambda, and have run into a problem using Lambda's bind with this feature. My minimal example (at the end of the message) fails when compiled with the VC7.1 command line "cl -c -EHsc -DBAD" (the -DBAD is to compile the non-compiling code). The error message (attached as err.txt) indicates that return type deduction has failed at some point, I guess. The compiling version of the code differs from the non-compiling version by assigning the bind result to a variable. This seems to enable correct return type deduction. No other forms using lambda and bind that I've tried have exhibited this problem. So, the question is - is this a bug in Lambda or am I doing something wrong? Oh, I've also tried this with gcc 3.4.2 (Mingw version) and it behaved the same as VC7.1. Stuart Dootson #include <boost/lambda/lambda.hpp> #include <boost/lambda/bind.hpp> #include <boost/lambda/if.hpp> #include <boost/function.hpp> using namespace boost::lambda; bool Test1(char); void Fn(char c, bool b) { bool flag; #if defined(BAD) boost::function<bool(char)> fn = if_then_else_return(var(b), bind<bool>(&Test1, _1), constant(false) ) ; #else bool blah; boost::function<bool(char)> fn = if_then_else_return(var(b), var(blah)=bind(&Test1, _1), constant(false) ) ; #endif }

2 2

Thread cancellation
by Sliwa, Przemyslaw (London) 01 Sep '05

01 Sep '05

Hi, Can anyone tell me if it is possible to cancel a thread using boost.thread library? Thanks Pshemek -------------------------------------------------------- If you are not an intended recipient of this e-mail, please notify the sender, delete it and do not read, act upon, print, disclose, copy, retain or redistribute it. Click here for important additional terms relating to this e-mail. http://www.ml.com/email_terms/ --------------------------------------------------------

6 5

program_options library, options_description object copying
by Leon Mergen 01 Sep '05

01 Sep '05

Hello, Today I upgraded to boost 1.33, which broke the 'program options' part of my application. Copying of a boost::program_options::options_description is not allowed anymore, because of a const unsigned int m_line_length, defined at line 211 of <boost/program_options/options_descriptions.hpp> : ===================================================================== Compiling: Configurator.o Configurator.cpp: In member function ` boost::program_options::options_description& boost::program_options::options_description::operator=(const boost::program_options::options_description&)': Configurator.cpp:13: error: non-static const member `const unsigned int boost::program_options::options_description::m_line_length', can't use default assignment operator make: *** [Configurator.o] Error 1 ===================================================================== I wonder, why is this not allowed anymore (except the obvious answer that a const variable cannot be assigned a new value) ? What is the "new", preferred way to copy these objects ? Right now, I've fixed it by removing the const qualifier of that variable, but I can see that's not the preferred way... :) Regards, Leon Mergen

2 2

Re: [Boost-users] Problem compiling boost::iostreams - bzlib.h file not found
by Tim Taylor 01 Sep '05

01 Sep '05

Thanks for your help Jonathan. Regarding my comment on the #includes, it's just a minor stylistic point which you can take or leave. My point was just that, in my experience, common practice is to use #include <..> for files from different libraries, and #include "..." only for files from your own project. Of course the only difference is that the <> version looks for files in the include path, and the "" version first looks in the current directory and then in the include path. Using <> to include headers from other libraries is therefore *slightly* safer I guess, if only in the unlikely situation where you have a header file with the same name in the current directory; with <> you know you're using the library's own version of the header file and not your own (which would generally be the desired action unless you specifically wanted to override the library's own version). Additionally, from a readability point of view, <> makes it clear that the header is from another library. As I say, this is a minor point, and feel free to ignore it! Tim > >Message: 2 >Date: Wed, 31 Aug 2005 12:34:46 -0600 >From: "Jonathan Turkanis" <technews(a)kangaroologic.com> >Subject: Re: [Boost-users] Problem compiling boost::iostreams - > bzlib.h file notfound >To: boost-users(a)lists.boost.org >Message-ID: <df4t2b$ive$1(a)sea.gmane.org> > >Tim Taylor wrote: > > >>I have just downloaded boost 1.33.0 and am doing a bulk-standard >>install on my linux PC as per the instructions, with the command: >> >>bjam "-sTOOLS=gcc" install >> >>Nearly everything worked fine, but the iostreams library failed to >>compile, with the error in boost_1_33_0/libs/iostreams/src/bzip2.cpp: >>could not find include file "bzlib.h" >> >> > >Try defining the variable NO_BZIP2. See http://tinyurl.com/bcjuz and >http://tinyurl.com/dn6gx. > > > >>On further investigation, this file comes from the package >>libbzip2_1-devel, which also needs to be installed. >> >>An extra thought: bzip2.cpp includes this file as >>#include "bzlib.h" >>but it should really be >>#include <bzlib.h> >>as this is from a different library. >> >> > >Could you elaborate? > > > >>Tim >> >> > >Jonathan > > >

2 1

Re: [Boost-users] [statechart] Can events carry data?
by BRIDGES Dick 01 Sep '05

01 Sep '05

> -----Original Message----- > From: boost-users-bounces(a)lists.boost.org > [mailto:boost-users-bounces@lists.boost.org] On Behalf Of Peter Petrov > Sent: Tuesday, August 30, 2005 1:13 PM > To: boost-users(a)lists.boost.org > Subject: Re: [Boost-users] [statechart] Can events carry data? > > > BRIDGES Dick wrote: > > Is there any provision for "event-local" storage? I'd like > to create > > events that carry data (e.g., timestamp, source, etc.) to be used by > > reactions and transitions to update state-local storage. > > > > I didn't see anything like this in the documentation. Bad > idea? Major > > drawbacks? If it wouldn't be a problem, how might I go > about doing it? > > > struct MyEvent : public boost::statechart::event<MyEvent> > { > int myData; > double myOtherData; > MyClass myOtherOtherData; > }; > > _______________________________________________ > Boost-users mailing list > Boost-users(a)lists.boost.org > http://lists.boost.org/mailman/listinfo.cgi/boost-users > Thank you for the example. I'm still not clear on the requirements surrounding such an instance. For example, the reference requires that <code>new E(*pCE)</code> be well-formed and make "a copy of pE". Does the current implementation work ok with boost::shared_ptr? How about auto_ptr? If a data member would normally require a deep copy, would I be better off managing it external to the event object - or avoiding that type of data altogether? How many copies are we talking about here? Any cautions and/or advise regarding the use of data members in events would be appreciated. Thanks again for the response. Regards, Dick Bridges

2 2

Thread cancellation
by Chris Coleman 01 Sep '05

01 Sep '05

Hi, I know at present that the Boost Threads implementation does not provide a terminate() / cancel() function, but the documentation suggests that work is in progress to implement this feature once a safe and portable way is found. I was just wondering whether this will appear soon in future releases, or if it is likely to be some time? At present I can kill a thread internally by simply throwing an exception and not catching it. But externally I cannot. I have a thread pool server I built some time ago using the pthread API and I'm porting it to use Boost Threads. The server has add() and remove() thread methods. Within the remove function under the pthread implementation I could call pthread_cancel(thrID) and that would be that, Obviously I cant call thread.cancel() as I'd like here and was wondering if there were any simple ways to signify that a particular thread should terminate? Cheers Chris This message has been checked for viruses but the contents of an attachment may still contain software viruses, which could damage your computer system: you are advised to perform your own checks. Email communications with the University of Nottingham may be monitored as permitted by UK legislation.

9 16

Boost.Random: Some proposed fixes
by Daniel Krügler 01 Sep '05

01 Sep '05

I observed some further missing definitions of constant static members of integral type, which have been initialized in-class: 1) additive_combine.hpp Proposal: Add the following #ifndef BOOST_NO_INCLASS_MEMBER_INITIALIZATION // A definition is required even for integral static constants template<class MLCG1, class MLCG2, #ifndef BOOST_NO_DEPENDENT_TYPES_IN_TEMPLATE_VALUE_PARAMETERS typename MLCG1::result_type #else int32_t #endif val> const bool additive_combine<MLCG1, MLCG2, val>::has_fixed_range; template<class MLCG1, class MLCG2, #ifndef BOOST_NO_DEPENDENT_TYPES_IN_TEMPLATE_VALUE_PARAMETERS typename MLCG1::result_type #else int32_t #endif val> const typename additive_combine<MLCG1, MLCG2, val>::result_type additive_combine<MLCG1, MLCG2, val>::min_value; template<class MLCG1, class MLCG2, #ifndef BOOST_NO_DEPENDENT_TYPES_IN_TEMPLATE_VALUE_PARAMETERS typename MLCG1::result_type #else int32_t #endif val> const typename additive_combine<MLCG1, MLCG2, val>::result_type additive_combine<MLCG1, MLCG2, val>::max_value; #endif 2) What is actually the reason for the trailing whitespace on streaming of the class template discard_block? It seems inconsistent compared to the other outputs. 3) linear_congruential.hpp: Add missing static member definitions for linear_congruential: #ifndef BOOST_NO_INCLASS_MEMBER_INITIALIZATION ... // Other already defined constants template<class IntType, IntType a, IntType c, IntType m, IntType val> const IntType linear_congruential<IntType,a,c,m,val>::multiplier; #endif .. and for class rand48 (in its corresponding cpp, not the header): #ifndef BOOST_NO_INCLASS_MEMBER_INITIALIZATION ... // Other already defined constants const bool rand48::has_fixed_range; const int32_t rand48::min_value; const int32_t rand48::max_value #endif Greetings from Bremen, Daniel Krügler

1 0

Problem compiling boost::iostreams - bzlib.h file not found
by Tim Taylor 31 Aug '05

31 Aug '05

I have just downloaded boost 1.33.0 and am doing a bulk-standard install on my linux PC as per the instructions, with the command: bjam "-sTOOLS=gcc" install Nearly everything worked fine, but the iostreams library failed to compile, with the error in boost_1_33_0/libs/iostreams/src/bzip2.cpp: could not find include file "bzlib.h" On further investigation, this file comes from the package libbzip2_1-devel, which also needs to be installed. An extra thought: bzip2.cpp includes this file as #include "bzlib.h" but it should really be #include <bzlib.h> as this is from a different library. Tim

2 1

boost::lambda::bind operator = std::vector sucess, bnu::vector and std::valarray fail
by pviallet＠yahoo.fr 31 Aug '05

31 Aug '05

I’m just starting to use boost::lambda an boost::lambda::bind, and I do not understand why this do not work whith bnuy::vector && std::valarray : class CToto{ public: CToto(double _i): a(_i) {} CToto(): a(0.0) {} double get() const {return a;} private: double a; }; std::vector<std::CToto *> aTotoPtrVect; aTotoPtrVect.push_back(new std::CToto(1.1)); aTotoPtrVect.push_back(new std::CToto(2.2)); aTotoPtrVect.push_back(new std::CToto(3.3)); aTotoPtrVect.push_back(new std::CToto(4.4)); //case 1 std::vector <double> dv(std::distance((aTotoVect.begin(), aTotoVect.end()); std::for_each(aTotoPtrVect.begin(), aTotoPtrVect.end(), bll::var(dv)[bll::var(uiIdx)++] = bll::bind(&CToto::get, bll::_1)); // work fine //case 2 double d(4) std::for_each(aTotoPtrVect.begin(), aTotoPtrVect.end(), bll::var(d)[bll::var(uiIdx)++] = bll::bind(&CToto::get, bll::_1)); // work fine //case 3 std::valaray <double> dvv(std::distance((aTotoVect.begin(), aTotoVect.end()); std::for_each(aTotoPtrVect.begin(), aTotoPtrVect.end(), bll::var(dvv)[bll::var(uiIdx)++] = bll::bind(&CToto::get, bll::_1)); // do not compile //case 4 bnu::vector<double> bvv(std::distance((aTotoVect.begin(), aTotoVect.end()); std::for_each(aTotoPtrVect.begin(), aTotoPtrVect.end(), bll::var(bvv)[bll::var(uiIdx)++] = bll::bind(&CToto::get, bll::_1)); // do not compile Is someone could explain me why it work in 1 and 2 ?

1 0

boost::date_time GMT/UTC question
by Leon Mergen 31 Aug '05

31 Aug '05

Hello, Simple/quick question: is boost::posix_time::ptime boost::posix_time::second_clock::universal_time(), which is described as UTC in the boost manual page, equal to GMT? If not, what is the difference between UTC and GMT? As I understood it, UTC is the "new" name for GMT, but I'm not sure. Regards, Leon

2 3

Re: [Boost-users] Boost-users] boost::date_time GMT/UTC question
by Christopher Hunt 31 Aug '05

31 Aug '05

Sorry about my previous post - I don't know quite what happened but it didn't include the intended response. What I meant to state was that for most applications, UTC and GMT can be regarded as the same. Here's a good explanation on UTC: http://en.wikipedia.org/wiki/Utc Cheers, -C

1 0

Re: [Boost-users] Regex boost 1.33 - (mingw/w32) linking
by Arno Mauhourat 31 Aug '05

31 Aug '05

> Well there's something wrong at your end, because it works for me: > > cd libs/regex/example/grep > g++ -I../../../.. -c -o grep.o grep.cpp > g++ -o grep.exe grep.o > 'C:\data\boost\develop\boost\bin\boost\libs\regex\build\libboost_regex.lib\mingw\debug\threading-multi\libboost_regex-mgw-mt-d-1_33.lib' > 'C:\data\boost\develop\boost\bin\boost\libs\program_options\build\libboost_program_options.lib\mingw\debug\threading-multi\libboost_program_options-mgw-mt-d-1_33.lib' > -g3 > > compiles and links cleanly with the current MinGW release. > > John. > Thanks John, for your time and quick answers. I found the issue: I compiled "grep.cpp" with -O3 and this leads to: - error at linking on debug version of the library (libboost_regex-mgw-mt-d-1_33.lib) - OK linking with non-debug version (libboost_regex-mgw-mt-1_33.lib) I am quite unfamiliar with g++ (and it is quite off topic here) but seems strange to me that an optimization level ruins a linking... Arno

2 1

Re: [Boost-users] Boost::multiIndex container problems
by JOAQUIN LOPEZ MU?Z 31 Aug '05

31 Aug '05

> I tried putting the boost::multi_index::member<> in bare and it > resulted in > the error, regardless of if I hit 'build' or 'rebuild' solution. Weird!! I'd be greateful if you could pursue this a little more. The macro looks like (the second branch is that matters): #if defined(BOOST_NO_POINTER_TO_MEMBER_TEMPLATE_PARAMETERS) #define BOOST_MULTI_INDEX_MEMBER(Class,Type,MemberName) \ ::boost::multi_index::member_offset<Class,Type,offsetof (Class,MemberName)> #else #define BOOST_MULTI_INDEX_MEMBER(Class,Type,MemberName) \ ::boost::multi_index::member<Class,Type,&Class::MemberName> #endif The only difference with the bare member call I can see is the full qualification, with a beginning :: included. Could you see if this makes any difference? Thanks! Joaquín M López Muñoz Telefónica, Investigación y Desarrollo

3 2

undefined symbols in the interval library
by Matei Stroila 31 Aug '05

31 Aug '05

Using Visual Studio 7.1 and boost_1_33_0, I am getting the following undefined symbol while trying to run an application that uses the interval_lib: error LNK2019: unresolved external symbol _rint referenced in function "public: static double __cdecl boost::numeric::interval_lib::detail::x86_rounding::to_int(double const &)" (?to_int@x86_rounding@detail@interval_lib@numeric@boost@@SANABN@Z) On the other hand, the same code is compiled and runs fine on my powerbook (gcc and the boost same library version). Thanks for help, Matei

2 1

Seg fault when using serialization library
by Sebastien Gerega 31 Aug '05

31 Aug '05

I am running FC4 with gcc4.0.1 and I installed boost-devel using yum. When I compile with gcc and run the serialization example located at http://www.boost.org/libs/serialization/example/demo.cpp I have no problems. However, the project I am working on requires that I use compatgcc32 for compilation. When I compile with gcc32 and run the same example I get the following output with a seg fault: original schedule 6:24 bob 0x0x8ede5b8 34\uffff135'52.56" 134\uffff22'78.3" 24th Street and 10th Avenue 0x0x8ede5e0 35\uffff137'23.456" 133\uffff35'54.12" State street and Cathedral Vista Lane 0x0x8edeb50 35\uffff136'15.456" 133\uffff32'15.3" White House 9:57 bob 0x0x8ede5b8 34\uffff135'52.56" 134\uffff22'78.3" 24th Street and 10th Avenue 0x0x8ede5e0 35\uffff137'23.456" 133\uffff35'54.12" State street and Cathedral Vista Lane 0x0x8edeb50 35\uffff136'15.456" 133\uffff32'15.3" White House 11:2 alice 0x0x8ede5b8 34\uffff135'52.56" 134\uffff22'78.3" 24th Street and 10th Avenue 0x0x8ede5e0 35\uffff137'23.456" 133\uffff35'54.12" State street and Cathedral Vista Lane 0x0x8edeb50 35\uffff136'15.456" 133\uffff32'15.3" White House 7:17 ted 0x0x8edeb78 35\uffff134'48.789" 133\uffff32'16.23" Lincoln Memorial 0x0x8edeb50 35\uffff136'15.456" 133\uffff32'15.3" White House 0x0x8ede5e0 35\uffff137'23.456" 133\uffff35'54.12" State street and Cathedral Vista Lane 9:38 ted 0x0x8edeb78 35\uffff134'48.789" 133\uffff32'16.23" Lincoln Memorial 0x0x8edeb50 35\uffff136'15.456" 133\uffff32'15.3" White House 0x0x8ede5e0 35\uffff137'23.456" 133\uffff35'54.12" State street and Cathedral Vista Lane 11:47 alice 0x0x8edeb78 35\uffff134'48.789" 133\uffff32'16.23" Lincoln Memorial 0x0x8edeb50 35\uffff136'15.456" 133\uffff32'15.3" White House Segmentation fault I am guessing this is because of different compilers being used or different versions of libstdc++ being required but I am able to compile and run examples using other Boost libraries without problems. Is there any way around this? thanks, Sebastien Gerega

2 3

Re: [Boost-users] Boost-users] boost::date_time GMT/UTC question
by Christopher Hunt 31 Aug '05

31 Aug '05

On 31/08/2005, at 8:07 AM, boost-users-request(a)lists.boost.org wrote: > Simple/quick question: is boost::posix_time::ptime > boost::posix_time::second_clock::universal_time(), which is > described as > UTC in the boost manual page, equal to GMT? If not, what is the > difference between UTC and GMT? > > As I understood it, UTC is the "new" name for GMT, but I'm not sure. * * * Showpiece your Palm device and instantly access world times using our beautiful 3 dimensional globe http://www.classactionpl.com/

1 0

boost::thread state check
by Ovanes Markarian 30 Aug '05

30 Aug '05

Can someone please provide an example how one can test if a started thread is still running or is done? With Kind Regards, Ovanes Markarian

2 3

Re: [Boost-users] Boost::multiIndex container problems
by JOAQUIN LOPEZ MU?Z 30 Aug '05

30 Aug '05

2 1

[statechart] Can events carry data?
by BRIDGES Dick 30 Aug '05

30 Aug '05

Is there any provision for "event-local" storage? I'd like to create events that carry data (e.g., timestamp, source, etc.) to be used by reactions and transitions to update state-local storage. I didn't see anything like this in the documentation. Bad idea? Major drawbacks? If it wouldn't be a problem, how might I go about doing it? Regards, Dick Bridges

2 1

function object wrapper problem
by Okko Willeboordse 30 Aug '05

30 Aug '05

I have a class that has a constructor that takes a Boost function object wrapper; class some_class { public: some_class(const boost::function1<wchar_t*, short*>& some_member) .... I call the constructor with a member function using Boost bind. some_class some_object(boost::bind(&some_other_class::some_member, &some_other_object, _1)); Now I want to use some_class for some_member functions that return an other type pointer. So I do class some_class { public: template <class T> some_class(const boost::function1<T*, short*>& get_member) .... But now the compiler (VS 2003) starts complaining; error C2664: 'some_class::some_class(const some_class &)' : cannot convert parameter 1 from 'boost::_bi::bind_t<R,F,L>' to 'const some_class &' with [ R=wchar_t *, F=boost::_mfi::mf1<wchar_t *,some_other_class,short *>, L=boost::_bi::list2<boost::_bi::list_av_2<some_other_class *__w64 ,boost::arg<1>>::B1,boost::_bi::list_av_2<some_other_class *__w64 ,boost::arg<1>>::B2> ] Reason: cannot convert from 'boost::_bi::bind_t<R,F,L>' to 'const some_class' with [ R=wchar_t *, F=boost::_mfi::mf1<wchar_t *,some_other_class,short *>, L=boost::_bi::list2<boost::_bi::list_av_2<some_other_class *__w64 ,boost::arg<1>>::B1,boost::_bi::list_av_2<some_other_class *__w64 ,boost::arg<1>>::B2> ] No constructor could take the source type, or constructor overload resolution was ambiguous Any ideas? Many thanks, Okko Willeboordse

3 4

bind's bind vs lambda's bind
by Jean-Louis Leroy 30 Aug '05

30 Aug '05

I see two "bind" adapters in Boost 1.32: one from bind and one from lambda. Although they seem to have the same interface, each seems to have its own implementation. In effect, "using namespace boost; using namespace boost::lambda;" doesn't work. What's the story here? Are they going to merge someday? Is one a full superset of the other, or better implemented (and I should stick to that one)? Do you have suggestions about handling this? TIA... -- Jean-Louis Leroy Sound Object Logic http://www.soundobjectlogic.com

6 13

Re: [Boost-users] Boost.Thread memory leak reported
by Sohail Somani 30 Aug '05

30 Aug '05

> -----Original Message----- > From: boost-users-bounces(a)lists.boost.org > [mailto:boost-users-bounces@lists.boost.org] On Behalf Of Peter Dimov > Sent: Friday, August 26, 2005 1:27 PM > To: boost-users(a)lists.boost.org > Subject: Re: [Boost-users] Boost.Thread memory leak reported > > > Sohail Somani wrote: > > >> Christian Henning wrote: > >> > >>> But Peter, we do agree that there is problem and it should > >> be fixed, > >>> dont't we? > >> > >> I see no problems in the code. > > > > Any dynamically allocated memory that isn't freed is a Bad > Thing imho. > > Because? Was it forgotten? Was it intentional? If the assumption is it will always be freed, then there is no ambiguity.

7 13

Boost.Wave compilation taking forever
by François Duranleau 30 Aug '05

30 Aug '05

I recently downloaded the source for Boost 1.33.0 and tried to compile and install it, but I hit a problem when compiling Boost.Wave: the compilation time for the file $BOOST_ROOT/libs/wave/src/instantiate_cpp_literalgrs.cpp seems to take forever (after 4 days, the compiler was still running hard, no output). Is that normal? It is mentioned in the documentation that without separate compilation, compiling a program using Boost.Wave can take up to an hour (depending on your system configuration), so I guess compiling the library could take a long time as well, but days!?! For reference, here is my compilation command: cd $BOOST_ROOT bjam --prefix=$SOMEWHERE --builddir=build --with-python-root=/usr \ "-sTOOLS=gcc" "-sBUILD=release <optimization>speed \ <runtime-link>dynamic <threading>multi" \ "-sPYTHON_VERSION=2.3" install The platform is x86_64 running GNU/Linux, kernel 2.6.10-1.771_FC2 (from Fedora Core 2). Compiler version is g++ (GCC) 3.3.3 20040412 (Red Hat Linux 3.3.3-7). -- Francois

4 4

Boost.Archive: Infinite recursion in dinkumware.hpp
by Daniel Krügler 30 Aug '05

30 Aug '05

The streaming inserter of Boost archive's dinkumware.hpp for boost::int64_t causes indefinite recursion in case of negative arguments. I think the following line inside the else clause should be changed from os << -t; to os << static_cast<boost::uint64_t>(-t); Greetings from Bremen, Daniel

2 4

Re: [Boost-users] incorrect random library equality implementation?
by Steven Solie 30 Aug '05

30 Aug '05

Scott McMurray wrote: > > The std::equal() call is comparing an array of doubles using > > operator == which I thought was impossible for floating point types > > due to their inexact nature et al. > > A (radix 2) floating-point number will never be exactly equal to one > seventh, for example, because it's not representable. The other issue > is that roundoff error will make things such as 1./3*3 not result in > exactly 1. > > That doesn't mean that you can't compare between them for equality. > If one float is a copy of another, then they should be bitwise equal. > Also, floating-point operations are deterministic, so the same > sequence of operations -- in exactly the same environment -- should > also yeild bitwise equal results. What the random streaming operators are doing is saving and restoring the state of the lagged_fibonacci607 object with text. This involves converting the doubles into strings and back again. I'm not certain if ISO C++ specifies whether we are allowed to assume the conversion from double to string and back always yields the identical floating point number or not. Here is a small test program that demonstrates what the random test suite is essentially doing: #include <iostream> #include <sstream> int main() { double pi = 3.14159; double pi2 = pi; if ( pi != pi2 ) { std::cout << "test failed, pi != pi2\n"; return -1; } std::ostringstream file; file << pi; std::string ostr(file.str()); std::istringstream input(file.str()); input >> pi; std::string istr(input.str()); if ( pi != pi2 ) { std::cout << "test failed, restored pi != pi2\n"; } else { std::cout << "passed\n"; } } This test always fails here. --Steven

1 0

[Random] Improved initialisation for mersenne_twister
by Richard Jennings 30 Aug '05

30 Aug '05

With Boost 1.33 the release notes say that there is improved initialisation for mersenne_twister. Does this mean that the pseudo-random sequence from the same seed will be different with Boost 1.33 to Boost 1.32? The reason I ask is that I use the random sequence to add noise to a signal and check how my algorithm handles it. As it's pseudo-random noise I can expect the same result each time and test for that expected result. It appears that with Boost 1.33 the results are very subtly different. That's fine, but I want to be clear that it's due to a change in the pseudo-random sequence (if it is) rather than some other regression. Richard

1 0

simple compile
by Martin Cavanagh 30 Aug '05

30 Aug '05

Hi everyone. I want to show my extreme newbieness. I can't compile the BASIC thread examples. I get lots of link errors http://www-eleves-isia.cma.fr/documentation/BoostDoc/boost_1_29_0/libs/thre… I'm running Windows XP SP2 with mingw (which compiles everything else in my project fine g++ -IC:/Boost/include/boost-1_32 -LC:/Boost/lib -lboost_thread-mgw-mt thread_test.cpp It definitely finds the library (when i miss type it it throws a different error) C:/DOKUME~1/Marty/LOKALE~1/Temp/cc8Yaaaa.o(.text+0x1ce): In function `main': c:/webcam/thread_test.cpp:27: undefined reference to `_imp___ZN5boost6threadC1ERKNS_9function0IvSaINS_13function_baseEEEE' C:/DOKUME~1/Marty/LOKALE~1/Temp/cc8Yaaaa.o(.text+0x235):c:/webcam/thread_test.cpp:28: undefined reference to `_imp___ZN5boost6thread4joinEv' C:/DOKUME~1/Marty/LOKALE~1/Temp/cc8Yaaaa.o(.text+0x26b):c:/webcam/thread_test.cpp:28: undefined reference to `_imp___ZN5boost6threadD1Ev' C:/DOKUME~1/Marty/LOKALE~1/Temp/cc8Yaaaa.o(.text+0x2a0):c:/webcam/thread_test.cpp:28: undefined reference to `_imp___ZN5boost6threadD1Ev' C:/DOKUME~1/Marty/LOKALE~1/Temp/cc8Yaaaa.o(.text$_ZN12thread_alarmclEv[thread_alarm::operator()()]+0x15): In function `ZN9__gnu_cxx13new_allocatorI12thread_alarmE7destroyEPS1_': c:/msys/MinGW/bin/../lib/gcc/mingw32/3.4.2/../../../../include/c++/3.4.2/ext/new_allocator.h: undefined reference to `_imp___ZN5boost9xtime_getEPNS_5xtimeEi' C:/DOKUME~1/Marty/LOKALE~1/Temp/cc8Yaaaa.o(.text$_ZN12thread_alarmclEv[thread_alarm::operator()()]+0x36):c:/msys/MinGW/bin/../lib/gcc/mingw32/3.4.2/../../../../include/c++/3.4.2/ext/new_allocator.h: undefined reference to `_imp___ZN5boost6thread5sleepERKNS_5xtimeE' collect2: ld returned 1 exit status But when I run it as 2 commands: g++ -IC:/Boost/include/boost-1_32 thread_test.cpp -o thread_test.o -c g++ -LC:/Boost/lib -o manual_test thread_test.o -lboost_thread-mgw-mt It compiles perfectly, no warnings or anything $ manual_test.exe setting alarm for 5 seconds... alarm sounded... is there some rule, for producing executables from librarys, that the linking stage must be seperate???? Thanks Martin Send instant messages to your online friends http://au.messenger.yahoo.com

3 2

Re: [Boost-users] Thread cancellation
by Sliwa, Przemyslaw (London) 30 Aug '05

30 Aug '05

Zthread looks promising but there is no documentation at all. In addition there is no mailing list. Pshemek -----Original Message----- From: boost-users-bounces(a)lists.boost.org [mailto:boost-users-bounces@lists.boost.org] On Behalf Of Charles BROSSOLLET Sent: 30 August 2005 12:52 To: boost-users(a)lists.boost.org Subject: Re: [Boost-users] Thread cancellation The ZThreads library supports thread cancellation, but I haven't tried it. Does anyone who have an experience with both libraries could share what he thinks of each one? Regards -- Charles ----- Original Message ----- From: Janusz Piwowarski To: boost-users(a)lists.boost.org Sent: Tuesday, August 30, 2005 11:52 AM Subject: Re: [Boost-users] Thread cancellation Sliwa, Przemyslaw (London) wrote: > Can anyone tell me if it is possible to cancel a thread using > boost.thread library? Form Boost.Thread FAQ: Q: Why isn't thread cancellation or termination provided? A: There's a valid need for thread termination, so at some point Boost.Threads probably will include it, but only after we can find a truly safe (and portable) mechanism for this concept. Regards, -- Janusz _______________________________________________ Boost-users mailing list Boost-users(a)lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users -------------------------------------------------------- If you are not an intended recipient of this e-mail, please notify the sender, delete it and do not read, act upon, print, disclose, copy, retain or redistribute it. Click here for important additional terms relating to this e-mail. http://www.ml.com/email_terms/ --------------------------------------------------------

1 0

Boost.Signals: Suspicious workaround tests
by Daniel Krügler 30 Aug '05

30 Aug '05

Yesterday I stumbled about the following tests in boost 1.33: In signals/detail/named_slot_map.hpp: class named_slot_map_iterator { .. #if BOOST_WORKAROUND(_MSC_VER, <= 0x1701) ... }; In signals/signal_template.hpp class BOOST_SIGNALS_SIGNAL { ... #if BOOST_WORKAROUND(BOOST_MSVC, <= 0x1700) ... }; Are these tests really correct?? I am wondering because _MSC_VER has the following values (decimal!!) VC6: 1200 VC7: 1300 VC7.1: 1310 which does not fit to those hexadecimal values, which would correspond to version number 5888 and 5889 (!). I know that boost coworkers often have good contacts to compiler providers, but that good ... ;-)) Greetings from Bremen, Daniel Krügler

2 1

[assign] Some basic questions (lengthy code example)
by Ames Andreas 30 Aug '05

30 Aug '05

Hi all, I could use some advice regarding this lengthy code example: ---------- <code> ------------ #include <vector> #include <map> #include <boost/function.hpp> #include <boost/assign.hpp> struct E1 {}; struct E2 {}; enum State { eS1 = 1, eS2 }; typedef boost::function< bool (const E1 &, int) > function0_t; typedef boost::function< bool (const E2 &, int) > function1_t; struct Functions { // Functions(std::vector< function0_t > af0 , std::vector< function1_t > af1) // : f0(af0) , f1(af1) // { // } std::vector< function0_t > f0; std::vector< function1_t > f1; }; struct Handler1 { bool operator()(const E1&, int) {return true;} }; struct Handler1a { bool operator()(const E1&, int) {return true;} }; struct Handler2 { bool operator()(const E2&, int) {return true;} }; typedef std::map< State, Functions > InitDesc; using namespace boost::assign; int main() { // [1] this works just fine Functions f1 = { list_of(Handler1()), list_of(Handler2())}; // [2] this doesn't work cause Handler1 and Handler1a have different types Functions f2 = { list_of(Handler1())(Handler1a()), list_of(Handler2())}; // [3] don't know how to do this InitDesc desc = map_list_of(eS1, {list_of(Handler1()), list_of(Handler2())}) (eS2, {list_of(Handler1a()), list_of(Handler2())}); } ---------- </code> ------------ The places marked with [1], [2] and [3] are of special interest for me. I like [1] very much thanks to what bost::assign offers me. Unfortunately I can get [2] only to work, if I explicitly create instances of function0_t from Handler1 and Handler1a. Are there more elegant ways to make this work? [3] is obviously broken, but I don't know how to come up with a similarly compact way to initialise an InitDesc instance. I can uncomment Funtions' constructor above and call it explicitely with what I've written into curly braces but that unfortunately breaks [1] (because Functions is no longer aggregate then). Is there a better way to do it prefarably without breaking [1]? TIA, aa -- Andreas Ames | Programmer | Comergo GmbH | Voice: +49 69 7505 3213 | andreas . ames AT comergo . com

1 0

Re: [Boost-users] Regex boost 1.33 - (mingw/w32) linking
by Arno Mauhourat 30 Aug '05

30 Aug '05

2 1

Compilation with comeau
by pisalmon＠numericable.fr 30 Aug '05

30 Aug '05

Hi I have some problem to compile boost 1.32 with comeau. I use como 4.33 + gcc 3.3.5 on Linux Ubuntu. During the comilation I have some error : ...found 4271 targets... ...updating 489 targets... como-C++-action bin/boost/libs/test/build/libboost_prg_exec_monitor.so/como/debug/execution_monitor.o Comeau C/C++ 4.3.3 (Oct 24 2003 16:00:23) for RedHat_LINUX_INTEL_ELF Copyright 1988-2003 Comeau Computing. All rights reserved. MODE:non-strict warnings C++ "/home/pierre/ressource/boost_1_32_0/boost/test/detail/basic_cstring/bcs_char_traits.hpp", line 64: error: namespace "std" has no member "size_t" static int compare( const_char* cstr1, const_char* cstr2, std::size_t n ) ^ "/home/pierre/ressource/boost_1_32_0/boost/test/detail/basic_cstring/bcs_char_traits.hpp", line 77: error: namespace "std" has no member "size_t" static std::size_t length( const_char* cstr ) ^ "/home/pierre/ressource/boost_1_32_0/boost/test/detail/basic_cstring/bcs_char_traits.hpp", line 88: error: namespace "std" has no member "size_t" static const_char* find( const_char* s, std::size_t n, CharT c ) ^ "/home/pierre/ressource/boost_1_32_0/boost/test/detail/basic_cstring/basic_cstring.hpp", line 47: error: namespace "std" has no member "size_t" typedef std::size_t size_type; ^ "/home/pierre/ressource/boost_1_32_0/boost/test/detail/basic_cstring/basic_cstring.hpp", line 48: error: namespace "std" has no member "ptrdiff_t" typedef std::ptrdiff_t difference_type; ^ "/home/pierre/ressource/boost_1_32_0/libs/test/build/../src/execution_monitor.cpp", line 92: error: namespace "std" has no member "size_t" const std::size_t REPORT_ERROR_BUFFER_SIZE = 512; ^ "/home/pierre/ressource/boost_1_32_0/libs/test/build/../src/execution_monitor.cpp", line 301: error: identifier "sigjmp_buf" is undefined static sigjmp_buf& jump_buffer() ^ "/home/pierre/ressource/boost_1_32_0/libs/test/build/../src/execution_monitor.cpp", line 310: error: incomplete type is not allowed struct sigaction m_same_action_for_all_signals; ^ "/home/pierre/ressource/boost_1_32_0/libs/test/build/../src/execution_monitor.cpp", line 311: error: incomplete type is not allowed struct sigaction m_old_SIGFPE_action; ^ "/home/pierre/ressource/boost_1_32_0/libs/test/build/../src/execution_monitor.cpp", line 312: error: incomplete type is not allowed struct sigaction m_old_SIGTRAP_action; ^ "/home/pierre/ressource/boost_1_32_0/libs/test/build/../src/execution_monitor.cpp", line 313: error: incomplete type is not allowed struct sigaction m_old_SIGSEGV_action; ^ "/home/pierre/ressource/boost_1_32_0/libs/test/build/../src/execution_monitor.cpp", line 314: error: incomplete type is not allowed struct sigaction m_old_SIGBUS_action; ^ "/home/pierre/ressource/boost_1_32_0/libs/test/build/../src/execution_monitor.cpp", line 315: error: incomplete type is not allowed struct sigaction m_old_SIGABRT_action; ^ "/home/pierre/ressource/boost_1_32_0/libs/test/build/../src/execution_monitor.cpp", line 316: error: incomplete type is not allowed struct sigaction m_old_SIGALRM_action; ^ "/home/pierre/ressource/boost_1_32_0/libs/test/build/../src/execution_monitor.cpp", line 318: error: identifier "sigjmp_buf" is undefined sigjmp_buf m_sigjmp_buf; ^ "/home/pierre/ressource/boost_1_32_0/libs/test/build/../src/execution_monitor.cpp", line 335: error: identifier "siglongjmp" is undefined siglongjmp( signal_handler::jump_buffer(), sig ); ^ "/home/pierre/ressource/boost_1_32_0/libs/test/build/../src/execution_monitor.cpp", line 352: error: identifier "sigemptyset" is undefined sigemptyset( &m_same_action_for_all_signals.sa_mask ); ^ "/home/pierre/ressource/boost_1_32_0/libs/test/build/../src/execution_monitor.cpp", line 356: error: incomplete type is not allowed sigaction( SIGFPE , &m_same_action_for_all_signals, &m_old_SIGFPE_action ); ^ "/home/pierre/ressource/boost_1_32_0/libs/test/build/../src/execution_monitor.cpp", line 356: error: expected a ")" sigaction( SIGFPE , &m_same_action_for_all_signals, &m_old_SIGFPE_action ); ^ "/home/pierre/ressource/boost_1_32_0/libs/test/build/../src/execution_monitor.cpp", line 357: error: incomplete type is not allowed sigaction( SIGTRAP, &m_same_action_for_all_signals, &m_old_SIGTRAP_action ); ^ "/home/pierre/ressource/boost_1_32_0/libs/test/build/../src/execution_monitor.cpp", line 357: error: expected a ")" sigaction( SIGTRAP, &m_same_action_for_all_signals, &m_old_SIGTRAP_action ); ^ "/home/pierre/ressource/boost_1_32_0/libs/test/build/../src/execution_monitor.cpp", line 358: error: incomplete type is not allowed sigaction( SIGSEGV, &m_same_action_for_all_signals, &m_old_SIGSEGV_action ); ^ "/home/pierre/ressource/boost_1_32_0/libs/test/build/../src/execution_monitor.cpp", line 358: error: expected a ")" sigaction( SIGSEGV, &m_same_action_for_all_signals, &m_old_SIGSEGV_action ); ^ "/home/pierre/ressource/boost_1_32_0/libs/test/build/../src/execution_monitor.cpp", line 359: error: incomplete type is not allowed sigaction( SIGBUS , &m_same_action_for_all_signals, &m_old_SIGBUS_action ); ^ "/home/pierre/ressource/boost_1_32_0/libs/test/build/../src/execution_monitor.cpp", line 359: error: expected a ")" sigaction( SIGBUS , &m_same_action_for_all_signals, &m_old_SIGBUS_action ); ^ "/home/pierre/ressource/boost_1_32_0/libs/test/build/../src/execution_monitor.cpp", line 360: error: incomplete type is not allowed sigaction( SIGABRT, &m_same_action_for_all_signals, &m_old_SIGABRT_action ); ^ "/home/pierre/ressource/boost_1_32_0/libs/test/build/../src/execution_monitor.cpp", line 360: error: expected a ")" sigaction( SIGABRT, &m_same_action_for_all_signals, &m_old_SIGABRT_action ); ^ "/home/pierre/ressource/boost_1_32_0/libs/test/build/../src/execution_monitor.cpp", line 364: error: incomplete type is not allowed sigaction( SIGALRM , &m_same_action_for_all_signals, &m_old_SIGALRM_action ); ^ "/home/pierre/ressource/boost_1_32_0/libs/test/build/../src/execution_monitor.cpp", line 364: error: expected a ")" sigaction( SIGALRM , &m_same_action_for_all_signals, &m_old_SIGALRM_action ); ^ "/home/pierre/ressource/boost_1_32_0/libs/test/build/../src/execution_monitor.cpp", line 379: error: incomplete type is not allowed sigaction( SIGALRM, &m_old_SIGALRM_action, sigaction_ptr() ); ^ "/home/pierre/ressource/boost_1_32_0/libs/test/build/../src/execution_monitor.cpp", line 379: error: expected a ")" sigaction( SIGALRM, &m_old_SIGALRM_action, sigaction_ptr() ); ^ "/home/pierre/ressource/boost_1_32_0/libs/test/build/../src/execution_monitor.cpp", line 383: error: incomplete type is not allowed sigaction( SIGFPE , &m_old_SIGFPE_action , sigaction_ptr() ); ^ "/home/pierre/ressource/boost_1_32_0/libs/test/build/../src/execution_monitor.cpp", line 383: error: expected a ")" sigaction( SIGFPE , &m_old_SIGFPE_action , sigaction_ptr() ); apparently, como don't find some type in std but i use libcomo and is correctly installed. If you have some idea Best regards

1 0

Boost.Random: Missing definitions of to static constants
by Daniel Krügler 30 Aug '05

30 Aug '05

The class template xor_combine<> from xor_combine.hpp declares 3 static constant members has_fixed_range (bool), shift1 (int), and shift2 (int), but **defines** only has_fixed_range. I propose, that proper definitions for shift1 and shift2 should be provided in the already existing BOOST_NO_INCLASS_MEMBER_INITIALIZATION block, too. Greetings from Bremen, Daniel Krügler

1 0

incorrect random library equality implementation?
by Steven Solie 30 Aug '05

30 Aug '05

The Boost 1.33.0 random library equality operators seem to be implemented incorrectly. For example, in file random/lagged_fibonacci.hpp starting at line 390 we have the following: friend bool operator==(const lagged_fibonacci_01& x, const lagged_fibonacci_01& y) { return x.i == y.i && std::equal(x.x, x.x+long_lag, y.x); } The std::equal() call is comparing an array of doubles using operator == which I thought was impossible for floating point types due to their inexact nature et al. This is causing all the test cases using floating point types to fail on AmigaOS with GCC 3.4.4. Is this an implementation error or am I missing something? --Steven

2 1

boost::thread waiting problem
by Ovanes Markarian 30 Aug '05

30 Aug '05

Hello, I have the following scenario: Evaluate String Stream until a certain string is found or a time has occured. The string evaluation is made not in a single function, but using a stream iterator and later an evaluator of the retrieved data. I have an iterator class as function object where a boost::shared_ptr<boost::timed_mutex> mutex; member is defined. It has 2 functions: operator()() which is a worker function of the time_out thread and an iteratorion function. Now I start when entered for the first time the iteration function the time_out thread. The time_out thread should block until the time_out elapses or the another function has found the desired string from the stream. my code looks like: operator()() { boost::timed_mutex::scoped_timed_lock lock(*mutex, true); boost::condition c; boost::xtime xt; boost::xtime_get(&xt, boost::TIME_UTC); xt.sec +=20; c.timed_wait(lock, xt); } My approach was to use the mutex object for syncronization. I assumed that it is locked as long as c.timed_wait(...) is waiting. So I try to lock this object in the other thread. If the mutex object can not be locked the worker thread is still waiting, otherwise time_out elapsed. >From the Rationale section of the thread docs I heavily understand which locking strategy is used for timed_mutex. Can someone point me to a the correct place with documentation and say if this approach will work or I should consider a redesign? With Kind Regards, Ovanes Markarian

1 0

Re: [Boost-users] [boost::bind] How use with fn objects?
by BRIDGES Dick 30 Aug '05

30 Aug '05

> -----Original Message----- > From: boost-users-bounces(a)lists.boost.org [mailto:boost-users- > bounces(a)lists.boost.org] On Behalf Of Rene Rivera > Sent: Monday, August 29, 2005 12:30 PM > To: boost-users(a)lists.boost.org > Subject: Re: [Boost-users] [boost::bind] How use with fn objects? > > BRIDGES Dick wrote: [snip] > > I'm trying to pass a function object that takes no > > parameters to a boost::thread constructor and cannot > > get it right. [snip] > Either: > > int > main( int argc, char **argv ) { > Foo f; > boost::thread doit( boost:bind(Foo::operator(),&f)() ); > doit.join(); > return 0; > } > > Or: > > int > main( int argc, char **argv ) { > Foo f; > boost::thread doit( f ); > doit.join(); > return 0; > } > > Should work. > > > -- > -- Grafik - Don't Assume Anything > -- Redshift Software, Inc. - http://redshift-software.com > -- rrivera/acm.org - grafik/redshift-software.com > -- 102708583/icq - grafikrobot/aim - Grafik/jabber.org After I figured out I had to use boost::ref(f) with my real class, the second form worked fine. I had a problem with the first form though. <code> boost::thread doit( boost::bind(Foo::operator(),&f)() ); </code> Yielded the following [edited to fit] result: <result> g++ -D_REENTRANT -I/usr/local -I/usr/local/boost_1_33_0 -I/usr/local/include -O0 -g3 -Wall -c -fmessage-length=0 -Wno-non-virtual-dtor -omain.o ../main.cpp ../main.cpp: In function `int main(int, char**)': ../main.cpp:22: error: invalid use of non-static member function `void my_namespace::Foo::operator()()' /usr/local/boost_1_33_0/boost/bind.hpp: At global scope: /usr/local/boost_1_33_0/boost/bind.hpp: In instantiation of `boost::_bi::result_traits<boost::_bi::unspecified, void (my_namespace::Foo::)()>': /usr/local/boost_1_33_0/boost/bind/bind_template.hpp:15: instantiated from `boost::_bi::bind_t<boost::_bi::unspecified, void (my_namespace::Foo::)(), boost::_bi::list1<boost::_bi::value<my_namespace::Foo*> > >' ../main.cpp:22: instantiated from here /usr/local/boost_1_33_0/boost/bind.hpp:63: error: `void (my_namespace::Foo::)()' is not a class, struct, or union type /usr/local/boost_1_33_0/boost/bind/bind_template.hpp: In instantiation of `boost::_bi::bind_t<boost::_bi::unspecified, void (my_namespace::Foo::)(), boost::_bi::list1<boost::_bi::value<my_namespace::Foo*> > >': ../main.cpp:22: instantiated from here /usr/local/boost_1_33_0/boost/bind/bind_template.hpp:15: error: no type named `type' in `struct boost::_bi::result_traits<boost::_bi::unspecified, void (my_namespace::Foo::)()>' /usr/local/boost_1_33_0/boost/bind/bind_template.hpp:18: error: no type named `type' in `struct boost::_bi::result_traits<boost::_bi::unspecified, void (my_namespace::Foo::)()>' [snip bind_template.hpp:24 thru bind_template.hpp:138] /usr/local/boost_1_33_0/boost/bind/bind_template.hpp:143: error: no type named `type' in `struct boost::_bi::result_traits<boost::_bi::unspecified, void (my_namespace::Foo::)()>' /usr/local/boost_1_33_0/boost/bind.hpp: In instantiation of `boost::_bi::bind_t<boost::_bi::unspecified, void (my_namespace::Foo::)(), boost::_bi::list1<boost::_bi::value<my_namespace::Foo*> > >': ../main.cpp:22: instantiated from here /usr/local/boost_1_33_0/boost/bind/bind_template.hpp:160: error: field `boost::_bi::bind_t<boost::_bi::unspecified, void (my_namespace::Foo::)(), boost::_bi::list1<boost::_bi::value<my_namespace::Foo*> > >::f_' invalidly declared method type ../main.cpp: In function `int main(int, char**)': ../main.cpp:22: error: no match for call to `(boost::_bi::bind_t<boost::_bi::unspecified, void (my_namespace::Foo::)(), boost::_bi::list1<boost::_bi::value<my_namespace::Foo*> > >) ()' /usr/local/boost_1_33_0/boost/bind.hpp: In constructor `boost::_bi::bind_t<R, F, L>::bind_t(F, const L&) [with R = boost::_bi::unspecified, F = void (my_namespace::Foo::)(), L = boost::_bi::list1<boost::_bi::value<my_namespace::Foo*> >]': /usr/local/boost_1_33_0/boost/bind.hpp:1403: instantiated from `boost::_bi::bind_t<boost::_bi::unspecified, F, typename boost::_bi::list_av_1<A1>::type> boost::bind(F, A1) [with F = void (my_namespace::Foo::)(), A1 = my_namespace::Foo*]' ../main.cpp:22: instantiated from here /usr/local/boost_1_33_0/boost/bind.hpp:861: error: invalid use of non-static member function make: *** [main.o] Error 1 make: Target `all' not remade because of errors. </result> Thank you (and Peter Dimov) for your assistance. BTW I'm still unclear on *why* (f) works. It doesn't look like any pointer to member function I've read about. Isn't f.operator() treated like any other member function? Can someone suggest something to read that might help me understand? Thanks again for your help. Regards, Dick Bridges

2 1

[Threads] Doc build error?
by Bruno Martínez 30 Aug '05

30 Aug '05

The documentation of boost.threads seems to be built wrong. In several places sentences don't make sense, and words are missing. Some examples are: " Introduction ??? allows C++ programs to execute as multiple, asynchronous, independent threads-of-execution. " " It is possible to write thread-safe implementations of these by using thread specific storage (see boost::thread_specific_ptr), and several C++ compiler vendors do just that. The technique is well-know and is explained in ???. " What's wrong? Bruno

1 0

Re: [Boost-users] Boost.Thread memory leak reported
by Sohail Somani 29 Aug '05

29 Aug '05

> -----Original Message----- > From: boost-users-bounces(a)lists.boost.org > [mailto:boost-users-bounces@lists.boost.org] On Behalf Of Elisha Berns > Sent: Monday, August 29, 2005 4:17 PM > To: boost-users(a)lists.boost.org > Subject: Re: [Boost-users] Boost.Thread memory leak reported > > > Peter Dimov wrote: > > > C++ doesn't guarantee a particular initialization order for > file scope > > objects in different translation units, so we have to > resort to local > > statics or call_once. > > I hear you, I hear the point. I don't have a good solution > to this, but I hope someone does! What about having a single singleton solely responsible for initializing all the other ones?

1 0

Boost.Iostreams: mapped_file_source can't open read only files
by Elisha Berns 29 Aug '05

29 Aug '05

Hi again, Odd, today I have only had PROBLEMS with boost. I guess it's just one of those days. Anyways, the open_impl() method for iostreams::mapped_file_source just doesn't open any mappings for files. I realize that it is reused by the mapped_file class, but that is what seems to cloud the design, flow and working of it as it needs to please everyone here, and it doesn't. It always throws in this location: pimpl_->mapped_handle_ = ::CreateFileMappingA( pimpl_->handle_, NULL, readonly ? PAGE_READONLY : PAGE_READWRITE, 0, 0, p.path.c_str() ); if (pimpl_->mapped_handle_ == NULL) { detail::cleanup_and_throw(*pimpl_, "couldn't create mapping"); } However, if I use just the raw Win32 APIs all works fine: HANDLE hFile = CreateFile(szFile, GENERIC_READ, FILE_SHARE_READ, NULL, OPEN_EXISTING, FILE_ATTRIBUTE_READONLY, NULL); if ( hFile == INVALID_HANDLE_VALUE ) return; HANDLE hFileMapping = CreateFileMapping(hFile, NULL, PAGE_READONLY, 0, 0, NULL); if ( hFileMapping == 0 ) { CloseHandle(hFile); return; } void* pView = ::MapViewOfFile(hFileMapping, FILE_MAP_READ, 0, 0, 0); if ( pView == 0 ) { CloseHandle(hFileMapping); CloseHandle(hFile); return; } Anyways, here my desire is to use the boost libraries as an insulation layer to enable writing cross-platform C++, but obviously if it doesn't work that idea doesn't go too far. So I really hope this gets addressed. Many thanks, Elisha Berns e.berns(a)computer.org tel. (310) 556 - 8332 fax (310) 556 - 2839

3 6

[boost::bind] How use with fn objects?
by BRIDGES Dick 29 Aug '05

29 Aug '05

The documentation gives examples for int operator()(int a, int b)... bool operator()(long a, long b)... that use _1 to represent the first parameter (i.e., 'a'). I'm trying to pass a function object that takes no parameters to a boost::thread constructor and cannot get it right. <my_code> class Foo { void operator()() { /* do something */ return; } } int main( int argc, char **argv ) { Foo f; boost::thread doit( boost:bind<void>(f,_1)() ); doit.join(); return 0; }</my_code> Isn't the '_1' required for the this pointer? If it's not required, what is the correct form? Thanks in advance for any help. Regards, Dick Bridges "Multithreading is just one damn thing after, before, or simultaneous with another." Scott Meyers and Andrei Alexandrescu

3 2

shared_ptr & polymorphic_iarchive in 1.33.0
by Sergey Skorniakov 29 Aug '05

29 Aug '05

Has anybody tested loading of shared_ptr with polymorphic archives? All that I manage to achive is just a couple of errors: c:\boost_1_33_0\boost\archive\detail\interface_iarchive.hpp(73) : error C2039: 'basic_iarchive' : is not a member of 'boost::archive::polymorphic_iarchive' c:\boost_1_33_0\boost\archive\polymorphic_iarchive.hpp(52) : see declaration of 'boost::archive::polymorphic_iarchive' c:\boost_1_33_0\boost\archive\detail\interface_iarchive.hpp(72) : while compiling class-template member function 'void boost::archive::detail::interface_iarchive<Archive>::lookup_helper(const boost::serialization::extended_type_info *const ,boost::shared_ptr<T> &)' with [ Archive=boost::archive::polymorphic_iarchive, T=void ] c:\boost_1_33_0\boost\archive\polymorphic_iarchive.hpp(54) : see reference to class template instantiation 'boost::archive::detail::interface_iarchive<Archive>' being compiled with [ Archive=boost::archive::polymorphic_iarchive ] c:\boost_1_33_0\boost\archive\detail\interface_iarchive.hpp(73) : error C2662: 'boost::archive::detail::basic_iarchive::lookup_basic_helper' : cannot convert 'this' pointer from 'boost::archive::polymorphic_iarchive' to 'boost::archive::detail::basic_iarchive &' Reason: cannot convert from 'boost::archive::polymorphic_iarchive' to 'boost::archive::detail::basic_iarchive' Conversion requires a second user-defined-conversion operator or constructor

3 6

Re: [Boost-users] [typeof] question: BOOST_TYPEOF_COMPLIANT
by Bulygin, Sergey 29 Aug '05

29 Aug '05

>>#include <boost/typeof/typeof.hpp> >>#define BOOST_TYPEOF_COMPLIANT >Just move define before the include, otherwise it has no effect. >Regards, >Arkadiy I tried that before, but it didn't give an effect. Now I discovered the problem - that was "#include <boost/typeof/typeof.hpp>" in the precompiled header file. That way typeof.hpp in the cpp was ignored, and BOOST_TYPEOF_COMPLIANT definition didn't make its job. Thanks! Sergey

1 0

Re: [Boost-users] [typeof] question: BOOST_TYPEOF_COMPLIANT
by Arkadiy Vertleyb 29 Aug '05

29 Aug '05

Hi Sergey, >#include <boost/typeof/typeof.hpp> >#define BOOST_TYPEOF_COMPLIANT Just move define before the include, otherwise it has no effect. Regards, Arkadiy

1 0

[mpl] looping over a list of types inside a function
by Geoffrey Irving 29 Aug '05

29 Aug '05

Hello, I would like to be able to write code like this: int i; for F in LIST_OF_TYPES complicated_function<F>(i); where this code is inside some other function which is inside a class templatized over LIST_OF_TYPES. Given the lack of nested functions and classes in C++ functions, am I correct in thinking that it's impossible to do this sort of thing inside another function? In my particlar case, all the complicated code has already been factored into complicated_function, and there are only ever two LISTS_OF_TYPES, so my current solution is just to manually specialize over LISTS_OF_TYPES. However, this kind of construct often appears several times (with different complicated_functions) in a given outer function, so it would be very nice to only have to write down the high level structure once. Thanks, Geoffrey

3 6

Re: [Boost-users] Using MPL for conditional compilation
by JOAQUIN LOPEZ MU?Z 29 Aug '05

29 Aug '05

----- Mensaje original ----- De: "Alan M. Carroll" <amc(a)network-geographics.com> Fecha: Martes, Agosto 23, 2005 8:52 pm Asunto: [Boost-users] Using MPL for conditional compilation > I am building a templated container class C. Normally it acts just > like an stl::map. However, if the mapped_type of a container > C<key1, value1> is also a specialization of C (value1 = C<key2, > value2>) then the key types of the containers are merged in to a > tuple yielding a container that acts like C< <key1, key2>, value2 >. > > Obviously the MPL has been quite useful for this but I'm not clear > on the best style / usage for a particular effect. > > Inside C, the insert method has two parts, the part that's the > same regardless of whether C is merged container and the part that > isn't. How should I arrange to have different code executed > depending on whether C is a merged container or not? I have a > class static const bool IS_OUTER that is set to true for merged > containers and false otherwise. > [...] > > 5) Use traits classes keyed by IS_OUTER to provide the differing > implementations. If the *syntactic* differences between both flavors can be reduced to only different definitions for key_type and mapped_type, I'd use something like your option 5) : template<typename Key, typename Value> class your_container { static bool const IS_OUTER=...; typedef typename boost::mpl::if_c< IS_OUTER, struct outer_tag, struct inner_tag >::type flavor; public: typedef typename boost::mpl::if_c< IS_OUTER, boost::tuple<Key,typename Value::key_type>, Key >::type key_type; typedef typename boost::mpl::if_c< IS_OUTER, typename Value::mapped_type, Value >::type mapped_type; // example of memfun with alternate implementations const_iterator find(const key_type& k)const { return find_impl(k,flavor()); } // shared menfuns do not need any special machinery private: // alternate implementations of find const_iterator find_impl(const key_type& k,outer_tag)const { ... } const_iterator find_impl(const key_type& k,inner_tag)const { ... } }; With this scaffolding set up, it is guaranteed that only the appropriate *_impl memfuns are compiled in each case, and the runtime penalty should be optimized away to zero. OTOH, if the number of memfuns with alternate implementations is very large with respect to shared memfuns, you might want to go for fully separated classes. HTH, Joaquín M López Muñoz Telefónica, Investigaión y Desarrollo

4 3

Regex boost 1.33 - (mingw/w32) linking problem
by Arno Mauhourat 29 Aug '05

29 Aug '05

Hi, I compiled the regex library with: bjam.exe -sTOOLS=mingw -sMINGW_ROOT_DIRECTORY=D:\Dev-Cpp When linking my project with the generated library (libboost_regex-mgw-d-1_33.lib), I get: ../sources/cmdline.o(.text+0x6fe9): In function `_tcf_1': d:/Dev-Cpp/Bin/../lib/gcc/mingw32/3.4.2/../../../../include/c++/3.4.2/bits/basic_string.h:257: undefined reference to `boost::re_detail::cpp_regex_traits_implementation<char>::init()::null_string' ... etc.... Does that mean I should try using STLPort or ? Regards, Arno

3 2

[typeof] question: BOOST_TYPEOF_COMPLIANT
by Bulygin, Sergey 29 Aug '05

29 Aug '05

Evaluating Boost.Typeof library with MSVC 7.1 compiler. Since this compiler has native typeof trick, BOOST_TYPEOF and BOOST_AUTO work fine by default. But with regard to future upgrade to MSVC 8.0, I want to have my TYPEOF-related code portable, i.e. registering all those user types for proper TYPEOF emulation. When I "#define BOOST_TYPEOF_COMPLIANT", nothing happens and the code proceeds working even without registering my types. I would expect BOOST_TYPEOF_COMPLIANT definition to cause compiler errors for not registered types. Here's the code snippet that I am trying to compile: #include <boost/typeof/typeof.hpp> #define BOOST_TYPEOF_COMPLIANT struct X {}; template<typename A, bool B> struct Y {}; typedef std::pair<X, Y<int, true> > Pair_t; Pair_t a; BOOST_AUTO(b, a); BOOST_AUTO(pp, Pair_t()); What do I miss here? Thank you, Sergey Bulygin

1 0

Boost.Algorithm: Functors must be CopyConstructible
by Daniel Krügler 29 Aug '05

29 Aug '05

Several functors in Boost.Algorithm do not fulfill CopyConstructable requirements, e.g. case_conv.hpp: to_lowerF, to_upperF formatter_regex.hpp: regex_formatF I propose to replace their reference members by either corresponding pointers or by boost::reference<>'s. Greetings from Bremen, Daniel Krügler

2 2

strange filesystem dll behaviour
by Paul 28 Aug '05

28 Aug '05

Hi, I'm having killer problems with the filesystem library. I'm compiling it with bjam "-sTOOLS=mingw", which seems to work just fine. All the tests pass etc. Then I wrote this simple program: #include <boost/filesystem/path.hpp> #include <iostream> using namespace std; using namespace boost::filesystem; int main() { try { path p("c:",native); } catch (exception & e) { cerr << "Error: " << e.what() << endl; return 1; } cerr << "Ok" << endl; return 0; } and compiled it with the Makefile: test: test.cpp Makefile g++ -g -I../boost/boost-compiled -I. -Wall -c test.cpp g++ -g -Wl,-enable-stdcall-fixup -Wl,-subsystem,console -Wall -o test.exe test.o libboost_filesystem-mgw-d-1_32.lib g++ -g -Wl,-enable-stdcall-fixup -Wl,-subsystem,console -Wall -o test-dll.exe test.o -L. -lboost_filesystem-mgw-d-1_3 (adjust for your paths, I copied the dlls and libs into the local dir Just To Be Sure). The output of running the two programs is as follows: paul@xyz ~/test $ ./test Ok paul@xyz ~/test $ ./test-dll.exe Error: boost::filesystem::path: invalid name "c:" in path: "c:" Why does it behave differently depending on the linkage? If I must use a .lib, what if it needs to be used in multiple .dlls of mine? Help? Thanks Paul

3 10

[Test] typo in auto_unit_test.hpp
by Takeshi Mouri 28 Aug '05

28 Aug '05

Hello, line 198: BOOST_AUTO_TC_REGISTRAR( test_nase )( This may cause the redefinition of test_nase_registrar(). I think that it is not "test_nase" but "test_name". Regards, Takeshi Mouri

2 1

Rationale for explicit ctors in boost smart pointers
by Matthias Kaeppler 28 Aug '05

28 Aug '05

Hi, I was wondering why e.g. boost:shared_ptr has an explicit constructor. This makes automatic conversion from T* to shared_ptr<T> impossible. The lack of the opposite conversion is covered by the FAQ and reasonable; however, I couldn't think of a good reason why I shouldn't be able to do something like this: std::set< boost::shared_ptr<Foo> > coll; coll.insert(new Foo); // error: No implicit conversion from Foo* to shared_ptr<Foo> Best regards, Matthias

2 4

Problem of using Boost::regex
by Aaron 28 Aug '05

28 Aug '05

I want to make a program to grep all symbols in header file,like: #define CMD_BASE 0x10000000 #define CMD_GETFile (CMD_BASE + 0X00000001) /* Get a file from srv*/ A singl symbole definition line will be extract to three parts: 1. symbol itself 2. the value of a symbol, it's a signed 32-bit value 3. comments about the symbol I use the following pattern: std::string ptn = "\\s*#define\\s+([^\\s]+)\\s+([^/]*)([^\r\n]*)"; I hope this pattern could do what I want, but when I use grep to do the parsing, I got from above two lines: what[1]: CMD_BASE what[2]: 0x00001000#define CMD_GET_ALL_DOMAINNAME (CMD_IS_BASE+0x1) you see, the match extend to the new line! I noticed that when I use the same text, same pattern, doing the same thing in a vbscript program, if I set "Global match" option, this wouldn't happen. So, what's the counterpoint at boost::regex? My code here: bool OnGrepSingleLineSymbols(const boost::match_results<std::string::const_iterator>& what) { Symbol* sym = new Symbol; strcpy(sym->szSymbolName, what[1].str().c_str()); strcpy(sym->szSymbolInfo, what[3].str().c_str()); MakePretty(sym->szSymbolName); MakePretty(sym->szSymbolInfo); sym->nSymbolValue = ResolveMsgValue(sym->szSymbolName, what[2].str()); GetMsgSrv().AddSymbols(sym); return true; } void GrepSingleLineSymbols(CString& strSymContainer) { //#define ARN_SUCCESS 0l //ARRON!'HAHA //#define Arn_error1 ARN_SUCCESS + 0X0F //AARON ERROR1 static std::string ptn = "\\s*#define\\s+([^\\s]+)\\s+([^/]*)([^\r\n]*)"; static boost::regex re(ptn); std::string::const_iterator start, end; std::string text = strSymContainer; start = text.begin(); end = text.end(); boost::regex_grep(OnGrepSingleLineSymbols, start, end, re); }

2 3

[Serialization] Class versioning & upward compatibilty
by Flavio Antonioli 27 Aug '05

27 Aug '05

Hello, is serialization class versioning supposed to allow old versions of a program that serializes an old version of a class to load files saved with a newer version that saves some extra data? It doesn't seem to be able to do it, but it would be a very useful feature. The docs mention the fact that new versions can read old version classes, they don't mention if old versions can load newer versions files. Unless I'm missing something, which is not unlikely, it should be relatively easy to implement, the xml readed should simply skip fields that it doesn't recognize. I'm using XML serialization, boost_1_33_0 dated 28-4-05, Visual C++ 7.1 & 8.0 beta 2. Thanks, Flavio Antonioli.

2 1

[thread] RFE 1274707: Remove try/catch(...) in thread.cpp:thread_proxy()
by Matt Gruenke 27 Aug '05

27 Aug '05

I've submitted an RFE on this rather troubling behavior. I won't restate my case, as you can just view it here: http://sourceforge.net/tracker/index.php?func=detail&aid=1274707&group_id=7… Anyhow, it occurred to me that perhaps users with threads experience on other platforms (especially Windows) could comment on whether there's any similarly useful debugging behavior when exceptions are allowed to propagate outside of a thread (i.e. what the 'catch(...)' in libs/thread/src/thread.cpp:thread_proxy() specifically inhibits). If so, please update the RFE, rather than posting to the list. Matt Gruenke Software Engineer IntelliVid Corp.

1 0

Re: [Boost-users] Boost.Thread memory leak reported
by Sohail Somani 26 Aug '05

26 Aug '05

> -----Original Message----- > From: boost-users-bounces(a)lists.boost.org > [mailto:boost-users-bounces@lists.boost.org] On Behalf Of Peter Dimov > Sent: Friday, August 26, 2005 1:45 PM > To: boost-users(a)lists.boost.org > Subject: Re: [Boost-users] Boost.Thread memory leak reported > > > Sohail Somani wrote: > > >>> Any dynamically allocated memory that isn't freed is a Bad > >> Thing imho. > >> > >> Because? > > > > Was it forgotten? Was it intentional? If the assumption is it will > > always be freed, then there is no ambiguity. > > Seems clearly intentional to me - the allocation is invoked > by call_once and > is a textbook implementation of a thread safe singleton. A > "this is not a > leak" comment may help. I understand its not a leak. There should atleast be a comment there saying we are not going to deallocate this memory that is allocated once. Its great you know, but part of this thread would have been avoided had there been that comment.

1 0

Re: [Boost-users] Boost.Thread memory leak reported
by Sohail Somani 26 Aug '05

26 Aug '05

> -----Original Message----- > From: boost-users-bounces(a)lists.boost.org > [mailto:boost-users-bounces@lists.boost.org] On Behalf Of Peter Dimov > Sent: Friday, August 26, 2005 1:07 PM > To: boost-users(a)lists.boost.org > Subject: Re: [Boost-users] Boost.Thread memory leak reported > > > Christian Henning wrote: > > > But Peter, we do agree that there is problem and it should > be fixed, > > dont't we? > > I see no problems in the code. Any dynamically allocated memory that isn't freed is a Bad Thing imho.

2 1

Re: [Boost-users] Boost.Thread memory leak reported
by Foster Gareth 26 Aug '05

26 Aug '05

> Because Purify is smart and doesn't report false leaks. > "False leaks"??

3 3

Compile errors with format.hpp on AIX
by Rich Cook 26 Aug '05

26 Aug '05

Hi, Sorry for this repost; my first post was ignored or didn't make it to the list somehow. I am hoping the answer is not, "Forget it, boost doesn't work on AIX." But that is what I'm beginning to suspect. Or am I posting to the wrong list? Including boost/format.hpp on AIX in my project results in the following errors. Does anyone have an idea what is happening? I googled all over the place but found no help on the subject. Is boost only good with gcc? I don't think so, because the compiler for boost works with xlC. Hmm. xlC -c -g -I/g/g0/rcook/aix_5_64_fed/include -I/g/g0/rcook/ downloads/boost_1_33_0 MirandaReader.C -o aix_5_64_fed/MirandaReader.o "/g/g0/rcook/downloads/boost_1_33_0/boost/optional/optional.hpp", line 388.66: 1540-0217 (S) "T" is not a member of "locale". "/g/g0/rcook/downloads/boost_1_33_0/boost/optional/optional.hpp", line 388.10: 1540-0700 (I) The previous message was produced while processing "boost::optional_detail::optional_base<std::locale>::destroy_impl (is_not_reference_tag)". "/g/g0/rcook/downloads/boost_1_33_0/boost/optional/optional.hpp", line 362.9: 1540-0700 (I) The previous message was produced while processing "boost::optional_detail::optional_base<std::locale>::destroy()". "/g/g0/rcook/downloads/boost_1_33_0/boost/optional/optional.hpp", line 208.24: 1540-0700 (I) The previous message was produced while processing "boost::optional_detail::optional_base<std::locale>::~optional_base()". "/g/g0/rcook/downloads/boost_1_33_0/boost/optional/optional.hpp", line 130.7: 1540-0700 (I) The previous message was produced while processing "boost::optional_detail::optional_base<std::locale>::__dftbdt()". "/g/g0/rcook/downloads/boost_1_33_0/boost/optional/optional.hpp", line 471.5: 1540-0700 (I) The previous message was produced while processing "boost::optional<std::locale>::~optional()". "/g/g0/rcook/downloads/boost_1_33_0/boost/format/internals.hpp", line 38.9: 1540-0700 (I) The previous message was produced while processing "boost::io::detail::stream_format_state<char,std::char_traits<char> >::stream_format_state(char)". "/g/g0/rcook/downloads/boost_1_33_0/boost/format/internals.hpp", line 78.53: 1540-0700 (I) The previous message was produced while processing "boost::io::detail::format_item<char,std::char_traits<char>,std::allocat or<char> >::format_item(char)". "/g/g0/rcook/downloads/boost_1_33_0/boost/format/ format_implementation.hpp", line 121.40: 1540-0700 (I) The previous message was produced while processing "boost::basic_format<char,std::char_traits<char>,std::allocator<char> >::make_or_reuse_data(size_t)". "/g/g0/rcook/downloads/boost_1_33_0/boost/format/parsing.hpp", line 415.9: 1540-0700 (I) The previous message was produced while processing "boost::basic_format<char,std::char_traits<char>,std::allocator<char> >::parse(const string_type &)". "/g/g0/rcook/downloads/boost_1_33_0/boost/format/ format_implementation.hpp", line 64.9: 1540-0700 (I) The previous message was produced while processing "boost::basic_format<char,std::char_traits<char>,std::allocator<char> >::basic_format(const string_type &)". "MirandaReader.C", line 138.6: 1540-0700 (I) The previous message was produced while processing "MirandaDataSet::GetGridOrigin(long, Point<double> &)". gmake: *** [aix_5_64_fed/MirandaReader.o] Error 1 -- Richard Cook ✇ Lawrence Livermore National Laboratory Bldg-453 Rm-4037, Mail Stop L-557 7000 East Avenue, Livermore, CA, 94550, USA ☎ (925) 423-9605  (925) 423-6961 --- Information Management & Graphics Grp., Services & Development Div., Integrated Computing & Communications Dept. (opinions expressed herein are mine and not those of LLNL)

1 0

Minor refinements for boost::rational
by Daniel Krügler 26 Aug '05

26 Aug '05

Hello, After a short view at the rational.hpp header I propose to perform the following changes: 1) As counterpart to the existing: bool operator!() const; one should definitly add: operator bool_replacement_type() const; with a proper (member function pointer) definition of bool_replacement_type. 2) The function template template <typename IntType> IntType lcm(IntType n, IntType m); should be defined as template <typename IntType> IntType lcm(IntType n, boost::call_traits<IntType>::param_type m); which makes sense in this case because m is not modified internally (in contrast to n) 3) The boost::rational IO should use proper templated extractors and inserters for those (most) compilers, which provide corresponding std IO libraries, such that #if defined (BOOST_NO_TEMPLATED_STREAMS) ... // current impl #else template<class CharType, class CharTrait, class IntType> inline std::basic_istream<CharType, CharTrait>& operator>>(std::basic_istream<CharType, CharTrait> &is, rational<IntType>&); template<class CharType, class CharTrait, class IntType> inline std::basic_ostream<CharType, CharTrait>& operator<<(std::basic_ostream<CharType, CharTrait> &os, const rational<IntType>&); #end Furtheron I propose to replace the helper class detail::resetter by boost::ios_flags_saver, or even better to remove it all all, because I assume, that the temporary unsetting of the skipws flag does not make much sense - Does it? I also propose to replace the current setting of ios_base::badbit (if widen('/') was not found) by the more appropriate setting of ios_base::failbit - This behaviour is in sync with std::complex and boost::tuple! Greetings from Bremen, Daniel Krügler

3 10

MPL and conditional compilation
by Alan M. Carroll 26 Aug '05

26 Aug '05

2 1

Regex Lib: Feature Set: Newbie ?
by Jordanna Chord 26 Aug '05

26 Aug '05

Newbie question; I'm porting a project from PCRE 3.9 to the most recent version of Boost Regex++. Has anyone compiled a list of differences between the regex supported by Boost and other libraries such as PCRE which supports Perl 5? Thanks, Lacey

2 1

Boost.Random: Suspicious code in uniform_smallint_integer
by Daniel Krügler 26 Aug '05

26 Aug '05

Although uniform_smallint_integer currently is no official code (its in the details section and seems nowhere used), I would like to mention, that the current implementation contains a subtle bug: The member _factor is never initialized, thus calling operator()() would cause U.B. The reason is, that the initializer member function set defines a **local** variable _factor, which is never assigned to this->_factor, such that uniform_smallint_integer::_factor will never be assigned. Just one question: Is detail::uniform_smallint_integer a leftover of some experiments by the library responsible or does it exist for interested boost users to test it? Greetings from Bremen, Daniel

1 0

Re: [Boost-users] Boost serialization
by Li Lirong 26 Aug '05

26 Aug '05

You may try to serialize the data to a std::vector. See here for how to write a ostream with std::vector: http://www.boost.org/libs/iostreams/doc/tutorial/container_sink.html Regards, Lirong --- Srikanth Rao <srirao_us(a)yahoo.com> wrote: > Hi, > > I saw a mail from you to the group. I have a similar > issue but I need to send the serialized data on the > network. > > After serializing to a stream, can I get the buffer? > > How? > TIA, > Sri. > > > > __________________________________ > Yahoo! Mail for Mobile > Take Yahoo! Mail with you! Check email on your > mobile phone. > http://mobile.yahoo.com/learn/mail > __________________________________ Do you Yahoo!? Yahoo! Mail - Find what you need with new enhanced search. http://info.mail.yahoo.com/mail_250

1 0

Re: [Boost-users] Boost.Thread memory leak reported
by Sohail Somani 25 Aug '05

25 Aug '05

> -----Original Message----- > From: boost-users-bounces(a)lists.boost.org > [mailto:boost-users-bounces@lists.boost.org] On Behalf Of Elisha Berns > Sent: Wednesday, August 24, 2005 8:48 PM > To: Boost > Subject: [Boost-users] Boost.Thread memory leak reported > > > > Detected memory leaks! > Dumping objects -> > {146} normal block at 0x00227008, 24 bytes long. > Data: < | > 08 7C 04 00 FF FF FF FF 00 00 00 00 00 00 00 > 00 > {145} normal block at 0x00223928, 8 bytes long. > Data: < p" > 08 70 22 00 01 CD CD CD > Object dump complete. Hi Elisha, Could you come up with a small test case that demonstrates the problem?

4 7

Re: [Boost-users] Boost.Thread memory leak reported
by Sohail Somani 25 Aug '05

25 Aug '05

> -----Original Message----- > From: boost-users-bounces(a)lists.boost.org > [mailto:boost-users-bounces@lists.boost.org] On Behalf Of > Christian Henning > Sent: Thursday, August 25, 2005 4:03 PM > To: boost-users(a)lists.boost.org > Subject: Re: [Boost-users] Boost.Thread memory leak reported > > > I'm just wondering why Purify doesn't show anything. (it sucks) Disclaimer: I only used it enough to make the above statement

1 0

[Test] redirecting unit test report
by Kim Barrett 25 Aug '05

25 Aug '05

I'm using the unit test framework provided by Boost.Test, mostly using the auto unit test facility. I wrote a parser for the XML formatted report output, as part of a regression package. Unfortunately, changes between 1.32 and 1.33 are causing a problem. The format of the XML output changed quite a bit between 1.32 and 1.33. Ok, I can deal with that; in fact, the new format is quite a bit easier to deal with, and I've already finished with the changes. It would be nice if this format were documented though. Unfortunately, there is one change that I haven't been able to figure out a good way to deal with. If a test case aborts, due to an exception uncaught by the test itself, the exception is caught by the unit test framework. The occurrence of the abort is recorded in the test results. In 1.32, this would be reported by including an <aborted ...> subentry for the test case data, including some descriptive text. In 1.33, the descriptive text is printed to std::cerr and the report indicates that the test case was aborted via the "result" value for the test case. The generated report no longer contains the descriptive text. (I don't care all that much about this last change.) The problem is the printing of the descriptive text for the exception to std::cerr. That is also the stream to which the test report is written, and I'm capturing the report information by redirecting stderr to a file when invoking a test program. The exception text ends up appearing at the beginning of the report file, and isn't valid XML, which causes my report parser to die. (If necessary, I may end up prefixing the parser with a step to skip over anything that doesn't look like XML, but that's pretty ugly.) Now, I never really liked redirecting stderr to a file in order to capture the report. What if something in the test program were to write to stderr? (Which is exactly what is happening now.) I see that there is now (in 1.33) a mechanism for setting the stream used by the report generator (boost:unit_test::results_reporter::set_stream()). But after spending the last couple of days pouring over the documentation and sources for Boost.Test, I have no idea where I would put a call to that function that doesn't involve patching the Boost.Test sources. There doesn't seem to be a place to insert such user code, at least not that I can find. Have I overlooked something, or is this really a hole in the present design / implementation?

3 13

Intermittent problem(s) building boost 1.33 with VC7.1
by Elisha Berns 25 Aug '05

25 Aug '05

The message "failed to write command file" comes up intermittently and seemingly at random when I build some or all of the 1.33 libraries. Once that message appears the build is killed and that's it. So far I have only been able to build the thread and iostreams libraries. What's the deal? Is it some problem with my machine, or with the build itself? Thanks, Elisha Berns e.berns(a)computer.org tel. (310) 556 - 8332 fax (310) 556 - 2839

2 1

Re: [Boost-users] Boost.Thread memory leak reported
by Sohail Somani 25 Aug '05

25 Aug '05

> -----Original Message----- > From: boost-users-bounces(a)lists.boost.org > [mailto:boost-users-bounces@lists.boost.org] On Behalf Of > Christian Henning > Sent: Thursday, August 25, 2005 10:53 AM > To: boost-users(a)lists.boost.org > Subject: Re: [Boost-users] Boost.Thread memory leak reported > > > On 8/25/05, Sohail Somani <s.somani(a)fincad.com> wrote: > > Valgrind doesn't find it either. I have yet to try it with stack > > walker (was about to but xp blue screened so I took it as a sign) > > > > Isn't valgrind for linux? I think the problem might be on > Windows machines, only. > > The functions new_critical_section() and > delete_critical_section() should be called only on Windows > machines, since they are calling Win32 functions. I didn't know it was a Windows only problem until you posted the location of the leaked allocation.

2 1

Re: [Boost-users] Boost.Thread memory leak reported
by Sohail Somani 25 Aug '05

25 Aug '05

Valgrind doesn't find it either. I have yet to try it with stack walker (was about to but xp blue screened so I took it as a sign) > -----Original Message----- > From: boost-users-bounces(a)lists.boost.org > [mailto:boost-users-bounces@lists.boost.org] On Behalf Of Elisha Berns > Sent: Thursday, August 25, 2005 9:45 AM > To: boost-users(a)lists.boost.org > Subject: Re: [Boost-users] Boost.Thread memory leak reported > > > Right, > > Those are the same project settings I'm using. The only > difference is that my code is in a non-MFC class. I tested > it with the VLD memory leak detector found on CodeProject and > it also reports zero leaks. > > Elisha > > > I got exactly the same error. Here is how I did it: > > > > I created a project of a MFC Application inside VC7.1 . The wizards > > creates the usual document/view classes. Inside the > document class I > > placed, like Elisha, a mutex. Inside the OnNewDocument() function I > > put the code from Elisha: > > > > BOOL CMFCTestDoc::OnNewDocument() > > { > > if (!CDocument::OnNewDocument()) > > return FALSE; > > > > // TODO: add reinitialization code here > > // (SDI documents will reuse this document) > > > > boost::thread indexer( > > boost::bind(&CMFCTestDoc::run, this)); > > > > boost::mutex::scoped_lock lock(m_orphan_annotation_mutex); > > > > indexer.join(); > > > > > > return TRUE; > > } > > > > I'm using MFC in a Shared DLL and Multithreaded Debug DLL runtime > libs. > > > > I can send the project files to anyone that is interessted. > > > > By the way, if I use Purify to track down the leaks, it cannot find > them. > > > > Regards, > > Christian > > > > > > > > > > On 8/25/05, Sohail Somani <s.somani(a)fincad.com> wrote: > > > > -----Original Message----- > > > > From: boost-users-bounces(a)lists.boost.org > > > > [mailto:boost-users-bounces@lists.boost.org] On Behalf Of Elisha > Berns > > > > Sent: Wednesday, August 24, 2005 8:48 PM > > > > To: Boost > > > > Subject: [Boost-users] Boost.Thread memory leak reported > > > > > > > > > > > > > > > > Detected memory leaks! > > > > Dumping objects -> > > > > {146} normal block at 0x00227008, 24 bytes long. > > > > Data: < | > 08 7C 04 00 FF FF FF FF 00 00 00 00 00 > 00 00 > > > > 00 > > > > {145} normal block at 0x00223928, 8 bytes long. > > > > Data: < p" > 08 70 22 00 01 CD CD CD > > > > Object dump complete. > > > > > > Hi Elisha, > > > > > > Could you come up with a small test case that demonstrates the > problem? > > > > > > > > > _______________________________________________ > > > 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 >

2 1

[filesystem] Mingw DLL problems
by Paul 25 Aug '05

25 Aug '05

Hi all, It seems that theres a lot of traffic in regards to using filesystem as a DLL with mingw (or other) compilers. I'd like to lay out what I know and try and figure out a solution for it. Or at least ask for a work-around to be added to the CVS, or to the documentation! Often I see complaints that it will fail to work as expected! This is because the 'native' "flag" passed to path will be virtually IGNORED when you link to it as a DLL. Why? Because native is not a flag, its a free function pointer. Inside the filesystem DLL, it compares the address of the passed checker against its version of 'native', however: the address of 'native' is DIFFERENT in the DLL compared with any other DLL or your executable! So native(you) != native(DLL), so paths will be checked the POSIX way, not the native way. I've heard suggestions that you should define BOOST_ALL_DYN_LINK, however that doesn't seem to do anything in my case. I've tested it. I am betting that most people 'solve' it by statically linking to it, but thats not an option for me. The only solution I have come up with is to add a function to get the DLL's native function address. Instead of passing 'native', I now pass get_native(). This just does return native; but it does it inside the DLL, so you get the "right" function address. Beman said that it should be fixed in the next version of filesystem, however it appears to be Not Hear Yet. So can we please please get an interim fix? Attached was my attempt from back in January, it worked for me, and I'll be applying it to my shiny new 1.33 version. Thanks Paul

1 0

Boost.Thread memory leak reported
by Elisha Berns 25 Aug '05

25 Aug '05

HI, There is a small memory leak reported by VC7.1 just by declaring a boost::mutex (presumably). Since this makes no sense at all, perhaps there is some explanation for this behavior in this compiler. The code looks like this: In the class definition: mutable boost::mutex m_orphan_annotation_mutex; (It's only declared mutable because it's used in 'const' methods also). In the .cpp file: void OrphanedAnnotationMap::IndexOrphanedAnnotations() { boost::thread indexer( boost::bind(&OrphanedAnnotationMap::Index, this)); boost::mutex::scoped_lock lock(m_orphan_annotation_mutex); indexer.join(); } The memory dump is this: Detected memory leaks! Dumping objects -> {146} normal block at 0x00227008, 24 bytes long. Data: < | > 08 7C 04 00 FF FF FF FF 00 00 00 00 00 00 00 00 {145} normal block at 0x00223928, 8 bytes long. Data: < p" > 08 70 22 00 01 CD CD CD Object dump complete. Elisha Berns e.berns(a)computer.org tel. (310) 556 - 8332 fax (310) 556 - 2839

1 0

Trouble using format.hpp on AIX
by Rich Cook 25 Aug '05

25 Aug '05

Hi, Newbie question. I have used Boost for little things and it has worked fine. Now I'd like to use the format.hpp header, but including it on AIX in my project results in the following errors. Does anyone have an idea what is happening? I googled all over the place but found no help on the subject: xlC -c -g -I/g/g0/rcook/aix_5_64_fed/include -I/g/g0/rcook/ downloads/boost_1_33_0 MirandaReader.C -o aix_5_64_fed/MirandaReader.o "/g/g0/rcook/downloads/boost_1_33_0/boost/optional/optional.hpp", line 388.66: 1540-0217 (S) "T" is not a member of "locale". "/g/g0/rcook/downloads/boost_1_33_0/boost/optional/optional.hpp", line 388.10: 1540-0700 (I) The previous message was produced while processing "boost::optional_detail::optional_base<std::locale>::destroy_impl (is_not_reference_tag)". "/g/g0/rcook/downloads/boost_1_33_0/boost/optional/optional.hpp", line 362.9: 1540-0700 (I) The previous message was produced while processing "boost::optional_detail::optional_base<std::locale>::destroy()". "/g/g0/rcook/downloads/boost_1_33_0/boost/optional/optional.hpp", line 208.24: 1540-0700 (I) The previous message was produced while processing "boost::optional_detail::optional_base<std::locale>::~optional_base()". "/g/g0/rcook/downloads/boost_1_33_0/boost/optional/optional.hpp", line 130.7: 1540-0700 (I) The previous message was produced while processing "boost::optional_detail::optional_base<std::locale>::__dftbdt()". "/g/g0/rcook/downloads/boost_1_33_0/boost/optional/optional.hpp", line 471.5: 1540-0700 (I) The previous message was produced while processing "boost::optional<std::locale>::~optional()". "/g/g0/rcook/downloads/boost_1_33_0/boost/format/internals.hpp", line 38.9: 1540-0700 (I) The previous message was produced while processing "boost::io::detail::stream_format_state<char,std::char_traits<char> >::stream_format_state(char)". "/g/g0/rcook/downloads/boost_1_33_0/boost/format/internals.hpp", line 78.53: 1540-0700 (I) The previous message was produced while processing "boost::io::detail::format_item<char,std::char_traits<char>,std::allocat or<char> >::format_item(char)". "/g/g0/rcook/downloads/boost_1_33_0/boost/format/ format_implementation.hpp", line 121.40: 1540-0700 (I) The previous message was produced while processing "boost::basic_format<char,std::char_traits<char>,std::allocator<char> >::make_or_reuse_data(size_t)". "/g/g0/rcook/downloads/boost_1_33_0/boost/format/parsing.hpp", line 415.9: 1540-0700 (I) The previous message was produced while processing "boost::basic_format<char,std::char_traits<char>,std::allocator<char> >::parse(const string_type &)". "/g/g0/rcook/downloads/boost_1_33_0/boost/format/ format_implementation.hpp", line 64.9: 1540-0700 (I) The previous message was produced while processing "boost::basic_format<char,std::char_traits<char>,std::allocator<char> >::basic_format(const string_type &)". "MirandaReader.C", line 138.6: 1540-0700 (I) The previous message was produced while processing "MirandaDataSet::GetGridOrigin(long, Point<double> &)". gmake: *** [aix_5_64_fed/MirandaReader.o] Error 1 -- Richard Cook ✇ Lawrence Livermore National Laboratory Bldg-453 Rm-4037, Mail Stop L-557 7000 East Avenue, Livermore, CA, 94550, USA ☎ (925) 423-9605  (925) 423-6961 --- Information Management & Graphics Grp., Services & Development Div., Integrated Computing & Communications Dept. (opinions expressed herein are mine and not those of LLNL)

1 0

[ptr_container]copy from one to other with iterator
by Thomas Matelich 24 Aug '05

24 Aug '05

I'm looking at ptr_vector to replace our wrapper around vector<shared_ptr>. How do I correctly write the following: ptr_vector<T> a; ptr_vector<T> b; ... b.push_back(a.begin()); I've tried plain iterators, dereferencing, *iter.base(), etc. I guess I could reinterpret_cast<T*>(*iter.base()). Is there a better way? Also, theres a typo in the docs. The examples page talks about using allocate_clone, and I'm pretty sure its supposed to be new_clone (If not, theres a typo in the tutorial). Thanks, Tom

3 8

Re: [Boost-users] [BULK] Re: [BULK] Re: [BULK] Re: [Test] Asserting a failure
by Sohail Somani 24 Aug '05

24 Aug '05

> -----Original Message----- > From: boost-users-bounces(a)lists.boost.org > [mailto:boost-users-bounces@lists.boost.org] On Behalf Of > Gennadiy Rozental > Sent: Wednesday, August 24, 2005 12:15 PM > To: boost-users(a)lists.boost.org > Subject: [BULK] Re: [Boost-users] [BULK] Re: [BULK] Re: > [Test] Asserting a failure > Importance: Low > > > > On second thought, why not just modify BOOST_REQUIRE? > > What do you propose to modify? > > One could use BOOST_REQUIRE *instead* of assert() or > BOOST_ASSERT. But if > they prefer keep using BOOST_ASSERT I could provide a handler. Well theres no problem using BOOST_ASSERT unless they use it in their code for different reasons. For example they might use it to log in production versions of the application... I guess its not such a big deal if boost test defines its own handler if enable assert handler is not defined. I don't even remember where this thread started :)

1 0

Re: [Boost-users] [BULK] Re: [BULK] Re: [Test] Asserting a failure
by Sohail Somani 24 Aug '05

24 Aug '05

> -----Original Message----- > From: boost-users-bounces(a)lists.boost.org > [mailto:boost-users-bounces@lists.boost.org] On Behalf Of > Sohail Somani > Hmm. That's an idea. I could probably do this within > > Boost.Test so users > > wouldn't need to bother: > > > > test_tools.hpp: > > > > #if !defined(BOOST_TEST_NO_ASSERT_HANDLER) > > > > namespace boost { > > inline void assertion_failed(char const * expr, char const * > > function, char > > const * file, long line) > > { > > ... > > } > > } > > > > #endif > > > > This way by default I will always supply definition for the > > function, unless > > user is willing to suply different one. > > I imagine that would work unless they already use boost > assert and define it in their own code for logging purposes. > Perhaps something along the lines of boost assert for boost test? On second thought, why not just modify BOOST_REQUIRE?

2 1

Re: [Boost-users] [BULK] Re: [BULK] Re: [Test] Asserting a failure
by Sohail Somani 24 Aug '05

24 Aug '05

> -----Original Message----- > From: boost-users-bounces(a)lists.boost.org > [mailto:boost-users-bounces@lists.boost.org] On Behalf Of > Gennadiy Rozental > Sent: Wednesday, August 24, 2005 11:50 AM > To: boost-users(a)lists.boost.org > Subject: [BULK] Re: [Boost-users] [BULK] Re: [Test] Asserting > a failure > Importance: Low > > > > > Try replacing your asserts with BOOST_ASSERT which can be a passive > > assert depending on how you use it. > > > > http://www.boost.org/libs/utility/assert.html > > Hmm. That's an idea. I could probably do this within > Boost.Test so users > wouldn't need to bother: > > test_tools.hpp: > > #if !defined(BOOST_TEST_NO_ASSERT_HANDLER) > > namespace boost { > inline void assertion_failed(char const * expr, char const * > function, char > const * file, long line) > { > ... > } > } > > #endif > > This way by default I will always supply definition for the > function, unless > user is willing to suply different one. I imagine that would work unless they already use boost assert and define it in their own code for logging purposes. Perhaps something along the lines of boost assert for boost test?

1 0

Re: [Boost-users] [BULK] Re: [Test] Asserting a failure
by Sohail Somani 24 Aug '05

24 Aug '05

> -----Original Message----- > From: boost-users-bounces(a)lists.boost.org > [mailto:boost-users-bounces@lists.boost.org] On Behalf Of > Gennadiy Rozental > Sent: Wednesday, August 24, 2005 9:51 AM > To: boost-users(a)lists.boost.org > Subject: [BULK] Re: [Boost-users] [Test] Asserting a failure > Importance: Low > > > > cannot find one. All I see are macros that assert > successes, and those > > that > > assert exceptions. But my particular function does not > throw, it simply > > "assert()"s. > > I do not know reliable/portable way to intercept an assert > invocation. So > you are on your own here. If you know any hooks to do the > job, I am open to > suggestions. Try replacing your asserts with BOOST_ASSERT which can be a passive assert depending on how you use it. http://www.boost.org/libs/utility/assert.html

2 1

Re: [Boost-users] [1.33][ptr_container] bug in erase() in associative containers?
by JOAQUIN LOPEZ MU?Z 24 Aug '05

24 Aug '05

----- Mensaje original ----- De: Thorsten Ottosen <nesotto(a)cs.aau.dk> Fecha: Miércoles, Agosto 24, 2005 6:05 pm Asunto: Re: [Boost-users] [1.33][ptr_container] bug inerase() inassociativecontainers? > > "JOAQUIN LOPEZ MU?Z" <joaquin(a)tid.es> wrote in message > news:1553a314f2df.14f2df1553a3@tid.es... > > > size_type erase( const key_type& x ) // nothrow > > > { > > > BOOST_ASSERT( !this->empty() ); > > Why the BOOST_ASSERT? Do you require that the container > be non-empty for erase to be callable? Am I missing something? > > >>>>>> > > Hm...I couldn't find anything on this in the standard. Can you > locate the > description for map<K,V>::erase( const K&) ? > In 23.1.2 [lib.associative.reqmts], the table has an entry for the expression "a.erase(k)" saying: "erases all the elements in the container with key equivalent to k. returns the number of erased elements." No precondition is stated that "a" should be nonempty, neither in the table itself nor in the general requisites for the table (23.1.2/7), hence "a" is allowed to be empty. I've taken a closer look at your code and think there are some more of these overzealous asserts: * The following in associative_ptr_container.hpp iterator erase( iterator first, iterator last ) // nothrow { BOOST_ASSERT( !this->empty() ); requires again that the container be nonempty. There's no such precondition in the std for the expression "a.erase(q1,q2)": the only requisite in 23.1.2/7 is that [q1, q2) be a valid range, which is compatible with "a" being empty if q1==q2==a.end() (see 24.1/7, see also DR151 which addresses an issue with the original erroneous requirement that q1 be dereferenceable). * Same problem as above in reversible_ptr_container.hpp. HTH, Joaquín M López Muñoz Telefónica, Investigación y Desarrollo

2 1

Re: [Boost-users] [bjam] [v1] How to copy the generated binaries from a dependent project?
by Ames Andreas 24 Aug '05

24 Aug '05

Hi, many thanks for your help. Rene Rivera wrote: > Hm, for 1.33 I see a "stage" target in the signals/build/Jamfile. You are right. What doesn't fit my use case is that, at least I believe so, I can't specify the destination directory there. It always copies the binaries to toplevel/stage/lib. My statement was misleading here, sorry. > Similarly for BBv1 it's: > > stage my_stage > : <dll>@boost/libs/signals/build/boost_signals > <lib>@boost/libs/signals/build/boost_signals > ; > > It requires that you add definition of "boost" to your Jamrules file: > > project boost : _path_to_boost_ ; Aah, that's exactly what I needed to get started. With a bit of additional boilerplate it does what I want. cheers, aa -- Andreas Ames | Programmer | Comergo GmbH | Voice: +49 69 7505 3213 | andreas . ames AT comergo . com

1 0

[Test] Asserting a failure
by Mike 24 Aug '05

24 Aug '05

Hi. Is there a way inside a test case using the Unit Testing Framework to specify that a particular function call ought to fail? For example, I have a function that asserts when passed invalid input. In my test case I want to pass it an invalid parameter and check that the assert is triggered. I'm looking for a macro called BOOST_CHECK_FAILURE (or something like that), but cannot find one. All I see are macros that assert successes, and those that assert exceptions. But my particular function does not throw, it simply "assert()"s. Any ideas? Thanks, Mike

2 1

Re: [Boost-users] [bjam] [v1] How to copy the generated binaries from a dependent project?
by Ames Andreas 24 Aug '05

24 Aug '05

Hi, Vladimir Prus wrote: > I know your message talks about V1, but with V2 this is a simple as: > > install install-boost-libs-you-want > : <path-to-boost>/libs/signals/build//boost_signals > : <location>some-directory > ; > > for multiple variants: > > install install-boost-libs-you-want > : <path-to-boost>/libs/signals/build//boost_signals/<variant>release > <path-to-boost>/libs/signals/build//boost_signals/<variant>debug > : <location>some-directory > ; Thanks for the hint. I have tried it out with the Boost.Buildv2 that ships with 1.33.0 but unfortunately there were some problems: 1) examples/echo doesn't build at all 2) boost toplevel doesn't build because of an issue in iostreams 3) boost/libs/signals builds only a single subvariant and I couldn't figure out how to build all the others 4) contrary to v1 when I build in a subproject (like signals) v2 seems to always complain about missing python, ICU etc. Unless these are grave failures on my part (I've followed the documentation on boost.org which seems to be a bit outdated) I will presumably stay with v1 and more so because Rene Rivera provided me the clue I needed to get going. cheers, aa -- Andreas Ames | Programmer | Comergo GmbH | Voice: +49 69 7505 3213 | andreas . ames AT comergo . com

1 0

[1.33][ptr_container] bug in erase() in associative containers?
by Malte Clasen 24 Aug '05

24 Aug '05

Hi, the erase() method (defined in associative_ptr_container.hpp, line 104) seems a bit strange: size_type erase( const key_type& x ) // nothrow { BOOST_ASSERT( !this->empty() ); iterator i = find( x ); // nothrow if( i == this->end() ) // nothrow return 0; // nothrow this->remove( i ); // nothrow return this->c_private().erase( i.base() ); // nothrow } http://cvs.sourceforge.net/viewcvs.py/boost/boost/boost/ptr_container/detai… My compiler (vc++7.1) complained about the unknown find() when I called erase() on ptr_map. "find" is not declared neither in this class nor in its base class. The closest valid call I could think of would be this->c_private().find( x ) . But there seems to be a nicer solution: size_type erase( const key_type& x ) // nothrow { BOOST_ASSERT( !this->empty() ); return this->c_private().erase( x ); // nothrow } This compiles fine and does just what I want it to do, even nothrow is guaranteed (I checked the vc++ reference for std::map). Now I wonder why erase() is implemented differently in Boost 1.33. Is there anything I overlooked? Btw, is there a rationale for the declaration of insert()? std::pair<iterator,bool> insert( key_type& k, value_type x ); http://cvs.sourceforge.net/viewcvs.py/boost/boost/boost/ptr_container/ptr_m… Passing key_type by non-const reference caused some unaesthetic constructs in my code because return values (temporaries) cannot be used directly. Malte

2 2

Re: [Boost-users] [1.33][ptr_container] bug in erase() inassociativecontainers?
by JOAQUIN LOPEZ MU?Z 24 Aug '05

24 Aug '05

----- Mensaje original ----- De: Thorsten Ottosen <nesotto(a)cs.aau.dk> Fecha: Martes, Agosto 23, 2005 11:22 pm Asunto: Re: [Boost-users] [1.33][ptr_container] bug in erase() inassociativecontainers? [...] > > > > size_type erase( const key_type& x ) // nothrow > > { > > BOOST_ASSERT( !this->empty() ); > > iterator i = find( x ); // nothrow > > if( i == this->end() ) // nothrow > > return 0; // nothrow > > this->remove( i ); // nothrow > > return this->c_private().erase( i.base() ); // nothrow > > } Why the BOOST_ASSERT? Do you require that the container be non-empty for erase to be callable? Am I missing something? Joaquín M López Muñoz Telefónica, Investigación y Desarrollo

2 1

program_options range checking?
by Fredrik Hedman 24 Aug '05

24 Aug '05

Hello, I would like to be able to specify different sanity checks on the input data using the program_options framework. This should be a common enough requirement, but I can not find any example that exactly fits the bill. To be more specific I have a solution that kind of works, but I think it needs a bit to much typing. Here is what I have now: /*! Check for values greater than min. */ template <typename T> class value_gt { public: value_gt(std::string const & msg, T min) : msg_(msg), min_(min) {} void operator()(T const & v) const { if (v > min_) return; ostringstream os; os << msg_ << " to small. Must be larger than " << min_ << " . Found " << v; throw pgmopt::invalid_option_value(os.str()); } private: std::string msg_; T min_; }; void doSetProgram(Options & options) { options.add_options() ("help,h", "show this message") ("density", pgmopt::value<double>()->notifier( value_gt<double>("density", 1.0)), "initial density") ("particles", pgmopt::value<unsigned>()->notifier( value_gt<unsigned>("particles", 100)), "number of particles") ; } I don't like repeating the type (see code above) and would rather like to have access to the name of the option in the function that does the check. What would be a better solution? Adding to the validators idea or? -- F.

2 2