- Boost-users - lists.boost.org

Re: [Boost-users] Serialization : unregistered_cast & otherquestions
by RIVASSEAU Jean Noel 24 Feb '06

24 Feb '06

I forgot the code promised in last email sorry... _____ De : boost-users-bounces(a)lists.boost.org [mailto:boost-users-bounces@lists.boost.org] De la part de Robert Ramey Envoyé : jeudi 23 février 2006 17:44 À : boost-users(a)lists.boost.org Objet : Re: [Boost-users] Serialization : unregistered_cast & otherquestions Without actually seeing the code, its hard for me to give intelligent advice. Lucky for you (maybe) that's not going to inhibit me from speculating. Here is what I recommend for anyone making a very large program: a) extended_type_info_no_rtti presumes that all classes serialized as pointers have been exported. Should this not be the case, you'll get the error message indicated. Double check this. b) Serilaization traits should be in the header files so that they are not "missed" anytime something like "ar << x" is invoked. Given you're situation I would recommend a file structure like the following: class.hpp - without seriaiization like you have now. serialization/class.hpp - includes class.hpp. also includes BOOST_EXPORT and any other traits for this "class". serialization/class.cpp c - includes serialization/class.hpp and includes the actual serialization code. Also this should include code instantiation for the archives that you use. Look at demo_pimpl to see how this is done. All the above code should be organized into a library. The reason is that this will generate code for all the archives mentioned but your application may not use all the archives so putting the above code in a library and linking to it will mean that your application will always have what it actuallyuses but nothing it doesn't - avoids "code bloat". Note that in compiling code for the library make sure to specify "function level linking". Take the "least derived class" - that one at the top of the class hierarchy. Make a small test program similar to the tests in the serialization library. This should be a very small job. This code can be class_test.cpp. Run this test on all archives you use. When this test passes, do the same for the other classes until something fails. This might seem to be more work - believe me its not. It will a) guarentee that you make progress toward a robust program b) give you confidence that your program has minimum of hidden bugs c) permit you to re-run the tests automatically when you make future changes. d) should a problem arise with the serialization or other library, it will give a lot more information in order to be helpful. Robert Ramey Now, the problem is where to put the serialization code for these classes. If I just write them on the implementation file (the .cc) for the class, it does not work. At run time I have always errors telling me that either the class is not exported (unregistered_class exception) or an unregistered_cast happens. The only solution I have found is to put *ALL* serialization code into the same big .cc file. If I do just that, it works. However this file is becoming enormous and has to be recompiled every time I change only *one* of the class to be serialized. It is already taking a minute to compile on a fast machine, so I must really break it up into other parts. But everytime I do that everything stops working. Have you any ideas, Robert? I am using extended_type_info_no_rtti, this may be the cause of the problem... Jean-Noël Ps: I still have the std::string bug, which is also uncomprehensible for me. _____ _______________________________________________ Boost-users mailing list Boost-users(a)lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users

1 0

using boost libs in a managed C++ dll (vc7.1)
by KonT 24 Feb '06

24 Feb '06

Hi, This is my second attempt to get some help on this issue... Can anyone provide a pointer to the steps required to using a boost lib in a managed C++ dll. I am using boost 1.33.1 with vc7.1. Boost libs were built with default options using bjam (bjam "-sTOOLS=vc-7_1" install). I am able to build a dll, but .net app using the dll crashes when it attempts to call code from the boost libs (in my case date). Building either managed or unmanaged static libs & using in a managed c++ app work fine, so I suspect that the problem is due to dll loader issues. I have tried linking with static & dynamically linked libs (CRT & boost), but the result is the same. I have built the dll with the /NO ENTRY switch & added manual calls to initialise the CRT. This removes the vc warnings, but the dll still cause the app to crash. Thanks in advance Kon Tantos

1 0

[Boost.date-time] Problem with leak with time_from_string? Incorrect use, or other problem?
by Stewart Loving-Gibbard 24 Feb '06

