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

[boost::format] How to not display 0 integer?
by tomasz2k＠poczta.onet.pl 29 Aug '07

29 Aug '07

Hello group I'm using boost::format heavily to format my output for user. I've run into a problem that I cannot resolve for now. I use this format: int i = 4; cout << format ("(%|1$+2|)") % i; // -> (+4) i = -4; cout << format ("(%|1$+2|)") % i; // -> (-4) That's fine and expected. But my question for the one below: int i = 0; cout << format ("(%|1$+2|)") % i; // -> ( 0) // -> ( ) how? How to avoid printing 0? I want formatter to print values in plus or in minus only. When there's value 0 - display only spaces to width. My problem is that I cannot create wrapper over that integer, I must feed formatter with int for various reasons. Does anyone know how to achive this? Maybe I override some parts of library or parsing method? Maybe some of you added your own formatts to formatter and want to share? Any hint or example would be valuable. Thanks in advance, Tomasz Kalkosiñski

1 0

warning C4180 in VS 2005 for bind.hpp
by Adam Badura 29 Aug '07

29 Aug '07

I have a large project at work. We use Visual Studio 2005 with SP 1 and Boost 1.34.0. When we use boost::bind in algorithms on collections we very often get following warning (at level 3): J:\ThirdParty\boost_1_34_0\boost/bind.hpp(1575) : warning C4180: qualifier applied to function type has no meaning; ignored the detailed message is following (just an example extract from compilation log, sadly I was unable to produce a simple stand-alone example - but if it is required then I will give some more work into finding one): J:\ThirdParty\boost_1_34_0\boost/bind.hpp(1575) : warning C4180: qualifier applied to function type has no meaning; ignored J:\ThirdParty\boost_1_34_0\boost/bind.hpp(1609) : see reference to class template instantiation 'boost::_bi::add_cref<Pm,I>' being compiled with [ Pm=boost::shared_ptr<nle::views::ScrollEventListener> , I=1 ] j:\sources\Common/Helpers/Observable.h(128) : see reference to class template instantiation 'boost::_bi::dm_result<Pm,A1>' being compiled with [ Pm=boost::shared_ptr<nle::views::ScrollEventListener> (__thiscall boost::weak_ptr<nle::views::ScrollEventListener>::* )(void), A1=boost::arg<1> ] j:\sources\Common/Helpers/Observable.h(120) : while compiling class template member function 'void common::helpers::Observable<T>::registerListener(const boost::weak_ptr<T> &) const' with [ T=nle::views::ScrollEventListener ] j:\sources\NLE/Views/ScrollInfo.h(65) : see reference to class template instantiation 'common::helpers::Observable<T>' being compiled with [ T=nle::views::ScrollEventListener ] One of my colleagues found a "solution" to this problem. If the modifier "const" is removed in one of typedef's the no warning are generated. However we would like a better solution since modifying the library doesn't seem a good one. What to do? Adam Badura

3 2

Graph: "extra" edge processing during BFS
by Eric Fowler 29 Aug '07

29 Aug '07

I have an algorithm that just screams breadth first search. After some thrashing around in the graph library I am confident in about 90% of the implementation. However there is one little snag: When I examine a grey vertex, I want to do some basic logic on the vertex and the "candidate" next edge to see if what I want to do with this edge and this vertex is "legitimate", according to my own definition of legitimacy(*). If the edge is good, I use it, perhaps relaxing it, if not, I just pass on it and go on to the next one. I would like to do this without tweaking or rewriting the BFS algo. Can this be done with just visitors and the various template parameters or must I write my own BFS variant (not that hard to do of course)? Eric * My idea of "legitimate" is to check to see if a path to a given vertex already contains a certain vertex. The path is built as I run the algorithm. "Parent" vertices are stored as the algorithm runs so I can follow a chain up from the examined vertex back to the root. So the basic logic is: Vertex u = Q.top(); Q.pop(); vis.examine_vertex(u, g); //this is already in BFS if(has_certain_property(u, g)) add_to_tree(u, g); else do_not_add(u, g); .... etc.

1 0

Different functions based on type of iterator?
by HighCommander4 29 Aug '07

29 Aug '07

Let's say I had a function template <typename Iterator> void function(Iterator first, Iterator last); and I want it to call two different functions based on if Iterator is a random access iterator or just a forward iterator. Essentially, I want two versions of this function: template <typename RandomAccessIterator> void function(RandomAccessIterator first, RandomAccessIterator last); template <typename ForwardIterator> void function(ForwardIterator first, ForwardIterator last); I want a function call to function(a, b) to translate to the first one if a and b are random access iterators, and the second one if they are not. I'm thinking of somehow combining enable_if and concept checking, I'm just not sure how... -- View this message in context: http://www.nabble.com/Different-functions-based-on-type-of-iterator--tf4345… Sent from the Boost - Users mailing list archive at Nabble.com.

1 0

Linking to DLLs on Windows with GCC
by John Pye 29 Aug '07

29 Aug '07

Hi all, I am having trouble linking against Boost DLLs. Even though I think I am using the correct compiler commands, I seem to end up with statically linked binaries (everything works fine, but Dependency Walker shows that I have no DLL dependency on Boost). Specifically, I am trying to link against Boost:Serialization. Because I'm using MinGW, my Boost libraries had to be compiled by me, so I used "bjam --toolset=gcc --layout=system". I then ran "bjam install" with the same options, which resulted in (over 1GB of) files in c:\Boost. Next I build my own program. It compiles against the Boost files using GCC parameters "-IC:\Boost\include" and then links against Boost::Serialisation using "-LC:\Boost\lib" -lboost_serialization-mt So, what can I do to set GCC to use dynamic linking to the DLL in this case, instead of the static linking that it appears to be using at the moment? (I am a little unclear about the purpose of the .a files currently present in the c:\Boost\lib directory. Do they refer in some way to the DLLs or are they self-contained static libraries?) Cheers JP

1 0

[ptr_container]Swap/reorder elements in ptr_vector
by Bill Buklis 28 Aug '07

28 Aug '07

What is the best or recommended way to swap or reorder elements in a ptr_vector? Naturally, I simply want to swap pointers and not copy any elements. Using swap with the "base" iterator works (see below), but it feels like I'm using an undocumented feature or something. Is there a preferred method? Or is this the best approach? typedef boost::ptr_vector<int> VEC; VEC v; v.push_back( new int(1) ); v.push_back( new int(2) ); VEC::iterator a = v.begin(); VEC::iterator b = v.begin() + 1; // Swap the two underlying pointers using the base iterator std::swap( *a.base(), *b.base() ); -- Bill --

1 0

Adding content to a vertex in a graph
by Stephen Torri 28 Aug '07

28 Aug '07

