- Boost - lists.preview.boost.org

[program_options] Feature request: settable argument names
by Joe Gottman 17 Oct '07

17 Oct '07

I recently used the program_options library for the first time and found it very useful. However, there's one easily implemented feature that's missing: the ability to set the name of a parameter that's associated with a particular option. In the first example in the tutorial we have the code po::options_description desc("Allowed options"); desc.add_options() ("help", "produce help message") ("compression", po::value<int>(), "set compression level") ; When desc is then sent to cout, the output then looks like Allowed options: --help : produce help message --compression arg : set compression level But suppose we wanted the name of the parameter associated with the --compression option to be something other than arg. As program_options is now written there's no way to do this. This is unfortunate, because replacing arg with a more relevant argument name could make it clearer to the user what type of values should be passed in. I suggest adding the following member to the typed_value template class: typed_value *argument_name(const std::string &); This function would change the name of the arguement associated with the option from "arg" to whatever string was passed in. If it isn't called then the argument name can remain as "arg". If this function were included, then the code above could be rewritten as po::options_description desc("Allowed options"); desc.add_options() ("help", "produce help message") ("compression", po::value<int>()->argument_name("level-number"), "set compression level") ; and then the output would be Allowed options: --help : produce help message --compression level-number : set compression level Joe Gottman

2 1

Re: [boost] [test] REVERTED
by Eric Niebler 17 Oct '07

17 Oct '07

Gennadiy Rozental wrote: > "Eric Niebler" <eric(a)boost-consulting.com> wrote in message > news:47150CB0.8060302@boost-consulting.com... >> Beman Dawes wrote: >>> Eric Niebler wrote: >>>> We seem to be having a lot of problems >>>> with Boost.Test lately. This is really bad. Should we revert Boost.Test >>>> to something that works? >>> Yes. This is a disaster. >>> >>> Can you do the revert? I'm tied up. It looks like a series of changes >>> where make on revisions 40065-40078, and then 40090. >> >> I've reverted all the Boost.Test changes since r40064. > > You reverted to wrong version. 40064 includes the issue with infinite > recursion. OK, but you didn't say which revision I should revert to, so I just reverted all the way back to r40013, which is just before a huge number of Boost.Test changes. Beman, others, please give this a shot. -- Eric Niebler Boost Consulting www.boost-consulting.com

2 1

[intrusive] Expected failure markup.
by Markus Schöpflin 17 Oct '07

17 Oct '07

Hello, I would like to ask if the expected failure markup for intrusive could be removed for Tru64/CXX. There are still many failures left, but as this platform has lost it's 'officially supported' boost status the expected failure markup isn't relevant anyway. It would help me a lot in fixing the remaining issues, as it gives a nice overview of what already works and what doesn't. Regards, Markus

3 3

[fusion] missing map_tie documentation from spirit website
by Michael Marcin 17 Oct '07

17 Oct '07

The map_tie documentation link on http://tinyurl.com/yw5le8 is broken. Thanks, Michael Marcin

1 0

[test] broken on gcc 3.4?
by Eric Niebler 17 Oct '07

17 Oct '07

This is gcc-3.4 (cygwin). In file included from C:\cygwin\home\ericne\boost\org\trunk\libs\test\src\execution_monitor.cpp:16: ../../boost/test/impl/execution_monitor.ipp: In function `void boost::detail::execution_monitor_jumping_signal_handler(int, siginfo_t*, void*)': ../../boost/test/impl/execution_monitor.ipp:635: error: expected id-expression before "__extension__" ../../boost/test/impl/execution_monitor.ipp:635: error: expected `;' before "__extension__" ../../boost/test/impl/execution_monitor.ipp:635: error: expected primary-expression before ')' token ../../boost/test/impl/execution_monitor.ipp:635: error: expected `;' before ')' token I'm fully sync'ed up to svn head. We seem to be having a lot of problems with Boost.Test lately. This is really bad. Should we revert Boost.Test to something that works? -- Eric Niebler Boost Consulting www.boost-consulting.com

4 4

