- Boost - lists.preview.boost.org

[Date-Time] Regressions/failures with Intel 7.1/Linux
by Aleksey Gurtovoy 29 Sep '04

29 Sep '04

What should we do about these three: http://tinyurl.com/4hbok http://tinyurl.com/4vv64 http://tinyurl.com/4a2xs ? -- Aleksey Gurtovoy MetaCommunications Engineering

2 2

Re:[boost] serialization: buffers
by Robert Ramey 29 Sep '04

29 Sep '04

>I've a class like this: >class Example{ >int str[BSize]; >int *p; >}; >Where p points to next available element (p==str+BSize is possible when it >is full). I.e. str is like begin() and p is like end(). I want to add a >serialize() function, something like this: >template<class Archive> void serialize(Archive &ar,const unsigned int){ >ar & BOOST_SERIALIZATION_NVP(buf,p); >} >but there seems to be no support for buffers like this? Of course the following would work: ar & BOOST_SERIALIZATION_NVP(buf,str); but it would copy too many elements. Or you might try the following (non-portable) idea ar & BOOST_SERIALIZATION_NVP(buf, make_binary_object((p - str)* sizeof(int), str) ); But really, I think you might be best off replacing the class above with class Example { std::slist<int> str; // or maybe std::vector<int> str } For which serialization is already implemented. Robert Ramey

2 1

Re: [boost] [serialization] documentation for xml archive usage
by Robert Ramey 28 Sep '04

28 Sep '04

>> Oh - no. Use the variable name for the tag not the name of the type. >> This is encouraged by usage of the idiom >> >> ar & BOOST_SERIALIZATION_NVP(my_variable); >Might I also suggest a similar interface which allows the caller to specify >the name to go with the value: >BOOST_SERIALIZATION_NAME_VALUE ("variable", m_variable); The following already exists. make_nvp("variable", m_variable); The above macro was only created to avoid retyping the variable name in the Most common case. Robert Ramey

1 0

[Thread] GCC 2.95/STLPort/Linux static lib failures
by Aleksey Gurtovoy 28 Sep '04

28 Sep '04