I made this property graph according to the documentation: class Component { public: typedef boost::shared_ptr<Component> ptr_t; }; class My_Graph { typedef boost::property< boost::vertex_name_t, Component::ptr_t > VertexProperty_t; typedef boost::adjacency_list<boost::vecS, // OutEdgeList boost::vecS, // VertexList boost::directedS, // Directed VertexProperty_t> // VertexProperties Graph_t; Graph_t m_graph; }; I cannot see from the MutablePropertyGraph page how I am suppose to add the VertexProperty_t to the vertex when its created. The documentation for the MutablePropertyGraph shows a use of "add_vertex" giving a vertex_propety_type with the graph. template <class G> struct MutablePropertyGraphConcept { typedef typename boost::graph_traits<G>::edge_descriptor edge_descriptor; void constraints() { function_requires< MutableGraphConcept<G> >(); v = add_vertex(vp, g); p = add_edge(u, v, ep, g); } G g; std::pair<edge_descriptor, bool> p; typename boost::graph_traits<G>::vertex_descriptor u, v; typename boost::graph_traits<G>::vertex_property_type vp; typename boost::graph_traits<G>::edge_property_type ep; }; My confusion lies in the fact that the add_vertex function requires a vertex_property_type the first parameter. So I am unsure how to create a vertex_property_type from a Component::ptr. Is a vertex_property_type equivalent to a Component::ptr? boost::graph_traits<Graph_t>::vertex_property_type vertex_propert_obj = Component::ptr ( new Component() ); boost::graph_traits<Graph_t>::vertex_descriptor new_vertex = add_vertex ( vertex_property_obj, m_graph ); Stephen

1 0

[BGL] Bundled Properties and setS Edgelist container
by Sam Peterson 28 Aug '07

28 Aug '07

I know that if I use a setS for the edgelist container for an adjacency_list class, each edge of my graph will only be added once as I build it. This functionality is very desirable for me, but I've found I can't seem to use it with the equally desirable Bundled Property Maps. Specifically, this line of code doesn't seem to work: (*g)[i].paper_id = atoi(row[0]); g is a pointer to my graph. The exact compiler error with g++ 4.1.1 is: error: invalid conversion from 'size_t' to 'void*' Is there anyway I can use these two features together? If not, I'm going to be very disappointed. If that's the case I'd advise making a large note of it in the bundled properties documentation as I wouldn't have bothered with bundled properties if I knew they carried this limitation. -- Sam Peterson peabody(a)freeshell.org peabodyenator(a)gmail.com

3 7

Short mailing list outage at 9:00PM EDT
by Doug Gregor 28 Aug '07

28 Aug '07

There will be a brief outage of the Boost mailing lists from 9:00PM-9:30PM EDT today. No mail will be lost. Subversion and the Trac will still be available during this time. - Doug

1 0

[BGL] read_graphviz and dynamic properties
by Sam Peterson 28 Aug '07

28 Aug '07

I have been trying (unsuccessfully for the past hour), to read a graphviz file into an adjacency_list type. The program stops with a SIGABRT because I haven't mapped "node_id" to anything within the dynamic properties argument. However, I really have no desire to map node_id to anything; this is a very large graph and I'd like to avoid the memory consumption. If I try to map node id to the vertex_index_t map I receive a compiler error stating that's a const property map. If I want to map node_id to vertex_name_t map, I have to add that property to my adjacency_list type which will bloat the memory consumption. I just want to build the graph without worry about the properties. Is there anyway this can be done easily? The documentation on read_graphviz and write_graphviz are sorely lacking on this subject in my opinion. -- Sam Peterson peabody(a)freeshell.org peabodyenator(a)gmail.com

2 3

boost undefined reference md5.
by chun ping wang 28 Aug '07

28 Aug '07

while trying to link to lib boost md5 i get these errors I build using make with -l"boost_md5-mgw41-1_34_1. booost md5 was build using gcc 4.1.2 mingw. C:/Boost/include/boost-1_34_1/boost/md5.hpp:33: undefined reference to `boost::md5::context::context()' C:/Boost/include/boost-1_34_1/boost/md5.hpp:33: undefined reference to `boost::md5::context::context()' C:/Boost/include/boost-1_34_1/boost/md5.hpp:57: undefined reference to `boost::md5::process(void const*, unsigned int, bool)' C:/Boost/include/boost-1_34_1/boost/md5.hpp:46: undefined reference to `boost::md5::clear()' C:/Boost/include/boost-1_34_1/boost/md5.hpp:46: undefined reference to `boost::md5::clear()'

1 0

[Boost.Test] User Exception handling
by Ewgenij Sokolovski 28 Aug '07

28 Aug '07

Hello. On the webpage I read: In case if your test cases may throw custom exceptions (see here for list of exceptions translated by default), you could register translator specific for that exception. http://www.boost.org/libs/test/doc/components/utf/index.html So, if I understand it right, if I throw some custom exception in my test program and do not catch it, then it is catched by the boost test framework and reported in the proper way - if the exception can be translated by default. Now I look at the exceptions, which can be translated by default and see: In majority of the cases the monitored function doesn't need to throw the boost::execution_exception to report an error in the Execution Monitor. If you want a custom error message to be included into the execution_exception's error message, use one of the following C++ types as an exception: * C string. * std:string. * any exception class in std::exception hierarchy. http://www.boost.org/libs/test/doc/components/execution_monitor/index.html#… So, I can use a C string for my exception. I have written a small example test case and included throwing of an uncaught exception in it: try{ throw "blub"; } catch(char* ex){ throw; } As I started the testing process I didn't get a "blub"-Exception message, but Boost.Test internal framework error: unknown reason So, what's wrong? Why is "blub" not reported as "blub"? Can anybody explain that? Regards Ewgenij

6 8

Serialization in an array
by Hansi Hansi 27 Aug '07

27 Aug '07

Hello, is it possible to serialize a class in a byte-array(e.g. array stream)? best regards Hansjörg _______________________________________________________________________ Jetzt neu! Schützen Sie Ihren PC mit McAfee und WEB.DE. 3 Monate kostenlos testen. http://www.pc-sicherheit.web.de/startseite/?mc=022220

3 2

boost::thread Destructor being called multiple times
by kaliwanagan 27 Aug '07

27 Aug '07

I was just curious as to why the class destructor are (apparently) being called multiple times. I have tried searching the archives to no avail (which prompted me to register and post to the mailinglist). #include <boost/thread/thread.hpp> struct TestingClass { TestingClass() { std::cout << "constructor called" << std::endl; } ~TestingClass() { std::cout << "destructor called" << std::endl; } void operator()() { std::cout << "operator() called" << std::endl; } } testclass; void testBoostThread() { boost::thread thrd (testclass); thrd.join(); } int main () { testBoostThread(); return 0; } The output: constructor called destructor called destructor called destructor called destructor called operator() called destructor called I would appreciate if someone can enlighten me on this. Will having the destructor called multiple times be a cause of concern? Will it cause some undefined symptoms? Is there a way to completely avoid this situation?

4 3

[boost-users][serialization]How to build the whole serialization regression test suite?
by wei niu 27 Aug '07

27 Aug '07

I find run_archive_test.bat, runtest.bat and Jamfile in boost_1_33_1\libs\serialization\test folder. Then I executed run_archive_test.bat,it output: run_archive_test "<test header file>" "<toolset>" "[<boost root directory>]" "[<target directory>]" I didn't know how to give a proper parameter of "test header file".So after reading runtest.bat file I entered command "bjam --dump-test -sTOOLS=vc-7_1 test". It really worked and generated a lot of folders in boost_1_33_1\bin\boost\libs\serialization\test folder and fast consumed all of the free 0.9GB storage space. But I still didn't know how to run so much test files.I executed one of them,it reported sth like "cannot find test_main function".

1 0

[Serialization]Cannot serialize pointer -- newbie needs help
by wei niu 27 Aug '07

27 Aug '07

I cannot serialize an object through a pointer.When running the program,it reports: This application has requested the Runtime to terminate it in an unusual way. Please contact the application's support team for more information. Below is the code : ////////////////////////////////////////////////////////////////////////////////////////////// // // static link library: libboost_serialization-vc71-s-1_33_1.lib // ////////////////////////////////////////////////////////////////////////////////////////////// #include <iostream> #include <fstream> #include <list> #include <boost/archive/text_oarchive.hpp> #include <boost/archive/text_iarchive.hpp> #include <boost/serialization/base_object.hpp> #include <boost/serialization/utility.hpp> #include <boost/serialization/list.hpp> using std::cout ; using std::endl ; class gps_position { public: int m_degrees ; int m_minu float m_seconds ; gps_position() { m_degrees = m_minutes = m_seconds = 0 ; } gps_position( int degrees, int minutes, float seconds ) { m_degrees = degrees ; m_minutes = minutes ; m_seconds = seconds ; } }; std::ostream& operator << ( std::ostream &out, const gps_position &g ) { return out << g.m_degrees << '\'' << g.m_minutes << '\'' << g.m_seconds; } namespace boost{ namespace serialization{ template <class Archive> void serialize( Archive &ar, gps_position &g, const unsigned int version ) { ar & g.m_degrees ; ar & g.m_minutes ; ar & g.m_seconds ; } } } class bus_stop { friend class boost::serialization::access; template<class Archive> void serialize(Archive & ar, const unsigned int version) { ar & latitude; ar & longitude; } gps_position latitude; gps_position longitude; protected: bus_stop(const gps_position & lat_, const gps_position & long_) : latitude(lat_), longitude(long_) {} public: bus_stop(){} // See item # 14 in Effective C++ by Scott Meyers. // re non-virtual destructors in base classes. virtual ~bus_stop(){} friend std::ostream& operator << ( std::ostream &out, const bus_stop &bs ) ; }; std::ostream& operator << ( std::ostream &out, const bus_stop &bs ) { return out << bs.latitude << '\t' << bs.longitude ; } class bus_stop_corner : public bus_stop { friend class boost::serialization::access; std::string street1; std::string street2; virtual std::string description() const { return street1 + " and " + street2; } template<class Archive> void serialize(Archive &ar, const unsigned int version) { // save/load base class information ar & boost::serialization::base_object<bus_stop>(*this); ar & street1 & street2; } public: bus_stop_corner(){} bus_stop_corner(const gps_position & _lat, const gps_position & _long, const std::string & _s1, const std::string & _s2 ) : bus_stop(_lat, _long), street1(_s1), street2(_s2) { } friend std::ostream& operator << ( std::ostream &out, const bus_stop_corner &bsc ) ; }; std::ostream& operator << ( std::ostream &out, const bus_stop_corner &bsc ) { return out << dynamic_cast<const bus_stop&>(bsc) << ' ' << bsc.description() ; } class bus_route { friend class boost::serialization::access; bus_stop * stops[2]; template<class Archive> void serialize(Archive & ar, const unsigned int version) { int i; for(i = 0; i < 2; ++i) ar & stops[i]; } public: bus_route() { stops[0] = stops[1] = 0 ; } bus_route( bus_stop *bs1, bus_stop *bs2 ) { stops[0] = bs1, stops[1] = bs2 ; } }; int main() { const char *file_name = "non_intrusive.dat" ; bus_stop *bs0 = new bus_stop_corner( gps_position(34, 135, 52.560f), gps_position(134, 22, 78.30f), "24th Street", "10th Avenue" ); bus_stop *bs1 = new bus_stop_corner( gps_position(35, 137, 23.456f), gps_position(133, 35, 54.12f), "State street", "Cathedral Vista Lane" ); const bus_route br( bs0, bs1 ) ; { std::ofstream ofs( file_name ) ; boost::archive::text_oarchive oa( ofs ) ; oa << (br) ; } bus_route newbr ; { std::ifstream ifs( file_name ) ; boost::archive::text_iarchive ia( ifs ) ; ia >> newbr ; } return 0 ; } I think maybe it's because I didn't build the serialize library correctly.Ibuilded it with bjam.When debuging it with VS2003,an exception was thrown in the _heap_alloc_base (size_t) function at line 211: line 211: return HeapAlloc(_crtheap, 0, size); Function "void * __cdecl _heap_alloc_base (size_t size)" is in malloc.c.

2 4

[1.33] [signals] auto_ptr and boost::signals
by Seweryn Habdank-Wojewódzki 26 Aug '07

26 Aug '07

Dears I have question. Why there are problems to connect function that returns auto_ptr to the signal? Below there is a code which won't compile i line where is comment. Regards. #include <iostream> #include <boost/signals.hpp> #include <boost/shared_ptr.hpp> #include <boost/bind.hpp> #include <memory> #include <vector> #include <iterator> #include <algorithm> class some_class { public: ::std::vector <int> func1() { using ::std::vector; typedef vector <int> Res; Res res (2); res.at(0) = 13; res.at(1) = 14; return res; } ::boost::shared_ptr < ::std::vector <int> > func2() { using ::std::vector; using ::boost::shared_ptr; typedef shared_ptr < vector <int> > Res; Res res (new vector<int> (2)); res->at(0) = 23; res->at(1) = 24; return res; } ::std::auto_ptr < ::std::vector <int> > func3() { using ::std::vector; using ::std::auto_ptr; typedef auto_ptr < vector <int> > Res; Res res (new vector<int> (2)); res->at(0) = 33; res->at(1) = 34; return res; } }; int main() { using ::boost::signal; using ::std::vector; using ::std::auto_ptr; using ::boost::shared_ptr; using ::boost::bind; some_class sc; signal < vector <int> (void) > sig1; signal < shared_ptr < vector <int> > (void) > sig2; signal < auto_ptr < vector <int> > (void) > sig3; sig1.connect (bind (&some_class::func1,&sc)); vector <int> ret1 (sig1()); ::std::copy (ret1.begin(), ret1.end(), ::std::ostream_iterator<int> (::std::cout, "\n")); sig2.connect (bind (&some_class::func2,&sc)); vector <int> ret2 (*sig2()); ::std::copy (ret2.begin(), ret2.end(), ::std::ostream_iterator<int> (::std::cout, "\n")); sig3.connect (bind (&some_class::func3,&sc)); //sig3(); // <- ERROR } -- |\/\/| Seweryn Habdank-Wojewódzki \/\/

1 0

Boost Unit Test Undefined Reference
by cmicel1＠cct.lsu.edu 26 Aug '07

26 Aug '07

Am I missing something when I get undefined references to main using boost 1.34.1. Here is a minimal example #include <iostream> #include <boost/test/unit_test.hpp> void my_test_function() { std::cout << "hi there" << std::endl; } boost::unit_test::test_suite* init_unit_test_suite( int , char*[] ) { boost::unit_test::test_suite* test = BOOST_TEST_SUITE( "Master test suite" ); test->add( BOOST_TEST_CASE( &my_test_function ) ); return test; } This is copied off of the main page. Here is the compilation line g++ test.cpp -o test -lboost_unit_test_framework-gcc41 With gcc version 4.1.2 Here is the error message: /usr/lib/gcc/i486-linux-gnu/4.1.2/../../../../lib/crt1.o: In function `_start': (.text+0x18): undefined reference to `main' collect2: ld returned 1 exit status Any insight? Chris Miceli

2 1

Re: [Boost-users] boost::thread Destructor being called multiple times
by Nat Goodspeed 26 Aug '07

26 Aug '07

At 09:51 AM 8/25/2007, kaliwanagan wrote: >I was just curious as to why the class destructor are (apparently) >being called multiple times. I have tried searching the archives to no >avail (which prompted me to register and post to the mailinglist). Try defining an explicit copy constructor with a message like the others. I believe the issue is that your object is being passed by value, and being copied a few times along the way. You're not seeing your no-args constructor message because the other new instances are invoking the copy constructor.

3 3

Unable to work out a Composite predicate.
by PJ Durai 25 Aug '07

25 Aug '07

Hello everyone, I am not able to figure out the correct syntax for something I am trying to do. The following works as expected. It filters all the 'new' events into a new vector. remove_copy_if ( myEvents.begin(), myEvents.end(), back_inserter(newEvents), !(boost::bind(&Event::GetEventType, _1) == EventType_New)); I cant figure out how to get a complex conditional working as the predicate. e.g. remove_copy_if ( myEvents.begin(), myEvents.end(), back_inserter(newEvents), (boost::bind(&Event::GetEventType, _1) == NotesEventType_New) && (boost::bind(&Event::GetEventID, _1) == 1000 ) ); I have tried various ways of putting parens around this expression. I just couldn't get it to compile. Is that even possible ? Please Advise. I am using Visual C++ 2005 SP1 on Windows XP SP2. Appreciate your time. thanks pj

3 3

Re: [Boost-users] Serialization newbie needs help
by Dominick Layfield 25 Aug '07

25 Aug '07

"Robert Ramey" <ramey(a)rrsd.com> wrote: >> goes away. Any chance this could be added to a boost::serialization >> FAQ? > > you mean change the section named "rationale" to "FAQ"? Ermm... Yes, I suppose so. There ought to be some section that a newbie who is having problems would immediately look to see if this is a common problem. In my browser, the "Rationale" section of the documentation appears unexpanded by default. And even when I expand it, "Compile time trap when saving a non-const value" doesn't seem (when skimming the docs) relevant to the static assertion error. It also didn't appear in my Google search for the cryptic error message that the compiler produced. >> The "Compile time trap" section of the documentation doesn't actually >> explain what "object tracking" is all about. Neither (amusingly) >> does the Boost->Serialization->Reference->Special >> Considerations->Object Tracking section! > > Hmmm - well it's intended to. Maybe I just thought the meaning of the > term "Object Tracking" obvious. As a newbie, I can tell you that it wasn't obvious to me! :-) As I said, I wouldn't have expected the serialization library to do any automagical pointer stuff, so from this perspective, it's very hard to see what object tracking is, and why it would be necessary. >> What on earth does it actually mean to serialize a pointer? > > Exactly what you think it means - see above. Well, once you've got an idea in your head about what should happen when a pointer is serialized (and had that concept for years, and written a whole library to implement it!), it probably seems obvious and "natural" that it should work that way. But to a newbie (to boost::serialization, not to C++), this behavior is rather surprising. For example if I do: my_class mc; my_class* mc_ptr = &mc; cout << mc_ptr; I don't get the my_class object sent to stdout. I get the value of the pointer itself. If I wanted the actual object displayed, I would dereference the pointer. So my intuition would be that boost::serialization would work in a similar way: if I wanted the object itself output/input, I would do it explicitly. I'm not trying to say that your approach is wrong. All I'm attempting to point out is that other people may have very different (and quite reasonable) expectations about what should happen. >> And why would I want to do such a thing, anyway? > > I don't know what your application is. Sorry. What I meant was "Why would someone want this?" or "Why is this a useful feature?" Fundamentally, there are two approaches to dealing with pointer serialization: (1) disallow it altogether; or (2) serialize the pointed-to object, and do all the clever object-tracking stuff. The first approach has the benefit of simplicity . So the only reason to take the second approach would be if automagic pointer serialization is really useful. However, I can't think of an example of when this would be really useful. Hence my question. But if you could provide me an example of when pointer serialization shines, then I would say "Aha! Now I understand why Robert went to so much trouble to make this work.", and I could be at peace with the world again! :-) BTW, I don't want to sound like I'm bashing your library, so let me end with a compliment. I think the symmetric design of serialize(), with the same function used for both input and output, is one of the prettiest idioms I've seen in years. -- Dominick

4 3

[boost::multi-index] improvement suggestion
by Ovanes Markarian 24 Aug '07

24 Aug '07

Hello all, working with boost multi-index container requires sometimes some effort in regards of correct tagging (or at least some typing work ;). I found the following approach to be useful and may be it can be integrated in the multi-index library. First of all the dealing with searchable collections (STL collections are no exception) can be really nasty in regards of finding an iterator and comparing it with the end iterator. The following function can really be of help: /// template function to dermine if the container contains the key specified /// @param T - container type /// @param K - key type /// @param container - container to search for a key /// @param key - key to be found in the container /// \return iterator_range containing the begin and end iterator of the found key. begin iterator equals end iterator the range is empty => nothing found template<class T, class K> inline boost::iterator_range<typename T::const_iterator> find_range(T const& container, K const& key) { return boost::make_iterator_range(container.find(key),container.end ()); } //non-const version follows as well ... Actually iterator_range defines a "bool"- and "!"- (NOT) operators. iterator_range is returned by this function. Therefore constructs like: std::set<std::string> some_set; if(!find_range(some_set, "my_key")) some_set.insert("my_key"); are possible without the need of accesing the underlying iterator types or explicitly comparing the found iterator with the end iterator. The next step dealing with Multi-Index container turned out in multiple typedefs for every tagged type. The main disadvantage in this approach was to constantly retrieve the required container view and related iterator, so I came up the the following class: /// helper class used to retrieve multi-index values dependent on the view tag template<class Tag_, class MultiIndex_> struct value_retrieval { /// type definition used to produce tag dependent view typedef typename MultiIndex_::index<Tag_>::type view_type; /// type definition for the const iterator through the view typedef typename view_type::const_iterator citer_type; /// iterator range used to represent the result typedef boost::iterator_range<citer_type> result_type; /// initializing ctor /// initializes the contained view by using the specified Tag_ type value_retrieval(MultiIndex_ const& mi) : view_(mi.get<Tag_>()) {} /// find a type at the key specified /// @param LookUpType_ - key type /// @param key - key instance to be found template<class LookUpType_> result_type at(LookUpType_ const& key)const { return find_range(view_, key); } private: /// view reference view_type const& view_; }; This class deals with constant views, since I did not require changeable ones, but as one can see the "at"-function can either be used to identify the found iterator range or just to make a check if such a key exists. Dealing with this type is more easier, as to define multi-index accessed view and iterator types. Sample typedef multi_index_container < some_type , indexed_by < .... > > my_container; typedef value_retrieval<my_container, tag_name> by_name; typedef value_retrieval<my_container, tag_value> by_value; //somewhere in code by_name value_by_name(some_container_inst); //if typename is required prefix it... by_name::result_type r = value_by_name.at("some key"); if(r) /// do smth with r Best Regards, Ovanes

3 4

Serializeable Boost hashmap with vector<long> as key
by Oliver Kania 24 Aug '07

24 Aug '07

Hello ! I am looking for a hashmap that is boost::serializeable, has good performance and is implemented by boost-means. Furthermore, it must have vector<long> as key type. I tried multiindex, but it seems one cannot have keys that are not members of the value type. Boost Bimap is not serializeabel and i do not need the bimap functionality. regards, Oliver

2 1

boost program_options "count" question
by F David Sacerdoti 24 Aug '07

24 Aug '07

As per Volodya's suggestion, posting this question here. He mentioned it had been discussed, but I was unable to find anything appropriate using search engines. I apologize in advance if this is a repeat question. Hi, I am trying to do a simple thing with your program_options boost library: I have a program foo, and I want to invoke it like this: foo -d -d -d I want foo to know "I have counted three -d". I followed your tutorial and tried this: desc.add_options() ("debug,d",po::value< vector<int> >()->default_value(1), "Debug level") ; po::variables_map vm; po::store(po::parse_command_line(argc, argv, desc), vm); po::notify(vm); if (vm.count("debug")) { cout << "Running, debug level: " << vm["debug"].as< vector<int> >().size() << "\n"; } But it did not work, always prints "debug level: 0". For background, this is to make the program compatible with a Python implementation which uses optparse. I have an extensive testing framework that assumes this behavior and it would be nice to implement the same with program_options. Thanks, Federico

3 4

error C2976 in python tutorial?
by Guido Ziliotti 24 Aug '07

24 Aug '07

Probably Has anybody faced error C2976: 'boost::python::class_' : too few template arguments? Compiler msvc-8.0. BOOST_PYTHON_MODULE(hello){ class_<World>("World") .def("greet", &World::greet) .def("set", &World::set) ; } produced that. Source code follows. #include <string> char const* greet() { return "hello, world"; } struct World { void set(std::string msg) { this->msg = msg; } std::string greet() { return msg; } std::string msg; }; #include <boost/python/module.hpp> #include <boost/python/def.hpp> using namespace boost::python; //nota che la funzione globale va prima BOOST_PYTHON_MODULE(hello) { def("greet", greet); class_<World>("World") .def("greet", &World::greet) .def("set", &World::set) ; }

1 0

[test] Uncaught exception in BOOST_CHECK_THROW() causing SIGABRT
by Richard Dingwall 24 Aug '07

24 Aug '07

Hi there, I thought I'd post this because A) it might save someone a lot of head-scratching and B) there aren't any posts on it already. The short of it is, that if you have a setup similar to the following (i.e., an empty throw() clause on a template specialisation): template<class output_type> output_type do_something(int input_value) throw(std::invalid_argument); template<> int do_something(int input_value) throw(std::invalid_argument); template<> long do_something(int input_value) throw(); And attempt to test throwing a std::invalid_argument from within the long specialised function, e.g.: // note: an argument less than zero will throw a std::invalid_argument BOOST_CHECK_THROW(do_something<long>(-1), std::invalid_argument); You will see something the following: Running 4 test cases... terminate called after throwing an instance of 'std::invalid_argument' what(): Input value too low. unknown location(0): fatal error in "long_throw": signal: SIGABRT (application abort requested) sigabrt_test_suite.cpp(58): last checkpoint *** 1 failure detected in test suite "sigabrt tests" My function is throwing a std::invalid_argument and my test case been programmed to catch it. But it doesn't. This had me scratching my head for a few days, until I noticed the empty throw() clause. Completing it resolved the problem immediately. I'm not sure if this is expected behaviour, but if anyone's interested, a test case is attached. I'm using gcc version 4.0.1 (Apple Computer, Inc. build 5367) on a G4 Powerbook with whatever was in Boost's SVN trunk on August 6. Cheers, Richard

2 1

Multi Array Question
by chris dion 24 Aug '07

24 Aug '07

Hi I'm having a problem with the boost/multi_array and I'm hoping someone here can help, or at least explain why the following doesn't work. The problem: I have a multi_array of ints that I want to be able to view as being either row major or column major to simplify a number algorithms. I don't want to change the internal representation of the array (the default c++ row major storage layout is fine), I just want to be able to interchange the indexing order from array[row][col] to array[col][row] for the same multi_array. To do so, I attempted to define 2 array_views of the same multi_array with different stride values, like this: #include <iostream> using namespace std; #include <boost/multi_array.hpp> using namespace boost; int main(void) { typedef multi_array<int, 2> intarray2; typedef intarray2::array_view<2>::type intarray2view2; typedef intarray2::array_view<1>::type intarray2view1; typedef intarray2::index_range intarray2range; intarray2 arr(extents[3][3]); // test data int a = 0; for (int r = 0; r < 3; r++) { for (int c = 0; c < 3; c++) { arr[r][c] = a++; } } intarray2view2 rows = arr[indices[intarray2range().stride(3)][intarray2range().stride(1)]]; intarray2view2 cols = arr[indices[intarray2range().stride(1)][intarray2range().stride(3)]]; /* 0 1 2 3 4 5 6 7 8 */ cout << rows[2][1]; // i expect this to print 7 cout << cols[2][1]; // i expect this to print 5 } Unfortunately, this doesn't work at all (an assert fails when indexing the views). I debugged (using Visual C 2005), and found that the 'rows' array_view has a stride collection of [9, 1], while the 'cols' array_view stride collection is [3, 3]. Both are different than what I specified during construction. It appears that they're being multiplied by the extents of the first dimension of the multi_view array (in this example: 3). I can produce a column major view of a single column of the array using a 1 dimensional view constructed using a degenerate range, like this: intarray2view1 col= arr[indices[1][intarray2range()]]; // column 1 in arr but that's not what I'm hoping to achieve. Can someone explain the behavior above and/or suggest a way of creating a 2d column major array_view of a 2d multi_array? Thanks - Chris Dion _________________________________________________________________ Show Your Messenger Buddies How You Really Feel http://www.freemessengeremoticons.ca/?icid=EMENCA122

2 1

Construction/assignment inconsistency with boost::function on MSVC2005
by Josef Grahn 23 Aug '07

23 Aug '07

Hello, I encountered the following inconsistency constructing a boost::function object from a pointer to a template function. template <typename T> void foo(T) {} int main(int argc, char **argv) { boost::function<void (int)> f1; f1 = foo<int>; boost::function<void (int)> f2 = foo<int>; f1(0); // ok f2(0); // error, function pointer is zero! return 0; } I am compiling on MSVC2005 SP1, using boost version 1.34.1. It seems to work properly with GCC 4.1.2 and boost 1.33.1 on Ubuntu, however. Is this a known problem? Best Regards, Josef Grahn

3 2

Re: [Boost-users] [boost] ScopeExit Review Begins Today
by Jody Hagins 23 Aug '07

23 Aug '07

The discussion threads included comments from several people who did not offer an actual review and/or YES/NO. I have filtered every message with either scope or exit in the subject, and I want to make sure I have all the reviews. If your name is in this list, that means I have a YES/NO review from you. Otherwise, I may see some discussion from you, but no YES/NO review. If your name is NOT in this list, but you feel you provided a review, please point me to your review posting, or provide appropriate clarification. The fact that you participated in the discussion does not mean that I know your opinion on the acceptance of ScopeExit. In addition, I have received a few reviews via private email. For the sake of fairness and openness, I asked the authors to send their review to the list. I will not consider them unless they appear in the open mailing list. Thanks for your cooperation! Kim Barrett Aaron LaFramboise Steven Watanabe Ben Kuppers Andrey Semashev Peder Holt Goran Mitrovic Johan Nilsson Pavel Vozenilek Tom Brinkman Maxim Yanchenko

1 0

Re: [Boost-users] [boost] ScopeExit Review Begins Today
by Jody Hagins 23 Aug '07

23 Aug '07

Thanks for all the input on Alexander's ScopeExit submission. There are some good discussions, so please continue them over the next day or so if necessary. I am very busy this weekend (I am HC of a high school football team, and our first game is tomorrow night), but I will render a conclusion some time next week. Again, thanks for the input.

1 0

ptr_container problem
by Aljaz 23 Aug '07

23 Aug '07

Hello I'm trying to use ptr_vector but I'm having headaches because I have no idea why I'm getting this error: error C2248: 'boost::ptr_container_detail::reversible_ptr_container<Config,CloneAllocator>::operator =' : cannot access private member declared in class 'boost::ptr_container_detail::reversible_ptr_container<Config,CloneAllocator>' with [ Config=boost::ptr_container_detail::sequence_config<boost::asio::dns::base_nameserver_resource,std::vector<void *,std::allocator<void *>>>, CloneAllocator=boost::heap_clone_allocator ] C:\Program Files\boost\boost_1_34_0\boost/ptr_container/detail/reversible_ptr_container.hpp(287) : see declaration of 'boost::ptr_container_detail::reversible_ptr_container<Config,CloneAllocator>::operator =' with [ Config=boost::ptr_container_detail::sequence_config<boost::asio::dns::base_nameserver_resource,std::vector<void *,std::allocator<void *>>>, CloneAllocator=boost::heap_clone_allocator ] This diagnostic occurred in the compiler generated function 'boost::ptr_sequence_adapter<T,VoidPtrSeq,CloneAllocator> &boost::ptr_sequence_adapter<T,VoidPtrSeq,CloneAllocator>::operator =(const boost::ptr_sequence_adapter<T,VoidPtrSeq,CloneAllocator> &)' with [ T=boost::asio::dns::base_nameserver_resource, VoidPtrSeq=std::vector<void *,std::allocator<void *>>, CloneAllocator=boost::heap_clone_allocator ] My code (simplified): class base1 { public: void somefunc() { }; }; class main : public base1 { public: virtual void somefunc() { } }; class derived : public main { public: virtual void somefunc() { } }; boost::ptr_vector<main> m_vector; Any Idea what am I doing wrong? I tried to add do_clone functions/members without success. Any help is highly appreciated Regards A

2 1

ScopeExit Review ends tomorrow (Wednesday)
by Jody Hagins 23 Aug '07

23 Aug '07

The ScopeExit review ends on Wednesday, August 22. If you want to have input on its acceptance into Boost, please provide a review by tomorrow. BTW, we need more input ;-) Thanks! >From the original announcement... The review period for Scope Exit Time Series, submitted by Alexander Nasonov, runs from Monday, August 13 until Wednesday, August 22. >From the documentation: Nowadays, every C++ developer is familiar with RAII technique. It binds resource acquisition and release to initialization and destruction of a variable that holds the resource. But there are times when writing a special class for such variable is not worth the effort. This is when ScopeExit macro comes into play. You put resource acquisition directly in your code and next to it you write a code that releases the resource. Note that ScopeExit uses PP macros and relies on Boost.Typeof. The latest version can is here: http://boost-consulting.com/vault/index.php?action=downloadfile&filename=sc… It's available also at http://tinyurl.com/2z6qg2 Online documentation is here: http://194.6.223.221/~nasonov/scope_exit-0.04/libs/scope_exit/doc/html/inde… >From the review guidelines here: http://boost.org/more/formal_review_process.htm ... Boost mailing list members are encouraged to submit Formal Review comments: * Publicly on the mailing list. * Privately to the Review Manager. Private comments to a library submitter may be helpful to her or him, but won't help the Review Manager reach a decision, so the other forms are preferred. What to include in Review Comments Your comments may be brief or lengthy, but basically the Review Manager needs your evaluation of the library. If you identify problems along the way, please note if they are minor, serious, or showstoppers. Here are some questions you might want to answer in your review: * What is your evaluation of the design? * What is your evaluation of the implementation? * What is your evaluation of the documentation? * What is your evaluation of the potential usefulness of the library? * Did you try to use the library? With what compiler? Did you have any problems? * How much effort did you put into your evaluation? A glance? A quick reading? In-depth study? * Are you knowledgeable about the problem domain? And finally, every review should answer this question: * Do you think the library should be accepted as a Boost library? Be sure to say this explicitly so that your other comments don't obscure your overall opinion. Thanks in advance to every for your participation in this review. _______________________________________________ Boost-users mailing list Boost-users(a)lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users

3 5

Boost fixed point data type or other support for monetary values?
by Jeff Dunlap 23 Aug '07

23 Aug '07

Hello, I'm having some rounding problems using the double data type on some financial calculations. Does Boost have a fixed point data type or is there other functionality that may be helpful to me? Any suggestions would also be appreciated. Thanks very much

1 0

basic file io in boost 1_34_1. A compilable 'hello world' example for large (>2^31byte) files?
by Peter Leopold 23 Aug '07

23 Aug '07

Dear Boost Users, I've used boost on and off for years for its string parsing. Now I'd like to use it to replace std::ifstream for file reading. The immediate requirement is a file > 2^31 bytes. Since my requirement is to replace ifstream, I was hoping for a fairly simple transition, perhaps even something I could manage with an emacs global search-and-replace. I started with kubuntu-feisty's boost 1.33.1. but was unable to execute the first main in the iostreams tutorial Overview (2.1.1). The showstopper was the compiler error <file_sink> not defined in scope. % g++ test.cpp test.cpp: In functin 'int main()': test.cpp::9: error: 'file_sink' was not declared in this scope . . . several more errors. This is an error without precedent, at least according to google. Thinking this is a kubuntu-apt-get issue, I downloaded and rebuilt and installed boost 1_34_1 from scratch. Alas, <file_sink> is still not declared. Am I doing something obvious wrong? I'm using g++ 4.1.2. Does anyone have a few lines of code that will * open a file? * seekg() to the beginning, end and arbitrary location in the file? * tellg() the present file pointer location in the file? * read(address, number of bytes) from the file? These are the basic STL features I'm trying to replace. Many thanks for any pointers to useful documentation (but not to boost.org/libs/iostreams/doc/index.html, please) or code snippets. Once I have my "hello world" working, I might start making sense of <file_sink> templated streams, and why my install can't find <file_sink> when it is sitting right there in <boost/iostreams/device/file.hpp>!?!? -- Peter Leopold Peter dot Leopold at BioAnalyte dot com <http://www.bioanalyte.com>

2 1

Bad Lexical_Cast!
by Frame Buffer 22 Aug '07

22 Aug '07

Hello! I am trying to compile the following program from *Beyond the C++ Standard Library: An Introduction to Boost. *Here is the source code: #include <iostream> #include <string> #include "boost/lexical_cast.hpp" class lexical_castable { public: lexical_castable() { }; lexical_castable(const std::string s) : s_(s) { }; friend std::ostream& operator<<(std::ostream& o, const lexical_castable& le); friend std::istream& operator>>(std::istream& i, lexical_castable& le); private: virtual void print_(std::ostream& o) const; void read_( std::istream& i ); std::string s_; }; std::ostream& operator<<(std::ostream& o, const lexical_castable& le) { le.print_(o); return o; } std::istream& operator>>(std::istream& i, lexical_castable& le) { le.read_(i); return i; } void lexical_castable::read_( std::istream& i ) { i >> s_; } void lexical_castable::print_( std::ostream& o ) const { o << s_ <<"\n"; } int main(int argc, char* argv[]) { lexical_castable le(); std::cin >> le; int i=0; try { i = boost::lexical_cast<int>(le); std::cout << i << '\n'; } catch(boost::bad_lexical_cast &e) { std::cout << e.what() << '\n'; std::cout << "You were supposed to enter a number!\n"; } } The lexical_cast is throwing an exception as follows: boost::bad_lexical_cast::what returned 0x004c9888 "bad lexical cast: source type value could not be interpreted as target" const char * Note that I have modified the original code a bit because I was trying to figure out what went wrong. The object le is getting created successfully with the user entered "number" getting stored in the string s_ Please help. I am using Visual studio 2005 with boost v1.34

2 1

program options
by Stefan Bradl 22 Aug '07

22 Aug '07

Hello, I am using boost::program_options and need to load custom config files. So I think I need to write a parser, right? But I did not find any tutorials or something like that where I can learn how to write and usea parser with program options. Can anybody help me out og this problem? Thx in advance

2 3

boost::serialization throwing bad_alloc
by Fletcher, Matthew (Information Technology) 22 Aug '07

22 Aug '07

Hi all, I am suffering from boost serialization throwing a bad_alloc exception at a very low-level that I've been unable to explain or workaround. I first hit the problem on 1_33 but upgrading to 1_34 and then 1_34_1 had no effect. My code is within one DLL and I'm loading boost dynamically through the DLLs. This is a real-showstopper for me - any suggestions at all gratefully received. Thanks, Matt. The disassembly from save_access::save_primitive: ar.save(t); 488FEC20 mov esi,esp 488FEC22 mov eax,dword ptr [t] 488FEC25 push eax 488FEC26 mov ecx,dword ptr [ar] 488FEC29 add ecx,8 488FEC2C call dword ptr [__imp_boost::archive::basic_binary_oprimitive<boost::archive::binary_oa rchive,char,std::char_traits<char> >::save (48EBA254h)] 488FEC32 cmp esi,esp 488FEC34 call @ILT+121865(__RTC_CheckEsp) (487A9C0Eh) } The debugger cursor points to the cmp line so I believe the exception is being thrown by the __imp_boost call. For what it's worth esi = 1301555968 and esp = 1301555820 and t is an innocuous looking string of size 5135. My top level calling code: std::ostringstream os; boost::archive::binary_oarchive oa( os ); oa << BOOST_SERIALIZATION_NVP( pMyClass ); where pMyClass has been passed as: const myClass * pMyClass Both my top-level class and all intermediate ones have the same standard serialization structure: class myClass : public boost::noncopyable { ... private: myClass(){}; friend class boost::serialization::access; template<class Archive> void serialize(Archive & ar, const unsigned int version) { ar & BOOST_SERIALIZATION_NVP( ... ) ... } } Full stack dump: kernel32.dll!7c812a5b() kernel32.dll!7c812a5b() msvcr71d.dll!47ce9504() msvcr71d.dll!47ce94fb() msvcr71d.dll!47cebed9() msvcr71d.dll!47d06fa9() msvcp71d.dll!47dd8946() msvcp71d.dll!47ddd05f() msvcp71d.dll!47d8a97c() msvcp71d.dll!47d890b2() msvcp71d.dll!47db4b55() msvcp71d.dll!47d8accc() msvcp71d.dll!47d994ca() msvcp71d.dll!47d994ca() boost_serialization-vc71-mt-gd-1_34_1.dll!47f4ae67() msvcp71d.dll!47d870bf() boost_serialization-vc71-mt-gd-1_34_1.dll!47f4abf1() > myDLL.dll!boost::archive::save_access::save_primitive<boost::archive::bi nary_oarchive,std::basic_string<char,std::char_traits<char>,std::allocat or<char> > >(boost::archive::binary_oarchive & ar={...}, const std::basic_string<char,std::char_traits<char>,std::allocator<char> > & t={...}) Line 91 + 0x12 C++ myDLL.dll!boost::archive::detail::save_non_pointer_type<boost::archive:: binary_oarchive,std::basic_string<char,std::char_traits<char>,std::alloc ator<char> > >::save_primitive::invoke(boost::archive::binary_oarchive & ar={...}, const std::basic_string<char,std::char_traits<char>,std::allocator<char> > & t={...}) Line 244 + 0xd C++ myDLL.dll!boost::archive::detail::save_non_pointer_type<boost::archive:: binary_oarchive,std::basic_string<char,std::char_traits<char>,std::alloc ator<char> > >::invoke(boost::archive::binary_oarchive & ar={...}, const std::basic_string<char,std::char_traits<char>,std::allocator<char> > & t={...}) Line 321 + 0xd C++ myDLL.dll!boost::archive::save<boost::archive::binary_oarchive,std::basi c_string<char,std::char_traits<char>,std::allocator<char> > >(boost::archive::binary_oarchive & ar={...}, const std::basic_string<char,std::char_traits<char>,std::allocator<char> > & t={...}) Line 535 + 0xd C++ myDLL.dll!boost::archive::detail::common_oarchive<boost::archive::binary _oarchive>::save_override<std::basic_string<char,std::char_traits<char>, std::allocator<char> > const >() Line 62 + 0x15 C++ myDLL.dll!boost::archive::basic_binary_oarchive<boost::archive::binary_o archive>::save_override<std::basic_string<char,std::char_traits<char>,st d::allocator<char> > const >() Line 66 C++ myDLL.dll!boost::archive::binary_oarchive_impl<boost::archive::binary_oa rchive,char,std::char_traits<char> >::save_override<std::basic_string<char,std::char_traits<char>,std::allo cator<char> > const >() Line 46 C++ myDLL.dll!boost::archive::detail::interface_oarchive<boost::archive::bin ary_oarchive>::operator<<<std::basic_string<char,std::char_traits<char>, std::allocator<char> > const >() Line 80 C++ myDLL.dll!boost::serialization::nvp<std::basic_string<char,std::char_tra its<char>,std::allocator<char> > const >::save<boost::archive::binary_oarchive>() Line 78 C++ myDLL.dll!boost::serialization::access::member_save<boost::archive::bina ry_oarchive,boost::serialization::nvp<std::basic_string<char,std::char_t raits<char>,std::allocator<char> > const > const >(boost::archive::binary_oarchive & ar={...}, const boost::serialization::nvp<std::basic_string<char,std::char_traits<char>, std::allocator<char> > const > & t={...}, const unsigned int file_version=0) Line 94 C++ myDLL.dll!boost::serialization::detail::member_saver<boost::archive::bin ary_oarchive,boost::serialization::nvp<std::basic_string<char,std::char_ traits<char>,std::allocator<char> > const > >::invoke(boost::archive::binary_oarchive & ar={...}, const boost::serialization::nvp<std::basic_string<char,std::char_traits<char>, std::allocator<char> > const > & t={...}, const unsigned int file_version=0) Line 43 + 0x11 C++ myDLL.dll!boost::serialization::split_member<boost::archive::binary_oarc hive,boost::serialization::nvp<std::basic_string<char,std::char_traits<c har>,std::allocator<char> > const > >(boost::archive::binary_oarchive & ar={...}, boost::serialization::nvp<std::basic_string<char,std::char_traits<char>, std::allocator<char> > const > & t={...}, const unsigned int file_version=0) Line 69 + 0x11 C++ myDLL.dll!boost::serialization::nvp<std::basic_string<char,std::char_tra its<char>,std::allocator<char> > const >::serialize<boost::archive::binary_oarchive>() Line 87 + 0x34 C++ myDLL.dll!boost::serialization::access::serialize<boost::archive::binary _oarchive,boost::serialization::nvp<std::basic_string<char,std::char_tra its<char>,std::allocator<char> > const > >(boost::archive::binary_oarchive & ar={...}, boost::serialization::nvp<std::basic_string<char,std::char_traits<char>, std::allocator<char> > const > & t={...}, const unsigned int file_version=0) Line 110 C++ myDLL.dll!boost::serialization::serialize<boost::archive::binary_oarchiv e,boost::serialization::nvp<std::basic_string<char,std::char_traits<char >,std::allocator<char> > const > >(boost::archive::binary_oarchive & ar={...}, boost::serialization::nvp<std::basic_string<char,std::char_traits<char>, std::allocator<char> > const > & t={...}, const unsigned int file_version=0) Line 81 + 0x11 C++ myDLL.dll!boost::serialization::serialize_adl<boost::archive::binary_oar chive,boost::serialization::nvp<std::basic_string<char,std::char_traits< char>,std::allocator<char> > const > >(boost::archive::binary_oarchive & ar={...}, boost::serialization::nvp<std::basic_string<char,std::char_traits<char>, std::allocator<char> > const > & t={...}, const unsigned int file_version=0) Line 140 + 0x18 C++ myDLL.dll!boost::archive::detail::save_non_pointer_type<boost::archive:: binary_oarchive,boost::serialization::nvp<std::basic_string<char,std::ch ar_traits<char>,std::allocator<char> > const > >::save_only::invoke(boost::archive::binary_oarchive & ar={...}, const boost::serialization::nvp<std::basic_string<char,std::char_traits<char>, std::allocator<char> > const > & t={...}) Line 256 + 0xf C++ myDLL.dll!boost::archive::detail::save_non_pointer_type<boost::archive:: binary_oarchive,boost::serialization::nvp<std::basic_string<char,std::ch ar_traits<char>,std::allocator<char> > const > >::invoke(boost::archive::binary_oarchive & ar={...}, const boost::serialization::nvp<std::basic_string<char,std::char_traits<char>, std::allocator<char> > const > & t={...}) Line 321 + 0xd C++ myDLL.dll!boost::archive::save<boost::archive::binary_oarchive,boost::se rialization::nvp<std::basic_string<char,std::char_traits<char>,std::allo cator<char> > const > >(boost::archive::binary_oarchive & ar={...}, const boost::serialization::nvp<std::basic_string<char,std::char_traits<char>, std::allocator<char> > const > & t={...}) Line 535 + 0xd C++ myDLL.dll!boost::archive::detail::common_oarchive<boost::archive::binary _oarchive>::save_override<boost::serialization::nvp<std::basic_string<ch ar,std::char_traits<char>,std::allocator<char> > const > const >() Line 62 + 0x15 C++ myDLL.dll!boost::archive::basic_binary_oarchive<boost::archive::binary_o archive>::save_override<boost::serialization::nvp<std::basic_string<char ,std::char_traits<char>,std::allocator<char> > const > const >() Line 66 C++ myDLL.dll!boost::archive::binary_oarchive_impl<boost::archive::binary_oa rchive,char,std::char_traits<char> >::save_override<boost::serialization::nvp<std::basic_string<char,std::c har_traits<char>,std::allocator<char> > const > const >() Line 46 C++ myDLL.dll!boost::archive::detail::interface_oarchive<boost::archive::bin ary_oarchive>::operator<<<boost::serialization::nvp<std::basic_string<ch ar,std::char_traits<char>,std::allocator<char> > const > const >() Line 80 C++ myDLL.dll!boost::serialization::stl::save_collection<boost::archive::bin ary_oarchive,std::vector<std::basic_string<char,std::char_traits<char>,s td::allocator<char> >,std::allocator<std::basic_string<char,std::char_traits<char>,std::allo cator<char> > > > >(boost::archive::binary_oarchive & ar={...}, const std::vector<std::basic_string<char,std::char_traits<char>,std::allocator <char> >,std::allocator<std::basic_string<char,std::char_traits<char>,std::allo cator<char> > > > & s={...}) Line 59 C++ myDLL.dll!boost::serialization::save<boost::archive::binary_oarchive,std ::basic_string<char,std::char_traits<char>,std::allocator<char> >,std::allocator<std::basic_string<char,std::char_traits<char>,std::allo cator<char> > > >(boost::archive::binary_oarchive & ar={...}, const std::vector<std::basic_string<char,std::char_traits<char>,std::allocator <char> >,std::allocator<std::basic_string<char,std::char_traits<char>,std::allo cator<char> > > > & t={...}, const unsigned int __formal=0) Line 41 + 0xd C++ myDLL.dll!boost::serialization::free_saver<boost::archive::binary_oarchi ve,std::vector<std::basic_string<char,std::char_traits<char>,std::alloca tor<char> >,std::allocator<std::basic_string<char,std::char_traits<char>,std::allo cator<char> > > > >::invoke(boost::archive::binary_oarchive & ar={...}, const std::vector<std::basic_string<char,std::char_traits<char>,std::allocator <char> >,std::allocator<std::basic_string<char,std::char_traits<char>,std::allo cator<char> > > > & t={...}, const unsigned int file_version=0) Line 45 + 0x18 C++ myDLL.dll!boost::serialization::split_free<boost::archive::binary_oarchi ve,std::vector<std::basic_string<char,std::char_traits<char>,std::alloca tor<char> >,std::allocator<std::basic_string<char,std::char_traits<char>,std::allo cator<char> > > > >(boost::archive::binary_oarchive & ar={...}, std::vector<std::basic_string<char,std::char_traits<char>,std::allocator <char> >,std::allocator<std::basic_string<char,std::char_traits<char>,std::allo cator<char> > > > & t={...}, const unsigned int file_version=0) Line 74 + 0x11 C++ myDLL.dll!boost::serialization::serialize<boost::archive::binary_oarchiv e,std::basic_string<char,std::char_traits<char>,std::allocator<char> >,std::allocator<std::basic_string<char,std::char_traits<char>,std::allo cator<char> > > >(boost::archive::binary_oarchive & ar={...}, std::vector<std::basic_string<char,std::char_traits<char>,std::allocator <char> >,std::allocator<std::basic_string<char,std::char_traits<char>,std::allo cator<char> > > > & t={...}, const unsigned int file_version=0) Line 68 + 0x11 C++ myDLL.dll!boost::serialization::serialize_adl<boost::archive::binary_oar chive,std::vector<std::basic_string<char,std::char_traits<char>,std::all ocator<char> >,std::allocator<std::basic_string<char,std::char_traits<char>,std::allo cator<char> > > > >(boost::archive::binary_oarchive & ar={...}, std::vector<std::basic_string<char,std::char_traits<char>,std::allocator <char> >,std::allocator<std::basic_string<char,std::char_traits<char>,std::allo cator<char> > > > & t={...}, const unsigned int file_version=0) Line 140 + 0x18 C++ myDLL.dll!boost::archive::detail::oserializer<boost::archive::binary_oar chive,std::vector<std::basic_string<char,std::char_traits<char>,std::all ocator<char> >,std::allocator<std::basic_string<char,std::char_traits<char>,std::allo cator<char> > > > >::save_object_data(boost::archive::detail::basic_oarchive & ar={...}, const void * x=0x4da09810) Line 151 + 0x2b C++ boost_serialization-vc71-mt-gd-1_34_1.dll!47f3a2bb() boost_serialization-vc71-mt-gd-1_34_1.dll!47f3aa3e() myDLL.dll!boost::archive::detail::save_non_pointer_type<boost::archive:: binary_oarchive,std::vector<std::basic_string<char,std::char_traits<char >,std::allocator<char> >,std::allocator<std::basic_string<char,std::char_traits<char>,std::allo cator<char> > > > >::save_standard::invoke(boost::archive::binary_oarchive & ar={...}, const std::vector<std::basic_string<char,std::char_traits<char>,std::allocator <char> >,std::allocator<std::basic_string<char,std::char_traits<char>,std::allo cator<char> > > > & t={...}) Line 263 + 0x15 C++ myDLL.dll!boost::archive::detail::save_non_pointer_type<boost::archive:: binary_oarchive,std::vector<std::basic_string<char,std::char_traits<char >,std::allocator<char> >,std::allocator<std::basic_string<char,std::char_traits<char>,std::allo cator<char> > > > >::invoke(boost::archive::binary_oarchive & ar={...}, const std::vector<std::basic_string<char,std::char_traits<char>,std::allocator <char> >,std::allocator<std::basic_string<char,std::char_traits<char>,std::allo cator<char> > > > & t={...}) Line 321 + 0xd C++ myDLL.dll!boost::archive::save<boost::archive::binary_oarchive,std::vect or<std::basic_string<char,std::char_traits<char>,std::allocator<char> >,std::allocator<std::basic_string<char,std::char_traits<char>,std::allo cator<char> > > > >(boost::archive::binary_oarchive & ar={...}, const std::vector<std::basic_string<char,std::char_traits<char>,std::allocator <char> >,std::allocator<std::basic_string<char,std::char_traits<char>,std::allo cator<char> > > > & t={...}) Line 535 + 0xd C++ myDLL.dll!boost::archive::detail::common_oarchive<boost::archive::binary _oarchive>::save_override<std::vector<std::basic_string<char,std::char_t raits<char>,std::allocator<char> >,std::allocator<std::basic_string<char,std::char_traits<char>,std::allo cator<char> > > > const >() Line 62 + 0x15 C++ myDLL.dll!boost::archive::basic_binary_oarchive<boost::archive::binary_o archive>::save_override<std::vector<std::basic_string<char,std::char_tra its<char>,std::allocator<char> >,std::allocator<std::basic_string<char,std::char_traits<char>,std::allo cator<char> > > > const >() Line 66 C++ myDLL.dll!boost::archive::binary_oarchive_impl<boost::archive::binary_oa rchive,char,std::char_traits<char> >::save_override<std::vector<std::basic_string<char,std::char_traits<cha r>,std::allocator<char> >,std::allocator<std::basic_string<char,std::char_traits<char>,std::allo cator<char> > > > const >() Line 46 C++ myDLL.dll!boost::archive::detail::interface_oarchive<boost::archive::bin ary_oarchive>::operator<<<std::vector<std::basic_string<char,std::char_t raits<char>,std::allocator<char> >,std::allocator<std::basic_string<char,std::char_traits<char>,std::allo cator<char> > > > const >() Line 80 C++ myDLL.dll!boost::serialization::nvp<std::vector<std::basic_string<char,s td::char_traits<char>,std::allocator<char> >,std::allocator<std::basic_string<char,std::char_traits<char>,std::allo cator<char> > > > >::save<boost::archive::binary_oarchive>() Line 78 C++ myDLL.dll!boost::serialization::access::member_save<boost::archive::bina ry_oarchive,boost::serialization::nvp<std::vector<std::basic_string<char ,std::char_traits<char>,std::allocator<char> >,std::allocator<std::basic_string<char,std::char_traits<char>,std::allo cator<char> > > > > const >(boost::archive::binary_oarchive & ar={...}, const boost::serialization::nvp<std::vector<std::basic_string<char,std::char_t raits<char>,std::allocator<char> >,std::allocator<std::basic_string<char,std::char_traits<char>,std::allo cator<char> > > > > & t={...}, const unsigned int file_version=0) Line 94 C++ myDLL.dll!boost::serialization::detail::member_saver<boost::archive::bin ary_oarchive,boost::serialization::nvp<std::vector<std::basic_string<cha r,std::char_traits<char>,std::allocator<char> >,std::allocator<std::basic_string<char,std::char_traits<char>,std::allo cator<char> > > > > >::invoke(boost::archive::binary_oarchive & ar={...}, const boost::serialization::nvp<std::vector<std::basic_string<char,std::char_t raits<char>,std::allocator<char> >,std::allocator<std::basic_string<char,std::char_traits<char>,std::allo cator<char> > > > > & t={...}, const unsigned int file_version=0) Line 43 + 0x11 C++ myDLL.dll!boost::serialization::split_member<boost::archive::binary_oarc hive,boost::serialization::nvp<std::vector<std::basic_string<char,std::c har_traits<char>,std::allocator<char> >,std::allocator<std::basic_string<char,std::char_traits<char>,std::allo cator<char> > > > > >(boost::archive::binary_oarchive & ar={...}, boost::serialization::nvp<std::vector<std::basic_string<char,std::char_t raits<char>,std::allocator<char> >,std::allocator<std::basic_string<char,std::char_traits<char>,std::allo cator<char> > > > > & t={...}, const unsigned int file_version=0) Line 69 + 0x11 C++ myDLL.dll!boost::serialization::nvp<std::vector<std::basic_string<char,s td::char_traits<char>,std::allocator<char> >,std::allocator<std::basic_string<char,std::char_traits<char>,std::allo cator<char> > > > >::serialize<boost::archive::binary_oarchive>() Line 87 + 0x34 C++ myDLL.dll!boost::serialization::access::serialize<boost::archive::binary _oarchive,boost::serialization::nvp<std::vector<std::basic_string<char,s td::char_traits<char>,std::allocator<char> >,std::allocator<std::basic_string<char,std::char_traits<char>,std::allo cator<char> > > > > >(boost::archive::binary_oarchive & ar={...}, boost::serialization::nvp<std::vector<std::basic_string<char,std::char_t raits<char>,std::allocator<char> >,std::allocator<std::basic_string<char,std::char_traits<char>,std::allo cator<char> > > > > & t={...}, const unsigned int file_version=0) Line 110 C++ myDLL.dll!boost::serialization::serialize<boost::archive::binary_oarchiv e,boost::serialization::nvp<std::vector<std::basic_string<char,std::char _traits<char>,std::allocator<char> >,std::allocator<std::basic_string<char,std::char_traits<char>,std::allo cator<char> > > > > >(boost::archive::binary_oarchive & ar={...}, boost::serialization::nvp<std::vector<std::basic_string<char,std::char_t raits<char>,std::allocator<char> >,std::allocator<std::basic_string<char,std::char_traits<char>,std::allo cator<char> > > > > & t={...}, const unsigned int file_version=0) Line 81 + 0x11 C++ myDLL.dll!boost::serialization::serialize_adl<boost::archive::binary_oar chive,boost::serialization::nvp<std::vector<std::basic_string<char,std:: char_traits<char>,std::allocator<char> >,std::allocator<std::basic_string<char,std::char_traits<char>,std::allo cator<char> > > > > >(boost::archive::binary_oarchive & ar={...}, boost::serialization::nvp<std::vector<std::basic_string<char,std::char_t raits<char>,std::allocator<char> >,std::allocator<std::basic_string<char,std::char_traits<char>,std::allo cator<char> > > > > & t={...}, const unsigned int file_version=0) Line 140 + 0x18 C++ myDLL.dll!boost::archive::detail::save_non_pointer_type<boost::archive:: binary_oarchive,boost::serialization::nvp<std::vector<std::basic_string< char,std::char_traits<char>,std::allocator<char> >,std::allocator<std::basic_string<char,std::char_traits<char>,std::allo cator<char> > > > > >::save_only::invoke(boost::archive::binary_oarchive & ar={...}, const boost::serialization::nvp<std::vector<std::basic_string<char,std::char_t raits<char>,std::allocator<char> >,std::allocator<std::basic_string<char,std::char_traits<char>,std::allo cator<char> > > > > & t={...}) Line 256 + 0xf C++ myDLL.dll!boost::archive::detail::save_non_pointer_type<boost::archive:: binary_oarchive,boost::serialization::nvp<std::vector<std::basic_string< char,std::char_traits<char>,std::allocator<char> >,std::allocator<std::basic_string<char,std::char_traits<char>,std::allo cator<char> > > > > >::invoke(boost::archive::binary_oarchive & ar={...}, const boost::serialization::nvp<std::vector<std::basic_string<char,std::char_t raits<char>,std::allocator<char> >,std::allocator<std::basic_string<char,std::char_traits<char>,std::allo cator<char> > > > > & t={...}) Line 321 + 0xd C++ myDLL.dll!boost::archive::save<boost::archive::binary_oarchive,boost::se rialization::nvp<std::vector<std::basic_string<char,std::char_traits<cha r>,std::allocator<char> >,std::allocator<std::basic_string<char,std::char_traits<char>,std::allo cator<char> > > > > >(boost::archive::binary_oarchive & ar={...}, const boost::serialization::nvp<std::vector<std::basic_string<char,std::char_t raits<char>,std::allocator<char> >,std::allocator<std::basic_string<char,std::char_traits<char>,std::allo cator<char> > > > > & t={...}) Line 535 + 0xd C++ myDLL.dll!boost::archive::detail::common_oarchive<boost::archive::binary _oarchive>::save_override<boost::serialization::nvp<std::vector<std::bas ic_string<char,std::char_traits<char>,std::allocator<char> >,std::allocator<std::basic_string<char,std::char_traits<char>,std::allo cator<char> > > > > const >() Line 62 + 0x15 C++ myDLL.dll!boost::archive::basic_binary_oarchive<boost::archive::binary_o archive>::save_override<boost::serialization::nvp<std::vector<std::basic _string<char,std::char_traits<char>,std::allocator<char> >,std::allocator<std::basic_string<char,std::char_traits<char>,std::allo cator<char> > > > > const >() Line 66 C++ myDLL.dll!boost::archive::binary_oarchive_impl<boost::archive::binary_oa rchive,char,std::char_traits<char> >::save_override<boost::serialization::nvp<std::vector<std::basic_string <char,std::char_traits<char>,std::allocator<char> >,std::allocator<std::basic_string<char,std::char_traits<char>,std::allo cator<char> > > > > const >() Line 46 C++ myDLL.dll!boost::archive::detail::interface_oarchive<boost::archive::bin ary_oarchive>::operator<<<boost::serialization::nvp<std::vector<std::bas ic_string<char,std::char_traits<char>,std::allocator<char> >,std::allocator<std::basic_string<char,std::char_traits<char>,std::allo cator<char> > > > > const >() Line 80 C++ myDLL.dll!boost::archive::detail::interface_oarchive<boost::archive::bin ary_oarchive>::operator&<boost::serialization::nvp<std::vector<std::basi c_string<char,std::char_traits<char>,std::allocator<char> >,std::allocator<std::basic_string<char,std::char_traits<char>,std::allo cator<char> > > > > const >() Line 91 C++ myDLL.dll!myNS::myComponentClass::serialize<boost::archive::binary_oarch ive>() Line 90 C++ myDLL.dll!boost::serialization::access::serialize<boost::archive::binary _oarchive,myNS::myFunc>(boost::archive::binary_oarchive & ar={...}, myNS::myFunc & t={...}, const unsigned int file_version=0) Line 110 C++ myDLL.dll!boost::serialization::serialize<boost::archive::binary_oarchiv e,myNS::myFunc>(boost::archive::binary_oarchive & ar={...}, myNS::myFunc & t={...}, const unsigned int file_version=0) Line 81 + 0x11 C++ myDLL.dll!boost::serialization::serialize_adl<boost::archive::binary_oar chive,myNS::myFunc>(boost::archive::binary_oarchive & ar={...}, myNS::myFunc & t={...}, const unsigned int file_version=0) Line 140 + 0x18 C++ myDLL.dll!boost::archive::detail::oserializer<boost::archive::binary_oar chive,myNS::myFunc>::save_object_data(boost::archive::detail::basic_oarc hive & ar={...}, const void * x=0x4da097d8) Line 151 + 0x2b C++ boost_serialization-vc71-mt-gd-1_34_1.dll!47f3a1de() boost_serialization-vc71-mt-gd-1_34_1.dll!47f3aa3e() myDLL.dll!boost::archive::detail::save_non_pointer_type<boost::archive:: binary_oarchive,myNS::myFunc>::save_standard::invoke(boost::archive::bin ary_oarchive & ar={...}, const myNS::myFunc & t={...}) Line 263 + 0x15 C++ myDLL.dll!boost::archive::detail::save_non_pointer_type<boost::archive:: binary_oarchive,myNS::myFunc>::invoke(boost::archive::binary_oarchive & ar={...}, const myNS::myFunc & t={...}) Line 321 + 0xd C++ myDLL.dll!boost::archive::save<boost::archive::binary_oarchive,myNS::myF unc>(boost::archive::binary_oarchive & ar={...}, const myNS::myFunc & t={...}) Line 535 + 0xd C++ myDLL.dll!boost::archive::detail::common_oarchive<boost::archive::binary _oarchive>::save_override<myNS::myFunc const >() Line 62 + 0x15 C++ myDLL.dll!boost::archive::basic_binary_oarchive<boost::archive::binary_o archive>::save_override<myNS::myFunc const >() Line 66 C++ myDLL.dll!boost::archive::binary_oarchive_impl<boost::archive::binary_oa rchive,char,std::char_traits<char> >::save_override<myNS::myFunc const >() Line 46 C++ myDLL.dll!boost::archive::detail::interface_oarchive<boost::archive::bin ary_oarchive>::operator<<<myNS::myFunc const >() Line 80 C++ myDLL.dll!boost::serialization::nvp<myNS::myFunc>::save<boost::archive:: binary_oarchive>() Line 78 C++ myDLL.dll!boost::serialization::access::member_save<boost::archive::bina ry_oarchive,boost::serialization::nvp<myNS::myFunc> const >(boost::archive::binary_oarchive & ar={...}, const boost::serialization::nvp<myNS::myFunc> & t={...}, const unsigned int file_version=0) Line 94 C++ myDLL.dll!boost::serialization::detail::member_saver<boost::archive::bin ary_oarchive,boost::serialization::nvp<myNS::myFunc> >::invoke(boost::archive::binary_oarchive & ar={...}, const boost::serialization::nvp<myNS::myFunc> & t={...}, const unsigned int file_version=0) Line 43 + 0x11 C++ myDLL.dll!boost::serialization::split_member<boost::archive::binary_oarc hive,boost::serialization::nvp<myNS::myFunc> >(boost::archive::binary_oarchive & ar={...}, boost::serialization::nvp<myNS::myFunc> & t={...}, const unsigned int file_version=0) Line 69 + 0x11 C++ myDLL.dll!boost::serialization::nvp<myNS::myFunc>::serialize<boost::arch ive::binary_oarchive>() Line 87 + 0x34 C++ myDLL.dll!boost::serialization::access::serialize<boost::archive::binary _oarchive,boost::serialization::nvp<myNS::myFunc> >(boost::archive::binary_oarchive & ar={...}, boost::serialization::nvp<myNS::myFunc> & t={...}, const unsigned int file_version=0) Line 110 C++ myDLL.dll!boost::serialization::serialize<boost::archive::binary_oarchiv e,boost::serialization::nvp<myNS::myFunc> >(boost::archive::binary_oarchive & ar={...}, boost::serialization::nvp<myNS::myFunc> & t={...}, const unsigned int file_version=0) Line 81 + 0x11 C++ myDLL.dll!boost::serialization::serialize_adl<boost::archive::binary_oar chive,boost::serialization::nvp<myNS::myFunc> >(boost::archive::binary_oarchive & ar={...}, boost::serialization::nvp<myNS::myFunc> & t={...}, const unsigned int file_version=0) Line 140 + 0x18 C++ myDLL.dll!boost::archive::detail::save_non_pointer_type<boost::archive:: binary_oarchive,boost::serialization::nvp<myNS::myFunc> >::save_only::invoke(boost::archive::binary_oarchive & ar={...}, const boost::serialization::nvp<myNS::myFunc> & t={...}) Line 256 + 0xf C++ myDLL.dll!boost::archive::detail::save_non_pointer_type<boost::archive:: binary_oarchive,boost::serialization::nvp<myNS::myFunc> >::invoke(boost::archive::binary_oarchive & ar={...}, const boost::serialization::nvp<myNS::myFunc> & t={...}) Line 321 + 0xd C++ myDLL.dll!boost::archive::save<boost::archive::binary_oarchive,boost::se rialization::nvp<myNS::myFunc> >(boost::archive::binary_oarchive & ar={...}, const boost::serialization::nvp<myNS::myFunc> & t={...}) Line 535 + 0xd C++ myDLL.dll!boost::archive::detail::common_oarchive<boost::archive::binary _oarchive>::save_override<boost::serialization::nvp<myNS::myFunc> const >() Line 62 + 0x15 C++ myDLL.dll!boost::archive::basic_binary_oarchive<boost::archive::binary_o archive>::save_override<boost::serialization::nvp<myNS::myFunc> const >() Line 66 C++ myDLL.dll!boost::archive::binary_oarchive_impl<boost::archive::binary_oa rchive,char,std::char_traits<char> >::save_override<boost::serialization::nvp<myNS::myFunc> const >() Line 46 C++ myDLL.dll!boost::archive::detail::interface_oarchive<boost::archive::bin ary_oarchive>::operator<<<boost::serialization::nvp<myNS::myFunc> const >() Line 80 C++ myDLL.dll!boost::archive::detail::pointer_oserializer<myNS::myFunc,boost ::archive::binary_oarchive>::save_object_ptr(boost::archive::detail::bas ic_oarchive & ar={...}, const void * x=0x4da097d8) Line 216 C++ boost_serialization-vc71-mt-gd-1_34_1.dll!47f3a868() boost_serialization-vc71-mt-gd-1_34_1.dll!47f3aa6e() myDLL.dll!boost::archive::detail::save_pointer_type<boost::archive::bina ry_oarchive,myNS::myFunc *>::polymorphic<myNS::myFunc>::save(boost::archive::binary_oarchive & ar={...}, const myNS::myFunc & t={...}, const boost::archive::detail::basic_pointer_oserializer * bpos_ptr=0x48eaf914) Line 401 + 0x13 C++ myDLL.dll!boost::archive::detail::save_pointer_type<boost::archive::bina ry_oarchive,myNS::myFunc *>::save<myNS::myFunc>(boost::archive::binary_oarchive & ar={...}, const myNS::myFunc & t={...}, const boost::archive::detail::basic_pointer_oserializer * bpos_ptr=0x48eaf914) Line 438 + 0x11 C++ myDLL.dll!boost::archive::detail::save_pointer_type<boost::archive::bina ry_oarchive,myNS::myFunc *>::invoke(boost::archive::binary_oarchive & ar={...}, myNS::myFunc * const t=0x4da097d8) Line 466 + 0x11 C++ myDLL.dll!boost::archive::save<boost::archive::binary_oarchive,myNS::myF unc *>(boost::archive::binary_oarchive & ar={...}, myNS::myFunc * const & t=0x4da097d8) Line 535 + 0xf C++ myDLL.dll!boost::archive::detail::common_oarchive<boost::archive::binary _oarchive>::save_override<myNS::myFunc * const>() Line 62 + 0x15 C++ myDLL.dll!boost::archive::basic_binary_oarchive<boost::archive::binary_o archive>::save_override<myNS::myFunc * const>() Line 66 C++ myDLL.dll!boost::archive::binary_oarchive_impl<boost::archive::binary_oa rchive,char,std::char_traits<char> >::save_override<myNS::myFunc * const>() Line 46 C++ myDLL.dll!boost::archive::detail::interface_oarchive<boost::archive::bin ary_oarchive>::operator<<<myNS::myFunc * const>() Line 80 C++ myDLL.dll!boost::serialization::nvp<myNS::myFunc *>::save<boost::archive::binary_oarchive>() Line 78 C++ myDLL.dll!boost::serialization::access::member_save<boost::archive::bina ry_oarchive,boost::serialization::nvp<myNS::myFunc *> const >(boost::archive::binary_oarchive & ar={...}, const boost::serialization::nvp<myNS::myFunc *> & t={...}, const unsigned int file_version=0) Line 94 C++ myDLL.dll!boost::serialization::detail::member_saver<boost::archive::bin ary_oarchive,boost::serialization::nvp<myNS::myFunc *> >::invoke(boost::archive::binary_oarchive & ar={...}, const boost::serialization::nvp<myNS::myFunc *> & t={...}, const unsigned int file_version=0) Line 43 + 0x11 C++ myDLL.dll!boost::serialization::split_member<boost::archive::binary_oarc hive,boost::serialization::nvp<myNS::myFunc *> >(boost::archive::binary_oarchive & ar={...}, boost::serialization::nvp<myNS::myFunc *> & t={...}, const unsigned int file_version=0) Line 69 + 0x11 C++ myDLL.dll!boost::serialization::nvp<myNS::myFunc *>::serialize<boost::archive::binary_oarchive>() Line 87 + 0x34 C++ myDLL.dll!boost::serialization::access::serialize<boost::archive::binary _oarchive,boost::serialization::nvp<myNS::myFunc *> >(boost::archive::binary_oarchive & ar={...}, boost::serialization::nvp<myNS::myFunc *> & t={...}, const unsigned int file_version=0) Line 110 C++ myDLL.dll!boost::serialization::serialize<boost::archive::binary_oarchiv e,boost::serialization::nvp<myNS::myFunc *> >(boost::archive::binary_oarchive & ar={...}, boost::serialization::nvp<myNS::myFunc *> & t={...}, const unsigned int file_version=0) Line 81 + 0x11 C++ myDLL.dll!boost::serialization::serialize_adl<boost::archive::binary_oar chive,boost::serialization::nvp<myNS::myFunc *> >(boost::archive::binary_oarchive & ar={...}, boost::serialization::nvp<myNS::myFunc *> & t={...}, const unsigned int file_version=0) Line 140 + 0x18 C++ myDLL.dll!boost::archive::detail::save_non_pointer_type<boost::archive:: binary_oarchive,boost::serialization::nvp<myNS::myFunc *> >::save_only::invoke(boost::archive::binary_oarchive & ar={...}, const boost::serialization::nvp<myNS::myFunc *> & t={...}) Line 256 + 0xf C++ myDLL.dll!boost::archive::detail::save_non_pointer_type<boost::archive:: binary_oarchive,boost::serialization::nvp<myNS::myFunc *> >::invoke(boost::archive::binary_oarchive & ar={...}, const boost::serialization::nvp<myNS::myFunc *> & t={...}) Line 321 + 0xd C++ myDLL.dll!boost::archive::save<boost::archive::binary_oarchive,boost::se rialization::nvp<myNS::myFunc *> >(boost::archive::binary_oarchive & ar={...}, const boost::serialization::nvp<myNS::myFunc *> & t={...}) Line 535 + 0xd C++ myDLL.dll!boost::archive::detail::common_oarchive<boost::archive::binary _oarchive>::save_override<boost::serialization::nvp<myNS::myFunc *> const >() Line 62 + 0x15 C++ myDLL.dll!boost::archive::basic_binary_oarchive<boost::archive::binary_o archive>::save_override<boost::serialization::nvp<myNS::myFunc *> const >() Line 66 C++ myDLL.dll!boost::archive::binary_oarchive_impl<boost::archive::binary_oa rchive,char,std::char_traits<char> >::save_override<boost::serialization::nvp<myNS::myFunc *> const >() Line 46 C++ myDLL.dll!boost::archive::detail::interface_oarchive<boost::archive::bin ary_oarchive>::operator<<<boost::serialization::nvp<myNS::myFunc *> const >() Line 80 C++ myDLL.dll!boost::archive::detail::interface_oarchive<boost::archive::bin ary_oarchive>::operator&<boost::serialization::nvp<myNS::myFunc *> const >() Line 91 C++ myDLL.dll!boost::serialization::serialize<boost::archive::binary_oarchiv e,myNS::Date const ,myNS::myFunc *>(boost::archive::binary_oarchive & ar={...}, std::pair<myNS::Date const ,myNS::myFunc *> & p={...}, const unsigned int __formal=0) Line 42 C++ myDLL.dll!boost::serialization::serialize_adl<boost::archive::binary_oar chive,std::pair<myNS::Date const ,myNS::myFunc *> >(boost::archive::binary_oarchive & ar={...}, std::pair<myNS::Date const ,myNS::myFunc *> & t={...}, const unsigned int file_version=0) Line 140 + 0x18 C++ myDLL.dll!boost::archive::detail::oserializer<boost::archive::binary_oar chive,std::pair<myNS::Date const ,myNS::myFunc *> >::save_object_data(boost::archive::detail::basic_oarchive & ar={...}, const void * x=0x4da28df4) Line 151 + 0x2b C++ boost_serialization-vc71-mt-gd-1_34_1.dll!47f3a2bb() boost_serialization-vc71-mt-gd-1_34_1.dll!47f3aa3e() myDLL.dll!boost::archive::detail::save_non_pointer_type<boost::archive:: binary_oarchive,std::pair<myNS::Date const ,myNS::myFunc *> >::save_standard::invoke(boost::archive::binary_oarchive & ar={...}, const std::pair<myNS::Date const ,myNS::myFunc *> & t={...}) Line 263 + 0x15 C++ myDLL.dll!boost::archive::detail::save_non_pointer_type<boost::archive:: binary_oarchive,std::pair<myNS::Date const ,myNS::myFunc *> >::invoke(boost::archive::binary_oarchive & ar={...}, const std::pair<myNS::Date const ,myNS::myFunc *> & t={...}) Line 321 + 0xd C++ myDLL.dll!boost::archive::save<boost::archive::binary_oarchive,std::pair <myNS::Date const ,myNS::myFunc *> >(boost::archive::binary_oarchive & ar={...}, const std::pair<myNS::Date const ,myNS::myFunc *> & t={...}) Line 535 + 0xd C++ myDLL.dll!boost::archive::detail::common_oarchive<boost::archive::binary _oarchive>::save_override<std::pair<myNS::Date const ,myNS::myFunc *> const >() Line 62 + 0x15 C++ myDLL.dll!boost::archive::basic_binary_oarchive<boost::archive::binary_o archive>::save_override<std::pair<myNS::Date const ,myNS::myFunc *> const >() Line 66 C++ myDLL.dll!boost::archive::binary_oarchive_impl<boost::archive::binary_oa rchive,char,std::char_traits<char> >::save_override<std::pair<myNS::Date const ,myNS::myFunc *> const >() Line 46 C++ myDLL.dll!boost::archive::detail::interface_oarchive<boost::archive::bin ary_oarchive>::operator<<<std::pair<myNS::Date const ,myNS::myFunc *> const >() Line 80 C++ myDLL.dll!boost::serialization::nvp<std::pair<myNS::Date const ,myNS::myFunc *> const >::save<boost::archive::binary_oarchive>() Line 78 C++ myDLL.dll!boost::serialization::access::member_save<boost::archive::bina ry_oarchive,boost::serialization::nvp<std::pair<myNS::Date const ,myNS::myFunc *> const > const >(boost::archive::binary_oarchive & ar={...}, const boost::serialization::nvp<std::pair<myNS::Date const ,myNS::myFunc *> const > & t={...}, const unsigned int file_version=0) Line 94 C++ myDLL.dll!boost::serialization::detail::member_saver<boost::archive::bin ary_oarchive,boost::serialization::nvp<std::pair<myNS::Date const ,myNS::myFunc *> const > >::invoke(boost::archive::binary_oarchive & ar={...}, const boost::serialization::nvp<std::pair<myNS::Date const ,myNS::myFunc *> const > & t={...}, const unsigned int file_version=0) Line 43 + 0x11 C++ myDLL.dll!boost::serialization::split_member<boost::archive::binary_oarc hive,boost::serialization::nvp<std::pair<myNS::Date const ,myNS::myFunc *> const > >(boost::archive::binary_oarchive & ar={...}, boost::serialization::nvp<std::pair<myNS::Date const ,myNS::myFunc *> const > & t={...}, const unsigned int file_version=0) Line 69 + 0x11 C++ myDLL.dll!boost::serialization::nvp<std::pair<myNS::Date const ,myNS::myFunc *> const >::serialize<boost::archive::binary_oarchive>() Line 87 + 0x34 C++ myDLL.dll!boost::serialization::access::serialize<boost::archive::binary _oarchive,boost::serialization::nvp<std::pair<myNS::Date const ,myNS::myFunc *> const > >(boost::archive::binary_oarchive & ar={...}, boost::serialization::nvp<std::pair<myNS::Date const ,myNS::myFunc *> const > & t={...}, const unsigned int file_version=0) Line 110 C++ myDLL.dll!boost::serialization::serialize<boost::archive::binary_oarchiv e,boost::serialization::nvp<std::pair<myNS::Date const ,myNS::myFunc *> const > >(boost::archive::binary_oarchive & ar={...}, boost::serialization::nvp<std::pair<myNS::Date const ,myNS::myFunc *> const > & t={...}, const unsigned int file_version=0) Line 81 + 0x11 C++ myDLL.dll!boost::serialization::serialize_adl<boost::archive::binary_oar chive,boost::serialization::nvp<std::pair<myNS::Date const ,myNS::myFunc *> const > >(boost::archive::binary_oarchive & ar={...}, boost::serialization::nvp<std::pair<myNS::Date const ,myNS::myFunc *> const > & t={...}, const unsigned int file_version=0) Line 140 + 0x18 C++ myDLL.dll!boost::archive::detail::save_non_pointer_type<boost::archive:: binary_oarchive,boost::serialization::nvp<std::pair<myNS::Date const ,myNS::myFunc *> const > >::save_only::invoke(boost::archive::binary_oarchive & ar={...}, const boost::serialization::nvp<std::pair<myNS::Date const ,myNS::myFunc *> const > & t={...}) Line 256 + 0xf C++ myDLL.dll!boost::archive::detail::save_non_pointer_type<boost::archive:: binary_oarchive,boost::serialization::nvp<std::pair<myNS::Date const ,myNS::myFunc *> const > >::invoke(boost::archive::binary_oarchive & ar={...}, const boost::serialization::nvp<std::pair<myNS::Date const ,myNS::myFunc *> const > & t={...}) Line 321 + 0xd C++ myDLL.dll!boost::archive::save<boost::archive::binary_oarchive,boost::se rialization::nvp<std::pair<myNS::Date const ,myNS::myFunc *> const > >(boost::archive::binary_oarchive & ar={...}, const boost::serialization::nvp<std::pair<myNS::Date const ,myNS::myFunc *> const > & t={...}) Line 535 + 0xd C++ myDLL.dll!boost::archive::detail::common_oarchive<boost::archive::binary _oarchive>::save_override<boost::serialization::nvp<std::pair<myNS::Date const ,myNS::myFunc *> const > const >() Line 62 + 0x15 C++ myDLL.dll!boost::archive::basic_binary_oarchive<boost::archive::binary_o archive>::save_override<boost::serialization::nvp<std::pair<myNS::Date const ,myNS::myFunc *> const > const >() Line 66 C++ myDLL.dll!boost::archive::binary_oarchive_impl<boost::archive::binary_oa rchive,char,std::char_traits<char> >::save_override<boost::serialization::nvp<std::pair<myNS::Date const ,myNS::myFunc *> const > const >() Line 46 C++ myDLL.dll!boost::archive::detail::interface_oarchive<boost::archive::bin ary_oarchive>::operator<<<boost::serialization::nvp<std::pair<myNS::Date const ,myNS::myFunc *> const > const >() Line 80 C++ myDLL.dll!boost::serialization::stl::save_collection<boost::archive::bin ary_oarchive,std::map<myNS::Date,myNS::myFunc *,std::less<myNS::Date>,std::allocator<std::pair<myNS::Date const ,myNS::myFunc *> > > >(boost::archive::binary_oarchive & ar={...}, const std::map<myNS::Date,myNS::myFunc *,std::less<myNS::Date>,std::allocator<std::pair<myNS::Date const ,myNS::myFunc *> > > & s={...}) Line 59 C++ myDLL.dll!boost::serialization::save<boost::archive::binary_oarchive,myN S::myFunc *,myNS::Date,std::less<myNS::Date>,std::allocator<std::pair<myNS::Date const ,myNS::myFunc *> > >(boost::archive::binary_oarchive & ar={...}, const std::map<myNS::Date,myNS::myFunc *,std::less<myNS::Date>,std::allocator<std::pair<myNS::Date const ,myNS::myFunc *> > > & t={...}, const unsigned int __formal=0) Line 41 + 0xd C++ myDLL.dll!boost::serialization::free_saver<boost::archive::binary_oarchi ve,std::map<myNS::Date,myNS::myFunc *,std::less<myNS::Date>,std::allocator<std::pair<myNS::Date const ,myNS::myFunc *> > > >::invoke(boost::archive::binary_oarchive & ar={...}, const std::map<myNS::Date,myNS::myFunc *,std::less<myNS::Date>,std::allocator<std::pair<myNS::Date const ,myNS::myFunc *> > > & t={...}, const unsigned int file_version=0) Line 45 + 0x18 C++ myDLL.dll!boost::serialization::split_free<boost::archive::binary_oarchi ve,std::map<myNS::Date,myNS::myFunc *,std::less<myNS::Date>,std::allocator<std::pair<myNS::Date const ,myNS::myFunc *> > > >(boost::archive::binary_oarchive & ar={...}, std::map<myNS::Date,myNS::myFunc *,std::less<myNS::Date>,std::allocator<std::pair<myNS::Date const ,myNS::myFunc *> > > & t={...}, const unsigned int file_version=0) Line 74 + 0x11 C++ myDLL.dll!boost::serialization::serialize<boost::archive::binary_oarchiv e,myNS::myFunc *,myNS::Date,std::less<myNS::Date>,std::allocator<std::pair<myNS::Date const ,myNS::myFunc *> > >(boost::archive::binary_oarchive & ar={...}, std::map<myNS::Date,myNS::myFunc *,std::less<myNS::Date>,std::allocator<std::pair<myNS::Date const ,myNS::myFunc *> > > & t={...}, const unsigned int file_version=0) Line 70 + 0x11 C++ myDLL.dll!boost::serialization::serialize_adl<boost::archive::binary_oar chive,std::map<myNS::Date,myNS::myFunc *,std::less<myNS::Date>,std::allocator<std::pair<myNS::Date const ,myNS::myFunc *> > > >(boost::archive::binary_oarchive & ar={...}, std::map<myNS::Date,myNS::myFunc *,std::less<myNS::Date>,std::allocator<std::pair<myNS::Date const ,myNS::myFunc *> > > & t={...}, const unsigned int file_version=0) Line 140 + 0x18 C++ myDLL.dll!boost::archive::detail::oserializer<boost::archive::binary_oar chive,std::map<myNS::Date,myNS::myFunc *,std::less<myNS::Date>,std::allocator<std::pair<myNS::Date const ,myNS::myFunc *> > > >::save_object_data(boost::archive::detail::basic_oarchive & ar={...}, const void * x=0x4d808784) Line 151 + 0x2b C++ boost_serialization-vc71-mt-gd-1_34_1.dll!47f3a2bb() boost_serialization-vc71-mt-gd-1_34_1.dll!47f3aa3e() myDLL.dll!boost::archive::detail::save_non_pointer_type<boost::archive:: binary_oarchive,std::map<myNS::Date,myNS::myFunc *,std::less<myNS::Date>,std::allocator<std::pair<myNS::Date const ,myNS::myFunc *> > > >::save_standard::invoke(boost::archive::binary_oarchive & ar={...}, const std::map<myNS::Date,myNS::myFunc *,std::less<myNS::Date>,std::allocator<std::pair<myNS::Date const ,myNS::myFunc *> > > & t={...}) Line 263 + 0x15 C++ myDLL.dll!boost::archive::detail::save_non_pointer_type<boost::archive:: binary_oarchive,std::map<myNS::Date,myNS::myFunc *,std::less<myNS::Date>,std::allocator<std::pair<myNS::Date const ,myNS::myFunc *> > > >::invoke(boost::archive::binary_oarchive & ar={...}, const std::map<myNS::Date,myNS::myFunc *,std::less<myNS::Date>,std::allocator<std::pair<myNS::Date const ,myNS::myFunc *> > > & t={...}) Line 321 + 0xd C++ myDLL.dll!boost::archive::save<boost::archive::binary_oarchive,std::map< myNS::Date,myNS::myFunc *,std::less<myNS::Date>,std::allocator<std::pair<myNS::Date const ,myNS::myFunc *> > > >(boost::archive::binary_oarchive & ar={...}, const std::map<myNS::Date,myNS::myFunc *,std::less<myNS::Date>,std::allocator<std::pair<myNS::Date const ,myNS::myFunc *> > > & t={...}) Line 535 + 0xd C++ myDLL.dll!boost::archive::detail::common_oarchive<boost::archive::binary _oarchive>::save_override<std::map<myNS::Date,myNS::myFunc *,std::less<myNS::Date>,std::allocator<std::pair<myNS::Date const ,myNS::myFunc *> > > const >() Line 62 + 0x15 C++ myDLL.dll!boost::archive::basic_binary_oarchive<boost::archive::binary_o archive>::save_override<std::map<myNS::Date,myNS::myFunc *,std::less<myNS::Date>,std::allocator<std::pair<myNS::Date const ,myNS::myFunc *> > > const >() Line 66 C++ myDLL.dll!boost::archive::binary_oarchive_impl<boost::archive::binary_oa rchive,char,std::char_traits<char> >::save_override<std::map<myNS::Date,myNS::myFunc *,std::less<myNS::Date>,std::allocator<std::pair<myNS::Date const ,myNS::myFunc *> > > const >() Line 46 C++ myDLL.dll!boost::archive::detail::interface_oarchive<boost::archive::bin ary_oarchive>::operator<<<std::map<myNS::Date,myNS::myFunc *,std::less<myNS::Date>,std::allocator<std::pair<myNS::Date const ,myNS::myFunc *> > > const >() Line 80 C++ myDLL.dll!boost::serialization::nvp<std::map<myNS::Date,myNS::myFunc *,std::less<myNS::Date>,std::allocator<std::pair<myNS::Date const ,myNS::myFunc *> > > >::save<boost::archive::binary_oarchive>() Line 78 C++ myDLL.dll!boost::serialization::access::member_save<boost::archive::bina ry_oarchive,boost::serialization::nvp<std::map<myNS::Date,myNS::myFunc *,std::less<myNS::Date>,std::allocator<std::pair<myNS::Date const ,myNS::myFunc *> > > > const >(boost::archive::binary_oarchive & ar={...}, const boost::serialization::nvp<std::map<myNS::Date,myNS::myFunc *,std::less<myNS::Date>,std::allocator<std::pair<myNS::Date const ,myNS::myFunc *> > > > & t={...}, const unsigned int file_version=0) Line 94 C++ myDLL.dll!boost::serialization::detail::member_saver<boost::archive::bin ary_oarchive,boost::serialization::nvp<std::map<myNS::Date,myNS::myFunc *,std::less<myNS::Date>,std::allocator<std::pair<myNS::Date const ,myNS::myFunc *> > > > >::invoke(boost::archive::binary_oarchive & ar={...}, const boost::serialization::nvp<std::map<myNS::Date,myNS::myFunc *,std::less<myNS::Date>,std::allocator<std::pair<myNS::Date const ,myNS::myFunc *> > > > & t={...}, const unsigned int file_version=0) Line 43 + 0x11 C++ myDLL.dll!boost::serialization::split_member<boost::archive::binary_oarc hive,boost::serialization::nvp<std::map<myNS::Date,myNS::myFunc *,std::less<myNS::Date>,std::allocator<std::pair<myNS::Date const ,myNS::myFunc *> > > > >(boost::archive::binary_oarchive & ar={...}, boost::serialization::nvp<std::map<myNS::Date,myNS::myFunc *,std::less<myNS::Date>,std::allocator<std::pair<myNS::Date const ,myNS::myFunc *> > > > & t={...}, const unsigned int file_version=0) Line 69 + 0x11 C++ myDLL.dll!boost::serialization::nvp<std::map<myNS::Date,myNS::myFunc *,std::less<myNS::Date>,std::allocator<std::pair<myNS::Date const ,myNS::myFunc *> > > >::serialize<boost::archive::binary_oarchive>() Line 87 + 0x34 C++ myDLL.dll!boost::serialization::access::serialize<boost::archive::binary _oarchive,boost::serialization::nvp<std::map<myNS::Date,myNS::myFunc *,std::less<myNS::Date>,std::allocator<std::pair<myNS::Date const ,myNS::myFunc *> > > > >(boost::archive::binary_oarchive & ar={...}, boost::serialization::nvp<std::map<myNS::Date,myNS::myFunc *,std::less<myNS::Date>,std::allocator<std::pair<myNS::Date const ,myNS::myFunc *> > > > & t={...}, const unsigned int file_version=0) Line 110 C++ myDLL.dll!boost::serialization::serialize<boost::archive::binary_oarchiv e,boost::serialization::nvp<std::map<myNS::Date,myNS::myFunc *,std::less<myNS::Date>,std::allocator<std::pair<myNS::Date const ,myNS::myFunc *> > > > >(boost::archive::binary_oarchive & ar={...}, boost::serialization::nvp<std::map<myNS::Date,myNS::myFunc *,std::less<myNS::Date>,std::allocator<std::pair<myNS::Date const ,myNS::myFunc *> > > > & t={...}, const unsigned int file_version=0) Line 81 + 0x11 C++ myDLL.dll!boost::serialization::serialize_adl<boost::archive::binary_oar chive,boost::serialization::nvp<std::map<myNS::Date,myNS::myFunc *,std::less<myNS::Date>,std::allocator<std::pair<myNS::Date const ,myNS::myFunc *> > > > >(boost::archive::binary_oarchive & ar={...}, boost::serialization::nvp<std::map<myNS::Date,myNS::myFunc *,std::less<myNS::Date>,std::allocator<std::pair<myNS::Date const ,myNS::myFunc *> > > > & t={...}, const unsigned int file_version=0) Line 140 + 0x18 C++ myDLL.dll!boost::archive::detail::save_non_pointer_type<boost::archive:: binary_oarchive,boost::serialization::nvp<std::map<myNS::Date,myNS::myFu nc *,std::less<myNS::Date>,std::allocator<std::pair<myNS::Date const ,myNS::myFunc *> > > > >::save_only::invoke(boost::archive::binary_oarchive & ar={...}, const boost::serialization::nvp<std::map<myNS::Date,myNS::myFunc *,std::less<myNS::Date>,std::allocator<std::pair<myNS::Date const ,myNS::myFunc *> > > > & t={...}) Line 256 + 0xf C++ myDLL.dll!boost::archive::detail::save_non_pointer_type<boost::archive:: binary_oarchive,boost::serialization::nvp<std::map<myNS::Date,myNS::myFu nc *,std::less<myNS::Date>,std::allocator<std::pair<myNS::Date const ,myNS::myFunc *> > > > >::invoke(boost::archive::binary_oarchive & ar={...}, const boost::serialization::nvp<std::map<myNS::Date,myNS::myFunc *,std::less<myNS::Date>,std::allocator<std::pair<myNS::Date const ,myNS::myFunc *> > > > & t={...}) Line 321 + 0xd C++ myDLL.dll!boost::archive::save<boost::archive::binary_oarchive,boost::se rialization::nvp<std::map<myNS::Date,myNS::myFunc *,std::less<myNS::Date>,std::allocator<std::pair<myNS::Date const ,myNS::myFunc *> > > > >(boost::archive::binary_oarchive & ar={...}, const boost::serialization::nvp<std::map<myNS::Date,myNS::myFunc *,std::less<myNS::Date>,std::allocator<std::pair<myNS::Date const ,myNS::myFunc *> > > > & t={...}) Line 535 + 0xd C++ myDLL.dll!boost::archive::detail::common_oarchive<boost::archive::binary _oarchive>::save_override<boost::serialization::nvp<std::map<myNS::Date, myNS::myFunc *,std::less<myNS::Date>,std::allocator<std::pair<myNS::Date const ,myNS::myFunc *> > > > const >() Line 62 + 0x15 C++ myDLL.dll!boost::archive::basic_binary_oarchive<boost::archive::binary_o archive>::save_override<boost::serialization::nvp<std::map<myNS::Date,my NS::myFunc *,std::less<myNS::Date>,std::allocator<std::pair<myNS::Date const ,myNS::myFunc *> > > > const >() Line 66 C++ myDLL.dll!boost::archive::binary_oarchive_impl<boost::archive::binary_oa rchive,char,std::char_traits<char> >::save_override<boost::serialization::nvp<std::map<myNS::Date,myNS::myF unc *,std::less<myNS::Date>,std::allocator<std::pair<myNS::Date const ,myNS::myFunc *> > > > const >() Line 46 C++ myDLL.dll!boost::archive::detail::interface_oarchive<boost::archive::bin ary_oarchive>::operator<<<boost::serialization::nvp<std::map<myNS::Date, myNS::myFunc *,std::less<myNS::Date>,std::allocator<std::pair<myNS::Date const ,myNS::myFunc *> > > > const >() Line 80 C++ myDLL.dll!boost::archive::detail::interface_oarchive<boost::archive::bin ary_oarchive>::operator&<boost::serialization::nvp<std::map<myNS::Date,m yNS::myFunc *,std::less<myNS::Date>,std::allocator<std::pair<myNS::Date const ,myNS::myFunc *> > > > const >() Line 91 C++ myDLL.dll!myNS::myClass::serialize<boost::archive::binary_oarchive>() Line 68 C++ myDLL.dll!boost::serialization::access::serialize<boost::archive::binary _oarchive,myNS::myClass>(boost::archive::binary_oarchive & ar={...}, myNS::myClass & t={...}, const unsigned int file_version=0) Line 110 C++ myDLL.dll!boost::serialization::serialize<boost::archive::binary_oarchiv e,myNS::myClass>(boost::archive::binary_oarchive & ar={...}, myNS::myClass & t={...}, const unsigned int file_version=0) Line 81 + 0x11 C++ myDLL.dll!boost::serialization::serialize_adl<boost::archive::binary_oar chive,myNS::myClass>(boost::archive::binary_oarchive & ar={...}, myNS::myClass & t={...}, const unsigned int file_version=0) Line 140 + 0x18 C++ myDLL.dll!boost::archive::detail::oserializer<boost::archive::binary_oar chive,myNS::myClass>::save_object_data(boost::archive::detail::basic_oar chive & ar={...}, const void * x=0x4d808780) Line 151 + 0x2b C++ boost_serialization-vc71-mt-gd-1_34_1.dll!47f3a1de() boost_serialization-vc71-mt-gd-1_34_1.dll!47f3aa3e() myDLL.dll!boost::archive::detail::save_non_pointer_type<boost::archive:: binary_oarchive,myNS::myClass>::save_standard::invoke(boost::archive::bi nary_oarchive & ar={...}, const myNS::myClass & t={...}) Line 263 + 0x15 C++ myDLL.dll!boost::archive::detail::save_non_pointer_type<boost::archive:: binary_oarchive,myNS::myClass>::invoke(boost::archive::binary_oarchive & ar={...}, const myNS::myClass & t={...}) Line 321 + 0xd C++ myDLL.dll!boost::archive::save<boost::archive::binary_oarchive,myNS::myC lass>(boost::archive::binary_oarchive & ar={...}, const myNS::myClass & t={...}) Line 535 + 0xd C++ myDLL.dll!boost::archive::detail::common_oarchive<boost::archive::binary _oarchive>::save_override<myNS::myClass const >() Line 62 + 0x15 C++ myDLL.dll!boost::archive::basic_binary_oarchive<boost::archive::binary_o archive>::save_override<myNS::myClass const >() Line 66 C++ myDLL.dll!boost::archive::binary_oarchive_impl<boost::archive::binary_oa rchive,char,std::char_traits<char> >::save_override<myNS::myClass const >() Line 46 C++ myDLL.dll!boost::archive::detail::interface_oarchive<boost::archive::bin ary_oarchive>::operator<<<myNS::myClass const >() Line 80 C++ myDLL.dll!boost::serialization::nvp<myNS::myClass>::save<boost::archive: :binary_oarchive>() Line 78 C++ myDLL.dll!boost::serialization::access::member_save<boost::archive::bina ry_oarchive,boost::serialization::nvp<myNS::myClass> const >(boost::archive::binary_oarchive & ar={...}, const boost::serialization::nvp<myNS::myClass> & t={...}, const unsigned int file_version=0) Line 94 C++ myDLL.dll!boost::serialization::detail::member_saver<boost::archive::bin ary_oarchive,boost::serialization::nvp<myNS::myClass> >::invoke(boost::archive::binary_oarchive & ar={...}, const boost::serialization::nvp<myNS::myClass> & t={...}, const unsigned int file_version=0) Line 43 + 0x11 C++ myDLL.dll!boost::serialization::split_member<boost::archive::binary_oarc hive,boost::serialization::nvp<myNS::myClass> >(boost::archive::binary_oarchive & ar={...}, boost::serialization::nvp<myNS::myClass> & t={...}, const unsigned int file_version=0) Line 69 + 0x11 C++ myDLL.dll!boost::serialization::nvp<myNS::myClass>::serialize<boost::arc hive::binary_oarchive>() Line 87 + 0x34 C++ myDLL.dll!boost::serialization::access::serialize<boost::archive::binary _oarchive,boost::serialization::nvp<myNS::myClass> >(boost::archive::binary_oarchive & ar={...}, boost::serialization::nvp<myNS::myClass> & t={...}, const unsigned int file_version=0) Line 110 C++ myDLL.dll!boost::serialization::serialize<boost::archive::binary_oarchiv e,boost::serialization::nvp<myNS::myClass> >(boost::archive::binary_oarchive & ar={...}, boost::serialization::nvp<myNS::myClass> & t={...}, const unsigned int file_version=0) Line 81 + 0x11 C++ myDLL.dll!boost::serialization::serialize_adl<boost::archive::binary_oar chive,boost::serialization::nvp<myNS::myClass> >(boost::archive::binary_oarchive & ar={...}, boost::serialization::nvp<myNS::myClass> & t={...}, const unsigned int file_version=0) Line 140 + 0x18 C++ myDLL.dll!boost::archive::detail::save_non_pointer_type<boost::archive:: binary_oarchive,boost::serialization::nvp<myNS::myClass> >::save_only::invoke(boost::archive::binary_oarchive & ar={...}, const boost::serialization::nvp<myNS::myClass> & t={...}) Line 256 + 0xf C++ myDLL.dll!boost::archive::detail::save_non_pointer_type<boost::archive:: binary_oarchive,boost::serialization::nvp<myNS::myClass> >::invoke(boost::archive::binary_oarchive & ar={...}, const boost::serialization::nvp<myNS::myClass> & t={...}) Line 321 + 0xd C++ myDLL.dll!boost::archive::save<boost::archive::binary_oarchive,boost::se rialization::nvp<myNS::myClass> >(boost::archive::binary_oarchive & ar={...}, const boost::serialization::nvp<myNS::myClass> & t={...}) Line 535 + 0xd C++ myDLL.dll!boost::archive::detail::common_oarchive<boost::archive::binary _oarchive>::save_override<boost::serialization::nvp<myNS::myClass> const >() Line 62 + 0x15 C++ myDLL.dll!boost::archive::basic_binary_oarchive<boost::archive::binary_o archive>::save_override<boost::serialization::nvp<myNS::myClass> const >() Line 66 C++ myDLL.dll!boost::archive::binary_oarchive_impl<boost::archive::binary_oa rchive,char,std::char_traits<char> >::save_override<boost::serialization::nvp<myNS::myClass> const >() Line 46 C++ myDLL.dll!boost::archive::detail::interface_oarchive<boost::archive::bin ary_oarchive>::operator<<<boost::serialization::nvp<myNS::myClass> const >() Line 80 C++ myDLL.dll!boost::archive::detail::pointer_oserializer<myNS::myClass,boos t::archive::binary_oarchive>::save_object_ptr(boost::archive::detail::ba sic_oarchive & ar={...}, const void * x=0x4d808780) Line 216 C++ boost_serialization-vc71-mt-gd-1_34_1.dll!47f3a868() boost_serialization-vc71-mt-gd-1_34_1.dll!47f3aa6e() myDLL.dll!boost::archive::detail::save_pointer_type<boost::archive::bina ry_oarchive,myNS::myClass const *>::polymorphic<myNS::myClass>::save(boost::archive::binary_oarchive & ar={...}, const myNS::myClass & t={...}, const boost::archive::detail::basic_pointer_oserializer * bpos_ptr=0x48eaf3c0) Line 401 + 0x13 C++ myDLL.dll!boost::archive::detail::save_pointer_type<boost::archive::bina ry_oarchive,myNS::myClass const *>::save<myNS::myClass>(boost::archive::binary_oarchive & ar={...}, const myNS::myClass & t={...}, const boost::archive::detail::basic_pointer_oserializer * bpos_ptr=0x48eaf3c0) Line 438 + 0x11 C++ myDLL.dll!boost::archive::detail::save_pointer_type<boost::archive::bina ry_oarchive,myNS::myClass const *>::invoke(boost::archive::binary_oarchive & ar={...}, const myNS::myClass * const t=0x4d808780) Line 466 + 0x11 C++ myDLL.dll!boost::archive::save<boost::archive::binary_oarchive,myNS::myC lass const *>(boost::archive::binary_oarchive & ar={...}, const myNS::myClass * const & t=0x4d808780) Line 535 + 0xf C++ myDLL.dll!boost::archive::detail::common_oarchive<boost::archive::binary _oarchive>::save_override<myNS::myClass const * const>() Line 62 + 0x15 C++ myDLL.dll!boost::archive::basic_binary_oarchive<boost::archive::binary_o archive>::save_override<myNS::myClass const * const>() Line 66 C++ myDLL.dll!boost::archive::binary_oarchive_impl<boost::archive::binary_oa rchive,char,std::char_traits<char> >::save_override<myNS::myClass const * const>() Line 46 C++ myDLL.dll!boost::archive::detail::interface_oarchive<boost::archive::bin ary_oarchive>::operator<<<myNS::myClass const * const>() Line 80 C++ myDLL.dll!boost::serialization::nvp<myNS::myClass const *>::save<boost::archive::binary_oarchive>() Line 78 C++ myDLL.dll!boost::serialization::access::member_save<boost::archive::bina ry_oarchive,boost::serialization::nvp<myNS::myClass const *> const >(boost::archive::binary_oarchive & ar={...}, const boost::serialization::nvp<myNS::myClass const *> & t={...}, const unsigned int file_version=0) Line 94 C++ myDLL.dll!boost::serialization::detail::member_saver<boost::archive::bin ary_oarchive,boost::serialization::nvp<myNS::myClass const *> >::invoke(boost::archive::binary_oarchive & ar={...}, const boost::serialization::nvp<myNS::myClass const *> & t={...}, const unsigned int file_version=0) Line 43 + 0x11 C++ myDLL.dll!boost::serialization::split_member<boost::archive::binary_oarc hive,boost::serialization::nvp<myNS::myClass const *> >(boost::archive::binary_oarchive & ar={...}, boost::serialization::nvp<myNS::myClass const *> & t={...}, const unsigned int file_version=0) Line 69 + 0x11 C++ myDLL.dll!boost::serialization::nvp<myNS::myClass const *>::serialize<boost::archive::binary_oarchive>() Line 87 + 0x34 C++ myDLL.dll!boost::serialization::access::serialize<boost::archive::binary _oarchive,boost::serialization::nvp<myNS::myClass const *> >(boost::archive::binary_oarchive & ar={...}, boost::serialization::nvp<myNS::myClass const *> & t={...}, const unsigned int file_version=0) Line 110 C++ myDLL.dll!boost::serialization::serialize<boost::archive::binary_oarchiv e,boost::serialization::nvp<myNS::myClass const *> >(boost::archive::binary_oarchive & ar={...}, boost::serialization::nvp<myNS::myClass const *> & t={...}, const unsigned int file_version=0) Line 81 + 0x11 C++ myDLL.dll!boost::serialization::serialize_adl<boost::archive::binary_oar chive,boost::serialization::nvp<myNS::myClass const *> >(boost::archive::binary_oarchive & ar={...}, boost::serialization::nvp<myNS::myClass const *> & t={...}, const unsigned int file_version=0) Line 140 + 0x18 C++ myDLL.dll!boost::archive::detail::save_non_pointer_type<boost::archive:: binary_oarchive,boost::serialization::nvp<myNS::myClass const *> >::save_only::invoke(boost::archive::binary_oarchive & ar={...}, const boost::serialization::nvp<myNS::myClass const *> & t={...}) Line 256 + 0xf C++ myDLL.dll!boost::archive::detail::save_non_pointer_type<boost::archive:: binary_oarchive,boost::serialization::nvp<myNS::myClass const *> >::invoke(boost::archive::binary_oarchive & ar={...}, const boost::serialization::nvp<myNS::myClass const *> & t={...}) Line 321 + 0xd C++ myDLL.dll!boost::archive::save<boost::archive::binary_oarchive,boost::se rialization::nvp<myNS::myClass const *> >(boost::archive::binary_oarchive & ar={...}, const boost::serialization::nvp<myNS::myClass const *> & t={...}) Line 535 + 0xd C++ myDLL.dll!boost::archive::detail::common_oarchive<boost::archive::binary _oarchive>::save_override<boost::serialization::nvp<myNS::myClass const *> const >() Line 62 + 0x15 C++ myDLL.dll!boost::archive::basic_binary_oarchive<boost::archive::binary_o archive>::save_override<boost::serialization::nvp<myNS::myClass const *> const >() Line 66 C++ myDLL.dll!boost::archive::binary_oarchive_impl<boost::archive::binary_oa rchive,char,std::char_traits<char> >::save_override<boost::serialization::nvp<myNS::myClass const *> const >() Line 46 C++ myDLL.dll!boost::archive::detail::interface_oarchive<boost::archive::bin ary_oarchive>::operator<<<boost::serialization::nvp<myNS::myClass const *> const >(const boost::serialization::nvp<myNS::myClass const *> & t={...}) Line 80 C++ -- This e-mail is confidential and the information contained in it may be privileged. It should not be read, copied or used by anyone other than the intended recipient. If you have received it in error, please contact the sender immediately by telephoning +44 (0)20 7623 8000 or by return email, and delete the e-mail and do not disclose its contents to any person. We believe, but do not warrant, that this e-mail and any attachments are virus free, but you must take full responsibility for virus checking. Please refer to http://www.dresdnerkleinwort.com/disc/email/ and read our e-mail disclaimer statement and monitoring policy. Dresdner Kleinwort is the trading name of the investment banking division of Dresdner Bank AG, and operates through Dresdner Bank AG, Dresdner Kleinwort Limited, Dresdner Kleinwort Securities Limited and their affiliated or associated companies. Dresdner Bank AG is a company incorporated in Germany with limited liability and registered in England (registered no. FC007638, place of business 30 Gresham Street, London EC2V 7PG), and is authorised by the German Federal Financial Supervisory Authority and by the Financial Services Authority ('FSA') and regulated by the FSA for the conduct of designated business in the UK. Dresdner Kleinwort Limited is a company incorporated in England (registered no. 551334, registered office 30 Gresham Street, London EC2V 7PG), and is authorised and regulated by the FSA. Dresdner Kleinwort Securities Limited is a company incorporated in England (registered no. 1767419, registered office 30 Gresham Street, London EC2V 7PG), and is authorised and regulated by the FSA.

