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

Re: [Boost-users] Using BOOST_STRING_TRIM_HPP to check whethertrim_copy() is available?
by Sohail Somani 30 Mar '06

30 Mar '06

> Hi, > > I've got a header that I'd like to use in both application that use > Boost and in ones that don't. > Is there a define I can use to check whether Boost is available? > In particular, I wish to use boost::trim_copy, but I don't want to > force all files that include my header to use Boost. I'm guessing BOOST_VERSION should be enough. I think all non-trivial boost headers end up including this, but I'm not 100%.

1 0

Using BOOST_STRING_TRIM_HPP to check whether trim_copy() is available?
by Olaf van der Spek 30 Mar '06

30 Mar '06

Hi, I've got a header that I'd like to use in both application that use Boost and in ones that don't. Is there a define I can use to check whether Boost is available? In particular, I wish to use boost::trim_copy, but I don't want to force all files that include my header to use Boost. Olaf

1 0

Re: [Boost-users] Serialization library question
by wayne.x.liu＠jpmchase.com 30 Mar '06

30 Mar '06

Well, I guess I'll work around it for gcc by using register_type(). Wayne ------------------------------ Message: 6 Date: Wed, 29 Mar 2006 20:39:57 -0800 From: "Robert Ramey" <ramey(a)rrsd.com> Subject: Re: [Boost-users] Serialization library question To: boost-users(a)lists.boost.org Message-ID: <e0fnef$aus$1(a)sea.gmane.org> I compiled, linked and executed this exact program on my VC 7.1 setup. I had no problems of any kind Robert Ramey

1 0

[type_traits][regex] VC++ __fastcall /clr
by Edward Diener 30 Mar '06

30 Mar '06

When compiling managed code in VC++ .NET, which is any of the /clr compiler options, the programmer can mix both CLR classes and regular C++ classes. In the regular C++ classes, Boost should work fine. The VC++ macro which tells one that managed code of any kind is being compiled is _MANAGED, which is defined if managed code is being compiled else it is not defined. So when any of the /clr compiler options are being used _MANAGED is defined, else it is not defined. The VC++ compiler issues compiler warning C4561 whenever managed code is being compiled and __fastcall shows up as a calling convention in any way. Obviously the programmer can turn off this warning via a VC++ #pragma, but I am wondering if Boost could not change some of its headers to avoid this warning. In Boost bind and mem_fn, the programmer has to specifically ask for __fastcall support via special Boost macros to have any functions declared with the __fastcall calling convention, so nothing should be done there since it is clearly a programming error if he does so while compiling managed code. However there are two other places in Boost which I have discovered where functions with the __fastcall calling convention are declared without the programmer doing anything. The first, and most cumbersome reagrding warning messages, is in type_traits in the helper header files type_traits\detail\is_mem_fun_pointer_tester.hpp and type_traits\detail\is_function_pointer_tester.hpp. Since many other libraries, lambda in my case recently, uses type_traits, might not these headers be changed so that when VC++ is the compiler and _MANAGED is defined, the __fastcall versions of these helper functions are not declared ? The second, which I have not encountered but which I saw while searching through Boost header code, is in regex\config.h and I do not know, given some other macros there, whether BOOST_REGEX_CALL can ever be __fastcall when compiling with /clr, but if it can perhaps a change can be made there also. I know that it is not the purpose of Boost to try to accomodate C++ .NET programmers creating /clr compilations using Boost, especially when just warnings and not errors are issued. But in this case, using the predefined macro _MANAGED in VC++ and BOOST_MSVC, it would seem this acoomodation could be made. So I would like the Boost developers of type_traits, especially since it is used by so many other Boost libraries, and regex to consider it.

2 1

boost program options cannot accept hex number
by Peng Yu 30 Mar '06

30 Mar '06

I tried to supply a hex number to an unsigned long integer. But it fails. ("code", po::value<unsigned long>(), "Via pattern code") Error message: in option 'code': invalid option value '0x5A' Could you please let me if it is possible to input a hex form integer in the command line? Thanks, Peng