24 Feb '06

We have observed leaky behavior while using the Boost.date-time libraries, with time_from_string specifically. The leak is simple to replicate for us, on both Win32 (Visual Studio .NET 2005) and on Linux (GCC 3.x). This code snippet leaks for us, at a rate of about a MB every 10 seconds: while (true) { time_from_string("2002-01-20 23:59:59"); } As far as I can tell, ptime (what time_from_string returns) is an object that doesn't need to be deallocated with a Boost API function. So, why are we leaking here? Did we compile Boost incorrectly? Is there a way to link Boost that can trigger a leak? (from_iso_string() also appears to leak for us, by the way, while to_iso_string does not. It looks like time_from_string and to_iso_string are in the same neighborhood, so I'm betting they share the same fix.) Any and all help appreciated. This is a blocking issue for us. Stewart

3 4

Re: [Boost-users] [spirit] should be a very simple problem, but I'm stumped
by Nat Goodspeed 23 Feb '06

23 Feb '06

> -----Original Message----- > From: boost-users-bounces(a)lists.boost.org [mailto:boost-users- > bounces(a)lists.boost.org] On Behalf Of Todd Day > Sent: Thursday, February 23, 2006 9:35 AM > To: boost-users(a)lists.boost.org > Subject: [Boost-users] [spirit] should be a very simple problem,but I'm > stumped > > I have to look for strings of the form (including the > quotes) > "ParmName: ParmValue" > I'm looking for certain ParmNames, and I have to grab the associated > ParmValue. [Nat] Maybe the Spirit parser is the wrong place to get specific about the ParmNames you're seeking? Maybe what you should do is parse *every* item of that form, stuffing the pairs into a std::map. Then you can extract from that map the specific items you want.

1 0

Re: [Boost-users] [statechart] Asynchronous Machines
by Gottlob Frege 23 Feb '06

23 Feb '06

> Date: Thu, 23 Feb 2006 11:45:00 -0500 > From: Kim Barrett <kab(a)irobot.com> > Subject: Re: [Boost-users] [statechart] Asynchronous Machines > To: boost-users(a)lists.boost.org > Message-ID: <p06230901c02396579da8(a)[192.168.1.102]> > Content-Type: text/plain; charset="us-ascii" ; format="flowed" > > At 2:08 AM -0500 2/23/06, Gottlob Frege wrote: > >All in the hopes of making at least a start on a useful atomics library. > > Are you familiar with the atomic operations library at > http://www.hpl.hp.com/research/linux/atomic_ops > > Yep, thanks. That's probably the level I'm thinking of, but I'd just like to see a few more libraries and know what some of the edges are. Every library I see tends to say that they avoid handling the esoterics, and I would as well, but I'd like to know better what the esoterics are so that they can later be added without redoing everything, if at all possible.

1 0

Serialization : unregistered_cast & other questions
by RIVASSEAU Jean Noel 23 Feb '06

23 Feb '06

Hello First I would like to point out a bug in the documentation : void_register_cast <Derived, Base> MUST take two (bogus) arguments, so calling void_register_cast <Derived, Base> () as said in the documentation will not work. I had to look at the code to figure that out. Secondly, I am at the point where I am wondering if I should have started to use the BSL at all. The library is undoubtly useful but is plagued by strange things that must be done in order for it to run smoothly. I do not at all understand how the system works behind the scenes; I would not care if it would "just work" but this is not the case. My problem is: Ok, I have lots of classes, many of which need to be persistent. So, I have written serialization code for them. I have always written my code as non-intrusive, which means I have not used member functions, but templated functions. Now, the problem is where to put the serialization code for these classes. If I just write them on the implementation file (the .cc) for the class, it does not work. At run time I have always errors telling me that either the class is not exported (unregistered_class exception) or an unregistered_cast happens. The only solution I have found is to put *ALL* serialization code into the same big .cc file. If I do just that, it works. However this file is becoming enormous and has to be recompiled every time I change only *one* of the class to be serialized. It is already taking a minute to compile on a fast machine, so I must really break it up into other parts. But everytime I do that everything stops working. Have you any ideas, Robert? I am using extended_type_info_no_rtti, this may be the cause of the problem... Jean-Noël Ps: I still have the std::string bug, which is also uncomprehensible for me.

