- Boost - lists.boost.org

shared pointer serialization
by Robert Ramey 28 Apr '04

28 Apr '04

Rozental, Gennadiy wrote: > There is another counter to direct counter using (I just think out loud - > it may be that you ok): what if I do not save all of the shared_ptr to the > same object? What will happened once they will get restored? Wouldn't it > cause memory leak? > I do realize that any other solution would be more complicated, but I > think we should go for it. I don't really understand what's being said here but I can shed a little more light on the way serialization is implemented right now. It's also used as a case study in the documentation and described in detail. > what if I do not save all of the shared_ptr to the same object? Here is a scenario: a) a shared_ptr exists and it points to and object which is pointed by 9 other shared_ptrs. b) we create and archive and save some objects. The set objects saved only includes 5 of the shared_ptrs out of the possible 10. c) later when we load, we create 5 new shared_ptr and one new object. Object tracking guarantees that only one shared object is created. As each new shared pointer is loaded, the shared count is incremented. So the new shared pointer is not identical to the original - its equal to 5. d) the process (almost?) guarantees that all the shared_ptr are valid in that they all point to shared object and the shared_count is maintained to be the correct number. The intention is that this process be exception safe - I'm not sure that this intention has been realized. A fuller explanation can be found at: http://www.rrsd.com/boost/libs/serialization/doc/shared_ptr.html Robert Ramey.

1 0

Re:[boost] Re: serialization and MFC
by Robert Ramey 28 Apr '04

28 Apr '04

Eric Niebler wrote: > Forgive the possibly naive question -- I have never used the > serialization library, but I have used MFC serialization. I am curious > if the boost serialization library can be made backwards-compatible > with MFC serialization; that is, if I have an old application that > uses MFC serialization, would it be possible to switch to the boost > serialization library and still have the ability to read old (MFC) > archives? > > I'd like to know: > - if it's possible > - how hard it would be (would it require reverse-engineering the > MFC archive format? is that format stable? documented?) > - what the advantages of switching are The easiest way to switch from MFC (or any other systems is to do the following): a) add boost serialization to your code. b) when you open an archive - currently MFC, use code like the following: open stream read the first part of the stream if doesn't contain a boost serialization signature invoke MFC de-serialization else invoke boost de-serialization. c) when you save an archive - just invoke boost serialization. In this way, all your old files will be compatible and will gradually be converted to the new system. The new archives can use all the new facilities without compromise. This is much easier, and forward looking than trying to adapt to an old format wich likely isn't rich enough to support the new facilities. Robert Ramey

1 0

