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

Re: [Boost-users] Boost Math Library
by Sliwa, Przemyslaw (London) 11 Jan '06

11 Jan '06

Please have a look at GSL. It is a C lib but can be used with C++. Kind regards Pshemek Przemyslaw Sliwa Global Foreign Exchange FX Risk Engine Development Merrill Lynch ( +44 (0)20 7995 4182 ) +44 (0)79 6325 2319 * Email: przemyslaw_sliwa(a)ml.com -----Original Message----- From: boost-users-bounces(a)lists.boost.org [mailto:boost-users-bounces@lists.boost.org] On Behalf Of yinglcs2(a)yahoo.com Sent: 10 January 2006 07:29 To: boost-users(a)lists.boost.org Subject: [Boost-users] Boost Math Library Hi, Does Boost Math Library support Statistic Calculation? (e.g. median, std deviation, etc)? >From here, it does not appear Boost Math library calculate has statistic algorithm. If not, can someone please recommend some c/c++ library which does statistics? Thank you. http://www.boost.org/libs/libraries.htm#Algorithms Math and numerics * math - Several contributions in the domain of mathematics, from various authors. * numeric/conversion - Optimized Policy-based Numeric Conversions, from Fernando Cacciola. * integer - Headers to ease dealing with integral types. * interval - Extends the usual arithmetic functions to mathematical intervals, from Guillaume Melquiond, Hervé Brönnimann and Sylvain Pion. * math/common_factor - Greatest common divisor and least common multiple, from Daryle Walker. * math/octonion - Octonions, from Hubert Holin. * math/quaternion - Quaternions, from Hubert Holin. * math/special_functions - Mathematical special functions such as atanh, sinc, and sinhc, from Hubert Holin. * multi_array - Multidimensional containers and adaptors for arrays of contiguous data, from Ron Garcia. * operators - Templates ease arithmetic classes and iterators, from Dave Abrahams and Jeremy Siek. * random - A complete system for random number generation, from Jens Maurer. * rational - A rational number class, from Paul Moore. * uBLAS - Basic linear algebra for dense, packed and sparse matrices, from Joerg Walter and Mathias Koch. __________________________________________ Yahoo! DSL - Something to write home about. Just $16.99/mo. or less. dsl.yahoo.com _______________________________________________ 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/ --------------------------------------------------------

2 1

[serialization] [wave] [spirit] Can't compile boost cvs
by Peter Whaite 10 Jan '06

10 Jan '06

Since before Christmas I haven't been able to compile the cvs serialization xml files. It looks like something in spirit. Wave also fails to compile with the same errors. I'm a bit surprised I haven't seen this mentioned on the boost lists, though I see there are many failures in the boost regression notifications. % gcc -v Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.2/specs Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --disable-checking --with-system-zlib --enable-__cxa_atexit --host=i386-redhat-linux Thread model: posix gcc version 3.2.2 20030222 (Red Hat Linux 3.2.2-5) % bjam --with-serialization Building Boost.Regex with the optional Unicode/ICU support disabled. Please refer to the Boost.Regex documentation for more information (and if you don't know what ICU is then you probably don't need it). ...found 4780 targets... ...updating 48 targets... gcc-C++-action bin/boost/libs/serialization/build/libboost_serialization.a/gcc/debug/xml_grammar.o In file included from /misc/hdb1/local-src/boost_cvs/boost/spirit/core/scanner/skipper.hpp:16, from /misc/hdb1/local-src/boost_cvs/boost/spirit/core/composite/impl/directives.ipp:16, from /misc/hdb1/local-src/boost_cvs/boost/spirit/core/primitives/primitives.hpp:16, from /misc/hdb1/local-src/boost_cvs/boost/spirit/utility/chset.hpp:15, from /misc/hdb1/local-src/boost_cvs/boost/archive/impl/basic_xml_grammar.hpp:69, from /misc/hdb1/local-src/boost_cvs/libs/serialization/src/xml_grammar.cpp:16: /misc/hdb1/local-src/boost_cvs/boost/spirit/core/primitives/impl/primitives.ipp:190: new declaration `template<class CharT> boost::enable_if<boost::spirit::impl::use_char_traits<CharT>, std::char_traits<_CharT>::int_type>::type boost::spirit::impl::to_int_type(CharT)' /misc/hdb1/local-src/boost_cvs/boost/spirit/core/primitives/impl/primitives.ipp:171: ambiguates old declaration `template<class CharT> boost::disable_if<boost::spirit::impl::use_char_traits<CharT>, CharT>::type boost::spirit::impl::to_int_type(CharT)' /misc/hdb1/local-src/boost_cvs/boost/spirit/core/primitives/impl/primitives.ipp:199: new declaration `template<class CharT> boost::enable_if<boost::spirit::impl::use_char_traits<CharT>, CharT>::type boost::spirit::impl::to_char_type(CharT)' /misc/hdb1/local-src/boost_cvs/boost/spirit/core/primitives/impl/primitives.ipp:179: ambiguates old declaration `template<class CharT> boost::disable_if<boost::spirit::impl::use_char_traits<CharT>, CharT>::type boost::spirit::impl::to_char_type(CharT)' set -e "g++" -c -DBOOST_LIB_DIAGNOSTIC=1 -g -O0 -fno-inline -Wall -ftemplate-depth-255 -Wno-non-virtual-dtor -Wno-ctor-dtor-privacy -I"bin/boost/libs/serial ization/build" -I "/misc/hdb1/local-src/boost_cvs" -o "bin/boost/libs/serialization/build/libboost_serialization.a/gcc/debug/xml_grammar.o" "/misc/hdb1/lo cal-src/boost_cvs/libs/serialization/build/../src/xml_grammar.cpp" "/usr/bin/objcopy" --set-section-flags .debug_str=contents,debug "bin/boost/libs/serialization/build/libboost_serialization.a/gcc/debug/xml_grammar.o" ...failed gcc-C++-action bin/boost/libs/serialization/build/libboost_serialization.a/gcc/debug/xml_grammar.o... gcc-C++-action bin/boost/libs/serialization/build/libboost_serialization.a/gcc/debug/xml_iarchive.o ...interrupted ...failed updating 1 target... -- Peter Whaite (http://whaite.ca)

2 1

[serialization] : Documentation
by nitin motgi 10 Jan '06

10 Jan '06

Hi, I think a sentence has to be modified in the documentation. On the link http://www.boost.org/libs/serialization/doc/index.html Section : Pending Issues [ Added >> << ] currently can't serialize through a pointer an object >>a of<< class that implements its own new/delete operators. I was wondering whether it is "object a". to currently can't serialize through a pointer an object >>of a<< class that implements its own new/delete operators. Thank you, -- Nitin Motgi NITIN . DOT. MOTGI .AT. GMAIL .DOT. COM

1 0

Re: [Boost-users] [BULK] Re: [Test] Running a specific Test Suite
by Sohail Somani 10 Jan '06

10 Jan '06

> -----Original Message----- > From: boost-users-bounces(a)lists.boost.org > [mailto:boost-users-bounces@lists.boost.org] On Behalf Of > Gennadiy Rozental > Sent: Tuesday, January 10, 2006 11:03 AM > To: boost-users(a)lists.boost.org > Subject: [BULK] Re: [Boost-users] [Test] Running a specific Test Suite > Importance: Low > > > > Is there a flag I can pass to the test program or any other > way to run > > only a specific Test Suite, ignoring the other ones? > > Hopefully by the end of this release cycle I will add an > ability to run tests by name, which should satisfy this request. I am not yet a user of boost unit test, but is there a way of listing all the tests/targets as well? That could be very useful. I still wish this was a feature in scons!

2 1

iterators 2
by jens-theisen＠gmx.de 10 Jan '06

10 Jan '06

Hello, Thanks for the references, I briefly looked at them (Views and any_iterator) and wasn't aware of them beforehand. I'm not really looking for a solution to a particular problem I might have, but rather wondering if there is not something very basic missing from C++. In many other programming languages there is a good notion for talking about a collection of things conveniently. Python and the .NET languages have this with their iterator concepts. C++ only has it's iterators currently, which is not always a very good solution for reasons alread said. Especially, for the starting problem of my original posting, there is no natural solution. True, there is any_iterator: We can define the virtual function in my original problem as typedef boost::iterator_range< adobe::any_iterator< ... > > ret_range; class X : ... { virtual ret_range give_stuff() const; ... It's still a monstrosity, however, given that any_iterator has 4 template parameters, is derived from iterator_facade, and the iterator_range doubles this even. Presumably, a library author would quickly write his own little nonstandard iterator interface himself and have the virtual function return this instead. It would be nice to have something lightweight enough to promote its use a bit like boost::shared_ptr has become "the obvious way" of dealing with dynamic objects in C++. What I like to have is something more lightweight, along the following requirements: - the "notion" of a collection of things as a concrete type rather than a concept - fast to compile, simple error messages, fun to use, it should be the obvious choice for a library programmer to give collections of things (rather than awkward input iterators derived from iterator_facade) - a toolbox of free functions to combine them in all the ways I can do with linked lists in functional languages - performance and memory usage don't have to be optimal if we're just talking about the cost of a virtualisation A while ago, I made a first attempt on this, making the following design decisions: - There is no concept, but just one templated type: class list< typename reference >; which has various implementations and is, despite the name, conceptually a forward traversal iterator which is aware of the end of its range. - lists are constructed by using a number of free functions only, notably - the make_list overload set, implementing construction from stuff like iterators, containers, etc. and - map, filter, concat, etc. for combining lists in useful ways. - lists have conversion operators along the line of the conversion of their underlying reference type, which especially enables list< T const& > to be used where list< T > is expected. - lists are not iterators, but they can export that behaviour. If this feature isn't used, iterator_facade don't have to be present. (If viewed as iterators, their end is a default constructed list, as usual.) The most important thing that's lacking, however, is that lists are conceptually forward traversal only. Actually, I'm not entirely convinced that it would really be necessary to have more than that (or less). My impression is that virtualisation for more than forward traversal is less dearly needed. I can only think of somewhat contrived examples. What do you think? If other forms of traversal are important, this would complexify all of this quite a bit. Presumably there would be a class hierarchy reflecting the traversal concepts, and possibly each such hiearchy for the implementations as well. But what should free function like map return then? There would have to be overloads for each of the traversal types, and there are already other reasons for overloads. How do people think on this matter? What direction to go? Is this worth spending time on? Cheers, Jens

2 2

[Test] Running a specific Test Suite
by Edson Tadeu 10 Jan '06

10 Jan '06

Is there a flag I can pass to the test program or any other way to run only a specific Test Suite, ignoring the other ones? Thanks in advance

2 1

Boost Serialization: extended_type_info_no_rtti not working...
by RIVASSEAU Jean Noel 10 Jan '06

10 Jan '06

Hello, I am trying to learn the Boost Serialization Library. Although I like the fundamental principles of the library, using the library so far has proven a nightmare for my project. To be more precise: I need to serialize objects via pointers to base class. And I need to do it without RTTI. While using extended_type_info_no_rtti for my classes I always get an "unregistered_class" exception at run time. But I have done the following: in all my classes, in the implementation unit (.cpp) I have included explicitely the headers needed for the archives I use: #include <boost/archive/text_oarchive.hpp> #include <boost/archive/text_iarchive.hpp> Then I have something like that in each class: #include <boost/serialization/base_object.hpp> #include <boost/serialization/type_info_implementation.hpp> #include <boost/serialization/extended_type_info_no_rtti.hpp> #include <boost/serialization/export.hpp> namespace boost { namespace serialization { template<class Archive> void serialize(Archive & ar, PrimitiveMemberVariableSpecification & m, const unsigned int version) { ar & boost::serialization::base_object<MemberVariableSpecification>(m); ar & m.unused_primitive_type; } } // namespace serialization } // namespace boost BOOST_CLASS_TYPE_INFO( PrimitiveMemberVariableSpecification, extended_type_info_no_rtti<PrimitiveMemberVariableSpecification> ) BOOST_CLASS_EXPORT(PrimitiveMemberVariableSpecification) (Here the name of the class is PrimitiveMemberVariableSpecification. I also want to report a bug in the documentation: the doc says that you should write: BOOST_CLASS_TYPE_INFO( ClassName, extended_type_info_no_rtti<BaseClassName> ) Although the example test_no_rtti.cpp uses the following syntax: BOOST_CLASS_TYPE_INFO( ClassName, extended_type_info_no_rtti<ClassName> ) I think that the example is right, not the documentation. ) Normally the BOOST_CLASS_EXPORT should *register* all my classes. Why doesn't it work? I have of course also written a correct get_key() virtual function for all my classes. If I just change extended_type_info_no_rtti to extended_type_info_typeid, everything works fine, but I do want extended_type_info_no_rtti. Also, keeping everything in the headers files seems to be a nightmare, although that is what Robert Ramsey recommends. I get tons of multiple definitions errors at link time if I do that (something like: multiple definition of `boost::archive::detail::guid_initializer<MemberVariableSpecification>::instance' with gcc - MinGW 3.4.2) I have looked at the documentation for two days, read absolutely everything and still do not understand. Maybe I should look at the code ??? Thank you Jean-Noël

2 1

Cross compiling boost libraries with gcc and using boost jam to crosscompile third-party library (Jambase problem)
by Vladimir Michl 10 Jan '06

10 Jan '06

Hi all in this list, recently I was put into task to cross compile boost for ARM platform with GCC. My building platform is i386 Linux with gcc and cross compiling to arm Linux. Standard way for this kind of compilation is, that name of cross compiler (running under i386 but producing arm code) and all cross binary utilities are prefixed by target plarform, so like arm-linux-gcc, arm-linux-g++, arm-linux-ar, arm-linux-objcopy for arm-linux. And this is causing a bit of problem with boost. I can force GCC and GXX, but still have a problem with ar and objcopy. I've tried to setup GCC_BIN_DIRECTORY but it didn't work. So I've done a small patch to tools/build/v1/gcc-tools.jam adding GCC_PREFIX variable, that if set up, will prefix names of all tools with that prefix. So I can compile boost with bjam -sTOOLS=gcc -sGCC_PREFIX=arm-linux- stage May be it will be useful to add the same functionality to gcc-stlport-tools.jam or mingw. So please find attached changes. It is possible to include them into next boost release? By the way, the same problem appears when boost jam is used to compile some third-party libraries. Is this place good to talk about boost jam and its Jambase file? Vlad -- Vladimir Michl <vladimir.michl(a)seznam.cz>, ICQ# 312939054 Tel: +447793527010 +447906361574 +420608413590

1 0

[bind] Problem with 1.33.1, g++ 3.3.3
by David Greene 10 Jan '06

10 Jan '06

I'm trying to compile this little program: #include <boost/bind.hpp> #include <iostream> namespace tester { class Test { public: void do_test(void) { std::cout << "Done!" << std::endl; }; }; }; int main(void) { tester::Test x; bind(&tester::Test::do_test, &x, _1)(); return(0); } But I end up with this error (full error trace below): /tools/i686-pc-linux-gnu/include/boost-1_33_1/boost/bind.hpp:63: error: ` void (tester::Test::*)()' is not a class, struct, or union type It looks like somewhere along the way the wrong template specialization is chosen for result type deduction. Am I doing something wrong or is this a known problem? I tried lambda's bind but that also gives an error. It's a different error but I believe it amounts to the same problem. Thanks! -Dave ------------------------ bind.cc:16: instantiated from here /tools/i686-pc-linux-gnu/include/boost-1_33_1/boost/bind.hpp:63: error: ` void (tester::Test::*)()' is not a class, struct, or union type /tools/i686-pc-linux-gnu/include/boost-1_33_1/boost/bind/bind_template.hpp: In instantiation of `boost::_bi::bind_t<boost::_bi::unspecified, void (tester::Test::*)(), boost::_bi::list2<boost::_bi::value<tester::Test*>, boost::arg<1> > >': /tools/i686-pc-linux-gnu/include/boost-1_33_1/boost/bind.hpp:1409: instantiated from `boost::_bi::bind_t<boost::_bi::unspecified, F, typename boost::_bi::list_av_2<A1, A2>::type> boost::bind(F, A1, A2) [with F = void (tester::Test::*)(), A1 = tester::Test*, A2 = boost::arg<1>]' bind.cc:16: instantiated from here /tools/i686-pc-linux-gnu/include/boost-1_33_1/boost/bind/bind_template.hpp:15: error: no type named `type' in `struct boost::_bi::result_traits<boost::_bi::unspecified, void (tester::Test::*)()> ' /tools/i686-pc-linux-gnu/include/boost-1_33_1/boost/bind/bind_template.hpp:18: error: no type named `type' in `struct boost::_bi::result_traits<boost::_bi::unspecified, void (tester::Test::*)()> ' /tools/i686-pc-linux-gnu/include/boost-1_33_1/boost/bind/bind_template.hpp:24: error: no type named `type' in `struct boost::_bi::result_traits<boost::_bi::unspecified, void (tester::Test::*)()> ' /tools/i686-pc-linux-gnu/include/boost-1_33_1/boost/bind/bind_template.hpp:30: error: no type named `type' in `struct boost::_bi::result_traits<boost::_bi::unspecified, void (tester::Test::*)()> ' /tools/i686-pc-linux-gnu/include/boost-1_33_1/boost/bind/bind_template.hpp:30: confused by earlier errors, bailing out make: *** [bind.o] Error 1 Compilation exited abnormally with code 2 at Mon Jan 9 17:08:20

3 3

accessing boost::format's parsing results?
by nospam＠technolumiere.com 10 Jan '06

10 Jan '06

Does anyone know if it is possible to have boost::format parse a printf style format string, and have the results accessible? i.e. given a string like "filename_v%02d.%s", I'd like to be able to parse it and see that there are two arguments, and then retrieve their type. It seems that all the parsing in boost::format is hidden away internally. It would be a shame to have to write my own printf format string parser when I know there is a good one already in there somewhere. AC.

2 1

Profiling Boost Graph Library with gprof
by Dave 10 Jan '06

10 Jan '06

Hello All, I have been trying to profile a few graph algorithms written using Boost Graph Library. I am using gprof for profiling. My graph has 100 vertices. It takes more than 10 minutes to compile, I suspect it is because of the size of the graph. The profile does not show any details though. It only shows the amount of time spent by the profiler. What am I doing wrong? Any help is greatly appreciated! Thanks. __________________________________________ Yahoo! DSL Something to write home about. Just $16.99/mo. or less. dsl.yahoo.com

3 2

Understanding Boost.Mpl Fold Algorithm
by Eduardo Bezerra 10 Jan '06

10 Jan '06

Hi, I'm having a hard time trying to understand what the placeholders _1 and _2 mean in the context of the mpl::fold algorithm. >From the Boost.Mpl Reference manual: typedef vector<long,float,short,double,float,long,long double> types; typedef fold< types , int_<0> , if_< is_float<_2>,next<_1>,_1 > >::type number_of_floats; BOOST_MPL_ASSERT_RELATION( number_of_floats::value, ==, 4 ); Could someone give me some help on this ? Best regards, Eduardo

4 6

Is there a StringBuffer equivalent in Boost library?
by ying lcs 10 Jan '06

10 Jan '06

Is there a StringBuffer equivalent in Boost library? If not, what is the most efficient way to append string? Thank you. __________________________________________ Yahoo! DSL Something to write home about. Just $16.99/mo. or less. dsl.yahoo.com

2 1

Bind signals together
by Will 10 Jan '06

10 Jan '06

Hi, I'm looking for a general technique for binding signals with varying signatures together. Obviously i can create custom functions for any specific case, but i'm wondering if boost::bind could be used to help out here? i.e. boost::signal1<void, const char *> sig1; boost::signal0<void> sig2; void bing() { std::cout << "bing" << std::endl; } // connect sig1 to sig2 such that calling sig1 will invoke sig2 // ... <- how do i do this? // connect sig2 to some function sig2.connect(&bing); // call the signal sig1("some string"); Thanks in advance - Will

2 2

any Boost library for unit testing C++ code
by ying lcs 09 Jan '06

09 Jan '06

Hi, Is there any Boost library for unit testing C++ code? If not, can anyone please recommend any good library for unit testing C+++ code? Thank you. __________________________________________ Yahoo! DSL Something to write home about. Just $16.99/mo. or less. dsl.yahoo.com

2 1

boost::thread problem on 1.33.1
by Brian Plummer 09 Jan '06

09 Jan '06

The following simple program seg faults. (I have boiled it down to the bare essentials to product the fault: ================================================================== #include <boost/thread.hpp> void * MMULT2(void); void * MMULT2CalcMaster(void); int main(void) { MMULT2(); } class MMULT2ThreadClass { void calculate(void) {} public : MMULT2ThreadClass() {} void operator ()() { calculate(); } }; void * MMULT2CalcMaster(void) { int numThreads = 2; boost::thread_group threads; for (int i = 0; i < numThreads; ++i) threads.create_thread(MMULT2ThreadClass()); threads.join_all(); } void * MMULT2(void) { return MMULT2CalcMaster(); } ================================================================== Here is the compile line: cd /SDE/common/src/lib/PSF/PSFWorkbook/testing/BoostThreadProblem/ make clean run DEBUG=YES /bin/rm -rf DO/LINUX_X86_GCC3.4.5/debug/BoostThreadProblem.o /SDE/common/bin/LINUX_X86_GCC3.4.5/debug/BoostThreadProblem *.o *.i Templates.DB gcc -I. -I/SDE/common/include -I/usr/java/jdk1.3.1_01/include -I/usr/java/jdk1.3.1_01/include/linux -I/opt/sybase-11.9.2/include -c -g -DDEBUG -D_TRACE -DLITTLEENDIAN=1 -DDBG=1 -DDEVL=1 -DDBGPROP -D_UNIX -DNEWPROPS -DBRP_LINUXINTEL -DBRP_LITTLE_ENDIAN BoostThreadProblem.cpp -o DO/LINUX_X86_GCC3.4.5/debug/BoostThreadProblem.o gcc DO/LINUX_X86_GCC3.4.5/debug/BoostThreadProblem.o -L/usr/local/lib -L/usr/lib -L/SDE/COTS/Boost/boost_1_33_1/bin/boost/libs/thread/build/libboost_thread.a/gcc/release/threading-multi -lboost_thread-gcc-mt-d-1_33_1 -o /SDE/common/bin/LINUX_X86_GCC3.4.5/debug/BoostThreadProblem /SDE/common/bin/LINUX_X86_GCC3.4.5/debug/BoostThreadProblem make: *** [run] Segmentation fault Compilation exited abnormally with code 2 at Wed Jan 4 17:12:11 ================================================================== I have tried using the -pthread and -D_REENTRANT compile flags with no luck. I had previously used the code that this example is based on, without any problems under 1.30.0 (and not using the -pthread and -D_REENTRANT flags). I feel I've got to be missing something very basic associated with building and using the Thread library. At this point I'm a bit stumped. Also, I noticed the following. bjam -sTOOLS=gcc in the build directory only builds the mt_d version of the library and not the release version. I don't remember needing to do anything special to get both versions built. Additionally, I'm not having any of these problems with the same code on WIN32 with Visual Studio 2003. Thanks in advance, Brian

3 5

[Parameter] Documentation opinions
by Thomas Matelich 09 Jan '06

09 Jan '06

Parameter seems perfect for some code I'm writing now, so I thought I'd give it a look. The organization of the documentation is definitely not oriented to the type of library user I am (skim tutorial, quick copy/paste of example, then hack with reference docs). I have two requests that would have given me less headaches. 1) Provide complete source for the examples at 3 phases. Say a .cpp covering the topics learned so far at the end of each 2.x section. Going and looking at the test code, I did find tutorial, though I was disappointed to find it had only the first minimal example, and the other test code is built around smaller/simpler problems 2) Move the reference doc link to the top. I totally missed it until I hit Konqueror's Up navigation button and saw the rst in http://www.boost.org/libs/parameter/doc/. Thanks for listening. Tom PS Please don't ask for patches, this is a suggestion, I don't care if you do it or not. I know Dave's a stickler for good docs, so I'm giving some feedback.

