- Boost-users - lists.boost.org

[Boost.Serialization] Memory management for references
by sadrok 18 Jan '07

18 Jan '07

Hi, I'm loading a class that requires a reference passed to the constructor. The implementation requires loading data into a pointer as explained in the docs. How is the memory for the loaded object handled? Does it automatically get freed when the object goes out of scope? Thanks -- sadrok(a)gmail.com Yahoo! IM: sadrok_za Jabber ID: sadrok(a)jabber.obsidian.co.za

2 1

Re: [Boost-users] [bjam] Building boost libraries for Win32 with alldebugging info
by Nat Goodspeed 18 Jan '07

18 Jan '07

________________________________________ From: boost-users-bounces(a)lists.boost.org [mailto:boost-users-bounces@lists.boost.org] On Behalf Of Lawrence Spector Sent: Thursday, January 18, 2007 11:44 AM To: boost-users(a)lists.boost.org Subject: [Boost-users] [bjam] Building boost libraries for Win32 with alldebugging info I had built the boost libraries a while ago, using bjam. It looks like all the boost debug libraries were built with Debug Information Format of "C7 Compatible (/Z7)" instead of "Program Database for Edit and Continue (/ZI)" and I'd like to rebuild the libraries with this option turned on. In addition, we're going to need "Treat wchar_t as a built-in type" turned off. It defaults to on. [Nat] We don't use bjam, so I'll let others address your real question. But do you intend to use the Serialization library? If so, beware of turning off 'wchar_t as built-in'.

2 1

[bjam] Building boost libraries for Win32 with all debugging info
by Lawrence Spector 18 Jan '07

18 Jan '07

I had built the boost libraries a while ago, using bjam. It looks like all the boost debug libraries were built with Debug Information Format of "C7 Compatible (/Z7)" instead of "Program Database for Edit and Continue (/ZI)" and I'd like to rebuild the libraries with this option turned on. In addition, we're going to need "Treat wchar_t as a built-in type" turned off. It defaults to on. Any help that can be given in setting the bjam to build correctly for our situation would be much appreciated. Thanks in advance, Lawrence

1 0

Using regex
by tintin 18 Jan '07

18 Jan '07

I've tried using the regex library in msvc, but keep getting unresolved external errors.. I have; #define BOOST_REGEX_NO_LIB #include <boost/regex.hpp> using namespace boost; Whenever I do a: regex e(".*test.*"); I keep getting a: 1>test.obj : error LNK2019: unresolved external symbol "private: class boost::basic_regex<char,struct boost::regex_traits<char,class boost::w32_regex_traits<char> > > & __thiscall boost::basic_regex<char,struct boost::regex_traits<char,class boost::w32_regex_traits<char> > >::do_assign(char const *,char const *,unsigned int)" (?do_assign@?$basic_regex@DU?$regex_traits@DV?$w32_regex_traits@D@boost@@@boost@@@boost@@AAEAAV12@PBD0I@Z) referenced in function "public: class boost::basic_regex<char,struct boost::regex_traits<char,class boost::w32_regex_traits<char> > > & __thiscall boost::basic_regex<char,struct boost::regex_traits<char,class boost::w32_regex_traits<char> > >::assign(char const *,char const *,unsigned int)" (?assign@?$basic_regex@DU?$regex_traits@DV?$w32_regex_traits@D@boost@@@boost@@@boost@@QAEAAV12@PBD0I@Z) Yeah I know it's long, but that's the msvc error ;) Any ideas why it won't work?

2 1

How can we serialize pointer of type base abstract class pointing to Derived concrete class
by Piyush Kapadia 18 Jan '07

18 Jan '07

We have a situation where there is BaseAbstract class and Derived concrete class. Interface requires that we pass BaseAbstractClassPointer, using which user can provide any of Derived Concrete class pointer and Interface remain generic to them. However serializing BaseAbstractPointer is throwing following error - *A unregistered class* How do we handle this situation ? #include <iostream> #include <fstream> #include <boost/archive/text_iarchive.hpp> #include <boost/archive/text_oarchive.hpp> #include <boost/archive/xml_iarchive.hpp> #include <boost/archive/xml_oarchive.hpp> #include <boost/archive/binary_iarchive.hpp> #include <boost/archive/binary_oarchive.hpp> #include <boost/serialization/vector.hpp> #include <boost/serialization/map.hpp> #include <vector> #include <map> #include <boost/archive/archive_exception.hpp> #include <boost/archive/basic_xml_archive.hpp> class BaseAbstract { public : virtual void setRate(double rate) = 0; virtual double getRate(int) = 0; }; class DerivedConcrete : public BaseAbstract { std::vector<double> rateVec; friend class boost::serialization::access; template<class Archive> void serialize(Archive & ar, const unsigned int version) { ar & BOOST_SERIALIZATION_NVP(rateVec); } public: DerivedConcrete(double rate) {rateVec.push_back(rate);} DerivedConcrete(){} virtual ~DerivedConcrete(){} void setRate(double rate){ rateVec.push_back(rate); }; double getRate(int idx){ return rateVec[idx]; }; }; class AnyClass { friend class boost::serialization::access; BaseAbstract* rate; template<class Archive> void serialize(Archive & ar, const unsigned int version) { ar & BOOST_SERIALIZATION_NVP(rate); } public: AnyClass(BaseAbstract* rateInput){ rate = rateInput; }; AnyClass() {}; setRate(BaseAbstract* rateInput){ rate = rateInput; }; }; int main(int argc, char* argv[]) { try { DerivedConcrete* fr = new DerivedConcrete(12.12); fr->setRate(14.5); AnyClass ac; ac.setRate(fr); std::ofstream ofs("AC.xml"); assert(ofs.good()); boost::archive::xml_oarchive oa(ofs); oa << BOOST_SERIALIZATION_NVP(ac); ofs.close(); } catch (boost::archive::xml_archive_exception ex) { std::cerr << " X " << ex.what() << std::endl; } catch (boost::archive::archive_exception ex) { std::cerr << " A " << ex.what() << std::endl; } catch (std::exception ex) { std::cerr << " E " << ex.what() << std::endl; } catch (...) { std::cerr << "Unknown Exception " << std::endl; } return 0; }