[Boost-bugs] [ boost-Support Requests-943555 ] Path.cpp:85: error: `portable_posix_name' undeclared in name
by SourceForge.net 28 Apr '04

28 Apr '04

Support Requests item #943555, was opened at 2004-04-28 01:07 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=207586&aid=943555&group_i… Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: Path.cpp:85: error: `portable_posix_name' undeclared in name Initial Comment: i am compiling a game and i get thru ./configure but when i goto make i get this error Path.cpp:85: error: `portable_posix_name' undeclared in namespace `boost::filesystem' i get simmilair errors on 85, 99 and 113 saying portable_posix_name is undeclared ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=207586&aid=943555&group_i… ------------------------------------------------------- This SF.Net email is sponsored by: Oracle 10g Get certified on the hottest thing ever to hit the market... Oracle 10g. Take an Oracle 10g class now, and we'll give you the exam FREE. http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click _______________________________________________ Boost-bugs mailing list Boost-bugs(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/boost-bugs

1 0

problems with boost::thread
by "Magomed Abdurakhmanov 28 Apr '04

28 Apr '04

Hello. I have some troubles with boost::thread, and think they are important: 1. condition::timed_wait dangerous to use, because waiting delay specified as time when we are will stop waiting. So this is very surprising when system time is changed! I guess that waiting for specified delay is much more safe than waiting until some time arrive. For example try launch the program bellow and change system time backward (to past) when it's working. I have tested this under win32 + msvc7 // ------------------------------- boost::condition cvar; boost::mutex monitor; void thread1() { for(;;) { boost::mutex::scoped_lock lock(monitor); boost::xtime xt; boost::xtime_get(&xt, boost::TIME_UTC); std::cout << "now: " << xt.sec << std::endl; xt.sec += 5; std::cout << "will wait until: " << xt.sec << std::endl; if (!cvar.timed_wait(lock, xt)) std::cout << "timed out!" << std::endl; std::cout << "next step" << std::endl; } } int main(int argc, char* argv[]) { boost::thread thrd1(&thread1); thrd1.join(); return 0; } // ------------------------------- 2. The secound trouble is that the thread function has catch(...) at the root and when unhandled exception in thread thrown, it's just silently eated and thread stopped. But the process stay alive, and now nothing about it. And ever wrong that catch(...) under VC6 will catch OS exceptions. p.s. sorry for so bad english

8 14

serialization and MFC
by Eric Niebler 28 Apr '04

28 Apr '04

Forgive the possibly naive question -- I have never used the serialization library, but I have used MFC serialization. I am curious if the boost serialization library can be made backwards-compatible with MFC serialization; that is, if I have an old application that uses MFC serialization, would it be possible to switch to the boost serialization library and still have the ability to read old (MFC) archives? I'd like to know: - if it's possible - how hard it would be (would it require reverse-engineering the MFC archive format? is that format stable? documented?) - what the advantages of switching are Thanks. -- Eric Niebler Boost Consulting www.boost-consulting.com

1 1

intel-linux toolset doc error
by Richard Hadsell 27 Apr '04

27 Apr '04

I am upgrading from Boost 1.30.0 to 1.31.0, trying to use bjam for the first time to build the libraries (including Regex). When building for intel-linux, I read (tools/build/v1/intel-linux-tools.html) that bjam would be able to find the compiler from the location of the iccvars.sh script. This did not work. Evidence: 162% which iccvars.sh /usr/local/intel/compiler80/ia32/bin/iccvars.sh 163% which icc /usr/local/intel/compiler80/ia32/bin/icc Despite both of these being in my PATH, bjam tried to look elsewhere: 168% bjam "-sTOOLS=intel-linux" --stagedir=stage "-sBUILD=debug release <threading>single" stage [snip] intel-linux-C++-action bin/boost/libs/date_time/build/libboost_date_time.so/intel-linux/debug/shared-linkable-true/greg_month.o /bin/sh: /opt/intel/compiler70/ia32/bin/iccvars.sh: No such file or directory Specifying the version number did not help: 169% bjam "-sTOOLS=intel-linux" "-sINTEL_VERSION=80" --stagedir=stage "-sBUILD=debug release <threading>single" stage [snip] intel-linux-C++-action bin/boost/libs/date_time/build/libboost_date_time.so/intel-linux/debug/shared-linkable-true/greg_month.o /bin/sh: /opt/intel_cc_80/bin/iccvars.sh: No such file or directory -- Dick Hadsell 914-259-6320 Fax: 914-259-6499 Reply-to: hadsell(a)blueskystudios.com Blue Sky Studios http://www.blueskystudios.com 44 South Broadway, White Plains, NY 10601

2 2

Problems using Boost, Pls Advise
by Steve Bobrowski 27 Apr '04

27 Apr '04

Hi, I'm a C++ newbie trying to use the Boost regex libraries. Here's my situation. My system is Red Hat Linux 9, using the Borland C++BuilderX Personal IDE (which uses the g++ compiler). I downloaded and installed Boost from boost.org using the command: bjam -sTOOLS=gcc install The install seemed to complete fine, with 2900+ targets updated. The libraries install in /usr/local/include/boost-1_31/boost. I created the following link: ln -s /usr/local/include/boost-1_31/boost /usr/include/boost I then use C++BuilderX to try and compile one of the example programs for the regex libaries that I found in the documentation. The source code is: /////////////////////// #include <list> #include <boost/regex.hpp> unsigned tokenise(std::list<std::string>& l, std::string& s) { return boost::regex_split(std::back_inserter(l), s); } #include <iostream> using namespace std; #if defined(BOOST_MSVC) || (defined(__BORLANDC__) && (__BORLANDC__ == 0x550)) // // problem with std::getline under MSVC6sp3 istream& getline(istream& is, std::string& s) { s.erase(); char c = is.get(); while(c != '\n') { s.append(1, c); c = is.get(); } return is; } #endif int main(int argc) { string s; list<string> l; do{ if(argc == 1) { cout << "Enter text to split (or \"quit\" to exit): "; getline(cin, s); if(s == "quit") break; } else s = "This is a string of tokens"; unsigned result = tokenise(l, s); cout << result << " tokens found" << endl; cout << "The remaining text is: \"" << s << "\"" << endl; while(l.size()) { s = *(l.begin()); l.pop_front(); cout << s << endl; } }while(argc == 1); return 0; } /////////////////////// The compiler returns the following errors: /////////////////////// g++ -c -o /home/sbobrows/cbproject/pmetest/linux/Debug_Build/splittest.o -g2 -O0 -MD -I/usr/include -I/usr/include/g++-3 splittest.cpp g++ -o /home/sbobrows/cbproject/pmetest/linux/Debug_Build/pmetest linux/Debug_Build/splittest.o linux/Debug_Build/splittest.o(.text+0x2c9): In function `__tcf_0': "stl_vector.h": /usr/include/c++/3.2.2/bits/stl_vector.h undefined reference to `boost::reg_expression<char, boost::regex_traits<char>, std::allocator<char> >::~reg_expression [in-charge]()' at line 998 linux/Debug_Build/splittest.o(.gnu.linkonce.t._ZN5boost9re_detail22get_defau lt_expressionIcEERKNS_14reg_expressionIT_NS_12regex_traitsIS3_EESaIS 3_EEES3_+0x39): In function `boost::reg_expression<char, boost::regex_traits<char>, std::allocator<char> > const& boost::re_detail::get_default_expression<char>(char)': "perl_matcher_common.hpp": /usr/include/boost/regex/v4/perl_matcher_common.hpp undefined reference to `boost::reg_expression<char, boost::regex_traits<char>, std::allocator<char> >::reg_expression[in-charge](char const*, unsigned, std::allocator<char> const&)' at line 734 linux/Debug_Build/splittest.o(.gnu.linkonce.t._ZN5boost11regex_splitISt20bac k_insert_iteratorISt4listISsSaISsEEEcSt11char_traitsIcESaIcENS_12reg ex_traitsIcEES8_EEjT_RSbIT0_T1_T2_ERKNS_14reg_expressionISC_T3_T4_EENS_15reg ex_constants12_match_flagsEj+0x12e): In function `unsigned boost::regex_split<std::back_insert_iterator<std::list<std::basic_string<cha r, std::char_traits<char>, std::allocator<char> >, std::allocator<std::basic_string<char, std::char_traits<char>, std::allocator<char> > > > >, char, std::char_traits<char>, std::allocator<char>, boost::regex_traits<char>, std::allocator<char> >(std::back_insert_iterator<std::list<std::basic_string<char, std::char_traits<char>, std::allocator<char> >, std::allocator<std::basic_string<char, std::char_traits<char>, std::allocator<char> > > > >, std::basic_string<char, std::char_traits<char>, std::allocator<char> >&, boost::reg_expression<char, boost::regex_traits<char>, std::allocator<char> > const&, boost::regex_constants::_match_flags, unsigned)': "perl_matcher_non_recursive.hpp": /usr/include/boost/regex/v4/perl_matcher_non_recursive.hpp undefined reference to `boost::reg_expression<char, boost::regex_traits<char>, std::allocator<char> >::mark_count() const' at line 1059 linux/Debug_Build/splittest.o(.gnu.linkonce.t._ZN5boost9re_detail12perl_matc herIN9__gnu_cxx17__normal_iteratorIPKcSsEESaINS_9sub_matchIS6_EEENS_ 12regex_traitsIcEESaIcEEC1ES6_S6_RNS_13match_resultsIS6_S9_EERKNS_14reg_expr essionIcSB_SC_EENS_15regex_constants12_match_flagsE+0x78): In function `boost::re_detail::perl_matcher<__gnu_cxx::__normal_iterator<char const*, std::basic_string<char, std::char_traits<char>, std::allocator<char> > >, std::allocator<boost::sub_match<__gnu_cxx::__normal_iterator<char const*, std::basic_string<char, std::char_traits<char>, std::allocator<char> > > > >, boost::regex_traits<char>, std::allocator<char> >::perl_matcher[in-charge](__gnu_cxx::__normal_iterator<char const*, std::basic_string<char, std::char_traits<char>, std::allocator<char> > >, __gnu_cxx::__normal_iterator<char const*, std::basic_string<char, std::char_traits<char>, std::allocator<char> > >, boost::match_results<__gnu_cxx::__normal_iterator<char const*, std::basic_string<char, std::char_traits<char>, std::allocator<char> > >, std::allocator<boost::sub_match<__gnu_cxx::__normal_iterator<char const*, std::basic_string<char, std::char_traits<char>, std::allocator<char> > > > > >&, boost::reg_expression<char, boost::regex_traits<char>, std::allocator<char> > const&, boost::regex_constants::_match_flags)': "perl_matcher_non_recursive.hpp": /usr/include/boost/regex/v4/perl_matcher_non_recursive.hpp undefined reference to `boost::reg_expression<char, boost::regex_traits<char>, std::allocator<char> >::get_traits() const' at line 869 ': "basic_string.tcc": /usr/include/c++/3.2.2/bits/basic_string.tcc undefined reference to `boost::reg_expression<char, boost::regex_traits<char>, std::allocator<char> >::empty() const' at line 146 linux/Debug_Build/splittest.o(.gnu.linkonce.t._ZN5boost9re_detail12perl_matc herIN9__gnu_cxx17__normal_iteratorIPKcSsEESaINS_9sub_matchIS6_EEENS_ 12regex_traitsIcEESaIcEE24estimate_max_state_countEPSt26random_access_iterat or_tag+0x30): In function `boost::re_detail::perl_matcher<__gnu_cxx::__normal_iterator<char const*, std::basic_string<char, std::char_traits<char>, std::allocator<char> > >, std::allocator<boost::sub_match<__gnu_cxx::__normal_iterator<char const*, std::basic_string<char, std::char_traits<char>, std::allocator<char> > > > >, boost::regex_traits<char>, std::allocator<char> >::estimate_max_state_count(std::random_access_iterator_tag*)': "regex_grep.hpp": /usr/include/boost/regex/v4/regex_grep.hpp undefined reference to `boost::reg_expression<char, boost::regex_traits<char>, std::allocator<char> >::size() const' at line 46 linux/Debug_Build/splittest.o(.gnu.linkonce.t._ZN5boost9re_detail12perl_matc herIN9__gnu_cxx17__normal_iteratorIPKcSsEESaINS_9sub_matchIS6_EEENS_ 12regex_traitsIcEESaIcEE8find_impEv+0xc0): In function `boost::re_detail::perl_matcher<__gnu_cxx::__normal_iterator<char const*, std::basic_string<char, std::char_traits<char>, std::allocator<char> > >, std::allocator<boost::sub_match<__gnu_cxx::__normal_iterator<char const*, std::basic_string<char, std::char_traits<char>, std::allocator<char> > > > >, boost::regex_traits<char>, std::allocator<char> >::find_imp()': "regex_grep.hpp": /usr/include/boost/regex/v4/regex_grep.hpp undefined reference to `boost::reg_expression<char, boost::regex_traits<char>, std::allocator<char> >::mark_count() const' at line 49 Build cancelled due to errors linux/Debug_Build/splittest.o(.gnu.linkonce.t._ZN5boost9re_detail12perl_matc herIN9__gnu_cxx17__normal_iteratorIPKcSsEESaINS_9sub_matchIS6_EEENS_ 12regex_traitsIcEESaIcEE8find_impEv+0x202): In function `boost::re_detail::perl_matcher<__gnu_cxx::__normal_iterator<char const*, std::basic_string<char, std::char_traits<char>, std::allocator<char> > >, std::allocator<boost::sub_match<__gnu_cxx::__normal_iterator<char const*, std::basic_string<char, std::char_traits<char>, std::allocator<char> > > > >, boost::regex_traits<char>, std::allocator<char> >::find_imp()': "perl_matcher_non_recursive.hpp": /usr/include/boost/regex/v4/perl_matcher_non_recursive.hpp undefined reference to `boost::reg_expression<char, boost::regex_traits<char>, std::allocator<char> >::mark_count() const' at line 767 linux/Debug_Build/splittest.o(.gnu.linkonce.t._ZN5boost9re_detail12perl_matc herIN9__gnu_cxx17__normal_iteratorIPKcSsEESaINS_9sub_matchIS6_EEENS_ 12regex_traitsIcEESaIcEE8find_impEv+0x290): In function `__static_initialization_and_destruction_0': "perl_matcher_non_recursive.hpp": /usr/include/boost/regex/v4/perl_matcher_non_recursive.hpp undefined reference to `boost::reg_expression<char, boost::regex_traits<char>, std::allocator<char> >::mark_count() const' at line 1254 linux/Debug_Build/splittest.o(.gnu.linkonce.t._ZN5boost9re_detail12perl_matc herIN9__gnu_cxx17__normal_iteratorIPKcSsEESaINS_9sub_matchIS6_EEENS_ 12regex_traitsIcEESaIcEE8find_impEv+0x2d7): In function `boost::re_detail::perl_matcher<__gnu_cxx::__normal_iterator<char const*, std::basic_string<char, std::char_traits<char>, std::allocator<char> > >, std::allocator<boost::sub_match<__gnu_cxx::__normal_iterator<char const*, std::basic_string<char, std::char_traits<char>, std::allocator<char> > > > >, boost::regex_traits<char>, std::allocator<char> >::find_imp()': "perl_matcher_common.hpp": /usr/include/boost/regex/v4/perl_matcher_common.hpp undefined reference to `boost::re_detail::verify_options(unsigned, boost::regex_constants::_match_flags)' at line 821 linux/Debug_Build/splittest.o(.gnu.linkonce.t._ZN5boost9re_detail8access_tIc NS_12regex_traitsIcEESaIcEE5firstERKNS_14reg_expressionIcS3_S4_EE+0x d): In function `boost::re_detail::access_t<char, boost::regex_traits<char>, std::allocator<char> >::first(boost::reg_expression<char, boost::regex_traits<char>, std::allocator<char> > const&)': "regex_split.hpp": /usr/include/boost/regex/v4/regex_split.hpp undefined reference to `boost::reg_expression<char, boost::regex_traits<char>, std::allocator<char> >::first(boost::reg_expression<char, boost::regex_traits<char>, std::allocator<char> > const&) at line 36 /////////////////////// After searching around extensively, I've not come up with any solution to my problem. Can someone please point me in the right direction? It seems like I'm just missing some configuration step along the way. Thanks in advance, Steve!