Is it the test environment that is at failt here (from http://tinyurl.com/5t5mf) /usr/bin/ld: cannot find -lstlport_gcc_stldebug_static collect2: ld returned 1 exit status set -e LD_LIBRARY_PATH=/usr/local/gcc-2.95.3/stlport-4.5.3/lib:/usr/local/gcc-2.95.3/lib:$LD_LIBRARY_PATH export LD_LIBRARY_PATH "/usr/local/gcc-2.95.3/bin/g++" -static -g -pthread -pthread -o "../bin/boost/libs/thread/test/test_barrier_lib.test/gcc-2.95.3-stlport-4.5.3-linux/debug/runtime-link-static/threading-multi/test_barrier_lib" -L"../bin/boost/libs/thread/build/libboost_thread.a/gcc-2.95.3-stlport-4.5.3-linux/debug/runtime-link-static/threading-multi" -L"../bin/boost/libs/test/build/libboost_unit_test_framework.a/gcc-2.95.3-stlport-4.5.3-linux/debug/runtime-link-static/threading-multi" -L"/usr/local/gcc-2.95.3/stlport-4.5.3/lib" -L"/usr/local/gcc-2.95.3/lib" "../bin/boost/libs/thread/test/test_barrier_lib.test/gcc-2.95.3-stlport-4.5.3-linux/debug/runtime-link-static/threading-multi/test_barrier.o" "../bin/boost/libs/thread/test/test_barrier_lib.test/gcc-2.95.3-stlport-4.5.3-linux/debug/runtime-link-static/threading-multi/tss_null.o" "../bin/boost/libs/thread/build/libboost_thread.a/gcc-2.95.3-stlport-4.5.3-linux/debug/runtime-link-static/threading-multi/libboost_thread-gcc295-mt-sgdp-1_32.a" "../bin/boost/libs/test/build/libboost_unit_test_framework.a/gcc-2.95.3-stlport-4.5.3-linux/debug/runtime-link-static/threading-multi/libboost_unit_test_framework.a" "../bin/boost/libs/thread/build/libboost_thread.a/gcc-2.95.3-stlport-4.5.3-linux/debug/runtime-link-static/threading-multi/libboost_thread-gcc295-mt-sgdp-1_32.a" "../bin/boost/libs/test/build/libboost_unit_test_framework.a/gcc-2.95.3-stlport-4.5.3-linux/debug/runtime-link-static/threading-multi/libboost_unit_test_framework.a" -lrt -lstlport_gcc_stldebug_static -lrt -Wl,-rpath-link,. ? -- Aleksey Gurtovoy MetaCommunications Engineering

3 5

Re:[boost] [serialization] documentation for xml archive usage
by Robert Ramey 28 Sep '04

28 Sep '04

>However, this triggers a BOOST_STATIC_ASSERT in >basic_xml_oarchive<Archive>::save_override<T>(const T&, BOOST_PFTO int). >The implementation insists that all serialized types be wrapped in a >nvp<T>. That is the intent. >But I couldn't find an >explanation in the docs what special steps a user is supposed to take >if the data shall be serialized into an xml archive. (The only hint >that xml archives need special care that I found was the description >of the header file nvp.hpp libs/serialization/doc/headers.html: "To >associate a name tag with a serializable object. This is necessary to >properly render an xml archive which includes the object name." BTW, >this webpage claims nvp.hpp is in boost/archive, but in fact it is in >boost/serialization.) >Do I need to write > ar & nvp<MyMemberType>("my_member_tag", this->my_member); >in my serialization functions for every variable I want to > (de-)serialize? Can I choose an arbitrary tag for each variable or is >it supposed to be consistent for all variables of a specific type? Oh - no. Use the variable name for the tag not the name of the type. This is encouraged by usage of the idiom ar & BOOST_SERIALIZATION_NVP(my_variable); >Am I correct to assume that the code will still work if I serialize into >a "normal" text archive and the nvp will essentially be ignored? And all other archives as well - with no extra runtime overhead (assuming a decent optimizing compiler) There a section Reference:Class Serialization:Serialization Wrappers:Name-Value pairs where this is described. Perhaps this isn't obvious from contents. >May I suggest that a section explaining the issues with xml archives be >added to the docs before the 1.32 release? Yes you may.

4 3

The Smart Container library
by brangdon＠cix.compulink.co.uk 28 Sep '04

28 Sep '04

In-Reply-To: <1256163046.20040926162826(a)topmail.sk> I'm very dubious about using: vec.begin()->bar(); instead of: (*vec.begin())->bar(); It means that ptr_vector<T> is not syntactically a drop-in replacement for vector<T *> or vector<shared_ptr<T> >. Won't that make it unnecessarily difficult to "upgrade" existing classes, and harder to switch back again should the need arise? Doesn't it also obscure what is going on? It seems a fundamentally wrong notation to me. -- Dave Harris, Nottingham, UK

2 1

repost: [mpl] bad interaction with Boost.Bind
by Joaquín Mª López Muñoz 28 Sep '04

28 Sep '04

Alexsey, do you think something must/can be done to solve this? http://lists.boost.org/MailArchives/boost/msg72210.php I think I cannot commit the patch myself since the affected code is automatically generated by some tools of yours. Otherwise, please tell me so and I'll be happy to proceed. Thanks Joaquín M López Muñoz Telefónica, Investigación y Desarrollo

2 1

Re: [boost] Re: [review] Formal review of the Smart Container
by brangdon＠cix.compulink.co.uk 28 Sep '04

28 Sep '04

In-Reply-To: <cj6o3i$rgn$1(a)sea.gmane.org> pavel_vozenilek(a)hotmail.com (Pavel Vozenilek) wrote (abridged): > 0. Name of the library should be "Smart Containers" > (note the plural). Also I'm not keen on anything calling itself "smart". It's too vague - smart in what way? Wouldn't "Pointer Container(s)" be better? -- Dave Harris, Nottingham, UK

1 0

Fw: Boost License Permission
by John Maddock 28 Sep '04

28 Sep '04

Another permission received: ----- Original Message ----- From: <SCleary(a)jerviswebb.com> To: <boost-owner(a)lists.boost.org> Sent: Tuesday, September 28, 2004 12:53 PM Subject: Boost License Permission > I, Stephen Cleary, give permission for all my contributions to Boost to be > moved to the Boost Software License Version 1. > > -Steve > > P.S. Sorry for the late reply; I've been on sabbatical. >

1 0

[Optional] Borland failures
by Aleksey Gurtovoy 28 Sep '04

28 Sep '04

Could somebody who cares about Borland take a look/comment of these two: http://tinyurl.com/5uw9x http://tinyurl.com/6jse9 ? Judging from the errors, they seem like a low-hanging fruit. -- Aleksey Gurtovoy MetaCommunications Engineering

3 5