3 4

Re: [Boost-users] Serialization newbie needs help
by Dominick Layfield 22 Aug '07

22 Aug '07

Frank Birbacher wrote: > Robert Ramey schrieb: >> > The real easy way is just to use a binary_object which saves/loads a >> > specified number of bytes. >> > so the above would look like: >> > >> > void write_to_cbuffer(char* buf_p, size_t* buf_sz_p) { // note only one * >> > std::ostringstream oss; >> > boost::archive::text_oarchive oa(oss); >> > oa << binary_object(bf_sz_p, mc); >> > } >> > void read_from_cbuffer(const char* buf, const size_t buf_sz) { >> > std::istringstream iss(buf_str); >> > boost::archive::text_iarchive ia(iss); >> > ia >> binary_object(buf_sz, buf) >> > } > > You got this one mixed up. The char array is not something to serailize > but it is the storage to searialize to. The "read_from_cbuffer" function > does *read* the cbuffer and construct a my_class instance out of it by > using serialization. The "write_to_cbuffer" serializes a my_class > instance an stores the result in the cbuffer. > > I can think of using the old strstream class to read from the buffer or > take something from Boost.IOStreams. And writing could be faster if you > use a std::deque wrapped with IOStreams and later on std::copy this into > a char array (instead of memcpy). A deque has usually better performance > on push_back than a vector or string, I guess. But then I don't know the > internals of a stringstream. > > Frank Frank is right. I don't quite know what Robert thought I was looking for, but it's pretty clear that his suggested code does not do what I want. (Nor does it compile!) To clarify: write_to_cbuffer() should serialize a my_class instance into a c-style char* buffer. It also needs to dynamically allocate storage for the buffer, set buf_p to point at the buffer, and set buf_sz to the size of the buffer. This is so that the legacy C code can then call write(fd, buf_p, buf_sz). read_from_cbuffer() does the opposite: it extracts a serialized instance of my_class from a char* buffer. I'll take a look at the boost::iostreams stuff to see if I can figure out how to make that work. Thanks for the tip, Frank. BTW, I don't think a push_back() is any faster for a deque than a vector -- it is push_front() that is faster for a deque. From the STL docs at SGI: "The main way in which deque differs from vector is that deque also supports constant time insertion and removal of elements at the beginning of the sequence". -- Dominick

2 1

building Boost on MacOS: maybe I'm just too stupid but...
by Ole Christian Weidner 22 Aug '07

22 Aug '07

Aloha, I just tried to build Boost 1.34.1 fat (a.k.a. Universal) libraries for MacOS X. This is what happened: I created the following ~/user-config.jam file in order to build Universal libs: using darwin : # version : # command not specified ? use default : # options <compileflags>"-O -g -isysroot /Developer/SDKs/MacOSX10.4u.sdk - arch i386 -arch ppc" <linkflags>"-arch i386 -arch ppc" ; As described in http://www.boost.org/more/getting_started/unix- variants.html 5.1 "Easy Build and Install" I tried to fire up the build system like this: macpro01:/Volumes/Macintosh HD 2/boost_1_34_1 $ ./configure --prefix=/ usr/local/ Building Boost.Jam with toolset darwin... ./configure: line 198: cd: / Volumes/Macintosh: No such file or directory ./configure: line 1: cd: ./tools/jam/src: No such file or directory tools/jam/src//bjam Detecting Python version... 2.5 Detecting Python root... /sw Unicode/ICU support for Boost.Regex?... not found. Backing up existing Boost.Build configuration in user-config.jam.2 Generating Boost.Build configuration in user-config.jam... Generating Makefile... It seems that configure has a problem with "Macintosh HD 2" as a directory name... $ make make: *** No targets specified and no makefile found. Stop. WHATEVER - there's still the 5.2 "custom" way to build the boost libs: $ cd ~/boost_1_34_1/tools/jam/src $ ./build.sh $ cp bin.macosxx86/bjam ../../../ $ cd ~/boost_1_34_1/ $ ./bjam --prefix=/usr/local $ sudo ./bjam install ... 1 hour later everything _seems_ to be fine: $ file /usr/local/lib/libboost_filesystem-1_34_1.dylib /usr/local/lib/libboost_filesystem-1_34_1.dylib: Mach-O universal binary with 2 architectures /usr/local/lib/libboost_filesystem-1_34_1.dylib (for architecture i386): Mach-O dynamically linked shared library i386 /usr/local/lib/libboost_filesystem-1_34_1.dylib (for architecture ppc): Mach-O dynamically linked shared library ppc That's exactly what I wanted. But... THIS is really strange (test.cpp is the regex example from the install manual): $ g++ test.cpp -I/usr/local/include/boost-1_34_1/ -L/usr/local/lib/ - lboost_regex-mt-d-1_34_1 $ ./a.out dyld: Library not loaded: /var/tmp//ccMlDtbZ.out Referenced from: /Volumes/Macintosh HD 2/./a.out Reason: image not found Trace/BPT trap WHAT? I _never_ referenced a library called /var/tmp//ccMlDtbZ.out. What's going on here? Any help is GREATLY appreciated! Thanks, Ole

1 0

CLI: A boost command line interpreter based on boost Program Option
by JD 22 Aug '07

22 Aug '07

Hi all, I wrote a little command line interpreter based on the program option library by Vladimir Prus. You can find it here: http://minilien.com/?bNPy1ECuWv. It's not a big thing but can help sometime. You also have the subversion repository there: http://code.google.com/p/clipo/ Let me know what you think. JD

3 5

Re: [Boost-users] serialization lib, demo_shared_ptr.cpp, XML archives
by Robbie Morrison 22 Aug '07

22 Aug '07

Hello again After posting my earlier message <mailman.2403.1187719362.16337.boost-users(a)lists.boost.org>, I thought some more about 'demo_shared_ptr.cpp' and tried new fixes (isn't that always the way). My modified file 'demo_shared_ptr.mod.cpp' now builds and runs cleanly in both text and XML archive modes. The revised file is appended here. It contains some documentation at the end which may be worth reading. Note too that the data members named 'x' are now member initialized and this duly silences (Linux system) g++ compilier warnings and a raft of valgrind (memory checker) errors. I would now hope that a modified form of 'demo_shared_ptr.cpp' drawing on my experiences can be checked into the Boost SVN repository. I don't think I should be the person who does this, as I may have introduced subtle bugs or bad practice. Neither I have filed a bug report but would do so if asked. Finally, the presence of a buggy 'demo_shared_ptr.cpp' in both 1.33.1 and 1.34.1 almost caused me to give up on using Boost.Serialization. By all accounts, I am not the first to struggle with this demo file and fixing it should be accorded some priority. Many thanks, as always, to the developers and maintainers of Boost.Serialization! best regards to all Robbie --- Robbie Morrison PhD student -- policy-oriented energy system simulation Institute for Energy Engineering (IET) Technical University of Berlin (TU-Berlin), Germany [from IMAP client] // demo_shared_ptr.cpp : shows polymorphic pointer XML serialization // ******************************************************************* // MODIFICATION WARNING: this file has been modified by a Boost user // and is not part of the official Boost distribution. // ******************************************************************* // (C) Copyright 2002 Robert Ramey - http://www.rrsd.com . Polymorphic // derived pointer example by David Tonge. XML variant and some bug // fixes added by Robbie Morrison <robbie(a)actrix.co.nz> on 22-Aug-2007. // Use, modification and distribution is subject to the Boost Software // License, Version 1.0. (See accompanying file LICENSE_1_0.txt or copy at // http://www.boost.org/LICENSE_1_0.txt) // // See http://www.boost.org for updates, documentation, and revision history. // // This file has been tested with Boost release 1.34.1 dated // 24-Jul-2007 (source build) and release 1.33.1 (Ubuntu package) // using the GNU GCC 4.1.2 compiler (with -Wall -pedantic), valgrind // version "valgrind-3.2.0-Debian" memory checker, and Linux Ubuntu // 6.10 operating system (now superseded by 7.04). The file builds // and runs cleanly under the conditions just listed. // // Unlike the 1.34.1 version of this demo, the archive file is not // deleted and can be subsequently examined using any pager utility or // text editor. // // Jump to the end of this file for a discussion on some of the coding // practices employed. // --------------------------------------------------------- // Preprocessor directives controlling archive type // --------------------------------------------------------- // these can be reset lower values to aid troubleshooting // 0 = straight text, 1 = text with NVP (name-value-pair) statements, 2 = xml #define ARCHIVE_MODE 2 // 0 = omit David Tonge derived pointer code, 1 = use derived pointer code #define POLYMORPHIC_CODE 1 // --------------------------------------------------------- #include <iomanip> // setw() and family #include <iostream> // standard io #include <fstream> // file-based io #include <string> // C++ strings #include <boost/archive/tmpdir.hpp> // locate a temporary directory #if (ARCHIVE_MODE >= 2) # include <boost/archive/xml_iarchive.hpp> // archive for loading XML # include <boost/archive/xml_oarchive.hpp> // archive for saving XML #else # include <boost/archive/text_iarchive.hpp> // archive for loading text # include <boost/archive/text_oarchive.hpp> // archive for saving text #endif #include <boost/serialization/shared_ptr.hpp> // shared_ptr serialization #include <boost/serialization/base_object.hpp> // base class serialization #include <boost/serialization/export.hpp> // explicit code for exports (place last) class A { friend class boost::serialization::access; private: template <class Archive> void serialize (Archive& ar, const unsigned int class_version) { #if (ARCHIVE_MODE >= 1) ar & BOOST_SERIALIZATION_NVP(x); // boost::serialization::make_nvp("x", x) #else ar & x; // simple form for text archives #endif } int x; public: A(): x(42) { ++count; } // default constructor, the 42 is arbitrary virtual ~A() { --count; } static int count; // public in order to simplify test code }; BOOST_CLASS_EXPORT(A) // requires <boost/serialization/export.hpp> // if using particular Metrowerks or Borland compilers, uncomment the following: // BOOST_SERIALIZATION_SHARED_PTR(B) int A::count = 0; class B : public A // class B added by David Tonge { friend class boost::serialization::access; private: int x; template<class Archive> void serialize(Archive& ar, const unsigned int class_version) { #if (ARCHIVE_MODE >= 1) //ar & boost::serialization::base_object<A>(*this); // CAUTION: problematic for XML ar & BOOST_SERIALIZATION_BASE_OBJECT_NVP(A); // .. but this works fine ar & BOOST_SERIALIZATION_NVP(x); #else ar & boost::serialization::base_object<A>(*this); // this is fine for text //ar & BOOST_SERIALIZATION_BASE_OBJECT_NVP(A); // .. and this also works ar & x; // x now saved (unlike 1.34.1) #endif } public: B() : A(), x(84) { ++count; } // default constructor, the 84 is arbitrary virtual ~B() { --count; } static int count; }; // if using particular Metrowerks or Borland compilers, uncomment the following: // BOOST_SERIALIZATION_SHARED_PTR(B) BOOST_CLASS_EXPORT(B) int B::count = 0; void display(boost::shared_ptr<A>& a, boost::shared_ptr<A>& a1) { std::cout << "a = 0x" << std::hex << a.get() << std::dec << ", "; if (a.get()) std::cout << "is a " << typeid(*(a.get())).name() << "*, "; std::cout << "use count = " << std::dec << a.use_count() << std::endl; std::cout << "a1 = 0x" << std::hex << a1.get() << std::dec << ", "; if (a1.get()) std::cout << "is a " << typeid(*(a1.get())).name() << "*, "; std::cout << "use count = " << std::dec << a1.use_count() << std::endl; std::cout << "unique element count = " << A::count << std::endl; std::cout << std::endl; } int main(int argc, char* argv[]) { // report some build details to the console std::cout << std::endl; std::cout << "archive mode : " << ARCHIVE_MODE << std::endl; std::cout << "DT extension mode : " << POLYMORPHIC_CODE << std::endl; // name the archive file appropriately #if (ARCHIVE_MODE >= 2) std::string ext = "xml"; // XML archive #else std::string ext = "txt"; // text archive #endif std::string filename(boost::archive::tmpdir()); //locate a temporary directory filename += "/demo_shared_ptr"; filename += "."; filename += ext; std::cout << "testfile name : " << filename << std::endl; std::cout << std::endl; // note the test type std::cout << "base smart pointer tests" << std::endl; std::cout << std::endl; // create a new shared pointer to a new object of type A boost::shared_ptr<A> spa(new A()); boost::shared_ptr<A> spa1; spa1 = spa; display(spa, spa1); // serialize the pointers { // open the archive file std::ofstream ofs(filename.c_str()); #if (ARCHIVE_MODE >= 2) boost::archive::xml_oarchive oa(ofs); #else boost::archive::text_oarchive oa(ofs); #endif #if (ARCHIVE_MODE >= 1) oa << BOOST_SERIALIZATION_NVP(spa); oa << BOOST_SERIALIZATION_NVP(spa1); #else oa << spa; oa << spa1; #endif } // reset the shared pointer to NULL thereby destroying the type A object spa.reset(); spa1.reset(); display(spa, spa1); // restore state to one equivalent to the original { // open the archive file std::ifstream ifs(filename.c_str()); #if (ARCHIVE_MODE >= 2) boost::archive::xml_iarchive ia(ifs); #else boost::archive::text_iarchive ia(ifs); #endif #if (ARCHIVE_MODE >= 1) ia >> BOOST_SERIALIZATION_NVP(spa); ia >> BOOST_SERIALIZATION_NVP(spa1); #else ia >> spa; ia >> spa1; #endif } display(spa, spa1); spa.reset(); spa1.reset(); #if (POLYMORPHIC_CODE >= 1) // that is, use derived pointer code // note the test type std::cout << "derived smart pointer tests" << std::endl; std::cout << std::endl; // new code by David Tonge starts here // create a new shared pointer to a new object of type A spa = boost::shared_ptr<A>(new B()); spa1 = spa; display(spa, spa1); // serialize it // CAUTION: archive saved earlier will be simply overwritten { std::ofstream ofs(filename.c_str()); #if (ARCHIVE_MODE >= 2) boost::archive::xml_oarchive oa(ofs); #else boost::archive::text_oarchive oa(ofs); #endif #if (ARCHIVE_MODE >= 1) oa << BOOST_SERIALIZATION_NVP(spa); oa << BOOST_SERIALIZATION_NVP(spa1); #else oa << spa; oa << spa1; #endif } // reset the shared pointer to NULL thereby destroying the type B object spa.reset(); spa1.reset(); display(spa, spa1); // restore state to one equivalent to the original { // reopen the archive std::ifstream ifs(filename.c_str()); #if (ARCHIVE_MODE >= 2) boost::archive::xml_iarchive ia(ifs); #else boost::archive::text_iarchive ia(ifs); #endif #if (ARCHIVE_MODE >= 1) ia >> BOOST_SERIALIZATION_NVP(spa); ia >> BOOST_SERIALIZATION_NVP(spa1); #else ia >> spa; ia >> spa1; #endif } display(spa, spa1); #endif // POLYMORPHIC_CODE return 0; } // main() // --------------------------------- // Output // --------------------------------- // // archive mode : 2 // DT extension mode : 1 // testfile name : ./demo_shared_ptr.xml // // base smart pointer tests // // a = 0x0x42ca428, is a 1A*, use count = 2 // a1 = 0x0x42ca428, is a 1A*, use count = 2 // unique element count = 1 // // a = 0x0, use count = 0 // a1 = 0x0, use count = 0 // unique element count = 0 // // a = 0x0x42d3a08, is a 1A*, use count = 2 // a1 = 0x0x42d3a08, is a 1A*, use count = 2 // unique element count = 1 // // derived smart pointer tests // // a = 0x0x42d4ab0, is a 1B*, use count = 2 // a1 = 0x0x42d4ab0, is a 1B*, use count = 2 // unique element count = 1 // // a = 0x0, use count = 0 // a1 = 0x0, use count = 0 // unique element count = 0 // // a = 0x0x42de180, is a 1B*, use count = 2 // a1 = 0x0x42de180, is a 1B*, use count = 2 // unique element count = 1 // --------------------------------- // Coding practices // --------------------------------- // // Polymorphic behavior // // This demo does involve polymorphic behavior due to the // presence of a virtual function in the base class, in this case // the virtual destructor for A: // // virtual ~A(); // gives rise to polymorphic behavior // // If you wish to experiment, remove the virtual specifier and // note the now much reduced XML archive. // // Default (zero-argument) constructor // // All deserialized classes need a default constructor. This // need not be explicitly defined, in which case the // compiler-supplied version is used. For deserialization // purposes, the default constructor can be private (although // other design considerations will normally mean that it is, at // most, protected). // // Class registration // // In this demo, class registration relies on explicit export of // the class and its globally unique identifier (GUID). This is // achieved using the following macro: // // BOOST_CLASS_EXPORT(Class) // "Class" becomes the GUID // // This form of class registration is known as "key export". A // more general macro also exists (but was not employed here) in // which the client code actively manages the GUID: // // BOOST_CLASS_EXPORT_GUID(Class, "my-guid") // // Class registration can also be accomplished by inserting a C++ // registration statement within 'serialize' or, in some cases, // placing reliance on serialization order. However these other // approaches require an up-front knowledge of the class // hierarchy or are dependent on program flow. Key export is // hence the more flexible and less brittle strategy and should // therefore be preferred. Moreover, it is probably good // practice to explicitly export all serialized classes, even when // this is not strictly required. // // Base/derived information // // Class hierarchy information is communicated here using the // following macro: // // ar & BOOST_SERIALIZATION_BASE_OBJECT_NVP(BaseClass); // // As before, a direct C++ statement is possible. However this // broke for the XML format archive (I didn't investigate why). // Hence it would appear that use of the above macro is necessary // when serializing to XML. // // Non-default names/GUIDs // // If a macro which employs an explicit object name or class GUID // is used, then the new string literal must be valid XML. In // particular, whitespace is not acceptable and its use will // generate an "unrecognized XML syntax" exception at run-time: // // using boost::serialization::make_nvp; // ar & make_nvp("my data", data); // run-time exception // // Associated headers // // Read the code itself for more information on the associated // headers and their correct placement: // // <boost/serialization/base_object.hpp> // <boost/serialization/export.hpp> // // Build and run command-lines (your library name may be different) // // all warnings (the grep screening relates to -Weffc++, see man g++): // // $ g++ -ggdb -Wall -Weffc++ -pedantic // demo_shared_ptr.mod.cpp // -lboost_serialization-gcc41 // -o demo_shared_ptr // 2>&1 // | grep --invert-match '/usr/local/include/boost-1_34_1/boost' // | grep --invert-match 'instantiated from' // // simplified build: // // $ g++ demo_shared_ptr.mod.cpp // -lboost_serialization-gcc41 // -o demo_shared_ptr // // run with memory checking: // // $ valgrind ./demo_shared_ptr // // simplified run: // // $ ./demo_shared_ptr // // Compile-time static asserts // // These may be difficult to interpret (in my limited // experience). Note that a pointer to a C++ fundamental type // (for example, int*) cannot be de/serialized. // // Run-time exceptions // // Some common messages and probable fixes (based on the style // recommendations above): // // "unregistered_class" // missing: BOOST_CLASS_EXPORT(SubClass) // // "unregistered void cast" // missing: ar & BOOST_SERIALIZATION_BASE_OBJECT_NVP(BaseClass); // // "unrecognized XML syntax" // name-value-pair name contains whitespace // end of file demo_shared_ptr.mod.cpp

2 1

Re: [Boost-users] [Boost][Serialization] Possible Bug inOptional.hpp
by Marc Viala 22 Aug '07

22 Aug '07

Thanks for your quick answer Robert. Sure it doesn't affect the program behaviour but the debug with Visual C++ IDE is little bit more painful ;-). I'm going to fix my own copy of the file. Marc Viala De la part de Robert Ramey clearly its a bug but it shouldn't affect any programs, I'll fix it in my working copy. You can fix it by just initializing to 0. Robert Ramey "Marc Viala" <mviala(a)acticm.com> wrote in message news:D0D608FD34E14C4BA93A30AC162651E18BA519@SERVEUR2003.acticm.com... I've downloaded recently the version Boost 1.34.1 and performed some tests on ours applications integrating Boost components. During theses tests, I've tried to deserialize some XML archives generated w/ Boost 1.33.1 including some boost::optional<> instances and I've observed that the Visual C++ 7.1 IDE emits run-time checks in the load<boost::optional<>>() @ line 60 in file boost/serialization/optional.hpp. template<class Archive, class T> void load( Archive & ar, boost::optional<T> & t, const unsigned int /*version*/ ){ bool tflag; ar >> boost::serialization::make_nvp("initialized", tflag); if (tflag){ unsigned int v; if(3 < ar.get_library_version()){ ar >> make_nvp("item_version", v); } detail::stack_construct<Archive, T> aux(ar, v); ^^^^^^^^^^^^^^^^^^^^^^^^ Here Run-Time Check Failure #3 - The variable 'v' is being used without being defined. ar >> boost::serialization::make_nvp("value", aux.reference()); t.reset(aux.reference()); } else { t.reset(); } } Is it possible to avoid this run-time check by a preinitialisation of the local variable "v"? Is it a Bug? Best regards, Used Configurations: Windows XP Boost 1.34.1 (through Boost Installer w/ DLL libraries) Marc Viala

1 0

regex_search all
by izua 22 Aug '07

22 Aug '07

How can I do a regex search that will return me all patterns for the given regular expression? Somehow like preg_match_all in PHP. -- View this message in context: http://www.nabble.com/regex_search-all-tf4292590.html#a12219928 Sent from the Boost - Users mailing list archive at Nabble.com.

3 6

Re: [Boost-users] [statechart] using events for passing information
by "Christian Bähnisch" 22 Aug '07

22 Aug '07

I'm working on a controller connected to a external device through a serial port. I have to process events triggered by the device which can be group into several categories like simple status events "My firmware has version XXXX" or "the result of my last working step was XXXX" as you can see my events carry data. I want to encapsulate this communication events in statechart events, so I can change to states depending on the event's category, and then make further processing where I have to extract data I have passed into them. I thought this would be a common use case for a statechart appproach ... -- GMX FreeMail: 1 GB Postfach, 5 E-Mail-Adressen, 10 Free SMS. Alle Infos und kostenlose Anmeldung: http://www.gmx.net/de/go/freemail

2 1

[Boost][Serialization] Possible Bug in Optional.hpp
by Marc Viala 22 Aug '07

22 Aug '07

I've downloaded recently the version Boost 1.34.1 and performed some tests on ours applications integrating Boost components. During theses tests, I've tried to deserialize some XML archives generated w/ Boost 1.33.1 including some boost::optional<> instances and I've observed that the Visual C++ 7.1 IDE emits run-time checks in the load<boost::optional<>>() @ line 60 in file boost/serialization/optional.hpp. template<class Archive, class T> void load( Archive & ar, boost::optional<T> & t, const unsigned int /*version*/ ){ bool tflag; ar >> boost::serialization::make_nvp("initialized", tflag); if (tflag){ unsigned int v; if(3 < ar.get_library_version()){ ar >> make_nvp("item_version", v); } detail::stack_construct<Archive, T> aux(ar, v); ^^^^^^^^^^^^^^^^^^^^^^^^ Here Run-Time Check Failure #3 - The variable 'v' is being used without being defined. ar >> boost::serialization::make_nvp("value", aux.reference()); t.reset(aux.reference()); } else { t.reset(); } } Is it possible to avoid this run-time check by a preinitialisation of the local variable "v"? Is it a Bug? Best regards, Used Configurations: Windows XP Boost 1.34.1 (through Boost Installer w/ DLL libraries) Marc Viala

2 1

Re: [Boost-users] Serialization newbie needs help
by Dominick Layfield 22 Aug '07

22 Aug '07

>> > Obviously, I can just switch to a different serialization library >> > (e.g. s11n). > > I believe that library also has serialization of pointers Darn it! Foiled at every turn! :-) If that is the case, maybe you might consider updating/clarifying the "Overview -> Other implementations" section of the docs. There you imply that s11n doesn't do this. (Maybe it didn't back when you wrote the docs.) >> But as much as possible, I would like to stick with >> > whatever is most "standard". And as part of the Boost family, I'm >> > guessing that boost::serialization is top dog here. Would that be >> > right? Is this library included in any of the proposed C++ >> > standards (TR2, C++0x)? > > This serialization library will never be part of any C++ standard. Oh. That's disappointing. Why not? Too much bureaucracy involved? > Because normally one doesn't want to change data while its being saved > one will typically have something like the following in his program. > > FileSave(const MyData & md){ > // create archive > oa << md; // no need for "const cast" because md is already "const" > ... > } Okay. That makes a lot of sense. Let me ask another newbie question, about how to get data in and out of an archive. I have to work with legacy C-based code that delivers/accepts data in a char* buffer. My code to serialize data into and out of this buffer is both convoluted and inefficient. It looks something like this: my_class mc; void read_from_cbuffer(const char* buf, const size_t buf_sz) { std::string buf_str(buf, buf_sz); std::istringstream iss(buf_str); boost::archive::text_iarchive ia(iss); ia >> mc; } void write_to_cbuffer(char** buf_p, size_t* buf_sz_p) { std::ostringstream oss; boost::archive::text_oarchive oa(oss); oa << mc; *buf_p = new char[oss.str().size()]; memcpy(*buf_p, oss.str().c_str(), oss.str().size()); *buf_sz_p = oss.str().size(); } Any suggestions about how this can be done better? Thanks, -- Dominick