3 3

RE: RE: Re: Re:[boost] Re: Serialization Formal Review #2
by Rozental, Gennadiy 27 Apr '04

27 Apr '04

> > > The main problem I had was that certain member variable weren't > > > accessible. The STL collections don't have that issue so > there was no > > > problem. > > > Sorry if this is silly question, but why would you need an > access to > > the counter? IMO we should be able to save/load shared_ptr without > > need to save it. > > I checked the code (which was written some time ago) and the > answer to that question isn't obvious to me. I do remember > starting with the idea that it wouldn't be necessary to look > beyond shared_ptr but I had to just keep adding on to make > things work. The implementation of shared_ptr is A LOT more > involved that one would guess. > > My implementation of shared_ptr implementation may not be the > only or best one. It is pretty straight forward however in > that it follows the chain of composition - which includes > shared_count. > > Sorry I can't give a better answer. > > Robert Ramey There is another counter to direct counter using (I just think out loud - it may be that you ok): what if I do not save all of the shared_ptr to the same object? What will happened once they will get restored? Wouldn't it cause memory leak? I do realize that any other solution would be more complicated, but I think we should go for it. Gennadiy.

1 0

Re:RE: Re: Re:[boost] Re: Serialization Formal Review #2
by Robert Ramey 27 Apr '04