3 4

GNU Cross compiler problem under cygwin
by Norbert Unterberg 18 Jan '07

18 Jan '07

I have a cross compiler problem. We are running a cross compiler toolchain under Cygwin/Windows. This toolchain uses a cuistomized gcc compiler to generate code for a linux target. When trying to build boost using this cross compiler, bjam still detects that it is running on cygwin and windows, and tries to build DLLs instead of linux shared libraries. Is there any chance to configure bjam to run under windows or cygwin but generate code for a different target, either by special command line options or even by compiling a custom version of bjam? I have looked into jam some time ago but had to drop it because it was unable to differentiate between host and target configuration (like running under a windows host but generate code for Linux). Seem I am faling into the same trap again... Any help is appreciated! Norbert Unterberg

1 0

[Boost.dynamic_bitset bug]: operators <<= and >>= interchanged?
by Martin Moene 18 Jan '07

18 Jan '07

boost_1_33_1 Dear all, I suspect that the shift operator of the dynamic_bitset are reversed. Best regards, Martin Moene ___ C:\>dynamic_bitset.exe x :11111 x <<= 1:01111 x >>= 2:11100 /* * dynamic_bitset bug: operator <<= and >>= interchanged. * * cl -GX -ID:/Libraries/boost_1_33_1/ dynamic_bitset.cpp * cl -GX -IC:/Libraries/boost_1_33_1/ dynamic_bitset.cpp * cl -GX -I%BOOST% dynamic_bitset.cpp */ #include <iostream> #include <boost/dynamic_bitset.hpp> std::ostream& operator<<( std::ostream& os, boost::dynamic_bitset<> const& bs ) { for ( boost::dynamic_bitset<>::size_type i = 0; i < bs.size(); ++i ) { os << bs[i]; } return os; } int main( int, char*[] ) { boost::dynamic_bitset<> x(5); // all 0's by default x.set(); std::cout << "x :" << x << std::endl; std::cout << "x <<= 1:" << ( x <<= 1 ) << std::endl; std::cout << "x >>= 2:" << ( x >>= 2 ) << std::endl; return EXIT_FAILURE; }

3 2

[fusion] vector documentation
by Chris Weed 18 Jan '07

18 Jan '07

Hi, This example <http://spirit.sourceforge.net/dl_more/fusion_v2/libs/fusion/doc/html/fusion…> has the following include #include <boost/fusion/sequence/container/vector/vector_forward.hpp> which appears to now be vector/vector_fwd.hpp in CVS. Am I using outdated docs, outdated code, or is it not consistent? Thanks, Chris

2 1

Compiling boost 1.33.1, Visual Studio 2005 SP1, 64 bit Windows, AMD
by Leslie Brody (TT) 18 Jan '07

18 Jan '07

When compiling boost 1.33.1 with Visual Studio 2005 SP1 for 64 bit AMD on windows I get the following error. once.obj : error LNK2019: unresolved external symbol _InterlockedCompareExchange referenced in function "long __cdecl `anonymous namespace'::compare_exchange(long * volatile,long,long)" (?compare_exchange@?A0x74ecc88f@@YAJREAJJJ@Z) >From what I have seen this works in multiple other projects. This also works if I use that header in a new isolated project. I am assuming it is some compiler setting. But I am not sure which. Any thoughts are greatly appreciated Thank You -Leslie

2 1

using serialization
by 041021042＠fudan.edu.cn 18 Jan '07

18 Jan '07

