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

Re: [Boost-users] serialization: loading std::map replaces existingmapdata objects
by Peter Whaite 13 Jan '06

13 Jan '06

Robert Ramey <ramey(a)rrsd.com> wrote: > Oh then maybe you want: > void serialize(boost::archive::xml_iarchive & ar, std::map<my_class> > & t, > const > unsigned int version){ > // for each member in the map > ar & *it; > } Ah, I was looking for that but missed it. I'm having trouble compiling the load though as gcc doesnt like the map member's std::pair.first being const. I'm sure I'm doing something incorrect that's blindingly obvious, but I just can't see it. The code and compiler messages are below. #include <map> #include <fstream> #include <boost/archive/xml_wiarchive.hpp> #include <boost/serialization/utility.hpp> // For std::pair typedef boost::archive::xml_wiarchive iarchive; typedef std::wifstream ifstream; struct Mark {}; enum MarkId {low,median,high}; typedef std::map<MarkId,Mark> MarkMap; void serialize(iarchive &ar, MarkMap & m, const unsigned int version) { MarkMap::iterator it; for (it = m.begin() ; it != m.end(); ++it) { ar & boost::serialization::make_nvp("item", *it); } } int main(int argc, char* argv[]) { ifstream ifs; iarchive ar(ifs); MarkMap marks; ar >> boost::serialization::make_nvp("marks",marks); } gcc --version gcc (GCC) 3.2.2 20030222 (Red Hat Linux 3.2.2-5) g++ -c tsrz.cpp -I/usr/local/include -isystem /usr/local/include/boost-1_33 -isystem ./boost -g -Wall -Wno-non-virtual-dtor -Wno-inline -ftemplate-depth-255 -finline-functions -MMD -MF.deps/tsrz.d /usr/local/include/boost-1_33/boost/archive/detail/iserializer.hpp: In function `void boost::archive::load(Archive&, T&) [with Archive = boost::archive::xml_wiarchive, T = const MarkId]': /usr/local/include/boost-1_33/boost/archive/basic_xml_iarchive.hpp:80: instantiated from `void boost::archive::basic_xml_iarchive<Archive>::load_override(const boost::serialization::nvp<T>&, int) [with T = const MarkId, Archive = boost::archive::xml_wiarchive]' /usr/local/include/boost-1_33/boost/archive/xml_wiarchive.hpp:78: instantiated from `void boost::archive::xml_wiarchive_impl<Archive>::load_override(T&, int) [with T = const boost::serialization::nvp<const MarkId>, Archive = boost::archive::xml_wiarchive]' /usr/local/include/boost-1_33/boost/archive/detail/interface_iarchive.hpp:84: instantiated from `Archive& boost::archive::detail::interface_iarchive<Archive>::operator>>(T&) [with T = const boost::serialization::nvp<const MarkId>, Archive = boost::archive::xml_wiarchive]' /usr/local/include/boost-1_33/boost/archive/detail/interface_iarchive.hpp:91: instantiated from `Archive& boost::archive::detail::interface_iarchive<Archive>::operator&(T&) [with T = const boost::serialization::nvp<const MarkId>, Archive = boost::archive::xml_wiarchive]' /usr/local/include/boost-1_33/boost/serialization/utility.hpp:43: instantiated from `void boost::serialization::serialize(Archive&, std::pair<F, S>&, unsigned int) [with Archive = boost::archive::xml_wiarchive, F = const MarkId, S = Mark]' /usr/local/include/boost-1_33/boost/serialization/serialization.hpp:140: instantiated from `void boost::serialization::serialize_adl(Archive&, T&, unsigned int) [with Archive = boost::archive::xml_wiarchive, T = std::pair<const MarkId, Mark>]' /usr/local/include/boost-1_33/boost/archive/detail/iserializer.hpp:158: instantiated from `void boost::archive::detail::iserializer<Archive, T>::load_object_data(boost::archive::detail::basic_iarchive&, void*, unsigned int) const [with Archive = boost::archive::xml_wiarchive, T = std::pair<const MarkId, Mark>]' /usr/local/include/boost-1_33/boost/mpl/if.hpp:67: instantiated from here /usr/local/include/boost-1_33/boost/archive/detail/iserializer.hpp:544: `sizeof' applied to incomplete type `boost::STATIC_ASSERTION_FAILURE<false>' /usr/local/include/boost-1_33/boost/archive/detail/iserializer.hpp: In static member function `static void boost::archive::detail::load_enum_type<Archive, T>::invoke(Archive&, T&) [with Archive = boost::archive::xml_wiarchive, T = const MarkId]': /usr/local/include/boost-1_33/boost/archive/detail/iserializer.hpp:559: instantiated from `void boost::archive::load(Archive&, T&) [with Archive = boost::archive::xml_wiarchive, T = const MarkId]' /usr/local/include/boost-1_33/boost/archive/basic_xml_iarchive.hpp:80: instantiated from `void boost::archive::basic_xml_iarchive<Archive>::load_override(const boost::serialization::nvp<T>&, int) [with T = const MarkId, Archive = boost::archive::xml_wiarchive]' /usr/local/include/boost-1_33/boost/archive/xml_wiarchive.hpp:78: instantiated from `void boost::archive::xml_wiarchive_impl<Archive>::load_override(T&, int) [with T = const boost::serialization::nvp<const MarkId>, Archive = boost::archive::xml_wiarchive]' /usr/local/include/boost-1_33/boost/archive/detail/interface_iarchive.hpp:84: instantiated from `Archive& boost::archive::detail::interface_iarchive<Archive>::operator>>(T&) [with T = const boost::serialization::nvp<const MarkId>, Archive = boost::archive::xml_wiarchive]' /usr/local/include/boost-1_33/boost/archive/detail/interface_iarchive.hpp:91: instantiated from `Archive& boost::archive::detail::interface_iarchive<Archive>::operator&(T&) [with T = const boost::serialization::nvp<const MarkId>, Archive = boost::archive::xml_wiarchive]' /usr/local/include/boost-1_33/boost/serialization/utility.hpp:43: instantiated from `void boost::serialization::serialize(Archive&, std::pair<F, S>&, unsigned int) [with Archive = boost::archive::xml_wiarchive, F = const MarkId, S = Mark]' /usr/local/include/boost-1_33/boost/serialization/serialization.hpp:140: instantiated from `void boost::serialization::serialize_adl(Archive&, T&, unsigned int) [with Archive = boost::archive::xml_wiarchive, T = std::pair<const MarkId, Mark>]' /usr/local/include/boost-1_33/boost/archive/detail/iserializer.hpp:158: instantiated from `void boost::archive::detail::iserializer<Archive, T>::load_object_data(boost::archive::detail::basic_iarchive&, void*, unsigned int) const [with Archive = boost::archive::xml_wiarchive, T = std::pair<const MarkId, Mark>]' /usr/local/include/boost-1_33/boost/mpl/if.hpp:67: instantiated from here /usr/local/include/boost-1_33/boost/archive/detail/iserializer.hpp:491: assignment of read-only reference `t'

2 4

Understanding Boost.Mpl Fold Algorithm
by Eduardo Bezerra 10 Jan '06

10 Jan '06

Hi, I'm having a hard time trying to understand what the placeholders _1 and _2 mean in the context of the mpl::fold algorithm. >From the Boost.Mpl Reference manual: typedef vector<long,float,short,double,float,long,long double> types; typedef fold< types , int_<0> , if_< is_float<_2>,next<_1>,_1 > >::type number_of_floats; BOOST_MPL_ASSERT_RELATION( number_of_floats::value, ==, 4 ); Could someone give me some help on this ? Best regards, Eduardo

4 6

Mutually exclusive options in boost::program_options?
by Marshall Clow 09 Jan '06

09 Jan '06

I'm trying to use boost::program_options for the first time, and there's a couple things that I am tripping over. The first is the idea of mutually exclusive options. I can't find any support for them in the library, and that surprises me - to the point of asking for help. I have two options, only one of which can be specified; say -frtti and -fno_rtti (say). The other one is that program_options, by default, wants to use double hyphens to define options: "foo --option1 --option2" I'm a lot more comfortable with single hyphens: "foo -option1 -option2" Am I missing something basic here? -- -- Marshall Marshall Clow Idio Software <mailto:marshall@idio.com> It is by caffeine alone I set my mind in motion. It is by the beans of Java that thoughts acquire speed, the hands acquire shaking, the shaking becomes a warning. It is by caffeine alone I set my mind in motion.

2 3

installing BGL-python
by Jeff Abrahamson 08 Jan '06

08 Jan '06

I'm installing the Boost Graph Library python bindings on a Debian testing machine. BGL-python appears not to be available as a .deb, so I am installing from source. http://www.osl.iu.edu/~dgregor/bgl-python/ The readme suggests I run $BOOST_ROOT/tools/build/jam_src/build.sh. This directory exists, but the file does not. It also suggests I run "bjam <options>". I can't think of any options I want a priori [ ;-) ] so I run bjam with no options, but to no avail: jeff@krypton:bgl-python-0.9 $ bjam Unable to load Boost.Build: could not find "boost-build.jam" --------------------------------------------------------------- Attempted search from /home/jeff/tmp/bgl-python-0.9 up to the root and in these directories from BOOST_BUILD_PATH and BOOST_ROOT: /usr/share/boost-build. Please consult the documentation at 'http://www.boost.org'. jeff@krypton:bgl-python-0.9 $ BTW, Boost.Build does not exist on my machine. I'm not clear on what should cause it to exist. Googling largely points me to the above. I'm a bit confused, clearly. Can anyone offer a pointer? Thanks much. -- Jeff Jeff Abrahamson <http://www.purple.com/jeff/> +1 215/837-2287 GPG fingerprint: 1A1A BA95 D082 A558 A276 63C6 16BF 8C4C 0D1D AE4B