2 1

Problems compiling Serialisation libs because of Spirit problem
by James Hughes 30 Mar '06

30 Mar '06

Hello all, I reported some time ago an issue with trying to compile the Boost libs using an ARM cross compiler. This has just started to have an impact as I wish to try out the Serialisation libs, and these are one of the areas with a compile issue. The following error is repeated over a considerable number of files and seems to indicate a problem with Spirit. I am using the latest release version of Boost (1.33.1)- no patches (are there any?) and a gcc v3.4.3 cross compiler to ARM architecture. Does anyone have any suggestions? I have had no luck figuring it out, but to be honest haven't spent a lot of time on it yet. Rgds James >>>>> gcc-C++-action bin/boost/libs/serialization/build/libboost_serialization.a/gcc/debug/xml_gr ammar.o 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_grammar.cpp:6 3: /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' set -e "/opt/montavista/mobilinux/devkit/arm/iwmmxt_le/bin/iwmmxt_le-g++" -D_REENTRANT -c -Wall -ftemplate-depth-255 -DBOOST_LIB_DIAGNOSTIC=1 -g -O0 -fno-inline -Wno-non-virtual-dtor -Wno-ctor-dtor-privacy -I"bin/boost/libs/serialization/build" -I "/home/jhughes/boost_1_33_1" -o "bin/boost/libs/serialization/build/libboost_serialization.a/gcc/debug/xml_g rammar.o" "/home/jhughes/boost_1_33_1/libs/serialization/build/../src/xml_grammar.cpp" "/opt/montavista/mobilinux/devkit/arm/iwmmxt_le/bin/iwmmxt_le-objcopy" --set-section-flags .debug_str=contents,debug "bin/boost/libs/serialization/build/libboost_serialization.a/gcc/debug/xml_g rammar.o" ...failed gcc-C++-action bin/boost/libs/serialization/build/libboost_serialization.a/gcc/debug/xml_gr ammar.o... <<<<<

1 0

Building boost libraries for x64 platform
by Sergei N. Malyutin 30 Mar '06

30 Mar '06

Hi, I need to use boost libraries under amd64 platform. At the build time of the library boost_thread I've got an error message from the linker that it failed to find an external symbol _InterlockedCompareExchange (this call is used in the source once.cpp). I really have not found this export among system libraries functions. Does this mean that currently the boost cannot be used in this environment? I did not see any limitations on the boost use under x64. May be I missed anything? Any help or links to the required information would be appreciated. Sergei Malyutin _______________________________________________ Boost-users mailing list Boost-users(a)lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users

2 2

[serialization] XML archive limitations?
by Delfin Rojas 30 Mar '06

30 Mar '06

Hello, I would like to know if it is possible to use the serialization lib and the XML archive to serialize into XML attributes instead of XML elements. For example I want to be able to generate something like: <song id="5" title="foo"/> I would also like to know if the order of XML elements is strict. Meaning, if I have the XML: <song> <id>5</id> <name>foo</name> </song> Can I ask the library to de-serialize "name" and then "id"? What if the xml contains extra XML elements that I don't care to de-serialize? Will I get an error processing the archive? If these things are not supported right now, what would it take to support it? New xml archive? Thanks a lot, Delfin Rojas

3 2

Re: [Boost-users] Serialization library question
by wayne.x.liu＠jpmchase.com 30 Mar '06

30 Mar '06