1 0

user defined seed
by Giulio Veronesi 09 Jan '06

09 Jan '06

Hi all, I've a problem with random number generator. Let us consider the following code fragment: long int s = 123456; mt19937 rnd_gen(s); When I try to compile it I get the following error message: /home/mpalesi/WORK/TOOLS/BGL/current/boost/random/mersenne_twister.hpp: In member function `void boost::random::mersenne_twister<UIntType, w, n, m, r, a, u, s, b, t, c, l, val>::seed(Generator&) [with Generator = long int, UIntType = uint32_t, int w = 32, int n = 624, int m = 397, int r = 31, UIntType a = 09908b0df, int u = 11, int s = 7, UIntType b = 09d2c5680, int t = 15, UIntType c = 0efc60000, int l = 18, UIntType val = 0c77666de]': /home/mpalesi/WORK/TOOLS/BGL/current/boost/random/mersenne_twister.hpp:67: instantiated from `boost::random::mersenne_twister<UIntType, w, n, m, r, a, u, s, b, t, c, l, val>::mersenne_twister(Generator&) [with Generator = long int, UIntType = uint32_t, int w = 32, int n = 624, int m = 397, int r = 31, UIntType a = 09908b0df, int u = 11, int s = 7, UIntType b = 09d2c5680, int t = 15, UIntType c = 0efc60000, int l = 18, UIntType val = 0c77666de]' src/apsra_mesh.cpp:253: instantiated from here /home/mpalesi/WORK/TOOLS/BGL/current/boost/random/mersenne_twister.hpp:103: error: ` gen' cannot be used as a function make: *** [obj/apsra_mesh.o] Error 1 The src/apsra_mesh.cpp:253 is the row "mt19937 rnd_gen(s);" I've no problem if I try to compile: mt19937 rnd_gen(123456); Please, could you help me to resolve this problem? Best regards, Giulio Chiacchiera con i tuoi amici in tempo reale! http://it.yahoo.com/mail_it/foot/*http://it.messenger.yahoo.com

2 1

Field of record as boost::any
by Mateusz Łoskot 09 Jan '06

09 Jan '06

Hi, Is boost::any suitable to use it as a type of field of record? Record is a set of fields. Every field may store value of different type: int, double, char*. Usually, in this case I'd use union of int,double and char*. But I'd like to solve it a better way, more C++ than C. So, would you recommend boost::any as a type of field value? Cheers -- Mateusz Łoskot http://mateusz.loskot.net

2 3

Is boost::filesystem::path unable to deal with hidden unix dircetories?
by Hendrik Belitz 09 Jan '06

09 Jan '06

Dear boost users and developers, I just encountered a minor problem in boost::filesystem::path which seems to be unable to deal with hidden unix directories ( == names preceeded by an dot '.' character ). Is there any way to generate a valid path object for paths like "/foo/.bar"? Trying to create such an object from a C++ string results in an exception getting thrown. ------------------------------------------------------------------------------------- Dipl.-Inform. Hendrik Belitz Central Institute of Electronics / Zentralinstitut für Elektronik Multimodal image processing workgroup / AG Multimodale Bildverarbeitung Research Center Juelich / Forschungszentrum Jülich GmbH D-52428 Jülich, Germany Tel.: (++49)2461 61 8701 Fax: (++49)2461 61 3990 email: h.belitz(a)fz-juelich.de ggp-key available via http://pgpkeys.pca.dfn.de

3 2

[MSVC7.0] functions missing when BOOST_NO_MEMBER_TEMPLATES is defined
by Allen Zhao 09 Jan '06

09 Jan '06

Hi, All, As I am working to get libtorrent working on Win32 with MSVC 7.0, I notice that BOOST_NO_MEMBER_TEMPLATES is defined by default. As a consquence, some of the functions in multi_index_container.cpp is not defined. For example, #if !defined(BOOST_NO_MEMBER_TEMPLATES) template<int N> struct nth_index { BOOST_STATIC_ASSERT(N>=0&&N<mpl::size<index_type_list>::type::value); typedef typename mpl::at_c<index_type_list,N>::type type; }; template<int N> typename nth_index<N>::type& get(BOOST_EXPLICIT_TEMPLATE_NON_TYPE(int,N)) { BOOST_STATIC_ASSERT(N>=0&&N<mpl::size<index_type_list>::type::value); return *this; } template<int N> const typename nth_index<N>::type& get( BOOST_EXPLICIT_TEMPLATE_NON_TYPE(int,N))const { BOOST_STATIC_ASSERT(N>=0&&N<mpl::size<index_type_list>::type::value); return *this; } #endif Is there anything to enable these functions when BOOST_NO_MEMBER_TEMPLATES is undef? Any suggestions? Best regards, Allen Zhao

5 4

Misuse of shared_ptr?
by Pooyan McSporran 09 Jan '06

09 Jan '06

Hi, (Using gcc 4.0.2, boost 1.33.1, linux) I've got a program which causes segfaults using shared_ptr. I've reduced the program as far as I can to show the fault without any extra fluff. It looks as if an object pointed to by a shared_ptr is being deleted more than once. What I'm trying to do is to have an instance of Memory 'know' about an instance of Foo. This is currently being done with a shared_ptr. It appears that I'm misusing shared_ptr in the assignment, but I'm unsure as to what the right way is. Alternatively, I probably could use a reference instead of a shared_ptr, but I'm not sure if the Foo instance will always exist. Thanks in anticipation. #include <cstdlib> #include <iostream> #include <string> #include <boost/shared_ptr.hpp> class Memory; typedef boost::shared_ptr<Memory> MemoryPtr; class Foo; typedef boost::shared_ptr<Foo> FooPtr; class Memory { public: Memory () : fp () { std::cout << "Constructed Memory" << std::endl; }; virtual ~Memory () { std::cout << "Destructing Memory" << std::endl; std::cout << "fp.use_count=" << fp.use_count () << std::endl; }; void remember1 (FooPtr f) { std::cout << "Remembering" << std::endl; fp = f; }; private: FooPtr fp; }; class Foo { public: Foo (const std::string& name_) : name (name_) { std::cout << "Constructed Foo '" << name << "'" << std::endl; }; virtual ~Foo () { std::cout << "Destructing Foo '" << name << "'" << std::endl; }; void test (MemoryPtr m) { m -> remember1 (FooPtr (this)); } private: const std::string name; }; int main () { { FooPtr f1 (new Foo ("first")); MemoryPtr m1 (new Memory ()); f1 -> test (m1); } return EXIT_SUCCESS; }

3 3

[program_options] How to use unknown program options?
by Vsevolod Vlaskin 09 Jan '06

09 Jan '06

Hi, I am trying to allow unknown options in the command line of my application (as described in "Allowing Unknown Options" section of program_options docs). Here is the code snippet: //----------------------------------------------------- boost::program_options::options_description my_options("Options"); my_options.add_options() /* adding some allowed options */ ; boost::program_options::variables_map vm; boost::program_options::store( boost::program_options::command_line_parser( ac, av ).options( my_options ).allow_unregistered().run(), vm ); boost::program_options::notify( vm ); //----------------------------------------------------- If an option is not specified in my_options, the call boost::program_options::store() above throws exception "unknown option". (I checked that it is store() that throws.) Does anyone have any suggestions how I could store and access the option values in this case? Of course, I can use basic_parsed_options returned by run(), but it seems to defeat the convenience of the library. Is there any way to use store() and variables_map in this case? Thank you for help. Best regards, Vsevolod Vlaskine __________________________________________ Yahoo! DSL Something to write home about. Just $16.99/mo. or less. dsl.yahoo.com

2 1

Mutually exclusive options in boost::program_options?
by Marshall Clow 09 Jan '06

09 Jan '06

I'm trying to use boost::program_options for the first time, and there's a couple things that I am tripping over. The first is the idea of mutually exclusive options. I can't find any support for them in the library, and that surprises me - to the point of asking for help. I have two options, only one of which can be specified; say -frtti and -fno_rtti (say). The other one is that program_options, by default, wants to use double hyphens to define options: "foo --option1 --option2" I'm a lot more comfortable with single hyphens: "foo -option1 -option2" Am I missing something basic here? -- -- Marshall Marshall Clow Idio Software <mailto:marshall@idio.com> It is by caffeine alone I set my mind in motion. It is by the beans of Java that thoughts acquire speed, the hands acquire shaking, the shaking becomes a warning. It is by caffeine alone I set my mind in motion.

2 3

Error when including date_time files
by Rob Marsden 09 Jan '06

09 Jan '06

I am having trouble with some date_time files. The following code (from the boost documentation): #include "boost/date_time/posix_time/posix_time.hpp" #include "boost/date_time/local_time_adjustor.hpp" #include "boost/date_time/c_local_time_adjustor.hpp" #include <iostream> int main() { return(0); } gives me errors C:\LOCAL\INCLUDE/boost/date_time/posix_time/time_formatters_limited.hpp(77): error: more than one operator "<<" matches these operands: function "std::basic_ostream<_E, _Tr>::operator<<(std::_Bool={bool={bool}}) [with _E=char, _Tr=std::char_traits<char>]" function "std::basic_ostream<_E, _Tr>::operator<<(short) [with _E=char, _Tr=std::char_traits<char>]" function "std::basic_ostream<_E, _Tr>::operator<<(unsigned short) [with _E=char, _Tr=std::char_traits<char>]" function "std::basic_ostream<_E, _Tr>::operator<<(int) [with _E=char, _Tr=std::char_traits<char>]" function "std::basic_ostream<_E, _Tr>::operator<<(unsigned int) [with _E=char, _Tr=std::char_traits<char>]" function "std::basic_ostream<_E, _Tr>::operator<<(long) [with _E=char, _Tr=std::char_traits<char>]" function "std::basic_ostream<_E, _Tr>::operator<<(unsigned long) [with _E=char, _Tr=std::char_traits<char>]" function "std::basic_ostream<_E, _Tr>::operator<<(float) [with _E=char, _Tr=std::char_traits<char>]" function "std::basic_ostream<_E, _Tr>::operator<<(double) [with _E=char, _Tr=std::char_traits<char>]" function "std::basic_ostream<_E, _Tr>::operator<<(long double) [with _E=char, _Tr=std::char_traits<char>]" operand types are: std::basic_ostream<char, std::char_traits<char>> << boost::posix_time::time_duration::fractional_seconds_type << frac_sec; ^ C:\LOCAL\INCLUDE/boost/date_time/posix_time/time_formatters_limited.hpp(140): error: more than one operator "<<" matches these operands: ...similar ^ C:\LOCAL\INCLUDE/boost/lexical_cast.hpp(156): error: no operator ">>" matches these operands operand types are: std::basic_stringstream<char, std::char_traits<char>, std::allocator<char>> >> boost::int64_t stream >> output && ^ detected during: instantiation of "bool={bool} boost::detail::lexical_stream<Target, Source>::operator>>(InputStreamable &) [with Target=boost::int64_t={__int64}, Source=boost::detail::array_to_pointer_decay<std::basic_string<char, std::char_traits<char> , std::allocator<char>>>::type, InputStreamable=boost::int64_t={__int64}]" at line 221 instantiation of "Target boost::lexical_cast<Target,Source>(const Source &) [with Target=boost::int64_t={__int64}, Source=std::basic_string<char, std::char_traits<char>, std::allocator<char>>::_Myt]" at line 94 of "C:\LOCAL\INCLUDE/boost /date_time/time_parsing.hpp" instantiation of "time_duration boost::date_time::parse_delimited_time_duration<time_duration>(const std::string &) [with time_duration=boost::posix_time::time_duration]" compilation aborted for C:\Research\DogWood\TextAnalysis\Parser\BoostTest\BoostTest.cpp (code 2) Error executing xicl6.exe. The environment is compiler Intel v9.0 in the VC6 IDE under Win2k Can anyone suggest a solution? -- Rob Marsden Gistix (Northern) Limited

2 1

[MPL] sorting sequence according to inheritance hierarchy
by Slawomir Lisznianski 09 Jan '06

09 Jan '06

Hello, I'm trying to find a solution to the following problem. Given types A, B and C such that C is derived from B and B is derived from A, and a sequence S1 which stores A, B and C (in arbitrary order): 1) transform S1 so resulting sequence S2 would have elements sorted according to their relative position within their inheritance hierarchy (say, most derived first). 2) when one introduces another type, D, which doesn't inherit from any of A, B or C, after sorting S1, it would end up at the end of S2. 3) the solution needs to be unintrusive for the "input" types, that is, it ought to work for existing types. Example ------- Input: S1 = { A, C, D, B }; Expected result, after sorting: S2 = { C, B, A, D }; Purpose ------- By finding a way to sort S1 according to predicates listed above, I hope to come up with a generic exception-handling mechanism (used in RPC-like library), example: typedef vector<E0, E1, .. ,En> sorted_exception_decl; try { func(); } catch(at<sorted_exception_decl, int_<0> >::value const & E0) { .. } catch(at<sorted_exception_decl, int_<1> >::value const & E1) { .. } catch(at<sorted_exception_decl, int_<n> >::value const & En) { .. } Your thoughts on how sane this idea is are greatly appreciated. -- Slawomir Lisznianski Paramay Group, LLC "Programs for Research Machinery"

2 2

date_time: convert to and from a timeval
by Thomas Lemaire 09 Jan '06

09 Jan '06

Dear list, I would like to convert ptime and time_duration to and from the standard timeval type. So that I can use all the operators available for ptime and time_duration I found that this topic has already been discussed here: http://lists.boost.org/Archives/boost/2003/06/49197.php The conclusion was: "" Ok will do. I'll add some protections or rounding for when durations support higher than microsecond resolution. I'll let you know when this gets added. Thx, Jeff "" This message was sent on 2003-06-23. I cannot find any thing related to timeval in the doc of boost 1.33. Did I miss something ? Also doc about xtime in boost.threads does not help that much... http://www.boost.org/doc/html/xtime.html cheers, -- thomas

2 1

iterators
by jens-theisen＠gmx.de 09 Jan '06

09 Jan '06

Hello, Say a library programmer wants to make a virtual interface to his class with a function that returns a collection of things. Usually one end up writing something silly like class interface { ... virtual std::vector< ... > give_stuff() const; }; which has some disadvantages, the most important being: - The implementing function must calculate the whole result, even if some of it might not be needed. Especially infinite collections of things are not possible in this way. - The vector is a container and that's a poorly defined concept. As a consequence, we can't do very much with it. For instance, you can't write give_stuff() + give_more_stuff() to concatenate. Though it's easy to implement that, we really don't want to do this on the basis of containers in general and we also don't want to do it again and again in every single project for std::vector in particular. - As the library gets used, it's poor interface is carved in stone, and so are the other two problems for it. The first problem can be addressed by using an iterator to some container. We obviouly can't use an iterator to a vector since that wouldn't solve any problems. It has to be a custom iterator class lib_iterator_impl : ... { ... virtual ... dereference() const; virtual ... advance() const; }; class lib_iterator { ... lib_iterator(lib_iterator_impl const* impl); }; class interface { ... virtual lib_iterator give_stuff() const; }; where lib_iterator_impl than has to be extended by the client of the library. Actually, there is no real need for lib_iterator to be a proper iterator in the standard sense. Especially, such iterators could be aware of there ends (or even their beginnings) to make it unnecessary to have always two of them. Both the virtualisation and halving the number of those iterators would also reduce the complexity of error messages. On such a framework, many small building blocks could be build, like concatenation, filtering, mapping, cartesian products, etc. In my opinion, at least the very low-level parts of such a framework are so important that they belong in boost. My question at this point is in what regard people share this opinion and to what extend we already have these things. I have heard of any_iterator in the past, but I can't find anything about it in the boost malings list archives or google, which would be related to this. Other than this, I'm not aware of anything in this regard. Cheers, Jens

4 3

Re: [Boost-users] Please don't reply to digests
by Phil Endecott 08 Jan '06

08 Jan '06

David Abrahams wrote: > Please don't reply to digests. > > http://www.boost.org/more/discussion_policy.htm#quoting Which says: Do not reply to digests if you are a digest delivery subscriber. Your reply will not be properly threaded and will probably have the wrong subject line. Instead, you can reply through the GMane web interface. The GMane interface doesn't work for posting messages, I've tried it; the mailing list rejects messages from non-subscribers, including those that come via GMane. There is a trade-off here: - On one hand, replying to digests means that threaded views using references: headers will not work properly. (There is no need for the subject line to be wrong, but it isn't difficult to forget to change it when replying.) - On the other hand, prohibiting digest subscribers (like me) from sending replies means that you won't hear from me again. You may or may not consider that a good thing. I do try to reply to questions on the rare occassions that someone even newer to Boost than me asks a question that I have an answer to, and I do so in the hope that this lets the more expert readers (Dave!) concentrate on more important things. I'd like to encourage a debate - which is considered more important, better threading or more contributions? If you don't want to hear from me again, that's fine, I'll unsubscribe until I next have a question of my own to ask. Regards, --Phil.

2 1

installing BGL-python
by Jeff Abrahamson 08 Jan '06

08 Jan '06

I'm installing the Boost Graph Library python bindings on a Debian testing machine. BGL-python appears not to be available as a .deb, so I am installing from source. http://www.osl.iu.edu/~dgregor/bgl-python/ The readme suggests I run $BOOST_ROOT/tools/build/jam_src/build.sh. This directory exists, but the file does not. It also suggests I run "bjam <options>". I can't think of any options I want a priori [ ;-) ] so I run bjam with no options, but to no avail: jeff@krypton:bgl-python-0.9 $ bjam Unable to load Boost.Build: could not find "boost-build.jam" --------------------------------------------------------------- Attempted search from /home/jeff/tmp/bgl-python-0.9 up to the root and in these directories from BOOST_BUILD_PATH and BOOST_ROOT: /usr/share/boost-build. Please consult the documentation at 'http://www.boost.org'. jeff@krypton:bgl-python-0.9 $ BTW, Boost.Build does not exist on my machine. I'm not clear on what should cause it to exist. Googling largely points me to the above. I'm a bit confused, clearly. Can anyone offer a pointer? Thanks much. -- Jeff Jeff Abrahamson <http://www.purple.com/jeff/> +1 215/837-2287 GPG fingerprint: 1A1A BA95 D082 A558 A276 63C6 16BF 8C4C 0D1D AE4B

5 5

[Boost.Python] newbie: Lifetime of objects
by Sergey Sikorskiy 08 Jan '06

08 Jan '06

Hello everyone. I'm trying to map into python classes shown below. class A { friend class B; public: ~A(void) {} private: A(B& b) : m_B(&b) { } B* m_B; }; class B { friend class C; public: ~B(void) {} A* make_a(void) { return new A(*this); } private: B(C& c) : m_C(&c) { } C* m_C; }; class C { public: ~C(void) {} B* make_b(void) { return new B(*this); } }; C* make_c() { return new C(); } Objects are supposed to be created in the order C, B, A and destroyed in the order A, B, C. I do not want to map constructors of A, B and C. I can see three ways to do what I want: 1) class_<A>("A", no_init); class_("B", no_init) .def("make_a", &B::make_a, return_internal_reference<>()) ; class_<C>("C", no_init) .def("make_b", &C::make_b, return_internal_reference<>()) ; def("make_c", make_c, return_value_policy<manage_new_object>()); 2) class_<A>("A", no_init); class_("B", no_init) .def("make_a", &B::make_a, return_value_policy<manage_new_object>()) ; class_<C>("C", no_init) .def("make_b", &C::make_b, return_value_policy<manage_new_object>()) ; def("make_c", make_c, return_value_policy<manage_new_object>()); 3) class_<A, shared_ptr<A>, noncopyable>("A", no_init); class_<B, shared_ptr, noncopyable>("B", no_init) .def("make_a", &B::make_a, return_value_policy<manage_new_object>()) ; class_<C, shared_ptr<C>, noncopyable>("C", no_init) .def("make_b", &C::make_b, return_value_policy<manage_new_object>()) ; def("make_c", make_c, return_value_policy<manage_new_object>()); C::make_b and B::make_a are supposed to return shared_ptr and shared_ptr<A> respectively in this case. After debugging this code I've got strange results: - In case 1 objects aren't get deleted at all; - In case 2 objects are get deleted in wrong order; - In case 3 objects are get deleted in wrong order; Cases 2 and three seem to be identical to me. The only difference I can see is that in case 3 I should manage objects lifetime by myself from C++ code. In opposite, in case 2 objects lifetime will be managed by python. I couldn't get an answer to my problem neither from documentation nor from Boost.Python tests nor from Google. Any explanations or suggestions will be greatly appreciated. Thank you. -- Sergey Sikorskiy

2 1

Re: [Boost-users] Boost-users Digest, Vol 760, Issue 2
by Ryan McGann 08 Jan '06

08 Jan '06

On Dec 19, 2005, at 9:00 AM, boost-users-request(a)lists.boost.org wrote: >> 1) The build.sh file for the boost bjam tool in the 1.33.0 and 1.33.1 >> release seems to have DOS line endings. I know there are prebuilt >> binaries of bjam up on the Web, but our build system builds it >> manually, and it choked on Darwin because sh didn't like the DOS line >> endings. I resaved the file with Unix line endings and it built fine. > > Did you download the tar.gz distribution? That should have Unix line > endings throughout where as the .zip file has DOS line endings > throughout > (intensionally). Well our build system uses whichever archive is checked in. I imagine the PC folks downloaded the .zip version. I can check in a different version for the Unix folks. >> 2) I get errors for multiply defined symbols for the placeholder >> symbols declared in boost/bind/placeholders.hpp. Every file that >> #include <boost/bind.hpp> contains actual instances of _1, _2, etc. >> Changing the declarations of these in boost/bind.hpp to static (I >> added a __APPLE__ to the #ifdef in the middle of the file) fixes this >> issue, but then I get warnings for unused static symbols if I don't >> use the placeholder objects. This issue in particular is quite >> annoying. > > What compiler are you using? The first #if says: > > #if defined(__BORLANDC__) || defined(__GNUC__) > > isn't this the branch that gets taken? Hm in my boost/placeholders.hpp, I see #if defined(__BORLANDC__) ... #elif defined(BOOST_MSVC) || (defined(__DECCXX_VER) && __DECCXX_VER <= 60590031) || defined(__MWERKS__) ... #else ... #endif I don't have a _GCC__ anywhere in there. This is from 1.33.1 (which I just newly expanded from the .tar.gz, not the .zip). If I add a defined(__GCC__) to the first or second set of #ifdefs, it works fine. >> 3) The header in boost/compatibility/cpp_c_headers/cstdio >> does not match up with the cstdio file included with the Mac OS X dev >> tools. >> In particular it is missing a using ::snprintf, which causes problems >> because this cstdio file is being included BEFORE the Mac OS X >> version of the same file, and other C++ header files rely on >> std::snprtinf being declared. I fixed this at first by deleting the >> boost/compatibility/cpp_c_headers folder, but then ending up just >> deleting that single file so that OS X always used the built-in >> header file. > > Why are those headers getting included? They were intended for use > only > with certain broken compilers that didn't have the c-prefixed std lib > headers. They're known not to work with several std conforming > compilers > (but shouldn't be included for these anyway). I'm not sure why they're being included. I'm guessing it's because we pass -I<path to boost> to GCC, which causes it to search inside of that directory before the standard directories get searched. I'll have to investigate that further. Thanks, Ryan