5 5

[Boost.Python] newbie: Lifetime of objects
by Sergey Sikorskiy 08 Jan '06

08 Jan '06

Hello everyone. I'm trying to map into python classes shown below. class A { friend class B; public: ~A(void) {} private: A(B& b) : m_B(&b) { } B* m_B; }; class B { friend class C; public: ~B(void) {} A* make_a(void) { return new A(*this); } private: B(C& c) : m_C(&c) { } C* m_C; }; class C { public: ~C(void) {} B* make_b(void) { return new B(*this); } }; C* make_c() { return new C(); } Objects are supposed to be created in the order C, B, A and destroyed in the order A, B, C. I do not want to map constructors of A, B and C. I can see three ways to do what I want: 1) class_<A>("A", no_init); class_<B>("B", no_init) .def("make_a", &B::make_a, return_internal_reference<>()) ; class_<C>("C", no_init) .def("make_b", &C::make_b, return_internal_reference<>()) ; def("make_c", make_c, return_value_policy<manage_new_object>()); 2) class_<A>("A", no_init); class_<B>("B", no_init) .def("make_a", &B::make_a, return_value_policy<manage_new_object>()) ; class_<C>("C", no_init) .def("make_b", &C::make_b, return_value_policy<manage_new_object>()) ; def("make_c", make_c, return_value_policy<manage_new_object>()); 3) class_<A, shared_ptr<A>, noncopyable>("A", no_init); class_<B, shared_ptr<B>, noncopyable>("B", no_init) .def("make_a", &B::make_a, return_value_policy<manage_new_object>()) ; class_<C, shared_ptr<C>, noncopyable>("C", no_init) .def("make_b", &C::make_b, return_value_policy<manage_new_object>()) ; def("make_c", make_c, return_value_policy<manage_new_object>()); C::make_b and B::make_a are supposed to return shared_ptr<B> and shared_ptr<A> respectively in this case. After debugging this code I've got strange results: - In case 1 objects aren't get deleted at all; - In case 2 objects are get deleted in wrong order; - In case 3 objects are get deleted in wrong order; Cases 2 and three seem to be identical to me. The only difference I can see is that in case 3 I should manage objects lifetime by myself from C++ code. In opposite, in case 2 objects lifetime will be managed by python. I couldn't get an answer to my problem neither from documentation nor from Boost.Python tests nor from Google. Any explanations or suggestions will be greatly appreciated. Thank you. -- Sergey Sikorskiy