4 3

Boost 1.34.1 + MinGW + STLport5-dll
by Johannes Barop 22 Aug '07

22 Aug '07

Hello, I'm trying to build Boost 1.34.1 with MinGW and STLport5. With no success. I created a user-config.jam in my home directory with following content: <snip> using stlport : 5.1 : "C:\\MinGW\\STLport-5.1.3\\stlport" "C:\\MinGW\\STLport-5.1.3\\lib" ; </snip> Then I tryed to build Boost with the following command line: bjam --toolset=gcc stage stdlib=stlport runtime-link=shared Which gave me a lots of errors. See here: http://nopaste.php-quake.net/2727 Any ideas what might be wrong? Cheers, Johannes

1 0

Subject : [Multi-index] -- using a hashed unique index that is not part of the hashed value
by Oliver Kania 22 Aug '07

22 Aug '07

Hello, what I basically want to do is using multi-index like a hashmap. I want to use vector<long> as key. However, all the examples I found are using member-fields of the values or the values themselves as key. Is it not possible to use multi-index like a hash_map<value,key> where the key is independent of the value type ? If yes, could someone please provide an example ? regards, Oliver

2 2

Re: [Boost-users] boost bind beginner throw problem
by Taglioretti Roberto 22 Aug '07

22 Aug '07