3 2

[Graph] Maximum common subgraph
by Andreas Sæbjørnsen 08 Jan '06

08 Jan '06

Hi, Lately I have been looking for a good C/C++ implementation of an algorithm for finding the maximum common subgraph in Boost::Graph. The algorithms I have looked for is mainly Bron-Kerbosch and the MCS algorithm, but I am very open for alternatives. The implementation must be able to handle directed graphs containing self-loops (it is possible to have two edges at the same time between two nodes i->j, j->i). Do you know of any implementation? Thanks Andreas Saebjornsen

6 9

Bjam problems with intel compiler on Windows when building Boost1.3.2
by Miller, Peter 08 Jan '06

08 Jan '06

Hi, list members. I am trying to build Boost (1_32_0) using intel/Windows compiler, but no dice. Following the steps in the "Getting started" guide, I chose to set up the environment variables, i.e. approach 2.1 So I pull up a command window, navigate to the intel directory, and run iclvars to establish the intel directory is in the PATH. It adds a bunch of items to the path, so it seems that worked. Then, I navigate to boost\boost_1_32_0\boost\1_32_0 where bjam.exe lives. I use it as-received, as it seemed there was no point in building it locally. Invocation to make Boost libraries I used was: bjam "-sTOOLS=intel-win32" install What I get is odd: first, a notice: skipping Boost.Python library build due to missing or incorrect configuration couldn't find python.h in "c:/tools/python/include" THis is puzzling to me: there is no Python setup on this machine - and why should Boost (a c++ package) be looking to create Python libraries? anyhow, there is a bit more info about various PYTHON_xxxx variables that I could set to configure the python installation. Then, it gets into the c++ compilation, and all these fail. The invocation that is shown in the command window is (for example): vc-C++ bin\boost\libs\date_time\build\libboost_date_time.lib\intel-win32 \debug\runtime-link-static\greg_month.obj '/Zm800' is not recognized as an internal or external comand, operable program or batch file. /Zm800 -nologo /EHsc -c -DBOOST_DATE_TIME_STATIC_LINK .Z7 etc. To me (who doesn't understand bjam), it seems that bjam has invoked the VC compiler rather than the intel compiler (which has an invocation of icl, IIRC). Anyhow, it looks like the compiler is hollering about the /Zm800 option, which is not a legal option for the intel compiler, though it is for VS 7.1. This error then repeats several hundred times, once for each file for which compilation is attempted. I suspect there is some very simple thing I am overlooking, but I've tried to follow every step in the "Getting Started" guide. Does anyone suggestions on what is wrong here? I'm stumped, and would appreciate any help or thoughts on how to chase this further. Thanks! Peter

2 1

boost and VC++ toolkit 2003
by Raphael Bousquet 08 Jan '06

08 Jan '06

I was wondering the Visual C++ Toolkit 2003 was going to be a future platform for boost. I believe no port is necessary just the appropriate bjam configuration. I have tried using the "vc-7_1" option but even though most of the libraries are created, when you try to use them, files such as msvcptr.lib are requested (though this does not generate any error during the compilation)... Maybe there is a workaround already? If anyone has any experience with that... The best link I have found so far is: http://groups.google.com/group/boost-list/browse_thread/thread/d9e9ba8e6c9c5 fa0/7a963d8e2eee9a4d?lnk=st&q=vc%2B%2B+toolkit+boost&rnum=1&hl=en#7a963d8e2e ee9a4d Thanks

3 4

Problem with program_options.
by Simen Kvaal 06 Jan '06

06 Jan '06

Dear all, I have problems with the program_options library. I am using boost 1.33.1 and gcc 3.2.3, and I notice that there are others with the same problem. However, I cannot find a reference to with a solution anywhere. Stated simply: My programs (even the example programs included with boost 1.33.1) using program_options do not link! For example (gcc 3.2.3): $ g++ -o first.x first.cpp /tmp/ccM0BLhg.o(.text+0x4a): In function `main': : undefined reference to `boost::program_options::options_description::options_description(std::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, unsigned int)' [ ... and a dozen more similar errors ... ] (As far as I can see, all header files in boost/program_options/ are included in boost/program_options.hpp.) I would appreciate any help with this. Regards, Simen Kvaal. -- ---- Simen Kvaal -- Ph.D student --------+------------------------- Centre of Mathematics for Applications | cell: +47 90199552 Room 1039, N.H.Abel's House, UiO | office: +47 22855681 http://folk.uio.no/simenkva/ | simen.kvaal(a)cma.uio.no

4 3

iostreams: example code of walk into zip file's filename/subdir
by David Xiao 06 Jan '06

06 Jan '06

Hi Friends: I am looking for a piece of code which can: input a .zip file name and provide a callback facility which allow me walking in file structure, as well as survive from corrupted zip file. I had read the example code and test code of zlib part in boost::iostreams, it extract data like this: //-- copy from iostreams/filter/test.hpp --// template<typename OutputFilter, typename InputFilter> bool test_filter_pair( OutputFilter out, InputFilter in, const std::string& data, mpl::true_ ) { for ( int inc = default_increment; inc <= default_increment * 40; inc += default_increment ) { array_source src(data.data(), data.data() + data.size()); std::string temp; std::string dest; iostreams::copy(src, compose(out, non_blocking_sink(temp, inc))); iostreams::copy( compose(in, non_blocking_source(temp, inc)), iostreams::back_inserter(dest) ); if (dest != data) return false; } return true; } I think it is not gentle because it try catch all data into memory. So there must be some better way to do? Rgds, David Xiao

1 0

date_time: convert to and from a timeval
by Thomas Lemaire 06 Jan '06

06 Jan '06

Dear list, I would like to convert ptime and time_duration to and from the standard timeval type. So that I can use all the operators available for ptime and time_duration I found that this topic has already been discussed here: http://lists.boost.org/Archives/boost/2003/06/49197.php The conclusion was: "" Ok will do. I'll add some protections or rounding for when durations support higher than microsecond resolution. I'll let you know when this gets added. Thx, Jeff "" This message was sent on 2003-06-23. I cannot find any thing related to timeval in the doc of boost 1.33. Did I miss something ? Also doc about xtime in boost.threads does not help that much... http://www.boost.org/doc/html/xtime.html cheers, -- thomas

1 0

[serialization] assert when serializing polymorphic type to XML (Visual Studio 8)
by Terence Wilson 06 Jan '06

06 Jan '06

I have condensed a short example which is appended to this message. The code tries to write then read a polymorphic class via a base pointer. The assertion I am seeing is assert(NULL != bpos_ptr); in oserializer.hpp. The documentation indicates that the problem is likely a lack of registration of the class, however, I have done this. Interestingly the code only fails for XML archive type. // BoostPolymorphicSerialize.cpp : Defines the entry point for the console application. // #include <stdio.h> #include <tchar.h> #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/export.hpp> #include <boost/shared_ptr.hpp> #include <boost/shared_array.hpp> #include <boost/serialization/shared_ptr.hpp> #include "boost/archive/xml_iarchive.hpp" #include "boost/archive/xml_oarchive.hpp" class CMyBaseClass { public: CMyBaseClass(void):m_BaseValue(0){} public: virtual ~CMyBaseClass(void){} int m_BaseValue; friend class boost::serialization::access; template<class Archive> void serialize(Archive & ar, const unsigned int /* file_version */) { ar & BOOST_SERIALIZATION_NVP(m_BaseValue); } }; class CMyDerivedClass : public CMyBaseClass { public: CMyDerivedClass(void):m_DerivedValue(1){} public: ~CMyDerivedClass(void){} int m_DerivedValue; friend class boost::serialization::access; template<class Archive> void serialize(Archive & ar, const unsigned int /* file_version */) { BOOST_SERIALIZATION_BASE_OBJECT_NVP(CMyBaseClass); ar & BOOST_SERIALIZATION_NVP(m_DerivedValue); } }; BOOST_CLASS_EXPORT_GUID(CMyBaseClass, "CMyBaseClass") BOOST_CLASS_EXPORT_GUID(CMyDerivedClass, "CMyDerivedClass") int _tmain(int argc, _TCHAR* argv[]) { const CMyBaseClass* const pMyBaseClass=new CMyDerivedClass(); const std::string fileName("c:\\docs\\BoostSerializeTest.xml"); CMyBaseClass* pMyBaseClass2=0; try { { std::ofstream ofs(fileName.c_str()); assert(ofs.good()); boost::archive::xml_oarchive oa(ofs); //boost::archive::text_oarchive oa(ofs); oa << BOOST_SERIALIZATION_NVP(pMyBaseClass); } { std::ifstream ifs(fileName.c_str()); assert(ifs.good()); boost::archive::xml_iarchive ia(ifs); //boost::archive::text_iarchive ia(ifs); ia >> BOOST_SERIALIZATION_NVP(pMyBaseClass2); } } catch(std::exception& e) { std::cout << e.what() << std::endl; } delete pMyBaseClass; delete pMyBaseClass2; return 0; }

2 5

Re: [Boost-users] [Boost.Program_options] Is there a way to havealloptions specifiedwith a single dash instead of double?
by Guy Peled 06 Jan '06

06 Jan '06

Okay, I finally found out the missing part. In case someone else is looking for the same info, here's my finding: There's additional flags that can be used to control this behavior, specifically the command_line_style::style_t::allow_long_disguise is the one that will make single dash options work exactly like double-dash. Here's an example : namespace po = boost::program_options; po::command_line_style::style_t style = po::command_line_style::style_t( po::command_line_style::unix_style | po::command_line_style::case_insensitive | po::command_line_style::allow_long_disguise ); string inputFilename; string statelessTeslaMethodsFilename; string strConfigFile; po::options_description desc2; desc2.add_options() ( "config-file", po::value< std::string >( & strConfigFile )->default_value( "jaja" ) ); po::variables_map vm2; po::store(po::parse_command_line(argc, argv, desc2, style ), vm2); po::notify(vm2); Enjoy, Guy. ________________________________ From: Guy Peled Sent: Thursday, January 05, 2006 9:15 AM To: 'boost-users(a)lists.boost.org' Subject: RE: [Boost-users] [Boost.Program_options] Is there a way to havealloptions specifiedwith a single dash instead of double? Hmmm...I must be missing something very obvious. Trying your example, I still don't seem to be able to use -config-file, but only --config-file. Here's my code snippet: string strConfigFile; po::options_description desc2; desc2.add_options() ( "config-file", po::value< std::string >( & strConfigFile )->default_value( "jaja" ) ); po::variables_map vm2; po::store(po::parse_command_line(argc, argv, desc2), vm2); po::notify(vm2); And this is accepted fine: --config-file foo While this throws an 'unkown option -c': -config-file foo Any insights into what may be causing such a difference in behaviot? Thanks Guy, ________________________________ From: boost-users-bounces(a)lists.boost.org [mailto:boost-users-bounces@lists.boost.org] On Behalf Of Alexandre Gacon Sent: Thursday, January 05, 2006 8:46 AM To: boost-users(a)lists.boost.org Subject: Re: [Boost-users] [Boost.Program_options] Is there a way to havealloptions specifiedwith a single dash instead of double? No, all the args start with a single '-'. For example, with the following code: po::options_description desc; desc.add_options() ( "config-file", po::value< std::string >( & strConfigFile )->default_value( defaultConfigFilePath.native_file_string() ) ); I am able to call my program with a -config-file my_config_file.cfg command line. Alexandre ________________________________ De : boost-users-bounces(a)lists.boost.org [mailto:boost-users-bounces@lists.boost.org] De la part de Guy Peled Envoyé : jeudi 5 janvier 2006 17:21 À : boost-users(a)lists.boost.org Objet : [Boost-users] [Boost.Program_options] Is there a way to have alloptions specifiedwith a single dash instead of double? I'm interested in switching over the command line processing of an existing tool to use program_options. However, all of the args are of the format '-foo -bar -whatever 1' etc. As far as I can tell from the docs it seems like by default the program_options library assumes args all start with a '--' or have single character short names that start with a single dash. Is there a way to coerce it into the behavior I'm looking for? Thanks for any tips! Guy. _________________________________________________________________ Guy Peled Email gpeled(a)nvidia.com 3D/Tools Architect 408-486-2505 nVIDIA 2701 San Tomas Expressway www.nvidia.com <file:///\\www.nvidia.com> Santa Clara, CA 95050 _________________________________________________________________

1 0

Re: [Boost-users] [Boost.Program_options] Is there a way to havealloptions specifiedwith a single dash instead of double?
by Guy Peled 05 Jan '06

05 Jan '06

Hmmm...I must be missing something very obvious. Trying your example, I still don't seem to be able to use -config-file, but only --config-file. Here's my code snippet: string strConfigFile; po::options_description desc2; desc2.add_options() ( "config-file", po::value< std::string >( & strConfigFile )->default_value( "jaja" ) ); po::variables_map vm2; po::store(po::parse_command_line(argc, argv, desc2), vm2); po::notify(vm2); And this is accepted fine: --config-file foo While this throws an 'unkown option -c': -config-file foo Any insights into what may be causing such a difference in behaviot? Thanks Guy, ________________________________ From: boost-users-bounces(a)lists.boost.org [mailto:boost-users-bounces@lists.boost.org] On Behalf Of Alexandre Gacon Sent: Thursday, January 05, 2006 8:46 AM To: boost-users(a)lists.boost.org Subject: Re: [Boost-users] [Boost.Program_options] Is there a way to havealloptions specifiedwith a single dash instead of double? No, all the args start with a single '-'. For example, with the following code: po::options_description desc; desc.add_options() ( "config-file", po::value< std::string >( & strConfigFile )->default_value( defaultConfigFilePath.native_file_string() ) ); I am able to call my program with a -config-file my_config_file.cfg command line. Alexandre ________________________________ De : boost-users-bounces(a)lists.boost.org [mailto:boost-users-bounces@lists.boost.org] De la part de Guy Peled Envoyé : jeudi 5 janvier 2006 17:21 À : boost-users(a)lists.boost.org Objet : [Boost-users] [Boost.Program_options] Is there a way to have alloptions specifiedwith a single dash instead of double? I'm interested in switching over the command line processing of an existing tool to use program_options. However, all of the args are of the format '-foo -bar -whatever 1' etc. As far as I can tell from the docs it seems like by default the program_options library assumes args all start with a '--' or have single character short names that start with a single dash. Is there a way to coerce it into the behavior I'm looking for? Thanks for any tips! Guy. _________________________________________________________________ Guy Peled Email gpeled(a)nvidia.com 3D/Tools Architect 408-486-2505 nVIDIA 2701 San Tomas Expressway www.nvidia.com <file:///\\www.nvidia.com> Santa Clara, CA 95050 _________________________________________________________________

1 0

[Boost.Program_options] Is there a way to have all options specifiedwith a single dash instead of double?
by Guy Peled 05 Jan '06

05 Jan '06

I'm interested in switching over the command line processing of an existing tool to use program_options. However, all of the args are of the format '-foo -bar -whatever 1' etc. As far as I can tell from the docs it seems like by default the program_options library assumes args all start with a '--' or have single character short names that start with a single dash. Is there a way to coerce it into the behavior I'm looking for? Thanks for any tips! Guy. _________________________________________________________________ Guy Peled Email gpeled(a)nvidia.com 3D/Tools Architect 408-486-2505 nVIDIA 2701 San Tomas Expressway www.nvidia.com Santa Clara, CA 95050 _________________________________________________________________

2 1

bjam build failed (vc7)
by Roman Gershman 05 Jan '06

05 Jan '06

Dear All, I got a trouble with building bjam.exe and I need your help. I downloaded boost 1.33.1 today and put it into c:\boost_1_33_1 directory. I failed to build bjam.exe when running build.bat from tools\build\jam_src directory. The outputs of the first and second runs (1.txt and 2.txt respectively) of the build.bat are attached. I have Visual Net 2003 with windows xp sp2 32bit on AMD athlon x2 64 (dual core). The interesting thing is that the script creates (empty) directory c:\bin.ntx86 during its run. I guess it should not happen since it should be created in jam_src. Moreover, when I take bjam.exe from other place, put it into my computer and try to build boost I get similar results : bjam creates directories "bin", "stage" in the root directory (c:\) instead of creating it in c:\boost1.33.1 Thanks in advance, Roman Gershman

2 2

Is boost compilation supported with VC 7.0 (Visual Studio 2002)?
by Allen Zhao 05 Jan '06

05 Jan '06

Hi, All, I am having troubles to compile libtorrent 0.9.1 which depends on boost 1.33+. From the error messages, boost does not work very well with Visual Studio 2002. What puzzles me more is that if I just build the boost alone by invoking bjam in the boost directory, I still can not build the whole library because of the spirit section; but all the errors as reported below does not appear. This seems to indicate some compiler options issues. Is there any successful story that you can share with me with regards to VC 7.0 compilation? Any pointers are welcome. The errors I have seem so far at enclosed at the end. The libtorrent only depends on boost:filesystem, boost:date_time and boost::thread. Best regards, Allen Zhao -------------------------- Following are some of the messages related to boost: 1) <boost\filesystem\operations.hpp>'s BOOST_OPERATOR_TEMPLATE definition: msvc.compile.c++ bin\msvc\debug\threading-multi\allocate_resources.obj allocate_resources.cpp C:\boost_1_33_1\boost\filesystem\operations.hpp(56) : error C2955: 'boost::equivalent' : use of class template requires template argument list C:\boost_1_33_1\boost\operators.hpp(820) : see declaration of 'boost::equivalent' call "C:\Program Files\Microsoft Visual Studio .NET\Vc7\bin\vcvars32.bat" > nul cl /Zm800 -nologo -TP /Z7 /Od /Ob0 /GR /MDd /wd4675 /EHs /Zc:forScope /Zc:wchar_t @"bin\msvc\debug\threading-multi\allocate_resources.obj.rsp" -c -Fo"bin\msvc\debug\threading-multi\allocate_resources.obj" && del /f "bin\msvc\debug\threading-multi\allocate_resources.obj.rsp" ...failed msvc.compile.c++ bin\msvc\debug\threading-multi\allocate_resources.obj... 2) boost::bind(std::less<int>(), _1, 0)) (libtorrent/src/session.cpp) msvc.compile.c++ bin\msvc\debug\threading-multi\session.obj session.cpp src\session.cpp(1613) : error C2780: 'boost::_bi::bind_t<R,boost::_mfi::dm<R,T>,boost::_bi::list_av_1<R>::type> boost::bind(R T::* ,A1)' : expects 2 arguments - 3 provided C:\boost_1_33_1\boost\bind.hpp(1616) : see declaration of 'boost::bind' src\session.cpp(1613) : error C2780: 'boost::_bi::bind_t<R,boost::_mfi::cmf8<R,T,B1,B2,B3,B4,B5,B6,B7,B8>,boost::_bi::list_av_9<R,T,B1,B2,B3,B4,B5,B6,B7>::type> boost::bind(R (__thiscall T::* )(B1,B2,B3,B4,B5,B6,B7,B8) const,A1,A2,A3,A4,A5,A6,A7,A8,A9)' : expects 10 arguments - 3 provided .... 3) msvc.compile.c++ bin\msvc\debug\threading-multi\storage.obj storage.cpp C:\boost_1_33_1\boost\lambda\detail\arity_code.hpp(61) : error C2065: 'T' : undeclared identifier C:\boost_1_33_1\boost\lambda\detail\arity_code.hpp(61) : error C2687: cannot define a nested UDT of a template class out of line C:\boost_1_33_1\boost\lambda\detail\arity_code.hpp(61) : fatal error C1903: unable to recover from previous error(s); stopping compilation call "C:\Program Files\Microsoft Visual Studio .NET\Vc7\bin\vcvars32.bat" > nul cl /Zm800 -nologo -TP /Z7 /Od /Ob0 /GR /MDd /wd4675 /EHs /Zc:forScope /Zc:wchar_t @"bin\msvc\debug\threading-multi\storage.obj.rsp" -c -Fo"bin\msvc\debug\threading-multi\storage.obj" && del /f "bin\msvc\debug\threading-multi\storage.obj.rsp" ...failed msvc.compile.c++ bin\msvc\debug\threading-multi\storage.obj... 4) src\torrent.cpp(218) : error C2065: 'complete' : undeclared identifier C:\boost_1_33_1\boost\tuple\detail\tuple_basic_no_partial_spec.hpp(471) : error C2039: 'map_tuple_to_cons' : is not a member of 'boost::detail' src\torrent.cpp(476) : see reference to class template instantiation 'boost::tuple<T1,T2,T3,T4,T5,T6,T7,T8,T9,T10>' being compiled with [ T1=libtorrent::size_type, T2=libtorrent::size_type, T3=boost::tuples::null_type, T4=boost::tuples::null_type, T5=boost::tuples::null_type, T6=boost::tuples::null_type, T7=boost::tuples::null_type, T8=boost::tuples::null_type, T9=boost::tuples::null_type, T10=boost::tuples::null_type ]

3 5

Wild Compile Errors with ptime member
by Merrill Cornish 04 Jan '06

04 Jan '06

