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

assignment library with functors
by gast128 06 Dec '05

06 Dec '05

Dear all, I am too tired to investigate it deeply, so does anyone know why this does not compile (on VS 2003): typedef boost::function<int (const int& , const int&)> BinOperand; typedef std::vector<BinOperand> BinOperandVector; BinOperandVector operands = boost::assign::list_of(std::plus<int>()) (std::minus<int>()) (std::multiplies<int>()) (std::divides<int>()); Wkr, me

3 3

Serialization/pickle
by Drumheller, Michael 06 Dec '05

06 Dec '05

>> From: David Abrahams <dave <at> boost-consulting.com> >> Subject: Re: Boost.python serialization >> Newsgroups: gmane.comp.lib.boost.user >> Date: 2005-11-29 23:28:17 GMT (6 days, 17 hours and 9 minutes ago) >> >> "Drumheller, Michael" <michael.drumheller <at> boeing.com> writes: >> >> > Thank you for the help. I have seen that link (the one you supplied) >> > before, but I posted my question because that link in particular does >> > not mention the words "Boost.Serialization" or "Archive" at all. >> >> That's because the Boost Serialization library is unrelated. I understand that it is technically unrelated. I am asking for information about about patterns of actual usage. >> > I suppose what I was really getting at, and was probably not very >> > clear about (sorry :| ) was whether the specific approach (by >> > N. Becker) of using a stringstream wrapped with a >> > boost::archive::binary_oarchive is a standard idiom. >> >> "Standard?" OK: "common," "popular," "preferred," "regarded-as-best-practice," "effective." >> > (Basically, I would have thought that "python pickle boost::archive" >> > would be a million-hit Google query, but it's only about a dozen. I >> > find that weird. Do people just not serialize their C++ extensions >> > very often?) >> >> Yes, they do it very often. There's usually no need to touch >> Boost.Serialization in order to do so, though. My extensions refer to one another, i.e., they form a significant object hierarchy in and of themselves. E.g., on the C++ side I might have an instance x of class X, which contains a vector of shared_ptrs p1,...,pn to instances y1,...,yn of another C++ class Y. At pickle-time there may be Python object z with a member u bound to to x and members w1,...,wm bound to a subset of the y1,...,yn. Is it even feasible to expect to be able to simple pickle.dump z and have it all work? Please keep in mind: I am just getting started wading into serializing a pretty complicated set of strongly interdependent Python and C++ objects and I am just trying to get my bearings. If this is the wrong forum to be asking these questions, please tell me. MD >> -- >> Dave Abrahams >> Boost Consulting >> www.boost-consulting.com

2 1

threads - thread_resource_error thrown by creating more than 256 threads
by Oliver.Kowalke＠infineon.com 06 Dec '05

06 Dec '05

Hi, if I try to create more than 255 threads (256 for instance) I get the exception thread_resource_error thrown. How can I increase the amount of threads? My System: Linux 2.4.21, gcc 3.3.1 (posix thread model). cat /proc/sys/kernel/threads-max --> max 12152 threads per process currently allowed With best regards, Oliver

3 2

Problem compiling boost on HP11i with aCC
by Gaurav Gehlot 06 Dec '05

06 Dec '05

