- Boost - lists.boost.org

Property tree rev.5
by Marcin Kalicinski 18 Apr '06

18 Apr '06

Property tree library revision 5 (review version) is now in the boost vault. Documentation can be viewed online at http://kaalus.atspace.com/ptree Major changes since revision 4: - basic_ptree no longer templated on character type, now templated on key type instead - get_b functions removed - get_o functions renamed get_optional - get_d functions renamed get, (resolution with throwing get through overloading) - enhancements to cmdline_parser - added more regression tests - updated docs and examples Marcin

8 8

Program Options: Allow long options without -- prefix?
by Olaf van der Spek 18 Apr '06

18 Apr '06

Hi, Is it possible to allow long options without -- prefix? The code doesn't seem to support it, but I think it's handy in cases where positional options aren't used.

1 0

[multi_index] Problems with chained pointers in multi index from 1.34 RC
by Alexei Alexandrov 18 Apr '06

18 Apr '06

Hi, my multi_index use case: * The container contains not objects themselves, but pointers (shared_ptr-s). * The objects are noncopyable - they are created by a factory and only smart pointers are copied between clients. * The container has 2 indexes. Indexes are built on const_mem_fn extractor. One of the indexes uses a function from a base class. It seems that in 1.34 problem with using member function from a base class is supposed to be solved, but it causes a regression that you cannot have pointers to noncopyable objects in the container. Is this a known issue? My compiler is MSVC 7.1/Intel Compiler 9.0. Here is a code snippet to demonstrate the problem. This code compiles well with boost 1.33.1, but fails to compile with RC 1.34. If you uncomment the second index, it won't compile neither with 1.33 nor with 1.34. #include <boost/multi_index_container.hpp> #include <boost/multi_index/mem_fun.hpp> #include <boost/multi_index/ordered_index.hpp> #include <boost/shared_ptr.hpp> #include <boost/noncopyable.hpp> #include <iostream> #include <string> using namespace boost::multi_index; /* A name record consists of the given name (e.g. "Charlie") * and the family name (e.g. "Brown"). The full name, calculated * by name_record::name() is laid out in the "phonebook order" * family name + given_name. */ class base_record : boost::noncopyable { public: int get_id() const { return id_; } protected: base_record() : id_(0) {} private: int id_; }; class name_record : public base_record { public: typedef boost::shared_ptr<name_record> Ptr; static Ptr create() { return Ptr(new name_record()); } const std::string & name() const { return name_; } protected: name_record() : name_("") {} private: std::string name_; }; typedef multi_index_container< name_record::Ptr, indexed_by< ordered_unique< BOOST_MULTI_INDEX_CONST_MEM_FUN(name_record, const std::string &, name) /**/> // , // ordered_unique< // BOOST_MULTI_INDEX_CONST_MEM_FUN(base_record, int, get_id) // > /**/> /**/> name_record_set; int main() { name_record_set ns; ns.insert(name_record::create()); return 0; }

2 4

[program_options] PATCH: fix VC8 runtime assertion error in options_description.cpp
by Trent Nelson 18 Apr '06

18 Apr '06

Hi, With regards to the following lines in the latest version (1.16) of program_options's options_description.cpp: 395: line_end = line_begin + line_length; 396: if (line_end > par_end) 397: { 398: line_end = par_end; 399: } Line 395 causes VC8 to throw a runtime assertion error when processing the last line of a multiline option description. This is because 'line_begin + line_length' will exceed the actual length of the string, and it seems VC8 is pretty intent on not letting that happen, despite the fact we correct it in following line. Following patch did the trick for me: --- options_description-1.16.cpp 2006-04-18 02:39:51.401147200 +0100 +++ options_description.cpp 2006-04-18 03:04:05.722358400 +0100 @@ -390,13 +390,13 @@ } } - string::const_iterator line_end; + string::const_iterator line_end = line_begin; + unsigned remaining = unsigned(distance(line_begin, par_end)); - line_end = line_begin + line_length; - if (line_end > par_end) - { - line_end = par_end; - } + // line_end will be determined by either the end of the + // current paragraph (remaining), or the current line + // length, which ever is less. + line_end += ((remaining < line_length) ? remaining : line_length); // prevent chopped words // Is line_end between two non-space characters?

2 1

[serialization] Is no_tracking from archive_flags working?
by Marcin Kalicinski 18 Apr '06

18 Apr '06

Is no_tracking flag of archives supposed to work? It is defined in archive_flags enum, but all the code that tests it in serialization library is commented out. Unfortunately, even if I uncomment all the code, tracking still performed. I need to disable tracking on per-archive basis and this flag would be just the solution, if I could make it work. (the only references to no_tracking flag I found are in iserializer.hpp and oserializer.hpp). thank you, Marcin

2 1

[boost.build]: docs for the --layout option
by Stefan Seefeld 18 Apr '06

18 Apr '06

I'v just built boost using 'bjam -sBUILD="release <threading>multi" --layout=system' and I notice that all library names contain an 'mt' tag, which I thought would be suppressed with the --layout=system option. Unfortunately, I'm unable to find documentation for the --layout option, so I can't verify whether I remembered it wrongly. Thus I have two questions: * Where can I find complete documentation for options such as --layout ? (I'm not even sure this is part of bjam, or boost.build, or something entirely different.) * What is the correct use of --layout, and what does it actually do ? Shouldn't 'mt' be suppressed, too ? (Did the actual behavior change recently ?) Thanks, Stefan

2 2

[serialization] Exported class names
by Marcin Kalicinski 18 Apr '06

18 Apr '06

Is there a way to force serialization library only input/output exported class names, not class id numbers? I'm trying to make serialization lib read a file created by a human, and human obviously cannot be supposed to type class-id integers. Best regards, Marcin

1 0

CVS
by Arkadiy Vertleyb 17 Apr '06

17 Apr '06

Hi all. I just got back from vacation, and, looking at the Sourceforge site, CVS is still not in a great shape. Does Boost have its own recommendations on what to do in this situation? Should we just wait until things get normal once again? Or should we take some extra precaution, like making extra copies of our libraries, etc.? (sorry if I missed any posts on a similar subject) Regards, Arkadiy

3 5

[shared_ptr] mutex in quick_allocator
by Boris 17 Apr '06

17 Apr '06

If you define BOOST_SP_DISABLE_THREADS class boost::detail::sp_counted_base doesn't use a mutex (see http://www.boost.org/libs/smart_ptr/shared_ptr.htm#ThreadSafety) However boost::detail::quick_allocator still uses a mutex as it checks BOOST_HAS_THREADS but not BOOST_SP_DISABLE_THREADS (see http://www.boost.org/boost/detail/quick_allocator.hpp) Is this intentional (as quick_allocator might be used by other classes)? Boris

2 4

metacomm borland 5_8_* results
by Vladimir Prus 17 Apr '06

17 Apr '06

Hi, at the moment, results for borland_5_8_1 and borland_5_8_2b compiler on RC_1_34_0 branch are pretty bad. See: http://engineering.meta-comm.com/boost-regression/CVS-RC_1_34_0/developer/s… Unless a user of borland can step forward and look into those failures, we'll essentially have no support for those toolsets in 1.34. Any volunteers? Thanks, Volodya

7 12