I am running Boost 1.33.0 and compiling wiht MinGW. When I compile the following source file ========================= #include "boost/shared_ptr.hpp" #include "boost/test/test_tools.hpp" #include "boost/date_time/posix_time/posix_time_types.hpp" class foo { public: foo() {} ~foo() {} boost::posix_time::ptime mExecutionStart; }; class foo_test { foo_test(); ~foo_test(); void run(); }; void foo_test::run() { boost::shared_ptr<foo> testObj(new foo()); BOOST_CHECK_EQUAL(testObj->mExecutionStart, testObj->mExecutionStart); }; ================================= I get the (lengthy) compiler error output below. As you can see, something seems to be trying to log something to an output stream. The test compile just fine as long as the BOOST_CHECK_EQUAL() doesn't reference a boost::posix_time::ptime variables. Any ideas? Merrill Cornish ================================= E:/Dev-Cpp/Workflow/boost/include/boost/test/test_tools.hpp: In member function `void boost::test_tools::tt_detail::print_log_value<T>::operator()(std::ostream&, const T&) [with T = boost::posix_time::ptime]': E:/Dev-Cpp/Workflow/boost/include/boost/test/test_tools.hpp:372: instantiated from `std::ostream& boost::test_tools::tt_detail::operator<<(std::ostream&, const boost::test_tools::tt_detail::print_helper_t<T>&) [with T = boost::posix_time::ptime]' E:/Dev-Cpp/Workflow/boost/include/boost/test/utils/wrap_stringstream.hpp:66: instantiated from `boost::basic_wrap_stringstream<CharT>& boost::operator<<(boost::basic_wrap_stringstream<CharT>&, const T&) [with CharT = char, T = boost::test_tools::tt_detail::print_helper_t<boost::posix_time::ptime>]' E:/Dev-Cpp/Workflow/boost/include/boost/test/test_tools.hpp:427: instantiated from `void boost::test_tools::tt_detail::check_frwd(Pred, boost::wrap_stringstream&, boost::test_tools::const_string, size_t, boost::test_tools::tt_detail::tool_level, boost::test_tools::tt_detail::check_type, const Arg0&, const char*, const Arg1&, const char*) [with Pred = boost::test_tools::tt_detail::equal_impl_frwd, Arg0 = boost::posix_time::ptime, Arg1 = boost::posix_time::ptime]' E:/Dev-Cpp/Workflow/test/src/TimeDemo.cc:19: instantiated from here E:/Dev-Cpp/Workflow/boost/include/boost/test/test_tools.hpp:274: error: no match for 'operator<<' in 'ostr << t' E:/MinGW/bin/../lib/gcc/mingw32/3.4.2/../../../../include/c++/3.4.2/bits/ostream.tcc:63: note: candidates are: std::basic_ostream<E, T>& std::basic_ostream<_CharT, _Traits>::operator<<(std::basic_ostream<_CharT, _Traits>&(*)(std::basic_ostream<_CharT, _Traits>&)) [with _CharT = char, _Traits = std::char_traits<char>] E:/MinGW/bin/../lib/gcc/mingw32/3.4.2/../../../../include/c++/3.4.2/bits/ostream.tcc:74: note: std::basic_ostream<E, T>& std::basic_ostream<_CharT, _Traits>::operator<<(std::basic_ios<_CharT, _Traits>&(*)(std::basic_ios<_CharT, _Traits>&)) [with _CharT = char, _Traits = std::char_traits<char>] E:/MinGW/bin/../lib/gcc/mingw32/3.4.2/../../../../include/c++/3.4.2/bits/ostream.tcc:86: note: std::basic_ostream<E, T>& std::basic_ostream<_CharT, _Traits>::operator<<(std::ios_base&(*)(std::ios_base&)) [with _CharT = char, _Traits = std::char_traits<char>] E:/MinGW/bin/../lib/gcc/mingw32/3.4.2/../../../../include/c++/3.4.2/bits/ostream.tcc:121: note: std::basic_ostream<E, T>& std::basic_ostream<_CharT, _Traits>::operator<<(long int) [with _CharT = char, _Traits = std::char_traits<char>] E:/MinGW/bin/../lib/gcc/mingw32/3.4.2/../../../../include/c++/3.4.2/bits/ostream.tcc:155: note: std::basic_ostream<E, T>& std::basic_ostream<_CharT, _Traits>::operator<<(long unsigned int) [with _CharT = char, _Traits = std::char_traits<char>] E:/MinGW/bin/../lib/gcc/mingw32/3.4.2/../../../../include/c++/3.4.2/bits/ostream.tcc:98: note: std::basic_ostream<E, T>& std::basic_ostream<_CharT, _Traits>::operator<<(bool) [with _CharT = char, _Traits = std::char_traits<char>] E:/MinGW/bin/../lib/gcc/mingw32/3.4.2/../../../../include/c++/3.4.2/ostream:178: note: std::basic_ostream<_CharT, _Traits>& std::basic_ostream<_CharT, _Traits>::operator<<(short int) [with _CharT = char, _Traits = std::char_traits<char>] E:/MinGW/bin/../lib/gcc/mingw32/3.4.2/../../../../include/c++/3.4.2/ostream:189: note: std::basic_ostream<_CharT, _Traits>& std::basic_ostream<_CharT, _Traits>::operator<<(short unsigned int) [with _CharT = char, _Traits = std::char_traits<char>] E:/MinGW/bin/../lib/gcc/mingw32/3.4.2/../../../../include/c++/3.4.2/ostream:193: note: std::basic_ostream<_CharT, _Traits>& std::basic_ostream<_CharT, _Traits>::operator<<(int) [with _CharT = char, _Traits = std::char_traits<char>] E:/MinGW/bin/../lib/gcc/mingw32/3.4.2/../../../../include/c++/3.4.2/ostream:204: note: std::basic_ostream<_CharT, _Traits>& std::basic_ostream<_CharT, _Traits>::operator<<(unsigned int) [with _CharT = char, _Traits = std::char_traits<char>] E:/MinGW/bin/../lib/gcc/mingw32/3.4.2/../../../../include/c++/3.4.2/bits/ostream.tcc:179: note: std::basic_ostream<E, T>& std::basic_ostream<_CharT, _Traits>::operator<<(long long int) [with _CharT = char, _Traits = std::char_traits<char>] E:/MinGW/bin/../lib/gcc/mingw32/3.4.2/../../../../include/c++/3.4.2/bits/ostream.tcc:214: note: std::basic_ostream<E, T>& std::basic_ostream<_CharT, _Traits>::operator<<(long long unsigned int) [with _CharT = char, _Traits = std::char_traits<char>] E:/MinGW/bin/../lib/gcc/mingw32/3.4.2/../../../../include/c++/3.4.2/bits/ostream.tcc:238: note: std::basic_ostream<E, T>& std::basic_ostream<_CharT, _Traits>::operator<<(double) [with _CharT = char, _Traits = std::char_traits<char>] E:/MinGW/bin/../lib/gcc/mingw32/3.4.2/../../../../include/c++/3.4.2/ostream:219: note: std::basic_ostream<_CharT, _Traits>& std::basic_ostream<_CharT, _Traits>::operator<<(float) [with _CharT = char, _Traits = std::char_traits<char>] E:/MinGW/bin/../lib/gcc/mingw32/3.4.2/../../../../include/c++/3.4.2/bits/ostream.tcc:261: note: std::basic_ostream<E, T>& std::basic_ostream<_CharT, _Traits>::operator<<(long double) [with _CharT = char, _Traits = std::char_traits<char>] E:/MinGW/bin/../lib/gcc/mingw32/3.4.2/../../../../include/c++/3.4.2/bits/ostream.tcc:284: note: std::basic_ostream<E, T>& std::basic_ostream<_CharT, _Traits>::operator<<(const void*) [with _CharT = char, _Traits = std::char_traits<char>] E:/MinGW/bin/../lib/gcc/mingw32/3.4.2/../../../../include/c++/3.4.2/bits/ostream.tcc:307: note: std::basic_ostream<E, T>& std::basic_ostream<_CharT, _Traits>::operator<<(std::basic_streambuf<_CharT, _Traits>*) [with _CharT = char, _Traits = std::char_traits<char>] E:/MinGW/bin/../lib/gcc/mingw32/3.4.2/../../../../include/c++/3.4.2/ostream:504: note: std::basic_ostream<char, _Traits>& std::operator<<(std::basic_ostream<char, _Traits>&, const unsigned char*) [with _Traits = std::char_traits<char>] E:/MinGW/bin/../lib/gcc/mingw32/3.4.2/../../../../include/c++/3.4.2/ostream:499: note: std::basic_ostream<char, _Traits>& std::operator<<(std::basic_ostream<char, _Traits>&, const signed char*) [with _Traits = std::char_traits<char>] E:/MinGW/bin/../lib/gcc/mingw32/3.4.2/../../../../include/c++/3.4.2/bits/ostream.tcc:612: note: std::basic_ostream<char, _Traits>& std::operator<<(std::basic_ostream<char, _Traits>&, const char*) [with _Traits = std::char_traits<char>] E:/MinGW/bin/../lib/gcc/mingw32/3.4.2/../../../../include/c++/3.4.2/bits/ostream.tcc:567: note: std::basic_ostream<E, T>& std::operator<<(std::basic_ostream<E, T>&, const char*) [with _CharT = char, _Traits = std::char_traits<char>] E:/MinGW/bin/../lib/gcc/mingw32/3.4.2/../../../../include/c++/3.4.2/ostream:465: note: std::basic_ostream<char, _Traits>& std::operator<<(std::basic_ostream<char, _Traits>&, unsigned char) [with _Traits = std::char_traits<char>] E:/MinGW/bin/../lib/gcc/mingw32/3.4.2/../../../../include/c++/3.4.2/ostream:460: note: std::basic_ostream<char, _Traits>& std::operator<<(std::basic_ostream<char, _Traits>&, signed char) [with _Traits = std::char_traits<char>] E:/MinGW/bin/../lib/gcc/mingw32/3.4.2/../../../../include/c++/3.4.2/bits/ostream.tcc:505: note: std::basic_ostream<char, _Traits>& std::operator<<(std::basic_ostream<char, _Traits>&, char) [with _Traits = std::char_traits<char>] E:/MinGW/bin/../lib/gcc/mingw32/3.4.2/../../../../include/c++/3.4.2/ostream:449: note: std::basic_ostream<E, T>& std::operator<<(std::basic_ostream<E, T>&, char) [with _CharT = char, _Traits = std::char_traits<char>] make: *** [test/obj/TimeDemo.o] Error 1

3 2

boost::thread memory leak problem
by monade 04 Jan '06

04 Jan '06

Hi, I'm using vc.net and when linking with mfc71d.lib memory leaks are reported for this code: void doNothing() {} int main() { boost::thread* thrd = new boost::thread( &doNothing ); thrd->join(); delete thrd; return 0; } Does it leak on other platforms too? When I build the thread on the stack instead, everything works fine. Thx for help, Boris

1 0

graph compile error with gcc3.3 when edge container is slist
by Weiqing Guo 03 Jan '06

03 Jan '06

Hi, the attached source code is copied from boost_1_33_0/libs/graph/example/adjacency_list.cpp, I only changed the edge container to be slist, and include <slist.h> I compiled it on linux with AMD opteron 844 processor. gcc2.95.3 works fine, but gcc3.3 doesn't compile. I think the reason is slist is not in std namespace in gcc3.3, and adjacency_list.hpp doesn't handle this correctly for slist. > grep BOOST_STD_EXTENSION_NAMESPACE adjacency_list.hpp adjacency_list.hpp: typedef BOOST_STD_EXTENSION_NAMESPACE::slist<ValueType> type; adjacency_list.hpp: typedef BOOST_STD_EXTENSION_NAMESPACE::hash_set<ValueType> type; adjacency_list.hpp: typedef BOOST_STD_EXTENSION_NAMESPACE::hash_set<ValueType> type; adjacency_list.hpp: struct bind_ { typedef BOOST_STD_EXTENSION_NAMESPACE::hash_set<T, std::less<T> > type; }; adjacency_list.hpp: struct bind_ { typedef BOOST_STD_EXTENSION_NAMESPACE::hash_set<T, std::less<T> > type; }; should slist be handled the same way as hash_set ? thanks weiqing //======================================================================= // Copyright 1997, 1998, 1999, 2000 University of Notre Dame. // Authors: Andrew Lumsdaine, Lie-Quan Lee, Jeremy G. Siek // // Distributed under the Boost Software License, Version 1.0. (See // accompanying file LICENSE_1_0.txt or copy at // http://www.boost.org/LICENSE_1_0.txt) //======================================================================= #include <boost/config.hpp> #include <iostream> #include <vector> #include <slist.h> #include <utility> #include <string> #include <boost/graph/adjacency_list.hpp> #include <boost/graph/graph_utility.hpp> #include <boost/property_map.hpp> /* Sample Output graph name: foo 0 --joe--> 1 1 --joe--> 0 --curly--> 2 --dick--> 3 2 --curly--> 1 --tom--> 4 3 --dick--> 1 --harry--> 4 4 --tom--> 2 --harry--> 3 (0,1) (1,2) (1,3) (2,4) (3,4) removing edge (1,3): 0 --joe--> 1 1 --joe--> 0 --curly--> 2 2 --curly--> 1 --tom--> 4 3 --harry--> 4 4 --tom--> 2 --harry--> 3 (0,1) (1,2) (2,4) (3,4) */ struct EdgeProperties { EdgeProperties(const std::string& n) : name(n) { } std::string name; }; struct VertexProperties { std::size_t index; boost::default_color_type color; }; int main(int , char* []) { using namespace boost; using namespace std; typedef adjacency_list<slistS, listS, undirectedS, VertexProperties, EdgeProperties> Graph; const int V = 5; Graph g(V); property_map<Graph, std::size_t VertexProperties::*>::type id = get(&VertexProperties::index, g); property_map<Graph, std::string EdgeProperties::*>::type name = get(&EdgeProperties::name, g); boost::graph_traits<Graph>::vertex_iterator vi, viend; int vnum = 0; for (boost::tie(vi,viend) = vertices(g); vi != viend; ++vi) id[*vi] = vnum++; add_edge(vertex(0, g), vertex(1, g), EdgeProperties("joe"), g); add_edge(vertex(1, g), vertex(2, g), EdgeProperties("curly"), g); add_edge(vertex(1, g), vertex(3, g), EdgeProperties("dick"), g); add_edge(vertex(2, g), vertex(4, g), EdgeProperties("tom"), g); add_edge(vertex(3, g), vertex(4, g), EdgeProperties("harry"), g); graph_traits<Graph>::vertex_iterator i, end; graph_traits<Graph>::out_edge_iterator ei, edge_end; for (boost::tie(i,end) = vertices(g); i != end; ++i) { cout << id[*i] << " "; for (boost::tie(ei,edge_end) = out_edges(*i, g); ei != edge_end; ++ei) cout << " --" << name[*ei] << "--> " << id[target(*ei, g)] << " "; cout << endl; } print_edges(g, id); cout << endl << "removing edge (1,3): " << endl; remove_edge(vertex(1, g), vertex(3, g), g); ei = out_edges(vertex(1, g), g).first; cout << "removing edge (" << id[source(*ei, g)] << "," << id[target(*ei, g)] << ")" << endl; remove_edge(ei, g); for(boost::tie(i,end) = vertices(g); i != end; ++i) { cout << id[*i] << " "; for (boost::tie(ei,edge_end) = out_edges(*i, g); ei != edge_end; ++ei) cout << " --" << name[*ei] << "--> " << id[target(*ei, g)] << " "; cout << endl; } print_edges(g, id); return 0; }

1 0

Fwd: cannot find lboost_thread -problem
by Väisänen Teemu 03 Jan '06

03 Jan '06

Hi all. It seems I have tried to send my messages to wrong mailing lists. Sorry about extra work. I need Boost and lboost_thread to compile Open Diameter. When compiling Open Diameter, I get message /usr/bin/ld: cannot find -lboost_thread I can not find lboost_thread with slocate after compiling Boost 1.33.1, so presumable reason is that I haven't used bjam with right options. Do I need to add libraries using --with-<lib> option to get lboost_thread? If yes, which library has it? Do I also need to use -th option? If I want to use boost rpm's (1.32.0) that came with Linux distribution and is installed already, what should I do to get lboost_thread? Thank you for any answers and help! -Teemu Väisänen

2 1

Problems cross compiling to ARM
by James Hughes 03 Jan '06

03 Jan '06

Hello all, I am cross compiling the boost libs to the PXA270 arm processor running Linux, using GCC 3.4.3 (iwmmxt_le-g++ et al from Montavista) Whilst a lot of libs do seem to build correctly, I get a number of other errors. Here is a typical example which comes up a lot..... /home/jhughes/boost_1_33_1/boost/spirit/core/primitives/numerics.hpp:120: error: declaration of `template<class ScannerT> struct boost::spirit::sign_parser::result' /home/jhughes/boost_1_33_1/boost/spirit/core/parser.hpp:123: error: conflicts with previous declaration `template<class ScannerT> struct boost::spirit::parser<boost::spirit::sign_parser>::result' In file included from /home/jhughes/boost_1_33_1/libs/serialization/build/../src/basic_xml_grammar .ipp:22, from /home/jhughes/boost_1_33_1/libs/serialization/build/../src/xml_wgrammar.cpp: 243 In fact most of the errors seem to be in the grammer area. The command I use to do the build is ... bjam "-sGCC_ROOT_DIRECTORY=/opt/montavista/mobilinux/devkit/arm/iwmmxt_le" "-sGCC=iwmmxt_le-gcc" "-sGXX=iwmmxt_le-g++" stage In addition, I do not seem to get any files copied to the include folder when doing a install build (/usr/local/lib has lots of my built boost libs, /usr/local/include is empty). I would expect to see files in there - am I correct in that expectation? Anyone any ideas? James

1 0

Robert Ramey: "Re: Boost.Serialization // Basic Usage Problem for yourhelp!"
by Feng Wang 03 Jan '06

03 Jan '06

Dear Robert, The boost library I use is from direct includes from Fedora Core 4. I think they might have done a good job to make it work before they distribute on FC4. I built a local boost library per your suggestion, however, the same errors come up. Any More suggestion? Like any small sample code can be built successfully on your system if it is a linux? Thanks. Feng

1 0

Merrill Cornish: "Re: Boost.Serialization // Basic Usage Problem for your help!"
by Feng Wang 03 Jan '06

03 Jan '06

Merrill, I tried to change the include files order as you suggested, but it does not work. Any more suggestions? Feng

1 0

Boost.Serialization // Basic Usage Problem for your help!
by Feng Wang 03 Jan '06

03 Jan '06