I am trying to compile boost 1.30.02 library with aCC 03.55 on HP-UX 11i, but I am getting following errors. Can anybody pls tell me what is causing these errors. aCC -AA -c +W823 -I/data/projects/sable/appl/ggehlot/boost-1.30.2 -DNDEBUG -DBOOST_DATE_TIME_POSIX_TIME_STD_CONFIG -O3 +Z -I" libs/date_time/build" -I"/data/projects/sable/appl/ggehlot/boost-1.30.2" -o "libs/date_time/build/bin/libboost_date_time.so/acc/release /runtime-link-dynamic/shared-linkable-true/greg_month.o" "libs/date_time/build/../src/gregorian/greg_month.cpp" ...failed aCC-C++-action libs/date_time/build/bin/libboost_date_time.so/acc/release/runtime-link-dynamic/shared-linkable-true/greg_month. o... ...skipped <libs!date_time!build/libboost_date_time.so/acc/release/runtime-link-dynamic/shared-linkable-true>libboost_date_time.so for la ck of <libs!date_time!build/libboost_date_time.so/acc/release/runtime-link-dynamic/shared-linkable-true>greg_month.o... ...skipped <libs!regex!build/libboost_regex.so/acc/debug/runtime-link-dynamic/shared-linkable-true>libboost_regex.so for lack of <libs!re gex!build/libboost_regex.so/acc/debug/runtime-link-dynamic/shared-linkable-true>cregex.o... aCC-Link-action libs/signals/build/bin/libboost_signals.so/acc/debug/runtime-link-dynamic/shared-linkable-true/libboost_signals.so /usr/ccs/bin/ld: Unsatisfied symbols: main (Not referenced yet! Probably due to -u option) aCC -g -AA -o "libs/signals/build/bin/libboost_signals.so/acc/debug/runtime-link-dynamic/shared-linkable-true/libboost_signals.so" "libs/signals/build/bin/libboost_signals.so/acc/debug/runtime-link-dynamic/shared-linkable-true/trackable.o" "libs/signals/build/bin/ libboost_signals.so/acc/debug/runtime-link-dynamic/shared-linkable-true/connection.o" "libs/signals/build/bin/libboost_signals.so/acc/deb ug/runtime-link-dynamic/shared-linkable-true/signal_base.o" "libs/signals/build/bin/libboost_signals.so/acc/debug/runtime-link-dynamic/sh ared-linkable-true/slot.o" ...failed aCC-Link-action libs/signals/build/bin/libboost_signals.so/acc/debug/runtime-link-dynamic/shared-linkable-true/libboost_signals .so... ...removing libs/signals/build/bin/libboost_signals.so/acc/debug/runtime-link-dynamic/shared-linkable-true/libboost_signals.so aCC-Link-action libs/signals/build/bin/libboost_signals.so/acc/release/runtime-link-dynamic/shared-linkable-true/libboost_signals.so /usr/ccs/bin/ld: Unsatisfied symbols: main (Not referenced yet! Probably due to -u option) aCC -s -AA -o "libs/signals/build/bin/libboost_signals.so/acc/release/runtime-link-dynamic/shared-linkable-true/libboost_signals.s o" "libs/signals/build/bin/libboost_signals.so/acc/release/runtime-link-dynamic/shared-linkable-true/trackable.o" "libs/signals/build/ bin/libboost_signals.so/acc/release/runtime-link-dynamic/shared-linkable-true/connection.o" "libs/signals/build/bin/libboost_signals.so/a cc/release/runtime-link-dynamic/shared-linkable-true/signal_base.o" "libs/signals/build/bin/libboost_signals.so/acc/release/runtime-link- dynamic/shared-linkable-true/slot.o" ...failed aCC-Link-action libs/signals/build/bin/libboost_signals.so/acc/release/runtime-link-dynamic/shared-linkable-true/libboost_signa ls.so... ...removing libs/signals/build/bin/libboost_signals.so/acc/release/runtime-link-dynamic/shared-linkable-true/libboost_signals.so aCC-Link-action libs/test/build/bin/libboost_prg_exec_monitor.so/acc/debug/runtime-link-static/shared-linkable-true/threading-single/libb oost_prg_exec_monitor.so /usr/ccs/bin/ld: Can't find library: "libstd_v2.a" aCC -llibstd_v2.a -g -AA -o "libs/test/build/bin/libboost_prg_exec_monitor.so/acc/debug/runtime-link-static/shared-linkable-true/t hreading-single/libboost_prg_exec_monitor.so" "libs/test/build/bin/libboost_prg_exec_monitor.so/acc/debug/runtime-link-static/shared-l inkable-true/threading-single/execution_monitor.o" "libs/test/build/bin/libboost_prg_exec_monitor.so/acc/debug/runtime-link-static/shared -linkable-true/threading-single/cpp_main.o" ...failed aCC-Link-action libs/test/build/bin/libboost_prg_exec_monitor.so/acc/debug/runtime-link-static/shared-linkable-true/threading-s ingle/libboost_prg_exec_monitor.so... aCC-Link-action libs/test/build/bin/libboost_prg_exec_monitor.so/acc/debug/runtime-link-static/shared-linkable-true/threading-multi/libbo ost_prg_exec_monitor.so /usr/ccs/bin/ld: Can't find library: "libstd_v2.a" ----------------------------------------- This message and its attachments may contain privileged and confidential information. If you are not the intended recipient(s), you are prohibited from printing, forwarding, saving or copying this email. If you have received this e-mail in error, please immediately notify the sender and delete this e-mail and its attachments from your computer.

1 0

Wave: how to recover after errors?
by Max Motovilov 06 Dec '05

06 Dec '05

I have a simple problem: wave warnings (specifically, macro re-definition) are reported as exceptions thrown from [potentially, any of, at least I don't yet know better] the methods of pp_iterator. It is very simple to catch one and print a message, however I can't figure out how to recover after one. Can't seem to find any mention of error recovery in documentation, tried some variations of last_known_good_iterator (store a copy before every increment, restore back to known copy in exception handler) -- it recovers simple cases but on more complex files there appears to be internal state corruption. Also, even when this recovery works, it leaves macro in the pre-redefinition state whereas the usual cpp policy is to allow redefinition and print a warning. I thought of using a preventive strategy -- undefine the existing macro from a policy method -- but unfortunately the exception is thrown before defined_macro() is called. Looks like it's time to ask the owners of the library: how do I do this? :-) Thanks in advance, ...Max... PS. I am using 1.33.0; should I _really_ _really_ be upgrading to 1.33.1 to get this resolved?