[parameter] Macro for CodeGear SFINAE problems (answering Dave's comment)
by Nicola Musatti 17 Oct '07

17 Oct '07

Dave wrote in a Ticket comment: > OK, then if you can find the time, I would prefer then to have another > configuration macro (parameter-library-specific if no other libs need it) > for this purpose. Code repetition is evil, even PP code. [I'm moving this discussion: http://svn.boost.org/trac/boost/ticket/1305 to the mailing list, as it seems more appropriate.] Where you thinking of something like BOOST_CODEGEAR_SFINAE_BUG? If so, I'll look into it. Cheers, Nicola Musatti

2 1

[xpressive] HP-UX_ia64_aCC problem ... care to help?
by Eric Niebler 17 Oct '07

17 Oct '07

Two of xpressive's tests are crashing on the HP-UX_ia64_aCC platform. Is there anybody with access to this platform that would like to help me track it down? Just run xpressive's "test_actions" test and send me a backtrace of the crash. Whoever helps gets a gold star. :-) -- Eric Niebler Boost Consulting www.boost-consulting.com

2 5

force threading
by Gennadiy Rozental 17 Oct '07

17 Oct '07

How do I force <threading>single for cw toolset?

1 0

[boos][Trac] Anybody tried the code review plugin?
by John Femiani 16 Oct '07

16 Oct '07

I noticed that there is a code review plug-in for Trac. Since boost seems to be using Trac now, does anybody else think that this could be nice to have as part of the boost process? I don't have experience using the plugin but it seems nice to me. -- John

2 1

Future of Boost.Thread, date-time, and C++0x
by Jeff Garland 16 Oct '07

16 Oct '07

At the Kona meeting (just finished) the standard committee made very significant progress on threading for C++0x -- voting in a proposal written by Howard H, Beman, Anthony Williams, myself, and others -- subject to wording changes to be made by a small drafting committee. Basically we were in agreement on semantics, but even after several late night drafting sessions people weren't happy with the standardeze. While much of the proposal is based on Boost.thread it has some serious departures in the way mutexes and guard interfaces work, it's use of date-time types for clock/timing interfaces and such. At this point I feel it would be very important to have a reference implementation widely available to Boosters and others to play with so that any issues are shaken out while there's still time tweak things. Howard has been maintaining a reference implementation, but this is a call out to the broader thread development team (not sure who all that is now besides Anthony) to consider how we might formalize this into Boost.threads. Thoughts? Jeff

8 15

[mipspro] shared libraries issue
by Vladimir Prus 16 Oct '07

16 Oct '07

Per: http://tinyurl.com/yuh7m4 Boost.Python fails to link on MIPSPRO toolset. The errors suggest that the linker tries to create executable, not a shared library, and in fact, I don't see any linker flag potentially causing shared library to be created in mipspro.jam:link.dll Any ideas? - Volodya

1 0

Rapid turnaround testing
by Beman Dawes 16 Oct '07

16 Oct '07

As an experiment, I've got a script that is checking svn every 15 minutes, and if there is a change, running the regression tests and uploading results to a web site. For current VC++ results, see http://mysite.verizon.net/beman/win32-trunk-results.html On these runs the reporting is set to show a row only if the results are something other than a simple "pass" without link. For slightly outdated Linux results, see http://mysite.verizon.net/beman/ubuntu-trunk-results.html Here the results show all tests, regardless of result. The idea is to supplement the regular regression tests at http://beta.boost.org/development/tests/trunk/developer/serialization.html with rapid turnaround tests on a few major platforms, aimed at giving developers quick response as they try to fix bugs affecting platforms they don't have access to. At the current level failures, the Win32 tests are turning around in 11 minutes while the Linux tests turn in 4 minutes. Thus worst case developers can see test results in 26 minutes! It seems to me this might be helpful to developers. Opinions? Presumably in regular use the upload would go to a centralized site. Or maybe decentralization is useful for reliability; a boost web page could contain links. Opinions on that? Which reporting do you prefer? My preference is just to show the tests with something to report. --Beman

6 9

[utility] value_init warning
by Gennadiy Rozental 16 Oct '07

16 Oct '07

Hi, I am buiulding trunk vertion of Boost.Test with msvc 8.0 and see following warning: ..\..\..\boost/utility/value_init.hpp(73) : warning C4345: behavior change: an object of POD type constructed with an initializer of the form () will be default-initialized ..\..\..\boost/utility/value_init.hpp(70) : while compiling class template member function 'boost::vinit_detail::non_const_T_base<T>::non_const_T_base(void)' with [ T=arg ] ..\..\..\boost/utility/value_init.hpp(139) : see reference to class template instantiation 'boost::vinit_detail::non_const_T_base<T>' being compiled with [ T=arg ] ..\..\..\boost/mpl/for_each.hpp(72) : see reference to class template instantiation 'boost::value_initialized<T>' being compiled with [ T=arg ] ..\..\..\boost/mpl/for_each.hpp(97) : see reference to function template instantiation 'void boost::mpl::aux::for_each_impl<false>::execute<first,last,TransformOp,F>(Iterator *,LastIterator *,TransformFunc *,F)' being compiled with [ TransformOp=boost::mpl::make_identity<boost::mpl::_>, F=boost::unit_test::ut_detail::generate_test_case_4_type<boost::unit_test::ut_detail::template_test_case_gen<free_test_function,numbers>,free_test_function>, Iterator=first, LastIterator=last, TransformFunc=boost::mpl::make_identity<boost::mpl::_> ] ..\..\..\boost/test/test_case_template.hpp(123) : see reference to function template instantiation 'void boost::mpl::for_each<TestTypesList,boost::mpl::make_identity<T>,boost::unit_test::ut_detail::generate_test_case_4_type<Generator,TestCaseTemplate>>(F,Sequence *,TransformOp *)' being compiled with [ TestTypesList=numbers, T=boost::mpl::_, Generator=boost::unit_test::ut_detail::template_test_case_gen<free_test_function,numbers>, TestCaseTemplate=free_test_function, F=boost::unit_test::ut_detail::generate_test_case_4_type<boost::unit_test::ut_detail::template_test_case_gen<free_test_function,numbers>,free_test_function>, Sequence=numbers, TransformOp=boost::mpl::make_identity<boost::mpl::_> ] ..\..\..\boost/test/test_case_template.hpp(118) : while compiling class template member function 'boost::unit_test::ut_detail::template_test_case_gen<TestCaseTemplate,TestTypesList>::template_test_case_gen(boost::unit_test::const_string)' with [ TestCaseTemplate=free_test_function, TestTypesList=numbers ] test_case_template_example.cpp(27) : see reference to class template instantiation 'boost::unit_test::ut_detail::template_test_case_gen<TestCaseTemplate,TestTypesList>' being compiled with [ TestCaseTemplate=free_test_function, TestTypesList=numbers ] Can we do something about it? Gennadiy

3 4

[Exception] Do we really need to register?
by Josh Napoli 16 Oct '07

16 Oct '07

I like the append capability of the Exception library I wrote an exception type that packed passed values into a "cons-list" (from the tuple library), and used stream-inserter syntax. The concise syntax has proven to be effective at preventing laziness with error cases. Support for asynchronous exception handling is also very important, but is missing from Exception. Can exception::pimpl remember the user exception type (CRTP), for the sake of clone/raise? The need to preregister tag types is slightly annoying. The need to specify the data-type with the tag is especially annoying. Why not use accompanying text as a key to retrieve values? For example, I would rather write this: class my_exception : public exception<my_exception> {}; void main() { try { int value=5; throw exception() << "Something went wrong. value=" << value; } catch(my_exception& e) { int value=e.get<int>("value="); //search for a field preceded by "value=" cout << value; } } You wouldn't even need to give the key text if you expect the field type to be unique in the exception. The internal map seems awkward, particularly because it discards the order in which attributes are added. -Joshua Napoli

2 2

[soc] Boost.extension/reflection project advances
by Mariano Gabriel Consoni 16 Oct '07

16 Oct '07

Hi Community...! As some of you may know, I'm working on a SoC project called "Boost.extensions and reflection". This mail is just to keep you informed about the project advances. At this time, we have very good news. The library is now near completion, and we expect submitting it for revision in the next days. We've been worked the last two weeks in the following tasks: - Code style: continued improving the code style according Boost guidelines. - Build: improved the Jamfiles to work well in more platforms. - Boost::function: migrated some code to (optionally) use boost::function. - Benchmarks: made new benchmarks to test the new integrations. - Performance analysis: documented the results of the benchmarks. - Preprocessor: replaced a lot of boiler-plate code with (optional) boost::preprocessor macros. - Dependencies flags: documented the optional dependencies and how to enable them. As I have finished all the tasks planned in my proposal (and a lot more :) ) I will advance to Reflection part and Jeremy (Pack, original author) will finish some remaining tasks of Extension. Bye! -- Mariano

4 6

[test] BOOST_AUTO_TEST for gcc broken on trunk
by Jürgen Hunold 16 Oct '07

16 Oct '07

Hi ! The latest changes to Boost.Test broke gcc (at least for me) running the Boost.Test testsuite _all_ tests using BOOST_AUTO_TEST fail with -- snip -- terminate called after throwing an instance of '__gnu_cxx::recursive_init_error' what(): std::exception --snap-- I've attached the output of one test run and the corresponding stack trace. I've traced this down to unit_test_suite_impl.hpp, line 287. This is: static auto_tc_exp_fail*& instance() { ->> static auto_tc_exp_fail inst; static auto_tc_exp_fail* inst_ptr = &inst; return inst_ptr; } It seems that gcc does something different than msvc... Ah, yes, gcc -v yields: Using built-in specs. Target: x86_64-suse-linux Configured with: ../configure --enable-threads=posix --prefix=/usr --with-local-prefix=/usr/local --infodir=/usr/share/info --mandir=/usr/share/man --libdir=/usr/lib64 --libexecdir=/usr/lib64 --enable-languages=c,c++,objc,fortran,obj-c++,java,ada --enable-checking=release --with-gxx-include-dir=/usr/include/c++/4.1.2 --enable-ssp --disable-libssp --disable-libgcj --with-slibdir=/lib64 --with-system-zlib --enable-shared --enable-__cxa_atexit --enable-libstdcxx-allocator=new --program-suffix=-4.1 --enable-version-specific-runtime-libs --without-system-libunwind --with-cpu=generic --host=x86_64-suse-linux Thread model: posix gcc version 4.1.2 20061115 (prerelease) (SUSE Linux) Any ideas on how to solve this ? Yours, Jürgen -- * Dipl.-Math. Jürgen Hunold ! Ingenieurgesellschaft für * voice: ++49 511 262926 57 ! Verkehrs- und Eisenbahnwesen mbH * fax : ++49 511 262926 99 ! Lister Straße 15 * juergen.hunold(a)ivembh.de ! www.ivembh.de * * Geschäftsführer: ! Sitz des Unternehmens: Hannover * Prof. Dr.-Ing. Thomas Siefer ! Amtsgericht Hannover, HRB 56965 * PD Dr.-Ing. Alfons Radtke !

3 2

Trac open bugs - by assignee
by Marshall Clow 16 Oct '07

16 Oct '07

[ 224 open bugs today, 221 yesterday ] If you are maintaining a library, and have not logged into the trac system at <http://svn.boost.org/trac/boost/>, please do so ASAP. Until you do that, no tickets can be assigned to you, and will remain under "None". Instructions on working with tickets can be found at: <http://svn.boost.org/trac/boost/wiki/TicketWorkflow> and a mapping of user names to "real names" can be found at: <http://svn.boost.org/trac/boost/report/16> 18 ramey 15 dgregor 15 az_sw_dude 14 grafik 14 djowel 12 doug_gregor 12 None 11 turkanis 10 rogeeff 9 dave 8 nesotto 7 jsiek 7 anthonyw 7 agurtovoy 6 vladimir_prus 5 samuel_krempp 5 bemandawes 4 witt 4 shammah 4 johnmaddock 4 fcacciola 3 pdimov 3 jbandela 3 igaztanaga 3 danielw 2 urzuga 2 nasonov 2 jmaurer 2 hubert_holin 2 hkaiser 2 ebf 1 t_schwinger 1 speedsnail 1 samuel_k 1 pavol_droba 1 kaalus 1 guwi17 1 dlwalker 1 aaron_windsor 1 <Blank> <Blank> 1307 [lambda] invalid boostbook None 1048 Spirit returns full = false in 1.34 if there is trailing spaces in input None 1068 Mersenne twister disables streaming for Visual C++ None 1094 Finding the correct library to link (feature request for pkg-config support)h None 1187 bcp copy not needed files None 1222 lambda::ret<T> should declare result_type. None 1247 Typos in "boost/random/additive_combine.hpp"_ lines 68-69 None 1252 [pool] severe overhead with unaligned sizes. None 1270 uniform_smallint doesn't compile with lagged_fibonacci random number generators None 1291 config.hpp fails to compile with gcc -Wundef None 1311 Can't call base members on derived object in unit_test None 960 [random] lognormal_distribution problem None 991 [pool] aaron_windsor 778 top-level configure is broken agurtovoy 1001 gcc 4.1.2 segfaults on mpl/test/apply.cpp agurtovoy 1051 MPL header ordering triggers bug agurtovoy 1099 unable to iterate through a "non-explicitly-declared" mpl::set agurtovoy 1215 Boost 1.34.1_ mpl: Wrong workaround detection using MinGW32 (or.hpp_ line #33) agurtovoy 1317 has_xxx randomly broken in msvc agurtovoy 588 mpl::remove compile error with gcc 4.1.0 agurtovoy 640 documentation mistake anthonyw 1154 tss destruction segfaults in conjunction with dlopen/dlclose anthonyw 1168 [thread] tss crashes randomly anthonyw 1226 macro TEXT() in GetProcAddress() anthonyw 1268 xtime_cmp changes to deal with overflow were reverted anthonyw 1323 Assertion Error during cleanup after running out of thread resources anthonyw 876 xtime documentation incomplete anthonyw 881 errors when build with Apache stdcxx az_sw_dude 1028 typo in boost header: date_time/time_defs.hpp az_sw_dude 1078 from_iso_string cannot read the output from to_iso_string az_sw_dude 1098 Urgent libboost-date-time1.33.1 : bugs on ia64 ? az_sw_dude 1147 date_time library contains global #define ERROR az_sw_dude 1160 warning: month_format shadows a member of this az_sw_dude 1162 warning: ticks shadows a member of this az_sw_dude 1289 posix_time::time_facet forgets to pass a_ref argument to base class az_sw_dude 1299 change in typedef stringstream_type in format_date_parser.hpp causing compilation error az_sw_dude 1306 invalid docbook in date_period.xml az_sw_dude 287 wrong usage of ios_base::narrow az_sw_dude 316 date_time type conversion warning az_sw_dude 604 from_ftime incorrectly processes FILETIME filled with zeros az_sw_dude 642 operator<< for gregorian::date_duration not found az_sw_dude 889 Insane Dependencies az_sw_dude 890 date_time library supports only the current dst rule bemandawes 1230 mbstate uninitialized bemandawes 1312 boost::filesystem link error on mac os x bemandawes 559 linker error mingw 3.4.5 bemandawes 752 directory_iterator doesn't work with catch bemandawes 897 exists() throws exeption on existing but locked file on wind danielw 1044 Argument pack inaccessable in a functions return type danielw 1054 Parameter takes an "infinite" amount of time to compile with the Intel compiler. danielw 1097 keyword.hpp generates many warnings C4180: qualifier applied to function type has no meaning; ignored dave 1010 linking boost.python on freebsd dave 1019 iterator_facade::pointer should be the return type of operator-> (DR 445) dave 1085 Python rules for compiling in Mac OS X dave 1096 Tutorial needs updating for BBv2 dave 1179 [boost.python] can not export a union in VC2005sp1 dave 1181 [boost.python] can modify enum value dave 1246 breakage in boost::python svn trunk dave 865 Use of C++0x keyword as identifier dave 910 gcc strict-aliasing problems with python dgregor 1002 [iostreams] close_impl<closable_tag> does not comply with spec dgregor 1003 [iostreams] copy-paste error in typedefs for wchar multichar_filters dgregor 1011 amd64: #error Boost.Numeric.Interval: Please specify rounding control mechanism. dgregor 1139 [iostreams] Regex filter segfaults when zero matches found dgregor 1140 boost::iostreams linked_streambuf bug dgregor 1149 Minor doc error in basic_null_device dgregor 1164 Floyd Warshall broken with unsigned edge weights dgregor 1185 iostreams::direct_streambuf<T_Tr>::is_open always returns false if output iterator is not null dgregor 1192 [boostbook] problem when two files have the same name dgregor 1199 configure doesn't work with path containing whitespaces (MacOS X) dgregor 1232 mapped_file_source::is_open() is broken under windows dgregor 1310 [result_of] const-qualified function pointer doesn't work dgregor 556 Bundled graph properties dgregor 732 Johnson All-Pairs needs better "no path" information dgregor 736 Const correctness violation djowel 1170 Emit Warnings instead of # symbols in the syntax highlighter djowel 1171 Quickbook title output djowel 1172 non-utf djowel 1176 Space after inline code djowel 1206 Escaping from within code? djowel 1273 CR+LF newlines in position_iterator djowel 1276 spirit problem with _GLIBCXX_DEBUG djowel 1277 Closing section like [pre with } causes Quickbok to crash djowel 1280 sections in imported source files get put inside <para> elements in docbook output djowel 1281 Quickbook produces invalid BoostBook/DocBook XML djowel 1324 tuple should have a swap() that operates element-by-element djowel 241 Miss " = ParserT()" djowel 314 spirit insert_key_actor.hpp djowel 664 crash in boost::spirit::parse dlwalker 613 boost/crc.hpp uses non-standard conforming syntax doug_gregor 1021 [Graph][reverse_graph] Problem using reverse_graph adapter with an adapted user defined graph doug_gregor 1076 compile error: disconnecting struct with operator()() doesn't work in VS2005 SP1 doug_gregor 375 LEDA graph adaptors do not handle hidden nodes properly doug_gregor 402 random_vertex/random_edge are unnecessarily inefficient doug_gregor 403 Document copy_component doug_gregor 447 reverse_graph and constness of property maps doug_gregor 708 Dijkstra no_init version should not require VertexListGraph doug_gregor 733 Numbered headers don't work with "preferred" syntax doug_gregor 735 Fruchterman-Reingold grid performance can be improved doug_gregor 738 Memory leaks with signal::connect? doug_gregor 829 Implicit graph not implement doug_gregor 852 Problem with Boost and GCC 4.1 ebf 965 [doc] boost::variant tutorial - final example uses v1_v2 should be seq1_seq2 ebf 993 Variant should use least common multiple of alignments_ rather than maximum fcacciola 1217 value_initialized leaves data uninitialized_ when using MSVC fcacciola 1301 copy-initialization from const-qualified object doesn't work fcacciola 617 Numeric Conversion Documentation minor bug fcacciola 818 No zero-argument in_place() grafik 1023 inspect grafik 1041 Cygwin requires PATH setting. grafik 1062 Cygwin install stage fails with combination of patches grafik 1146 KAI Referenced in compiler status acknowledgements grafik 1233 Boost website still refers to CVS grafik 1244 Broken links to unit test examples grafik 1318 http links have gone bad in boost.test documentation grafik 1322 trac rejects patch attachment as spam grafik 546 boost.build needs fixes for HP/UX grafik 616 Boost Jam_ and non english directorys grafik 896 <native-wchar_t>off does not work when build with vc-8.0 grafik 959 linking fails when Boost is compiled with STLport 5.1.* on Linux (names mismatch) grafik 977 bjam crashes when compiled with gcc 4.2 grafik 986 Problem building Python modules on boost 1.34.0 guwi17 1237 Resizing symmetric matrices hkaiser 1077 Spirit integer parser does not always detect integer overflow hkaiser 1079 boost-1.34.0 fails to compile. concept checks not satisfied. hubert_holin 162 Cannot compile octonion_test.cpp because of bug in sinc.hpp hubert_holin 647 octonion documentation bug igaztanaga 1080 boost::interprocess win32 global file mapping issue igaztanaga 1210 interprocess::barrier hangs during second use under linux (boost 1.33.1) igaztanaga 1231 interprocess_condition (emulated) hangs after notify_all(). jbandela 283 Compiler error for tokenizer on Solaris jbandela 501 token_iterator::at_end() result is inversed jbandela 665 bug in char_separator jmaurer 351 Diff in state of mersenne_twister gen between GCC3.41 & CW9 jmaurer 819 uniform_int<> with type's maximum availaible range error johnmaddock 1081 Empty string rejected as perl-style regex johnmaddock 1083 boost_regex 1.34.0 uses ICU library without linking to it johnmaddock 1148 boost_1_34_1 regex library compile failure on aix with xlv johnmaddock 1314 Using SSE-intrinsics in VC8 causes static assert in type_with_alignment.hpp jsiek 416 Spelling of Edmonds-Karp-Algorithm jsiek 575 Calling subgraph::global_to_local on a root graph jsiek 636 strange compiling problem for transitive_closure jsiek 813 concept_check.hpp unused variable warning jsiek 815 remove_edge core dumps on self-circle jsiek 875 No iterator based constructor for adjacency_matrix jsiek 900 graphml reader namespace handling is broken kaalus 1184 property_tree assignment (operator) bug nasonov 1220 lexical_cast requires RTTI nasonov 754 boost::any - typeid comparison across shared boundaries nesotto 1145 Small bugs in Boost.Range documentation nesotto 1284 [range] sub_range assignment issue nesotto 1308 two assign_decays again nesotto 471 boost.range and "const char[]". nesotto 518 [Boost.Range]boost::const_begin calls non-qualified 'begin' nesotto 723 local_time_facet error in VS2005 Win2003 nesotto 730 The ptr_map iterator cannot be dereference to value type nesotto 807 boost::assignment documentation: mathematical "typo" pavol_droba 1152 rle_example fails pdimov 1106 shared_ptr<T> should not convert to shared_ptr<U> when T* doesn't convert to U* pdimov 1108 shared_ptr does not compile under g++ with -fno-rtti pdimov 997 error in boost::bind doc ramey 1036 assert failure in oserializer.hpp:418 ramey 1038 "<" and ">" should be excaped in xml_oarchive ramey 1086 Serialization of weak_ptr produces invalid XML ramey 1089 missing boost::serialization::make_nvp in pointer container library ramey 1121 xml_archive_exception is missing seperate header file_ and documentation mismatch ramey 1137 Virtual destructor is missing ramey 1141 Dangerious operator<< for wostream ramey 1142 boost/serialization/optional doesn't include necessary header ramey 1223 boost::serialization chokes on correcly formatted empty XML element ramey 1267 Assertion `new_cid == cid' failed in basic_iarchive ramey 1285 [serialization] problem when including shared_ptr_132.hpp ramey 1286 Missing/Incorrect dllimport/dllexport directives prevent Windows DLLs from building ramey 1290 Serialization export.hpp (or type_info_implementation.hpp) is NOT self-contained and causes compile error ramey 757 xml serialization fails when using namespace ramey 878 error C2039: 'mbstate_t' : is not a member of 'std' ramey 961 boost::basic_binary_oprimitive not instantiated correctly ramey 968 xml_grammar - incorrect define char ramey 969 basic_binary_iprimitive::load_binary bug rogeeff 1030 execution_monitor.ipp #warning directive breaks compilation on MSVC 8.0 rogeeff 1032 typo in Boost.Test documentation rogeeff 1050 BOOST_CHECK_CLOSE_FRACTION documentation missing rogeeff 1060 no example sources in online docs for Boost::Test rogeeff 1212 Template fixtures rogeeff 607 Log level names wrong in documentation rogeeff 842 typo in auto_unit_test.hpp Revision 1.17 rogeeff 893 grammatical error in error message rogeeff 956 Doc error in test examples. rogeeff 962 Missing links in Test library documentation samuel_k 585 64 bit compile warning/error for boost::format samuel_krempp 1195 patch: boost/format/parsing.hpp does not compile if BOOST_NO_LOCALE_ISDIGIT is defined samuel_krempp 1196 Patch: when BOOST_NO_STD_LOCALE is not defined_ boost/format/internals.hpp fails to compile. samuel_krempp 1278 declaration of 'str' shadows a member of 'this' samuel_krempp 704 format zero length string msvc-8 samuel_krempp 859 boost::format ignores a user defined locale shammah 284 pool::purge_memory() does not reset next_size shammah 290 perfomance: memory cleanup for pool takes too long shammah 386 boost::pool_allocator breaks with vector of vectors shammah 88 ct_gcd_lcm.hpp compilation error speedsnail 1138 Problems with TSS and static thread library t_schwinger 1100 Building boost.function_types fails cvs rev-1.1_ no chdir command in bash turkanis 1033 iostreams::restrict doesn't work on an iostreams::file_source turkanis 1070 [iostreams]boost\iostreams\copy.hpp line80 copy_impl turkanis 525 problem with boost::iostreams when compiled with Visual C++ turkanis 699 Changing size of memory-mapped file on Windows turkanis 786 bug in iostreams/copy.hpp line 81 turkanis 791 iostreams::tee_filter is for output only turkanis 817 Performance problem in iostreams turkanis 822 Incorrect usage of bad_write()_ bad_seek() etc. turkanis 823 Seekable file_descriptor_source /sink? turkanis 824 BOOST_IOSTREAMS_HAS_LSEEK64 on Mac OS X turkanis 856 iostreams file_descriptor::write fails under Win32 urzuga 574 [boost::lambda] Compile error with libstdc++ debug mode urzuga 781 Lambda: (_1 + "y")(string("x")) Doesn't Compile vladimir_prus 1165 more quoting problems vladimir_prus 1274 Useless error message vladimir_prus 1275 boost::program_options::validation_error::what() is private vladimir_prus 1321 invalid docbook in tool documentation vladimir_prus 469 multitoken broken vladimir_prus 689 [program_options] Endless loop with long default arguments witt 1046 Boost.Python quickstart instructions mention nonexistent target witt 834 Homepage regression links witt 957 The "Getting Started" page does not mention the stdlib option witt 973 zip_iterator has value_type == reference -- -- Marshall Marshall Clow Qualcomm, Inc. <mailto:mclow@qualcomm.com> The famous British scientist, Lord Kelvin, said: "When you measure what you are speaking about and express it in numbers, you know something about it, but when you cannot (or do not) measure it, when you cannot (or do not) express it in numbers, then your knowledge is of a meagre and unsatisfactory kind."

1 0

A (much) better object factory
by Marco Costalba 16 Oct '07

16 Oct '07

Hi all, having a night asleep due to jet lag I have hacked another object factory code. Download factory_16_10_2007.zip from Boost Vault or directly with: http://tinyurl.com/yq7cap This new object factory is IMHO much more powerful and has a much better design then the previous one. It is based on complete different ideas and has all the features of the previous one with added implicit argument conversions, so that asking the factory for an object now mimics 100% what you would have calling the object c'tor directly. It is an integration of the new 'overload' utility with Tobias boost::factory (get from Vault) As 'overload' utility I used mine (original code by Joel) not Marco Cecchetti' s one because I only needed a very trimmed down version, I have trimmed down also mine that was already very small !! There are no stored variables or member data anywhere. The factory itsef is just a bunch of typedefs and few static member functions. I think code is small and nice for the task and further polishing could be expected. Previous simple_factory.zip code has been retired from Boost Vault to not pollute the namespace ;-) Marco

1 0

[test][msvc-6.0/7.0] problem with rev. 40035 of boost/test/impl/unit_test_suite.ipp
by Joaquín Mª López Muñoz 16 Oct '07

16 Oct '07

The aforementioned rev includes the following new member function: test_unit_id test_suite::get( const_string tu_name ) const { BOOST_TEST_FOREACH( test_unit_id, id, m_members ) { if( const_string(framework::get( id, test_id_2_unit_type( id ) ).p_name) == tu_name ) return id; } return INV_TEST_UNIT_ID; } which unfortunately results in the following code: #include <boost/test/included/test_exec_monitor.hpp> int test_main(int,char *[]) { return 0; } failing in MSVC++ 6.0 (and possibly also 7.0) with: ...\boost\test\impl\unit_test_suite.ipp(158) : error C2676: binary '==' : 'class boost::unit_test::readwrite_property<class std::basic_string<char,struct std::char_traits<char>, class std::allocator<char> > >' does not define this operator or a conversion to a type acceptable to the predefined operator Looks like the compiler is having a hard time with ADLing the appropriate overload of operator== in this particular dependent context. By changing the offending line like this, however, if( const_string( framework::get( id, test_id_2_unit_type( id ) ).p_name ) == tu_name ) everything works fine (checked in MSVC++ 6.0 and GCC 3.2). As this is a rather innocent change and definitely helps poor old MSVC++ 6.0, is it OK to commit the attached patch? Thank you, Joaquín M López Muñoz Telefónica, Investigación y Desarrollo Index: unit_test_suite.ipp =================================================================== --- unit_test_suite.ipp (revision 40053) +++ unit_test_suite.ipp (working copy) @@ -155,7 +155,7 @@ test_suite::get( const_string tu_name ) const { BOOST_TEST_FOREACH( test_unit_id, id, m_members ) { - if( framework::get( id, test_id_2_unit_type( id ) ).p_name == tu_name ) + if( const_string( framework::get( id, test_id_2_unit_type( id ) ).p_name ) == tu_name ) return id; }

3 4

[pimpl] Proposal. Determining interest.
by Vladimir.Batov＠wrsa.com.au 15 Oct '07

15 Oct '07

I wrote a Pimple generalization thin interface layer on top of boost::shared_ptr or boost::impl_ptr (uploaded in the Boost Vault as Pimpl-01.zip). Based on previous discussions I extended my original suggestion to support pointer and value semantics. The code is very simple but offers the following advantages: 1. First is obviously implementation hiding. The reason Pimpl come to being in the first place. 2. Pimpl-based classes only define pure application interface without any usual scaffolding. 3. Memory management is fully encapsulated (delete and new) to minimize abuse/mis-use. Currently I've been using and testing it only in pointer-semantics mode. If it is determined that there is sufficient interest in the suggestion, we'll need to bring in Peter Dimov's impl_ptr and extend it a bit (that's my current impression.Peter might prove me wrong) Thanks, Vladimir.

1 0

[serialization] Proposal for an extension API to the Archive concept
by "JOAQUIN LOPEZ MU?Z" 15 Oct '07

15 Oct '07

Reviewing the discussion in the thread entitled "[serialization][trunk] please bring us archive helpers back" at http://lists.boost.org/Archives/boost/2007/09/127065.php , I've been thinking about the design issues raised there and I'd like to make a proposal for a seamless extension API that I think can solve the practical concerns originating the discussion while addressing Robert's policy of keeping the Archive concept simple. The last proposal Robert made regarding the helper API and special support for shared_ptr can be summarized in the following points: 1. The Archive concept does not include any extra requirement concerning special support for shared_ptr and/or a helper API. 2. There are naked_* archive implementations which conform to the bare requirements of the Archive concept. 3. The traditional archive implementations (without the "naked_" prefix) inherit from naked_ as well as from a class shared_ptr_helper and a class named, say, helper_api so that special support for shared_ptr and a helper API are provided. This approach has pros and cons: pros: the Archive concept is not polluted by impure considerations such as those accomodating shared_ptr and helpers, thus helping keep the conceptual design and the work of archive implementers simple. cons: A naked archive implementation, while conforming with the concept requirements, will fail to handle shared_ptr and any type relying on the helper API. My point of view is that this solution is just a half-baked one: having a conformant archive which fails to handle shared_ptrs would come as a surprising (and annoying) fact to users of B.S. So, how to make B.S provide shared_ptr and helper support whitout polluting the archive concept with too specific provisions? My proposal is to add a single "hook" to the Archive concept which is as agnostic as possible and can be leveraged in the future for unforeseen necessities beyond shared_ptr and helper support. Add the following requirement to the Archive concept (both Saving and Loading): a.get_extension_obj(p); a.set_extension_obj(p); Returns and sets, respectively, an internal object of type shared_ptr<void>. This object is default initialized upon archive construction and is destroyed along with destruction of the archive. These expressions are reserved for the internal usage of Boost.Serialization and thus must not be called by user code. >From the point of view of the implementer of an Archive, satisfying this new requirement is as simple as having an internal member of type shared_ptr<void> and granting access to it through member functions as described above. That's all the extra burden put on the Archive concept. So far, the concept is not polluted with considerations on shared_ptrs, helpers or anything. How can Boost.Serialization leverage this extension API to *universally* provide helper and shared_ptr support for any Archive type? The following is an skectch of the procedure: B.S can define an internal type resembling this: class extension: public shared_ptr_helper, public helper_api {}; where shared_ptr_helper is more or less like the currently existing class and helper_api will package the helper API functions formerly present in Boost 1.34 (lookup_helper, insert_helper, etc.) Now, B.S can publicly provide the following helper API to user code: namespace boost{ namespace serialization{ template<typename Archive> void lookup_helper( Archive& ar, const extended_type_info* eti, shared_ptr<void> & sph); // rest of the helper API ... } } which is implemented along the following lines: template<typename Archive> void lookup_helper( Archive& ar, const extended_type_info* eti, shared_ptr<void> & sph) { // get the extension object or create a new one if this // is the first time shared_ptr<void> ext_obj=ar.get_extension_obj(); if(!ext_obj){ ext_obj.reset(new extension); ar.set_extension_obj(ext_obj); } extension& ext=*ext_obj; // forward to the extension object ext.lookup_helper(eti,sph); } and similarly for the other helper API and shared_ptr support functions. What do we gain with this? 1. The Archive concept is kept almost intact, and the required extension is both trivial to implement and totally agnostic. 2. We can provide support for shared_ptr and helpers *universally*, without putting the burden of its implementation to the writers of Archive classes. This extra functionality will be called using a notation boost::serialization::foo(ar,...); instead of ar.foo(...); but this is the only drawback (if it can be considered a drawback.) 3. Future functionality can be added by Boost.Serialization to Archives by adjoining it to the internal extension class without the Archive concept or its implementation needing any revision at all. How do you like it? Your feedback is greatly appreciated. Joaquín M López Muñoz Telefónica, Investigación y Desarrollo

5 15

CIA hooks for Boost IRC channel
by Vladimir Prus 15 Oct '07

15 Oct '07

CIA is an mechanism how commits to open source projects can be announced on IRC channels for the corresponding project. It's a great way to keep everybody informed about what's going on, and in nicely complements commit emails -- since IRC audience not necessary reads commit emails, and IRC messages are more convenient to get rid of ;-) What would people say about setting up such thing for Boost? It basically requires adding another post-commit hook, which is a small Python script. The docs can be found at: http://cia.vc/doc/ and the script can be found at: http://cia.vc/clients/svn/ciabot_svn.py and if this idea sounds worthwhile, I can provide a version of that script with Boost-related properties filled in. - Volodya