27 Apr '04

> > The main problem I had was that certain member variable weren't > > accessible. The STL collections don't have that issue so there was no > > problem. > Sorry if this is silly question, but why would you need an access to the > counter? IMO we should be able to save/load shared_ptr without need to > save it. I checked the code (which was written some time ago) and the answer to that question isn't obvious to me. I do remember starting with the idea that it wouldn't be necessary to look beyond shared_ptr but I had to just keep adding on to make things work. The implementation of shared_ptr is A LOT more involved that one would guess. My implementation of shared_ptr implementation may not be the only or best one. It is pretty straight forward however in that it follows the chain of composition - which includes shared_count. Sorry I can't give a better answer. Robert Ramey

1 0

shared_ptr and BOOST_DISABLE_THREADS
by Carl Daniel 27 Apr '04

27 Apr '04

Playing with a Spirit-based parser for a simple scripting language I noticed that #defining BOOST_DISABLE_THREADS resulted in a parser that was nearly 3 times faster. For reasons that aren't relevant to the discussion, this had to be an MT build, but the parser didn't need thread safety. That made me wonder though: If I #define BOOST_DISABLE_THREADS in some translation units but not in others, what's going to happen? I suppose one way of summarizing it is this: does BOOST_DISABLE_THREADS change the type of shared_ptr that's made? If not, that seems like a rather serious problem to me - especially given the enormous difference in performance that I measured (optimized build with VC8 alpha). What obvious thing am I overlooking? -cd

10 23