- Boost-users - lists.boost.org

serialization: again a problem, failing to serialize a std::vector of pointers
by RIVASSEAU Jean Noel 02 Mar '06

02 Mar '06

Hello This is my last problem with the BSL but the most important one (because there is no workaround). I am trying to serialize a class (whose name is "ClassSpecification") which has a std::vector of pointers. The code for serializing the class the pointer refer to (MemberVariableSpecification) is written and instantiated correctly. However I cannot correctly serialize the std::vector. It fails with a message complaining about: C:/Boost/include/boost-1_33_1/boost/archive/detail/iserializer.hpp:115: error: incomplete type `boost::serialization::extended_type_info_null<std::vector<MemberVariableSpecification*, std::allocator<MemberVariableSpecification*> > >' used in nested name specifier I do not understand why I need an extended_type_info for this vector. I sure need it for the class the pointers refer to (and I did specify it), but the std::vector itself is serialized as such, not as a pointer. Why do I get this error ??? Can you please check the attached code and help me? Thanks Jean-Noël Ps: using gcc 3.4.2

2 2

[serialization] non-intrusive serialization problem
by Federico Feller 02 Mar '06

02 Mar '06

Hi. I have problems defining a non-instrusive serialization of a class. Ive defined the following functions: namespace boost { namespace serialization { template<class Archive> inline void save( Archive & ar, const CLITimeStamp & t, const unsigned int /* file_version */ ){ std::string aux = std::string(t.get14LengthRepresentation()); ar & aux; } template<class Archive> inline void load( Archive & ar, const CLITimeStamp & t, const unsigned int /* file_version */ ){ std::string aux; ar & aux; t = CLITimeStamp((char*)aux.c_str()); } template<class Archive> inline void serialize( Archive & ar, const CLITimeStamp & t, const unsigned int file_version ){ split_free(ar, t, file_version); } }} According to the doc Ive read, this is the way to declare that the class 'CLITimeStamp' can be serialized. Howerver, when I try to do this: template<class Archive> void load(Archive & ar, const unsigned int version){ ar & minDate }; where minDate is a CLITimeStamp pointer, i get the follwing error: <'serialize' is not a Member of CLITimeStamp> Any ideas of what i could be doing wrong? Thanks Federico __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

2 1

Boost can't build with Intel C++ Compiler 9.0
by Yoshihiro ISHIKAWA 02 Mar '06

02 Mar '06

Hello everyone I could not build all boost-1.33.1 libraries using Intel C++ Compiler 9.0.0.32. I tried following steps. # export INTEL_PATH=/opt/intel/cc/9.0 # export INTEL_CXX="icpc -cxxlib-icc" # ./configure --with-toolset=intel-linux # make My environment Fedora Core 4 i386 Intel C++ Compiler version 9.0.0.32 Boost version 1.33.1 How can I build all libraries ? Please Help. Yoshihiro Ishikawa

2 1

newbie question
by Lucio Flores 02 Mar '06

02 Mar '06

Just trying to use mpl::transform on a vector of int's and I can't seem to get it working properly. Can anyone see what's wrong?? I'm trying to perform vector_c<int, 1, 2, 3> + vector_c<int, 1, 1, 1> = vector_c<int, 2, 3 ,4> The is_same function always returns false when I compile and run it. ------------------- typedef mpl::vector_c<int, 1, 2, 3> type_a; typedef mpl::vector_c<int, 1, 1, 1> type_b; struct plus_f { template<class A, class B> struct apply { typedef typename mpl::plus<A, B>::type type; }; }; typedef mpl::transform<type_a, type_b, plus_f >::type result_type; std::cerr << "True " << boost::is_same<result_type, mpl::vector_c<int, 2, 3, 4> >::value << std::endl; __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

13 55

Re: [Boost-users] Boost can't build with Intel C++ Compiler 9.0
by Ormond, Randy (Mission Systems) 02 Mar '06

02 Mar '06

I'm in the middle of building on an Altix (Itanium, Linux) with Intel 9.0 also. Still checking but this looks like it's working for me: bjam -sTOOLS=intel-linux "-sINTEL_CC=icc -cxxlib-icc" -sINTEL_PATH=/opt/intel/cc/9.0 But I guess you have a reason for not wanting to use bjam. Hope this helps. Randy Ormond -----Original Message----- From: boost-users-bounces(a)lists.boost.org [mailto:boost-users-bounces@lists.boost.org] On Behalf Of Yoshihiro ISHIKAWA Sent: Thursday, March 02, 2006 5:56 AM To: boost-users(a)lists.boost.org Subject: [Boost-users] Boost can't build with Intel C++ Compiler 9.0 Hello everyone I could not build all boost-1.33.1 libraries using Intel C++ Compiler 9.0.0.32. I tried following steps. # export INTEL_PATH=/opt/intel/cc/9.0 # export INTEL_CXX="icpc -cxxlib-icc" # ./configure --with-toolset=intel-linux # make My environment Fedora Core 4 i386 Intel C++ Compiler version 9.0.0.32 Boost version 1.33.1 How can I build all libraries ? Please Help. Yoshihiro Ishikawa _______________________________________________ Boost-users mailing list Boost-users(a)lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users

1 0

Re: [Boost-users] Using multiple versions/targets of Boost
by Staal, J.J. (Joes) 02 Mar '06

02 Mar '06

> > It should... Did you use "-sTOOLS=vc-8_0" both times? As that's what > > it uses to determine the "vc80" tag. I had a similar problem, until I found out that I made an error. I used -"sTOOLS=vc-8_0" instead of "-sTOOLS=vc-8_0" (notice the location of the first minus sign). Joes. This e-mail and its contents are subject to the DISCLAIMER at http://www.tno.nl/disclaimer/email.html

2 1

Using multiple versions/targets of Boost
by Mateusz Łoskot 02 Mar '06

02 Mar '06

Hi, I have VC++ 7.1 and VC++ 8.0 installed on my laptop. I'd like to use Boost with both VC++. So, as I understand I need to build Boost twice, with VC++ 7.1 and with VC++ 8.0. Documentation does not say anything about such case. Now, the question is, should I install both targets to separate directories (different --prefix, e.g. C:\Boost-vc-8.0 and C:\Boost-vc-7.1) or can I install then in common dir C:\Boost ? AFAIK, libs names include toolset name e.g. libboost_date_time-vc71-mt-gdp.lib ^^^^^ So, I suppose I can install both targets into common place and I'll have following files in C:\Boost\lib: libboost_date_time-vc71-mt-gdp.lib and libboost_date_time-vc80-mt-gdp.lib Are my assumptions correct? Or it's more recommended to install separate targets (builds made with different toolsets) to separate folders? Thanks in advance Best regards -- Mateusz Łoskot http://mateusz.loskot.net

4 6

Re: [Boost-users] Serialization: docs regarding abstract base class
by RIVASSEAU Jean Noel 02 Mar '06

02 Mar '06

Since the demo doesn't use BOOST_EXPORT, I suspect that that there is some sort of problem related to instantiation of abstract base class code for exported types. I'lll look into it. If you can look into it, thank you, Robert. I have finished the organization of my (big) project serialization into separate files for each class, and now everything is working fine ! :) However, I still have the problem that every time I use a std::vector of pointers, and serialize it as such, there is a compile time error, since extended_type_info for the std::vector is not defined. This is a bug since type info should not matter here. My workaround was to use a BOOST_CLASS_TYPE_INFO(std::vector< ClassPointedTo *>, extended_type_info_no_rtti< std::vector< ClassPointedTo *> >) everytime such a vector occurs. However, if you can look into this problem and fix it, Robert, this would appreciated. I could then remove my workaround code, which makes my code ugly :) Jean-Noël -----Message d'origine----- De : boost-users-bounces(a)lists.boost.org [mailto:boost-users-bounces@lists.boost.org] De la part de Robert Ramey Envoyé : jeudi 2 mars 2006 03:49 À : boost-users(a)lists.boost.org Objet : Re: [Boost-users] Serialization: docs regarding abstract base class Note that the tutorial programs do use BOOST_IS_ABSTRACT so I've always assumed that it functions as advertised. Since the demo doesn't use BOOST_EXPORT, I suspect that that there is some sort of problem related to instantiation of abstract base class code for exported types. I'lll look into it. Robert Ramey "RIVASSEAU Jean Noel" <JN.RIVASSEAU(a)oberthurcs.com> wrote in message news:87F60F7FA02FF749AFB02BD9FCAA6B04DE1BE3@naserv31.nanterre.oberthurcs.com... I quote the Boost serialization docs: When serializing an object through a pointer to its base class and that base class is abstract (i.e. has at least one virtual function assigned a value of 0), A compile error will be emitted. This is addressable in one over several ways: remove the =0 in the base classes so that the base class is no longer abstract. implement is_abstract for your compiler. (code written according to the C++ standard is included with this library. But it is known to fail on several compilers. If the compiler suports "is_abstract" type trait - use that. Otherwise assume a class is NOT abstract unless BOOST_IS_ABSTRACT has been set for the class. use the macro BOOST_IS_ABSTRACT(my_class) to indicate that the class is an abstract base class. This will cause the compiler to avoid generating code that causes this error. I still do not understand part 2 of this advice, Robert. Could you explain? Jean-Noël Ps: as already mentioned, part 3 does not change anything for me, and I'd like to avoid the solution of part 1 since I do want the base class to be abstract. _______________________________________________ Boost-users mailing list Boost-users(a)lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users

1 0

Can't statically link demo program with Boost.Serialization 1.33
by Demos Rali 02 Mar '06

02 Mar '06

Hello, I am having difficulties statically compiling the demo program at http://www.boost.org/libs/serialization/example/demo.cpp on Linux (Linux 2.6.15-1.1831_FC4 #1 SMP Tue Feb 7 13:37:59 EST 2006 x86_64 GNU/Linux) with gcc version 4.0.2 20051125. When I try: g++ -o demo -I /path/boost/ -L /path/boost/ -lboost_serialization demo.cpp it works fine, but I get a program which needs dynamic versions of the serialization library. However, I would like to compile against the static versions of the Boost.Serialization library. If I try g++ -static -o demo -I /path/boost/ -L /path/boost/ -lboost_serialization demo.cpp the linker complains of a lot of undefined references, like /tmp/ccFAJsqB.o(.gnu.linkonce.r._ZTIN5boost13serialization16void_cast_detail21void_caster_primitiveIK20bus_stop_destinationK8bus_stopEE[typeinfo for boost::serialization::void_cast_detail::void_caster_primitive<bus_stop_destination const, bus_stop const>]+0x10): undefined reference to `typeinfo for boost::serialization::void_cast_detail::void_caster' ... I have no difficulties when statically linking against other boost libraries. I built the librairies with gcc, with no exotic options. Any suggestions would be greatly appreciated. Thanks a lot. Fabrizio

2 1

Serialization: docs regarding abstract base class
by RIVASSEAU Jean Noel 02 Mar '06

02 Mar '06

I quote the Boost serialization docs: When serializing an object through a pointer to its base class and that base class is abstract (i.e. has at least one virtual function assigned a value of 0), A compile error will be emitted. This is addressable in one over several ways: * remove the =0 in the base classes so that the base class is no longer abstract. * implement is_abstract for your compiler. (code written according to the C++ standard is included with this library. But it is known to fail on several compilers. * use the macro BOOST_IS_ABSTRACT(my_class) to indicate that the class is an abstract base class. This will cause the compiler to avoid generating code that causes this error. I still do not understand part 2 of this advice, Robert. Could you explain? Jean-Noël Ps: as already mentioned, part 3 does not change anything for me, and I'd like to avoid the solution of part 1 since I do want the base class to be abstract.

3 2