2 1

Re: [Boost-users] Boost-users Digest, Vol 760, Issue 2
by Ryan McGann 08 Jan '06

08 Jan '06

On Dec 19, 2005, at 9:00 AM, boost-users-request(a)lists.boost.org wrote: >> 1) The build.sh file for the boost bjam tool in the 1.33.0 and 1.33.1 >> release seems to have DOS line endings. I know there are prebuilt >> binaries of bjam up on the Web, but our build system builds it >> manually, and it choked on Darwin because sh didn't like the DOS line >> endings. I resaved the file with Unix line endings and it built fine. > > Did you download the tar.gz distribution? That should have Unix line > endings throughout where as the .zip file has DOS line endings > throughout > (intensionally). Well our build system uses whichever archive is checked in. I imagine the PC folks downloaded the .zip version. I can check in a different version for the Unix folks. >> 2) I get errors for multiply defined symbols for the placeholder >> symbols declared in boost/bind/placeholders.hpp. Every file that >> #include <boost/bind.hpp> contains actual instances of _1, _2, etc. >> Changing the declarations of these in boost/bind.hpp to static (I >> added a __APPLE__ to the #ifdef in the middle of the file) fixes this >> issue, but then I get warnings for unused static symbols if I don't >> use the placeholder objects. This issue in particular is quite >> annoying. > > What compiler are you using? The first #if says: > > #if defined(__BORLANDC__) || defined(__GNUC__) > > isn't this the branch that gets taken? Hm in my boost/placeholders.hpp, I see #if defined(__BORLANDC__) ... #elif defined(BOOST_MSVC) || (defined(__DECCXX_VER) && __DECCXX_VER <= 60590031) || defined(__MWERKS__) ... #else ... #endif I don't have a _GCC__ anywhere in there. This is from 1.33.1 (which I just newly expanded from the .tar.gz, not the .zip). If I add a defined(__GCC__) to the first or second set of #ifdefs, it works fine. >> 3) The header in boost/compatibility/cpp_c_headers/cstdio >> does not match up with the cstdio file included with the Mac OS X dev >> tools. >> In particular it is missing a using ::snprintf, which causes problems >> because this cstdio file is being included BEFORE the Mac OS X >> version of the same file, and other C++ header files rely on >> std::snprtinf being declared. I fixed this at first by deleting the >> boost/compatibility/cpp_c_headers folder, but then ending up just >> deleting that single file so that OS X always used the built-in >> header file. > > Why are those headers getting included? They were intended for use > only > with certain broken compilers that didn't have the c-prefixed std lib > headers. They're known not to work with several std conforming > compilers > (but shouldn't be included for these anyway). I'm not sure why they're being included. I'm guessing it's because we pass -I<path to boost> to GCC, which causes it to search inside of that directory before the standard directories get searched. I'll have to investigate that further. Thanks, Ryan