Dear All, I got a trouble with boost::serialization library and need your help. 1) I am working with FC4 on my laptop. GCC 4.0.2 is known handle this library pretty well according to yesterdays's report. http://boost.sourceforge.net/regression-logs/cs-Linux.html 2) try to test the basic sample obtained on webpage posted by Jeff Cogswell: #include <fstream> #include <iostream> //#include <boost/serialization/base_object.hpp> #include <boost/archive/text_oarchive.hpp> #include <boost/archive/detail/basic_iarchive.hpp> #include <boost/archive/text_iarchive.hpp> #include <boost/serialization/utility.hpp> #include <boost/serialization/access.hpp> using namespace std; class Vertex { private: friend class boost::serialization::access; template<class Archive> void serialize(Archive & ar, const unsigned int version) { ar & x; ar & y; } double x; double y; public: Vertex() {} // Serialization requires a default constructor Vertex(double newX, double newY) : x(newX), y(newY) {} double getX() const { return x; } double getY() const { return y; } void dump() { cout << x << " " << y << endl; } }; int main() { Vertex v1(1.5, 2.5); std::ofstream ofs("myfile.vtx"); boost::archive::text_oarchive oa(ofs); oa << v1; ofs.close(); return 0; } 3) try to compile and link it by the following command: g++ -lboost_serialization testoa.cpp -otestoa and got a bunch of errors. 4) The errors looks as this: /tmp/ccS4C1Wt.o(.gnu.linkonce.r._ZTIN5boost7archive6detail15common_oarchiveINS0_13text_oarchiveEEE[typeinfo for boost::archive::detail::common_oarchive<boost::archive::text_oarchive>]+0x10): undefined reference to `typeinfo for boost::archive::detail::basic_oarchive' /tmp/ccS4C1Wt.o(.gnu.linkonce.t._ZN5boost13serialization6detail27extended_type_info_typeid_0C2Ev[boost::serialization::detail::extended_type_info_typeid_0::extended_type_info_typeid_0()]+0x7): In function `boost::serialization::detail::extended_type_info_typeid_0::extended_type_info_typeid_0()': testoa.cpp: undefined reference to `boost::serialization::detail::extended_type_info_typeid_0::type_info_key' /tmp/ccS4C1Wt.o(.gnu.linkonce.t._ZN5boost7archive6detail15common_oarchiveINS0_13text_oarchiveEED2Ev[boost::archive::detail::common_oarchive<boost::archive::text_oarchive>::~common_oarchive()]+0x18): In function `boost::archive::detail::common_oarchive<boost::archive::text_oarchive>::~common_oarchive()': testoa.cpp: undefined reference to `boost::archive::detail::basic_oarchive::~basic_oarchive()' /tmp/ccS4C1Wt.o(.gnu.linkonce.t._ZN5boost7archive18text_oarchive_implINS0_13text_oarchiveEED0Ev[boost::archive::text_oarchive_impl<boost::archive::text_oarchive>::~text_oarchive_impl()]+0x3d): In function `boost::archive::text_oarchive_impl<boost::archive::text_oarchive>::~text_oarchive_impl()': testoa.cpp: undefined reference to `boost::archive::basic_text_oprimitive<std::basic_ostream<char, std::char_traits<char> > >::~basic_text_oprimitive()' /tmp/ccS4C1Wt.o(.gnu.linkonce.t._ZN5boost7archive18text_oarchive_implINS0_13text_oarchiveEED0Ev[boost::archive::text_oarchive_impl<boost::archive::text_oarchive>::~text_oarchive_impl()]+0x69):testoa.cpp: undefined reference to `boost::archive::basic_text_oprimitive<std::basic_ostream<char, std::char_traits<char> > >::~basic_text_oprimitive()' /tmp/ccS4C1Wt.o(.gnu.linkonce.t._ZN5boost7archive18text_oarchive_implINS0_13text_oarchiveEED1Ev[boost::archive::text_oarchive_impl<boost::archive::text_oarchive>::~text_oarchive_impl()]+0x3d): In function `boost::archive::text_oarchive_impl<boost::archive::text_oarchive>::~text_oarchive_impl()': testoa.cpp: undefined reference to `boost::archive::basic_text_oprimitive<std::basic_ostream<char, std::char_traits<char> > >::~basic_text_oprimitive()' /tmp/ccS4C1Wt.o(.gnu.linkonce.t._ZN5boost7archive18text_oarchive_implINS0_13text_oarchiveEED1Ev[boost::archive::text_oarchive_impl<boost::archive::text_oarchive>::~text_oarchive_impl()]+0x69):testoa.cpp: undefined reference to `boost::archive::basic_text_oprimitive<std::basic_ostream<char, std::char_traits<char> > >::~basic_text_oprimitive()' /tmp/ccS4C1Wt.o(.gnu.linkonce.t._ZN5boost7archive18text_oarchive_implINS0_13text_oarchiveEED2Ev[boost::archive::text_oarchive_impl<boost::archive::text_oarchive>::~text_oarchive_impl()]+0x3d): In function `boost::archive::text_oarchive_impl<boost::archive::text_oarchive>::~text_oarchive_impl()': testoa.cpp: undefined reference to `boost::archive::basic_text_oprimitive<std::basic_ostream<char, std::char_traits<char> > >::~basic_text_oprimitive()' /tmp/ccS4C1Wt.o(.gnu.linkonce.t._ZN5boost7archive18text_oarchive_implINS0_13text_oarchiveEED2Ev[boost::archive::text_oarchive_impl<boost::archive::text_oarchive>::~text_oarchive_impl()]+0x69):testoa.cpp: more undefined references to `boost::archive::basic_text_oprimitive<std::basic_ostream<char, std::char_traits<char> > >::~basic_text_oprimitive()' follow /tmp/ccS4C1Wt.o(.gnu.linkonce.t._ZN5boost7archive6detail15common_oarchiveINS0_13text_oarchiveEED1Ev[boost::archive::detail::common_oarchive<boost::archive::text_oarchive>::~common_oarchive()]+0x18): In function `boost::archive::detail::common_oarchive<boost::archive::text_oarchive>::~common_oarchive()': testoa.cpp: undefined reference to `boost::archive::detail::basic_oarchive::~basic_oarchive()' /tmp/ccS4C1Wt.o(.gnu.linkonce.t._ZN5boost7archive6detail15common_oarchiveINS0_13text_oarchiveEED0Ev[boost::archive::detail::common_oarchive<boost::archive::text_oarchive>::~common_oarchive()]+0x18): In function `boost::archive::detail::common_oarchive<boost::archive::text_oarchive>::~common_oarchive()': testoa.cpp: undefined reference to `boost::archive::detail::basic_oarchive::~basic_oarchive()' /tmp/ccS4C1Wt.o(.gnu.linkonce.t._ZN5boost7archive6detail15common_oarchiveINS0_13text_oarchiveEEC2Ev[boost::archive::detail::common_oarchive<boost::archive::text_oarchive>::common_oarchive()]+0xe): In function `boost::archive::detail::common_oarchive<boost::archive::text_oarchive>::common_oarchive()': testoa.cpp: undefined reference to `boost::archive::detail::basic_oarchive::basic_oarchive()' /tmp/ccS4C1Wt.o(.gnu.linkonce.t._ZN5boost7archive11save_access14save_primitiveINS0_13text_oarchiveESsEEvRT_RKT0_[void boost::archive::save_access::save_primitive<boost::archive::text_oarchive, std::basic_string<char, std::char_traits<char>, std::allocator<char> > >(boost::archive::text_oarchive&, std::basic_string<char, std::char_traits<char>, std::allocator<char> > const&)]+0x20): In function `void boost::archive::save_access::save_primitive<boost::archive::text_oarchive, std::basic_string<char, std::char_traits<char>, std::allocator<char> > >(boost::archive::text_oarchive&, std::basic_string<char, std::char_traits<char>, std::allocator<char> > const&)': testoa.cpp: undefined reference to `boost::archive::text_oarchive_impl<boost::archive::text_oarchive>::save(std::basic_string<char, std::char_traits<char>, std::allocator<char> > const&)' /tmp/ccS4C1Wt.o(.gnu.linkonce.t._ZN5boost13serialization25extended_type_info_typeidIK6VertexEC1Ev[boost::serialization::extended_type_info_typeid<Vertex const>::extended_type_info_typeid()]+0x28): In function `boost::serialization::extended_type_info_typeid<Vertex const>::extended_type_info_typeid()': testoa.cpp: undefined reference to `boost::serialization::extended_type_info::self_register()' /tmp/ccS4C1Wt.o(.gnu.linkonce.t._ZN5boost7archive6detail21save_non_pointer_typeINS0_13text_oarchiveE6VertexE4save7invokexERS3_RKS4_[boost::archive::detail::save_non_pointer_type<boost::archive::text_oarchive, Vertex>::save::invokex(boost::archive::text_oarchive&, Vertex const&)]+0x17): In function `boost::archive::detail::save_non_pointer_type<boost::archive::text_oarchive, Vertex>::save::invokex(boost::archive::text_oarchive&, Vertex const&)': testoa.cpp: undefined reference to `boost::archive::detail::basic_oarchive::save_object(void const*, boost::archive::detail::basic_oserializer const&)' /tmp/ccS4C1Wt.o(.gnu.linkonce.t._ZN5boost7archive6detail15common_oarchiveINS0_13text_oarchiveEE4initEv[boost::archive::detail::common_oarchive<boost::archive::text_oarchive>::init()]+0x18): In function `boost::archive::detail::common_oarchive<boost::archive::text_oarchive>::init()': testoa.cpp: undefined reference to `boost::archive::ARCHIVE_SIGNATURE' /tmp/ccS4C1Wt.o(.gnu.linkonce.t._ZN5boost7archive6detail15common_oarchiveINS0_13text_oarchiveEE4initEv[boost::archive::detail::common_oarchive<boost::archive::text_oarchive>::init()]+0x98):testoa.cpp: undefined reference to `boost::archive::ARCHIVE_VERSION' /tmp/ccS4C1Wt.o(.gnu.linkonce.t._ZN5boost7archive18text_oarchive_implINS0_13text_oarchiveEEC2ERSoj[boost::archive::text_oarchive_impl<boost::archive::text_oarchive>::text_oarchive_impl(std::basic_ostream<char, std::char_traits<char> >&, unsigned int)]+0x21): In function `boost::archive::text_oarchive_impl<boost::archive::text_oarchive>::text_oarchive_impl(std::basic_ostream<char, std::char_traits<char> >&, unsigned int)': testoa.cpp: undefined reference to `boost::archive::basic_text_oprimitive<std::basic_ostream<char, std::char_traits<char> > >::basic_text_oprimitive(std::basic_ostream<char, std::char_traits<char> >&, bool)' /tmp/ccS4C1Wt.o(.gnu.linkonce.t._ZN5boost7archive18text_oarchive_implINS0_13text_oarchiveEEC2ERSoj[boost::archive::text_oarchive_impl<boost::archive::text_oarchive>::text_oarchive_impl(std::basic_ostream<char, std::char_traits<char> >&, unsigned int)]+0x8c):testoa.cpp: undefined reference to `boost::archive::basic_text_oprimitive<std::basic_ostream<char, std::char_traits<char> > >::~basic_text_oprimitive()' /tmp/ccS4C1Wt.o(.gnu.linkonce.t._ZN5boost7archive19basic_text_oarchiveINS0_13text_oarchiveEE13save_overrideERKNS0_15class_name_typeEi[boost::archive::basic_text_oarchive<boost::archive::text_oarchive>::save_override(boost::archive::class_name_type const&, int)]+0x54): In function `boost::archive::basic_text_oarchive<boost::archive::text_oarchive>::save_override(boost::archive::class_name_type const&, int)': testoa.cpp: undefined reference to `boost::archive::text_oarchive_impl<boost::archive::text_oarchive>::save(std::basic_string<char, std::char_traits<char>, std::allocator<char> > const&)' /tmp/ccS4C1Wt.o(.gnu.linkonce.t._ZN5boost15smart_cast_impl9referenceIRNS_7archive13text_oarchiveEE11polymorphic5cross4castINS2_6detail14basic_oarchiveEEES4_RT_[boost::archive::text_oarchive& boost::smart_cast_impl::reference<boost::archive::text_oarchive&>::polymorphic::cross::cast<boost::archive::detail::basic_oarchive>(boost::archive::detail::basic_oarchive&)]+0xe): In function `boost::archive::text_oarchive& boost::smart_cast_impl::reference<boost::archive::text_oarchive&>::polymorphic::cross::cast<boost::archive::detail::basic_oarchive>(boost::archive::detail::basic_oarchive&)': testoa.cpp: undefined reference to `typeinfo for boost::archive::detail::basic_oarchive' collect2: ld returned 1 exit status 5) Another compile and link issue was talked about on boost user-list half a year ago(http://lists.boost.org/boost-users/2005/05/11624.php) However, I could not decipher the my correct answer from that. My error looks different from the errors posted there. 6) Thanks in advance for your time and help with this issue. I think I might miss some basic points on this library. Henry .K. Wang Jan 2, 2006

2 1

Re: [Boost-users] Boost.Serialization // Basic Usage Problem for your help!
by Merrill Cornish 03 Jan '06

03 Jan '06

Feng, I don't have the expertise to decode the full list of errors. However, I do know that there is an ordering dependency that requires all archive include files come before any serialization include files. So, try rearranging your #includes to put archive includes first and see what happens. Merrill

1 0

Re: [Boost-users] vc 7.1 bug: multiple definitions of symbol with Boost.Test
by Ross Boylan 02 Jan '06

02 Jan '06

On Mon, 2006-01-02 at 04:48 -0500, Daryle Walker wrote: > On 12/29/05 4:21 AM, "Perepelitsa Roman" <romka(a)ptc.ru> wrote: > > > Sorry, I forgot to mention you have to enable precompiler headers to > > reproduce the problem. Project Settings -> C/C++ -> Precompiled > > Headers -> Automatically Generate. > [TRUNCATE] > > Is the header pre-compile option just for VC 7.1, or is it also for (Apple > special) GCC 3.3? As I wrote, I didn't request PCH, and I'm not even sure gcc 3.3 supports them. > Looking at the code from a few posts ago, complaining > about the GCC problem, I don't think you can use the pre-compiled header. > The auto-testing system requires BOOST_AUTO_TEST_MAIN to be #defined in > exactly one source file, which disqualifies it from being in a common > header. True, but it's not the BOOST_AUTO_TEST_MAIN that's causing the problem, or that's being included in more than one file. > Worse, that also means that other headers that pay attention to > that macro can't be in a common header, otherwise the One Definition Rule > would be broken. If you have two translation units with an anonymous namespace, they may appear to be defining the same thing twice. But the C++ standard says it is not the same thing, since each anonymous namespace is distinct. So the definitions occur in different namespaces. Compiler writers seem to be having trouble getting the correct semantics in this case. -- Ross Boylan wk: (415) 514-8146 185 Berry St #5700 ross(a)biostat.ucsf.edu Dept of Epidemiology and Biostatistics fax: (415) 514-8150 University of California, San Francisco San Francisco, CA 94107-1739 hm: (415) 550-1062

1 0

Re: [Boost-users] multiple definitions of symbol withRe: multiple definitions of symbol with Boost.Test
by Perepelitsa Roman 02 Jan '06

02 Jan '06