Thanks for the help. The new code works. For my application, I would like to use BOOST_CLASS_EXPORT_GUID to simplify the registration process. Changing the demo code to use EXPORT causes it to core dump. Perhaps I'm not using correctly... Again, help would be appreciated. Wayne Liu #0 0x004a2575 in boost::archive::detail::basic_iarchive_impl::load_preamble () from /cbb/public/wayne/build/lib/libboost_serialization-gcc-1_33_1.so.1.33.1 #1 0x004a30b9 in boost::archive::detail::basic_iarchive_impl::load_pointer () from /cbb/public/wayne/build/lib/libboost_serialization-gcc-1_33_1.so.1.33.1 #2 0x004a2934 in boost::archive::detail::basic_iarchive::load_pointer () from /cbb/public/wayne/build/lib/libboost_serialization-gcc-1_33_1.so.1.33.1 #3 0x0804d989 in boost::archive::detail::load_pointer_type<boost::archive::text_iarchive, bus_stop*>::invoke (ar=@0xbfff7fd0, t=@0xbfff800c) at /cbb/public/wayne/build/include/boost-1_33_1/boost/archive/detail/iserializer.hpp:486 #4 0x0804d8f6 in load<boost::archive::text_iarchive, bus_stop*> (ar=@0xbfff7fd0, t=@0xbfff800c) at /cbb/public/wayne/build/include/boost-1_33_1/boost/archive/detail/iserializer.hpp:572 #5 0x0804d80b in boost::archive::basic_text_iarchive<boost::archive::text_iarchive>::load_override<bus_stop*> (this=0xbfff7fd0, t=@0xbfff800c) at /cbb/public/wayne/build/include/boost-1_33_1/boost/archive/basic_text_iarchive.hpp:64 #6 0x0804d718 in boost::archive::text_iarchive_impl<boost::archive::text_iarchive>::load_override<bus_stop*> (this=0xbfff7fd0, t=@0xbfff800c) at /cbb/public/wayne/build/include/boost-1_33_1/boost/archive/text_iarchive.hpp:64 #7 0x0804d65d in operator>><bus_stop*> (this=0xbfff7fd0, t=@0xbfff800c) at /cbb/public/wayne/build/include/boost-1_33_1/boost/archive/detail/interface_iarchive.hpp:76 #8 0x0804c807 in restore (ss=@0xbfff8070) at test/d3.cpp:138 #9 0x0804cf69 in main (argc=1, argv=0xbfff8274) at test/d3.cpp:180 /////////1/////////2/////////3/////////4/////////5/////////6/////////7/////////8 // demo.cpp // // (C) Copyright 2002-4 Robert Ramey - http://www.rrsd.com . // Use, modification and distribution is subject to 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 <iomanip> #include <iostream> #include <sstream> #include <string> #include <boost/archive/text_iarchive.hpp> #include <boost/archive/text_oarchive.hpp> #include <boost/serialization/access.hpp> #include <boost/serialization/base_object.hpp> #include <boost/serialization/utility.hpp> #include <boost/serialization/export.hpp> ///////////////////////////////////////////////////////////// // One bus stop // // illustrates serialization of serializable members // class bus_stop { friend class boost::serialization::access; friend std::ostream & operator<<(std::ostream &os, const bus_stop &gp); virtual std::string description() const = 0; int latitude; int longitude; template<class Archive> void serialize(Archive &ar, const unsigned int version) { ar & latitude; ar & longitude; } protected: bus_stop(const int & _lat, const int & _long) : latitude(_lat), longitude(_long) {} public: bus_stop(){} virtual ~bus_stop(){} }; BOOST_IS_ABSTRACT(bus_stop) BOOST_CLASS_EXPORT_GUID(bus_stop, "bus_stop") std::ostream & operator<<(std::ostream &os, const bus_stop &bs) { return os << bs.latitude << bs.longitude << ' ' << bs.description(); } ///////////////////////////////////////////////////////////// // Several kinds of bus stops // // illustrates serialization of derived types // class bus_stop_corner : public bus_stop { friend class boost::serialization::access; std::string street1; std::string street2; virtual std::string description() const { return street1 + " and " + street2; } template<class Archive> void serialize(Archive &ar, const unsigned int version) { // save/load base class information ar & boost::serialization::base_object<bus_stop>(*this); ar & street1 & street2; } public: bus_stop_corner(){} bus_stop_corner(const int & _lat, const int & _long, const std::string & _s1, const std::string & _s2 ) : bus_stop(_lat, _long), street1(_s1), street2(_s2) { } }; BOOST_CLASS_EXPORT_GUID(bus_stop_corner, "bus_stop_corner") class bus_stop_destination : public bus_stop { friend class boost::serialization::access; std::string name; virtual std::string description() const { return name; } template<class Archive> void serialize(Archive &ar, const unsigned int version) { ar & boost::serialization::base_object<bus_stop>(*this) & name; } public: bus_stop_destination(){} bus_stop_destination( const int & _lat, const int & _long, const std::string & _name ) : bus_stop(_lat, _long), name(_name) { } }; BOOST_CLASS_EXPORT_GUID(bus_stop_destination, "bus_stop_destination") void save(const bus_stop * const s, std::stringstream &ss) /* NOTE extra const here !! */ { std::cout << "original"; std::cout << *s; boost::archive::text_oarchive oa(ss); //oa.register_type(static_cast<bus_stop_corner *>(NULL)); //oa.register_type(static_cast<bus_stop_destination *>(NULL)); oa << s; } void restore( std::stringstream &ss) { bus_stop *s; boost::archive::text_iarchive ia(ss); //ia.register_type(static_cast<bus_stop_corner *>(NULL)); //ia.register_type(static_cast<bus_stop_destination *>(NULL)); ia >> s; std::cout << "restored"; std::cout << *s; } int main(int argc, char *argv[]) { // fill in the data // make a few stops bus_stop *bs0 = new bus_stop_corner( 34, 134, "24th Street", "10th Avenue" ); bus_stop *bs1 = new bus_stop_corner( 35, 133, "State street", "Cathedral Vista Lane" ); bus_stop *bs2 = new bus_stop_destination( 35, 133, "White House" ); bus_stop *bs3 = new bus_stop_destination( 35, 133, "Lincoln Memorial" ); { std::stringstream ss; // display the complete schedule save(bs0,ss); restore(ss); } { std::stringstream ss; // display the complete schedule save(bs1,ss); restore(ss); } { std::stringstream ss; // display the complete schedule save(bs2,ss); restore(ss); } { std::stringstream ss; // display the complete schedule save(bs3,ss); restore(ss); } return 0; }

