- Boost-users - lists.boost.org

MPL & Shared Libraries
by Robert Dailey 28 Nov '07

28 Nov '07

Hi, I heard from someone that when building a shared library (DLL file), the compiler will not do the same processing of MPL code that it would do for an EXE. For example: struct Foo { static const float val = 1.5f; }; When exporting the 'Foo' class to a shared library, what will become of the 'val' member? Is just the number "1.5f" written out or what? I've given a very simple example, but the more complex example expands into the boost::mpl library, which follows the same concepts.

3 2

Boost. Parameter and deduced constructor ?
by StephQ 28 Nov '07

28 Nov '07

Thank you for your previous help with the Boost. Parameter library, I have been able to solve my problem. I would like to know if is it possible in any way to exploit the Boost. Parameter library to get a template class with a constructor that automatically deduce the correct template parameters. If not I would like to know if there exist a convenient way to minimize the pain resulting from template classes. For example now I have to write: VariateSampler< GaussianDistribution, MersenneTwisterPseudoRng> gaussianSampler( myGenerator, GaussianDistribution() ); Creating a make_VariateSampler function alone does not buy me anything. I would like to write: I would really like to write: VariateSampler<> gaussianSampler = make_VariateSampler( myGenerator, GaussianDistribution() ); VariateSampler<> poissonSampler = make_VariateSampler( myGenerator, PossionDistribution() ); and gaussianSampler and poissonSampler be of different types (deduced from the rhs): gaussianSampler of type VariateSampler<MersenneTwisterPseudoRng,GaussianDistribution> and poissonSampler of type VariateSampler<MersenneTwisterPseudoRng,PoissonDistribution> Now, these types are not complicated, but I am using a template decorator approach to modify the behaviour of these samplers and the resulting types are too nasty for anyone to write them. How could I improve the situation? Something like boost::function for classes? The point is that I (the user) could not care less about these types, only the sampler class needs to know them to operate correctly. Do I have necessarily to create them (via a make_VariateSampler) and pass them on the fly where needed? Thank you StephQ

2 1

boost::serialization binary archives not portable?
by Daniel Oberhoff 28 Nov '07

28 Nov '07