From: "Peter Dimov" > The following program works for me with VC 7.1. > #include <boost/bind.hpp> > struct Error {}; > struct X { void test( int i ) throw( Error ) {}}; > int main() > { > X obj; > boost::bind( &X::test, obj, _1 ); >} I try to compile your example, theese are the error messages on my VC 7.1: C:\sviluppo\r2\boost\build\1.34.1\include\boost\lambda\detail\bind_functions.hpp(544): error C2553: no legal conversion of return value to return type 'type' "const boost::lambda::lambda_functor<T>" with [ T=boost::lambda::lambda_functor_base<boost::lambda::action<4,boost::lambda::function_action<4>>,boost::tuples::tuple<const boost::lambda::detail::bind_traits<void (__thiscall SVLCompiler::Analysis::* const )(SVLCompiler::Analysis::Iteratorp_t,SVLCompiler::Analysis::Iteratorp_t)>::type,const boost::lambda::detail::bind_traits<SVLCompiler::Analysis *const >::type,const boost::lambda::detail::bind_traits<const boost::lambda::placeholder1_type>::type,const boost::lambda::detail::bind_traits<const boost::lambda::placeholder2_type>::type,boost::lambda::detail::bind_traits<boost::tuples::null_type>::type,boost::lambda::detail::bind_traits<boost::tuples::null_type>::type,boost::lambda::detail::bind_traits<boost::tuples::null_type>::type,boost::lambda::detail::bind_traits<boost::tuples::null_type>::type,boost::lambda::detail::bind_traits<boost::tuples::null_type>::type,boost::lambda::detail::bind_traits<boost::tuples::null_type>::type>> ] C:\sviluppo\r2\boost\build\1.34.1\include\boost\lambda\detail\bind_functions.hpp(544): error C2664: "boost::lambda::lambda_functor<T>::lambda_functor(const boost::lambda::lambda_functor<T> &)": impossibile convertire il parametro 1 da "boost::lambda::lambda_functor_base<Act,Args>" a "const boost::lambda::lambda_functor<T> &" with [ T=boost::lambda::lambda_functor_base<boost::lambda::action<4,boost::lambda::function_action<4>>,boost::tuples::tuple<const boost::lambda::detail::bind_traits<void (__thiscall SVLCompiler::Analysis::* const )(SVLCompiler::Analysis::Iteratorp_t,SVLCompiler::Analysis::Iteratorp_t)>::type,const boost::lambda::detail::bind_traits<SVLCompiler::Analysis *const >::type,const boost::lambda::detail::bind_traits<const boost::lambda::placeholder1_type>::type,const boost::lambda::detail::bind_traits<const boost::lambda::placeholder2_type>::type,boost::lambda::detail::bind_traits<boost::tuples::null_type>::type,boost::lambda::detail::bind_traits<boost::tuples::null_type>::type,boost::lambda::detail::bind_traits<boost::tuples::null_type>::type,boost::lambda::detail::bind_traits<boost::tuples::null_type>::type,boost::lambda::detail::bind_traits<boost::tuples::null_type>::type,boost::lambda::detail::bind_traits<boost::tuples::null_type>::type>> ] and [ Act=boost::lambda::action<4,boost::lambda::function_action<4>>, Args=boost::tuples::tuple<const boost::lambda::detail::bind_traits<void (__thiscall SVLCompiler::Analysis::* const )(SVLCompiler::Analysis::Iteratorp_t,SVLCompiler::Analysis::Iteratorp_t) throw(SVLCompiler::Analysis::Error_check)>::type,const boost::lambda::detail::bind_traits<SVLCompiler::Analysis *const >::type,const boost::lambda::detail::bind_traits<const boost::lambda::placeholder1_type>::type,const boost::lambda::detail::bind_traits<const boost::lambda::placeholder2_type>::type,boost::lambda::detail::bind_traits<boost::tuples::null_type>::type,boost::lambda::detail::bind_traits<boost::tuples::null_type>::type, I hope you can help me :-( -- Roberto Taglioretti *sono affetto da discromatopsia, per favore evitate l'invio di mail o allegati colorati* *I have dyschromatopsia, please do not send coloured text or email and attach* Aderite al progetto SETI: http://setiweb.ssl.berkeley.edu/team_display.php?teamid=30233