3 8

[serialization] seriazation from base pointer / Runtime Casting
by __PPS__ 06 Dec '05

06 Dec '05

is it possible to have this exported from dll: ///export.h/// #include <boost/serialization/serialization.hpp> class session_record { virtual void print_on(std::ostream& os) const = 0; friend std::ostream & operator<<(std::ostream& os, const session_record& sr){ sr.print_on(os); return os; } public: friend class boost::serialization::access; virtual ~session_record(); template<class Archive> void serialize(Archive & ar, const unsigned int file_version){} operator session_record *(); }; void serialize(session_record* derived, const char* file_name); session_record* deserialize(const char* file_name); ///end of export.h/// and then in an application (linked to the dll that exports all from export.h) I create derived classes from session_record and serialize or deserialize them to/from files using the two exported free functions. I followed exactly steps in "Runtime Casting" of the manual, but it doesn't work. So... is it really runtime if it doesn't work this way - it only works if all the derived classes are known & registered at the time of compilation of the two functions. All that worked well if everything from export.h was linked statically, but not dynamically Am I doing something wrong with all that stuff?? thanks

2 4

STLPort & VC++ 8?
by Jerker Öhman 06 Dec '05

06 Dec '05

Does anyone know if there are plans to support STLPort 5 with Visual C++ 8? Although Microsoft know ships a good implementation of STL, STLPort is much faster and has a nice debug mode so I think it would be nice to continue to support it. /Jerker

1 0

Implementing an Event class
by Raffaele Romito 06 Dec '05

06 Dec '05

Hi, I need to implement an Event class around (I suppose) boost::condition. The class needs the follow interface class Event { public: Event(); ~Event(); public: void reset(); void signal(); void wait(unsigned int ms = 0); // 0 = infinite }; Any advice? Thanks

1 0

Re: [Boost-users] [multi_index] Problem with find() and Hashed_Index
by Martin Higham 06 Dec '05

06 Dec '05

Thats just what I needed to know. It's all working fine now. Thanks Martin > From: JOAQUIN LOPEZ MU?Z <joaquin(a)tid.es> > To: boost-users(a)lists.boost.org > Date: Sun, 04 Dec 2005 00:31:08 +0100 > Subject: Re: [Boost-users] [multi_index] Problem with find() and > Hashed_Index > Hello Martin, > > ----- Mensaje original ----- > De: Martin Higham <martinh(a)gmail.com> > Fecha: Sábado, Diciembre 3, 2005 11:42 am > Asunto: [Boost-users] [multi_index] Problem with find() and > Hashed_Index > > > I have created a multi_index_container inline with one ordered_unique > > index and one hashed_unique index as demonstrated in the > > documentation > > > (http://www.boost.org/libs/multi_index/doc/advanced_topics.html#hash_lo > okup).I can happily add and retrieve items using find() as indicated. > > > > However, if I use the =* operator as indicated and there is no > > matching record a memory error occurs. > > > > Therefore I need to assign the find result to an iterator and check > > for end(). Can anyone tell me what type this iterator should be? I've > > tried many combinations non of which compile. > > There are several syntaxes to get to the type > of the iterator: > > your_container_type::nth_index<N>::type::iterator > your_container_type::index<Tag>::type::iterator > your_container_type::nth_index_iterator<N>::type > your_container_type::index_iterator<Tag>::type > > Where N is the 0-based ordinal of the index you're > interested in. If the index is tagged, you can also > use the <Tag> variations. > Does this help? Thanks for using Boost.MultiIndex! > > Joaquín M López Muñoz > Telefónica, Investigación y Desarrollo >

1 0

Boost.Filesystem DLL builds on Mingw
by Alo Sarv 06 Dec '05

06 Dec '05

The topic itself is already few months old, namely the fact that Boost.Filesystem library breaks on Mingw in DLL builds. As I see from regression tests, this issue hasn't been fixed yet. The reason I'm bringing this up again is that while originally it was concluded that static builds should be used on Mingw instead of DLL builds, it is becoming an increasing problem for me, since default_name_check doesn't work across DLL boundaries when B.FS is linked statically to one of the DLL's, which results unexpected exceptions being thrown all over my codebase unless I explicitly construct paths using native name-checker, but tracking all those places is a constant headache. Is there any plans on addressing this issue, or are there any additional workarounds to have default_name_check functioanlity working across DLL boundaries when Boost.Filesystem is linked statically? My experience has been that mixing dynamic and static libraries is a really bad idea... Alo Sarv

3 2