2 1

filter_iterator usage
by Nico Galoppo 23 Feb '06

23 Feb '06

Hi, I have a class with some custom iterators, I would like to add another custom iterator that is a 'filtered' version of the custom iterator. Something like this: class A { public: typedef boost::filter_iterator<predicate_type, custom_iterator> filtered_iterator; filtered_iterator begin() { predicate_type predicate = boost::bind(...); return boost::make_filter_iterator(predicate, custom_begin(), custom_end()); } } Unfortunately, the following code doesn't compile: A a; A::filtered_iterator it = a.begin(); Reason: cannot convert from 'boost::filter_iterator<Predicate,Iterator>' to 'const boost::filter_iterator<Predicate,Iterator>' I can give more compiler output if needed. Thanks! --nico -- nico galoppo von borries @ address: 105 creel st., chapel hill comp. graphics phd. student @ north carolina, 27516 USA UNC, chapel hill @ phone: +1 (919) 962-1898 (office) @ +1 (919) 942-7609 (home) @ email: nico at cs dot unc dot edu @ homepage: http://www.cs.unc.edu/~nico --- debian linux :: vim powered

2 1

[spirit] should be a very simple problem, but I'm stumped
by Todd Day 23 Feb '06

23 Feb '06

There has got to be a very very easy problem, but I've been knocking around for the better part of 12 hours in the docs and the examples and in google groups and the spirit list, and I've not made any progress. There must be some basic concept I'm totally missing out on. This is my first cut at using Spirit. I have the following, which is a simplified version of what I'm really after. Basically, I have to look for strings of the form (including the quotes) "ParmName: ParmValue" I'm looking for certain ParmNames, and I have to grab the associated ParmValue. This is what the code below is supposed to do. list<string> sl; rule<> parm_string = ch_p('"') >> str_p("DeviceName") >> ch_p(':') >> *blank_p >> (*~ch_p('"'))[push_back_a(sl)] >> ch_p('"'); rule<> r = *~ch_p('"') >> parm_string; parse(str, *r); This works just find when str = " (text \"DeviceName: Altera in Controller\" (blah))"; It properly returns to me only the value, which is Altera in Controller However, inserting the quoted word "broken" is enough to break it, like so str = "\"broken\" (text \"DeviceName: Altera in Controller\" (blah))"; In other words, it doesn't work if non-matching random quoted text is found. The problem in my rule r is the *~ch_p('"'). I thought this rule would mean, (a) eat all non-quoted characters until followed by (b) my parm match. But the rule really says, (a) eat all non-quoted characters, then stop working if it isn't followed by (b) my parm match. I think I might be screwed here since *anychar_p is greedy and I can't figure out how to otherwise skip over bad stuff. It still doesn't make sense to me that the simpler parse(str, *parm_string) does not work. I'm not sure why I have to specify the characters I want to skip if I've specified the characters I want to match. Perplexed, and thanking you profusely in advance for any help, -todd- PS - hopefully, any solution does not involve a skip rule. These don't seem to work when parsing file_iterators, which is what I'm really trying to do. I get compile errors that I don't get when using the simple string version of parse(). Also, don't skip rules run *after* a match has first been made?

1 0

how to get free space of a folder (or disk) using boost?
by hongxing 23 Feb '06

23 Feb '06

how to get free space of a folder (or disk) using boost? I am no using boost 1.33 in windows xp sp2 and SuSE Linux Enterprise Server sp2 thanks!

3 2

Serialization problem with polymorphic archives and std::string
by Michael Sperber 23 Feb '06

23 Feb '06