2 1

boost::spirit
by Christer Borgqvist 22 Aug '07

22 Aug '07

Hello Boost Experts I'm using the BDS 2006 and trying to use the spirit library like this #include <boost/spirit.hpp> in my function string hex="0x1F"; unsigned int value; parse( hex.c_str() , hex_p[assign_a(value)] ); // i get following compiler error [C++ Error] closures.hpp(238): E2299 Cannot generate template specialization from 'impl::closure_frame_holder<FrameT>' thanks for any help //Christer

3 2

Bug in shared_array
by Hansi Hansi 22 Aug '07

22 Aug '07

Hello, I think I have found an bug in the shared_array implementation in version 1.34.1 for VC8.0. I hope that this is the right location to post this and that one fixes this file. I think that the implementation needs this: #elif defined( _MANAGED ) static void unspecified_bool( this_type*** ) { } typedef void (*unspecified_bool_type)( this_type*** ); operator unspecified_bool_type() const // never throws { return px == 0? 0: unspecified_bool; } it is the same implementation as used in shared_ptr. If I don't have this I get during the call a buffer overrun. Best regards Hansjörg __________________________________________________________________________ Erweitern Sie FreeMail zu einem noch leistungsstärkeren E-Mail-Postfach! Mehr Infos unter http://produkte.web.de/club/?mc=021131

1 0

Re: [Boost-users] Serialization newbie needs help
by Dominick Layfield 21 Aug '07

21 Aug '07

"Robert Ramey" <ramey(a)rrsd.com> wrote: > Actually, I've considered reviewing all the email in this list and > summarizing > the results in a section "Hints and Troubleshooting Tips". I think this > is useful and necessary and useful, but I just havent gotten around to it. That sounds ideal. > > But if you could provide me an example of when pointer serialization > > shines, > > then I would say "Aha! Now I understand why Robert went to so much > > trouble to make this work.", and I could be at peace with the world > > again! :-) > > LOL - I haven't had time to make any real apps lately. So... no example at all? My problem is that I just don't see when pointer serialization would be a big win. But I can't tell if I just have a limited perspective. That's why I was genuinely hoping that you could provide a concrete example. Naturally, a system that "just works" no matter what structure is thrown at it sounds very enticing. However, as you have acknowledged, the system is not foolproof, and user gotchas remain. One way to eliminate the gotchas would be to reduce the scope of the library. Clearly, this is unlikely to happen, as (i) you've invested a lot of time and effort getting the pointer magic to work, and (ii) there are probably a lot of applications out there that would break if you did so. I for one would certainly appreciate a simplified version which omitted the pointer magic, and thus removed the const trap and similar issues. If I want to set up pointers within an object, then I can do so manually using the type-specific load()/save() functions. Obviously, I can just switch to a different serialization library (e.g. s11n). But as much as possible, I would like to stick with whatever is most "standard". And as part of the Boost family, I'm guessing that boost::serialization is top dog here. Would that be right? Is this library included in any of the proposed C++ standards (TR2, C++0x)? > > BTW, I don't want to sound like I'm bashing your library, so let me > > end with a compliment. I think the symmetric design of serialize(), > > with the same function used for both input and output, is one of the > > prettiest > > idioms I've seen in years. > > And that's the one thing I didn't do - I believe I "borrowed" it from Jens > Maurer. Hah! Ooops. Well, that compliment backfired! ;-) Let's try again: I *really* appreciate the built-in support for all the STL container classes. So far, these have "just worked" perfectly for me. Nice work! > One tiny point. I'm aware that the "const" trap is annoying. But I've > become > convinced that the annoyance is small compared to the hassles it saves me > and users from. I suspect that those who have a problem with aren't in the > habit of using "const" everywhere they can. It does seem bizarre to have to const-cast an object just so that it can be output. I presume that the majority of objects that are to be serialized are not intrinsically constant, so this needs to be done the majority of the time. And it looks dangerous. What does the const-cast actually mean in this context? I assume it means: "I promise that no other thread is going to modify the object (or anything its pointers point to) while the serialize() operation is pending. Is that correct? If so, then shouldn't it be solved explicitly with concurrent programming primitives (i.e. mutexes or similar)? -- Dominick

5 7

An easy one
by Panayiotis 21 Aug '07

21 Aug '07

Hello, what is the equivalent of: void foo(int array[]) for boost::array? Thanks, Panayiotis

4 6

Can Python "httplib" module be directly embedded in C++ ?
by Raja Cherukuri 21 Aug '07

21 Aug '07

Hello, I am trying to use python to do my XML post ? Can I do this by directly calling import on the httplib like this and setting parameters ? ex: boost::python::object http_module((boost::python::handle<>(boost::python::borrowed(PyImport_Ad dModule("httplib"))))); boost::python::<....some kind of python compile time...interface...> h = < some kind of cast...> http_module.HTTP("http://www.abc.com"); h.putrequest('POST', selector) h.putheader('content-type', content_type) h.putheader('content-length', str(len(body))) h.endheaders() h.send(body) Or should the actual code for this object reside in a text file and I should call exec_file ? Thanks in Advance. - Raja

2 6

[mpl] Is it possible to mpl_assert depending on the derivation of a class
by Hughes, James 21 Aug '07

21 Aug '07

Hello all, I want some template code to assert if the passed in template type is NOT derived from a particular base class. I've looked through the Template Metaprogamming book, but haven't seen anything that can do this, but I seem to remember something along those lines. Can anyone help? James This message (including any attachments) contains confidential and/or proprietary information intended only for the addressee. Any unauthorized disclosure, copying, distribution or reliance on the contents of this information is strictly prohibited and may constitute a violation of law. If you are not the intended recipient, please notify the sender immediately by responding to this e-mail, and delete the message from your system. If you have any questions about this e-mail please notify the sender immediately.

4 9

serialization lib, demo_shared_ptr.cpp, XML archives
by Robbie Morrison 21 Aug '07

21 Aug '07

Hello all My problem is similar to that discussed by Phil and Robert Ramey on 'Boost - Users' back in 08-Feb-2007. Their thread was titled "serialization stream error". Phil however did not post back a follow up and it remains unclear as to whether his difficulties were resolved or not. Moreover, these discussions predate the 1.34.1 release on 24-Jul-2007 by about five months. For my part, I have tried solving the problem covered in this email using: - Boost 1.33.1 from an Ubuntu package and dated 05-Dec-2005 - Boost 1.34.1 built from source under Ubuntu 6.10 I would like to get 'demo_shared_ptr.cpp' to run using XML rather than text as the archive format -- as a precursor to integrating this kind of code into an energy system simulation. I decided to use a step-by-step approach: step 1 - build and run the original 'demo_shared_ptr.cpp' using the original text archive format - therefore, remove the leading A:: and B:: from constructor and destructor definitions - comment out the following (two places): oa.register_type(static_cast<boost::detail::sp_counted_base_impl > *>(NULL)); [as far as I could tell 'sp_counted_base_impl' no longer exists] step 2 - add NVP statements while retaining the text archive format for the time being - therefore, swap over all archive calls, for instance: // ar & x; ar & boost::serialization::make_nvp("x", x); step 3 - switch to the XML archive format - duly change the following headers: // #include <boost/archive/text_iarchive.hpp> // #include <boost/archive/text_oarchive.hpp> #include <boost/archive/xml_iarchive.hpp> #include <boost/archive/xml_oarchive.hpp> - duly change the archive objects: // boost::archive::text_oarchive oa(ofs); boost::archive::xml_oarchive oa(ofs); Step 3 fails but only in the derived pointer code added by David Tonge to 'demo_shared_ptr.cpp'. A 'boost::STATIC_ASSERTION_FAILURE' is generated. Typical error messages are given after the main body of this posting. At this point, I ran out of ideas. I have read the HTML documentation and made my own notes and still can't see a solution. Any assistance would be very gratefully received! Note too that I only log on once per day so don't expect a rapid turn-around for requests for details. In addition, I will send diffs to the maintainer when I get a satisfactory solution. And, in passing, it is material to note that derived class B does not fully archive its state and that there should probably be an "ar & x" statement in its 'serialize' definition. For the record, here is my development environment: os : Ubuntu 6.10, Linux 2.6.17-12-generic hardware : Toshiba Tecra A2 330 laptop (purchased 27-Aug-2004) specs : 1.4GHz Intel Celeron M (32-bit) / 512MiB RAM / 40GB HDD / 1024x76 gcc : gcc (GCC) 4.1.2 20060928 (prerelease) (Ubuntu 4.1.1-13ubuntu5) I realize that this is not the latest release of Ubuntu, but otherwise my system is fully current. Lastly, I take it Boost.Serialization and TR1 shared pointers (std::tr1::shared_ptr) remain incompatible at this point in development. Many thanks to Robert Ramey for developing Boost.Serialization. It suits my needs to a tee, so I hope I can get this issue resolved and move on with real coding. best wishes Robbie --------------------------------- selected error messages --------------------------------- /usr/local/include/boost-1_34_1/boost/archive/basic_xml_oarchive.hpp: In member function 'void boost::archive::basic_xml_oarchive<Archive>::save_override(T&, int) [with T = const A, Archive = boost::archive::xml_oarchive]': /usr/local/include/boost-1_34_1/boost/archive/detail/interface_oarchive.hpp:79: instantiated from 'Archive& boost::archive::detail::interface_oarchive<Archive>::operator<<(T&) [with T = const A, Archive = boost::archive::xml_oarchive]' /usr/local/include/boost-1_34_1/boost/archive/detail/interface_oarchive.hpp:87: instantiated from 'Archive& boost::archive::detail::interface_oarchive<Archive>::operator&(T&) [with T = A, Archive = boost::archive::xml_oarchive]' qdemo_shared_ptr.mod01.cpp:76: instantiated from 'void B::serialize(Archive&, unsigned int) [with Archive = boost::archive::xml_oarchive]' /usr/local/include/boost-1_34_1/boost/serialization/access.hpp:109: instantiated from 'static void boost::serialization::access::serialize(Archive&, T&, unsigned int) [with Archive = boost::archive::xml_oarchive, T = B]' /usr/local/include/boost-1_34_1/boost/serialization/serialization.hpp:81: instantiated from 'void boost::serialization::serialize(Archive&, T&, unsigned int) [with Archive = boost::archive::xml_oarchive, T = B]' /usr/local/include/boost-1_34_1/boost/serialization/serialization.hpp:140: instantiated from 'void boost::serialization::serialize_adl(Archive&, T&, unsigned int) [with Archive = boost::archive::xml_oarchive, T = B]' /usr/local/include/boost-1_34_1/boost/archive/detail/oserializer.hpp:225: instantiated from 'boost::archive::detail::pointer_oserializer<T, Archive>::pointer_oserializer() [with T = B, Archive = boost::archive::xml_oarchive]' /usr/local/include/boost-1_34_1/boost/archive/detail/oserializer.hpp:197: instantiated from 'const boost::archive::detail::pointer_oserializer<B, boost::archive::xml_oarchive> boost::archive::detail::pointer_oserializer<B, boost::archive::xml_oarchive>::instance' /usr/local/include/boost-1_34_1/boost/archive/detail/oserializer.hpp:189: instantiated from 'static const boost::archive::detail::pointer_oserializer<T, Archive>& boost::archive::detail::pointer_oserializer<T, Archive>::instantiate() [with T = B, Archive = boost::archive::xml_oarchive]' /usr/local/include/boost-1_34_1/boost/archive/detail/oserializer.hpp:514: instantiated from 'const boost::archive::detail::basic_pointer_oserializer& boost::archive::detail::instantiate_pointer_oserializer(Archive*, T*) [with Archive = boost::archive::xml_oarchive, T = B]' /usr/local/include/boost-1_34_1/boost/archive/detail/interface_oarchive.hpp:59: instantiated from 'const boost::archive::detail::basic_pointer_oserializer* boost::archive::detail::interface_oarchive<Archive>::register_type(const T*) [with T = B, Archive = boost::archive::xml_oarchive]' demo_shared_ptr.mod01.cpp:200: instantiated from here /usr/local/include/boost-1_34_1/boost/archive/basic_xml_oarchive.hpp:83: error: invalid application of 'sizeof' to incomplete type 'boost::STATIC_ASSERTION_FAILURE<false>' --------------------------------- my modifications --------------------------------- $ diff -u demo_shared_ptr.cpp demo_shared_ptr.mod01.cpp --- demo_shared_ptr.cpp 2007-08-21 11:51:35.000000000 +0200 +++ demo_shared_ptr.mod01.cpp 2007-08-21 14:44:33.000000000 +0200 @@ -9,6 +9,21 @@ // // See http://www.boost.org for updates, documentation, and revision history. +// build : $ g++ -ggdb -Wall demo_shared_ptr.mod01.cpp +// -lboost_serialization-gcc41 -o demo_shared_ptr +// run : $ demo_shared_ptr + +// --------------------------------------------------------- +// PREPROCESSOR DIRECTIVES +// --------------------------------------------------------- + +// 0 = text, 1 = text with NPV statements, 2 = xml +#define XEONA_ARCHIVE_MODE 2 +// 0 = omit DT code, 1 = use DT code +#define DT_CODE 1 + +// --------------------------------------------------------- + #include <iomanip> #include <iostream> #include <fstream> @@ -17,15 +32,23 @@ #include <cstdio> // remove #include <boost/config.hpp> #if defined(BOOST_NO_STDC_NAMESPACE) -namespace std{ +namespace std{ using ::remove; } #endif -#include <boost/archive/text_oarchive.hpp> -#include <boost/archive/text_iarchive.hpp> +#if (XEONA_ARCHIVE_MODE >= 2) +# include <boost/archive/xml_oarchive.hpp> +# include <boost/archive/xml_iarchive.hpp> +#else +# include <boost/archive/text_oarchive.hpp> +# include <boost/archive/text_iarchive.hpp> +#endif + #include <boost/archive/tmpdir.hpp> +//#include <boost/serialization/base_object.hpp> // base class serialization + #include <boost/serialization/shared_ptr.hpp> /////////////////////////// @@ -37,12 +60,18 @@ int x; template<class Archive> void serialize(Archive & ar, const unsigned int /* file_version */){ - ar & x; + +#if (XEONA_ARCHIVE_MODE >= 1) + ar & boost::serialization::make_nvp("x", x); +#else + ar & x; +#endif + } public: static int count; - A::A(){++count;} // default constructor - virtual A::~A(){--count;} // default destructor + A(){++count;} // default constructor + virtual ~A(){--count;} // default destructor }; BOOST_SERIALIZATION_SHARED_PTR(A) @@ -56,12 +85,18 @@ int x; template<class Archive> void serialize(Archive & ar, const unsigned int /* file_version */){ - ar & boost::serialization::base_object<A>(*this); + +#if (XEONA_ARCHIVE_MODE >= 1) + ar & boost::serialization::base_object<A>(*this); // problem +#else + ar & boost::serialization::base_object<A>(*this); +#endif + } public: static int count; - B::B() : A() {}; - virtual B::~B() {}; + B() : A() {}; + virtual ~B() {}; }; BOOST_SERIALIZATION_SHARED_PTR(B) @@ -83,8 +118,30 @@ int main(int argc, char *argv[]) { + std::cout << std::endl; + std::cout << "xeona archive mode : " + << XEONA_ARCHIVE_MODE + << std::endl; + + std::cout << "DT extension mode : " + << DT_CODE + << std::endl; + +#if (XEONA_ARCHIVE_MODE >= 2) + std::string ext = "xml"; +#else + std::string ext = "txt"; +#endif + std::string filename(boost::archive::tmpdir()); filename += "/testfile"; + filename += "."; + filename += ext; + + std::cout << "testfile : " + << filename + << "\n" + << std::endl; // create a new shared pointer to ta new object of type A boost::shared_ptr<A> spa(new A); @@ -94,9 +151,21 @@ // serialize it { std::ofstream ofs(filename.c_str()); + +#if (XEONA_ARCHIVE_MODE >= 2) + boost::archive::xml_oarchive oa(ofs); +#else boost::archive::text_oarchive oa(ofs); +#endif + +#if (XEONA_ARCHIVE_MODE >= 1) + oa << boost::serialization::make_nvp("spa", spa); + oa << boost::serialization::make_nvp("spa1", spa1); +#else oa << spa; oa << spa1; +#endif + } // reset the shared pointer to NULL // thereby destroying the object of type A @@ -108,17 +177,28 @@ { // open the archive std::ifstream ifs(filename.c_str()); + +#if (XEONA_ARCHIVE_MODE >= 2) + boost::archive::xml_iarchive ia(ifs); +#else boost::archive::text_iarchive ia(ifs); +#endif - // restore the schedule from the archive +#if (XEONA_ARCHIVE_MODE >= 1) + ia >> boost::serialization::make_nvp("spa", spa); + ia >> boost::serialization::make_nvp("spa1", spa1); +#else ia >> spa; ia >> spa1; +#endif + } display(spa, spa1); spa.reset(); spa1.reset(); - std::cout << std::endl; +#if (DT_CODE >= 1) + std::cout << std::endl; std::cout << "New tests" << std::endl; @@ -131,17 +211,29 @@ // serialize it { std::ofstream ofs(filename.c_str()); + +#if (XEONA_ARCHIVE_MODE >= 2) + boost::archive::xml_oarchive oa(ofs); +#else boost::archive::text_oarchive oa(ofs); +#endif oa.register_type(static_cast(NULL)); - oa.register_type( - static_cast< - boost::detail::sp_counted_base_impl< - B *, boost::checked_deleter - > * - >(NULL) - ); +// oa.register_type( +// static_cast< +// boost::detail::sp_counted_base_impl< +// B *, boost::checked_deleter +// > * +// >(NULL) +// ); + +#if (XEONA_ARCHIVE_MODE >= 1) + oa << boost::serialization::make_nvp("spa", spa); + oa << boost::serialization::make_nvp("spa1", spa1); +#else oa << spa; oa << spa1; +#endif + } // reset the shared pointer to NULL // thereby destroying the object of type B @@ -153,25 +245,40 @@ { // open the archive std::ifstream ifs(filename.c_str()); + +#if (XEONA_ARCHIVE_MODE >= 2) + boost::archive::xml_iarchive ia(ifs); +#else boost::archive::text_iarchive ia(ifs); +#endif - // restore the schedule from the archive ia.register_type(static_cast(NULL)); - ia.register_type( - static_cast< - boost::detail::sp_counted_base_impl< - B *, boost::checked_deleter - > * - >(NULL) - ); +// ia.register_type( +// static_cast< +// boost::detail::sp_counted_base_impl< +// B *, boost::checked_deleter +// > * +// >(NULL) +// ); + +#if (XEONA_ARCHIVE_MODE >= 1) + ia >> boost::serialization::make_nvp("spa", spa); + ia >> boost::serialization::make_nvp("spa1", spa1); +#else ia >> spa; ia >> spa1; +#endif + } display(spa, spa1); + +#endif // DT code + /////////////// - std::remove(filename.c_str()); + // std::remove(filename.c_str()); // obj of type A gets destroyed // as smart_ptr goes out of scope return 0; } + --- Robbie Morrison PhD student -- policy-oriented energy system simulation Institute for Energy Engineering (IET) Technical University of Berlin (TU-Berlin), Germany University email (redirected) : morrison(a)iet.tu-berlin.de Webmail (preferred) : robbie(a)actrix.co.nz [from IMAP client]

1 0

certain headers missing
by Dragos Sbarlea 21 Aug '07

21 Aug '07

Hello! I am a new Boost user and my question might seem dumb, but please try to help me. I installed boost and I can run the example posted on the boost getting started page successfully, but when I try to use Boost.Process i get an error that the header fiel does not exist. Looking in the boost include files, i see there is no such file as process.hpp and no folder called process ... Where do I do something wrong? (working on Linux with boost from ubuntu 7.04 repos) Thank you for your time! ____________________________________________________________________________________ Be a better Heartthrob. Get better relationship answers from someone who knows. Yahoo! Answers - Check it out. http://answers.yahoo.com/dir/?link=list&sid=396545433

2 1

boost assign: insufficent type error.
by chun ping wang 20 Aug '07

20 Aug '07

heres the code. template <class T> class next { public: next(const int& k) : k_(k), count(0) {} std::complex<T> operator()() { return std::complex<T>(((2.0*PI*k_/Random::randint(k_, 2*k_))*(++count)), 0); } private: static const double PI = 3.141592654; int k_; int count; }; when i tried to do boost::assign::list_of<std::complex<T> >.repeat_func(num_elems, next<T>(num_elems)); I get an error about insuffiecnet contextual information to determine type.

1 1

[boost.iostream & Boost Windows Installer 1.34.1] Trouble during linking
by Marc Viala 20 Aug '07

20 Aug '07

Hi, I've recently downloaded the new Boost 1.34.1 Windows Installer and tried to use it but I've met some linking troubles in conjunction with Boost.Iostream & Zlib compression scheme. To explain that, I've just tried to compile w/ VC++7.1 this code snippet: #include <boost/iostreams/filtering_streambuf.hpp> #include <boost/iostreams/copy.hpp> #include <boost/iostreams/filter/gzip.hpp> #include <iostream> #include <sstream> namespace io = boost::iostreams ; // Zlib compression void compress(std::istream& is, std::ostream& os) { io::filtering_streambuf<io::output> out ; out.push(io::gzip_compressor()) ; out.push(os) ; io::copy(is, out) ; } void main() { } The VC++ linker complains that "boost_zlib-vc71-mt-gd-1_34_1.lib" library can't be opened from the Boost installation library path. I've checked it and didn't find any "boost_zlib*" library in the distribution. I've read the "Getting started documentation" and I've found "no specific configuration" for Boost.Iostream with Zlib. I've surely missed something but... I've also went through the boost user-list archive unsuccessfully. Any help or suggestion will be welcomed Marc Viala

1 0

boost bind beginner throw problem
by Taglioretti Roberto 20 Aug '07

20 Aug '07

Hi, I have a problem with boot bind, in a my class there is this member: void test(int i) throw(Error); If I use bind(&test,obj,_1); I have a compilation error, instead if I change the member in void test(int i); all it works. Could someone help me to use bind with my original member ? I do not understand where is the problem. Thanks SO: windows XP SP2 compiler: VC 7.1 boot version: 1.34.1 -- Roberto *sono affetto da discromatopsia, per favore evitate l'invio di mail o allegati colorati* *I have dyschromatopsia, please do not send coloured text or email and attach*

2 1

ICU and Boost Regex
by Sudarshan Gaikaiwari 20 Aug '07

20 Aug '07

Hello Boost Experts I am trying to use Boost Regex to replace the java.util.regex package. I want to use the Unicode Regular Expressions and need to link with the ICU libraries. However I want to keep the size of my program as small as possible. What components of ICU are essential for Boost regex? What is the ICU configuration that would lead to the smallest ICU binaries that can still be usable by Boost regex? Thanks regards Sudarshan -- Sudarshan Gaikaiwari www.sudarshan.org sudarshan(a)acm.org

2 1

[Fwd: Having trouble with boost thread library]
by Fei Liu 20 Aug '07

20 Aug '07

3 3

serialization - portability
by Stefaan 20 Aug '07

20 Aug '07