Hi, I have a problem with boost::serialization in that I cannot transport binary archives between my macbookpro (osx 10.4 latest update) and my dell box at work (ubuntu gutsy with universe). As a test I just serialized a 10-byte binary object. Has anyone else been moving binary archives between different platforms? here are the stacktraces up to the exception throws Moving from ubuntu to osx I get this #7 0x0001bcc8 in boost::throw_exception<boost::archive::archive_exception> () at libs/serialization/src/basic_serializer_map.cpp:52 #8 0x0000f104 in boost::archive::basic_binary_iarchive<boost::archive::binary_iarchive>::init (this=0xbfffeec8) at ./boost/archive/impl/basic_binary_iarchive.ipp:54 #9 0x0000f20b in boost::archive::binary_iarchive_impl<boost::archive::binary_iarchive, char, std::char_traits<char> >::init (this=0xbfffeec8, flags=0) at ./boost/archive/binary_iarchive_impl.hpp:51 #10 0x0000f4a4 in boost::archive::binary_iarchive_impl<boost::archive::binary_iarchive, char, std::char_traits<char> >::binary_iarchive_impl (this=0xbfffeec8, is=@0xbfffec30, flags=0) at ./boost/archive/binary_iarchive_impl.hpp:80 #11 0x0001862d in boost::archive::binary_iarchive::binary_iarchive () at libs/serialization/src/basic_serializer_map.cpp:52 #12 0x00002bda in main () the other direction: #4 0x00002b41bac2d773 in std::terminate () from /usr/lib/libstdc++.so.6 #5 0x00002b41bac2d85a in __cxa_throw () from /usr/lib/libstdc++.so.6 #6 0x00002b41babc944a in std::__throw_length_error () from /usr/lib/libstdc++.so.6 #7 0x00002b41bac0cda2 in std::string::resize () from /usr/lib/libstdc++.so.6 #8 0x00000000004339de in boost::archive::basic_binary_iprimitive<boost::archive::binary_iarchive, char, std::char_traits<char> >::load (this=0x7ffff015afe0, s=@0x7ffff015ad50) at ./boost/archive/impl/basic_binary_iprimitive.ipp:96 #9 0x0000000000433a23 in boost::archive::load_access::load_primitive<boost::archive::binary_iarchive, std::string> (ar=@0x7ffff015afd0, t=@0x7ffff015ad50) at ./boost/archive/detail/iserializer.hpp:96 #10 0x0000000000433a43 in boost::archive::detail::load_non_pointer_type<boost::archive::binary_iarchive, std::string>::load_primitive::invoke (ar=@0x7ffff015afd0, t=@0x7ffff015ad50) at ./boost/archive/detail/iserializer.hpp:339 #11 0x0000000000433a63 in boost::archive::detail::load_non_pointer_type<boost::archive::binary_iarchive, std::string>::invoke (ar=@0x7ffff015afd0, t=@0x7ffff015ad50) at ./boost/archive/detail/iserializer.hpp:414 #12 0x0000000000433a83 in boost::archive::load<boost::archive::binary_iarchive, std::string> (ar=@0x7ffff015afd0, t=@0x7ffff015ad50) at ./boost/archive/detail/iserializer.hpp:561 #13 0x0000000000433aae in boost::archive::detail::common_iarchive<boost::archive::binary_iarchive>::load_override<std::string> (this=0x7ffff015afd0, t=@0x7ffff015ad50) at ./boost/archive/detail/common_iarchive.hpp:59 #14 0x0000000000433ad3 in boost::archive::array::iarchive<boost::archive::binary_iarchive>::load_override<std::string> (this=0x7ffff015afd0, x=@0x7ffff015ad50, version=0) at ./boost/archive/array/iarchive.hpp:122 #15 0x0000000000433afb in boost::archive::basic_binary_iarchive<boost::archive::binary_iarchive>::load_override<std::string> (this=0x7ffff015afd0, t=@0x7ffff015ad50) at ./boost/archive/basic_binary_iarchive.hpp:62 #16 0x0000000000433b23 in boost::archive::binary_iarchive_impl<boost::archive::binary_iarchive, char, std::char_traits<char> >::load_override<std::string> (this=0x7ffff015afd0, t=@0x7ffff015ad50) at ./boost/archive/binary_iarchive_impl.hpp:45 #17 0x0000000000433b50 in boost::archive::detail::interface_iarchive<boost::archive::binary_iarchive>::operator>><std::string> (this=0x7ffff015afd0, t=@0x7ffff015ad50) at ./boost/archive/detail/interface_iarchive.hpp:63 #18 0x0000000000433b87 in boost::archive::basic_binary_iarchive<boost::archive::binary_iarchive>::init (this=0x7ffff015afd0) at ./boost/archive/impl/basic_binary_iarchive.ipp:52 #19 0x000000000040c8ee in boost::archive::binary_iarchive_impl<boost::archive::binary_iarchive, char, std::char_traits<char> >::init (this=0x7ffff015afd0, flags=0) at ./boost/archive/binary_iarchive_impl.hpp:51 #20 0x000000000040c971 in binary_iarchive_impl (this=0x7ffff015afd0, is=@0x7ffff015b790, flags=0) at ./boost/archive/binary_iarchive_impl.hpp:80 #21 0x000000000040c9db in boost::archive::binary_iarchive::binary_iarchive () at ./boost/archive/codecvt_null.hpp:48 #22 0x0000000000405518 in main () daniel

4 5

Follow-up on 64 bit boost
by Phil Hystad 28 Nov '07

28 Nov '07

Yet another question on 64 bit boost (follow-up)... Can someone confirm that boost builds OK on Windows 64 bit platforms and if the "address-model=64" instruction applies to the somewhat confusing (to me) 64 bit Windows architecture. Thanks for the confirmations on Red Hat 64 bit. 73, phil phystad(a)mac.com

2 1