3 2

Wild Compile Errors with ptime member
by Merrill Cornish 04 Jan '06

04 Jan '06

I am running Boost 1.33.0 and compiling wiht MinGW. When I compile the following source file ========================= #include "boost/shared_ptr.hpp" #include "boost/test/test_tools.hpp" #include "boost/date_time/posix_time/posix_time_types.hpp" class foo { public: foo() {} ~foo() {} boost::posix_time::ptime mExecutionStart; }; class foo_test { foo_test(); ~foo_test(); void run(); }; void foo_test::run() { boost::shared_ptr<foo> testObj(new foo()); BOOST_CHECK_EQUAL(testObj->mExecutionStart, testObj->mExecutionStart); }; ================================= I get the (lengthy) compiler error output below. As you can see, something seems to be trying to log something to an output stream. The test compile just fine as long as the BOOST_CHECK_EQUAL() doesn't reference a boost::posix_time::ptime variables. Any ideas? Merrill Cornish ================================= E:/Dev-Cpp/Workflow/boost/include/boost/test/test_tools.hpp: In member function `void boost::test_tools::tt_detail::print_log_value<T>::operator()(std::ostream&, const T&) [with T = boost::posix_time::ptime]': E:/Dev-Cpp/Workflow/boost/include/boost/test/test_tools.hpp:372: instantiated from `std::ostream& boost::test_tools::tt_detail::operator<<(std::ostream&, const boost::test_tools::tt_detail::print_helper_t<T>&) [with T = boost::posix_time::ptime]' E:/Dev-Cpp/Workflow/boost/include/boost/test/utils/wrap_stringstream.hpp:66: instantiated from `boost::basic_wrap_stringstream<CharT>& boost::operator<<(boost::basic_wrap_stringstream<CharT>&, const T&) [with CharT = char, T = boost::test_tools::tt_detail::print_helper_t<boost::posix_time::ptime>]' E:/Dev-Cpp/Workflow/boost/include/boost/test/test_tools.hpp:427: instantiated from `void boost::test_tools::tt_detail::check_frwd(Pred, boost::wrap_stringstream&, boost::test_tools::const_string, size_t, boost::test_tools::tt_detail::tool_level, boost::test_tools::tt_detail::check_type, const Arg0&, const char*, const Arg1&, const char*) [with Pred = boost::test_tools::tt_detail::equal_impl_frwd, Arg0 = boost::posix_time::ptime, Arg1 = boost::posix_time::ptime]' E:/Dev-Cpp/Workflow/test/src/TimeDemo.cc:19: instantiated from here E:/Dev-Cpp/Workflow/boost/include/boost/test/test_tools.hpp:274: error: no match for 'operator<<' in 'ostr << t' E:/MinGW/bin/../lib/gcc/mingw32/3.4.2/../../../../include/c++/3.4.2/bits/ostream.tcc:63: note: candidates are: std::basic_ostream<E, T>& std::basic_ostream<_CharT, _Traits>::operator<<(std::basic_ostream<_CharT, _Traits>&(*)(std::basic_ostream<_CharT, _Traits>&)) [with _CharT = char, _Traits = std::char_traits<char>] E:/MinGW/bin/../lib/gcc/mingw32/3.4.2/../../../../include/c++/3.4.2/bits/ostream.tcc:74: note: std::basic_ostream<E, T>& std::basic_ostream<_CharT, _Traits>::operator<<(std::basic_ios<_CharT, _Traits>&(*)(std::basic_ios<_CharT, _Traits>&)) [with _CharT = char, _Traits = std::char_traits<char>] E:/MinGW/bin/../lib/gcc/mingw32/3.4.2/../../../../include/c++/3.4.2/bits/ostream.tcc:86: note: std::basic_ostream<E, T>& std::basic_ostream<_CharT, _Traits>::operator<<(std::ios_base&(*)(std::ios_base&)) [with _CharT = char, _Traits = std::char_traits<char>] E:/MinGW/bin/../lib/gcc/mingw32/3.4.2/../../../../include/c++/3.4.2/bits/ostream.tcc:121: note: std::basic_ostream<E, T>& std::basic_ostream<_CharT, _Traits>::operator<<(long int) [with _CharT = char, _Traits = std::char_traits<char>] E:/MinGW/bin/../lib/gcc/mingw32/3.4.2/../../../../include/c++/3.4.2/bits/ostream.tcc:155: note: std::basic_ostream<E, T>& std::basic_ostream<_CharT, _Traits>::operator<<(long unsigned int) [with _CharT = char, _Traits = std::char_traits<char>] E:/MinGW/bin/../lib/gcc/mingw32/3.4.2/../../../../include/c++/3.4.2/bits/ostream.tcc:98: note: std::basic_ostream<E, T>& std::basic_ostream<_CharT, _Traits>::operator<<(bool) [with _CharT = char, _Traits = std::char_traits<char>] E:/MinGW/bin/../lib/gcc/mingw32/3.4.2/../../../../include/c++/3.4.2/ostream:178: note: std::basic_ostream<_CharT, _Traits>& std::basic_ostream<_CharT, _Traits>::operator<<(short int) [with _CharT = char, _Traits = std::char_traits<char>] E:/MinGW/bin/../lib/gcc/mingw32/3.4.2/../../../../include/c++/3.4.2/ostream:189: note: std::basic_ostream<_CharT, _Traits>& std::basic_ostream<_CharT, _Traits>::operator<<(short unsigned int) [with _CharT = char, _Traits = std::char_traits<char>] E:/MinGW/bin/../lib/gcc/mingw32/3.4.2/../../../../include/c++/3.4.2/ostream:193: note: std::basic_ostream<_CharT, _Traits>& std::basic_ostream<_CharT, _Traits>::operator<<(int) [with _CharT = char, _Traits = std::char_traits<char>] E:/MinGW/bin/../lib/gcc/mingw32/3.4.2/../../../../include/c++/3.4.2/ostream:204: note: std::basic_ostream<_CharT, _Traits>& std::basic_ostream<_CharT, _Traits>::operator<<(unsigned int) [with _CharT = char, _Traits = std::char_traits<char>] E:/MinGW/bin/../lib/gcc/mingw32/3.4.2/../../../../include/c++/3.4.2/bits/ostream.tcc:179: note: std::basic_ostream<E, T>& std::basic_ostream<_CharT, _Traits>::operator<<(long long int) [with _CharT = char, _Traits = std::char_traits<char>] E:/MinGW/bin/../lib/gcc/mingw32/3.4.2/../../../../include/c++/3.4.2/bits/ostream.tcc:214: note: std::basic_ostream<E, T>& std::basic_ostream<_CharT, _Traits>::operator<<(long long unsigned int) [with _CharT = char, _Traits = std::char_traits<char>] E:/MinGW/bin/../lib/gcc/mingw32/3.4.2/../../../../include/c++/3.4.2/bits/ostream.tcc:238: note: std::basic_ostream<E, T>& std::basic_ostream<_CharT, _Traits>::operator<<(double) [with _CharT = char, _Traits = std::char_traits<char>] E:/MinGW/bin/../lib/gcc/mingw32/3.4.2/../../../../include/c++/3.4.2/ostream:219: note: std::basic_ostream<_CharT, _Traits>& std::basic_ostream<_CharT, _Traits>::operator<<(float) [with _CharT = char, _Traits = std::char_traits<char>] E:/MinGW/bin/../lib/gcc/mingw32/3.4.2/../../../../include/c++/3.4.2/bits/ostream.tcc:261: note: std::basic_ostream<E, T>& std::basic_ostream<_CharT, _Traits>::operator<<(long double) [with _CharT = char, _Traits = std::char_traits<char>] E:/MinGW/bin/../lib/gcc/mingw32/3.4.2/../../../../include/c++/3.4.2/bits/ostream.tcc:284: note: std::basic_ostream<E, T>& std::basic_ostream<_CharT, _Traits>::operator<<(const void*) [with _CharT = char, _Traits = std::char_traits<char>] E:/MinGW/bin/../lib/gcc/mingw32/3.4.2/../../../../include/c++/3.4.2/bits/ostream.tcc:307: note: std::basic_ostream<E, T>& std::basic_ostream<_CharT, _Traits>::operator<<(std::basic_streambuf<_CharT, _Traits>*) [with _CharT = char, _Traits = std::char_traits<char>] E:/MinGW/bin/../lib/gcc/mingw32/3.4.2/../../../../include/c++/3.4.2/ostream:504: note: std::basic_ostream<char, _Traits>& std::operator<<(std::basic_ostream<char, _Traits>&, const unsigned char*) [with _Traits = std::char_traits<char>] E:/MinGW/bin/../lib/gcc/mingw32/3.4.2/../../../../include/c++/3.4.2/ostream:499: note: std::basic_ostream<char, _Traits>& std::operator<<(std::basic_ostream<char, _Traits>&, const signed char*) [with _Traits = std::char_traits<char>] E:/MinGW/bin/../lib/gcc/mingw32/3.4.2/../../../../include/c++/3.4.2/bits/ostream.tcc:612: note: std::basic_ostream<char, _Traits>& std::operator<<(std::basic_ostream<char, _Traits>&, const char*) [with _Traits = std::char_traits<char>] E:/MinGW/bin/../lib/gcc/mingw32/3.4.2/../../../../include/c++/3.4.2/bits/ostream.tcc:567: note: std::basic_ostream<E, T>& std::operator<<(std::basic_ostream<E, T>&, const char*) [with _CharT = char, _Traits = std::char_traits<char>] E:/MinGW/bin/../lib/gcc/mingw32/3.4.2/../../../../include/c++/3.4.2/ostream:465: note: std::basic_ostream<char, _Traits>& std::operator<<(std::basic_ostream<char, _Traits>&, unsigned char) [with _Traits = std::char_traits<char>] E:/MinGW/bin/../lib/gcc/mingw32/3.4.2/../../../../include/c++/3.4.2/ostream:460: note: std::basic_ostream<char, _Traits>& std::operator<<(std::basic_ostream<char, _Traits>&, signed char) [with _Traits = std::char_traits<char>] E:/MinGW/bin/../lib/gcc/mingw32/3.4.2/../../../../include/c++/3.4.2/bits/ostream.tcc:505: note: std::basic_ostream<char, _Traits>& std::operator<<(std::basic_ostream<char, _Traits>&, char) [with _Traits = std::char_traits<char>] E:/MinGW/bin/../lib/gcc/mingw32/3.4.2/../../../../include/c++/3.4.2/ostream:449: note: std::basic_ostream<E, T>& std::operator<<(std::basic_ostream<E, T>&, char) [with _CharT = char, _Traits = std::char_traits<char>] make: *** [test/obj/TimeDemo.o] Error 1