Hi! I'm having an issue with archive portability. As I'm quite new to the internals of boost, I hope my attempt at pinpointing the problem is sensible: #include <iostream> #include <boost/serialization/vector.hpp> int main() { std::cerr << boost::serialization::implementation_level <std::vector <long long> >::value << std::endl; return 0; } built on a x86_64 platform prints out "3", on a i386 platform it prints out "2". I tested this both with boost 1.33.1 and 1.34.1. It is my guess that it causes the serialization of the used type to result in a larger archive on x86_64 than on i386. (Which is the original problem that led me to discover this) So my question is: is this the result of a bug in boost? If not, then what is the explanation of this difference? Using linux-2.6 with gcc. Thanks, Stefaan

3 2

Newbie needs yet more help with serialization - BOOST_SERIALIZATION_SPLIT_FREE
by Hector C. 20 Aug '07

20 Aug '07

Hi all, I don't understand why the following code doesn't compile. It gives an strange error: "missing type specifier - int assumed. Note: C++ does not support default-int" Any ideas? --Hector C. #define tpath boost::filesystem::wpath template< class Archive > void save( Archive & x_Stream, const tpath & x_Path, const unsigned int a_Version ) {} BOOST_SERIALIZATION_SPLIT_FREE(tpath) BOOST_CLASS_TRACKING(tpath, boost::serialization::track_never) int wmain(int argc, tchar * argv[]) { tpath tt; std::ofstream off(_T("test.txt"), std::ios_base::binary); boost::archive::binary_oarchive oa((std::ostream &)off); oa << tt; return 0; } ____________________________________________________________________________________ Looking for a deal? Find great prices on flights and hotels with Yahoo! FareChase. http://farechase.yahoo.com/

2 2

Compiling problem, Intel Compiler 9.1, Boost 1.34.1
by Notger Heinz 20 Aug '07

20 Aug '07

Dear community: I have a problem compiling with Intel 9.1 and Boost 1.34.1. It quits with error message, that says it was unable to find the lib libboost_thread-iw-mt-s-1_34_1.lib. Please, can anyone help me with this? Thank you very much in advance N. Heinz.

1 0

Still cannot cross-build boost libs
by Bruce Reid 20 Aug '07

20 Aug '07

I am trying to use linux-x86 platform to cross-build for linux-ppc. I have followed Vladimir’s suggestion to specify my cross-compiler/archiver by updating user-config.jam with: using gcc : : /path/to/my/linux-ppc-g++ : <archiver>/path/to/my/linux-ppc-ar ; I have confirmed this works IF I build one of the [header-only] example programs. This proves that user-config.jam (located in my home directory) is being found, and the compiler/archiver are specified correctly, since the resulting executable runs on the correct target (ppc) platform. However, when attempting to apply the same user-config.jam file to build boost/serialization, it appears my cross-compiler/archiver directives are ignored, and the resulting libraries are in the native x86 format, since attempting to build a program with one of them using my ppc-g++ compiler produces a spew of link errors. Modifying my makefile to use the native g++ compiler permits a successful linkage with the boost/serialization library, and the resulting executable runs fine on the x86 platform. The command I used to build boost/serialization is: bjam --toolset=gcc --with-serialization --prefix=/my/prefix/path --exec-prefix=/my/exec-prefix/path/linux_ppc --libdir=/my/exec-prefix/path/linux_ppc/lib install I also saved the output from the build, but can’t see any clues to explain where things went wrong. Any ideas why I seem to be so close, but still cannot produce boost library binaries for the desired target platform?

5 10

Re: [Boost-users] Serialization newbie needs help
by Dominick Layfield 19 Aug '07

19 Aug '07

Frank Birbacher wrote: > I now noticed that the link I posted does not reference excatly what I > meant to point at. Your code makes me think that you have not read what > I wanted you to read. Here it goes. > > READ THIS: > > http://www.boost.org/libs/serialization/doc/rationale.html#trap Well, Hector may not have read this, but I did! And it seems that I have the same problem as him. If I make the object I want to serialize a const, the (completely incomprehensible) compile error goes away. Any chance this could be added to a boost::serialization FAQ? It appears that I have a choice between (i) doing a const_cast on every object I want to save, and (ii) inserting a BOOST_CLASS_TRACKING(XXX, boost::serialization::track_never) line into my source code. Both are ugly, and although the former might be safe, it certainly looks dangerous! The "Compile time trap" section of the documentation doesn't actually explain what "object tracking" is all about. Neither (amusingly) does the Boost->Serialization->Reference->Special Considerations->Object Tracking section! After re-reading these sections several times, I realized that this is all related to serializing pointers. To my mind, it is not at all intuitive what should happen if I try to serialize a pointer to an object. What Boost::serialization seems to do is to serialize the object itself, but wrapped up in some magic that remembers the object was output/input through a pointer. i.e. if I create a my_class object, then output a pointer to the object, the object itself is output, and when I come to input the pointer, the library silently creates an object of type my_class, then puts a pointer to the object into my pointer. Is that about right? If so, this is (1) not transparent, and (2) seems ludicrously complex. As alluded to in the documentation, this creates a morass of problems (object-tracking, memory leaks etc.). Having said that, I have to applaud the tour-de-force of C++ wizardry required to make all of this magic work. To quote Bjarne Stroustrup, "...but you have to be very clever. If any of you have seen some of the Boost stuff, you don't want to be that clever!" (from his recent Waterloo talk) It seems to me that a cleaner, simpler (and less ambitious) solution would just be to make serialization of pointers an error. What on earth does it actually mean to serialize a pointer? And why would I want to do such a thing, anyway? -- Dominick

3 2

shared_ptr and thread safety
by gast128 19 Aug '07

19 Aug '07

Dear all, it is already posted a dozen times, but still I do not get it. I understand that if you have a class, the shared_ptr will not make this thread safe. That's fair. Non const operations accessed by different threads should still be guarded (and probably their const versions then also). But what about the shared_ptr itself. From the doc's (http://www.boost.org/libs/smart_ptr/shared_ptr.htm#ThreadSafety) I read that reading and writing to the shared_ptr object (not the pointee) is safe: 'A shared_ptr instance can be "read" (accessed using only const operations) simultaneously by multiple threads. Different shared_ptr instances can be "written to" (accessed using mutable operations such as operator= or reset) simultaneosly by multiple threads (even when these instances are copies, and share the same reference count underneath.)' However then a couple of examples are listed where both operator= and a dtor call are marked as undefined, and this is of course the most use (share a shared pointer over multiple threads and let them decide who finishes last, but this is then illegal?) >From the code I see that the ref counting is implemented through atomic inc's and dec's, and I would therefore expect that it is thread safe after all, since only the thread which makes the ref count 0 will be assigned the job of 'dispose', and the ref counting is thread safe. who can help this poor programmer... wkr, me

6 13

Looking for ScopeExit Reviews
by Jody Hagins 19 Aug '07

19 Aug '07

The review ends in three days (on Wednesday). The current collection of reviews is very small, thus I am asking for more reviews of this library. Thanks! >From the original announcement... The review period for Scope Exit Time Series, submitted by Alexander Nasonov, runs from Monday, August 13 until Wednesday, August 22. >From the documentation: Nowadays, every C++ developer is familiar with RAII technique. It binds resource acquisition and release to initialization and destruction of a variable that holds the resource. But there are times when writing a special class for such variable is not worth the effort. This is when ScopeExit macro comes into play. You put resource acquisition directly in your code and next to it you write a code that releases the resource. Note that ScopeExit uses PP macros and relies on Boost.Typeof. The latest version can is here: http://boost-consulting.com/vault/index.php?action=downloadfile&filename=sc… It's available also at http://tinyurl.com/2z6qg2 Online documentation is here: http://194.6.223.221/~nasonov/scope_exit-0.04/libs/scope_exit/doc/html/inde… >From the review guidelines here: http://boost.org/more/formal_review_process.htm ... Boost mailing list members are encouraged to submit Formal Review comments: * Publicly on the mailing list. * Privately to the Review Manager. Private comments to a library submitter may be helpful to her or him, but won't help the Review Manager reach a decision, so the other forms are preferred. What to include in Review Comments Your comments may be brief or lengthy, but basically the Review Manager needs your evaluation of the library. If you identify problems along the way, please note if they are minor, serious, or showstoppers. Here are some questions you might want to answer in your review: * What is your evaluation of the design? * What is your evaluation of the implementation? * What is your evaluation of the documentation? * What is your evaluation of the potential usefulness of the library? * Did you try to use the library? With what compiler? Did you have any problems? * How much effort did you put into your evaluation? A glance? A quick reading? In-depth study? * Are you knowledgeable about the problem domain? And finally, every review should answer this question: * Do you think the library should be accepted as a Boost library? Be sure to say this explicitly so that your other comments don't obscure your overall opinion. Thanks in advance to every for your participation in this review.

1 0

Re: [Boost-users] regex_search on non-NULL terminated strings.
by Anders Dalvander 19 Aug '07

19 Aug '07

> The ideal interface would be: > 1) terminate when NULL character is found > 2) if NULL character not found, terminate when end marker is reached. char buffer[BUFFER_SIZE]; char* buffer_begin = buffer; char* buffer_end = buffer + BUFFER_SIZE; // TODO fill buffer with string. char* string_begin = buffer; char* string_end = std::find(buffer_begin, buffer_end, 0); // TODO call regex with string_begin and string_end. // Anders Dalvander

2 1

Re: [Boost-users] Serialization newbie needs help
by Hector C. 19 Aug '07

19 Aug '07

Robert Ramey wrote: > Actually, I've considered reviewing all the email in this list and > summarizing > the results in a section "Hints and Troubleshooting Tips". I think this > is useful and necessary and useful, but I just havent gotten around to it. > What about documentation using doxygen (in addition to what is already there)? I spent a lot of time reading the code to understand the usage of many things. For example, in current documentation there is no (semi-obvious) place for BOOST_SERIALIZATION_SPLIT. -- Hector C. ____________________________________________________________________________________ Yahoo! oneSearch: Finally, mobile search that gives answers, not web links. http://mobile.yahoo.com/mobileweb/onesearch?refer=1ONXIC

1 0

gregorian date and julian
by thom_schu＠gmx.de 18 Aug '07

18 Aug '07

Hi all, Can anyone tell me how to construct a date (gregorian) with a julian number ? I tried the constructor "date(special_values sv)" and it looked like it would work, but Im not sure if I can do this (what for is this constructor ?) So after taking a look in the source I found another possibility: greg_year_month_day ymd = gregorian_calendar::from_julian_day_number(2443510); date d(ymd); So are both ways right ? thanks in advance -- Der GMX SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen! Ideal für Modem und ISDN: http://www.gmx.net/de/go/smartsurfer

2 1

Re: [Boost-users] Serialization newbie needs help
by Hector C. 18 Aug '07

18 Aug '07

Robert Ramey wrote: Dominick Layfield wrote: Frank Birbacher wrote: I now noticed that the link I posted does not reference excatly whatI meant to point at. Your code makes me think that you have not readwhat I wanted you to read. Here it goes.READ THIS:http://www.boost.org/libs/serialization/doc/rationale.html#trap Well, Hector may not have read this, but I did! C'mon, c'mon ;-) And it seems that Ihave the same problem as him. After I realized what the problem was, I found that it was rathercommon. If I make the object I want toserialize a const, the (completely incomprehensible) compile errorgoes away. Any chance this could be added to a boost::serializationFAQ? you mean change the section named "rationale" to "FAQ"? Perhaps the comments before the trap (code in the hpp file), shouldhave a hyperlink. It appears that I have a choice between (i) doing a const_cast onevery object I want to save, and (ii) inserting aBOOST_CLASS_TRACKING(XXX, boost::serialization::track_never) lineinto my source code. After reading the rationale, I saw that option (ii) allows me topostpone the fight (and I took it). What is more important is that thetrap is there to remember it. Perhaps another solution would be toprovide a base class for tracking objects. This way, instead of usingthe macro, one could derive from such class: class MyClass : private boost::serialization::trackme And this "trackme" class could have parameters in the constructor tosay whether it should be tracked: MyClass()::MyClass() : boost::serialization::trackme(never) {} or MyClass()::MyClass() : boost::serialization::trackme(selectively) {} etc .. This solution would be in addition to the const-reference andBOOST_CLASS_TRACKING ones. It seems to me that a cleaner, simpler (and less ambitious) solutionwould just be to make serialization of pointers an error. I wouldn't do that. C++ must allow me to shot myself if I'm notcareful!! --------------------------------- Take the Internet to Go: Yahoo!Go puts the Internet in your pocket: mail, news, photos & more.

1 0

Serialization newbie needs YET MORE help
by Hector C. 18 Aug '07

18 Aug '07

Hi all, Can anyone give any ideas why uncommenting the #define will give me errors? --Hector C. //#define GiveMeErrors #include <fstream> #ifdef GiveMeErrors # include <boost/archive/binary_woarchive.hpp> #else # include <boost/archive/binary_oarchive.hpp> #endif int main(int argc, char * argv[]) { #ifdef GiveMeErrors std::wofstream off("test.txt", std::ios_base::binary); boost::archive::binary_woarchive oa((std::wostream &)off); #else std::ofstream off("test.txt", std::ios::binary); boost::archive::binary_oarchive oa((std::ostream &)off); #endif return 0; } ---------------------------------- ____________________________________________________________________________________ Take the Internet to Go: Yahoo!Go puts the Internet in your pocket: mail, news, photos & more. http://mobile.yahoo.com/go?refer=1GNXIC

3 2

regex_search all
by izua 18 Aug '07

18 Aug '07

Hi everyone! I'm Richard from romania, and I'm pretty new to boost. I started using it because I need regex functionalities. Is there a regex_search functionality that will show me all found entries for the given regular expression? Something like preg_match_all in PHP? For example, if i have a regex ([0-9]+?[\W]+?) and the search string "abcd123.ef56[tab]essn" it would return me 2 arrays of arrays: first with an array 123 and ., second with 56 and tab. Thanks. -- View this message in context: http://www.nabble.com/regex_search-all-tf4285608.html#a12199378 Sent from the Boost - Users mailing list archive at Nabble.com.

3 7

asio example compile error
by ope 18 Aug '07

18 Aug '07

Hi, I try to compile the asio example at http://asio.sourceforge.net/boost_asio_0_3_7/libs/asio/doc/tutorial/tuttime… using boost svn trunk; as well as the the 1.34.1 The error attached occoured. What did I wrong? All headers seems to be found. Thanks, Olaf $ g++ -I boost-trunk/ t1.cpp ./boost-trunk/libs/system/src/error_code.cpp -o t1 boost-trunk/boost/asio/detail/bind_handler.hpp: In member function »void boost::asio::detail::binder1<Handler, Arg1>::operator()() [with Handler = void (*)(const boost::asio::error&), Arg1 = boost::system::error_code]«: boost-trunk/boost/asio/handler_invoke_hook.hpp:63: instantiated from »void boost::asio::asio_handler_invoke(Function, ...) [with Function = boost::asio::detail::binder1<void (*)(const boost::asio::error&), boost::system::error_code>]« boost-trunk/boost/asio/detail/handler_invoke_helpers.hpp:39: instantiated from »void asio_handler_invoke_helpers::invoke(const Function&, Context*) [with Function = boost::asio::detail::binder1<void (*)(const boost::asio::error&), boost::system::error_code>, Context = void (*)(const boost::asio::error&)]« boost-trunk/boost/asio/detail/bind_handler.hpp:72: instantiated from »void boost::asio::detail::asio_handler_invoke(const Function&, boost::asio::detail::binder1<Handler, Arg1>*) [with Function = boost::asio::detail::binder1<void (*)(const boost::asio::error&), boost::system::error_code>, Handler = void (*)(const boost::asio::error&), Arg1 = boost::system::error_code]« boost-trunk/boost/asio/detail/handler_invoke_helpers.hpp:39: instantiated from »void asio_handler_invoke_helpers::invoke(const Function&, Context*) [with Function = boost::asio::detail::binder1<void (*)(const boost::asio::error&), boost::system::error_code>, Context = boost::asio::detail::binder1<void (*)(const boost::asio::error&), boost::system::error_code>]« boost-trunk/boost/asio/detail/task_io_service.hpp:412: instantiated from »static void boost::asio::detail::task_io_service<Task>::handler_wrapper<Handler>::do_call(boost::asio::detail::task_io_service<Task>::handler_base*) [with Handler = boost::asio::detail::binder1<void (*)(const boost::asio::error&), boost::system::error_code>, Task = boost::asio::detail::epoll_reactor<false>]« boost-trunk/boost/asio/detail/task_io_service.hpp:392: instantiated from »boost::asio::detail::task_io_service<Task>::handler_wrapper<Handler>::handler_wrapper(Handler) [with Handler = boost::asio::detail::binder1<void (*)(const boost::asio::error&), boost::system::error_code>, Task = boost::asio::detail::epoll_reactor<false>]« boost-trunk/boost/asio/detail/handler_alloc_helpers.hpp:138: instantiated from »boost::asio::detail::handler_ptr<Alloc_Traits>::handler_ptr(boost::asio::detail::raw_handler_ptr<Alloc_Traits>&, Arg1&) [with Arg1 = boost::asio::detail::binder1<void (*)(const boost::asio::error&), boost::system::error_code>, Alloc_Traits = boost::asio::detail::handler_alloc_traits<boost::asio::detail::binder1<void (*)(const boost::asio::error&), boost::system::error_code>, boost::asio::detail::task_io_service<boost::asio::detail::epoll_reactor<false> >::handler_wrapper<boost::asio::detail::binder1<void (*)(const boost::asio::error&), boost::system::error_code> > >]« boost-trunk/boost/asio/detail/task_io_service.hpp:180: instantiated from »void boost::asio::detail::task_io_service<Task>::post(Handler) [with Handler = boost::asio::detail::binder1<void (*)(const boost::asio::error&), boost::system::error_code>, Task = boost::asio::detail::epoll_reactor<false>]« boost-trunk/boost/asio/impl/io_service.ipp:125: instantiated from »void boost::asio::io_service::post(Handler) [with CompletionHandler = boost::asio::detail::binder1<void (*)(const boost::asio::error&), boost::system::error_code>]« boost-trunk/boost/asio/detail/deadline_timer_service.hpp:169: instantiated from »void boost::asio::detail::deadline_timer_service<Time_Traits, Timer_Scheduler>::wait_handler<Handler>::operator()(const boost::system::error_code&) [with Handler = void (*)(const boost::asio::error&), Time_Traits = boost::asio::time_traits<boost::posix_time::ptime>, Timer_Scheduler = boost::asio::detail::epoll_reactor<false>]« boost-trunk/boost/asio/detail/timer_queue.hpp:277: instantiated from »static void boost::asio::detail::timer_queue<Time_Traits>::timer<Handler>::invoke_handler(boost::asio::detail::timer_queue<Time_Traits>::timer_base*, const boost::system::error_code&) [with Handler = boost::asio::detail::deadline_timer_service<boost::asio::time_traits<boost::posix_time::ptime>, boost::asio::detail::epoll_reactor<false> >::wait_handler<void (*)(const boost::asio::error&)>, Time_Traits = boost::asio::time_traits<boost::posix_time::ptime>]« boost-trunk/boost/asio/detail/timer_queue.hpp:269: instantiated from »boost::asio::detail::timer_queue<Time_Traits>::timer<Handler>::timer(const typename Time_Traits::time_type&, Handler, void*) [with Handler = boost::asio::detail::deadline_timer_service<boost::asio::time_traits<boost::posix_time::ptime>, boost::asio::detail::epoll_reactor<false> >::wait_handler<void (*)(const boost::asio::error&)>, Time_Traits = boost::asio::time_traits<boost::posix_time::ptime>]« boost-trunk/boost/asio/detail/timer_queue.hpp:70: instantiated from »bool boost::asio::detail::timer_queue<Time_Traits>::enqueue_timer(const typename Time_Traits::time_type&, Handler, void*) [with Handler = boost::asio::detail::deadline_timer_service<boost::asio::time_traits<boost::posix_time::ptime>, boost::asio::detail::epoll_reactor<false> >::wait_handler<void (*)(const boost::asio::error&)>, Time_Traits = boost::asio::time_traits<boost::posix_time::ptime>]« boost-trunk/boost/asio/detail/epoll_reactor.hpp:325: instantiated from »void boost::asio::detail::epoll_reactor<Own_Thread>::schedule_timer(boost::asio::detail::timer_queue<Time_Traits>&, const typename Time_Traits::time_type&, Handler, void*) [with Time_Traits = boost::asio::time_traits<boost::posix_time::ptime>, Handler = boost::asio::detail::deadline_timer_service<boost::asio::time_traits<boost::posix_time::ptime>, boost::asio::detail::epoll_reactor<false> >::wait_handler<void (*)(const boost::asio::error&)>, bool Own_Thread = false]« boost-trunk/boost/asio/detail/deadline_timer_service.hpp:183: instantiated from »void boost::asio::detail::deadline_timer_service<Time_Traits, Timer_Scheduler>::async_wait(boost::asio::detail::deadline_timer_service<Time_Traits, Timer_Scheduler>::implementation_type&, Handler) [with Handler = void (*)(const boost::asio::error&), Time_Traits = boost::asio::time_traits<boost::posix_time::ptime>, Timer_Scheduler = boost::asio::detail::epoll_reactor<false>]« boost-trunk/boost/asio/deadline_timer_service.hpp:153: instantiated from »void boost::asio::deadline_timer_service<TimeType, TimeTraits>::async_wait(typename boost::asio::detail::deadline_timer_service<TimeTraits, boost::asio::detail::epoll_reactor<false> >::implementation_type&, WaitHandler) [with WaitHandler = void (*)(const boost::asio::error&), TimeType = boost::posix_time::ptime, TimeTraits = boost::asio::time_traits<boost::posix_time::ptime>]« boost-trunk/boost/asio/basic_deadline_timer.hpp:374: instantiated from »void boost::asio::basic_deadline_timer<Time, TimeTraits, TimerService>::async_wait(WaitHandler) [with WaitHandler = void (*)(const boost::asio::error&), Time = boost::posix_time::ptime, TimeTraits = boost::asio::time_traits<boost::posix_time::ptime>, TimerService = boost::asio::deadline_timer_service<boost::posix_time::ptime, boost::asio::time_traits<boost::posix_time::ptime> >]« t1.cpp:15: instantiated from here boost-trunk/boost/asio/detail/bind_handler.hpp:39: Fehler: ungültige Initialisierung einer Referenz des Typs »const boost::asio::error&« von Ausdruck des Typs »boost::system::error_code«

1 0

oarchive and woarchive in different headers
by Hector C. 18 Aug '07

18 Aug '07

Hi all, Why is it that boost::archive::binary_oarchive and binary_woarchive require different headers? Isn't this against the custom in other headers, e.g. both string and wstring are defined in <string>. -- Hector C. ---------------------------------- ____________________________________________________________________________________ Be a better Globetrotter. Get better travel answers from someone who knows. Yahoo! Answers - Check it out. http://answers.yahoo.com/dir/?link=list&sid=396545469

1 0

Serialization library build problems
by Dominick Layfield 18 Aug '07

18 Aug '07

When I try to compile an application that uses the Boost serialization library, I get some compilation errors that I don't understand. I've taken the code, and trimmed it down to the simplest possible case that produces the same error. Here's the code: // Test of Boost serialization library #include <sstream> #include <boost/archive/text_oarchive.hpp> class test_t { public: int i; template <class Archive> void serialize(Archive& ar, const unsigned int version ) { ar & i; } test_t(int _i) : i(_i) {}; }; int main(void) { std::ostringstream oss; boost::archive::text_oarchive oa(oss); test_t test(1); oa << test; return 0; } When I compile this (gcc 4.1.2, Boost 1.33.1, under Fedora 7), I get the following error: g++ serialization_test.cpp -l boost_serialization /usr/include/boost/archive/detail/oserializer.hpp: In function ‘void boost::archive::save(Archive&, T&) [with Archive = boost::archive::text_oarchive, T = test_t]’: /usr/include/boost/archive/basic_text_oarchive.hpp:78: instantiated from ‘void boost::archive::basic_text_oarchive<Archive>::save_override(T&, int) [with T = test_t, Archive = boost::archive::text_oarchive]’ /usr/include/boost/archive/detail/interface_oarchive.hpp:78: instantiated from ‘Archive& boost::archive::detail::interface_oarchive<Archive>::operator<<(T&) [with T = test_t, Archive = boost::archive::text_oarchive]’ serialization_test.cpp:21: instantiated from here /usr/include/boost/archive/detail/oserializer.hpp:567: error: invalid application of ‘sizeof’ to incomplete type ‘boost::STATIC_ASSERTION_FAILURE<false>’ Can someone explain to me WTF is going on? That error makes absolutely no sense at all to me, and I'm at my wits end! Thanks, -- Dominick

2 1

Serialization newbie needs help
by Hector C. 18 Aug '07

18 Aug '07

Hi all, I just cannot understand why the following code fails to compile. I have read the help files, did my Google, stared at it for hours, etc. But I cannot make sense. It compiles to the following message. Any ideas will be appreciated, --Hector C. ----MESSAGE---- // if your program traps here, it indicates taht your doing one of the following: // a) serializing an object of a type marked "track_never" through a pointer. // b) saving an non-const object of a type not markd "track_never) // Either of these conditions may be an indicator of an error usage of the // serialization library and should be double checked. See documentation on // object tracking. --END MESSAGE-- ----CODE---- #include <iomanip> #include <iostream> #include <fstream> #include <string> #include <boost/archive/text_iarchive.hpp> #include <boost/archive/text_oarchive.hpp> #include <boost/serialization/base_object.hpp> #include <boost/serialization/utility.hpp> #include <boost/serialization/list.hpp> using namespace std; class A { public: string m; A(){}; private: friend class boost::serialization::access; template<class Archive> void serialize(Archive & ar, const unsigned int version) { ar & m; } }; int main(int argc, char * argv[]) { A a; { ofstream off("test.txt"); boost::archive::text_oarchive oa(off); //Uncommenting any of the following lines //produces compilation errors //oa << a; //oa << (const A) a; } return 0; } ---END CODE--- ---------------------------------- ____________________________________________________________________________________ Building a website is a piece of cake. Yahoo! Small Business gives you all the tools to get online. http://smallbusiness.yahoo.com/webhosting

3 4

where is Accumulators library?
by Frank Birbacher 17 Aug '07

17 Aug '07

Hi! The Accumulators library from Eric Niebler has been accepted for boost on February 19th. Now I cannot find evidence anywhere in boost: - neither the release has it - nor the CVS - nor the sandbox SVN I want to use this library. How? Frank

6 16

wide char i/o problem.
by chun ping wang 17 Aug '07

17 Aug '07

while trying to compile boost i get several failure. ...failed gcc.compile.c++ bin.v2\libs\serialization\build\gcc-mingw-3.4.5\releas e\link-static\runtime-link-static\text_wiarchive.o... gcc.compile.c++ bin.v2\libs\serialization\build\gcc-mingw-3.4.5\release\link-sta tic\runtime-link-static\text_woarchive.o libs\serialization\src\text_woarchive.cpp:13:2: #error "wide char i/o not suppor ted on this platform" "C:/mingw/bin/gcc" -ftemplate-depth-128 -O3 -finline-functions -Wno-inline -Wall -DBOOST_ALL_NO_LIB=1 -DNDEBUG -I"." -c -o " bin.v2\libs\serialization\bui ld\gcc-mingw-3.4.5\release\link-static\runtime-link-static\text_woarchive.o" "li bs\serialization\src\text_woarchive.cpp" ...failed gcc.compile.c++ bin.v2\libs\serialization\build\gcc-mingw-3.4.5\releas e\link-static\runtime-link-static\text_woarchive.o... gcc.compile.c++ bin.v2\libs\serialization\build\gcc-mingw-3.4.5\release\link-sta tic\runtime-link-static\xml_wgrammar.o libs\serialization\src\xml_wgrammar.cpp:14:2: #error "wide char i/o not supporte d on this platform" is their any ways for fix around this? using gcc mingw 3.4.5

6 7

[boost-users] boost assignment problem on non primitive type.
by chun ping wang 17 Aug '07

17 Aug '07

Question 1. std::vector<Roles> vr; the constructor for Roles: enum Role { .....}; explicit Roles (const std::string& usr, const Role& r); How would I use boost::assign::list_of to assign a vector of Roles instead of doing regular vector push_back. Question 2. Related. I have a Hash map i.e. boost::unordered_map<std::string, compositionType> and i want to use boost::map_list_of how would i do that. Question 3. trying to use operator += in boost::assignment i get error specifying unknown types. typedef boost::function<std::vector<int>(std::vector<int>)> sortfunc; std::vector<sortfunc> function_list; // quicksort random function_list += (&quicksort<QSTYPE(RANDOM), int, std::vector>) // quicksort median (&quicksort<QSTYPE(MEDIAN), int, std::vector>) // error here. // quicksort mediantriple (&quicksort<QSTYPE(MEDIANTRIPLE), int, std::vector>) // merge sort (&mergesort<int, std::vector>) // heap sort (&heapsort<int, std::vector>) // selection sort (&selection_sort<int, std::vector>) // standard sort (&standard_sort<int, std::vector>); Thanks for any help in advanced.