Dear all, I have been experimenting with the boost serialization library. The working environment is Cygwin + gcc3.4.4 + boost_1_33. I creat the following program, the data structure is about electric circuits. The data is saved successfully, but the loadded data is wrong, some pointers in the Wire objects points to invalid address. While when I compile and run it in another machine (Linux + gcc4.1.1 + boost_1_33_1), it works properly. I wonder if it is a compiler compatibility problem or there is something wrong in my program. #ifndef CIRCUIT_H_ #define CIRCUIT_H_ #include <ostream> #include <string> #include <vector> #include <boost/archive/xml_iarchive.hpp> #include <boost/archive/xml_oarchive.hpp> #include <boost/serialization/base_object.hpp> #include <boost/serialization/vector.hpp> #include <boost/serialization/nvp.hpp> class Pin { std::string parent; int index; friend std::ostream& operator<< (std::ostream& os, const Pin& pin); friend class boost::serialization::access; template<class Archive> void serialize(Archive & ar, const unsigned int version) { ar & BOOST_SERIALIZATION_NVP(parent) & BOOST_SERIALIZATION_NVP (index); } public: Pin(std::string p="", int i=0) : parent(p), index(i) {} }; class Wire { Pin* source; Pin* sink; friend std::ostream& operator<< (std::ostream& os, const Wire& wire); friend class boost::serialization::access; template<class Archive> void serialize(Archive & ar, const unsigned int version) { ar & BOOST_SERIALIZATION_NVP(source) & BOOST_SERIALIZATION_NVP(sink); } public: Wire(Pin* src=0, Pin* snk=0) : source(src), sink(snk) {} }; class Block { protected: std::string name; std::vector<Pin*> pins; Block() {} virtual std::ostream& print(std::ostream& os) const; friend std::ostream& operator<< (std::ostream& os, const Block& blk); friend class boost::serialization::access; template<class Archive> void serialize(Archive & ar, const unsigned int version ) { ar & BOOST_SERIALIZATION_NVP(name) & BOOST_SERIALIZATION_NVP (pins); } public: Block(std::string n, int np) : name(n), pins(np) { for (int i=0; i<np; i++) pins[i] = new Pin(n, i); } virtual ~Block() { for (int i=0; i<pins.size(); i++) delete pins [i]; } Pin* get_pin(int i) { return pins[i]; } std::string get_name() { return name; } virtual std::ostream& print_recursive(std::ostream& os) const { return print(os); } }; class Circuit : public Block { protected: std::vector<Block*> children; std::vector<Wire*> wires; std::ostream& print(std::ostream& os) const; friend class boost::serialization::access; template<class Archive> void serialize(Archive & ar, const unsigned int version) { ar.register_type(static_cast<Circuit *>(NULL)); ar & BOOST_SERIALIZATION_BASE_OBJECT_NVP(Block); ar & BOOST_SERIALIZATION_NVP(children) & BOOST_SERIALIZATION_NVP(wires); } public: Circuit() : Block() {} Circuit(std::string name, int np) : Block(name, np) { } void add_block(Block& b) { children.push_back(&b); } void add_wire(Wire& w) { wires.push_back(&w); } std::ostream& print_recursive(std::ostream& os) const; }; std::ostream& operator<< (std::ostream& os, const Pin& pin); std::ostream& operator<< (std::ostream& os, const Wire& wire); std::ostream& operator<< (std::ostream& os, const Block& blk); #endif /*CIRCUIT_H_*/ // main.cpp #include <iostream> #include <fstream> #include "circuit.h" void save_circuit(const Circuit& c, const char * filename) { std::ofstream ofs(filename); boost::archive::xml_oarchive oa(ofs); oa << BOOST_SERIALIZATION_NVP(c); } void load_circuit(Circuit& c, const char * filename) { std::ifstream ifs(filename); boost::archive::xml_iarchive ia(ifs); ia >> BOOST_SERIALIZATION_NVP(c); } int main() { Circuit pe1("pe1",5); Circuit top("top", 4); top.add_block(pe1); Wire w6(top.get_pin(0), pe1.get_pin(0)); Wire w7(top.get_pin(1), pe1.get_pin(1)); Wire w8(pe1.get_pin(4), top.get_pin(2)); top.add_wire(w6); top.add_wire(w7); top.add_wire(w8); top.print_recursive(std::cout); save_circuit(top, "circuit.xml"); Circuit top2; load_circuit(top2, "circuit.xml"); top2.print_recursive(std::cout); } There is another problem, when I inlined the 'save' and 'load' function, the following error occured, and the data couldn't be saved. terminate called after throwing an instance of 'boost::archive::xml_archive_exception' what(): unrecognized XML syntax Aborted The program is listed here: int main() { // ... ... // prepare data std::ofstream ofs("circuit.xml"); boost::archive::xml_oarchive oa(ofs); oa << BOOST_SERIALIZATION_NVP(top); Circuit top2; std::ifstream ifs("circuit.xml"); boost::archive::xml_iarchive ia(ifs); ia >> BOOST_SERIALIZATION_NVP(top2); top2.print_recursive(std::cout); } The error occured on both machine. Could anyone explain what's the difference between the two programs. Best regards, Roger Zhou

1 0