>> When I try to link a test suite I get this: >> >> ld: multiple definitions of symbol boost::test_tools::(anonymous >> namespace)::check_is_close >> mspathCEntry_test.o definition of boost::test_tools::(anonymous >> namespace)::check_is_close in section (__DATA,__data) >> ModelBuilder_test.o definition of boost::test_tools::(anonymous >> namespace)::check_is_close in section (__DATA,__data) >> ld: multiple definitions of symbol boost::test_tools::(anonymous >> namespace)::check_is_small >> mspathCEntry_test.o definition of boost::test_tools::(anonymous >> namespace)::check_is_small in section (__DATA,__data) >> ModelBuilder_test.o definition of boost::test_tools::(anonymous >> namespace)::check_is_small in section (__DATA,__data) >> LinearProduct_test.o definition of boost::test_tools::(anonymous >> namespace)::check_is_close in section (__DATA,__data) >> LinearProduct_test.o definition of boost::test_tools::(anonymous >> namespace)::check_is_small in section (__DATA,__data) >> ..... >> >> This is with boost 1.33 on Darwin/OS-X. The same code was building OK >> with the 1.31 libraries (and 1.32 on linux, I think). I'm using libtool. >> Here's the makefile > I remember seeing similar report recently. As it clear from error message > linker complains about multiple definitions for symbols in anonymous > namespace. This looks like compiler bug. If you know any workarounds please > share them with us. > Gennadiy I had the same problem with vc 7.1. If you add 'static' to all variables definitions in anonymous namespaces it works fine. For example instead of namespace { check_is_close_t check_is_close; } You can write namespace { static check_is_close_t check_is_close; // note 'static' keyword } Best regards, Perepelitsa Roman.

5 5

[serialization] assertion in basic_binary_oprimitive::save_binary() revisited
by Austin Bingham 02 Jan '06

02 Jan '06

A while ago I brought up what I considered (and still consider) to be a serious problem in basic_binary_oprimitive::save_binary(). The problem is the assert at the end of the function: assert(os.good()); There are a number of reasons why doing this is a bad idea, but the discussion on this issue was dropped flat on the floor. Is there any possibility of discussing alternatives to this assertion? At the very least, can I get an explanation of why an assert is correct to which counter-arguments might be considered? -- Austin Bingham

2 2

boost::spirit, comment_p("//")
by elviin 02 Jan '06

02 Jan '06

Hello Boost users. I'd like to know if anyone was solving the following problem. I tried to use comment_p("//") in this way: rule_t r = *(anychar_p-comment_p("//")) % comment_p("//")[push_back_a(v)] ; This works for me except this case: C++ code: <snip> else if (szMethodName == "the test //") open(tCallParams, tAction); <snip> Problem is caused by the string "the test //". Then the source is parsed in the wrong way because //") open(tCallParams, tAction); is assumed as comment. I think I should select an allowed segment where // is valid.

2 1

Re: [Boost-users] vc 7.1 bug: multiple definitions of symbol with Boost.Test
by Perepelitsa Roman 02 Jan '06

02 Jan '06

>> I had the same problem with vc 7.1. > Strange. I never had problems like this with vc7.1 It's very easy to reproduce the problem. Create project with two source files (e.g. a.cpp and b.cpp) both with the same content: -- begin #include <boost/test/floating_point_comparison.hpp> -- end When you try to compile you get two errors: b.obj : error LNK2005: "struct check_is_small_t::boost::check_is_small_t boost::test_tools::`anonymous namespace'::check_is_small" (?check_is_small@?A0xa003c394@test_tools@boost@@3Ucheck_is_small_t@23@A) already defined in a.obj b.obj : error LNK2005: "struct check_is_close_t::boost::check_is_close_t boost::test_tools::`anonymous namespace'::check_is_close" (?check_is_close@?A0xa003c394@test_tools@boost@@3Ucheck_is_close_t@23@A) already defined in a.obj boost version 1.33.1. >> If you add 'static' to all >> variables definitions in anonymous namespaces it works fine. > But anonimous namespace should do the trick itself! Agree. Seems like compiler bug to me. Roman.

2 2

Building boost 1.33.1 with Comeau 4.3.3
by Pooyan McSporran 02 Jan '06

02 Jan '06

I'm having problems trying to build boost 1.33.1 with comeau 4.3.3 on Linux. Firstly, I verified that the como compiler is working by creating a 'hello world' test program, and building it with the como compiler and running it. I tried to build Boost using the information at http://www.boost.org/tools/build/v1/como-tools.html For example, $ tar -xjf boost_1_33_1.tar.bz2 $ cd boost_1_33_1 $ bjam -sTOOLS=como -sCOMO_PATH=/cc -sCOMO_INCLUDE_PATH=/cc/lib -sCOMO_STDLIB_PATH=/cc stage This results in numerous errors: Building Boost.Regex with the optional Unicode/ICU support disabled. Please refer to the Boost.Regex documentation for more information (and if you don't know what ICU is then you probably don't need it). **** wide char i/o not supported by libcomo standard library **** **** skipping build of <@boost!libs!serialization!build>libboost_wserialization.a; toolset= como variant= debug **** **** wide char i/o not supported by libcomo standard library **** **** skipping build of <@boost!libs!serialization!build>libboost_wserialization.a; toolset= como variant= release **** **** DLLs cannot be built with this compiler **** **** skipping build of <@boost!libs!serialization!build>libboost_serialization.so; toolset= como variant= debug **** **** DLLs cannot be built with this compiler **** **** skipping build of <@boost!libs!serialization!build>libboost_serialization.so; toolset= como variant= release **** **** wide char i/o not supported by libcomo standard library **** **** DLLs cannot be built with this compiler **** **** skipping build of <@boost!libs!serialization!build>libboost_wserialization.so; toolset= como variant= debug **** **** wide char i/o not supported by libcomo standard library **** **** DLLs cannot be built with this compiler **** **** skipping build of <@boost!libs!serialization!build>libboost_wserialization.so; toolset= como variant= release **** ...patience... ...patience... ...patience... ...found 6796 targets... ...updating 789 targets... MkDir1 stage MkDir1 stage/lib MkDir1 bin MkDir1 bin/boost MkDir1 bin/boost/libs MkDir1 bin/boost/libs/regex MkDir1 bin/boost/libs/regex/build MkDir1 bin/boost/libs/regex/build/libboost_regex.so MkDir1 bin/boost/libs/regex/build/libboost_regex.so/como MkDir1 bin/boost/libs/regex/build/libboost_regex.so/como/debug como-C++-action bin/boost/libs/regex/build/libboost_regex.so/como/debug/c_regex_traits.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:strict errors C++ "/cc/lib/stl_tempbuf.h", line 53: error: identifier "INT_MAX" is undefined if (__len > ptrdiff_t(INT_MAX / sizeof(_Tp))) ^ "/cc/lib/stl_tempbuf.h", line 101: error: identifier "INT_MAX" is undefined if (_M_len > (ptrdiff_t)(INT_MAX / sizeof(_Tp))) ^ "/cc/lib/limits", line 205: error: identifier "CHAR_BIT" is undefined __STL_DECLARE_LIMITS_MEMBER(int, ^ (etc!) Am I doing something stupid? For what it's worth, I've been using boost with gcc for quite some time now with no problems, but decided to give it a try with comeau, but no luck yet. I have searched online for solutions to this, but couldn't find any solutions that work for me.

2 2

How to identify Boost libraries which support eVC++ compiler
by Mateusz Łoskot 01 Jan '06

01 Jan '06

Hi, I'm trying to use Boost libraries with eMbedded Visual C++ 4.0 compiler (Windows CE applications development). I'd like to catalogue as much as possible Boost libraries which can be used with eVC++ 4.0 compiler. Currently, I can use smart pointers successfully. I also tried to use boost\date_time libraries and I found most of them can not be used with eVC++. I got "unknown CE compiler" error message. So, I suppose I will get that message in most cases. As I revealed there is a compiler detection mechanism in file boost\config\compiler\visualc.hpp but I couldn't find out how exactly it is used. I'd like to identify all Boost libraries which can not be used with eVC++. Could anyone give me a few hints about how to start such identification? Are there any macro definitions or can I expect that visualc.hpp can help me in this task? Thank in advance for all comments Best regards -- Mateusz Łoskot http://mateusz.loskot.net

3 11

Problems with CVS
by Mateusz Łoskot 01 Jan '06

01 Jan '06

Hi, Yesterday I met some problems with accessing Boost CVS. I started to checkout the CVS HEAD using anonymous user. The process was going well but after a few minutes I got many timeouts errors. I tried to checkout again and update my existing sandbox but without any success. Here are errors I got when using command line CVS client: D:\__projects_mloskot\boost>cvs -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/boost login Logging in to :pserver:anonymous@cvs.sourceforge.net:2401:/cvsroot/boost CVS Password: cvs [login aborted]: Error reading from server cvs.sourceforge.net: 0: No such file or directory D:\__projects_mloskot\boost>cvs -z3 -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/boost co -P boost cvs [checkout aborted]: Error reading from server cvs.sourceforge.net: 0: Invalid argument D:\__projects_mloskot\boost>cvs -z3 -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/boost update -P boost cvs [update aborted]: Error reading from server cvs.sourceforge.net: 0: Invalid argument As I checked CVS Web Browser is working well, so CVS on SF.net seems to be up. Am I doing something wrong? Cheers -- Mateusz Łoskot http://mateusz.loskot.net

1 1

Re: [Boost-users] [multi_index] const_mem_fun with an inherited member function
by JOAQUIN LOPEZ MU?Z 01 Jan '06

01 Jan '06

----- Mensaje original ----- De: Matt Steele <steelerm(a)netlab.uky.edu> Fecha: Domingo, Enero 1, 2006 8:32 pm Asunto: Re: [Boost-users] [multi_index] const_mem_fun with an inherited member function [...] > Your suggestion worked without any changes (runtime tested it > with a few toy calls to insert()/find() ). However, if instead of > invoking the global get<>() function template, I try to call the > member function template, > > return t.get<N>(); > > I get this compile error: > > error: invalid use of member (did you forget the '&' ?) > > Do you know if this code should compile? If not, is there a way > to call > a member function template in this context without relying on a global > function wrapper? Try return t.template get<N>(); Joaquín M López Muñoz Telefónica, Investigación y Desarrollo

1 0

Re: [Boost-users] [multi_index] const_mem_fun with an inherited member function
by Matt Steele 01 Jan '06

01 Jan '06

Hello Joaquin, Thank you for your response. > 2. I think that the code won't work as expected: const_mem_fun > has some overloads of operator() in order to support > chained pointers (http://tinyurl.com/9cd2v) that will hide > the implicit conversion from const tuple<int>& to > const tuple<int>::inherited&. Could you please try to insert > some element in my_tuple_container_type? My hunch is that > you'll get a compiler error about tuple<int> not having > operator*. Please report back. You're right; the code fails to compile and for the reason you give. > remains. My suggestion is that you simply provide a user-defined > key extractor like this (uncompiled, beware typos): > template<typename Tuple,int N> > struct tuple_member_extractor > { > typedef typename > boost::tuples::element<N,Tuple>::type result_type; > > const result_type& operator()(const Tuple& t)const > { > return boost::tuples::get<N>(t); > } > }; > > Hope this helps; I'd appreciate if you reported on the > success/failure of this approach. > Your suggestion worked without any changes (runtime tested it with a few toy calls to insert()/find() ). However, if instead of invoking the global get<>() function template, I try to call the member function template, return t.get<N>(); I get this compile error: error: invalid use of member (did you forget the '&' ?) Do you know if this code should compile? If not, is there a way to call a member function template in this context without relying on a global function wrapper? Thanks, Matt

1 0

Re: [Boost-users] Why is boost::thread::mutex noncopyable?
by Phil Endecott 01 Jan '06

01 Jan '06

>>Can someone help me to understand why boost::thread::mutex is >>noncopyable? I expect that there is a good reason, but I can't see it >>at the moment. > > http://www.boost.org/doc/html/threads/faq.html#id2786688 Thanks for the link. Here is the text: Why do Mutexes have noncopyable semantics? To ensure that deadlocks don't occur. The only logical form of copy would be to use some sort of shallow copy semantics in which multiple mutex objects could refer to the same mutex state. This means that if ObjA has a mutex object as part of its state and ObjB is copy constructed from it, then when ObjB::foo() locks the mutex it has effectively locked ObjA as well. This behavior can result in deadlock. Other copy semantics result in similar problems (if you think you can prove this to be wrong then supply us with an alternative and we'll reconsider). I disagree with the first comment: "The only logical form of copy would be to use some sort of shallow copy semantics in which multiple mutex objects could refer to the same mutex state." What's wrong with the copy of a mutex being a new independent mutex? (There's a problem if you copy a locked mutex, but I don't propose to do that.) --Phil.

3 2

Re: [Boost-users] Why is boost::thread::mutex noncopyable?
by Phil Endecott 01 Jan '06

01 Jan '06

>>Can someone help me to understand why boost::thread::mutex is >>noncopyable? I expect that there is a good reason, but I can't see it >>at the moment. > > http://www.boost.org/doc/html/threads/faq.html#id2786688 I'm being a bit dense - a subsequent FAQ shows how you can write a copy-constructor for a struct that contains a mutex that explicitly copies the data, giving you a new default-constructed mutex. The constructor can even lock the thing it is copying. --Phil.

1 0

Why is boost::thread::mutex noncopyable?
by Phil Endecott 31 Dec '05

31 Dec '05

Dear All, Can someone help me to understand why boost::thread::mutex is noncopyable? I expect that there is a good reason, but I can't see it at the moment. In my multithreaded application I have a struct with some uninteresting data in it, but I want updates to the struct as a whole to be atomic so I have a mutex. For example: struct person { string firstname; string surname; mutex m; }; I want to be able to put these structs in a container. Say a map: map<int,person> people; person p; people.insert(make_pair(1,p)); But I can't do this because the mutex is noncopyable and inserting copies it. Yes, I could have a map<int,person*>. But I don't understand why I'm forced to do that. Of course, copying a struct person while the mutex is locked would be a bad thing to do. And copying the struct is not thread safe. But higher-level constraints can prevent this sort of thing from happening; for example, I might create my map while only one thread exists. Can anyone offer any insight? Thanks, --Phil.

2 1

Re: [Boost-users] [multi_index] const_mem_fun with an inherited memberfunction
by JOAQUIN LOPEZ MU?Z 31 Dec '05

31 Dec '05

Hello Matt, ----- Mensaje original ----- De: Matt Steele <steelerm(a)netlab.uky.edu> Fecha: Sábado, Diciembre 31, 2005 8:21 am Asunto: [Boost-users] [multi_index] const_mem_fun with an inherited memberfunction > I am trying to use Boost.Multi-index (version 1.33.0) to store a > set of > boost::tuples, and it appears that const_mem_fun has some difficulties > when the desired member function is inherited from a base class. The > following typedef > > typedef multi_index_container< > tuple<int>, > indexed_by< ordered_non_unique< const_mem_fun< tuple<int>, > const int&, > &tuple<int>::get<0> > > > > > > > > my_tuple_container_type; > > yields this error (edited for clarity) on my compiler (g++ 4.0.3): > > &TupleBaseClass<int>::get' is not a valid template argument for > type > 'const int& (tuple<int>::*)()const' because it is of type > 'const int& (TupleBaseClass<int>::*)const' > note: standard conversions are not allowed in this context > > > Now the declaration of boost::tuple has something like this: > > template <class T> > class tuple : public TupleBaseClass<T> { > public: > typedef typename TupleBaseClass<T> inherited; > ... > }; > > (Also, as far as I can tell, get<0>() is declared and implemented in > TupleBaseClass, not tuple). The public typedef 'inherited' looked > promising, so I modified my code as follows: > > typedef multi_index_container< > tuple<int>, > indexed_by< ordered_non_unique< const_mem_fun< > tuple<int>::inherited, > const int&, > &tuple<int>::get<0> > > > > > > > > my_tuple_container_type; > > and that compiles. > > I have a few questions/comments about all this. First of all, is my > compiler correct to generate the error for the first case? Unfortunately, it is correct. There are some quirks about the contravariance rules of pointer to members in C++. For instance, the following is legal (as expected): struct A { int x; }; struct B:A{}; int main() { int B::* p=&B::x; } whereas the following is not: struct A { int x; }; struct B:A{}; template<int B::*Ptr> struct foo{}; int main() { // error: argument of type "int A::*" is incompatible with // template parameter of type "int B::*" foo<&B::x> f; } To me, this is a defect in the standard, but there might be a reason for this behavior. I'll go ask in comp.std.c++. > Secondly, is > the above workaround satisfactory? My opinion is that it's a little > ungainly; it appears to me that boost::tuple is a derived type for > implementation reasons, and I'd rather not have to know about that > fact. It is unsatisfactory for two reasons: 1. As you say, having to expose an implementation artifact is ugly. 2. I think that the code won't work as expected: const_mem_fun has some overloads of operator() in order to support chained pointers (http://tinyurl.com/9cd2v) that will hide the implicit conversion from const tuple<int>& to const tuple<int>::inherited&. Could you please try to insert some element in my_tuple_container_type? My hunch is that you'll get a compiler error about tuple<int> not having operator*. Please report back. As for issue #2, I've corrected the problem (for SFINAE-capable compilers) for the next Boost 1.34 release. Even so, issue #1 remains. My suggestion is that you simply provide a user-defined key extractor like this (uncompiled, beware typos): template<typename Tuple,int N> struct tuple_member_extractor { typedef typename boost::tuples::element<N,Tuple>::type result_type; const result_type& operator()(const Tuple& t)const { return boost::tuples::get<N>(t); } }; Hope this helps; I'd appreciate if you reported on the success/failure of this approach. Joaquín M López Muñoz Telefónica, Investigación y Desarrollo

1 0

Re: [Boost-users] multi_index new user question
by JOAQUIN LOPEZ MU?Z 31 Dec '05

31 Dec '05

Hello Evan, ----- Mensaje original ----- De: Evan Carew <carew(a)pobox.com> [...] > int main(){ > const people_set::nth_index<2>::type& resstreet_index=ps.get<2>(); > pair<people_set::iterator, people_set::iterator> range; > range = resstreet_index.equal_range((*domoItor).first); > } > > The above code doesn't compile. > > - ---Fourth entry: > By changing the pair instance to: > > pair<people_set::nth_index<2>::type::iterator, > people_set::nth_index<2>::type::iterator> range; > > I finally got it to compile. I managed this not by reading the > tutorialfor the library (the information isn't there) Well, you're right there's no explicit mention to this issue in the tutorial. The info can be extracted from the reference, though. In any case, I'll try to improve the docs on this and add some comments on how to obtain index iterators. Thanks for the feedback! > but from > reading the > rather prodigious code in multi_index. Wow, this is quite an achievement. The code can look very unintelligible. > > - ---Fifth entry: > Am I headed in the right direction, or is there specific interface > that > defines the iterator types in a less painful/safe way? > You've used one of several syntaxes for getting the type of the index #2 iterator. Other possibilities are: people_set::index<resstreetnum>::type::iterator people_set::nth_index_iterator<2>::type people_set::index_iterator<resstreetnum>::type nth_index<people_set,2>::type::iterator index<people_set,resstreetnum>::type::iterator nth_index_iterator<people_set,2>::type index_iterator<people_set,resstreetnum>::type Since you've assigned tags to your indices, it is probably nicer to use some of the tag variations instead of those based on the index ordinal. Other than this, no syntax is particularly clearer or more concise. You may also want to follow Todd Day's suggestion in another reply to your post, and use some typedef's in order to increase code readability. For instance, if you define typedef people_set::index<resstreetnum>::type resstreet_index_type; then the iterator you're looking for is simply resstreet_index_type::iterator which looks quite obvious, since it follows exactly the same pattern as you'd adopt for an STL container. HTH Joaquín M López Muñoz Telefónica, Investigación y Desarrollo

1 0

[bind] Specifying bind types
by David A. Greene 31 Dec '05

31 Dec '05

I have a situation where I need to be able to specify the type of object that will be created by an invocation of bind(): template<typename F> class Callback { public: Callback(F func) ... } template<typename F, typename Arg> class OneMoreArgCallback : public Callback<SOME_BIND_TYPE> { public: OneMoreArgCallback(F func, Arg arg) : Callback(boost::bind(func, arg, _1)) {}; } What's the best way to do this? typeof? -Dave

3 3

Re: [Boost-users] The boost Tokenizer package: split into a vectorof vectors of tokens
by Alex Vinokur 31 Dec '05

31 Dec '05

nitin motgi wrote: > > > > > if(It != string_find_iterator()) cout << "(" < > << (*It) << endl; > > > Modify this line to (*It) ==> (*It++) > if(It != string_find_iterator()) cout << "(" < (*It++) << endl; > string s = "ab cd \n xy z\n123"; > And output would be > $ ./a.exe > (0, 0) : ab > (0, 1) : cd > (1, 0) : > (1, 1) : > (2, 0) : xy > (2, 1) : z [snip] How to interpret that output? * Why are there two spaces between 'cd' and 'xy'? * Why are there no spaces 'xy' and 'z'? * Why is '123' missing? -- Alex Vinokur email: alex DOT vinokur AT gmail DOT com http://mathforum.org/library/view/10978.html http://sourceforge.net/users/alexvn

1 0

[multi_index] const_mem_fun with an inherited member function
by Matt Steele 31 Dec '05

31 Dec '05

I am trying to use Boost.Multi-index (version 1.33.0) to store a set of boost::tuples, and it appears that const_mem_fun has some difficulties when the desired member function is inherited from a base class. The following typedef typedef multi_index_container< tuple<int>, indexed_by< ordered_non_unique< const_mem_fun< tuple<int>, const int&, &tuple<int>::get<0> > > > > my_tuple_container_type; yields this error (edited for clarity) on my compiler (g++ 4.0.3): &TupleBaseClass<int>::get' is not a valid template argument for type 'const int& (tuple<int>::*)()const' because it is of type 'const int& (TupleBaseClass<int>::*)const' note: standard conversions are not allowed in this context Now the declaration of boost::tuple has something like this: template <class T> class tuple : public TupleBaseClass<T> { public: typedef typename TupleBaseClass<T> inherited; ... }; (Also, as far as I can tell, get<0>() is declared and implemented in TupleBaseClass, not tuple). The public typedef 'inherited' looked promising, so I modified my code as follows: typedef multi_index_container< tuple<int>, indexed_by< ordered_non_unique< const_mem_fun< tuple<int>::inherited, const int&, &tuple<int>::get<0> > > > > my_tuple_container_type; and that compiles. I have a few questions/comments about all this. First of all, is my compiler correct to generate the error for the first case? Secondly, is the above workaround satisfactory? My opinion is that it's a little ungainly; it appears to me that boost::tuple is a derived type for implementation reasons, and I'd rather not have to know about that fact. Thank you. Matt Steele

1 0

Re: [Boost-users] multi_index new user question
by Todd Day 31 Dec '05

31 Dec '05

I've got the following in my project // dummies needed for tagging struct by_name {}; struct by_id {}; struct by_vreg {}; // breaking this up into two steps makes things easier on the compiler, and produces readable? error messages struct ParmListIndices : multi_index::indexed_by < multi_index::sequenced<>, multi_index::ordered_unique<multi_index::tag<by_name>, multi_index::const_mem_fun<ParmBase, string, &ParmBase::GetNameStripped> >, multi_index::ordered_non_unique<multi_index::tag<by_id>, multi_index::const_mem_fun<ParmBase, int, &ParmBase::GetID> >, multi_index::ordered_non_unique<multi_index::tag<by_vreg>, multi_index::const_mem_fun<ParmBase, int32, &ParmBase::GetVreg> > > {}; struct ParmList : multi_index::multi_index_container<ParmBase*, ParmListIndices> {}; typedef multi_index::nth_index<ParmList, 1>::type ParmList_by_name; typedef multi_index::nth_index<ParmList, 2>::type ParmList_by_id; typedef multi_index::nth_index<ParmList, 3>::type ParmList_by_vreg; typedef pair<ParmList::iterator, bool> ParmListResultPair; Note that I used structs to wrap a complicated multi_index instead of using typedefs. I learned this trick from a previous web discussion about multi_index. This relieves stress on the compiler (important for MSVC7.1 with maximum debugging turned on) and makes the error messages easier to read. I used typedef shortcuts for referring to the nth_index'es 'cause structs don't work there. This allowed me to write the following fairly simple looking code. Note the type of the variable "byName" and the iterator "f" below. ParmBase* ParmGroup::FindName(const string& name) { ParmList_by_name& byName = pParmList->get<by_name>(); ParmList_by_name::iterator f = byName.find(name); return (f != byName.end()) ? *f : NULL; } These sorts of tricks make the code a little bit more readable. You can do a similar thing for your iterator pair in your range variable. -todd- > -----Original Message----- > From: boost-users-bounces(a)lists.boost.org [mailto:boost-users- > bounces(a)lists.boost.org] On Behalf Of Evan Carew > Sent: Friday, December 30, 2005 1:03 PM > To: boost-users(a)lists.boost.org > Subject: [Boost-users] multi_index new user question > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > The following is todays log of my efforts to get multi_index to work: > > - ---First entry: > I'm using boost multi index for the first time. I've managed to populate > the container with my data & now I am trying to get the non-unique > ordered index to work. Does anyone have a source example (not from the > boost.multiindex tutorial please) used to get a list, set, whatever, of > tuples from such a search on such an index? > > Thanks, > Evan Carew > > P.S. > G++ V3.4.2 > Boost version 103300 > > - ---Second entry: > Hmm... Looks like their list server is down. I am unable to register. <sigh> > > - ---Third entry: > Well, lets try this example source code: > > > typedef multi_index::multi_index_container< > person, > multi_index::indexed_by< > multi_index::ordered_unique< > multi_index::tag<voterid>, > BOOST_MULTI_INDEX_MEMBER(person,unsigned long,voterid)>, > multi_index::ordered_non_unique< > > multi_index::tag<lastname>,BOOST_MULTI_INDEX_MEMBER(person,string,lastna me) > >, > multi_index::ordered_non_unique< > multi_index::tag<resstreetnum>, > BOOST_MULTI_INDEX_MEMBER(person,int,resstreetnum)> > > > people_set; > > ..... > > int main(){ > const people_set::nth_index<2>::type& resstreet_index=ps.get<2>(); > pair<people_set::iterator, people_set::iterator> range; > range = resstreet_index.equal_range((*domoItor).first); > } > > The above code doesn't compile. > > - ---Fourth entry: > By changing the pair instance to: > > pair<people_set::nth_index<2>::type::iterator, > people_set::nth_index<2>::type::iterator> range; > > I finally got it to compile. I managed this not by reading the tutorial > for the library (the information isn't there) but from reading the > rather prodigious code in multi_index. > > - ---Fifth entry: > Am I headed in the right direction, or is there specific interface that > defines the iterator types in a less painful/safe way? > > Evan Carew

1 0

multi_index new user question
by Evan Carew 30 Dec '05

30 Dec '05

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The following is todays log of my efforts to get multi_index to work: - ---First entry: I'm using boost multi index for the first time. I've managed to populate the container with my data & now I am trying to get the non-unique ordered index to work. Does anyone have a source example (not from the boost.multiindex tutorial please) used to get a list, set, whatever, of tuples from such a search on such an index? Thanks, Evan Carew P.S. G++ V3.4.2 Boost version 103300 - ---Second entry: Hmm... Looks like their list server is down. I am unable to register. <sigh> - ---Third entry: Well, lets try this example source code: typedef multi_index::multi_index_container< person, multi_index::indexed_by< multi_index::ordered_unique< multi_index::tag<voterid>, BOOST_MULTI_INDEX_MEMBER(person,unsigned long,voterid)>, multi_index::ordered_non_unique< multi_index::tag<lastname>,BOOST_MULTI_INDEX_MEMBER(person,string,lastname)>, multi_index::ordered_non_unique< multi_index::tag<resstreetnum>, BOOST_MULTI_INDEX_MEMBER(person,int,resstreetnum)> > > people_set; ..... int main(){ const people_set::nth_index<2>::type& resstreet_index=ps.get<2>(); pair<people_set::iterator, people_set::iterator> range; range = resstreet_index.equal_range((*domoItor).first); } The above code doesn't compile. - ---Fourth entry: By changing the pair instance to: pair<people_set::nth_index<2>::type::iterator, people_set::nth_index<2>::type::iterator> range; I finally got it to compile. I managed this not by reading the tutorial for the library (the information isn't there) but from reading the rather prodigious code in multi_index. - ---Fifth entry: Am I headed in the right direction, or is there specific interface that defines the iterator types in a less painful/safe way? Evan Carew -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFDtaBppxCQXwV2bJARAtYyAJ4lZRAoEbT1m0jsllTGAfmUZEpqSwCguhZO V18uawK1QSD2iJF00hPm4qA= =qn+Q -----END PGP SIGNATURE-----

1 0

Re: [Boost-users] The boost Tokenizer package: split into a vectorof vectors of tokens
by Alex Vinokur 30 Dec '05

30 Dec '05

Pavol Droba wrote: > On Sat, Dec 24, 2005 at 09:06:51AM +0200, Alex Vinokur wrote: > > > > "Pavol Droba" <droba(a)topmail.sk> wrote in message news:20051223180408.GP15407@lenin.felcer.sk... > > > Hi, > > > > > > You might be able to do it using the string_algo find_iterator. > > > > > > #include <boost/algorithm/string.hpp> > > > > > > using namespace std; > > > using namespace boost; > > > > > > ... > > > > > [snip] > > typedef split_iterator<string::iterator> string_find_iterator; > > ------------------------------------------------------------------------------ > > > string_find_iterator It=make_find_iterator(str1, token_finder(is_space())); > > > > That line produces the following error message: > > > > error: conversion from `boost::algorithm::find_iterator<__gnu_cxx::__normal_iterator<char*, std::basic_string<char, > > std::char_traits<char>, std::allocator<char> > > >' to non-scalar type > > `boost::algorithm::split_iterator<__gnu_cxx::__normal_iterator<char*, std::basic_string<char, std::char_traits<char>, > > std::allocator<char> > > >' requested > > > > Sorry, I have fixed one error, but the other line was tied to it. > the second line should be > string_find_iterator It=make_split_iterator(str1, token_finder(is_space())); > > Regards, > Pavol Thanks. Here is what I compiled: -------- #include<iostream> #include<boost/tokenizer.hpp> #include<boost/algorithm/string.hpp> #include<string> using namespace std; using namespace boost; void test() { string s = "ab cd \n xy z\n123"; typedef split_iterator<string::iterator> string_find_iterator; string_find_iterator It = make_split_iterator(s, token_finder(is_space())); const int maxi = 3; const int maxj = 2; for(int i=0; i < maxi; i++) { for(int j=0; j < maxj; j++) { if(It != string_find_iterator()) cout << "(" << i << ", " << j << ") : " << (*It) << endl; else break; } } } int main () { test(); return 0; } -------- And here is what I have got after running: --- (0, 0) : ab (0, 1) : ab (1, 0) : ab (1, 1) : ab (2, 0) : ab (2, 1) : ab --- Alex Vinokur email: alex DOT vinokur AT gmail DOT com http://mathforum.org/library/view/10978.html http://sourceforge.net/users/alexvn

3 2

[iostreams] array_sink full exception
by Robert Ramey 30 Dec '05

30 Dec '05

I'm looking at array_sink stream buffer as a possible speed enhancement to binary_oarchive in some cases. My quesion is" What happens when the capacity of the array used for the buffer is exceeded? Is an exception thrown or what? I've looked through the documentation and don't find exceptions mentioned. Robert Ramey

2 2

Re: [Boost-users] [Multi-index] Sorted range selection
by JOAQUIN LOPEZ MU?Z 29 Dec '05

29 Dec '05

Hello Tamas, ----- Mensaje original ----- De: Tamas Szepes <tamas.szepes(a)ieee.org> Fecha: Miércoles, Diciembre 28, 2005 9:11 pm Asunto: [Boost-users] [Multi-index] Sorted range selection > Hi All, > > I'm learning to use the multi-index library by rewriting an > existing STL > based code. > I'm storing rectangles (X, Y, Width, Height, ...) in a set ordered > by a > composite key on X, Y. > > What is the best way to select rectangles where X has a certain > value and > sort the result by Width? Can I use a sorted indice on Width, or I > must sort > the range? I also thought to create a composite key on X and > Width, but > sorting order is run time determined and I have a dosen other > properties. Your analysis is correct. I'm afraid you have to externally sort the interval returned by range(), pseudocode follows: std::vector<boost::reference_wrapper<const Rectangle> > rng; std::pair< YourCompositeKeyIndex::iterator, YourCompositeKeyIndex::iterator> p= yourcompositekeyindex.range(...); while(p.first!=p.second)rng.push_back(boost::cref(*p.first++)); std::sort(rng.begin(),rng.end(),WidthCompare()); Having a composite key on (X,Width) is also an option, but as you say the number of combinations might be too large, and manipulating those indices with run-time decisions is not trivial. So, my suggestion is to follow the scheme proposed on the pseudocode above. > I'm realy looking for the possibility to mimic SQL's ORDER BY clause. Well, Boost.MultiIndex does not aim to provide complete functionality for relational stuff, as stated explicitly in the rationale at http://boost.org/libs/multi_index/doc/tutorial.html. The idea is to keep Boost.MultiIndex application-agnostic and more focused on the STL conceptual framework. As I see it, this kind of funcionality could be better served by a relational-specific lib built on top of Boost.MultiIndex. There are currently two libs approaching this goal, Arkadiy Vertleyb's RTL and Calum Grant's RML (look for those on recent discussions on the Boost list.) Unfortunately, neither of these libs actually uses internally Boost.MultiIndex, but this is another story :) > > Thanks for any help in advance, I'm sorry I can't be more helpful. Thanks for using Boost.MultiIndex and please come back if you have further problems or want to comment on proposals for enhancements of the library. Joaquín M López Muñoz Telefónica, Investigación y Desarrollo

1 0

BGL question: non local exit by throwing an exception
by Andreas Fabri 29 Dec '05

29 Dec '05

Hi, I am wondering, if it is good style to throw an exception in the middle of a BGL algorithm, for example during BFS when I have found what I want. Or are there nicer ways to achive the same goal? Thanks in advance, andreas

2 1

[BGL] Mixing bundled properties and property lists
by Nicola Vitacolonna 29 Dec '05

29 Dec '05

Hi, consider the following (excerpt from a) class wrapper around an adjacency_list: using namespace boost; template <typename VertexProperty = no_property> class MyGraphWrapper { private: typedef adjacency_list<vecS, listS, bidirectionalS, property<vertex_index_t, int, VertexProperty> > GraphImpl; // ... }; I want to store some property (in this case, a vertex index) inside the graph implementation, but at the same time I want to allow the client to specify further properties via the template parameter. May the client use the bundled property mechanism, e.g. struct Label { std::string lab; }; MyGraphWrapper<Label> g; My test compiled and it seems to run fine. Is it really possible/safe to mix bundle properties with property lists in this way? Or, is there a way to avoid property lists? Nicola

3 2

Re: [Boost-users] [boost] bug in signals library? - segmentation fault (onlylinked) -> exit(11) called
by Oliver.Kowalke＠infineon.com 29 Dec '05

29 Dec '05

Hi, Strange - the segmentation fault disappears if I link with the debug-version of libboost_signals (-lboost_signals-gcc-d-1_33_1)! It seams to me that some assert statements contain required code (removed in release version if signals)?! >> I get an segmentation fault if I try to link against >> libboost_signals-gcc-1_33_1 or libboost_signals-gcc-mt-1_33_1! >> The application consist only of an empty main function and the binary is >> linked against the signals library. >> I've appended an output (tusc.out) of tusc (trace unix system calls) >> which indicates, that exit(11) is called and so a core dump created. > >Can you run the program under gdb debugger, and when hittin segfault >produce >backtrace with the "backtrace" command. That will be more usefull, in any >case, then syscall trace. I'm not familiar with gdb! What I did (hopefully correct): [src]$ /opt/langtools/bin/gdb32 test HP gdb 5.2 for PA-RISC 1.1 or 2.0 (narrow), HP-UX 11.00 and target hppa1.1-hp-hpux11.00. Copyright 1986 - 2001 Free Software Foundation, Inc. Hewlett-Packard Wildebeest 5.2 (based on GDB) is covered by the GNU General Public License. Type "show copying" to see the conditions to change it and/or distribute copies. Type "show warranty" for warranty/support. .. (gdb) run Starting program: /eda-home/kowalke/Projects/test/debug/src/test Program received signal SIGSEGV, Segmentation fault si_code: 0 - SEGV_UNKNOWN - Unknown Error. 0xc0017cd8 in <unknown_procedure> () (gdb) backtrace #0 0xc0017cd8 in <unknown_procedure> () warning: Attempting to unwind past bad PC 0xc0017cd8 #1 0xc0027400 in <unknown_procedure> () #2 0xc0027400 in <unknown_procedure> () Error accessing memory address 0x3e7: Bad address.

2 1

boost: debug step into extremely slow at VC8
by David Xiao 29 Dec '05

29 Dec '05

Hi Guys: In my computer, if compile with VC8 with boost library, the debug stepping speed is extremely slow! I have to wait 3-5 second for one step! With VC7.1 everything is ok. Who has the same problem with me ? Rgds, David Xiao

2 1

[Multi-index] Sorted range selection
by Tamas Szepes 28 Dec '05

28 Dec '05

Hi All, I'm learning to use the multi-index library by rewriting an existing STL based code. I'm storing rectangles (X, Y, Width, Height, ...) in a set ordered by a composite key on X, Y. What is the best way to select rectangles where X has a certain value and sort the result by Width? Can I use a sorted indice on Width, or I must sort the range? I also thought to create a composite key on X and Width, but sorting order is run time determined and I have a dosen other properties. I'm realy looking for the possibility to mimic SQL's ORDER BY clause. Thanks for any help in advance, Tamas

1 0

cannot open file 'libboost_date_time-vc71-sgd-1_33_1.lib'
by Subrahmanyam (Arun) 28 Dec '05

28 Dec '05

Hi, I am new to boost libraries. I have viewed some samples in http://www.boost.org/doc/html/date_time/examples.html#date_time.examples.da… in which i tried to build "Days Alive" example. The application reports: boost1 fatal error LNK1104: cannot open file 'libboost_date_time-vc71-sgd-1_33_1.lib' I have searched this in my list of libraries/files installed, but failed to find the same. Can any one please help how to overcome this error. Thanks, Arun.

2 1

Re: [Boost-users] [serialization]Mal-formed XML output
by Merrill Cornish 28 Dec '05

28 Dec '05

Robert, I changed the archive output from XML to text. The example I sent you prevously ran to completion without error. However, the text format doesn't have enough syntax detail to make a syntax error obvious. The text archive it generated was 22 serialization::archive 3 0 1 1 1 0 0 0 0 0 1 -1 4 abcd 0 0 0 0 8 20051227 0 0 0 18 41 40 0 I had also written a serialization test for another class. Its serialize() function looks like this private: friend class boost::serialization::access; template<class Archive> void serialize(Archive& ar, const unsigned int version) { ar & BOOST_SERIALIZATION_NVP(mNode); ar & BOOST_SERIALIZATION_NVP(mInputIndex); ar & BOOST_SERIALIZATION_NVP(mIsInbound); }//serialize() where, again, mNode is a shared_ptr, mInputIndex is size_t, and mIsInbound is a bool. The code to generate the archive and to then read is back is as I showed you before. The archive generated was 22 serialization::archive 3 0 1 1 1 0 0 0 1 Is that enough of an archive to record the serialize() function above? The serialization of the mNode data member should have included the value 1142 in it, but I see nothing that would represent that. Merrill

2 1

multiple definitions of symbol with Boost.Test
by Ross Boylan 27 Dec '05

27 Dec '05

When I try to link a test suite I get this: ld: multiple definitions of symbol boost::test_tools::(anonymous namespace)::check_is_close mspathCEntry_test.o definition of boost::test_tools::(anonymous namespace)::check_is_close in section (__DATA,__data) ModelBuilder_test.o definition of boost::test_tools::(anonymous namespace)::check_is_close in section (__DATA,__data) ld: multiple definitions of symbol boost::test_tools::(anonymous namespace)::check_is_small mspathCEntry_test.o definition of boost::test_tools::(anonymous namespace)::check_is_small in section (__DATA,__data) ModelBuilder_test.o definition of boost::test_tools::(anonymous namespace)::check_is_small in section (__DATA,__data) LinearProduct_test.o definition of boost::test_tools::(anonymous namespace)::check_is_close in section (__DATA,__data) LinearProduct_test.o definition of boost::test_tools::(anonymous namespace)::check_is_small in section (__DATA,__data) ..... This is with boost 1.33 on Darwin/OS-X. The same code was building OK with the 1.31 libraries (and 1.32 on linux, I think). I'm using libtool. Here's the makefile output before those errors (I've deleted some of the files on the command line to save space): ../libtool --mode=link --tag=CXX g++ -o test1 -g AbstractTimeStepsGenerator.o Coefficients.o -lboost_unit_test_framework -L/usr/local/lib/boost-1_33_1 g++ -o test1 -g AbstractTimeStepsGenerator.o Coefficients.o Covariates.o -Wl,-bind_\ at_load -lboost_unit_test_framework -L/usr/local/lib/boost-1_33_1 There are several copies of various flavors of the library lying around, but I don't think any are on the default library paths. So I think I'm only getting the one in /usr/local/lib/boost-1_33_1. It looks as if each invocation of, e.g., BOOST_CHECK_CLOSE, is generating a defiition for the symbols on which I'm getting duplicates. But why would it do that? Any suggestions, or ideas what might be going wrong? Thanks. Ross Boylan Here are some possibly relevant details. Example code: -------------------------------------------------- #include <cstdlib> #include <fstream> #include <iostream> #include <iterator> #include <vector> #include <boost/test/auto_unit_test.hpp> #include <boost/test/floating_point_comparison.hpp> using namespace boost::unit_test_framework; #include "basic.h" #include "Data.h" #include "Model.h" #include "mspath.h" #include "main_test.h" using namespace mspath; using namespace std; static Data * readInputDataFile() { //.... } BOOST_AUTO_UNIT_TEST(CEntry){ if (gOptions.input1() == 0) { BOOST_ERROR("Skipping mspathCEntry test. You need to specify an input file."); return; }; cout.imbue(locale("")); Data* pdata = readInputDataFile(); // ..... BOOST_CHECK_CLOSE(results[0], 2835.43092, tol); // .... } ------------------------------ Maybe I'm messing things up by rolling my own outer level code for the auto-unit tests: ------------------------------------- #include "main_test.h" #include <boost/test/auto_unit_test.hpp> #include "basic.h" // g for global // It's ugly, but it works. mspath::TestOptions mspath::gOptions; /* The following function is just a slight modification to the usual product of #define BOOST_AUTO_TEST_MAIN so that I can capture command line arguments. See the top of the file for the meaning of those arguments. */ #if defined( BOOST_1_31) // code for 1.31 and 1.32 snipped for brevity #elif defined(BOOST_1_33) boost::unit_test::test_suite* init_unit_test_suite( int argc, char* argv[] ) { mspath::gOptions.init(argc, argv); boost::unit_test::auto_unit_test_suite_t* master_test_suite = boost::unit_test::auto_unit_test_suite(); boost::unit_test::auto_unit_test_suite_t* master_test_suite = boost::unit_test::auto_unit_test_suite(); boost::unit_test::const_string new_name = boost::unit_test::const_string( "BOOST_AUTO_TEST_MAIN" ); if( !new_name.is_empty() ) boost::unit_test::assign_op( master_test_suite->p_name.value, new_name, 0 ); master_test_suite->argc = argc; master_test_suite->argv = argv; return master_test_suite; } #else #error I do not know how to setup for this version of boost BOOST_VERSION #endif // etc --------------------------------------------------------------

2 2

Re: [Boost-users] [serialization]Mal-formed XML output
by Merrill Cornish 27 Dec '05

27 Dec '05

Robert, The immediate object being serialized was a shared_ptr and one of the data members being serialized was also a shared_ptr, although it doesn't appear that the process got to the point of serializing that data member. Removing the data member from serialization did nothing. The same faulty output was created. Removing the shared_ptr data member AND replacing the testObj_out shared_ptr with an ordinary pointer produced a different mal-formed XML output: <?xml version="1.0" encoding="UTF-8" standalone="yes" ?> <!DOCTYPE boost_serialization> <boost_serialization signature="serialization::archive" version="3"> <testObj_out class_id="0" tracking_level="1" version="0" object_id="_0"</boost_serialization> By the way, in your reply, you mentioned the missing </px element. However, the original error (and this one too) is more primitive: the initial <px element (or, in this case, the <testObj_out element) have no closing >. Therefore, the serialization process never got past outputting the FULL introductory element. I doubt that the processing ever got to the point of serializing any of the data members. Merrill

1 0

Re: [Boost-users] [serialization]Mal-formed XML output
by Merrill Cornish 27 Dec '05

27 Dec '05

Robert, Here is the relevant code: =========================================== from the header file for the class being serialized... #include "boost/serialization/shared_ptr.hpp" #include "boost/serialization/nvp.hpp" #include "boost/date_time/posix_time/ptime.hpp" #include "boost/date_time/posix_time/time_serialize.hpp" . . . private: friend class boost::serialization::access; template<class Archive> void serialize(Archive& ar, const unsigned int version) { ar & BOOST_SERIALIZATION_BASE_OBJECT_NVP(WkFlo::RetractionMixin); ar & BOOST_SERIALIZATION_NVP(mNode); ar & BOOST_SERIALIZATION_NVP(mExportId); ar & BOOST_SERIALIZATION_NVP(mExportStart); }//serialize() where mNode is a shared_ptr<>, mExportedId is a string, and mExportStart is a ptime. =========================================== from the test source file... #include "boost/archive/xml_iarchive.hpp" #include "boost/archive/xml_oarchive.hpp" #include "boost/serialization/shared_ptr.hpp" #include "boost/serialization/nvp.hpp" . . . void ExportedNode_Test::serializationTest() { const char* archiveFile = "temp/Exported_Node_archive.xml"; remove(archiveFile); // remove any file with that name MockNode_ptr BasicNodeObj1(new MockNode(2312)); ExportedNode_ptr testObj_out(new ExportedNode(BasicNodeObj1, "abcd")); { // save data to archive ofstream outStream(archiveFile); boost::archive::xml_oarchive outArchive(outStream); // write class instance to archive try { outArchive << BOOST_SERIALIZATION_NVP(testObj_out); } catch (exception& ex) { cerr << "write: " << ex.what() << endl;} } // archive and stream closed when destructors are called . . . } where the outArchive << is what wrote: <?xml version="1.0" encoding="UTF-8" standalone="yes" ?> <!DOCTYPE boost_serialization> <boost_serialization signature="serialization::archive" version="3"> <testObj_out class_id="0" tracking_level="0" version="1"> <px class_id="1" tracking_level="1" version="0" object_id="_0"</boost_serialization> and threw the exception: "unrecognized XML syntax" Is this enough to go on? Merrill

2 1

[serialization]Mal-formed XML output
by Merrill Cornish 27 Dec '05

27 Dec '05

I've finally gotten serialization for XML archives to compile using Boost 1.33.1. Now I'm trying to execute the test. Unfortunately, the first archive output statement outArchive << BOOST_SERIALIZATION_NVP(testObj_out); triggers an exception saying, "unrecognized XML syntax". The output file looks like <?xml version="1.0" encoding="UTF-8" standalone="yes" ?> <!DOCTYPE boost_serialization> <boost_serialization signature="serialization::archive" version="3"> <testObj_out class_id="0" tracking_level="0" version="1"> <px class_id="1" tracking_level="1" version="0" object_id="_0"</boost_serialization> Note that the closing ">" for the px element is missing, which is probably the reason why there is no newline before </boost_serialization>. The serialize() function for the class object being archived has one ar & for a base class plus three data members. So, it looks like serialization is going awry while string to write the initial class element and never gets to the class contents. By the way, I've never seen the XML root element (<boost_serialization>) with attributes. Is that standard? Any ideas? Merrill

3 3

The boost Tokenizer package: split into a vector of vectors of tokens
by Alex Vinokur 27 Dec '05

27 Dec '05

Can the boost Tokenizer package split a string into into a series of serieses of tokens (a vector of vectors of tokens)? ==================== For instance, string s = "ab cd \nxy z\n123"; vector<vector<string> > v; Output should be as follows: v[0][0] = "ab"; v[0][1] = "cd"; v[1][0] = "xy"; v[1][1] = "z"; v[2][0] = "123"; ==================== http://boost.org/libs/tokenizer/introduc.htm doesn't contain such a sample. Alex Vinokur email: alex DOT vinokur AT gmail DOT com http://mathforum.org/library/view/10978.html http://sourceforge.net/users/alexvn

3 5

Confusion about output_test_stream in the testing tools
by Ross Boylan 27 Dec '05

27 Dec '05

I have a unit test case that includes #include <boost/test/auto_unit_test.hpp> #include <boost/test/floating_point_comparison.hpp> // I will try without the unit test namespace // 1.32 using boost::test_toolbox::ostream_test_stream; using boost::test_toolbox::output_test_stream; output_test_stream ostream; This worked in 1.32 (I think--the comment makes it sound as if it shouldn't). But in 1.33 I get error: `output_test_stream' not declared Turning to the documentation, I couldn't find any mention of this navigating the docs for boost.test (including looking at the detailed release notes). However, when I did a site search I found http://www.boost.org/libs/test/doc/components/test_tools/output_test_stream… That page itself is confusing. the heading is boost::test_tools::ostream_test_stream but the class definition and other material use output_test_stream. The file test/output_test_stream.hpp names the class output test stream. Can anyone clarify what's going on? Either the documentation needs to be tweaked, or I'm confused, or both. Ross

2 4

Boost serialization- looks great, but I'm confused about serializing polymorphic types
by Terence Wilson 24 Dec '05

24 Dec '05

I am an MFC veteran that wants to use a more modern mechanism for archival, in MFC a base pointer can be written and the object recreated automatically upon the read. I've been reading the serialization documentation and I am very confused about what I need to do to make this work using Boost, the code I have so far fails to compile with a static assert in the save function in oserializer.hpp. class CMyClassBase { public: CMyClassBase():m_TagBase(0){} virtual ~CMyClassBase(){} int m_TagBase; friend class boost::serialization::access; template<class Archive> void serialize(Archive & ar, const unsigned int /* file_version */) { ar & m_TagBase; } }; class CMyClassDerived : public CMyClassBase { public: CMyClassDerived():m_TagDerived(1){} virtual ~CMyClassDerived(){} int m_TagDerived; friend class boost::serialization::access; template<class Archive> void serialize(Archive & ar, const unsigned int /* file_version */) { boost::serialization::base_object<CMyClassBase>(*this); ar & m_TagDerived; } }; BOOST_CLASS_EXPORT_GUID(CMyClassDerived, "CMyClassDerived") void save_myclass(CMyClassBase* pMyClassBase, const char * filename){ // make an archive std::ofstream ofs(filename); boost::archive::text_oarchive oa(ofs); oa << pMyClassBase; } void restore_myclass(CMyClassBase* pMyClassBase, const char * filename) { // open the archive std::ifstream ifs(filename); boost::archive::text_iarchive ia(ifs); // restore the schedule from the archive ia >> pMyClassBase; }

2 2

Re: [Boost-users] [serialization] Can't compile archive I/O - 2
by Merrill Cornish 24 Dec '05

24 Dec '05

Robert, Thanks. THAT did it. It also explained to me why this had worked before then "suddenly" stopped working. In the intervening time, I had "optimized" my headers and #includes. Somewhere along the way, I got serialization headers before archive headers. Would it be useful to put something like #define BOOST_SERIALIZATION_HEADER_INCLUDED in each serialization header file and #ifdef BOOST_SERIALIZATION_HEADER_INCLUDED #error A Boost serialization header was included BEFORE an Boost archive header. #endif. in each archive header file? In the meantime, thanks for your help, thanks for the promptness of your help, and have warm, safe holidays. Merrill

2 1

Re: [Boost-users] [serialization] Can't compile archive I/O - 2
by Merrill Cornish 24 Dec '05

24 Dec '05

Robert, I just now got home to try adding the two NVP wrappers you suggested. The old problems went away, but there's a new set: Merrill Succ.h=========================================== #include "boost/serialization/nvp.hpp" #include "boost/test/test_tools.hpp" namespace MyNS { class Succ { friend class Succ_Test; private: size_t mInputIndex; bool mIsInbound; friend class boost::serialization::access; template<class Archive> void serialize(Archive& ar, const unsigned int version) { ar & BOOST_SERIALIZATION_NVP(mInputIndex); ar & BOOST_SERIALIZATION_NVP(mIsInbound); }//serialize() public: Succ() {} // needed by serialization Succ(size_t inputIndex, bool isInbound); virtual ~Succ(); size_t inputIndex() const; bool isInbound() const; };//Succ }//MyNS Succ_Test.cc=================================== #include <fstream> #include "Succ.h" #include "boost/archive/xml_iarchive.hpp" #include "boost/archive/xml_oarchive.hpp" #include "boost/test/test_tools.hpp" using namespace std; namespace MyNS { class Succ_Test { public: void run(); };//Succ_Test //============================================================================= void Succ_Test::run() { const char* archiveFile = "temp/Succ_archive.xml"; size_t inputIndex = 65; bool isInbound = true; Succ* testObj_out = new Succ(inputIndex, isInbound); { // save data to archive ofstream outStream(archiveFile); boost::archive::xml_oarchive outArchive(outStream); // write class instance to archive outArchive << BOOST_SERIALIZATION_NVP(testObj_out); } // archive and stream closed when destructors are called Succ* testObj_in;// = new Succ(); { // create and open an archive for input ifstream inStream(archiveFile); boost::archive::xml_iarchive inArchive(inStream); // read class state from archive inArchive >> BOOST_SERIALIZATION_NVP(testObj_in); } // archive and stream closed when destructors are called return; }//run() }//MyNS compile stderr======================================== Foo/boost-1_33_1/include/boost/archive/detail/oserializer.hpp: In static member function `static void boost::archive::detail::save_pointer_type<Archive, TPtr>::save(Archive&, const T&, const boost::archive::detail::basic_pointer_oserializer*) [with T = MyNS::Succ, Archive = boost::archive::xml_oarchive, TPtr = MyNS::Succ*]': Foo/boost-1_33_1/include/boost/archive/detail/oserializer.hpp:467: instantiated from `static void boost::archive::detail::save_pointer_type<Archive, TPtr>::invoke(Archive&, TPtr) [with Archive = boost::archive::xml_oarchive, TPtr = MyNS::Succ*]' Foo/boost-1_33_1/include/boost/archive/detail/oserializer.hpp:536: instantiated from `void boost::archive::save(Archive&, const T&) [with Archive = boost::archive::xml_oarchive, T = MyNS::Succ*]' Foo/boost-1_33_1/include/boost/archive/basic_xml_oarchive.hpp:99: instantiated from `void boost::archive::basic_xml_oarchive<Archive>::save_override(const boost::serialization::nvp<T>&, int) [with T = MyNS::Succ*, Archive = boost::archive::xml_oarchive]' Foo/boost-1_33_1/include/boost/archive/detail/interface_oarchive.hpp:78: instantiated from `Archive& boost::archive::detail::interface_oarchive<Archive>::operator<<(T&) [with T = const boost::serialization::nvp<MyNS::Succ*>, Archive = boost::archive::xml_oarchive]' Foo/test/src/Succ_Test.cc:48: instantiated from here Foo/boost-1_33_1/include/boost/archive/detail/oserializer.hpp:438: error: invalid use of undefined type `struct boost::serialization::extended_type_info_null<MyNS::Succ>' Foo/boost-1_33_1/include/boost/serialization/type_info_implementation.hpp:26: error: declaration of `struct boost::serialization::extended_type_info_null<MyNS::Succ>' Foo/boost-1_33_1/include/boost/archive/detail/oserializer.hpp:439: error: invalid use of undefined type `struct boost::serialization::extended_type_info_null<MyNS::Succ>' Foo/boost-1_33_1/include/boost/serialization/type_info_implementation.hpp:26: error: declaration of `struct boost::serialization::extended_type_info_null<MyNS::Succ>' Foo/boost-1_33_1/include/boost/archive/detail/oserializer.hpp:439: error: `save' is not a member of `<declaration error>' Foo/boost-1_33_1/include/boost/archive/detail/iserializer.hpp: In static member function `static T* boost::archive::detail::load_pointer_type<Archive, Tptr>::pointer_tweak(const boost::serialization::extended_type_info&, void*, T&) [with T = MyNS::Succ, Archive = boost::archive::xml_iarchive, Tptr = MyNS::Succ*]': Foo/boost-1_33_1/include/boost/archive/detail/iserializer.hpp:493: instantiated from `static void boost::archive::detail::load_pointer_type<Archive, Tptr>::invoke(Archive&, Tptr&) [with Archive = boost::archive::xml_iarchive, Tptr = MyNS::Succ*]' Foo/boost-1_33_1/include/boost/archive/detail/iserializer.hpp:572: instantiated from `void boost::archive::load(Archive&, T&) [with Archive = boost::archive::xml_iarchive, T = MyNS::Succ*]' Foo/boost-1_33_1/include/boost/archive/basic_xml_iarchive.hpp:80: instantiated from `void boost::archive::basic_xml_iarchive<Archive>::load_override(const boost::serialization::nvp<T>&, int) [with T = MyNS::Succ*, Archive = boost::archive::xml_iarchive]' Foo/boost-1_33_1/include/boost/archive/xml_iarchive.hpp:74: instantiated from `void boost::archive::xml_iarchive_impl<Archive>::load_override(T&, int) [with T = const boost::serialization::nvp<MyNS::Succ*>, Archive = boost::archive::xml_iarchive]' Foo/boost-1_33_1/include/boost/archive/detail/interface_iarchive.hpp:76: instantiated from `Archive& boost::archive::detail::interface_iarchive<Archive>::operator>>(T&) [with T = const boost::serialization::nvp<MyNS::Succ*>, Archive = boost::archive::xml_iarchive]' Foo/test/src/Succ_Test.cc:58: instantiated from here Foo/boost-1_33_1/include/boost/archive/detail/iserializer.hpp:475: error: incomplete type `boost::serialization::extended_type_info_null<MyNS::Succ>' used in nested name specifier Foo/boost-1_33_1/include/boost/archive/detail/oserializer.hpp: In constructor `boost::archive::detail::pointer_oserializer<T, Archive>::pointer_oserializer() [with T = MyNS::Succ, Archive = boost::archive::xml_oarchive]': Foo/boost-1_33_1/include/boost/archive/detail/oserializer.hpp:198: instantiated from `const boost::archive::detail::pointer_oserializer<MyNS::Succ, boost::archive::xml_oarchive> boost::archive::detail::pointer_oserializer<MyNS::Succ, boost::archive::xml_oarchive>::instance' Foo/boost-1_33_1/include/boost/archive/detail/oserializer.hpp:190: instantiated from `static const boost::archive::detail::pointer_oserializer<T, Archive>& boost::archive::detail::pointer_oserializer<T, Archive>::instantiate() [with T = MyNS::Succ, Archive = boost::archive::xml_oarchive]' Foo/boost-1_33_1/include/boost/archive/detail/oserializer.hpp:515: instantiated from `const boost::archive::detail::basic_pointer_oserializer& boost::archive::detail::instantiate_pointer_oserializer(Archive*, T*) [with Archive = boost::archive::xml_oarchive, T = MyNS::Succ]' Foo/boost-1_33_1/include/boost/archive/detail/interface_oarchive.hpp:58: instantiated from `const boost::archive::detail::basic_pointer_oserializer* boost::archive::detail::interface_oarchive<Archive>::register_type(const T*) [with T = MyNS::Succ, Archive = boost::archive::xml_oarchive]' Foo/boost-1_33_1/include/boost/archive/detail/oserializer.hpp:344: instantiated from `static const boost::archive::detail::basic_pointer_oserializer* boost::archive::detail::save_pointer_type<Archive, TPtr>::non_abstract<T>::register_type(Archive&) [with T = MyNS::Succ, Archive = boost::archive::xml_oarchive, TPtr = MyNS::Succ*]' Foo/boost-1_33_1/include/boost/archive/detail/oserializer.hpp:360: instantiated from `static const boost::archive::detail::basic_pointer_oserializer* boost::archive::detail::save_pointer_type<Archive, TPtr>::register_type(Archive&, T&) [with T = MyNS::Succ, Archive = boost::archive::xml_oarchive, TPtr = MyNS::Succ*]' Foo/boost-1_33_1/include/boost/archive/detail/oserializer.hpp:460: instantiated from `static void boost::archive::detail::save_pointer_type<Archive, TPtr>::invoke(Archive&, TPtr) [with Archive = boost::archive::xml_oarchive, TPtr = MyNS::Succ*]' Foo/boost-1_33_1/include/boost/archive/detail/oserializer.hpp:536: instantiated from `void boost::archive::save(Archive&, const T&) [with Archive = boost::archive::xml_oarchive, T = MyNS::Succ*]' Foo/boost-1_33_1/include/boost/archive/basic_xml_oarchive.hpp:99: instantiated from `void boost::archive::basic_xml_oarchive<Archive>::save_override(const boost::serialization::nvp<T>&, int) [with T = MyNS::Succ*, Archive = boost::archive::xml_oarchive]' Foo/boost-1_33_1/include/boost/archive/detail/interface_oarchive.hpp:78: instantiated from `Archive& boost::archive::detail::interface_oarchive<Archive>::operator<<(T&) [with T = const boost::serialization::nvp<MyNS::Succ*>, Archive = boost::archive::xml_oarchive]' Foo/test/src/Succ_Test.cc:48: instantiated from here Foo/boost-1_33_1/include/boost/archive/detail/oserializer.hpp:233: error: incomplete type `boost::serialization::extended_type_info_null<MyNS::Succ>' used in nested name specifier Foo/boost-1_33_1/include/boost/archive/detail/oserializer.hpp:233: error: incomplete type `boost::serialization::extended_type_info_null<MyNS::Succ>' used in nested name specifier Foo/boost-1_33_1/include/boost/archive/detail/iserializer.hpp: In constructor `boost::archive::detail::pointer_iserializer<T, Archive>::pointer_iserializer() [with T = MyNS::Succ, Archive = boost::archive::xml_iarchive]': Foo/boost-1_33_1/include/boost/archive/detail/iserializer.hpp:211: instantiated from `const boost::archive::detail::pointer_iserializer<MyNS::Succ, boost::archive::xml_iarchive> boost::archive::detail::pointer_iserializer<MyNS::Succ, boost::archive::xml_iarchive>::instance' Foo/boost-1_33_1/include/boost/archive/detail/iserializer.hpp:203: instantiated from `static const boost::archive::detail::pointer_iserializer<T, Archive>& boost::archive::detail::pointer_iserializer<T, Archive>::instantiate() [with T = MyNS::Succ, Archive = boost::archive::xml_iarchive]' Foo/boost-1_33_1/include/boost/archive/detail/iserializer.hpp:546: instantiated from `const boost::archive::detail::basic_pointer_iserializer& boost::archive::detail::instantiate_pointer_iserializer(Archive*, T*) [with Archive = boost::archive::xml_iarchive, T = MyNS::Succ]' Foo/boost-1_33_1/include/boost/archive/detail/interface_iarchive.hpp:57: instantiated from `const boost::archive::detail::basic_pointer_iserializer* boost::archive::detail::interface_iarchive<Archive>::register_type(T*) [with T = MyNS::Succ, Archive = boost::archive::xml_iarchive]' Foo/boost-1_33_1/include/boost/archive/detail/iserializer.hpp:449: instantiated from `static const boost::archive::detail::basic_pointer_iserializer* boost::archive::detail::load_pointer_type<Archive, Tptr>::non_abstract<T>::register_type(Archive&) [with T = MyNS::Succ, Archive = boost::archive::xml_iarchive, Tptr = MyNS::Succ*]' Foo/boost-1_33_1/include/boost/archive/detail/iserializer.hpp:465: instantiated from `static const boost::archive::detail::basic_pointer_iserializer* boost::archive::detail::load_pointer_type<Archive, Tptr>::register_type(Archive&, T&) [with T = MyNS::Succ, Archive = boost::archive::xml_iarchive, Tptr = MyNS::Succ*]' Foo/boost-1_33_1/include/boost/archive/detail/iserializer.hpp:485: instantiated from `static void boost::archive::detail::load_pointer_type<Archive, Tptr>::invoke(Archive&, Tptr&) [with Archive = boost::archive::xml_iarchive, Tptr = MyNS::Succ*]' Foo/boost-1_33_1/include/boost/archive/detail/iserializer.hpp:572: instantiated from `void boost::archive::load(Archive&, T&) [with Archive = boost::archive::xml_iarchive, T = MyNS::Succ*]' Foo/boost-1_33_1/include/boost/archive/basic_xml_iarchive.hpp:80: instantiated from `void boost::archive::basic_xml_iarchive<Archive>::load_override(const boost::serialization::nvp<T>&, int) [with T = MyNS::Succ*, Archive = boost::archive::xml_iarchive]' Foo/boost-1_33_1/include/boost/archive/xml_iarchive.hpp:74: instantiated from `void boost::archive::xml_iarchive_impl<Archive>::load_override(T&, int) [with T = const boost::serialization::nvp<MyNS::Succ*>, Archive = boost::archive::xml_iarchive]' Foo/boost-1_33_1/include/boost/archive/detail/interface_iarchive.hpp:76: instantiated from `Archive& boost::archive::detail::interface_iarchive<Archive>::operator>>(T&) [with T = const boost::serialization::nvp<MyNS::Succ*>, Archive = boost::archive::xml_iarchive]' Foo/test/src/Succ_Test.cc:58: instantiated from here Foo/boost-1_33_1/include/boost/archive/detail/iserializer.hpp:339: error: incomplete type `boost::serialization::extended_type_info_null<MyNS::Succ>' used in nested name specifier Foo/boost-1_33_1/include/boost/archive/detail/iserializer.hpp:339: error: incomplete type `boost::serialization::extended_type_info_null<MyNS::Succ>' used in nested name specifier Foo/boost-1_33_1/include/boost/archive/detail/oserializer.hpp: In constructor `boost::archive::detail::oserializer<Archive, T>::oserializer() [with Archive = boost::archive::xml_oarchive, T = MyNS::Succ]': Foo/boost-1_33_1/include/boost/archive/detail/oserializer.hpp:135: instantiated from `static boost::archive::detail::oserializer<Archive, T>& boost::archive::detail::oserializer<Archive, T>::instantiate() [with Archive = boost::archive::xml_oarchive, T = MyNS::Succ]' Foo/boost-1_33_1/include/boost/archive/detail/oserializer.hpp:235: instantiated from `boost::archive::detail::pointer_oserializer<T, Archive>::pointer_oserializer() [with T = MyNS::Succ, Archive = boost::archive::xml_oarchive]' Foo/boost-1_33_1/include/boost/archive/detail/oserializer.hpp:198: instantiated from `const boost::archive::detail::pointer_oserializer<MyNS::Succ, boost::archive::xml_oarchive> boost::archive::detail::pointer_oserializer<MyNS::Succ, boost::archive::xml_oarchive>::instance' Foo/boost-1_33_1/include/boost/archive/detail/oserializer.hpp:190: instantiated from `static const boost::archive::detail::pointer_oserializer<T, Archive>& boost::archive::detail::pointer_oserializer<T, Archive>::instantiate() [with T = MyNS::Succ, Archive = boost::archive::xml_oarchive]' Foo/boost-1_33_1/include/boost/archive/detail/oserializer.hpp:515: instantiated from `const boost::archive::detail::basic_pointer_oserializer& boost::archive::detail::instantiate_pointer_oserializer(Archive*, T*) [with Archive = boost::archive::xml_oarchive, T = MyNS::Succ]' Foo/boost-1_33_1/include/boost/archive/detail/interface_oarchive.hpp:58: instantiated from `const boost::archive::detail::basic_pointer_oserializer* boost::archive::detail::interface_oarchive<Archive>::register_type(const T*) [with T = MyNS::Succ, Archive = boost::archive::xml_oarchive]' Foo/boost-1_33_1/include/boost/archive/detail/oserializer.hpp:344: instantiated from `static const boost::archive::detail::basic_pointer_oserializer* boost::archive::detail::save_pointer_type<Archive, TPtr>::non_abstract<T>::register_type(Archive&) [with T = MyNS::Succ, Archive = boost::archive::xml_oarchive, TPtr = MyNS::Succ*]' Foo/boost-1_33_1/include/boost/archive/detail/oserializer.hpp:360: instantiated from `static const boost::archive::detail::basic_pointer_oserializer* boost::archive::detail::save_pointer_type<Archive, TPtr>::register_type(Archive&, T&) [with T = MyNS::Succ, Archive = boost::archive::xml_oarchive, TPtr = MyNS::Succ*]' Foo/boost-1_33_1/include/boost/archive/detail/oserializer.hpp:460: instantiated from `static void boost::archive::detail::save_pointer_type<Archive, TPtr>::invoke(Archive&, TPtr) [with Archive = boost::archive::xml_oarchive, TPtr = MyNS::Succ*]' Foo/boost-1_33_1/include/boost/archive/detail/oserializer.hpp:536: instantiated from `void boost::archive::save(Archive&, const T&) [with Archive = boost::archive::xml_oarchive, T = MyNS::Succ*]' Foo/boost-1_33_1/include/boost/archive/basic_xml_oarchive.hpp:99: instantiated from `void boost::archive::basic_xml_oarchive<Archive>::save_override(const boost::serialization::nvp<T>&, int) [with T = MyNS::Succ*, Archive = boost::archive::xml_oarchive]' Foo/boost-1_33_1/include/boost/archive/detail/interface_oarchive.hpp:78: instantiated from `Archive& boost::archive::detail::interface_oarchive<Archive>::operator<<(T&) [with T = const boost::serialization::nvp<MyNS::Succ*>, Archive = boost::archive::xml_oarchive]' Foo/test/src/Succ_Test.cc:48: instantiated from here Foo/boost-1_33_1/include/boost/archive/detail/oserializer.hpp:108: error: incomplete type `boost::serialization::extended_type_info_null<MyNS::Succ>' used in nested name specifier Foo/boost-1_33_1/include/boost/archive/detail/iserializer.hpp: In constructor `boost::archive::detail::iserializer<Archive, T>::iserializer() [with Archive = boost::archive::xml_iarchive, T = MyNS::Succ]': Foo/boost-1_33_1/include/boost/archive/detail/iserializer.hpp:146: instantiated from `static boost::archive::detail::iserializer<Archive, T>& boost::archive::detail::iserializer<Archive, T>::instantiate() [with Archive = boost::archive::xml_iarchive, T = MyNS::Succ]' Foo/boost-1_33_1/include/boost/archive/detail/iserializer.hpp:340: instantiated from `boost::archive::detail::pointer_iserializer<T, Archive>::pointer_iserializer() [with T = MyNS::Succ, Archive = boost::archive::xml_iarchive]' Foo/boost-1_33_1/include/boost/archive/detail/iserializer.hpp:211: instantiated from `const boost::archive::detail::pointer_iserializer<MyNS::Succ, boost::archive::xml_iarchive> boost::archive::detail::pointer_iserializer<MyNS::Succ, boost::archive::xml_iarchive>::instance' Foo/boost-1_33_1/include/boost/archive/detail/iserializer.hpp:203: instantiated from `static const boost::archive::detail::pointer_iserializer<T, Archive>& boost::archive::detail::pointer_iserializer<T, Archive>::instantiate() [with T = MyNS::Succ, Archive = boost::archive::xml_iarchive]' Foo/boost-1_33_1/include/boost/archive/detail/iserializer.hpp:546: instantiated from `const boost::archive::detail::basic_pointer_iserializer& boost::archive::detail::instantiate_pointer_iserializer(Archive*, T*) [with Archive = boost::archive::xml_iarchive, T = MyNS::Succ]' Foo/boost-1_33_1/include/boost/archive/detail/interface_iarchive.hpp:57: instantiated from `const boost::archive::detail::basic_pointer_iserializer* boost::archive::detail::interface_iarchive<Archive>::register_type(T*) [with T = MyNS::Succ, Archive = boost::archive::xml_iarchive]' Foo/boost-1_33_1/include/boost/archive/detail/iserializer.hpp:449: instantiated from `static const boost::archive::detail::basic_pointer_iserializer* boost::archive::detail::load_pointer_type<Archive, Tptr>::non_abstract<T>::register_type(Archive&) [with T = MyNS::Succ, Archive = boost::archive::xml_iarchive, Tptr = MyNS::Succ*]' Foo/boost-1_33_1/include/boost/archive/detail/iserializer.hpp:465: instantiated from `static const boost::archive::detail::basic_pointer_iserializer* boost::archive::detail::load_pointer_type<Archive, Tptr>::register_type(Archive&, T&) [with T = MyNS::Succ, Archive = boost::archive::xml_iarchive, Tptr = MyNS::Succ*]' Foo/boost-1_33_1/include/boost/archive/detail/iserializer.hpp:485: instantiated from `static void boost::archive::detail::load_pointer_type<Archive, Tptr>::invoke(Archive&, Tptr&) [with Archive = boost::archive::xml_iarchive, Tptr = MyNS::Succ*]' Foo/boost-1_33_1/include/boost/archive/detail/iserializer.hpp:572: instantiated from `void boost::archive::load(Archive&, T&) [with Archive = boost::archive::xml_iarchive, T = MyNS::Succ*]' Foo/boost-1_33_1/include/boost/archive/basic_xml_iarchive.hpp:80: instantiated from `void boost::archive::basic_xml_iarchive<Archive>::load_override(const boost::serialization::nvp<T>&, int) [with T = MyNS::Succ*, Archive = boost::archive::xml_iarchive]' Foo/boost-1_33_1/include/boost/archive/xml_iarchive.hpp:74: instantiated from `void boost::archive::xml_iarchive_impl<Archive>::load_override(T&, int) [with T = const boost::serialization::nvp<MyNS::Succ*>, Archive = boost::archive::xml_iarchive]' Foo/boost-1_33_1/include/boost/archive/detail/interface_iarchive.hpp:76: instantiated from `Archive& boost::archive::detail::interface_iarchive<Archive>::operator>>(T&) [with T = const boost::serialization::nvp<MyNS::Succ*>, Archive = boost::archive::xml_iarchive]' Foo/test/src/Succ_Test.cc:58: instantiated from here Foo/boost-1_33_1/include/boost/archive/detail/iserializer.hpp:115: error: incomplete type `boost::serialization::extended_type_info_null<MyNS::Succ>' used in nested name specifier make: *** [test/obj/Succ_Test.o] Error 1 //========================================================

2 1

boost::filesystem question: iterate upcast directory path string?
by David Xiao 23 Dec '05

23 Dec '05

Hi Friends: For example I have path "C:\Temp\abcd\hello\", I wish to iterate to get C: , C:\Temp , C:\Temp\abcd , C:\Temp\abcd\hello . I have read code of path::iterator, but not what I expected.... How to do it? I also want to have the code portable for UNIX paths, means also work for "/foo/bar1/bar2/bar3/" ... Thanks for your help! Rgds, David

3 2

Re: [Boost-users] [BGL] Remove all vertices from graph with zero degree
by Dmitry Bufistov 23 Dec '05

23 Dec '05

Hello Jeffrey, I'm sorry for long silence, but better later then never, Thank you very much for help! Merry Christmas! Best regards, --Dmitry > The way that I had to implement a template function to erase a graph > was like: > template<typename T1> inline void > WorkFlow_Datum::EraseGraph(T1& g) > { > typedef typename std::vector<typename > boost::graph_traits<T1>::vertex_descriptor> Vertices; > Vertices vertices; > typename boost::graph_traits<T1>::vertex_iterator vi,vi_end; > for (boost::tie(vi,vi_end)=boost::vertices(g);vi!=vi_end;++vi) > vertices.push_back(*vi); > for (typename Vertices::reverse_iterator > iter=vertices.rbegin();iter!=vertices.rend();++iter) { > boost::clear_vertex(*iter,g); > boost::remove_vertex(*iter,g); > } > } > > My graph uses vectors, so I suspect that you need to use something > similiar to avoid iterator instability and vertice descriptor > instability. The later is way a reverse iterator was needed. >

1 0

asio review extended till Dec 30th
by Jeff Garland 23 Dec '05

23 Dec '05

Please post review comments to developer list... ---- Thanks to everyone for the excellent reviews and discussions of asio! Some folks want additional time for the asio review, so the review will be extended until Dec 30th. Note that Chrisopher may not be able to respond to posts during a significant part of this time due to holiday commitments, but the feedback will eventually be addressed and discussed. In the way of reminder, here's the library details again: Today (Dec 22nd) is the first continuation of the formal review of the Asynchronous I/O library (asio) library by Christopher Kohlhoff. The review will run be extended until Friday December 30th. I will be serving as review manager. >From the library synopsis: Boost.Asio is a cross-platform C++ library for network programming that provides developers with a consistent asynchronous I/O model using a modern C++ approach. Downloads of the library as well as online documentation can be found at: http://asio.sourceforge.net/ http://asio.sourceforge.net/boost-asio-proposal-0.3.6/libs/asio/doc/ As usual, please state in review comments how you reviewed the library and whether the you think the library should be accepted into Boost. Further guidelines for writing reviews can be found on the website at: http://www.boost.org/more/formal_review_process.htm#Comments Please review early and often! Thanks, Jeff ******************************************************* A Few Library Details: ******************************************************* Supported Platforms The following platforms and compilers have been tested: * Win32 using Visual C++ 7.1 and Visual C++ 8.0. * Win32 using Borland C++Builder 6 patch 4. * Win32 using MinGW. * Linux (2.4 or 2.6 kernels) using g++ 3.3 or later. * Solaris using g++ 3.3 or later. * Mac OS X 10.4 using g++ 3.3 or later. Rationale The Boost.Asio library is intended for programmers using C++ for systems programming, where access to operating system functionality such as networking is often required. In particular, Boost.Asio attempts to address the following goals: * Portability. The library should support, and provide consistent behaviour across, a range of commonly used operating systems. * Scalability. The library should allow, and indeed encourage, the development of network applications that scale to hundreds or thousands of concurrent connections. The library implementation for each operating system should use the mechanism that best enables this scalability. * Efficiency. The library should support techniques such as scatter-gather I/O, and allow protocol implementations that minimise data copying. * Model Berkeley sockets. The Berkeley sockets API is widely implemented and understood, as well as being covered in much literature. Other programming languages often use a similar interface for networking APIs. * Ease of use. Lower the entry barrier for new users by taking a toolkit, rather than framework, approach. That is, try to minimise the up-front investment in time to just learning a few basic rules and guidelines. After that, a library user should only need to understand the specific functions that are being used. * Basis for further abstraction. The library should permit the development of other libraries that provide higher levels of abstraction. For example, implementations of commonly used protocols such as HTTP. Although the current incarnation of Boost.Asio focuses primarily on networking, its concepts of asynchronous I/O can be extended to include other operating system resources such as files.

1 0

linker problem with date_time library
by Oliver.Kowalke＠infineon.com 23 Dec '05

23 Dec '05

Hi, I get an linker message if I compile my app with gcc-3.4.2 on Linux and link it against date_time library of boost 1.33.1: /usr/lib/gcc-lib/i586-suse-linux/3.3.1/../../../../i586-suse-linux/bin/l d: `.L1966' referenced in section `.rodata' of .libs/oci_date.o: defined in discarded section `.gnu.linkonce.t._ZN5boost9date_time23gregorian_calendar_baseINS0_19year _month_day_baseINS_9gregorian9greg_yearENS3_10greg_monthENS3_8greg_dayEE EmE16end_of_month_dayES4_S5_' of .libs/oci_date.o I only instantiate an ptime and call time_from_string and to_iso_extended_string. What is going wrong? Regards, Oliver

2 1

Re: [Boost-users] [serialization] Can't compile archive I/O
by Merrill Cornish 23 Dec '05

23 Dec '05

Robert, Thanks for your prompt response. I saw the compile-time assert saying the problem was probably a missing wrapper, but for some reason, I never thought about the temporary object used to make the test. Thanks again. Merrill

1 0

compiling 1_33_1 with vc6 / sp6 fails with error C2258...
by Ingo Becker 23 Dec '05

23 Dec '05

Hi, i try to compile boost_1_33_1 or boost_1_33_0 with Visual C++ 6 (SP 6) on Windows XP (SP 2) and also on Windows 2000 (SP 4). The libraries date_time, filesystem, iostreams, regex, signals, test, thread, wave seems to be compiled without errors. But then..... The compilation fails with a syntax-error (pure virtual method needs '=0'...). ... vc-C++ bin\boost\libs\program_options\build\libboost_program_options.lib\msvc\debug\runtime-link-static\cmdline.obj cmdline.cpp F: \boost_init\boost_1_33_1\boost/program_options/options_description.hpp(156) : error C2258: Ungueltige Syntax fr rein virtuelle Methode; '= 0' erforderlich F: \boost_init\boost_1_33_1\boost/program_options/options_description.hpp(156) : error C2252: 'm_default_line_length' : Nur Funktionen koennen rein virtuell deklariert werden F: \boost_init\boost_1_33_1\boost/program_options/options_description.hpp(159) : error C2065: 'm_default_line_length' : nichtdeklarierter Bezeichner ... Something i've forgotten to set/configure ? Any help would be apreciated. Ingo

3 2

unchain_ptr functionality?
by Alo Sarv 23 Dec '05

23 Dec '05

Hi all When writing generic code, it's sometimes needed to call a member function of a passed object, however it's not known at the implementation time whether the function is passed a pointer or reference to the object. For example: template<typename T> void process(T t) { t.foo(); } This breaks as soon as the function is passed a pointer (or smart pointer) type, which means one needs to either provide overloads for all those cases (inconvenient), or have means of unchaining the pointer (it could also be pointer-to-pointer for example). Basically I'm looking for syntax like this: template<typename T> void process(T t) { unchain_ptr(t).foo(); } struct X { void foo() {} }; X *x = new X; process(x); process(&x); process(*x); process(boost::shared_ptr<X>(x)); // etc Is there such an utility in Boost libraries? Currently I wrote the implementation myself, and achieved the expected syntax, but perhaps there's an existing implementation already that I could use instead? I saw some libraries (multi_index) using something like this internally, but there doesn't seem to be any "end-user" API for this as far as I can see... Alo Sarv

2 1

bug in signals library? - segmentation fault (only linked) -> exit(11) called
by Oliver.Kowalke＠infineon.com 23 Dec '05

23 Dec '05

Hello, I get an segmentation fault if I try to link against libboost_signals-gcc-1_33_1 or libboost_signals-gcc-mt-1_33_1! The application consist only of an empty main function and the binary is linked against the signals library. I've appended an output (tusc.out) of tusc (trace unix system calls) which indicates, that exit(11) is called and so a core dump created. System: HP/UX 11.11 PA-RISC Compiler: gcc-3.4.4 (with posix thread support) Code: int main( int argc, char* argv[]) { return 0; } Compiled with: if g++ -DHAVE_CONFIG_H -I. -I/eda-home/kowalke/Projects/test/src -I.. -I/opt/boost/include/boost-1_33_1 -O0 -g3 -MT test.o -MD -MP -MF ".deps/test.Tpo" -c -o test.o /eda-home/kowalke/Projects/test/src/test.cpp; then mv -f ".deps/test.Tpo" ".deps/test.Po"; else rm -f ".deps/test.Tpo"; exit 1; fi /bin/sh ../libtool --tag=CXX --mode=link g++ -O0 -g3 -o test -L/opt/boost/lib test.o -lboost_signals-gcc-1_33_1 mkdir .libs g++ -O0 -g3 -o test test.o -L/opt/boost/lib -lboost_signals-gcc-1_33_1 <<tusc.out>>

2 1