3 2

Question about asio socket time
by Sebastian Deutsch 15 Oct '07

15 Oct '07

hello, i'm trying to implement a synchronous httprequest - almost everything is fine - but when a host is not reachable the timeout takes pritty long. is there any change to set the timeout manually or do i have to switch to an asynchrounus implementation with a deadline timer? regards sebastian deutsch

1 0

[date_time][patch] svn docs build failure
by Frank Mori Hess 15 Oct '07

15 Oct '07

I have to apply the attached patch to one of the date_time jamfiles to get the docs in svn to build. Otherwise, some of the parameters to some xsltproc calls get doubly quoted, like ""Gregorian Reference" below: "/usr/bin/X11/xsltproc" --stringparam boost.doxygen.reftitle ""Gregorian Reference"" --xinclude -o "../bin.v2/libs/date_time/xmldoc/gcc-4.1.2/debug/gregorian_autodoc-xml.boostbook" "/home/fhess/svn/boost/tools/boostbook/xsl/doxygen/doxygen2boostbook.xsl" "../bin.v2/libs/date_time/xmldoc/gcc-4.1.2/debug/gregorian_autodoc-xml.doxygen" warning: failed to load external entity "Reference" cannot parse Reference Does anyone else have this problem or is it just me? -- Frank

3 2

[intrusive] slist error and hashtable_node problem
by Markus Schöpflin 15 Oct '07

15 Oct '07

Hello, I think I found two more issues with intrusive: 1. boost/intrusive/slist.hpp:908 This line calls the non-existing method insert_after_and_dispose(). 2. boost/intrusive/detail/hashtable_node.hpp:65 The operator=() of bucket_impl is missing a return statement. Regards, Markus

2 3