3 2

Re: [Boost-users] multiple definitions of symbol withRe: multiple definitions of symbol with Boost.Test
by Perepelitsa Roman 02 Jan '06

02 Jan '06

>> When I try to link a test suite I get this: >> >> ld: multiple definitions of symbol boost::test_tools::(anonymous >> namespace)::check_is_close >> mspathCEntry_test.o definition of boost::test_tools::(anonymous >> namespace)::check_is_close in section (__DATA,__data) >> ModelBuilder_test.o definition of boost::test_tools::(anonymous >> namespace)::check_is_close in section (__DATA,__data) >> ld: multiple definitions of symbol boost::test_tools::(anonymous >> namespace)::check_is_small >> mspathCEntry_test.o definition of boost::test_tools::(anonymous >> namespace)::check_is_small in section (__DATA,__data) >> ModelBuilder_test.o definition of boost::test_tools::(anonymous >> namespace)::check_is_small in section (__DATA,__data) >> LinearProduct_test.o definition of boost::test_tools::(anonymous >> namespace)::check_is_close in section (__DATA,__data) >> LinearProduct_test.o definition of boost::test_tools::(anonymous >> namespace)::check_is_small in section (__DATA,__data) >> ..... >> >> This is with boost 1.33 on Darwin/OS-X. The same code was building OK >> with the 1.31 libraries (and 1.32 on linux, I think). I'm using libtool. >> Here's the makefile > I remember seeing similar report recently. As it clear from error message > linker complains about multiple definitions for symbols in anonymous > namespace. This looks like compiler bug. If you know any workarounds please > share them with us. > Gennadiy I had the same problem with vc 7.1. If you add 'static' to all variables definitions in anonymous namespaces it works fine. For example instead of namespace { check_is_close_t check_is_close; } You can write namespace { static check_is_close_t check_is_close; // note 'static' keyword } Best regards, Perepelitsa Roman.

5 5

Re: [Boost-users] vc 7.1 bug: multiple definitions of symbol with Boost.Test
by Perepelitsa Roman 02 Jan '06

02 Jan '06

>> I had the same problem with vc 7.1. > Strange. I never had problems like this with vc7.1 It's very easy to reproduce the problem. Create project with two source files (e.g. a.cpp and b.cpp) both with the same content: -- begin #include <boost/test/floating_point_comparison.hpp> -- end When you try to compile you get two errors: b.obj : error LNK2005: "struct check_is_small_t::boost::check_is_small_t boost::test_tools::`anonymous namespace'::check_is_small" (?check_is_small@?A0xa003c394@test_tools@boost@@3Ucheck_is_small_t@23@A) already defined in a.obj b.obj : error LNK2005: "struct check_is_close_t::boost::check_is_close_t boost::test_tools::`anonymous namespace'::check_is_close" (?check_is_close@?A0xa003c394@test_tools@boost@@3Ucheck_is_close_t@23@A) already defined in a.obj boost version 1.33.1. >> If you add 'static' to all >> variables definitions in anonymous namespaces it works fine. > But anonimous namespace should do the trick itself! Agree. Seems like compiler bug to me. Roman.

2 2

How to identify Boost libraries which support eVC++ compiler
by Mateusz Łoskot 01 Jan '06

01 Jan '06

Hi, I'm trying to use Boost libraries with eMbedded Visual C++ 4.0 compiler (Windows CE applications development). I'd like to catalogue as much as possible Boost libraries which can be used with eVC++ 4.0 compiler. Currently, I can use smart pointers successfully. I also tried to use boost\date_time libraries and I found most of them can not be used with eVC++. I got "unknown CE compiler" error message. So, I suppose I will get that message in most cases. As I revealed there is a compiler detection mechanism in file boost\config\compiler\visualc.hpp but I couldn't find out how exactly it is used. I'd like to identify all Boost libraries which can not be used with eVC++. Could anyone give me a few hints about how to start such identification? Are there any macro definitions or can I expect that visualc.hpp can help me in this task? Thank in advance for all comments Best regards -- Mateusz Łoskot http://mateusz.loskot.net

3 11