Boost 1.35 release date
by Chauhan, Vikas 28 Nov '07

28 Nov '07

Hello, Can you please advise the planned release date for BOOST 1.35 version. Regards, Vikas

2 1

BOOST_STATIC_ASSERT
by Hicham Mouline 28 Nov '07

28 Nov '07

hi, template <typename CT> class C { BOOST_STATIC_ASSERT(...); }; class D; I would like to forbid the instantiation of C<D>. How can i compare CT with D to serve as the condition of the boost static assert=? rds,

3 2

Re boost::bind
by Martin Fisher 28 Nov '07

28 Nov '07

I'm trying to use boost::bind - and I'm probably doing something very obviously wrong, but code blindness has set in. A simple example: I have class X { public: void t(int a, int b) { cout << a * b << endl; } }; then in main... vector<int> v; // filled with some ints for_each(v.begin(), v.end(), boost::bind(&X::t, _1, 4)); // or _1, 4 But this doesn't compile - using Borland Turbo C++ (or Visual C++) Elsewhere in my code I use for_each(istream_iterator<string>(f), istream_iterator<string>(), boost::bind(Inserter<T>(), boost::ref(m), _1)); Which works just fine... I'm sure it's something strikingly obvious - but as far as I can see I'm doing much the same as in the docs ? Thanks for any comments. Martin

2 1

vs2005, intel10.1, autolinking libs
by Hicham Mouline 28 Nov '07

28 Nov '07

Hi, I built a 64bit release version of Boost.Test with intel10.1 64bit compiler. bjam -with-test -toolset=intel stage release I moved the 64bit libs to c:\program files\boost\lib which I set in LIB env var, and set in Tools/Options/VC++directories/x64/Libraries in VS. #including boost test headers works correcty. Compilation works but linking (xilink) fails because of undefined symbols which are in libboost_unit_test_framework-iw-mt-s.lib I compile my project with /MT. Adding verbose to the linker, the list of libraries being searched doesn't include any boost lib. 0. Autolinking is not working? (I'm sure it worked once with date_time where I didn't specify the lib at all and it looked for it by itself) 1. If I explicitly add libboost_unit_test_framework-iw-mt-s.lib in Project Properties/Linker/Input/Additional Dependencies, linking fails as it doesn't find the .lib, even though the LIB env var + VS tools/options are set to include c:\program files\boost\lib 2. If I add c:\program files\boost\lib explicitly to Project Properties/Linker/General/Additional Library Directories, then all works. I'd prefer not to include in the project properties the dependencies on boost, but have it as a system-wide setting (LIB or VS/Tools/Options) 3. there is a warning that the compiler version is unknown, run the configure script. Should I look in Boost.Build doc? Rds,

1 0

boost and intel compiler (ICPC).
by Yann Golanski 28 Nov '07

28 Nov '07

Did anyone run any benchmarks on boost compiled with icpc, the Intel compiler? -- yann(a)kierun.org -= H+ =- www.kierun.org PGP: 009D 7287 C4A7 FD4F 1680 06E4 F751 7006 9DE2 6318

2 2

Re: [Boost-users] Serialization using BOOST_CLASS_EXPORT_GUID
by Pavlo Korzhyk 28 Nov '07

28 Nov '07

When class is XXX_EXPORT-ed the code is generated for each included archive header. This is explained somewhere in the docs, probably near BOOST_CLASS_EXPORT macro description. So to avoid XML-related code generation don't #include unneeded archives Sincerely, Pavlo Korzhyk. I'm not sure what "implicit generation of XML-Archive code" refers to. > > Code is generated only for those archive classes actually used. > > RObert Ramey > > "Oliver Kania" <kania.oliver(a)googlemail.com> wrote in message > news:1262c4ee0711270804o50863f90l98f47fa7b2597005@mail.gmail.com... > Hello ! > when using BOOST_CLASS_EXPORT_GUID, is there an option > to disable implicit generation of XML-Archive code. > I have quite a lot of serialization going on and want to save myself > some headaches connected to XML archives. >

2 1