2 2

Re: [Boost-users] Time Series review results
by David Abrahams 17 Aug '07

17 Aug '07

on Fri Aug 17 2007, John Phillips <phillips-AT-delos.mps.ohio-state.edu> wrote: > list. However, for the sake of easy > reference I will list the major points and my current understanding of > what to do about them below. The order in which the points are presented > should not be taken as a rating of importance: it is just the order I > made notes about them as I reviewed the discussion. > <snip> > 32) Consider whether users need access to the metafunctions used to > determine return types. If so, consider how they could be exposed in a > user friendly way. If I may, 33) The PropertyMap concept used in the library needs to be renamed or reconceived to avoid clashing with the Boost PropertyMap library. This one is my fault, which is why I'm very conscious of it. -- Dave Abrahams Boost Consulting http://www.boost-consulting.com The Astoria Seminar ==> http://www.astoriaseminar.com

1 0

How to compile Boost for use with MinGW in Linux
by Ravi kumar Singh 17 Aug '07

17 Aug '07

I want to use Boost libraries with my MinGW compiler installed in my Linux Desktop, since I want to cross-compile a few programs for ms-windows. Though I have Boost installed in my system for native compilation, but I am unable to compile it for MinGW. Recently I have tried to compile Boost for MinGW, first by executing the following commands :- export CC=i586-mingw32msvc-gcc export CXX=i586-mingw32msvc-c++ export LD=i586-mingw32msvc-ld export AR=i586-mingw32msvc-ar export AS=i586-mingw32msvc-as export NM=i586-mingw32msvc-nm export STRIP=i586-mingw32msvc-strip export RANLIB=i586-mingw32msvc-ranlib export DLLTOOL=i586-mingw32msvc-dlltool export OBJDUMP=i586-mingw32msvc-objdump export RESCOMP=i586-mingw32msvc-windres and then :- ./configure make but it still produced native libraries..... Please tell me how to achieve that, or if you have any link where I can find proper instructions to do so. Thanks --------------------------------- Why delete messages? Unlimited storage is just a click away.

1 0

[statechart] using events for passing information
by "Christian Bähnisch" 17 Aug '07

17 Aug '07

Hello, I wonder if it is possible to use events for passing in data to states. I even cannot find some hints in the statechart documentation how to determine in some state which event caused a transistion to the this state! regards, chris -- Der GMX SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen! Ideal für Modem und ISDN: http://www.gmx.net/de/go/smartsurfer

3 3

Passing user defined visitor for breadth_first_search
by Sourabh 17 Aug '07

17 Aug '07

Hi, I am using the boost graph (adjacency_list) and want to perform BFS on that. I am constructing the graph, passing VertexProperty as a structure (bundled_properties). When I try to modify the structure in my own bfs visitior (in the overriden function discover_vertex), the compiler says the structure (representing the vertex property) is readonly. I had to switch to const_cast of that structure, but it is not elegant. Can anyone help me through this? Regards, Sourabh

2 1

Boost.Test Documentation
by James Hamlin 17 Aug '07

17 Aug '07

Hi, I've begun using Boost.Test to construct test suites for a project, and it looks like it does a great job and is full of nice features (I really like the auto unit tests). But I have a big complaint: the documentation is pretty poor. I had a hard time getting a simple example off the ground, because it wasn't clear that I had to link to parts of the library. This was a surprise since most of Boost is templated and so is available entirely through the headers. I had to dig a bit to find the comment about the header that includes the main() code and other concrete functions. In addition, many of the examples are missing, and some of those that are available require the linking I mentioned but fail to note this, adding to my initial confusion. Lastly, the English grammar is very rough in parts, and while I understand that English may not be the primary language of the author, it can be a big hurdle to get started using the library when one has to grapple with the documentation to understand the intentions of the author. I don't mean to rant - the library is great, and I've already found it useful - but I'd love to get more out of it, and clean, clear, and thorough documentation will get me and others started with much less head scratching and frustration.<boost-test%20at%20emailaccount%20dot%20com%20%28please%20unobscure%29> Sincerely, James Hamlin Postscript: This is Boost-users, but I assume Gennadiy Rozental or somebody else with the knowledge and ability to update the documentation will see this message.

8 17

[multi_array]BOOST_NO_SFINAE Warnings
by Mark Ruzon 16 Aug '07

16 Aug '07

I recently upgraded to 1.34.1, gcc 3.4.6, and certain new changes in multi_array don't make sense to me: In view.hpp: template <class BaseList> #ifdef BOOST_NO_SFINAE void #else typename disable_if<typename boost::is_integral<BaseList>::type,void >::type #endif reindex(const BaseList& values) { boost::function_requires< detail::multi_array::CollectionConcept<BaseList> >(); boost::detail::multi_array:: copy_n(values.begin(),num_dimensions(),index_base_list_.begin()); origin_offset_ = this->calculate_indexing_offset(stride_list_,index_base_list_); } multi_array_ref.hpp has a similar function except for the last function call. Both give me warnings because BOOST_NO_SFINAE is not defined, and so reindex has a non-void return type but does not actually return anything. I can get rid of it by #defining this constant, but it seems like a bug in the code. Will someone more knowledgeable shed some light on this, please? Do I need to #define BOOST_NO_SFINAE? Thanks, Mark Ruzon P.S. Apologies if this is the second post asking this question.

1 0

[iostreams] file sink/source and wide char paths?
by Michael Ellery 16 Aug '07

16 Aug '07

it looks like the file_sink and file_source classes in iostreams take std::string for the file path. Was this intentional? I'm not sure what the consensus is on wide char file system paths, but it seems like they are supported by the filesystem package, for instance. Should I just convert my wide char paths to narrow char when it comes to using them with file_sink/file_source -- or is there a better way? Thanks, Mike Ellery

1 0

Unregistered Class Exception - Boost Serialization
by Jason Gorski 16 Aug '07

16 Aug '07

Hello, I have been using the Boost Serialization libraries on a project of mine and so far they have worked very well. However, I have been unable to properly load derived objects using a base class pointer. The following code generates an unregistered class exception: #include <iostream> #include <sstream> #include <iomanip> #include <string> #include <sstream> #include <boost/archive/text_oarchive.hpp> #include <boost/archive/text_iarchive.hpp> #include <boost/serialization/export.hpp> class Base_Class { public: friend class boost::serialization::access; template<class Archive> void serialize(Archive & ar, const unsigned int version) { // empty } virtual void print()=0; }; class Derived_Class: public Base_Class { public: int i1; int i2; int i3; friend class boost::serialization::access; template<class Archive> void serialize(Archive & ar, const unsigned int version) { ar & boost::serialization::base_object<Base_Class>(*this); ar & i1; ar & i2; ar & i3; } void print(){ std::cout << "i am a derived class object" << std::endl; } }; BOOST_CLASS_EXPORT(Derived_Class) /***************************************** Main *****************************************/ int main() { Derived_Class derived_send; derived_send.i1=12; derived_send.i2=13; derived_send.i3=14; Base_Class * base_ptr; Derived_Class * derived_recv; // save derived class std::ostringstream output_stream; boost::archive::text_oarchive output_archive( output_stream ); output_archive & derived_send; // load using base class ptr std::istringstream input_stream( output_stream.str() ); boost::archive::text_iarchive input_archive( input_stream ); input_archive & base_ptr; derived_recv = (Derived_Class*) base_ptr; derived_recv->print(); } From reading the documentation, it seems as if this should work fine. Am I missing something? Thanks in advance, Jason -- Jason Gorski Research Engineer Oasis Advanced Engineering, Inc. (248)373-9800 x 269 gorski(a)OasisAdvancedEngineering.com

2 3

asio example compile error
by ope 16 Aug '07

16 Aug '07

Hi, I try to compile the asio example at http://asio.sourceforge.net/boost_asio_0_3_7/libs/asio/doc/tutorial/tuttime… using boost 1.34.0 with latest sf.com release of boost_asio in directory extra/boost and lib_system of asio is in directory build/lib. The error attached occoured. What did I wrong? All headers seems to be found. Thanks, Olaf $ g++ asio.cpp -o asio -I /usr/local/include/ -I extra/boost/ -L build/lib/ -static -lboost_system-gcc41-mt-0_1 extra/boost/boost/asio/detail/bind_handler.hpp: In member function »void boost::asio::detail::binder1<Handler, Arg1>::operator()() [with Handler = void (*)(const boost::asio::error&), Arg1 = boost::system::error_code]«: extra/boost/boost/asio/handler_invoke_hook.hpp:63: instantiated from »void boost::asio::asio_handler_invoke(Function, ...) [with Function = boost::asio::detail::binder1<void (*)(const boost::asio::error&), boost::system::error_code>]« extra/boost/boost/asio/detail/handler_invoke_helpers.hpp:39: instantiated from »void asio_handler_invoke_helpers::invoke(const Function&, Context*) [with Function = boost::asio::detail::binder1<void (*)(const boost::asio::error&), boost::system::error_code>, Context = void (*)(const boost::asio::error&)]« extra/boost/boost/asio/detail/bind_handler.hpp:72: instantiated from »void boost::asio::detail::asio_handler_invoke(const Function&, boost::asio::detail::binder1<Handler, Arg1>*) [with Function = boost::asio::detail::binder1<void (*)(const boost::asio::error&), boost::system::error_code>, Handler = void (*)(const boost::asio::error&), Arg1 = boost::system::error_code]« extra/boost/boost/asio/detail/handler_invoke_helpers.hpp:39: instantiated from »void asio_handler_invoke_helpers::invoke(const Function&, Context*) [with Function = boost::asio::detail::binder1<void (*)(const boost::asio::error&), boost::system::error_code>, Context = boost::asio::detail::binder1<void (*)(const boost::asio::error&), boost::system::error_code>]« extra/boost/boost/asio/detail/task_io_service.hpp:412: instantiated from »static void boost::asio::detail::task_io_service<Task>::handler_wrapper<Handler>::do_call(boost::asio::detail::task_io_service<Task>::handler_base*) [with Handler = boost::asio::detail::binder1<void (*)(const boost::asio::error&), boost::system::error_code>, Task = boost::asio::detail::epoll_reactor<false>]« extra/boost/boost/asio/detail/task_io_service.hpp:392: instantiated from »boost::asio::detail::task_io_service<Task>::handler_wrapper<Handler>::handler_wrapper(Handler) [with Handler = boost::asio::detail::binder1<void (*)(const boost::asio::error&), boost::system::error_code>, Task = boost::asio::detail::epoll_reactor<false>]« extra/boost/boost/asio/detail/handler_alloc_helpers.hpp:138: instantiated from »boost::asio::detail::handler_ptr<Alloc_Traits>::handler_ptr(boost::asio::detail::raw_handler_ptr<Alloc_Traits>&, Arg1&) [with Arg1 = boost::asio::detail::binder1<void (*)(const boost::asio::error&), boost::system::error_code>, Alloc_Traits = boost::asio::detail::handler_alloc_traits<boost::asio::detail::binder1<void (*)(const boost::asio::error&), boost::system::error_code>, boost::asio::detail::task_io_service<boost::asio::detail::epoll_reactor<false> >::handler_wrapper<boost::asio::detail::binder1<void (*)(const boost::asio::error&), boost::system::error_code> > >]« extra/boost/boost/asio/detail/task_io_service.hpp:180: instantiated from »void boost::asio::detail::task_io_service<Task>::post(Handler) [with Handler = boost::asio::detail::binder1<void (*)(const boost::asio::error&), boost::system::error_code>, Task = boost::asio::detail::epoll_reactor<false>]« extra/boost/boost/asio/impl/io_service.ipp:125: instantiated from »void boost::asio::io_service::post(Handler) [with CompletionHandler = boost::asio::detail::binder1<void (*)(const boost::asio::error&), boost::system::error_code>]« extra/boost/boost/asio/detail/deadline_timer_service.hpp:169: instantiated from »void boost::asio::detail::deadline_timer_service<Time_Traits, Timer_Scheduler>::wait_handler<Handler>::operator()(const boost::system::error_code&) [with Handler = void (*)(const boost::asio::error&), Time_Traits = boost::asio::time_traits<boost::posix_time::ptime>, Timer_Scheduler = boost::asio::detail::epoll_reactor<false>]« extra/boost/boost/asio/detail/timer_queue.hpp:243: instantiated from »static void boost::asio::detail::timer_queue<Time_Traits>::timer<Handler>::invoke_handler(boost::asio::detail::timer_queue<Time_Traits>::timer_base*, const boost::system::error_code&) [with Handler = boost::asio::detail::deadline_timer_service<boost::asio::time_traits<boost::posix_time::ptime>, boost::asio::detail::epoll_reactor<false> >::wait_handler<void (*)(const boost::asio::error&)>, Time_Traits = boost::asio::time_traits<boost::posix_time::ptime>]« extra/boost/boost/asio/detail/timer_queue.hpp:234: instantiated from »boost::asio::detail::timer_queue<Time_Traits>::timer<Handler>::timer(const typename Time_Traits::time_type&, Handler, void*) [with Handler = boost::asio::detail::deadline_timer_service<boost::asio::time_traits<boost::posix_time::ptime>, boost::asio::detail::epoll_reactor<false> >::wait_handler<void (*)(const boost::asio::error&)>, Time_Traits = boost::asio::time_traits<boost::posix_time::ptime>]« extra/boost/boost/asio/detail/timer_queue.hpp:68: instantiated from »bool boost::asio::detail::timer_queue<Time_Traits>::enqueue_timer(const typename Time_Traits::time_type&, Handler, void*) [with Handler = boost::asio::detail::deadline_timer_service<boost::asio::time_traits<boost::posix_time::ptime>, boost::asio::detail::epoll_reactor<false> >::wait_handler<void (*)(const boost::asio::error&)>, Time_Traits = boost::asio::time_traits<boost::posix_time::ptime>]« extra/boost/boost/asio/detail/epoll_reactor.hpp:325: instantiated from »void boost::asio::detail::epoll_reactor<Own_Thread>::schedule_timer(boost::asio::detail::timer_queue<Time_Traits>&, const typename Time_Traits::time_type&, Handler, void*) [with Time_Traits = boost::asio::time_traits<boost::posix_time::ptime>, Handler = boost::asio::detail::deadline_timer_service<boost::asio::time_traits<boost::posix_time::ptime>, boost::asio::detail::epoll_reactor<false> >::wait_handler<void (*)(const boost::asio::error&)>, bool Own_Thread = false]« extra/boost/boost/asio/detail/deadline_timer_service.hpp:183: instantiated from »void boost::asio::detail::deadline_timer_service<Time_Traits, Timer_Scheduler>::async_wait(boost::asio::detail::deadline_timer_service<Time_Traits, Timer_Scheduler>::implementation_type&, Handler) [with Handler = void (*)(const boost::asio::error&), Time_Traits = boost::asio::time_traits<boost::posix_time::ptime>, Timer_Scheduler = boost::asio::detail::epoll_reactor<false>]« extra/boost/boost/asio/deadline_timer_service.hpp:153: instantiated from »void boost::asio::deadline_timer_service<TimeType, TimeTraits>::async_wait(typename boost::asio::detail::deadline_timer_service<TimeTraits, boost::asio::detail::epoll_reactor<false> >::implementation_type&, WaitHandler) [with WaitHandler = void (*)(const boost::asio::error&), TimeType = boost::posix_time::ptime, TimeTraits = boost::asio::time_traits<boost::posix_time::ptime>]« extra/boost/boost/asio/basic_deadline_timer.hpp:374: instantiated from »void boost::asio::basic_deadline_timer<Time, TimeTraits, TimerService>::async_wait(WaitHandler) [with WaitHandler = void (*)(const boost::asio::error&), Time = boost::posix_time::ptime, TimeTraits = boost::asio::time_traits<boost::posix_time::ptime>, TimerService = boost::asio::deadline_timer_service<boost::posix_time::ptime, boost::asio::time_traits<boost::posix_time::ptime> >]« asio.cpp:15: instantiated from here extra/boost/boost/asio/detail/bind_handler.hpp:39: Fehler: ungültige Initialisierung einer Referenz des Typs »const boost::asio::error&« von Ausdruck des Typs »boost::system::error_code«

1 0

[Announcement] Boost joins the Software Freedom Conservancy
by Beman Dawes 16 Aug '07

16 Aug '07

Effective August 10th, 2007, Boost became a member project of the Software Freedom Conservancy, http://conservancy.softwarefreedom.org. This means that Boost is now part of a legal entity under US law, and tax-exempt under section 501(c)(3) of the US tax regulations. Although this doesn't have much short-term effect, it lets us move forward with BoostCon 2008 planning with less administrative delay. Long-term, being part of a non-profit organization allows Boost to continue to grow and prosper, and to raise money if that becomes useful. After considering the option of starting our own foundation (a huge amount of work), the Boost moderators decided that joining the Software Freedom Conservancy was a better option. The SFC provides the same legal abilities of a foundation at NO cost to the Boost project. It also minimizes the amount of legal and administrative hassles for project members -- allowing us to stay focused on technical matters rather than tax law. In addition, we are free to leave the SFC and create our own foundation at a later time if we decide that the SFC is not serving us well. Boost is not alone -- some other well known open source projects have also joined the SFC (eg: Samba, Wine). For those interested in the details, see a copy of the legal agreement at svn.boost.org/svn/boost/trunk/more/BoostSponsorshipAgreement.pdf I signed for Boost, since I was the founder and am the owner of the boost.org domain name. Dave Abrahams gets the credit for working out the details of the SFC agreement, with the help of the other moderators. --Beman

1 0

Boost Serialization tracking issues
by gast128 16 Aug '07

16 Aug '07

Dear all, I was trying to use the Boost Serialization library again, but I ran into a problem which cost me a full day. The Boost Serialization library is a very handy library, but often when I use it I run into problems which cost me days. This time I try to serialize just 'track_never' objects. First of all the compiler firewall which is built in the library does not work when using the nvp macro: void Foo() { boost::archive::xml_oarchive oa(...) SomeStruct s; oa << s; // compile time error oa << BOOST_SERIALIZATION_NVP(s); //ok } But this wasn't the real problem. I was looping to serialize non tracking objects: void Bla() { boost::archive::xml_oarchive oa(...) for (int i = 0; i < 1000; ++i) { const SomeStruct s; oa << s; } } However the library did track them by pointer due to a previous request to serialize a pointer. It decides this on a call to 'basic_serializer::serialized_as_pointer' deep in the library. struct SomeStructHolder { SomeStructHolder() : m_p(NULL){} template <class Archive> void serialize(Archive& ar, const unsigned int /*version*/) { ar & BOOST_SERIALIZATION_NVP(m_p); } const SomeStruct* m_p; }; somewhere else: void Bla() { boost::archive::xml_oarchive oa(...) const SomeStructHolder holder; oa << holder; } So this is again an unexpected property of the library. Maybe the ambition for automatic object tracking is too high, and specify it explicitly per class / per archiving operation would be more work for the user, but also clearer. And still the original problem was too find out if Boost Serialization could also be used on a per demand loading of (value-)objects: in my problem the final storage can be potential bigger than computer memory, so I was wondering if objects could be loaded on demand (instead of all in once). wkr, me

3 9

ScopeExit Review Reminder
by Jody Hagins 16 Aug '07

16 Aug '07

We have received only a few reviews so far. The review ends in less than a week, so time is running short. Thanks! >From the original announcement... The review period for Scope Exit Time Series, submitted by Alexander Nasonov, runs from Monday, August 13 until Wednesday, August 22. >From the documentation: Nowadays, every C++ developer is familiar with RAII technique. It binds resource acquisition and release to initialization and destruction of a variable that holds the resource. But there are times when writing a special class for such variable is not worth the effort. This is when ScopeExit macro comes into play. You put resource acquisition directly in your code and next to it you write a code that releases the resource. Note that ScopeExit uses PP macros and relies on Boost.Typeof. The latest version can is here: http://boost-consulting.com/vault/index.php?action=downloadfile&filename=sc… It's available also at http://tinyurl.com/2z6qg2 Online documentation is here: http://194.6.223.221/~nasonov/scope_exit-0.04/libs/scope_exit/doc/html/inde… >From the review guidelines here: http://boost.org/more/formal_review_process.htm ... Boost mailing list members are encouraged to submit Formal Review comments: * Publicly on the mailing list. * Privately to the Review Manager. Private comments to a library submitter may be helpful to her or him, but won't help the Review Manager reach a decision, so the other forms are preferred. What to include in Review Comments Your comments may be brief or lengthy, but basically the Review Manager needs your evaluation of the library. If you identify problems along the way, please note if they are minor, serious, or showstoppers. Here are some questions you might want to answer in your review: * What is your evaluation of the design? * What is your evaluation of the implementation? * What is your evaluation of the documentation? * What is your evaluation of the potential usefulness of the library? * Did you try to use the library? With what compiler? Did you have any problems? * How much effort did you put into your evaluation? A glance? A quick reading? In-depth study? * Are you knowledgeable about the problem domain? And finally, every review should answer this question: * Do you think the library should be accepted as a Boost library? Be sure to say this explicitly so that your other comments don't obscure your overall opinion. Thanks in advance to every for your participation in this review.

1 0

[Fwd: boost serialization excessive warning messages]
by Fei Liu 16 Aug '07

16 Aug '07

1 0

Boost regex Java Regex package compatibility
by Sudarshan Gaikaiwari 16 Aug '07

16 Aug '07

Hello Boost Experts Here is my situation. Users write regular expressions which act as input to our programs and are used to perform matches. Currently the code base is Java and uses the java.util.regex package to handle regular expressions. I need to convert this code to C++ and intend to use boost regex. How compatible is boost regex with Java regex? I have looked at Java regex documentation here http://java.sun.com/j2se/1.5.0/docs/api/java/util/regex/Pattern.html to note the differences between Java regex and Perl 5 regexs. Are these the only with boost regex also? -- Sudarshan Gaikaiwari www.sudarshan.org sudarshan(a)acm.org

2 1

exceptions from regexp library usage
by Venkat Rangan 16 Aug '07

16 Aug '07

Hi, I get the following exception while using a boost regexp matching libraries (with Windows Visual Studio, 7.1 environment). Setup: static RegexClass::RegularExpression re_exp; bool CMyclass::parseExpression(string expression) { LoggerPtr logger = Logger::getRootLogger(); ostringstream oss; RegexClass::RegularExpression *re = &re_exp; re->Expression = expression; RegexClass::RegularExpression::ExpressionErrorCode eec = re->ParseExpression(); if (eec == RegexClass::RegularExpression::REG_NOERROR) { oss << "Parse successful: " << expression; logger->info(oss.str()); return true; } ... } Matching call: bool CMyClass::matchSpec(RegexClass::RegularExpression *pRe, const char *stringToMatch) { pRe->SetStringToMatch(stringToMatch); if (pRe->Match()) { return true; } return false; } Exception while using expression matcher on Windows Server 2003 Platforms: Exception Stack Trace 0x0343c900 0x00457374 boost::re_detail::reg_grep2<boost::re_detail::grep_search_predicate<std: :basic_string<char,std::char_traits<char>,std::allocator<char> >::iterator,boost::detail::allocator<char> >,std::basic_string<char,std::char_traits<char>,std::allocator<char> >::iterator,char,boost::regex_traits<char>,boost::detail::allocator<char >,boost::detail::allocator<char> > 0x00000044 0x0343c924 0x0045a65b boost::regex_search<std::basic_string<char,std::char_traits<char>,std::a llocator<char>>::iterator,boost::detail::allocator<char>,char,boost::reg ex_traits<char>,boost::detail::allocator<char> > 0x0000003b 0x0343c970 0x0045ae66 RegexClass::RegularExpression::Match 0x000001c6 Sometimes, I get the following exception: Stack Trace 0x037dc938 0x0045db6e RegexClass::RegularExpressionPimpl::GetMatchingInformation 0x0000027e 0x037dc970 0x0045af19 RegexClass::RegularExpression::Match 0x00000279 0x037dc9a0 0x004370b1 CMyClass::matchSpec 0x00000091 at myclass.cpp(349) Any help would be much appreciated. Thanks.

2 1

Link errors using Boost & STLPort with VC8
by Jason Ivey 16 Aug '07

16 Aug '07

I am attempting to compile and link a small test application using STLPort_5.1.3, boost_1_34_1 and MSVC8 sp1. Everything works fine when I don't have to link against any boost libraries. To test linking against the boost static libraries I wrote a simple little test app that used the boost::regex library and ran into errors. I am not completely sure that this is a boost issue but since I can compile and link programs without any problems that don't use boost binaries I wasn't sure of who else to turn to. The linker error I am getting is: 1>LINK : fatal error LNK1104: cannot open file 'stlportstld_x.5.1.lib' The problem is that all of the stlport libraries are named stlportstld.5.1.lib or similar. I did try to just rename the library to make it match but, of course, I got a boat load of unresolved external linker errors pointing to names such as "stlpdx_std::basic_string." Looking at a dumpbin output of the actual regex library it is linking against, libboost_regex-vc80-mt-sgdp-1_34_1.lib, I found linker directives of the form: /DEFAULTLIB:"stlportstld_x.5.1.lib" /DEFAULTLIB:"libcpmtd" /DEFAULTLIB:"LIBCMTD" /DEFAULTLIB:"OLDNAMES" I couldn't find anywhere that boost had put those directives in the libraries but I could be missing something so I also did a dumpbin of one of the stlport libraries, stlportd_static.5.1.lib, and only found the following linker directives: /DEFAULTLIB:"LIBCMTD" /DEFAULTLIB:"OLDNAMES" I have to believe there are at least a few companies out there who have replaced the shipping MSVC STL for testing purposes, if for no other reason, and are also using Boost so hopefully I'm just missing something obvious. Below are the steps I followed to compile both sets of libraries and the test application. Let me know if anything appears to be off or if there is simply a better/easier way. Thanks, Jason Ivey Open command prompt and run: "%VS80COMNTOOLS%\vsvars32.bat" STLPort_5.1.3 build\lib\configure -c msvc8 nmake /fmsvc.mak install Boost_1_34_1 edit tools\build\v2\user-config.jam added line 45 with using stlport : : d:\\build\\stlport\\stlport d:\\build\\stlport\\lib ; bjam --toolset=msvc stdlib=stlport --with-regex stage Build Test Application set include=d:\build\stlport\stlport;D:\build\boost_1_34_1;%include% set lib=d:\build\stlport\lib;D:\build\boost_1_34_1\stage\lib;%lib% call "%VS80COMNTOOLS%\..\IDE\devenv.exe" /useenv

2 2

function/bind - passing function pointer to C API
by Nicholas Yue 16 Aug '07

16 Aug '07

Hi, I am attempting to use Boost bind and function to help me pass a member function as a function pointer to the GLUT C-library. I have difficulty understanding the usage of bind and function in the Boost library. When I attempt to pass what I thought was a function pointer, the compiler indicated that it is actually not a function pointer. class MyGlut { public: MyGlut(); virtual ~MyGlut(); void loop(int argc, char **argv); void draw(void); void displayFunc(boost::function<void()> func); private: boost::function<void()> display_callback; }; void MyGlut::displayFunc(boost::function<void()> func) { glutDisplayFunc(func); // ERROR IN COMPILATION } void MyGlut::loop(int argc, char **argv) { glutInit(&argc,argv); glutInitDisplayMode(GLUT_RGB | GLUT_DOUBLE | GLUT_DEPTH | GLUT_MULTISAMPLE); glutCreateWindow("Hello World"); //glutDisplayFunc(redraw); // Original way to pass C-function pointer displayFunc( boost::bind(&MyGlut::draw, *this) ); } Regards

2 1

Need ideas...
by Noah Roberts 16 Aug '07

16 Aug '07

I am trying to generalize the concept of putting database data into boost::tuple objects. I'm thinking syntax similar to something like so: typedef boost::tuple<int, double, std::string> row; row r = SqlQuery<row>::run_query(db, "select * from x"); I imagine something like so being contained in the processing: TUPLE t; ... t.get<X>() = boost::lexical_cast< typename boost::tuples::element<X,TUPLE>::type >(data[X]); // data is char ** Where X is the index of the element and the entire tuple is iterated in this manner. I thought maybe there would be something in MPL that could help but I'm not seeing it. Anyone got any bright ideas?

5 7