Hi there, I'm trying to convert a piece of code from templated archives to polymorphic ones, and am running into trouble when serializing std::string. Either I get an error message saying that std::string has no serialize member function, or I get the attached message. The relevant code is this: ---snip--- #include <boost/serialization/serialization.hpp> #include <boost/archive/polymorphic_iarchive.hpp> #include <boost/archive/polymorphic_oarchive.hpp> void mtime::serialize(boost::archive::polymorphic_iarchive& ar, const unsigned int file_version) { std::string iso; ar & boost::serialization::make_nvp("iso_time", iso); set_from_iso_string(iso); } void mtime::serialize(boost::archive::polymorphic_oarchive& ar, const unsigned int file_version) { std::string iso =3D to_iso_string(); ar & boost::serialization::make_nvp("iso_time", iso); } ---snip--- Am I missing something obvious? Are certain types not directly supported for serialization via polymorphic archives? Any help would be much appreciated. -- Cheers =8-} Mike Friede, Völkerverständigung und überhaupt blabla --=-=-= g++ -g -Wall -I /afs/informatik.uni-tuebingen.de/i386_fbsd54/boost-1.33.1/include/boost-1_33_1 -c -o mtime.o mtime.cpp /afs/informatik.uni-tuebingen.de/i386_fbsd54/boost-1.33.1/include/boost-1_33_1/boost/archive/detail/iserializer.hpp: In constructor `boost::archive::detail::iserializer<Archive, T>::iserializer() [with Archive = boost::archive::polymorphic_iarchive, T = std::basic_string<char, std::char_traits<char>, std::allocator<char> >]': /afs/informatik.uni-tuebingen.de/i386_fbsd54/boost-1.33.1/include/boost-1_33_1/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::polymorphic_iarchive, T = std::basic_string<char, std::char_traits<char>, std::allocator<char> >]' /afs/informatik.uni-tuebingen.de/i386_fbsd54/boost-1.33.1/include/boost-1_33_1/boost/archive/detail/iserializer.hpp:375: instantiated from `static void boost::archive::detail::load_non_pointer_type<Archive, T>::load_standard::invoke(Archive&, T&) [with Archive = boost::archive::polymorphic_iarchive, T = std::basic_string<char, std::char_traits<char>, std::allocator<char> >]' /afs/informatik.uni-tuebingen.de/i386_fbsd54/boost-1.33.1/include/boost-1_33_1/boost/archive/detail/iserializer.hpp:425: instantiated from `static void boost::archive::detail::load_non_pointer_type<Archive, T>::invoke(Archive&, T&) [with Archive = boost::archive::polymorphic_iarchive, T = std::basic_string<char, std::char_traits<char>, std::allocator<char> >]' /afs/informatik.uni-tuebingen.de/i386_fbsd54/boost-1.33.1/include/boost-1_33_1/boost/archive/detail/iserializer.hpp:572: instantiated from `void boost::archive::load(Archive&, T&) [with Archive = boost::archive::polymorphic_iarchive, T = std::basic_string<char, std::char_traits<char>, std::allocator<char> >]' /afs/informatik.uni-tuebingen.de/i386_fbsd54/boost-1.33.1/include/boost-1_33_1/boost/archive/polymorphic_iarchive.hpp:127: instantiated from `void boost::archive::polymorphic_iarchive::load_override(const boost::serialization::nvp<T>&, int) [with T = std::string]' /afs/informatik.uni-tuebingen.de/i386_fbsd54/boost-1.33.1/include/boost-1_33_1/boost/archive/detail/interface_iarchive.hpp:76: instantiated from `Archive& boost::archive::detail::interface_iarchive<Archive>::operator>>(T&) [with T = const boost::serialization::nvp<std::string>, Archive = boost::archive::polymorphic_iarchive]' /afs/informatik.uni-tuebingen.de/i386_fbsd54/boost-1.33.1/include/boost-1_33_1/boost/archive/detail/interface_iarchive.hpp:83: instantiated from `Archive& boost::archive::detail::interface_iarchive<Archive>::operator&(T&) [with T = const boost::serialization::nvp<std::string>, Archive = boost::archive::polymorphic_iarchive]' mtime.cpp:36: instantiated from here /afs/informatik.uni-tuebingen.de/i386_fbsd54/boost-1.33.1/include/boost-1_33_1/boost/archive/detail/iserializer.hpp:115: error: incomplete type `boost::serialization::extended_type_info_null<std::basic_string<char, std::char_traits<char>, std::allocator<char> > >' used in nested name specifier /afs/informatik.uni-tuebingen.de/i386_fbsd54/boost-1.33.1/include/boost-1_33_1/boost/archive/detail/oserializer.hpp: In constructor `boost::archive::detail::oserializer<Archive, T>::oserializer() [with Archive = boost::archive::polymorphic_oarchive, T = std::basic_string<char, std::char_traits<char>, std::allocator<char> >]': /afs/informatik.uni-tuebingen.de/i386_fbsd54/boost-1.33.1/include/boost-1_33_1/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::polymorphic_oarchive, T = std::basic_string<char, std::char_traits<char>, std::allocator<char> >]' /afs/informatik.uni-tuebingen.de/i386_fbsd54/boost-1.33.1/include/boost-1_33_1/boost/archive/detail/oserializer.hpp:264: instantiated from `static void boost::archive::detail::save_non_pointer_type<Archive, T>::save_standard::invoke(Archive&, const T&) [with Archive = boost::archive::polymorphic_oarchive, T = std::basic_string<char, std::char_traits<char>, std::allocator<char> >]' /afs/informatik.uni-tuebingen.de/i386_fbsd54/boost-1.33.1/include/boost-1_33_1/boost/archive/detail/oserializer.hpp:322: instantiated from `static void boost::archive::detail::save_non_pointer_type<Archive, T>::invoke(Archive&, const T&) [with Archive = boost::archive::polymorphic_oarchive, T = std::basic_string<char, std::char_traits<char>, std::allocator<char> >]' /afs/informatik.uni-tuebingen.de/i386_fbsd54/boost-1.33.1/include/boost-1_33_1/boost/archive/detail/oserializer.hpp:536: instantiated from `void boost::archive::save(Archive&, const T&) [with Archive = boost::archive::polymorphic_oarchive, T = std::basic_string<char, std::char_traits<char>, std::allocator<char> >]' /afs/informatik.uni-tuebingen.de/i386_fbsd54/boost-1.33.1/include/boost-1_33_1/boost/archive/polymorphic_oarchive.hpp:128: instantiated from `void boost::archive::polymorphic_oarchive::save_override(const boost::serialization::nvp<T>&, int) [with T = std::string]' /afs/informatik.uni-tuebingen.de/i386_fbsd54/boost-1.33.1/include/boost-1_33_1/boost/archive/detail/interface_oarchive.hpp:78: instantiated from `Archive& boost::archive::detail::interface_oarchive<Archive>::operator<<(T&) [with T = const boost::serialization::nvp<std::string>, Archive = boost::archive::polymorphic_oarchive]' /afs/informatik.uni-tuebingen.de/i386_fbsd54/boost-1.33.1/include/boost-1_33_1/boost/archive/detail/interface_oarchive.hpp:86: instantiated from `Archive& boost::archive::detail::interface_oarchive<Archive>::operator&(T&) [with T = const boost::serialization::nvp<std::string>, Archive = boost::archive::polymorphic_oarchive]' mtime.cpp:46: instantiated from here /afs/informatik.uni-tuebingen.de/i386_fbsd54/boost-1.33.1/include/boost-1_33_1/boost/archive/detail/oserializer.hpp:108: error: incomplete type `boost::serialization::extended_type_info_null<std::basic_string<char, std::char_traits<char>, std::allocator<char> > >' used in nested name specifier make: *** [mtime.o] Error 1 Compilation exited abnormally with code 2 at Wed Feb 22 11:56:36 --=-=-=--

4 3