2 2

Re: [Boost-users] Dynamically creating classed by name?
by Wu Yinghui, Freddie 30 Mar '06

30 Mar '06

> Note that a component of the serialization library "extended_type_info" addresses > this issue (as it must) in order to de-serialize pointers. You might look in > the serialization documentation. > > Robert Ramey Frankly speaking, I've been researching on this topic as well. Most of the current libraries (e.g. Reflex) uses external programs/scripts to general the "stub" program for reflection support. This is not acceptable for our current environment. Boost.Serialization was a very good candidate, though a little bit difficult to use--It provides the necessary support all under the hood of C++ and C++ alone. Nonetheless, though I've inspected "extended_type_info" reference in the manual a number of times, I'm sorry that I cannot see how to achieve what Rob Caldecott wanted using it. Maybe you can shed some light on this? TIA! Cheers, Freddie > Rob Caldecott wrote: > > Is there any way that, using Boost, you can dynamically create > > classes by name, similar to the MFC RUNTIME_CLASS macros? I was > > hoping that the boost::serialize libs might be able to help with this. > > > > For example, I want to be able to do something like: > > > > CMyClass* pClass = CREATE_CLASS_BY_NAME("CMyClass"); > > > > Can Boost help me to achieve this? -- Wu Yinghui, Freddie Research & Development Software Engineer Volume Interactions Pte Ltd 1 Kim Seng Promenade, #12-01 Great World City East Tower Singapore 237994 Tel: +65 62226962 (Ext 216) Fax: +65 62226215 Email: yhwu(a)volumeinteractions.com URL: http://www.volumeinteractions.com Important: This message is intended for the recipient(s) addressed above. It contains privileged and confidential information. If you are not the intended recipient, please notify the sender immediately by replying to this message and then delete it from your system. You must not read, copy, use, or disseminate this communication in any form. Thank you.

2 1