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

[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