- Boost - lists.preview.boost.org

[Boost-bugs] [ boost-Bugs-1326132 ] format: assert when parsing invalid pattern
by SourceForge.net 13 Oct '05

13 Oct '05

Bugs item #1326132, was opened at 2005-10-13 21:39 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=107586&aid=1326132&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Petr Lindovsky (plindovsky) Assigned to: Nobody/Anonymous (nobody) Summary: format: assert when parsing invalid pattern Initial Comment: An assert occurs in fmter.parse in the following code: boost::format fmter; fmter.exceptions(boost::io::no_error_bits); fmter.parse("Unknown option mask %1$06x%"); ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=107586&aid=1326132&group_… ------------------------------------------------------- This SF.Net email is sponsored by: Power Architecture Resource Center: Free content, downloads, discussions, and more. http://solutions.newsforge.com/ibmarch.tmpl _______________________________________________ Boost-bugs mailing list Boost-bugs(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/boost-bugs

1 0

Bug list status
by Marshall Clow 13 Oct '05

13 Oct '05

Last week: 144 open bugs Today: 117 open bugs Thanks to everyone who dealt with the bugs! Here are the currently opened bugs, sorted by assignee. If you think that a bug has been assigned incorrectly, please let me know! Assignee: agurtovoy <http://sourceforge.net/users/agurtovoy/> Summary: missing ## in some concatenations Bug #: 851623 <http://sourceforge.net/tracker/index.php?func=detail&aid=851623&group_id=75…> Assignee: agurtovoy <http://sourceforge.net/users/agurtovoy/> Summary: mpl::less<> doesn't compile Bug #: 891611 <http://sourceforge.net/tracker/index.php?func=detail&aid=891611&group_id=75…> Assignee: az_sw_dude <http://sourceforge.net/users/az_sw_dude/> Summary: Minor coding issue Bug #: 946917 <http://sourceforge.net/tracker/index.php?func=detail&aid=946917&group_id=75…> Assignee: az_sw_dude <http://sourceforge.net/users/az_sw_dude/> Summary: typos in wrapping_int.hpp Bug #: 949189 <http://sourceforge.net/tracker/index.php?func=detail&aid=949189&group_id=75…> Assignee: az_sw_dude <http://sourceforge.net/users/az_sw_dude/> Summary: wrong usage of ios_base::narrow Bug #: 989487 <http://sourceforge.net/tracker/index.php?func=detail&aid=989487&group_id=75…> Assignee: az_sw_dude <http://sourceforge.net/users/az_sw_dude/> Summary: date_time type conversion warning Bug #: 1069225 <http://sourceforge.net/tracker/index.php?func=detail&aid=1069225&group_id=7…> Assignee: az_sw_dude <http://sourceforge.net/users/az_sw_dude/> Summary: std::locale construction slows down convert_to_lower() Bug #: 1178092 <http://sourceforge.net/tracker/index.php?func=detail&aid=1178092&group_id=7…> Assignee: az_sw_dude <http://sourceforge.net/users/az_sw_dude/> Summary: local_adjustor::utc_to_local throws 'Time label invalid' Bug #: 1220011 <http://sourceforge.net/tracker/index.php?func=detail&aid=1220011&group_id=7…> Assignee: beman_dawes <http://sourceforge.net/users/beman_dawes/> Summary: filesytem::directory_iterator portability Bug #: 735403 <http://sourceforge.net/tracker/index.php?func=detail&aid=735403&group_id=75…> Assignee: beman_dawes <http://sourceforge.net/users/beman_dawes/> Summary: boost::filesystem fails in posix with files containing ':' Bug #: 776146 <http://sourceforge.net/tracker/index.php?func=detail&aid=776146&group_id=75…> Assignee: beman_dawes <http://sourceforge.net/users/beman_dawes/> Summary: clock is not portable Bug #: 788762 <http://sourceforge.net/tracker/index.php?func=detail&aid=788762&group_id=75…> Assignee: beman_dawes <http://sourceforge.net/users/beman_dawes/> Summary: Boost::Filesystem fails when last character in path is ':' Bug #: 875970 <http://sourceforge.net/tracker/index.php?func=detail&aid=875970&group_id=75…> Assignee: beman_dawes <http://sourceforge.net/users/beman_dawes/> Summary: boost::tokenizer implicit typename Bug #: 912368 <http://sourceforge.net/tracker/index.php?func=detail&aid=912368&group_id=75…> Assignee: beman_dawes <http://sourceforge.net/users/beman_dawes/> Summary: filesystem::directory_iterator returns incorrect listing Bug #: 937606 <http://sourceforge.net/tracker/index.php?func=detail&aid=937606&group_id=75…> Assignee: beman_dawes <http://sourceforge.net/users/beman_dawes/> Summary: xtime_cmp: use comparison not subtraction Bug #: 993272 <http://sourceforge.net/tracker/index.php?func=detail&aid=993272&group_id=75…> Assignee: beman_dawes <http://sourceforge.net/users/beman_dawes/> Summary: boost::filesystem::exists is broken on cygwin Bug #: 1010681 <http://sourceforge.net/tracker/index.php?func=detail&aid=1010681&group_id=7…> Assignee: beman_dawes <http://sourceforge.net/users/beman_dawes/> Summary: boost::filesystem is systematically broken Bug #: 1012135 <http://sourceforge.net/tracker/index.php?func=detail&aid=1012135&group_id=7…> Assignee: beman_dawes <http://sourceforge.net/users/beman_dawes/> Summary: Don't work multilevel hierarchy of test suites in dll. Bug #: 1076691 <http://sourceforge.net/tracker/index.php?func=detail&aid=1076691&group_id=7…> Assignee: beman_dawes <http://sourceforge.net/users/beman_dawes/> Summary: boost::filesystem::native() should reject '/' on non-Win32 Bug #: 1151823 <http://sourceforge.net/tracker/index.php?func=detail&aid=1151823&group_id=7…> Assignee: beman_dawes <http://sourceforge.net/users/beman_dawes/> Summary: boost::filesystem::exists has bugs with UNC paths Bug #: 1164057 <http://sourceforge.net/tracker/index.php?func=detail&aid=1164057&group_id=7…> Assignee: beman_dawes <http://sourceforge.net/users/beman_dawes/> Summary: &#1057;ompilation test/minmax_element_test.cpp failed on Sunpro Bug #: 1165844 <http://sourceforge.net/tracker/index.php?func=detail&aid=1165844&group_id=7…> Assignee: beman_dawes <http://sourceforge.net/users/beman_dawes/> Summary: Bad XML format outpout Bug #: 1173937 <http://sourceforge.net/tracker/index.php?func=detail&aid=1173937&group_id=7…> Assignee: beman_dawes <http://sourceforge.net/users/beman_dawes/> Summary: boost::filesystem::equivalent does not work on w98 Bug #: 1235262 <http://sourceforge.net/tracker/index.php?func=detail&aid=1235262&group_id=7…> Assignee: beman_dawes <http://sourceforge.net/users/beman_dawes/> Summary: path and directory_iterator doesn't handle windows root path Bug #: 1259176 <http://sourceforge.net/tracker/index.php?func=detail&aid=1259176&group_id=7…> Assignee: bill_kempf <http://sourceforge.net/users/bill_kempf/> Summary: timeconv.inl to_duration() nsec error Bug #: 548104 <http://sourceforge.net/tracker/index.php?func=detail&aid=548104&group_id=75…> Assignee: bill_kempf <http://sourceforge.net/users/bill_kempf/> Summary: Solaris - once.cpp compile error Bug #: 549162 <http://sourceforge.net/tracker/index.php?func=detail&aid=549162&group_id=75…> Assignee: bill_kempf <http://sourceforge.net/users/bill_kempf/> Summary: condition variables and recursive_mutex Bug #: 1072605 <http://sourceforge.net/tracker/index.php?func=detail&aid=1072605&group_id=7…> Assignee: david_abrahams <http://sourceforge.net/users/david_abrahams/> Summary: DoIterator adaptor documentation missing Bug #: 430821 <http://sourceforge.net/tracker/index.php?func=detail&aid=430821&group_id=75…> Assignee: david_abrahams <http://sourceforge.net/users/david_abrahams/> Summary: iterator_adapter and abstract classes Bug #: 480585 <http://sourceforge.net/tracker/index.php?func=detail&aid=480585&group_id=75…> Assignee: david_abrahams <http://sourceforge.net/users/david_abrahams/> Summary: pytype_check not defined Bug #: 744295 <http://sourceforge.net/tracker/index.php?func=detail&aid=744295&group_id=75…> Assignee: david_abrahams <http://sourceforge.net/users/david_abrahams/> Summary: BPL includes Python.h too late Bug #: 806732 <http://sourceforge.net/tracker/index.php?func=detail&aid=806732&group_id=75…> Assignee: david_abrahams <http://sourceforge.net/users/david_abrahams/> Summary: cast.hpp: greater_than_type_max&lt;false, false&gt; int/uint bug Bug #: 807722 <http://sourceforge.net/tracker/index.php?func=detail&aid=807722&group_id=75…> Assignee: david_abrahams <http://sourceforge.net/users/david_abrahams/> Summary: mpl::select2nd on vc6 Bug #: 812263 <http://sourceforge.net/tracker/index.php?func=detail&aid=812263&group_id=75…> Assignee: david_abrahams <http://sourceforge.net/users/david_abrahams/> Summary: Compiling Boost with Python without Unicode Bug #: 925163 <http://sourceforge.net/tracker/index.php?func=detail&aid=925163&group_id=75…> Assignee: david_abrahams <http://sourceforge.net/users/david_abrahams/> Summary: Error in msvc in building inheritance.obj to build hello.pyd Bug #: 1083760 <http://sourceforge.net/tracker/index.php?func=detail&aid=1083760&group_id=7…> Assignee: david_abrahams <http://sourceforge.net/users/david_abrahams/> Summary: tries to build for old Python 2.2 by default Bug #: 1235310 <http://sourceforge.net/tracker/index.php?func=detail&aid=1235310&group_id=7…> Assignee: david_abrahams <http://sourceforge.net/users/david_abrahams/> Summary: bjam HDRS rule in python tutorial compilation Bug #: 1273836 <http://sourceforge.net/tracker/index.php?func=detail&aid=1273836&group_id=7…> Assignee: dgregor <http://sourceforge.net/users/dgregor/> Summary: no conversion from type to const_type Bug #: 547743 <http://sourceforge.net/tracker/index.php?func=detail&aid=547743&group_id=75…> Assignee: dgregor <http://sourceforge.net/users/dgregor/> Summary: EdgeListS = setS for adjacency_list does not work Bug #: 1163077 <http://sourceforge.net/tracker/index.php?func=detail&aid=1163077&group_id=7…> Assignee: dgregor <http://sourceforge.net/users/dgregor/> Summary: adjacency_matrix should model BidirectionalGraph Bug #: 1168411 <http://sourceforge.net/tracker/index.php?func=detail&aid=1168411&group_id=7…> Assignee: dgregor <http://sourceforge.net/users/dgregor/> Summary: LEDA graph adaptors for undirected graphs Bug #: 1168420 <http://sourceforge.net/tracker/index.php?func=detail&aid=1168420&group_id=7…> Assignee: dgregor <http://sourceforge.net/users/dgregor/> Summary: LEDA adaptors for node_array, edge_array Bug #: 1168424 <http://sourceforge.net/tracker/index.php?func=detail&aid=1168424&group_id=7…> Assignee: dgregor <http://sourceforge.net/users/dgregor/> Summary: LEDA graph adaptors do not handle hidden nodes properly Bug #: 1168431 <http://sourceforge.net/tracker/index.php?func=detail&aid=1168431&group_id=7…> Assignee: dgregor <http://sourceforge.net/users/dgregor/> Summary: Generate patches for Graph bugs in 1.32.0 Bug #: 1169920 <http://sourceforge.net/tracker/index.php?func=detail&aid=1169920&group_id=7…> Assignee: dgregor <http://sourceforge.net/users/dgregor/> Summary: Investigate other kinds of heaps for dijkstra_shortest_paths Bug #: 1170106 <http://sourceforge.net/tracker/index.php?func=detail&aid=1170106&group_id=7…> Assignee: dgregor <http://sourceforge.net/users/dgregor/> Summary: function.hpp breaks assign.hpp Bug #: 1181272 <http://sourceforge.net/tracker/index.php?func=detail&aid=1181272&group_id=7…> Assignee: dgregor <http://sourceforge.net/users/dgregor/> Summary: vertex bundle properties do not work with VC++.NET 2003 Bug #: 1190394 <http://sourceforge.net/tracker/index.php?func=detail&aid=1190394&group_id=7…> Assignee: dgregor <http://sourceforge.net/users/dgregor/> Summary: BGL graph types do not support allocators Bug #: 1193883 <http://sourceforge.net/tracker/index.php?func=detail&aid=1193883&group_id=7…> Assignee: dgregor <http://sourceforge.net/users/dgregor/> Summary: random_vertex/random_edge are unnecessarily inefficient Bug #: 1204684 <http://sourceforge.net/tracker/index.php?func=detail&aid=1204684&group_id=7…> Assignee: dgregor <http://sourceforge.net/users/dgregor/> Summary: Document copy_component Bug #: 1204688 <http://sourceforge.net/tracker/index.php?func=detail&aid=1204688&group_id=7…> Assignee: dgregor <http://sourceforge.net/users/dgregor/> Summary: reverse_graph and constness of property maps Bug #: 1246336 <http://sourceforge.net/tracker/index.php?func=detail&aid=1246336&group_id=7…> Assignee: dgregor <http://sourceforge.net/users/dgregor/> Summary: boost:signals SIGSEV Bug #: 1262038 <http://sourceforge.net/tracker/index.php?func=detail&aid=1262038&group_id=7…> Assignee: djowel <http://sourceforge.net/users/djowel/> Summary: Miss ' = ParserT()' Bug #: 907299 <http://sourceforge.net/tracker/index.php?func=detail&aid=907299&group_id=75…> Assignee: djowel <http://sourceforge.net/users/djowel/> Summary: spirit insert_key_actor.hpp Bug #: 1059936 <http://sourceforge.net/tracker/index.php?func=detail&aid=1059936&group_id=7…> Assignee: djowel <http://sourceforge.net/users/djowel/> Summary: Another config correction for Sun C++ Bug #: 1220782 <http://sourceforge.net/tracker/index.php?func=detail&aid=1220782&group_id=7…> Assignee: dlwalker <http://sourceforge.net/users/dlwalker/> Summary: template problems with common_factor.hpp Bug #: 491637 <http://sourceforge.net/tracker/index.php?func=detail&aid=491637&group_id=75…> Assignee: ebf <http://sourceforge.net/users/ebf/> Summary: boost::blank - missing operators Bug #: 1191356 <http://sourceforge.net/tracker/index.php?func=detail&aid=1191356&group_id=7…> Assignee: glassfordm <http://sourceforge.net/users/glassfordm/> Summary: pthread_delay_np() parm incorrect Bug #: 551157 <http://sourceforge.net/tracker/index.php?func=detail&aid=551157&group_id=75…> Assignee: glassfordm <http://sourceforge.net/users/glassfordm/> Summary: Bosot.Thread.condition(win32).notify_all Bug #: 551308 <http://sourceforge.net/tracker/index.php?func=detail&aid=551308&group_id=75…> Assignee: glassfordm <http://sourceforge.net/users/glassfordm/> Summary: AIX 4.3 SIGSEGV at thread termination Bug #: 551577 <http://sourceforge.net/tracker/index.php?func=detail&aid=551577&group_id=75…> Assignee: glassfordm <http://sourceforge.net/users/glassfordm/> Summary: boost::threads uses msvc only function? Bug #: 568951 <http://sourceforge.net/tracker/index.php?func=detail&aid=568951&group_id=75…> Assignee: glassfordm <http://sourceforge.net/users/glassfordm/> Summary: threads unnecessary #include Bug #: 571615 <http://sourceforge.net/tracker/index.php?func=detail&aid=571615&group_id=75…> Assignee: glassfordm <http://sourceforge.net/users/glassfordm/> Summary: thread_cleanup problems Bug #: 649291 <http://sourceforge.net/tracker/index.php?func=detail&aid=649291&group_id=75…> Assignee: glassfordm <http://sourceforge.net/users/glassfordm/> Summary: Mac implementation of threads is CPU hog Bug #: 885045 <http://sourceforge.net/tracker/index.php?func=detail&aid=885045&group_id=75…> Assignee: glassfordm <http://sourceforge.net/users/glassfordm/> Summary: compiler error on Mac implementation of threads Bug #: 1201779 <http://sourceforge.net/tracker/index.php?func=detail&aid=1201779&group_id=7…> Assignee: glassfordm <http://sourceforge.net/users/glassfordm/> Summary: timeconv.inl line 116 copy/paste error Bug #: 1239052 <http://sourceforge.net/tracker/index.php?func=detail&aid=1239052&group_id=7…> Assignee: glassfordm <http://sourceforge.net/users/glassfordm/> Summary: Exception safety in class 'thread' Bug #: 1305885 <http://sourceforge.net/tracker/index.php?func=detail&aid=1305885&group_id=7…> Assignee: grafik <http://sourceforge.net/users/grafik/> Summary: jam_src build scripts need como --c Bug #: 973310 <http://sourceforge.net/tracker/index.php?func=detail&aid=973310&group_id=75…> Assignee: jbandela <http://sourceforge.net/users/jbandela/> Summary: tokenizer fails with wchar_t Bug #: 446155 <http://sourceforge.net/tracker/index.php?func=detail&aid=446155&group_id=75…> Assignee: jbandela <http://sourceforge.net/users/jbandela/> Summary: tokenizer not works with Dinkumware 308 Bug #: 458236 <http://sourceforge.net/tracker/index.php?func=detail&aid=458236&group_id=75…> Assignee: jbandela <http://sourceforge.net/users/jbandela/> Summary: Tokenizer.hpp doesn't work with BOOST_ENABLE_ASSERT_HANDLER Bug #: 972406 <http://sourceforge.net/tracker/index.php?func=detail&aid=972406&group_id=75…> Assignee: jbandela <http://sourceforge.net/users/jbandela/> Summary: Compiler error for tokenizer on Solaris Bug #: 976241 <http://sourceforge.net/tracker/index.php?func=detail&aid=976241&group_id=75…> Assignee: jbandela <http://sourceforge.net/users/jbandela/> Summary: tokenizer and signed char Bug #: 1003889 <http://sourceforge.net/tracker/index.php?func=detail&aid=1003889&group_id=7…> Assignee: jmaurer <http://sourceforge.net/users/jmaurer/> Summary: Diff in state of mersenne_twister gen between GCC3.41 & CW9 Bug #: 1115124 <http://sourceforge.net/tracker/index.php?func=detail&aid=1115124&group_id=7…> Assignee: joerg_walter <http://sourceforge.net/users/joerg_walter/> Summary: bug in ublas/storage.hpp Bug #: 1095697 <http://sourceforge.net/tracker/index.php?func=detail&aid=1095697&group_id=7…> Assignee: joerg_walter <http://sourceforge.net/users/joerg_walter/> Summary: dead links in uBLAS page Bug #: 1169273 <http://sourceforge.net/tracker/index.php?func=detail&aid=1169273&group_id=7…> Assignee: joerg_walter <http://sourceforge.net/users/joerg_walter/> Summary: Documentation not available on web site: Bug #: 1228242 <http://sourceforge.net/tracker/index.php?func=detail&aid=1228242&group_id=7…> Assignee: joerg_walter <http://sourceforge.net/users/joerg_walter/> Summary: uBLAS::subslice doesn't work Bug #: 1292635 <http://sourceforge.net/tracker/index.php?func=detail&aid=1292635&group_id=7…> Assignee: johnmaddock <http://sourceforge.net/users/johnmaddock/> Summary: Adding boost::is_complex to type_traits.hpp Bug #: 1315712 <http://sourceforge.net/tracker/index.php?func=detail&aid=1315712&group_id=7…> Assignee: jsiek <http://sourceforge.net/users/jsiek/> Summary: Can't use BOOST_CLASS_REQUIRES macro Bug #: 431226 <http://sourceforge.net/tracker/index.php?func=detail&aid=431226&group_id=75…> Assignee: jsiek <http://sourceforge.net/users/jsiek/> Summary: invalid result for File Dependency Examp Bug #: 551110 <http://sourceforge.net/tracker/index.php?func=detail&aid=551110&group_id=75…> Assignee: jsiek <http://sourceforge.net/users/jsiek/> Summary: Spelling of Edmonds-Karp-Algorithm Bug #: 1226292 <http://sourceforge.net/tracker/index.php?func=detail&aid=1226292&group_id=7…> Assignee: kevlin <http://sourceforge.net/users/kevlin/> Summary: Is there a Bug In boost::any&#65311; Bug #: 1009515 <http://sourceforge.net/tracker/index.php?func=detail&aid=1009515&group_id=7…> Assignee: mark_rodgers <http://sourceforge.net/users/mark_rodgers/> Summary: Cannot compile octonion_test.cpp because of bug in sinc.hpp Bug #: 751269 <http://sourceforge.net/tracker/index.php?func=detail&aid=751269&group_id=75…> Assignee: mark_rodgers <http://sourceforge.net/users/mark_rodgers/> Summary: Cannot compile octonion_test.cpp because of bug in sinc.hpp Bug #: 751289 <http://sourceforge.net/tracker/index.php?func=detail&aid=751289&group_id=75…> Assignee: nobody Summary: BCB6 throw EExternelException Bug #: 596149 <http://sourceforge.net/tracker/index.php?func=detail&aid=596149&group_id=75…> Assignee: nobody Summary: boost and VC++ 6 with STLPORT problem Bug #: 618820 <http://sourceforge.net/tracker/index.php?func=detail&aid=618820&group_id=75…> Assignee: nobody Summary: 1.31.0 doesn't support inter-win32-stlport use intel8.0 Bug #: 918570 <http://sourceforge.net/tracker/index.php?func=detail&aid=918570&group_id=75…> Assignee: nobody Summary: failure in boost jam unit tests on cygwin Bug #: 940941 <http://sourceforge.net/tracker/index.php?func=detail&aid=940941&group_id=75…> Assignee: nobody Summary: vc-7_1-stlport native-wchar_t problem Bug #: 1070327 <http://sourceforge.net/tracker/index.php?func=detail&aid=1070327&group_id=7…> Assignee: nobody Summary: 'failed fileclone' when building with -j on 1.32.0 Bug #: 1102389 <http://sourceforge.net/tracker/index.php?func=detail&aid=1102389&group_id=7…> Assignee: nobody Summary: can't compile with intel-linux (icc 8) Bug #: 1105342 <http://sourceforge.net/tracker/index.php?func=detail&aid=1105342&group_id=7…> Assignee: nobody Summary: Can't build on cygwin Bug #: 1145183 <http://sourceforge.net/tracker/index.php?func=detail&aid=1145183&group_id=7…> Assignee: nobody Summary: Muss of 'host' and 'target' Bug #: 1178259 <http://sourceforge.net/tracker/index.php?func=detail&aid=1178259&group_id=7…> Assignee: nobody Summary: boost jam problem with parallel builds Bug #: 1234224 <http://sourceforge.net/tracker/index.php?func=detail&aid=1234224&group_id=7…> Assignee: nobody Summary: Build process doesn't generate DLL import libs on Cygwin Bug #: 1262967 <http://sourceforge.net/tracker/index.php?func=detail&aid=1262967&group_id=7…> Assignee: nobody Summary: html docs frequently missing key words Bug #: 1294420 <http://sourceforge.net/tracker/index.php?func=detail&aid=1294420&group_id=7…> Assignee: ramey <http://sourceforge.net/users/ramey/> Summary: boost::serialization - strings with '&' character included Bug #: 1043942 <http://sourceforge.net/tracker/index.php?func=detail&aid=1043942&group_id=7…> Assignee: ramey <http://sourceforge.net/users/ramey/> Summary: build process still hangs on xml_grammar.cpp Bug #: 1157766 <http://sourceforge.net/tracker/index.php?func=detail&aid=1157766&group_id=7…> Assignee: ramey <http://sourceforge.net/users/ramey/> Summary: Problem writing wstrings containing \0 to xml archives Bug #: 1235441 <http://sourceforge.net/tracker/index.php?func=detail&aid=1235441&group_id=7…> Assignee: ramey <http://sourceforge.net/users/ramey/> Summary: Spelling error in error message Bug #: 1250022 <http://sourceforge.net/tracker/index.php?func=detail&aid=1250022&group_id=7…> Assignee: ramey <http://sourceforge.net/users/ramey/> Summary: polymorphic i/o archives and stl containers problem Bug #: 1250901 <http://sourceforge.net/tracker/index.php?func=detail&aid=1250901&group_id=7…> Assignee: ramey <http://sourceforge.net/users/ramey/> Summary: 1.33 RC2: polymorphic stuff broken further?? Bug #: 1254062 <http://sourceforge.net/tracker/index.php?func=detail&aid=1254062&group_id=7…> Assignee: ramey <http://sourceforge.net/users/ramey/> Summary: 1.33RC2: archive_pointer_[o/i]serializer assert problem Bug #: 1255637 <http://sourceforge.net/tracker/index.php?func=detail&aid=1255637&group_id=7…> Assignee: ramey <http://sourceforge.net/users/ramey/> Summary: VC7.1 operator << doesn't work for non-const objects Bug #: 1260961 <http://sourceforge.net/tracker/index.php?func=detail&aid=1260961&group_id=7…> Assignee: ramey <http://sourceforge.net/users/ramey/> Summary: crash deserializing 1.32 data (poly archive + stl container) Bug #: 1262084 <http://sourceforge.net/tracker/index.php?func=detail&aid=1262084&group_id=7…> Assignee: ramey <http://sourceforge.net/users/ramey/> Summary: Serialization 1.33 assertion failure when deserializing STL Bug #: 1277742 <http://sourceforge.net/tracker/index.php?func=detail&aid=1277742&group_id=7…> Assignee: ramey <http://sourceforge.net/users/ramey/> Summary: extended_type_info crash on global dtors (arm) Bug #: 1307106 <http://sourceforge.net/tracker/index.php?func=detail&aid=1307106&group_id=7…> Assignee: ramey <http://sourceforge.net/users/ramey/> Summary: many 'virtual functions vs. non-virtual destructor' warnings Bug #: 1312222 <http://sourceforge.net/tracker/index.php?func=detail&aid=1312222&group_id=7…> Assignee: rogeeff <http://sourceforge.net/users/rogeeff/> Summary: typo in Boost.Test document Bug #: 629685 <http://sourceforge.net/tracker/index.php?func=detail&aid=629685&group_id=75…> Assignee: rogeeff <http://sourceforge.net/users/rogeeff/> Summary: BOOST_CHECK_CLOSE in Boost Test Library Bug #: 754551 <http://sourceforge.net/tracker/index.php?func=detail&aid=754551&group_id=75…> Assignee: rogeeff <http://sourceforge.net/users/rogeeff/> Summary: BOOST_AUTO_TEST doesn't work across multiple units Bug #: 823589 <http://sourceforge.net/tracker/index.php?func=detail&aid=823589&group_id=75…> Assignee: rogeeff <http://sourceforge.net/users/rogeeff/> Summary: Bug in build via MSVC Solution Bug #: 953876 <http://sourceforge.net/tracker/index.php?func=detail&aid=953876&group_id=75…> Assignee: shammah <http://sourceforge.net/users/shammah/> Summary: ct_gcd_lcm.hpp compilation error Bug #: 558174 <http://sourceforge.net/tracker/index.php?func=detail&aid=558174&group_id=75…> Assignee: shammah <http://sourceforge.net/users/shammah/> Summary: test_pool_alloc.cpp not compile CW8.1 Bug #: 586779 <http://sourceforge.net/tracker/index.php?func=detail&aid=586779&group_id=75…> Assignee: shammah <http://sourceforge.net/users/shammah/> Summary: pool::purge_memory() does not reset next_size Bug #: 984124 <http://sourceforge.net/tracker/index.php?func=detail&aid=984124&group_id=75…> Assignee: shammah <http://sourceforge.net/users/shammah/> Summary: Borland compiler error with Pool, boost::pool_allocator Bug #: 988124 <http://sourceforge.net/tracker/index.php?func=detail&aid=988124&group_id=75…> Assignee: shammah <http://sourceforge.net/users/shammah/> Summary: perfomance: memory cleanup for pool takes too long Bug #: 995270 <http://sourceforge.net/tracker/index.php?func=detail&aid=995270&group_id=75…> Assignee: shammah <http://sourceforge.net/users/shammah/> Summary: boost::pool_allocator breaks with vector of vectors Bug #: 1179641 <http://sourceforge.net/tracker/index.php?func=detail&aid=1179641&group_id=7…> Assignee: turkanis <http://sourceforge.net/users/turkanis/> Summary: Self division wrong in template rational Bug #: 504411 <http://sourceforge.net/tracker/index.php?func=detail&aid=504411&group_id=75…> Assignee: turkanis <http://sourceforge.net/users/turkanis/> Summary: Rational sum not optimal for overflows Bug #: 519635 <http://sourceforge.net/tracker/index.php?func=detail&aid=519635&group_id=75…> Assignee: turkanis <http://sourceforge.net/users/turkanis/> Summary: rational operator&lt; can overflow Bug #: 798357 <http://sourceforge.net/tracker/index.php?func=detail&aid=798357&group_id=75…> Assignee: turkanis <http://sourceforge.net/users/turkanis/> Summary: boost::rational documentation typos(?) Bug #: 1043616 <http://sourceforge.net/tracker/index.php?func=detail&aid=1043616&group_id=7…> Assignee: turkanis <http://sourceforge.net/users/turkanis/> Summary: no Boolean conversion for boost::rational Bug #: 1239906 <http://sourceforge.net/tracker/index.php?func=detail&aid=1239906&group_id=7…> Assignee: vladimir_prus <http://sourceforge.net/users/vladimir_prus/> Summary: call to split_winmain raises exception for 8-bit locale Bug #: 1206663 <http://sourceforge.net/tracker/index.php?func=detail&aid=1206663&group_id=7…> Assignee: vladimir_prus <http://sourceforge.net/users/vladimir_prus/> Summary: multitoken broken in program_options 1.33 Bug #: 1266877 <http://sourceforge.net/tracker/index.php?func=detail&aid=1266877&group_id=7…> -- -- Marshall Marshall Clow Idio Software <mailto:marshall@idio.com> It is by caffeine alone I set my mind in motion. It is by the beans of Java that thoughts acquire speed, the hands acquire shaking, the shaking becomes a warning. It is by caffeine alone I set my mind in motion.

2 1

Boost regression notification (2005-10-13 [HEAD])
by Douglas Gregor 13 Oct '05

13 Oct '05

Boost regression test failures ------------------------------ Report time: 2005-10-13T05:00:24Z This report lists all regression test failures on release platforms. Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-HEAD/developer/issues… 205 failures in 12 libraries: concept_check (13) graph (2) mpl (1) parameter (13) python (1) serialization (36) spirit (8) thread (4) tuple (1) type_traits (1) typeof (21) xpressive (104) |concept_check| stl_concept_covering: cw-9_4 gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin intel-win32-9_0 intel-win32-9_0 mingw-3_4_2 msvc vc-7_1 |graph| graphviz_test: vc-7_1 layout_test: intel-win32-9_0 |mpl| size_t: gcc-4_0-darwin |parameter| basics: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux efficiency: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux msvc macros: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux sfinae: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux msvc unnamed: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux vc-7_1 |python| exec: intel-win32-9_0 |serialization| test_class_info_load_binary_archive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_binary_archive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_archive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_archive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_warchive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_warchive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_archive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_archive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_warchive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_warchive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_const_save_fail1: msvc test_const_save_fail2: msvc test_const_save_fail3: msvc test_map_binary_archive_dll: msvc test_map_text_archive_dll: msvc test_map_text_warchive_dll: msvc |spirit| action_tests_debug: gcc-3_4_3-sunos distinct_tests_debug: gcc-3_4_3-sunos escape_char_parser_tests_debug: gcc-3_4_3-sunos grammar_def_test_debug: gcc-3_4_3-sunos switch_problem_debug: gcc-3_4_3-sunos switch_tests_single_debug: gcc-3_4_3-sunos traverse_tests: intel-win32-9_0 traverse_tests_debug: intel-win32-9_0 |thread| test_condition: gcc-3_4_3-sunos test_mutex: gcc-3_4_3-sunos test_tss: gcc-3_4_3-sunos gcc-3_4_3-sunos |tuple| tuple_test_bench: gcc-3_4_3-sunos |type_traits| tricky_abstract_type_test: intel-win32-9_0 |typeof| data_member_native: cw-9_4 function_native: cw-9_4 msvc function_ptr_native: cw-9_4 function_ref_native: cw-9_4 lvalue_native: cw-9_4 msvc member_function_native: cw-9_4 modifiers_emulation: cw-9_4 modifiers_native: cw-9_4 noncopyable_native: cw-9_4 std_emulation: cw-9_4 std_native: cw-9_4 template_dependent_native: cw-9_4 template_enum_native: cw-9_4 template_int_native: cw-9_4 template_multiword_native: cw-9_4 template_tpl_native: cw-9_4 msvc template_type_native: cw-9_4 type_native: cw-9_4 |xpressive| misc1: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux test1: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux intel-win32-9_0 test1u: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux intel-win32-9_0 test2: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3_3-darwin intel-win32-9_0 test2u: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3_3-darwin intel-win32-9_0 test3: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 test3u: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3_3-darwin intel-win32-9_0 test4: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3_3-darwin test4u: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3_3-darwin test5: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin test5u: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3_3-darwin test6: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin test6u: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3_3-darwin test7: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux intel-win32-9_0 test7u: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux intel-win32-9_0 test8: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux intel-win32-9_0 test8u: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux intel-win32-9_0 test9: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3_3-darwin intel-win32-9_0 test9u: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3_3-darwin intel-win32-9_0 test_basic_regex: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux test_cycles: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux test_dynamic: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux test_match_results: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux test_non_char: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux test_regex_algorithms: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux test_regex_compiler: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux test_regex_error: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux test_regex_iterator: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux test_regex_primitives: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux test_regex_token_iterator: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux test_regex_traits: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux test_static: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux test_sub_match: gcc-2.95.3-linux

1 0

What is Boost?
by David Abrahams 13 Oct '05

13 Oct '05

Hi, Last night I hosted a birds-of-a-feather session at the SD Best Practices conferences here in Boston. I was encouraged that, at a conference that only adopted a C++ track this year, we had 15 people there. It was about evenly split between people who were using Boost and those who just came to find out more about it. Those who were using Boost were really enthusiastic. I was stunned to discover that the rest of them reported that wanted to know what Boost _is_, but that the website doesn't tell them. And when they said that, it hit me like a ton of bricks: they're right! We really need a section at the top of the page titled "What is Boost?" that covers something like the following: * Boost is a collection of C++ libraries - Free for any use - Extensively peer-reviewed - Extensively Tested * When you download Boost, you get the whole collection * There are some dependencies among libraries, but they are not tightly coupled * There is a tool (bcp) for extracting the parts you want and their dependencies. * Many boost libraries can be used just by putting the library collection's top directory in your #include path. Complete instructions for getting started are at: ___ * The important features of the Boost directory structure are: - boost - libs - more - tools (with rough descriptions of each) I'd like to see some discussion of what's missing (or extra) in the list above... and a volunteer to write the introductory passage :) -- Dave Abrahams Boost Consulting www.boost-consulting.com

13 42

Re: [boost] Report from Mont Tremblant C++ Committee meeting
by Thorsten Ottosen 13 Oct '05

13 Oct '05

Gennadiy Rozental <gennadiy.rozental <at> thomson.com> writes: > > >>>String-algo : Interested, but concern over interface and choice of > >>>functions, generic vs basic_string.5.3 separate proposal > >> > >> Any details on this? I love this library, and I would love to see it > >> standardized in some form. Overall I've found the interface and function > >> choices to be excellent (and I'd love to see even more), and I love that > >> it's generic and not limited to basic_string. I use it on vectors and > >> other containers for different kinds of network protocol parsing. > > > > Thorsten Ottosen acted as champion for the paper, but I'll try to recall > > the discussion. > > > > There concern was that at least some of the algorithms were only useful in > > the context of strings, and so it would be an over-generalization to > > supply them as free algorithms. My notes say that the solution that got most support was free-standing functions for "arbitrary strings". So support for stuff like rope was considered important. Let me also recap some other feedback: (a) the algorithms should work directly with string literals as they do today in boost. (b) many requested additional motivation for choosing this particular set of functions. > My point exactly. I believe string_algo library went (completely?) wrong > way. It should never use iterator parameterization, but char type only. If > there exist any algorithm that is useful beyond strings - it doesn't belong > to this library. Well, there are just too many string types out there to base the interface on basic_string<CharT>. Besides, it would not be very c++-ish to preach generic programming yet avoid using it in obvious places in the standard library. -Thorsten

1 0

Re: [boost] [ANN] Phoenix-2 prerelease
by Eric Niebler 13 Oct '05

13 Oct '05

Daryle Walker wrote: > On 10/12/05 7:31 PM, "Eric Niebler" <eric(a)boost-consulting.com> wrote: >> iterator begin, end; >> ... >> boost::make_filter_iterator(arg1 > 5, begin, end); >> // Oops! ---------------------------^ >> >>Isn't that comma going to be Phoenix's overloaded comma? > > > I don't think so. The comma used to separate function (call) arguments > always overrides a comma operator. Yeah, you're right, I figured that out with Joel's help yesterday. C++ is funky. -- Eric Niebler Boost Consulting www.boost-consulting.com

1 0

RTL: Relational Template Library
by Arkadiy Vertleyb 13 Oct '05

13 Oct '05

Hi All. I just uploaded the latest version of Dmitriy Arapov's and my Relational Template Library (RTL) to the Boost file vault, http://tinyurl.com/8lbmg. This version is compatible with Boost 1.33. The RTL was discussed on this list at some time in the past. The early version of RTL is described in the March 2004 issue of CUJ. The main difference from currently discussed RML is that we decided against using SQL - like interface, and use the relational algebra-based interface instead. This choice is caused by our belief that the optimizer -- the module converting SQL query into an optimized relational expression -- is one of the most sophisticated parts of modern database engines. Also, writing a good optimizer in a system like RTL (or RML) would have to be done in large part at compile time, by the means of template meta-programming. This task doesn't seems to be feasible, at least currently. OTOH, writing a primitive optimizer, would, in our opinion do more harm than good. So, the RTL gives its user the possibility to build arbitrary relational expressions by hand. We augment the pure relational algebra with a few things, such as sort order, indexing, groupby, join, etc. We also allow indexing of any relational expressions, not just tables. So, for example, a user can do a selection on some arbitrary complicated criteria, and then index this selection. This would ultimately result in the index storing just keys to these records. This index would be incrementally updated when the underlying table has been changed. Achieving the same effect with conventional approach would require creation of a much larger index on a calculated field. Another example -- you have table of cities, and you need to get all the pairs, such as the distance between them is less than certain number. How would one solve the problem with the conventional SQL approach? This is a self-join. But how to make this query fast? With RTL approach, we could create an index on this self-join. The RTL can currently be compiled with VC7.1 or GCC 3.3+ (although with GCC there might still remain some naming conflicts between MPL and STL, that show up with certain usages) Regards, Arkadiy

6 36

[signals] expected failure markup for como
by Markus Schöpflin 13 Oct '05

13 Oct '05

There are currently two test failures (dead_slot_test, and trackable_test) which are marked as expected for como. The note says: 'The failure is caused by a compiler bug, which has been reported to the compiler supplier (or is already known to them).' Does anyone know the exact circumstances of this compiler bug or even has a small reproducer? Tru64/CXX has the same failures and I would like to submit a bug report to the vendor. Markus

2 3

[signals] usage of any_cast
by Andreas Pokorny 13 Oct '05

13 Oct '05

Hi, We just stumbled across a small problem with Boost.Signals, while playing with the symbol visibility features of gcc-3.4 and gcc-4. That feature is still buggy, but it unveiled some strange code. Somehow gcc failed to turn the type info of the types stored by any into a visible symbol, which is required for using boost::signals across shared libraries. So there are multiple type info objects and the dynamic_casts within signal failed, and the application crashed with a seg fault, since no one expected the cast to fail The code is in signal_template.hpp: template<typename Pair> R operator()(const Pair& slot) const { F* target = const_cast<F*>(any_cast<F>(&slot.second)); return (*target)(BOOST_SIGNALS_BOUND_ARGS); } I dont see why any_cast is used here at all. The type safety is guranteed by the interface of Boost.Signals, so I doubt that someone will be able to abuse the library. I believe the author of that code had the same in mind, since he did not test target != 0 before invoking the target. So in my opinion a simple reinterpret_cast should suffice here. It would also fix our issue, although that one is caused by gcc. Regards Andreas Pokorny

3 5

[mpl] weird interaction between mpl::set and mpl::map headers
by Joaquín Mª López Muñoz 13 Oct '05

13 Oct '05

The following snippet #include <boost/mpl/set/set0.hpp> #include <boost/mpl/map.hpp> int main() { return 0; } produces the following in GCC 3.2: In file included from /usr/local/boost_1_33_0/boost/mpl/map/map0.hpp:18, from /usr/local/boost_1_33_0/boost/mpl/map/map10.hpp:19, from /usr/local/boost_1_33_0/boost/mpl/map/map20.hpp:19, from /usr/local/boost_1_33_0/boost/mpl/map.hpp:36, from mpl_iterator.cpp:2: /usr/local/boost_1_33_0/boost/mpl/map/aux_/contains_impl.hpp:34: no class template named `apply' in `struct boost::mpl::at_impl<boost::mpl::aux::map_tag>' /usr/local/boost_1_33_0/boost/mpl/map/aux_/contains_impl.hpp:35: `type' is not a class or namespace /usr/local/boost_1_33_0/boost/mpl/map/aux_/contains_impl.hpp:35: ISO C++ forbids declaration of `type name' with no type In file included from /usr/local/boost_1_33_0/boost/mpl/map/aux_/erase_key_impl. hpp:19, from /usr/local/boost_1_33_0/boost/mpl/map/aux_/erase_impl.hpp: 19, from /usr/local/boost_1_33_0/boost/mpl/map/map0.hpp:22, from /usr/local/boost_1_33_0/boost/mpl/map/map10.hpp:19, from /usr/local/boost_1_33_0/boost/mpl/map/map20.hpp:19, from /usr/local/boost_1_33_0/boost/mpl/map.hpp:36, from mpl_iterator.cpp:2: /usr/local/boost_1_33_0/boost/mpl/map/aux_/has_key_impl.hpp:33: no class template named `apply' in `struct boost::mpl::at_impl<boost::mpl::aux::map_tag>' /usr/local/boost_1_33_0/boost/mpl/map/aux_/has_key_impl.hpp:34: `type' is not a class or namespace /usr/local/boost_1_33_0/boost/mpl/map/aux_/has_key_impl.hpp:34: ISO C++ forbids declaration of `type name' with no type In file included from /usr/local/boost_1_33_0/boost/mpl/map/aux_/begin_end_impl. hpp:20, from /usr/local/boost_1_33_0/boost/mpl/map/map0.hpp:30, from /usr/local/boost_1_33_0/boost/mpl/map/map10.hpp:19, from /usr/local/boost_1_33_0/boost/mpl/map/map20.hpp:19, from /usr/local/boost_1_33_0/boost/mpl/map.hpp:36, from mpl_iterator.cpp:2: /usr/local/boost_1_33_0/boost/mpl/map/aux_/iterator.hpp:41: parse error before `<' token /usr/local/boost_1_33_0/boost/mpl/map/aux_/iterator.hpp:62: parse error before `<' token but if I reverse the order of the #includes, everything works OK. I suspect this problem is also showing in the GCC 3.4.x family. Thank you, Joaquín M López Muñoz Telefónica, Investigación y Desarrollo

1 0

Toolset for VC8.0 and stlport
by Thierry Miceli 13 Oct '05

13 Oct '05

Did somebody make a toolset for VC8.0 and stlport? Thanks, Thierry

2 1

[MPL.Math] partial comeback of big_integral
by Cromwell Enage 13 Oct '05

13 Oct '05

I've rewritten mpl::math::big_integral_impl so that, instead of being a heavyweight mpl::vector, the mantissa (formerly magnitude) is treated as a nullary metafunction containing the integral constant expressions digit_0...digit_N, where N is one less than the mantissa size, which is now directly configurable. Arithmetic operations are now much faster as a result. The functionality that converts integral_c et. al. to a big_integral_impl is now moved to mpl::math::enlarge_integral. All I need now is a *much* more efficient division algorithm and, of course, mpl::math::big_integral itself. BTW, there may be extraneous files in the <mpl_math.zip>boost/ directory; ignore them, I was using them for study purposes. Cromwell D. Enage __________________________________ Yahoo! Mail - PC Magazine Editors' Choice 2005 http://mail.yahoo.com

2 2

[concept_check.hpp] unreferenced formal parameter line 227
by Kevin Wheatley 13 Oct '05

13 Oct '05

Hi, I was wondering if anybody has thought about adding a #else to the #if !defined(_ITERATOR) to ignore the unused variable warning in AssignableConcept::const_constraints() you get when compiling on VC7.1 ? (Or am I missing something subtle about the situation) Thanks Kevin -- | Kevin Wheatley, Cinesite (Europe) Ltd | Nobody thinks this | | Senior Technology | My employer for certain | | And Network Systems Architect | Not even myself |

3 4

singleton_ptr
by Jason Hise 13 Oct '05

13 Oct '05

Due to the fact that to get a bachelors degree in computer science at my university I need 4 semesters of a foreign language, I currently have run out of time to keep working on singleton. I have no idea why C++ couldn't count as my foreign language... for whatever reason I just have to learn French instead :-P. I definitely plan to resume work on this library in the future, but in order to avoid keeping everyone else waiting I am uploading the current code to the sandbox. I think that although I have not yet had time to create html docs, the comments document the functionality reasonably well. The only real things missing are some sort of timeout_lifetime and multiton_ptr. As a jumping off point, here is some sample code to demonstrate example usage: #include <boost/singleton_ptr.hpp> class MyClass { public: void DoSomething ( ) { } }; typedef boost::singleton_ptr < MyClass > MySingletonPtr; void foo ( ) { MySingletonPtr ptr; ptr->DoSomething ( ); } singleton_ptr uses named template parameters to specialize functionality. The following policies are provided: factory - determines how instances are created and destroyed, also responsible for memory allocation threading - determines how member access is serialized lifetime - determines how instance is automatically destroyed storage - determines where and how the singleton policies themselves are stored name - allows multiple singletons of the same type to coexist, even if their other policies aren't different. also used to specify segment names in the case of shmem. you may specify any or all of these, in any order, as follows: using boost::singleton_ptr; using boost::singleton::name; using boost::singleton::factory; using boost::singleton::threading; using boost::singleton::lifetime; using boost::singleton::storage; typedef boost::singleton_ptr < MyType, name < /*instance name here*/ > factory < /*factory policy here*/ >, threading < /*threading policy here*/ >, lifetime < /*lifetime policy here*/ >, storage < /*storage policy here*/ > > MySingletonPtr; When you declare a singleton_ptr, you can also throw manual_creation, lazy_creation, or greedy_creation anywhere into the policy list. This is a special argument, and multiple singleton_ptr types which differ only by this specification will still point to the same instance (this cannot be said about any of the other arguments). Choosing one of these allows you to control when pointers of that type will perform automatic creation (if the instance does not yet already exist). Since there is not yet any official documentation, I encourage everyone to use me as documentation and pummel me with questions :) If you wonder if something can or can't be done with the library, want clarification on some of its features, or have ideas for code improvement please let me know. The code is in the sandbox under the "Patterns" folder. -Jason

1 0

Re: [boost] [ANN] Phoenix-2 prerelease
by Eric Niebler 13 Oct '05

13 Oct '05

Joel de Guzman wrote: > > Docs: http://tinyurl.com/77pz5 > Doc bug regarding QuickBook shorthand notation for strike-through in the Include Files table, in section "Supported Operators". http://tinyurl.com/b25hr (I've been bitten by this strike-though issue with QuickBook several times. I'm considering ripping the short-hand notation for strike-through out of QuickBook.) Also, I'm not wild for the names val(), var() and invar(). "val" and "var" look too much alike, and could lead to subtle bugs; "invar" doesn't read well, or it isn't evocative of what it does. Have you considered using val(), ref() and cref()? -- Eric Niebler Boost Consulting www.boost-consulting.com

2 1

[MPL.Math] tribool
by Cromwell Enage 12 Oct '05

12 Oct '05

Any interest in compile-time tribooleans? Functionality is currently limited by the fact that mpl::and_, mpl::or_, and mpl::not_ are not implemented in terms of any respective *_impl metafunction classes. (That means no nested expressions, no lambda expressions, and no 3+-arg expressions.) Any desire to change this? Cromwell D. Enage __________________________________ Yahoo! Music Unlimited Access over 1 million songs. Try it free. http://music.yahoo.com/unlimited/

1 0

[Review] TR1 library accepted
by Beman Dawes 12 Oct '05

12 Oct '05

John Maddock's TR1 library is accepted by Boost. Coincidentally, ISO has just announced that TR1 unanimously passed its final ballot, and so is now official. There were four reviews of John's submission, all urging acceptance. For most of the relatively few issues raised during review, John has already responded. Unless I missed it, however, John hasn't responded to Jonathan Wakely's review comments yet, anduld do so when he gets a chance. For example: It might be useful to list all the BOOST_HAS_TR1_XXX macros on the Configuration page, so you can glance at them all at once (most people will know what components each macro relates to.) Otherwise you have to read through a lot of text on the "TR1 By Subject" page to see what's available. Congratulations to John, and thanks to our reviewers! --Beman Dawes, Review Manager

1 0

Re: [boost] [ANN] Phoenix-2 prerelease
by David Abrahams 12 Oct '05

12 Oct '05

Joel de Guzman <joel(a)boost-consulting.com> writes: > Hi, > > Here's a pre-release package of Phoenix-2. Jaakko and I agreed > that it will be the basis of the Phoenix and Boost Lambda > merger. This version is Phoenix 1 + Lambda + a lot more. > > Take note though that this is not a drop-in replacement of > Phoenix-1 for Spirit users. In particular, there is no > closure support. Phoenix-2 has true local variables. The > plan for Spirit-2 is to replace closures with local variables. > > Docs: http://tinyurl.com/77pz5 > > The pre-release package is here: > http://spirit.sourceforge.net/dl_more/phoenix_v2.zip > > Just drop it where Phoenix-1 is and run the examples/tests. > Comments, feedback very welcome! arg1 // evaluates to a unary function arg2 // evaluates to a binary function arg3 // evaluates to a ternary function I am surprised. Shouldn't arg1 be a one-or-more argument function that returns its first argument, and arg3 be a three-or-more argument function that returns its third argument? Also, I think you can drop "evaluates to" and put something more descriptive in the comments. -- Dave Abrahams Boost Consulting www.boost-consulting.com

1 0

Yet another FOREACH
by A. Azuma 12 Oct '05

12 Oct '05

Hi, Boosters. First, sorry for my bad English and the long post. I have been much inspired by Eric Niebler's FOREACH. It is very nice and useful. However, I think there are some drawbacks in his implementation. First, Eric's FOREACH should explicitly specify the value type of the range. It is still bothering me in some cases. For example, std::map or a range of ranges. Second, the reference type should be declared when a value is written into the range. It seems unclear. Then, I show yet another idea to implement FOREACH. My implementation can provide the following syntax. vector<int> v; ..... FOREACH(iter, v){ cout << *iter << endl; } The code above can be considered that `iter' is declared as an iterator. In this syntax, the first problem I picked up is clearly solved. Moreover, when writing a value into the range, the code whould be int i = 0; FOREACH(iter, v){ *iter = i++; } It seems very clear. The second problem is solved, too. This syntax would be reasonable and familiar to C++ programmers. Of cource, all the stuffs in the macro and operator* are calculated in compile-time, and compilers can optimize at the same level as an equivalent handwritten for-loop. On the other hand, there is a very serious limitation in my code. A number of FOREACH in each translation unit is limited. With the implementation in the attached file, the number is limited up to 100. This number can be easily increased, but increasing it burdens a compiler. In addition, member access operator (operator->) cannot be used. I use a subtle implementation of compile-time global counter to emulate auto/decltype, and subtly hides them in FOREACH macro and iterator syntax. Please see the attached code for more detail. The attached code has been tested on GCC3.4.2, MSVC7.1 and MSVC8.0 beta 2. All the implementations are compliant to the standard, I believe so at least. By the way, my idea contains auto/decltype emulation, so such a syntax as followings can be also provided by using my idea. AUTO_ANY(less, boost::lambda::_1 < boost::lambda::_2); sort(v1, v2, auto_cast(less)); // the type of the lambda functor is restored. Of course, this does not look so nice. I would like to ask boosters how useful, portable and interesting my idea is. Thanks in advance.

3 4

[iostreams][1.33.1] Re: possible code_converter bug?
by Jonathan Turkanis 12 Oct '05

12 Oct '05

[Doug, I think I'd like to fix this problem. The noconv case is not covered by the regression test; if it were, this problem would have been noticed before] Niklas Wiberg wrote: > Hi, > Sorry for mailing you privately, but this feels a bit too detailed to > bother the list readers with... I don't mind your writing me privately, but we discuss lots of detailed things on the list, and someone else might have some good insight. With your permission, I'll post this to the list. > I'm using a "null codecvt" as described at > http://www.codeproject.com/vcpp/stl/upgradingstlappstounicode.asp?df=100&fo… > > together with code_converter. > > In code_converter<Device, Codevt, Alloc>::write(), there is a piece of > code for handling noconv results: > case codecvt_base::noconv: > { > // This can be shortened to two memcpy's. > const char* c = (const char*) (s + total); > for ( std::size_t index = 0; > index < sizeof(intern_type); > index += sizeof(extern_type), > ++buf.ptr() ) > { > memcpy(buf.ptr(), c + index, sizeof(extern_type)); > if (buf.eptr() == buf.end()) > buf.flush(dev()); > } > ++total; > } > > eptr() is never increased. Can that be correct? > If I debug and look at the call to buffer::flush() (which is called when > my stream is flushed, not by this code), I can see that > streamsize amt = static_cast<std::streamsize>(eptr_ - ptr_); > results in amt being negative since ptr_ is larger than eptr_. > Perhaps that's why I don't get anything in my file? This code probably doesn't do what I wanted it to do, but it turns out it doesn't matter, since there's a more fundamental problem. When I wrote this, I was working from the 1998 standard; in the 2003 edition, the role of noconv was clarified, as follows: result do_out(stateT& state, const internT* from, const internT* from_end, const internT*& from_next, externT* to, externT* to_limit, externT*& to_next) const; result do_in(stateT& state, const externT* from, const externT* from_end, const externT*& from_next, internT* to, internT* to_limit, internT*& to_next) const; .... If returns noconv, internT and externT are the same type and the converted sequence is identical to the input sequence [from, from_next). As a result, the NullCodecvt in the article you cite should never be returning noconv, since wchar_t != char. The next version of code_converter will handle noconv correctly, and may also be more correct in other respects. Unfortunately, it will have to wait for 1.34. > Niklas Wiberg -- Jonathan Turkanis www.kangaroologic.com

1 0

Boost regression notification (2005-10-12 [RC_1_33_0])
by Douglas Gregor 12 Oct '05

12 Oct '05

Boost regression test failures ------------------------------ Report time: 2005-10-12T14:19:18Z This report lists all regression test failures on release platforms. Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-RC_1_33_0/developer/i… 868 failures in 6 libraries: graph (1) iostreams (1) parameter (3) python (6) range (3) serialization (854) |graph| graphviz_test: cw-9_4 |iostreams| gzip_test: gcc-4_0-darwin |parameter| sfinae: vc-6_5 vc-6_5-stlport unnamed: vc-7_1 |python| pointer_vector: cw-9_4 try: gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-4.0.1-linux vector_indexing_suite: cw-9_4 |range| array: vc-6_5 vc-6_5-stlport vc-7_0 |serialization| test_binary_text_archive: vc-7_1 test_binary_text_archive_dll: vc-7_1 test_class_info_save_text_archive: vc-7_1 test_class_info_save_text_archive_dll: vc-7_1 test_delete_pointer_binary_archive: cw-9_5-darwin gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1 test_delete_pointer_binary_archive_dll: cw-9_5-darwin gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1 test_delete_pointer_text_archive: cw-9_5-darwin gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1 test_delete_pointer_text_archive_dll: gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1 test_delete_pointer_text_warchive: cw-9_5-darwin gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-4.0.1-linux intel-9.0-linux vc-7_1 test_delete_pointer_text_warchive_dll: gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1 test_delete_pointer_xml_archive: cw-9_5-darwin gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1 test_delete_pointer_xml_archive_dll: gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1 test_delete_pointer_xml_warchive: cw-9_5-darwin gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1 test_delete_pointer_xml_warchive_dll: gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1 test_demo_polymorphic: gcc-3_4_3-sunos test_demo_polymorphic_dll: gcc-3_4_3-sunos test_demo_xml_load: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin intel-win32-8_1 test_demo_xml_load_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_deque_binary_archive: cw-9_5-darwin gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1 test_deque_binary_archive_dll: cw-9_5-darwin gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1 test_deque_text_archive: cw-9_5-darwin gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1 test_deque_text_archive_dll: gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1 test_deque_text_warchive: cw-9_5-darwin gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-4.0.1-linux intel-9.0-linux vc-7_1 test_deque_text_warchive_dll: gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1 test_deque_xml_archive: cw-9_5-darwin gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1 test_deque_xml_archive_dll: gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1 test_deque_xml_warchive: cw-9_5-darwin gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1 test_deque_xml_warchive_dll: gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1 test_derived_text_archive: vc-7_1 test_derived_text_archive_dll: vc-7_1 test_diamond_binary_archive: gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_4_3-sunos gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1 test_diamond_binary_archive_dll: gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_4_3-sunos gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1 test_diamond_text_archive: gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_4_3-sunos gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1 test_diamond_text_archive_dll: gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_4_3-sunos gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1 test_diamond_text_warchive: gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_4_3-sunos gcc-4.0.1-linux intel-9.0-linux vc-7_1 test_diamond_text_warchive_dll: gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_4_3-sunos gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1 test_diamond_xml_archive: gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_4_3-sunos gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1 test_diamond_xml_archive_dll: gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_4_3-sunos gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1 test_diamond_xml_warchive: gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_4_3-sunos gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1 test_diamond_xml_warchive_dll: gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_4_3-sunos gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1 test_exported_binary_archive: gcc-3.2.3-linux gcc-4.0.1-linux intel-9.0-linux vc-6_5 test_exported_binary_archive_dll: gcc-4.0.1-linux vc-6_5 test_exported_text_archive: gcc-3.2.3-linux gcc-4.0.1-linux vc-6_5 vc-7_1 test_exported_text_archive_dll: gcc-3.2.3-linux gcc-4.0.1-linux vc-6_5 vc-7_1 test_exported_text_warchive: gcc-4.0.1-linux vc-6_5 test_exported_text_warchive_dll: gcc-4.0.1-linux vc-6_5 test_exported_xml_archive: gcc-4.0.1-linux intel-8.1-linux vc-6_5 test_exported_xml_archive_dll: gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-6_5 test_exported_xml_warchive: gcc-3.2.3-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-6_5 test_exported_xml_warchive_dll: gcc-3.2.3-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-6_5 test_list_binary_archive: cw-9_5-darwin gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1 test_list_binary_archive_dll: cw-9_5-darwin gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1 test_list_ptrs_binary_archive: cw-9_5-darwin gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1 test_list_ptrs_binary_archive_dll: cw-9_5-darwin gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1 test_list_ptrs_text_archive: cw-9_5-darwin gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1 test_list_ptrs_text_archive_dll: gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1 test_list_ptrs_text_warchive: cw-9_5-darwin gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-4.0.1-linux intel-9.0-linux vc-7_1 test_list_ptrs_text_warchive_dll: gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1 test_list_ptrs_xml_archive: cw-9_5-darwin gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1 test_list_ptrs_xml_archive_dll: gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1 test_list_ptrs_xml_warchive: cw-9_5-darwin gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1 test_list_ptrs_xml_warchive_dll: gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1 test_list_text_archive: cw-9_5-darwin gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1 test_list_text_archive_dll: gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1 test_list_text_warchive: cw-9_5-darwin gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-4.0.1-linux intel-9.0-linux vc-7_1 test_list_text_warchive_dll: gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1 test_list_xml_archive: cw-9_5-darwin gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1 test_list_xml_archive_dll: gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1 test_list_xml_warchive: cw-9_5-darwin gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1 test_list_xml_warchive_dll: gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1 test_map_binary_archive: cw-9_5-darwin gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_4_3-sunos gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1 test_map_binary_archive_dll: cw-9_5-darwin gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_4_3-sunos gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1 test_map_text_archive: cw-9_5-darwin gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_4_3-sunos gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1 test_map_text_archive_dll: gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_4_3-sunos gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1 test_map_text_warchive: cw-9_5-darwin gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_4_3-sunos gcc-4.0.1-linux intel-9.0-linux vc-7_1 test_map_text_warchive_dll: gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_4_3-sunos gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1 test_map_xml_archive: cw-9_5-darwin gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_4_3-sunos gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1 test_map_xml_archive_dll: gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_4_3-sunos gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1 test_map_xml_warchive: cw-9_5-darwin gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_4_3-sunos gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1 test_map_xml_warchive_dll: gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_4_3-sunos gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1 test_mi_text_archive: vc-7_1 test_mi_text_archive_dll: vc-7_1 test_no_rtti_binary_archive: vc-6_5 test_no_rtti_binary_archive_dll: vc-6_5 test_no_rtti_text_archive: vc-6_5 test_no_rtti_text_archive_dll: vc-6_5 test_no_rtti_text_warchive: vc-6_5 test_no_rtti_text_warchive_dll: vc-6_5 test_no_rtti_xml_archive: vc-6_5 test_no_rtti_xml_archive_dll: vc-6_5 test_no_rtti_xml_warchive: vc-6_5 test_no_rtti_xml_warchive_dll: vc-6_5 test_non_default_ctor2_text_archive: vc-7_1 test_non_default_ctor2_text_archive_dll: vc-7_1 test_non_default_ctor_text_archive: vc-7_1 test_non_default_ctor_text_archive_dll: vc-7_1 test_non_intrusive_text_archive: vc-7_1 test_non_intrusive_text_archive_dll: vc-7_1 test_null_ptr_text_archive: vc-7_1 test_null_ptr_text_archive_dll: vc-7_1 test_object_text_archive: vc-7_1 test_object_text_archive_dll: vc-7_1 test_polymorphic_binary_archive: gcc-3_4_3-sunos test_polymorphic_binary_archive_dll: gcc-3_4_3-sunos test_polymorphic_text_archive: gcc-3_4_3-sunos test_polymorphic_text_archive_dll: gcc-3_4_3-sunos test_polymorphic_text_warchive: gcc-3_4_3-sunos test_polymorphic_text_warchive_dll: gcc-3_4_3-sunos test_polymorphic_xml_archive: gcc-3_4_3-sunos test_polymorphic_xml_archive_dll: gcc-3_4_3-sunos test_polymorphic_xml_warchive: gcc-3_4_3-sunos test_polymorphic_xml_warchive_dll: gcc-3_4_3-sunos test_primitive_text_archive: vc-7_1 test_primitive_text_archive_dll: vc-7_1 test_registered_text_archive: vc-7_1 test_registered_text_archive_dll: vc-7_1 test_set_binary_archive: cw-9_5-darwin gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_4_3-sunos gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1 test_set_binary_archive_dll: cw-9_5-darwin gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_4_3-sunos gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1 test_set_text_archive: cw-9_5-darwin gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_4_3-sunos gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1 test_set_text_archive_dll: gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_4_3-sunos gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1 test_set_text_warchive: cw-9_5-darwin gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_4_3-sunos gcc-4.0.1-linux intel-9.0-linux vc-7_1 test_set_text_warchive_dll: gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_4_3-sunos gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1 test_set_xml_archive: cw-9_5-darwin gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_4_3-sunos gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1 test_set_xml_archive_dll: gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_4_3-sunos gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1 test_set_xml_warchive: cw-9_5-darwin gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_4_3-sunos gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1 test_set_xml_warchive_dll: gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_4_3-sunos gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1 test_shared_ptr_132_binary_archive: vc-6_5 vc-6_5-stlport test_shared_ptr_132_binary_archive_dll: vc-6_5 test_shared_ptr_132_text_archive: vc-6_5 vc-6_5-stlport test_shared_ptr_132_text_archive_dll: vc-6_5 test_shared_ptr_132_text_warchive: vc-6_5 vc-6_5-stlport test_shared_ptr_132_text_warchive_dll: intel-win32-8_1 vc-6_5 test_shared_ptr_132_xml_archive: vc-6_5 vc-6_5-stlport test_shared_ptr_132_xml_archive_dll: vc-6_5 test_shared_ptr_132_xml_warchive: vc-6_5 vc-6_5-stlport test_shared_ptr_132_xml_warchive_dll: vc-6_5 test_shared_ptr_binary_archive: borland-5_6_4 vc-6_5 test_shared_ptr_binary_archive_dll: borland-5_6_4 vc-6_5 test_shared_ptr_text_archive: borland-5_6_4 vc-6_5 test_shared_ptr_text_archive_dll: borland-5_6_4 vc-6_5 test_shared_ptr_text_warchive: borland-5_6_4 vc-6_5 test_shared_ptr_text_warchive_dll: borland-5_6_4 vc-6_5 test_shared_ptr_xml_archive: borland-5_6_4 vc-6_5 test_shared_ptr_xml_archive_dll: borland-5_6_4 vc-6_5 test_shared_ptr_xml_warchive: borland-5_6_4 vc-6_5 test_shared_ptr_xml_warchive_dll: borland-5_6_4 vc-6_5 test_split_text_archive: vc-7_1 test_split_text_archive_dll: vc-7_1 test_tracking_text_archive: vc-7_1 test_tracking_text_archive_dll: vc-7_1 test_unregistered_binary_archive: gcc-3.2.3-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux test_unregistered_binary_archive_dll: gcc-3.2.3-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux test_unregistered_text_archive: gcc-3.2.3-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1 test_unregistered_text_archive_dll: gcc-3.2.3-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1 test_unregistered_xml_archive: gcc-3.2.3-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux test_unregistered_xml_archive_dll: gcc-3.2.3-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux test_unregistered_xml_warchive: gcc-4.0.1-linux test_unregistered_xml_warchive_dll: gcc-4.0.1-linux test_variant_binary_archive: cw-9_5-darwin gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1 test_variant_binary_archive_dll: cw-9_5-darwin gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1 test_variant_text_archive: cw-9_5-darwin gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1 test_variant_text_archive_dll: gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1 test_variant_text_warchive: cw-9_5-darwin gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1 test_variant_text_warchive_dll: gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1 test_variant_xml_archive: cw-9_5-darwin gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1 test_variant_xml_archive_dll: gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1 test_variant_xml_warchive: cw-9_5-darwin gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1 test_variant_xml_warchive_dll: gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1 test_vector_binary_archive: cw-9_5-darwin gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1 test_vector_binary_archive_dll: cw-9_5-darwin gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1 test_vector_text_archive: cw-9_5-darwin gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1 test_vector_text_archive_dll: gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1 test_vector_text_warchive: cw-9_5-darwin gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-4.0.1-linux intel-9.0-linux vc-7_1 test_vector_text_warchive_dll: gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1 test_vector_xml_archive: cw-9_5-darwin gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1 test_vector_xml_archive_dll: gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1 test_vector_xml_warchive: cw-9_5-darwin gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1 test_vector_xml_warchive_dll: gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1

1 0

Boost regression notification (2005-10-12 [HEAD])
by Douglas Gregor 12 Oct '05

12 Oct '05

Boost regression test failures ------------------------------ Report time: 2005-10-12T05:00:23Z This report lists all regression test failures on release platforms. Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-HEAD/developer/issues… 101 failures in 11 libraries: concept_check (13) graph (2) mpl (1) parameter (13) python (1) serialization (36) spirit (8) thread (4) tuple (1) type_traits (1) typeof (21) |concept_check| stl_concept_covering: cw-9_4 gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin intel-win32-9_0 intel-win32-9_0 mingw-3_4_2 msvc vc-7_1 |graph| graphviz_test: vc-7_1 layout_test: intel-win32-9_0 |mpl| size_t: gcc-4_0-darwin |parameter| basics: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux efficiency: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux msvc macros: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux sfinae: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux msvc unnamed: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux vc-7_1 |python| exec: intel-win32-9_0 |serialization| test_class_info_load_binary_archive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_binary_archive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_archive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_archive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_warchive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_warchive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_archive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_archive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_warchive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_warchive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_const_save_fail1: msvc test_const_save_fail2: msvc test_const_save_fail3: msvc test_map_binary_archive_dll: msvc test_map_text_archive_dll: msvc test_map_text_warchive_dll: msvc |spirit| action_tests_debug: gcc-3_4_3-sunos distinct_tests_debug: gcc-3_4_3-sunos escape_char_parser_tests_debug: gcc-3_4_3-sunos grammar_def_test_debug: gcc-3_4_3-sunos switch_problem_debug: gcc-3_4_3-sunos switch_tests_single_debug: gcc-3_4_3-sunos traverse_tests: intel-win32-9_0 traverse_tests_debug: intel-win32-9_0 |thread| test_condition: gcc-3_4_3-sunos test_mutex: gcc-3_4_3-sunos test_tss: gcc-3_4_3-sunos gcc-3_4_3-sunos |tuple| tuple_test_bench: gcc-3_4_3-sunos |type_traits| tricky_abstract_type_test: intel-win32-9_0 |typeof| data_member_native: cw-9_4 function_native: cw-9_4 msvc function_ptr_native: cw-9_4 function_ref_native: cw-9_4 lvalue_native: cw-9_4 msvc member_function_native: cw-9_4 modifiers_emulation: cw-9_4 modifiers_native: cw-9_4 noncopyable_native: cw-9_4 std_emulation: cw-9_4 std_native: cw-9_4 template_dependent_native: cw-9_4 template_enum_native: cw-9_4 template_int_native: cw-9_4 template_multiword_native: cw-9_4 template_tpl_native: cw-9_4 msvc template_type_native: cw-9_4 type_native: cw-9_4

1 0

Boost::Ruby
by Alan Gutierrez 12 Oct '05

12 Oct '05

Is there any interest? -- Alan Gutierrez - alan(a)engrm.com - http://engrm.com/blogometer/

14 36

[tools][bcp] using boost internally in other libraries
by Bjørn Roald 12 Oct '05

12 Oct '05

Hi boosters, In the following I have made the assumption that it is in the spirit of the Boost license for Boost to be used as foundation for other libraries, open-source, free, commercial, or whatever. In addition, that any modifications to the libraries is allowed for any such purpose. However, it is my belief that most of the developers would not like to see extensive branching in the effort of providing better Boost libraries. This would most likely stretch the potential of the C++ community in providing a better future set of standard libraries for the language. So to my main subject: I have been working for some time to get acceptance for using Boost libraries as elements in a higher level portable platform for library development. It has surprised me how hard it is to make compelling and attractive set of arguments for using Boost (or other libraries) without attempting to ignore some pretty serious concerns. These concerns are: - commercial support for our use of Boost - quality assurance of Boost itself - stability of Boost API - maintainability of Boost source code - deployability of our library into environments using different versions of Boost or libraries used in boost - configuration management issues in general for us and our customers - platform support in Boost ( or if the platform support Boost if you like ;-) All of these concerns can be declared acceptable, given that you are willing to accept trade offs and risk. The issue I try to raze is if it is possible to reduce the magnitude of these risks and trade offs. One of the key issues is that you have to decide on some strategy of how to maintain your boost version. The most obvious strategy may be to stay with the latest Boost release at any time, this will however add risk as you have to adopt new changes as they are introduced into Boost and not as it fits your own release plans. The obvious alternative is to stay with a Boost release longer, possibly until you are forced to switch. This strategy will quickly force you into maintaining your own branch as Boost developers can not be expected to support old releases. Between these there are many shades of gray which may fit more or less well depending on your project and your customers. If your customers themselves use boost you are likely to meet a added configuration management, testing and release related cost and risk. As library developers have a very different type of customer relationship than what is the case for end application developers there are a number of concerns that make adaptation of Boost, or any other 3rd party library for that sake, more problematic for library developers. The main issue is to what degree a library depends on other libraries and hence introduces indirect or direct dependencies to its users. These dependencies tend to be troublesome for the library developer to support, as well as they may be troublesome for users to accept. In fact users may easily be in situations where such dependencies are completely unacceptable. To help to understand the issue I like to define categories of libraries which affect the degree they are affected by these concerns. Cat1. open source, source distributions, allowing encapsulation Cat2. open source, source distributions in general Cat3. open source, binary distributions Cat4. closed source Cat1 and Cat2 are build-able source code distributions. This give the user the ability to build the library and ensure that it is built correctly with other library it depends on, on the target system. Cat1 add to this the ability to hide the use of it inside other libraries, i.e. it can live concurrently in an end system with other versions of the same Cat1 library. Cat3 and Cat4 are for this discussion as far as I can tell similar. Cat3 may be called open source by some, but if for a variation of reasons rebuild by user is not an option, the results in this discussion becomes the same. Boost is a Cat2 library. Even if the extensive use of headers only libraries help some of the issues addressed in this post, it is not a general solution that makes Boost or part of Boost a Cat1 library. Now an example showing some dependencies: MyCustomersApplication |---- Boost 1.33 |---- MyLib |---- Boost 1.32 If MyLib is Cat1 or Cat2 the chances are good that we may be ok. Most likely MyLib will soon adopt the migration to new Boost releases by the actions of the maintainer or by patches from end users. If however MyLib is Cat 3 or 4 we have a problem. This problem is real even if the use of Boost in MyLib is strictly internal. In my view this is an especially bad problem. Even if I do not intend to use Boost in any way in the API of MyLib I still have this issue of incompatibility. This problem will disqualify use of Boost even internally for many library developers. Now, if we assume (which in most cases is dangerous) that library developers are a skilled race among the general population of the C++ community, it is in my view sad that many of them are not able to use Boost or potentially participate professionally in the efforts to improve Boost. I am sure many actually would participate if they could use it at work. Any management with commercial goals mixed with good sense of business would also let their developers participate actively, especially if this was the best way of maintaining parts of their product. This would let their developers focus their effort on the parts of the product that is core to their business rather than the parts that can be found and downloaded on the net (read boost.org) Ok, back to the example. If MyLib have no intention of using Boost in the API, is there a way? I have been struggling with this issue for a while. The obvious solution to me is to make Boost a Cat1, the problem is how? As mentioned earlier in many threads on this list header-only libraries helps, however this does not apply to all of Boost and it is possibly other issues that I am not aware of. If we look at the C++ domain in general, there are limited ways of hiding symbols in libraries. As far as I can see, none of these are sufficiently powerful to hide boost completely. One alternative is however to let the symbols leak, but make sure none are in conflict with the other version of boost. Some sort of namespace replacement or wrapping comes to my mind. Side Note: I am aware of symbol encapsulation abilities in windows DLLs and similar new features supported by GCC, however these are not generally supported on all platforms, so I have selected to ignore them. They may however be helpful to many. The general idea is that there are no references to symbols in the boost namespace between any MyLib libraries, nor in any header files in or referenced from MyLib API. How can this be achieved? I have concluded that accessing boost trough namespace wrapping header files are unpractical at best. This needs to be designed into all of boost for this to work, and I do not know exactly how. The main challenge is #include <boost/xxxx.hpp> directives which does not refer to the wrapping headers. An alternative is to replace all references to boost namespace with e.g. MyLib::boost namespace in the boost source code and change all #include <boost/xxx.hpp> directives to #include <Mylib/boost/xxx.hpp>. This would make a buildable library which would not share symbols with other versions of boost. The result is a branch or clone if you like of Boost that can be used with the same effect as if we actually had a Cat1 boost library. There is however serious problems here. Any management with common sense would say.... hey.... stop. The prospect of undertaking maintenance of a branch or clone of Boost does not make much sense --- So, the only way this would work is to make it possible to maintain the library in the boost community and somehow make the translation to the MyLib/boost namespace a pure production step. In configuration management terms this means that the original or possibly slightly patched boost source code is under configuration control along with a tool-chain used under MyLib system build that transforms the boost source tree to the form used internally. This is where I started looking at Boost tools/bcp. The bcp (boost copy I guess) tool is an excellent starting point since it already has the ability to copy selected libraries and their dependencies from the boost distribution to project specific source tree. So in a sense it is similar in spirit, but solves primarily a different goal, which is to reduce the size of the boost distribution imported. This is complementary to what I want. I have experimented a little with some extensions to bcp using some simple regexp replace calls and got some encouraging results. I am able to build the resulting source tree using only small adjustments to top level bjam files after treatment by the modified bcp. I have yet to complete support for replacing boost with nested namespaces since it is trickier to do the replacement of the ending braces of the namespace scope. I believe other tools than the Regexp library may be more appropriate for this task. So to wrap up: I do not believe anything prevents me from going along this path if I decide to do so. I am however interested in the boost developers attitude toward this approach, and in particular if this is something you will encourage and/or support. I am willing to work on the tool support for this in boost or to maintain a modified bcp tool if that is more appropriate. Regards Bjørn Roald

9 24

Problem building boost regex on hpux - getlocale(int) problem
by Navdeep Shergill 12 Oct '05

12 Oct '05

Hi all I am trying to build boost v 1.30.0 regex library on a hp machine. The 'syname' output is this: PA-RISC2.0_hpux_11.00_v5.1c I go to the "boost-1.30.0/libs/regex/build" directory and issue a 'make -f gcc.mak' command. I get the following errors: ../src/c_regex_traits.cpp:660: call of overloaded `getlocale(int)' is ambiguous /usr/gcc/3.1/lib/gcc-lib/hppa2.0w-hp-hpux11.00/3.1/include/locale.h:144: candidates are: locale_data* getlocale(int) ../src/c_regex_traits.cpp:62: const char* <unnamed>::getlocale(int) ../src/c_regex_traits.cpp:663: call of overloaded `getlocale(int)' is ambiguous /usr/gcc/3.1/lib/gcc-lib/hppa2.0w-hp-hpux11.00/3.1/include/locale.h:144: candidates are: locale_data* getlocale(int) ../src/c_regex_traits.cpp:62: const char* Here is the gcc version. Its v3.1 =========================================================== [4:00pm: regex/build]gcc -v Reading specs from /usr/intel/pkgs/gcc/3.1/lib/gcc-lib/hppa2.0w-hp-hpux11.00/3.1/specs Configured with: ../gcc-3.1/configure --host=hppa2.0w-hp-hpux11.00 --target=hppa2.0w-hp-hpux11.00 --prefix=/usr/gcc/3.1 --enable-languages=c,c++ --enable-threads --with-gnu-as --with-as=/usrgcc/3.1/bin/gas Thread model: single gcc version 3.1 [4:03pm: regex/build] ============================================================= Anyone have any idea how I can fix this problem of the ambiguious getlocale function? Thanks!

2 2

Short Mailing List Outage on Thursday 10/13
by Jeff Garland 12 Oct '05

12 Oct '05

FYI --------------------------- I am sorry for this short notice but I need to reboot milliways to upgrade its firmware. It will be down for about 1 hour Thursday morning (10/13). - 6:00am-7:00am Pacific US time - 7:00am-8:00am Mountain US time - 8:00am-9:00am Central US time - 9:00am-10:00am Eastern US time - 1:00pm-2:00pm GMT Specifically, the following services provided by the OSL will be unavailable during this timeframe: - All e-mail services - Incoming mail (including all mailman list hosting) - Outgoing mail (including all mailman list hosting) - IMAP/SSL - All web hosting - lists.boost.org - ...and all others hosted by the OSL

1 0

Is there PGI & PathScale compiler support?
by Ryo IGARASHI 12 Oct '05

12 Oct '05

Hi developpers, Are no boost user using PGI or PathScale compiler on AMD x86_64 machines? There seems to be no toolset support for both compilers yet. Are they bad compilers when using boost libraries? -- Ryo IGARASHI rigarash(a)gmail.com

1 0

Re: [boost] Please look at my suggested pimpl library in the file vault.
by Asger Mangaard 12 Oct '05

12 Oct '05

I've uploaded an updated version ... >> Pavel Vozenilek wrote ... > I do have a few. > /Pavel > > ________________________________________________ > 1. You should not use double underscores > (and neither leading single underscore). > These are reserved for standard. > It's corrected. > ________________________________________________ > 2. It is better when member functions are all > lowercase (like elsewhere in Boost). > > It's corrected. > ________________________________________________ > 3. pimpl.hpp: > > The base::_Get() should have > BOOST_ASSERT() before dereferencing. > > Possibly this function could be omitted > altogether since it is always overriden. > It's corrected. > ----------- > > _Destructor should be named destroy() > to evoke action. > > Better yet, move it into real destructor. > It's corrected. > ----------- > > late_creation policy may nam named "manual_creation" > or so. > > The Set() should destroy previous instance > if non-NULL. > > The _Get() should contain > BOOST_ASSERT() or throw if NULL. > It's corrected. > --------------- > > Closing bracket for namespace should nopt have ";" > but should have comment like // namespace pimpl_policies > It's corrected. > ---------------- > > operator=() does shallow copy of dynamically > allocated value. Is this really what ypu want? > It's corrected. > ________________________________________________ > 4. Compiling with Intel C++ 7.0 for Windows > I get error: > > testsuite.cpp > C:\work\reviews\pimpl\testsuite.cpp(54): error: no suitable user-defined > conversion from "boost::pimpl<CMyValues1, > > boost::pimpl_policies::base>" to "const boost::pimpl<CMyValues2, > boost::pimpl_policies::late_creation>" exists > test.m_ValuesWithLazyCreator2 = test.m_ValuesWithDefaultConstructor; > I've now tested with Intel C++ 9.0 windows and it works fine. How can I get a copy of this old version? > ________________________________________________ > 5. The pimpl doesn't show how I work with > member functions. This is the most important part > of the idiom and If there's way to make the tedious > work any simpler I am all for it. > You just work with the pimpl's -> operator. That will give you access to the pimpl's member functions. The new 'testsuite.cpp' shows its use. And thanks for your corrections, I highly appreciate them. Regards, Asger Mangaard

10 22

[regex, C++ Committee Meeting] any progress on lwg issue #523?
by Eric Niebler 12 Oct '05

12 Oct '05

Was library issue 523: "regex case-insensitive character ranges are unimplementable as specified" discussed at the committee meeting? http://www.open-std.org/jtc1/sc22/wg21/docs/lwg-active.html#523 -- Eric Niebler Boost Consulting www.boost-consulting.com

2 1

[serialization] Inherited objects
by Jared McIntyre 12 Oct '05

12 Oct '05

I've gone through the documentation, and I'm still unable to get this particular aspect of serialization working. I have two objects 'a' and 'b', and 'b' inherits from 'a'. I have a vector of 'a' pointers that may just be 'a' or may be 'b'. I've preregistered 'b', right before the vector serialization occurs, so that the serialization system should properly recognize that 'b' inherits from 'a'. However, only the 'a' pieces of each 'b' in the vector serializes. If I place all the 'b' items in a second 'b' containing vector, and serialize that afterwards, it properly discovers that the 'a' part has been serialized already and simply points to that reference. I don't really want to store this second 'b' vector. Is there a way to get a vector of a items to also serialize the 'b' part of the element if the item is a 'b'? I apologize if this is already in the documentation, but if it is, I missed it. Also, there is an issue in the documentation. In the "Pointers to Objects of Derived Classes" section, it has example registration code: main(){ ... ar.template register_type<derived_one>(); ar.template register_type<derived_two>(); base *b; ar & b; } I'm guessing that is supposed to be: main(){ ... ar.register_type<derived_one>(); ar.register_type<derived_two>(); base *b; ar & b; } Thanks, Jared

7 15

[optional] Breaking changes in 1.33.0 vs 1.32.0
by Anthony Williams 11 Oct '05

11 Oct '05

I have some code that has been merrily using the 1.32.0 release of boost, including boost::optional, and I've just tried to change to use the 1.33.0 release (this is the first change to this codebase since 1.33.0 was released). In my code, I have boost::optional<X> where X is copy-constructible, but not assignable. This works in 1.32.0, but fails in 1.33.0. Ouch! What is the reason for the change? Why is this not listed in the "Updated libraries" section of the docs? Why is this not listed under the "Type Requirements" section of the docs? Anthony -- Anthony Williams Software Developer Just Software Solutions Ltd http://www.justsoftwaresolutions.co.uk

2 2

Suggest who's developer information on more/getting_started.html
by Larry Evans 11 Oct '05

11 Oct '05

PROBLEM: I had been a sandbox cvs developer, but I was unsure if that also made me main cvs developer. This resulted in several emails between me and mailto:boost-owner@lists.boost.org before things were cleared up. SUGGESTED SOLUTION: apply the attached patch to: http://www.boost.org/more/getting_started.html This makes clear who has write access to the main cvs. FEEDBACK: Please let me know within the next 10 days if there are any objections to this patch. If there are no objections, I will apply the patch on day 11. TIA. Index: getting_started.html =================================================================== RCS file: /cvsroot/boost/boost/more/getting_started.html,v retrieving revision 1.29 diff -r1.29 getting_started.html 2,4c2,3 < <html> < <head> < <title>Getting Started</title> --- > <html><head><title>Getting Started</title> > 9,16c8,16 < <LINK href="../boost.css" type="text/css" rel="stylesheet"></head> < <body text="#000000" bgColor="#ffffff"> < <table cellSpacing="0" cellPadding="0" width="100%" summary="" border="0"> < <tr vAlign="top"> < <td vAlign="top" align="left"><IMG height="86" alt="boost.png (6897 bytes)" src="../boost.png" width="277"></td> < <td vAlign="top" align="right"> < <table cellSpacing="0" cellPadding="2" summary="" border="1"> < <tr> --- > <link href="getting_started_files/boost.css" type="text/css" rel="stylesheet"></head> > > <body bgcolor="#ffffff" text="#000000"> > <table summary="" border="0" cellpadding="0" cellspacing="0" width="100%"> > <tbody><tr valign="top"> > <td align="left" valign="top"><img alt="boost.png (6897 bytes)" src="getting_started_files/boost.png" height="86" width="277"></td> > <td align="right" valign="top"> > <table summary="" border="1" cellpadding="2" cellspacing="0"> > <tbody><tr> 18,25c18,25 < <table cellSpacing="0" cellPadding="2" summary="" border="0"> < <tr> < <td bgColor="#dddddd"> < <p>. <A href="../index.htm">Home</A><br> < . <A href="../libs/libraries.htm">Libraries</A><br> < . <A href="../people/people.htm">People</A><br> < . <A href="faq.htm">FAQ</A><br> < . <A href="index.htm">More</A></p> --- > <table summary="" border="0" cellpadding="2" cellspacing="0"> > <tbody><tr> > <td bgcolor="#dddddd"> > <p>. <a href="http://www.boost.org/index.htm">Home</a><br> > . <a href="http://www.boost.org/libs/libraries.htm">Libraries</a><br> > . <a href="http://www.boost.org/people/people.htm">People</a><br> > . <a href="http://www.boost.org/more/faq.htm">FAQ</a><br> > . <a href="http://www.boost.org/more/index.htm">More</a></p> 28c28 < </table> --- > </tbody></table> 31c31 < </table> --- > </tbody></table> 34c34 < </table> --- > </tbody></table> 38,40c38,40 < <A href="#Introduction">Introduction</A> < <li> < <A href="#Download">Download</A> --- > <a href="#Introduction">Introduction</a> > </li><li> > <a href="#Download">Download</a> 43,47c43,47 < <A href="#.zip">.zip file</A> < <li> < <A href="#.tar.gz">.tar.gz and .tar.bz2 files</A> < <li> < <A href="#CVS">Boost CVS Repository</A> --- > <a href="#.zip">.zip file</a> > </li><li> > <a href="#.tar.gz">.tar.gz and .tar.bz2 files</a> > </li><li> > <a href="#CVS">Boost CVS Repository</a> 50,51c50,51 < <li> < <A href="#Preparation">Preparation</A> --- > </li><li> > <a href="#Preparation">Preparation</a> 54,56c54,56 < <A href="#Configuring">Configuring the tools</A> < <li> < <A href="#Tools">Supported Toolsets</A> --- > <a href="#Configuring">Configuring the tools</a> > </li><li> > <a href="#Tools">Supported Toolsets</a> 59,66c59,66 < <li> < <A href="#Build_Install">Build and Install</A> < <li> < <A href="#Results">Results</A> < <LI> < <A href="#auto-link">Automatic Linking on Windows</A> < <li> < <A href="#Additional_Steps">Additional Steps</A> --- > </li><li> > <a href="#Build_Install">Build and Install</a> > </li><li> > <a href="#Results">Results</a> > </li><li> > <a href="#auto-link">Automatic Linking on Windows</a> > </li><li> > <a href="#Additional_Steps">Additional Steps</a> 75,83c75,83 < <A href="#step1">Download Boost</A>. < <li> < <A href="#step2">Install Boost.Jam</A>. < <li> < <A href="#step3">Configure your compiler toolset</A>. < <li> < <A href="#step4">Go to Boost distribution directory</A>. < <li> < <A href="#step5">Build and install</A>. --- > <a href="#step1">Download Boost</a>. > </li><li> > <a href="#step2">Install Boost.Jam</a>. > </li><li> > <a href="#step3">Configure your compiler toolset</a>. > </li><li> > <a href="#step4">Go to Boost distribution directory</a>. > </li><li> > <a href="#step5">Build and install</a>. 87,89c87,89 < <table cellSpacing="2" cellPadding="2" width="100%" summary="" border="0"> < <tr vAlign="top" align="left"> < <td vAlign="top" align="center" width="40" bgColor="#ffff66"><font size="6"><b><a id="step1" name="step1"></a>1</b></font></td> --- > <table summary="" border="0" cellpadding="2" cellspacing="2" width="100%"> > <tbody><tr align="left" valign="top"> > <td align="center" bgcolor="#ffff66" valign="top" width="40"><font size="6"><b><a id="step1" name="step1"></a>1</b></font></td> 91c91 < system. Click here to <b><a href="http://sourceforge.net/project/showfiles.php?group_id=7586&package_id=8041"> --- > system. Click here to <b><a href="http://sourceforge.net/project/showfiles.php?group_id=7586&package_id=8…"> 95c95 < </table> --- > </tbody></table> 97,98c97,98 < site. It is available in <A href="#.zip">ZIP</A>, <A href="#.tar.gz">TAR.GZ</A>, < and <A href="#.tar.gz">TAR.BZ2</A> formats. Past releases are also available.</p> --- > site. It is available in <a href="#.zip">ZIP</a>, <a href="#.tar.gz">TAR.GZ</a>, > and <a href="#.tar.gz">TAR.BZ2</a> formats. Past releases are also available.</p> 100c100 < Boost's <A href="#CVS">CVS repository</A>. --- > Boost's <a href="#CVS">CVS repository</a>. 141c141,146 < write access, please contact one of the <A href="moderators.html">moderators</A>.</p> --- > write access, please contact one of the <a > href="http://www.boost.org/more/moderators.html">moderators</a>. > For confirmation of write access, check the sourceforge > boost project member list, available via a link on <a > href="http://sourceforge.net/projects/boost/">this page</a>. > </p> 149,150c154,155 < <p>Some of the Boost documentation is generated from <A href="../doc/html/boostbook.html"> < BoostBook XML</A> source stored in the CVS repository, and will not appear --- > <p>Some of the Boost documentation is generated from <a href="http://www.boost.org/doc/html/boostbook.html"> > BoostBook XML</a> source stored in the CVS repository, and will not appear 159,160c164,165 < <p>The recommended way to build and install the Boost Libraries is to use <A href="../tools/build/v1/build_system.htm"> < Boost.Build</A>, the Boost Build system. The rest of these instructions --- > <p>The recommended way to build and install the Boost Libraries is to use <a href="http://www.boost.org/tools/build/v1/build_system.htm"> > Boost.Build</a>, the Boost Build system. The rest of these instructions 164,167c169,172 < <table cellSpacing="2" cellPadding="2" width="100%" summary="" border="0"> < <tr vAlign="top" align="left"> < <td vAlign="top" align="center" width="40" bgColor="#ffff66"><font size="6"><b><a id="step2" name="step2"></a>2</b></font></td> < <td>The build system uses <A href="../tools/build/jam_src/index.html">Boost.Jam</A>, --- > <table summary="" border="0" cellpadding="2" cellspacing="2" width="100%"> > <tbody><tr align="left" valign="top"> > <td align="center" bgcolor="#ffff66" valign="top" width="40"><font size="6"><b><a id="step2" name="step2"></a>2</b></font></td> > <td>The build system uses <a href="http://www.boost.org/tools/build/jam_src/index.html">Boost.Jam</a>, 173,174c178,179 < sources in an unreleased state, it may be necessary to <A href="../tools/build/jam_src/index.html#building_bjam"> < build <tt>bjam</tt> from sources</A> included in the Boost source tree. To --- > sources in an unreleased state, it may be necessary to <a href="http://www.boost.org/tools/build/jam_src/index.html#building_bjam"> > build <tt>bjam</tt> from sources</a> included in the Boost source tree. To 178c183 < </table> --- > </tbody></table> 191c196 < <li> --- > </li><li> 209,213c214,218 < <table cellSpacing="2" cellPadding="2" width="100%" summary="" border="0"> < <tr vAlign="top" align="left"> < <td vAlign="top" align="center" width="40" bgColor="#ffff66"><font size="6"><b><a id="step3" name="step3"></a>3</b></font></td> < <td>The following toolsets are supported by Boost.Build. For information about <A href="#Configuring"> < configuring</A> each toolset, click its name in the leftmost column.</td> --- > <table summary="" border="0" cellpadding="2" cellspacing="2" width="100%"> > <tbody><tr align="left" valign="top"> > <td align="center" bgcolor="#ffff66" valign="top" width="40"><font size="6"><b><a id="step3" name="step3"></a>3</b></font></td> > <td>The following toolsets are supported by Boost.Build. For information about <a href="#Configuring"> > configuring</a> each toolset, click its name in the leftmost column.</td> 215c220 < </table> --- > </tbody></table> 217,218c222,223 < <table cellPadding="5" summary="" border="1"> < <tr> --- > <table summary="" border="1" cellpadding="5"> > <tbody><tr> 223c228 < <td><A href="../tools/build/v1/borland-tools.html"><code>borland</code></A></td> --- > <td><a href="http://www.boost.org/tools/build/v1/borland-tools.html"><code>borland</code></a></td> 227,228c232,233 < <td><A href="../tools/build/v1/como-tools.html"><code>como</code></A></td> < <td><a href="http://www.comeaucomputing.com">Comeau C++</a> compiler front-end for --- > <td><a href="http://www.boost.org/tools/build/v1/como-tools.html"><code>como</code></a></td> > <td><a href="http://www.comeaucomputing.com/">Comeau C++</a> compiler front-end for 232,233c237,238 < <td><code><A href="../tools/build/v1/como-tools.html">como-win32</A></code></td> < <td><a href="http://www.comeaucomputing.com">Comeau C++</a> compiler front-end for --- > <td><code><a href="http://www.boost.org/tools/build/v1/como-tools.html">como-win32</a></code></td> > <td><a href="http://www.comeaucomputing.com/">Comeau C++</a> compiler front-end for 238,239c243,244 < <td><A href="../tools/build/v1/cw-tools.html"><code>cw</code></A></td> < <td><a href="http://www.metrowerks.com">Metrowerks CodeWarrior</a> Pro 6.x, 7.x, --- > <td><a href="http://www.boost.org/tools/build/v1/cw-tools.html"><code>cw</code></a></td> > <td><a href="http://www.metrowerks.com/">Metrowerks CodeWarrior</a> Pro 6.x, 7.x, 243c248 < <td><A href="../tools/build/v1/darwin-tools.html"><code>darwin</code></A></td> --- > <td><a href="http://www.boost.org/tools/build/v1/darwin-tools.html"><code>darwin</code></a></td> 248c253 < <td><A href="../tools/build/v1/dmc-tools.html"><code>dmc</code></A></td> --- > <td><a href="http://www.boost.org/tools/build/v1/dmc-tools.html"><code>dmc</code></a></td> 252,253c257,258 < <td><A href="../tools/build/v1/dmc-stlport-tools.html"><code>dmc-stlport</code></A></td> < <td><a href="http://www.digitalmars.com/">Digital Mars C++</a>, using the <a href="http://www.stlport.org"> --- > <td><a href="http://www.boost.org/tools/build/v1/dmc-stlport-tools.html"><code>dmc-stlport</code></a></td> > <td><a href="http://www.digitalmars.com/">Digital Mars C++</a>, using the <a href="http://www.stlport.org/"> 257c262 < <td><A href="../tools/build/v1/edg-tools.html"><code>edg</code></A></td> --- > <td><a href="http://www.boost.org/tools/build/v1/edg-tools.html"><code>edg</code></a></td> 262,263c267,268 < <td><A href="../tools/build/v1/gcc-tools.html"><code>gcc</code></A></td> < <td><a href="http://gcc.gnu.org">GNU GCC</a> on Unix and <a href="http://www.cygwin.com"> --- > <td><a href="http://www.boost.org/tools/build/v1/gcc-tools.html"><code>gcc</code></a></td> > <td><a href="http://gcc.gnu.org/">GNU GCC</a> on Unix and <a href="http://www.cygwin.com/"> 267,269c272,274 < <td><A href="../tools/build/v1/gcc-stlport-tools.html"><code>gcc-stlport</code></A></td> < <td><a href="http://gcc.gnu.org">GNU GCC</a> on Unix and <a href="http://www.cygwin.com"> < Cygwin</a>, using the <a href="http://www.stlport.org">STLport</a> standard --- > <td><a href="http://www.boost.org/tools/build/v1/gcc-stlport-tools.html"><code>gcc-stlport</code></a></td> > <td><a href="http://gcc.gnu.org/">GNU GCC</a> on Unix and <a href="http://www.cygwin.com/"> > Cygwin</a>, using the <a href="http://www.stlport.org/">STLport</a> standard 273c278 < <td><A href="../tools/build/v1/gcc-nocygwin-tools.html"><code>gcc-nocygwin</code></A></td> --- > <td><a href="http://www.boost.org/tools/build/v1/gcc-nocygwin-tools.html"><code>gcc-nocygwin</code></a></td> 278c283 < <td><A href="../tools/build/v1/intel-linux-tools.html"><code>intel-linux</code></A></td> --- > <td><a href="http://www.boost.org/tools/build/v1/intel-linux-tools.html"><code>intel-linux</code></a></td> 283c288 < <td><A href="../tools/build/v1/intel-win32-tools.html"><code>intel-win32</code></A></td> --- > <td><a href="http://www.boost.org/tools/build/v1/intel-win32-tools.html"><code>intel-win32</code></a></td> 290c295 < <td><A href="../tools/build/v1/kcc-tools.html"><code>kcc</code></A></td> --- > <td><a href="http://www.boost.org/tools/build/v1/kcc-tools.html"><code>kcc</code></a></td> 294c299 < <td><A href="../tools/build/v1/kylix-tools.html"><code>kylix</code></A></td> --- > <td><a href="http://www.boost.org/tools/build/v1/kylix-tools.html"><code>kylix</code></a></td> 298,299c303,304 < <td><A href="../tools/build/v1/mingw-tools.html"><code>mingw</code></A></td> < <td>GNU GCC and associated tools in <a href="http://www.mingw.org">MinGW</a> configuration --- > <td><a href="http://www.boost.org/tools/build/v1/mingw-tools.html"><code>mingw</code></a></td> > <td>GNU GCC and associated tools in <a href="http://www.mingw.org/">MinGW</a> configuration 303,305c308,310 < <td><A href="../tools/build/v1/mingw-stlport-tools.html"><code>mingw-stlport</code></A></td> < <td>GNU GCC and associated tools in <a href="http://www.mingw.org">MinGW</a> configuration < (produces commercially redistributable objects), using the <a href="http://www.stlport.org"> --- > <td><a href="http://www.boost.org/tools/build/v1/mingw-stlport-tools.html"><code>mingw-stlport</code></a></td> > <td>GNU GCC and associated tools in <a href="http://www.mingw.org/">MinGW</a> configuration > (produces commercially redistributable objects), using the <a href="http://www.stlport.org/"> 309c314 < <td><A href="../tools/build/v1/mipspro-tools.html"><code>mipspro</code></A></td> --- > <td><a href="http://www.boost.org/tools/build/v1/mipspro-tools.html"><code>mipspro</code></a></td> 314c319 < <td><A href="../tools/build/v1/msvc-tools.html"><code>msvc</code></A></td> --- > <td><a href="http://www.boost.org/tools/build/v1/msvc-tools.html"><code>msvc</code></a></td> 320c325 < <td><A href="../tools/build/v1/msvc-stlport-tools.html"><code>msvc-stlport</code></A></td> --- > <td><a href="http://www.boost.org/tools/build/v1/msvc-stlport-tools.html"><code>msvc-stlport</code></a></td> 322c327 < 6 command-line tools, using the <a href="http://www.stlport.org">STLport</a> standard --- > 6 command-line tools, using the <a href="http://www.stlport.org/">STLport</a> standard 327c332 < <td><A href="../tools/build/v1/sunpro-tools.html"><code>sunpro</code></A></td> --- > <td><a href="http://www.boost.org/tools/build/v1/sunpro-tools.html"><code>sunpro</code></a></td> 331c336 < <td><A href="../tools/build/v1/tru64cxx-tools.html"><code>tru64cxx</code></A></td> --- > <td><a href="http://www.boost.org/tools/build/v1/tru64cxx-tools.html"><code>tru64cxx</code></a></td> 336c341 < <td><A href="../tools/build/v1/tru64cxx-tools.html"><code>tru64cxx65</code></A></td> --- > <td><a href="http://www.boost.org/tools/build/v1/tru64cxx-tools.html"><code>tru64cxx65</code></a></td> 341c346 < <td><A href="../tools/build/v1/vacpp-tools.html"><code>vacpp</code></A></td> --- > <td><a href="http://www.boost.org/tools/build/v1/vacpp-tools.html"><code>vacpp</code></a></td> 346c351 < <td><A href="../tools/build/v1/vc7-tools.html"><code>vc7</code></A></td> --- > <td><a href="http://www.boost.org/tools/build/v1/vc7-tools.html"><code>vc7</code></a></td> 351c356 < <td><A href="../tools/build/v1/vc7-stlport-tools.html"><code>vc7-stlport</code></A></td> --- > <td><a href="http://www.boost.org/tools/build/v1/vc7-stlport-tools.html"><code>vc7-stlport</code></a></td> 356c361 < <td><A href="../tools/build/v1/vc-7_1-tools.html"><code>vc-7_1</code></A></td> --- > <td><a href="http://www.boost.org/tools/build/v1/vc-7_1-tools.html"><code>vc-7_1</code></a></td> 361c366 < <td><A href="../tools/build/v1/vc-7_1-stlport-tools.html"><code>vc-7_1-stlport</code></A></td> --- > <td><a href="http://www.boost.org/tools/build/v1/vc-7_1-stlport-tools.html"><code>vc-7_1-stlport</code></a></td> 365c370 < </table> --- > </tbody></table> 367,370c372,375 < <p>The common build and install process is driven by the top-level build file (<A href="../Jamfile">Jamfile</A>).</p> < <table cellSpacing="2" cellPadding="2" width="100%" summary="" border="0"> < <tr vAlign="top" align="left"> < <td vAlign="top" align="center" width="40" bgColor="#ffff66"><font size="6"><b><a id="step4" name="step4"></a>4</b></font></td> --- > <p>The common build and install process is driven by the top-level build file (<a href="http://www.boost.org/Jamfile">Jamfile</a>).</p> > <table summary="" border="0" cellpadding="2" cellspacing="2" width="100%"> > <tbody><tr align="left" valign="top"> > <td align="center" bgcolor="#ffff66" valign="top" width="40"><font size="6"><b><a id="step4" name="step4"></a>4</b></font></td> 379c384 < </table> --- > </tbody></table> 386,389c391,394 < <table cellSpacing="2" cellPadding="2" width="100%" summary="" border="0"> < <tr vAlign="top" align="left"> < <td vAlign="top" align="center" width="40" bgColor="#ffff66"><font size="6"><b><a id="step5" name="step5"></a>5</b></font></td> < <td>Invoke the build system, specifying the <A href="#Tools">toolset</A>(s) you --- > <table summary="" border="0" cellpadding="2" cellspacing="2" width="100%"> > <tbody><tr align="left" valign="top"> > <td align="center" bgcolor="#ffff66" valign="top" width="40"><font size="6"><b><a id="step5" name="step5"></a>5</b></font></td> > <td>Invoke the build system, specifying the <a href="#Tools">toolset</a>(s) you 400c405 < </table> --- > </tbody></table> 409,410c414,415 < <table cellSpacing="0" cellPadding="2" summary="" border="1"> < <tr> --- > <table summary="" border="1" cellpadding="2" cellspacing="0"> > <tbody><tr> 416,417c421,422 < <td vAlign="top" noWrap align="left"><i>none</i></td> < <td vAlign="top" align="left">Only builds the Boost libraries. This lets you do --- > <td align="left" nowrap="nowrap" valign="top"><i>none</i></td> > <td align="left" valign="top">Only builds the Boost libraries. This lets you do 422,423c427,428 < <td vAlign="top" noWrap align="left"><tt>install</tt></td> < <td vAlign="top" align="left">Builds and installs Boost libraries and headers.</td> --- > <td align="left" nowrap="nowrap" valign="top"><tt>install</tt></td> > <td align="left" valign="top">Builds and installs Boost libraries and headers.</td> 426,427c431,432 < <td vAlign="top" noWrap align="left"><tt>stage</tt></td> < <td vAlign="top" align="left">Builds the Boost libraries and copies them into a --- > <td align="left" nowrap="nowrap" valign="top"><tt>stage</tt></td> > <td align="left" valign="top">Builds the Boost libraries and copies them into a 431c436 < <th noWrap> --- > <th nowrap="nowrap"> 433c438 < <td vAlign="top" align="left"> </td> --- > <td align="left" valign="top"> </td> 436,437c441,442 < <td vAlign="top" noWrap align="left"><tt>--help</tt></td> < <td vAlign="top" align="left">Shows a short summary of the options and syntax of --- > <td align="left" nowrap="nowrap" valign="top"><tt>--help</tt></td> > <td align="left" valign="top">Shows a short summary of the options and syntax of 441,442c446,447 < <td vAlign="top" noWrap align="left"><tt>-sTOOLS=<<i>toolsets</i>></tt></td> < <td vAlign="top" align="left">The list of tools to compile with. Usually only one --- > <td align="left" nowrap="nowrap" valign="top"><tt>-sTOOLS=<<i>toolsets</i>></tt></td> > <td align="left" valign="top">The list of tools to compile with. Usually only one 446,447c451,452 < <td vAlign="top" noWrap align="left"><tt>--prefix=PREFIX</tt></td> < <td vAlign="top" align="left">Install architecture independent files here.<br> --- > <td align="left" nowrap="nowrap" valign="top"><tt>--prefix=PREFIX</tt></td> > <td align="left" valign="top">Install architecture independent files here.<br> 452,453c457,458 < <td vAlign="top" noWrap align="left"><tt>--exec-prefix=EPREFIX</tt></td> < <td vAlign="top" align="left">Install architecture dependent files here.<br> --- > <td align="left" nowrap="nowrap" valign="top"><tt>--exec-prefix=EPREFIX</tt></td> > <td align="left" valign="top">Install architecture dependent files here.<br> 457,458c462,463 < <td vAlign="top" noWrap align="left"><tt>--libdir=DIR</tt></td> < <td vAlign="top" align="left">Install libraries here.<br> --- > <td align="left" nowrap="nowrap" valign="top"><tt>--libdir=DIR</tt></td> > <td align="left" valign="top">Install libraries here.<br> 462,463c467,468 < <td vAlign="top" noWrap align="left"><tt>--includedir=DIR</tt></td> < <td vAlign="top" align="left">Install source headers here. The Boost headers are --- > <td align="left" nowrap="nowrap" valign="top"><tt>--includedir=DIR</tt></td> > <td align="left" valign="top">Install source headers here. The Boost headers are 469,470c474,475 < <td vAlign="top" noWrap align="left"><tt>--builddir=DIR</tt></td> < <td vAlign="top" align="left">Build in this location instead of building within --- > <td align="left" nowrap="nowrap" valign="top"><tt>--builddir=DIR</tt></td> > <td align="left" valign="top">Build in this location instead of building within 475,476c480,481 < <td vAlign="top" noWrap align="left"><tt>--stagedir=DIR</tt></td> < <td vAlign="top" align="left">When staging only, with the "<tt>stage</tt>" action, --- > <td align="left" nowrap="nowrap" valign="top"><tt>--stagedir=DIR</tt></td> > <td align="left" valign="top">When staging only, with the "<tt>stage</tt>" action, 481,482c486,487 < <td vAlign="top" noWrap align="left"><tt>--without-<<i>library</i>></tt></td> < <td vAlign="top" align="left">Do not build, stage, or install the specified --- > <td align="left" nowrap="nowrap" valign="top"><tt>--without-<<i>library</i>></tt></td> > <td align="left" valign="top">Do not build, stage, or install the specified 486,487c491,492 < <td vAlign="top" noWrap align="left"><tt>--with-<<i>library</i>></tt></td> < <td vAlign="top" align="left">Build, stage, or install the specified library. This --- > <td align="left" nowrap="nowrap" valign="top"><tt>--with-<<i>library</i>></tt></td> > <td align="left" valign="top">Build, stage, or install the specified library. This 492,493c497,498 < <td vAlign="top" noWrap align="left"><tt>--with-python-root[=PYTHON_ROOT]</tt></td> < <td vAlign="top" align="left">Build Boost.Python libraries with the Python devel --- > <td align="left" nowrap="nowrap" valign="top"><tt>--with-python-root[=PYTHON_ROOT]</tt></td> > <td align="left" valign="top">Build Boost.Python libraries with the Python devel 501,502c506,507 < <td vAlign="top" noWrap align="left"><tt>--with-pydebug</tt></td> < <td vAlign="top" align="left">Build Boost.Python libraries using the Python debug --- > <td align="left" nowrap="nowrap" valign="top"><tt>--with-pydebug</tt></td> > <td align="left" valign="top">Build Boost.Python libraries using the Python debug 508,509c513,514 < <td vAlign="top" noWrap align="left"><tt>-sHAVE_ICU=1</tt></td> < <td vAlign="top" align="left">Build Boost.Regex libraries with Unicode support --- > <td align="left" nowrap="nowrap" valign="top"><tt>-sHAVE_ICU=1</tt></td> > <td align="left" valign="top">Build Boost.Regex libraries with Unicode support 514c519 < <a href="../libs/regex/doc/install.html#unicode">the Boost.Regex --- > <a href="http://www.boost.org/libs/regex/doc/install.html#unicode">the Boost.Regex 518,519c523,524 < <td vAlign="top" noWrap align="left"><tt>-sICU_PATH=<I>path</I></tt></td> < <td vAlign="top" align="left">Build Boost.Regex libraries with Unicode support --- > <td align="left" nowrap="nowrap" valign="top"><tt>-sICU_PATH=<i>path</i></tt></td> > <td align="left" valign="top">Build Boost.Regex libraries with Unicode support 523c528 < (or installed to) directory <I>path</I>. --- > (or installed to) directory <i>path</i>. 526c531 < <a href="../libs/regex/doc/install.html#unicode">the Boost.Regex --- > <a href="http://www.boost.org/libs/regex/doc/install.html#unicode">the Boost.Regex 530,531c535,536 < <td vAlign="top" noWrap align="left"><tt>-sNO_COMPRESSION=1</tt></td> < <td vAlign="top" align="left">Build Boost.Iostreams without support for the compression --- > <td align="left" nowrap="nowrap" valign="top"><tt>-sNO_COMPRESSION=1</tt></td> > <td align="left" valign="top">Build Boost.Iostreams without support for the compression 535c540 < <A HREF="http://www.boost.org/libs/iostreams/doc/index.html?path=7">Boost.Iostreams Installation</A>. --- > <a href="http://www.boost.org/libs/iostreams/doc/index.html?path=7">Boost.Iostreams Installation</a>. 538,541c543,546 < </table> < <p>There are additional options as supported by <A href="../tools/build/v1/build_system.htm"> < Boost.Build</A> and <A href="../tools/build/jam_src/index.html">Boost.Jam</A>. < Of the additional options perhaps the most imporant is "<tt>-s<A href="../tools/build/v1/build_system.htm#build">BUILD</A>=<features/variants></tt>" --- > </tbody></table> > <p>There are additional options as supported by <a href="http://www.boost.org/tools/build/v1/build_system.htm"> > Boost.Build</a> and <a href="http://www.boost.org/tools/build/jam_src/index.html">Boost.Jam</a>. > Of the additional options perhaps the most imporant is "<tt>-s<a href="http://www.boost.org/tools/build/v1/build_system.htm#build">BUILD</a>=<features/variants></tt>" 550c555 < line at the <A href="mailing_lists.htm#jamboost">Boost.Build mailing list</A>. --- > line at the <a href="http://www.boost.org/more/mailing_lists.htm#jamboost">Boost.Build mailing list</a>. 562c567 < <li> --- > </li><li> 564c569 < <li> --- > </li><li> 566c571 < <li> --- > </li><li> 568c573 < <li> --- > </li><li> 570c575 < <li> --- > </li><li> 572c577 < <li> --- > </li><li> 574c579 < <li> --- > </li><li> 578,582c583,587 < <table cellSpacing="0" cellPadding="0" width="100%" summary="" border="0"> < <tr> < <td colSpan="11"> < <table cellSpacing="2" cellPadding="2" bgColor="#cccccc" summary="" border="0"> < <tr> --- > <table summary="" border="0" cellpadding="0" cellspacing="0" width="100%"> > <tbody><tr> > <td colspan="11"> > <table summary="" bgcolor="#cccccc" border="0" cellpadding="2" cellspacing="2"> > <tbody><tr> 584,585c589,590 < · Library Prefix</th></tr> < </table> --- > · Library Prefix</th></tr> > </tbody></table> 590,593c595,598 < <td vAlign="bottom" bgColor="#cccccc" rowSpan="7"><tt><font size="+1">lib</font></tt></td> < <td colSpan="11"> < <table cellSpacing="2" cellPadding="2" summary="" border="0"> < <tr> --- > <td rowspan="7" bgcolor="#cccccc" valign="bottom"><tt><font size="+1">lib</font></tt></td> > <td colspan="11"> > <table summary="" border="0" cellpadding="2" cellspacing="2"> > <tbody><tr> 595,596c600,601 < · Library Name</th></tr> < </table> --- > · Library Name</th></tr> > </tbody></table> 600,603c605,608 < <td vAlign="bottom" rowSpan="6"><tt><font size="+1">boost_date_time</font></tt></td> < <td colSpan="10"> < <table cellSpacing="2" cellPadding="2" bgColor="#cccccc" summary="" border="0"> < <tr> --- > <td rowspan="6" valign="bottom"><tt><font size="+1">boost_date_time</font></tt></td> > <td colspan="10"> > <table summary="" bgcolor="#cccccc" border="0" cellpadding="2" cellspacing="2"> > <tbody><tr> 605,606c610,611 < · Toolset</th></tr> < </table> --- > · Toolset</th></tr> > </tbody></table> 610,614c615,619 < <td vAlign="bottom" bgColor="#cccccc" rowSpan="5"><tt><font size="+1">-</font></tt></td> < <td vAlign="bottom" bgColor="#cccccc" rowSpan="5"><tt><font size="+1">gcc</font></tt></td> < <td colSpan="8"> < <table cellSpacing="2" cellPadding="2" summary="" border="0"> < <tr> --- > <td rowspan="5" bgcolor="#cccccc" valign="bottom"><tt><font size="+1">-</font></tt></td> > <td rowspan="5" bgcolor="#cccccc" valign="bottom"><tt><font size="+1">gcc</font></tt></td> > <td colspan="8"> > <table summary="" border="0" cellpadding="2" cellspacing="2"> > <tbody><tr> 616,617c621,622 < · Threading</th></tr> < </table> --- > · Threading</th></tr> > </tbody></table> 621,625c626,630 < <td vAlign="bottom" rowSpan="4"><tt><font size="+1">-</font></tt></td> < <td vAlign="bottom" rowSpan="4"><tt><font size="+1">mt</font></tt></td> < <td colSpan="6"> < <table cellSpacing="2" cellPadding="2" bgColor="#cccccc" summary="" border="0"> < <tr> --- > <td rowspan="4" valign="bottom"><tt><font size="+1">-</font></tt></td> > <td rowspan="4" valign="bottom"><tt><font size="+1">mt</font></tt></td> > <td colspan="6"> > <table summary="" bgcolor="#cccccc" border="0" cellpadding="2" cellspacing="2"> > <tbody><tr> 627,628c632,633 < · Runtime</th></tr> < </table> --- > · Runtime</th></tr> > </tbody></table> 632,636c637,641 < <td vAlign="bottom" bgColor="#cccccc" rowSpan="3"><tt><font size="+1">-</font></tt></td> < <td vAlign="bottom" bgColor="#cccccc" rowSpan="3"><tt><font size="+1">d</font></tt></td> < <td colSpan="4"> < <table cellSpacing="2" cellPadding="2" summary="" border="0"> < <tr> --- > <td rowspan="3" bgcolor="#cccccc" valign="bottom"><tt><font size="+1">-</font></tt></td> > <td rowspan="3" bgcolor="#cccccc" valign="bottom"><tt><font size="+1">d</font></tt></td> > <td colspan="4"> > <table summary="" border="0" cellpadding="2" cellspacing="2"> > <tbody><tr> 638,639c643,644 < · Boost Version</th></tr> < </table> --- > · Boost Version</th></tr> > </tbody></table> 643,647c648,652 < <td vAlign="bottom" rowSpan="2"><tt><font size="+1">-</font></tt></td> < <td vAlign="bottom" rowSpan="2"><tt><font size="+1">1_31</font></tt></td> < <td colSpan="2"> < <table cellSpacing="2" cellPadding="2" bgColor="#cccccc" summary="" border="0"> < <tr> --- > <td rowspan="2" valign="bottom"><tt><font size="+1">-</font></tt></td> > <td rowspan="2" valign="bottom"><tt><font size="+1">1_31</font></tt></td> > <td colspan="2"> > <table summary="" bgcolor="#cccccc" border="0" cellpadding="2" cellspacing="2"> > <tbody><tr> 649,650c654,655 < · Library Type</th></tr> < </table> --- > · Library Type</th></tr> > </tbody></table> 654c659 < <td vAlign="bottom" bgColor="#cccccc"><tt><font size="+1">.a</font></tt></td> --- > <td bgcolor="#cccccc" valign="bottom"><tt><font size="+1">.a</font></tt></td> 657c662 < </table> --- > </tbody></table> 667c672 < <li> --- > </li><li> 674,691c679,696 < <P> < <TABLE id="Table1" cellSpacing="1" cellPadding="1" width="300" border="0"> < <TR> < <TD><FONT face="Courier New">*.dll</FONT></TD> < <TD>Dynamic library version.</TD> < </TR> < <TR> < <TD><FONT face="Courier New">*.lib</FONT> < </TD> < <TD>Import library for the dll.</TD> < </TR> < <TR> < <TD><FONT face="Courier New">lib*.lib</FONT> < </TD> < <TD>Static library version.</TD> < </TR> < </TABLE> < </P> --- > <p> > <table id="Table1" border="0" cellpadding="1" cellspacing="1" width="300"> > <tbody><tr> > <td><font face="Courier New">*.dll</font></td> > <td>Dynamic library version.</td> > </tr> > <tr> > <td><font face="Courier New">*.lib</font> > </td> > <td>Import library for the dll.</td> > </tr> > <tr> > <td><font face="Courier New">lib*.lib</font> > </td> > <td>Static library version.</td> > </tr> > </tbody></table> > </p> 701,702c706,707 < <table cellPadding="5" summary="" border="1"> < <tr> --- > <table summary="" border="1" cellpadding="5"> > <tbody><tr> 707c712 < <td><A href="../tools/build/v1/borland-tools.html"><code>borland</code></A></td> --- > <td><a href="http://www.boost.org/tools/build/v1/borland-tools.html"><code>borland</code></a></td> 711c716 < <td><A href="../tools/build/v1/como-tools.html"><code>como</code></A></td> --- > <td><a href="http://www.boost.org/tools/build/v1/como-tools.html"><code>como</code></a></td> 715c720 < <td><code><A href="../tools/build/v1/como-tools.html">como-win32</A></code></td> --- > <td><code><a href="http://www.boost.org/tools/build/v1/como-tools.html">como-win32</a></code></td> 719c724 < <td><A href="../tools/build/v1/cw-tools.html"><code>cw</code></A></td> --- > <td><a href="http://www.boost.org/tools/build/v1/cw-tools.html"><code>cw</code></a></td> 723c728 < <td><A href="../tools/build/v1/darwin-tools.html"><code>darwin</code></A></td> --- > <td><a href="http://www.boost.org/tools/build/v1/darwin-tools.html"><code>darwin</code></a></td> 727c732 < <td><A href="../tools/build/v1/dmc-tools.html"><code>dmc</code></A></td> --- > <td><a href="http://www.boost.org/tools/build/v1/dmc-tools.html"><code>dmc</code></a></td> 731c736 < <td><A href="../tools/build/v1/dmc-stlport-tools.html"><code>dmc-stlport</code></A></td> --- > <td><a href="http://www.boost.org/tools/build/v1/dmc-stlport-tools.html"><code>dmc-stlport</code></a></td> 735c740 < <td><A href="../tools/build/v1/edg-tools.html"><code>edg</code></A></td> --- > <td><a href="http://www.boost.org/tools/build/v1/edg-tools.html"><code>edg</code></a></td> 739c744 < <td><A href="../tools/build/v1/gcc-tools.html"><code>gcc</code></A></td> --- > <td><a href="http://www.boost.org/tools/build/v1/gcc-tools.html"><code>gcc</code></a></td> 743c748 < <td><A href="../tools/build/v1/gcc-stlport-tools.html"><code>gcc-stlport</code></A></td> --- > <td><a href="http://www.boost.org/tools/build/v1/gcc-stlport-tools.html"><code>gcc-stlport</code></a></td> 747c752 < <td><A href="../tools/build/v1/gcc-nocygwin-tools.html"><code>gcc-nocygwin</code></A></td> --- > <td><a href="http://www.boost.org/tools/build/v1/gcc-nocygwin-tools.html"><code>gcc-nocygwin</code></a></td> 751c756 < <td><A href="../tools/build/v1/intel-linux-tools.html"><code>intel-linux</code></A></td> --- > <td><a href="http://www.boost.org/tools/build/v1/intel-linux-tools.html"><code>intel-linux</code></a></td> 755c760 < <td><A href="../tools/build/v1/intel-win32-tools.html"><code>intel-win32</code></A></td> --- > <td><a href="http://www.boost.org/tools/build/v1/intel-win32-tools.html"><code>intel-win32</code></a></td> 759c764 < <td><A href="../tools/build/v1/kcc-tools.html"><code>kcc</code></A></td> --- > <td><a href="http://www.boost.org/tools/build/v1/kcc-tools.html"><code>kcc</code></a></td> 763c768 < <td><A href="../tools/build/v1/kylix-tools.html"><code>kylix</code></A></td> --- > <td><a href="http://www.boost.org/tools/build/v1/kylix-tools.html"><code>kylix</code></a></td> 767c772 < <td><A href="../tools/build/v1/mingw-tools.html"><code>mingw</code></A></td> --- > <td><a href="http://www.boost.org/tools/build/v1/mingw-tools.html"><code>mingw</code></a></td> 771c776 < <td><A href="../tools/build/v1/mingw-stlport-tools.html"><code>mingw-stlport</code></A></td> --- > <td><a href="http://www.boost.org/tools/build/v1/mingw-stlport-tools.html"><code>mingw-stlport</code></a></td> 775c780 < <td><A href="../tools/build/v1/mipspro-tools.html"><code>mipspro</code></A></td> --- > <td><a href="http://www.boost.org/tools/build/v1/mipspro-tools.html"><code>mipspro</code></a></td> 779c784 < <td><A href="../tools/build/v1/msvc-tools.html"><code>msvc</code></A></td> --- > <td><a href="http://www.boost.org/tools/build/v1/msvc-tools.html"><code>msvc</code></a></td> 783c788 < <td><A href="../tools/build/v1/msvc-stlport-tools.html"><code>msvc-stlport</code></A></td> --- > <td><a href="http://www.boost.org/tools/build/v1/msvc-stlport-tools.html"><code>msvc-stlport</code></a></td> 787c792 < <td><A href="../tools/build/v1/sunpro-tools.html"><code>sunpro</code></A></td> --- > <td><a href="http://www.boost.org/tools/build/v1/sunpro-tools.html"><code>sunpro</code></a></td> 791c796 < <td><A href="../tools/build/v1/tru64cxx-tools.html"><code>tru64cxx</code></A></td> --- > <td><a href="http://www.boost.org/tools/build/v1/tru64cxx-tools.html"><code>tru64cxx</code></a></td> 795c800 < <td><A href="../tools/build/v1/tru64cxx-tools.html"><code>tru64cxx65</code></A></td> --- > <td><a href="http://www.boost.org/tools/build/v1/tru64cxx-tools.html"><code>tru64cxx65</code></a></td> 799c804 < <td><A href="../tools/build/v1/vacpp-tools.html"><code>vacpp</code></A></td> --- > <td><a href="http://www.boost.org/tools/build/v1/vacpp-tools.html"><code>vacpp</code></a></td> 803c808 < <td><A href="../tools/build/v1/vc7-tools.html"><code>vc7</code></A></td> --- > <td><a href="http://www.boost.org/tools/build/v1/vc7-tools.html"><code>vc7</code></a></td> 807c812 < <td><A href="../tools/build/v1/vc7-stlport-tools.html"><code>vc7-stlport</code></A></td> --- > <td><a href="http://www.boost.org/tools/build/v1/vc7-stlport-tools.html"><code>vc7-stlport</code></a></td> 811c816 < <td><A href="../tools/build/v1/vc-7_1-tools.html"><code>vc-7_1</code></A></td> --- > <td><a href="http://www.boost.org/tools/build/v1/vc-7_1-tools.html"><code>vc-7_1</code></a></td> 815c820 < <td><A href="../tools/build/v1/vc-7_1-stlport-tools.html"><code>vc-7_1-stlport</code></A></td> --- > <td><a href="http://www.boost.org/tools/build/v1/vc-7_1-stlport-tools.html"><code>vc-7_1-stlport</code></a></td> 822c827 < </table> --- > </tbody></table> 831,832c836,837 < <table cellPadding="5" summary="" border="1"> < <tr> --- > <table summary="" border="1" cellpadding="5"> > <tbody><tr> 861c866 < </table> --- > </tbody></table> 877,878c882,883 < <H2><A name="auto-link"></A>Automatic Linking on Windows</H2> < <P>For most Boost libraries that have separate source, the correct build variant --- > <h2><a name="auto-link"></a>Automatic Linking on Windows</h2> > <p>For most Boost libraries that have separate source, the correct build variant 882,883c887,888 < Metrowerks C++ , and Borland C++ all support this).</P> < <P>If you are linking to a dynamic runtime, then you can choose to link to either --- > Metrowerks C++ , and Borland C++ all support this).</p> > <p>If you are linking to a dynamic runtime, then you can choose to link to either 885,886c890,891 < You can alter this for a specific library <EM>whatever</EM> by defining < BOOST_WHATEVER_DYN_LINK to force Boost library <EM>whatever</EM> to be linked --- > You can alter this for a specific library <em>whatever</em> by defining > BOOST_WHATEVER_DYN_LINK to force Boost library <em>whatever</em> to be linked 888,891c893,896 < link by defining BOOST_ALL_DYN_LINK.</P> < <P>This feature can be disabled for Boost library <EM>whatever</EM> by defining < BOOST_WHATEVER_NO_LIB, or for all of Boost by defining BOOST_ALL_NO_LIB.</P> < <P>If you want to observe which libraries are being linked against then defining --- > link by defining BOOST_ALL_DYN_LINK.</p> > <p>This feature can be disabled for Boost library <em>whatever</em> by defining > BOOST_WHATEVER_NO_LIB, or for all of Boost by defining BOOST_ALL_NO_LIB.</p> > <p>If you want to observe which libraries are being linked against then defining 893,894c898,899 < message</code> each time a library is selected for linking.</P> < <P>There are some Boost libraries (<A href="../libs/test/doc/index.html">Boost.Test</A> --- > message</code> each time a library is selected for linking.</p> > <p>There are some Boost libraries (<a href="http://www.boost.org/libs/test/doc/index.html">Boost.Test</a> 897c902 < you are using for more information, and the <A href="../libs/config/index.html">Boost.Config</A> --- > you are using for more information, and the <a href="http://www.boost.org/libs/config/index.html">Boost.Config</a> 900,962c905,967 < here consist of headers only):</P> < <P> < <TABLE id="Table2" cellSpacing="1" cellPadding="1" width="100%" border="1"> < <TR> < <TD><STRONG>Library</STRONG></TD> < <TD><STRONG>Static Link</STRONG></TD> < <TD><STRONG>Dynamic Link</STRONG></TD> < <TD><STRONG>Default linkage</STRONG></TD> < <TD><STRONG>Automatic library selection</STRONG></TD> < <TD><STRONG>Comments</STRONG></TD> < </TR> < <TR> < <TD>Date-Time</TD> < <TD>Yes</TD> < <TD>Yes</TD> < <TD>static</TD> < <TD>Yes</TD> < <TD> </TD> < </TR> < <TR> < <TD>Filesystem</TD> < <TD>Yes</TD> < <TD> < <P>Yes</P> < </TD> < <TD>static</TD> < <TD>Yes</TD> < <TD> </TD> < </TR> < <TR> < <TD>Graph</TD> < <TD>Yes</TD> < <TD>No</TD> < <TD>static</TD> < <TD>No</TD> < <TD>The separate Graph library source is needed only when <A href="../libs/graph/doc/read_graphviz.html"> < reading an AT&T graphviz file.</A></TD> < </TR> < <TR> < <TD>Iostreams</TD> < <TD>Yes</TD> < <TD> < <P>Yes</P> < </TD> < <TD>static</TD> < <TD>Yes</TD> < <TD> </TD> < </TR> < <TR> < <TD>Program Options</TD> < <TD>Yes</TD> < <TD>Yes</TD> < <TD>static</TD> < <TD>Yes</TD> < <TD> </TD> < </TR> < <TR> < <TD>Python</TD> < <TD>Yes</TD> < <TD>Yes</TD> < <TD>dynamic</TD> < <TD>No</TD> < <TD>Since all Python extensions are DLL's it makes sense to dynamic link to the --- > here consist of headers only):</p> > <p> > <table id="Table2" border="1" cellpadding="1" cellspacing="1" width="100%"> > <tbody><tr> > <td><strong>Library</strong></td> > <td><strong>Static Link</strong></td> > <td><strong>Dynamic Link</strong></td> > <td><strong>Default linkage</strong></td> > <td><strong>Automatic library selection</strong></td> > <td><strong>Comments</strong></td> > </tr> > <tr> > <td>Date-Time</td> > <td>Yes</td> > <td>Yes</td> > <td>static</td> > <td>Yes</td> > <td> </td> > </tr> > <tr> > <td>Filesystem</td> > <td>Yes</td> > <td> > <p>Yes</p> > </td> > <td>static</td> > <td>Yes</td> > <td> </td> > </tr> > <tr> > <td>Graph</td> > <td>Yes</td> > <td>No</td> > <td>static</td> > <td>No</td> > <td>The separate Graph library source is needed only when <a href="http://www.boost.org/libs/graph/doc/read_graphviz.html"> > reading an AT&T graphviz file.</a></td> > </tr> > <tr> > <td>Iostreams</td> > <td>Yes</td> > <td> > <p>Yes</p> > </td> > <td>static</td> > <td>Yes</td> > <td> </td> > </tr> > <tr> > <td>Program Options</td> > <td>Yes</td> > <td>Yes</td> > <td>static</td> > <td>Yes</td> > <td> </td> > </tr> > <tr> > <td>Python</td> > <td>Yes</td> > <td>Yes</td> > <td>dynamic</td> > <td>No</td> > <td>Since all Python extensions are DLL's it makes sense to dynamic link to the 964,1017c969,1022 < if you are embedding python).</TD> < </TR> < <TR> < <TD>Regex</TD> < <TD>Yes</TD> < <TD>Yes</TD> < <TD>static</TD> < <TD>Yes</TD> < <TD> </TD> < </TR> < <TR> < <TD>Serialization</TD> < <TD>Yes</TD> < <TD>Yes</TD> < <TD>static</TD> < <TD>Yes</TD> < <TD> </TD> < </TR> < <TR> < <TD>Signals</TD> < <TD>Yes</TD> < <TD>Yes</TD> < <TD>static</TD> < <TD>Yes</TD> < <TD> </TD> < </TR> < <TR> < <TD>Test</TD> < <TD>Yes</TD> < <TD>No</TD> < <TD>static</TD> < <TD>No</TD> < <TD>Which library you link to depends upon which program entry point you define, < rather than which Boost.Test features you use.</TD> < </TR> < <TR> < <TD>Thread</TD> < <TD>Partial</TD> < <TD>Yes</TD> < <TD>static (Visual C++), otherwise dynamic</TD> < <TD>Yes</TD> < <TD>For technical reasons static linking is supported on only one Windows compiler < (Visual C++).</TD> < </TR> < <TR> < <TD>Wave</TD> < <TD>Yes</TD> < <TD>Yes</TD> < <TD>static</TD> < <TD>Yes</TD> < <TD> </TD> < </TR> < </TABLE> < </P> --- > if you are embedding python).</td> > </tr> > <tr> > <td>Regex</td> > <td>Yes</td> > <td>Yes</td> > <td>static</td> > <td>Yes</td> > <td> </td> > </tr> > <tr> > <td>Serialization</td> > <td>Yes</td> > <td>Yes</td> > <td>static</td> > <td>Yes</td> > <td> </td> > </tr> > <tr> > <td>Signals</td> > <td>Yes</td> > <td>Yes</td> > <td>static</td> > <td>Yes</td> > <td> </td> > </tr> > <tr> > <td>Test</td> > <td>Yes</td> > <td>No</td> > <td>static</td> > <td>No</td> > <td>Which library you link to depends upon which program entry point you define, > rather than which Boost.Test features you use.</td> > </tr> > <tr> > <td>Thread</td> > <td>Partial</td> > <td>Yes</td> > <td>static (Visual C++), otherwise dynamic</td> > <td>Yes</td> > <td>For technical reasons static linking is supported on only one Windows compiler > (Visual C++).</td> > </tr> > <tr> > <td>Wave</td> > <td>Yes</td> > <td>Yes</td> > <td>static</td> > <td>Yes</td> > <td> </td> > </tr> > </tbody></table> > </p> 1023c1028 < <A href="../libs/config/config.htm#configuring">Configure the boost source code</A>. --- > <a href="http://www.boost.org/libs/config/config.htm#configuring">Configure the boost source code</a>. 1028c1033 < <li> --- > </li><li> 1031c1036 < more information, see these detailed <a href="../libs/python/doc/building.html#building"> --- > more information, see these detailed <a href="http://www.boost.org/libs/python/doc/building.html#building"> 1037,1039c1042,1044 < <p>Copyright © Rene Rivera 2003.<br> < Copyright © Jens Maurer 2001.<BR> < Copyright © John Maddock 2004.</p> --- > <p>Copyright © Rene Rivera 2003.<br> > Copyright © Jens Maurer 2001.<br> > Copyright © John Maddock 2004.</p> 1041c1046 < accompanying file <a href="../LICENSE_1_0.txt">LICENSE_1_0.txt</a> or copy at <a href="http://www.boost.org/LICENSE_1_0.txt"> --- > accompanying file <a href="http://www.boost.org/LICENSE_1_0.txt">LICENSE_1_0.txt</a> or copy at <a href="http://www.boost.org/LICENSE_1_0.txt"> 1043,1047c1048 < </body> < </html> < < < --- > </body></html>

4 8

Re: [boost] Report from Mont Tremblant C++ Committee meeting
by Thore Karlsen 11 Oct '05

11 Oct '05

On Tue, 11 Oct 2005 15:59:23 -0400, "Gennadiy Rozental" <gennadiy.rozental(a)thomson.com> wrote: >> Well, one thing I use it for is parsing HTTP directly in the read >> buffer, which is a vector. If the interfaces weren't generic, I'd either >> have to write my own functions to duplicate the functionality, or I'd >> have to copy the incoming data to a string. The first seems silly, and >> the latter would have unacceptable overhead in my case. The HTTP I'm >> parsing is streaming video from several dozen cameras at once, so I have >> to work with the buffers directly. >> >> I also use this library on plain old C strings, which wouldn't be >> possible if it were locked to basic_string. >> >> Some changes may make sense, but I really like the way it is now. >The way I see it all string algorithms should be using class like >const_string in their interfaces. Maybe I'm misunderstanding you, but are you suggesting that no string algorithms should modify a string in-place? That would be unacceptable to me. I wouldn't use such a library. -- Be seeing you.

1 0

Re: [boost] [integer] Create (u)int_natural_t
by Martin Bonner 11 Oct '05

11 Oct '05

----Original Message---- From: Simon Buchan [mailto:simon@hand-multimedia.co.nz] Sent: 29 September 2005 10:21 To: boost(a)lists.boost.org Subject: Re: [boost] [integer] Create (u)int_natural_t > Daryle Walker wrote: >> The "int" type was supposed to match the processor's natural built-in >> integer processor. That was easy to maintain in the 16- and 32-bit >> eras, but got screwed up when we started 64-bit computing. The C >> and C++ communities decided to expand its integer types by keeping >> the current types at their 32-bit-era sizes and extended the type >> system with a "long long" instead of moving "int" and "long" up and >> adding a "short short". Now we don't have a convenient way to name >> the best integer type in a portable fashion. I suggest we add a >> "int_natural_t" typedef to <boost/cstdint.hpp> to name the best >> integer type (and a corresponding "uint_natural_t"). We would have >> to research what that type is for each compiler and/or platform >> combination and use #conditionals. I don't think it's worth it. The performance difference between a 16-bit integer and 32-bit integer on a PDP-11 was pretty significant. Is there any noticable difference between a 32-bit and 64-bit integer on any of the 64-bit processors? > Isn't int the 'natural' integer type, by definition? Depends what you mean by "natural", but for a normal English meaning, probably not. > I never understood why long didn't become the 64-bit type. It seems > pointless to have int and long the same size on 32-bit. Oh god no! The thread that would not die! This has been argued to death on comp.std.c. The reason long didn't become the 64-bit type is that most commercial C compiler vendors wanted to continue to support code their customers had written that assumed long was exactly four eight-bit bytes. You can argue as long as you like that the problem is in that code (and I would agree with you). It won't change the fact that telling your customers they are wrong is not usually the route to commercial success. > Who still writes 16-bit code on desktop, anyway? :D Nobody ... but who still writes for the desktop? Think about the number of car radios (as just one example) compared to the number of PCs. -- Martin Bonner Martin.Bonner(a)Pitechnology.com Pi Technology, Milton Hall, Ely Road, Milton, Cambridge, CB4 6WZ, ENGLAND Tel: +44 (0)1223 441434

5 4

[parameter] little flaw in tutorial
by Martin Wille 11 Oct '05

11 Oct '05

Hello, the example code in the Boost.Parameter tutorial #includes <boost/parameter/keyword.hpp> as only Boost.Parameter header. This is apparently insufficient, since I get errors regarding incomplete types (e.g. return type `struct boost::parameter::aux::tagged_argument<graphs::tag::index_map, const char[13]>' is incomplete ). With <boost/parameter.hpp> #included, there are no errors. Regards, m Send instant messages to your online friends http://au.messenger.yahoo.com

2 3

Re: [boost] GUI coordinate units (Was: GUI foundations)
by brangdon＠cix.compulink.co.uk 11 Oct '05

11 Oct '05

In-Reply-To: <434AED3E.1020006(a)torjo.com> john.lists(a)torjo.com (John Torjo) wrote (abridged): > I'm not sure I understand: once you set a "size policy" to "fixed", it > seems that you would need to set a fixed size (for a button, for > instance). You could calculate it at run-time, though. "Fixed" is relative. For example, if you based it on the width of some text, it would change (be recalculated) whenever the dialog's font changed. -- Dave Harris, Nottingham, UK.

1 0

[serialization]Thread-safety of serialization lib
by Sean Huang 11 Oct '05

11 Oct '05

There are many places in serialization library that use a pattern like the following: static oserializer & instantiate(){ static oserializer instance; return instance; } AFAIK, not all compilers guarantee the initialization of a function level (or class member level) static variable is thread-safe. If I understand the code correctly, this essentially means that simultaneously serializing objects of the same type is not thread-safe. Am I missing something here? Thanks, Sean

2 2

compiler error with Spirit: wrong internal use of regex library
by Oliver Kullmann 11 Oct '05

11 Oct '05

Hello, when using the regular expression parser with the Spirit library, I get the following compilation error (I've edited the g++-output somewhat): g++ -c -o TestSpirit.o -ansi -g -Iboost-1_33/include/boost-1_33/ TestSpirit.cpp In file included from boost-1_33/include/boost-1_33/boost/spirit/utility/regex.hpp:46, boost-1_33/include/boost-1_33/boost/spirit/utility/impl/regex.ipp:65: error: wrong number of template arguments (1, should be 2) Command exited with non-zero status 1 I edited the file boost-1_33/include/boost-1_33/boost/spirit/utility/impl/regex.ipp, replacing line 65 boost::reg_expression<CharT> rxstr; // regular expression to match with boost::basic_regex<CharT> rxstr; // regular expression to match , and now it seems to work (at least my application). So I guess the Spirit library needs to be updated (according to the new regex-library standard). Oliver P.S. I tried it out with g++ 3.4.3 and 4.0.1, but it doesn't matter.

1 0

a question about scoped_ptr and checked_delete
by Bronek Kozicki 11 Oct '05

11 Oct '05

As I understand, checked_delete is being used by scoped_ptr to prevent deletion of incomplete type. However, this very simple program is accepted by MSVC6, MSVC71 and MinGW (GCC) 3.4.4, even though implicit destructor of A is deleting incomplete class A::impl . Only one compiler of these that I could test (Comeau 4.3.3) throws compilation error. Could we do better? I know, there are simple workaround - declare destructor in class A or use shared_ptr . But as we know, workarounds in user code to generate compilation error (not suppress them) are rare thing. B. #include <boost/scoped_ptr.hpp> struct A { struct impl; boost::scoped_ptr<impl> impl_; A(); }; int main() { A a; } struct A::impl {}; A::A() : impl_(new impl()) {}

2 1

Boost regression notification (2005-10-11 [RC_1_33_0])
by Douglas Gregor 11 Oct '05

11 Oct '05

Boost regression test failures ------------------------------ Report time: 2005-10-11T13:56:13Z This report lists all regression test failures on release platforms. Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-RC_1_33_0/developer/i… 428 failures in 5 libraries: graph (1) iostreams (1) range (3) serialization (418) spirit (5) |graph| graphviz_test: cw-9_4 |iostreams| gzip_test: gcc-4_0-darwin |range| array: vc-6_5 vc-6_5-stlport vc-7_0 |serialization| test_binary_text_archive: vc-7_1 test_binary_text_archive_dll: vc-7_1 test_class_info_save_text_archive: vc-7_1 test_class_info_save_text_archive_dll: vc-7_1 test_demo_polymorphic: borland-5_6_4 cw-8_3 cw-9_4 cw-9_5-darwin gcc-3_3-darwin gcc-3_4_3-sunos intel-win32-8_1 intel-win32-9_0 mingw-3_4_2 vc-6_5 vc-7_0 vc-7_1 test_demo_polymorphic_dll: borland-5_6_4 cw-9_4 gcc-3_3-darwin gcc-3_4_3-sunos intel-win32-8_1 intel-win32-9_0 mingw-3_4_2 vc-6_5 vc-7_0 vc-7_1 test_demo_xml_load: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin intel-win32-8_1 test_demo_xml_load_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_derived_text_archive: vc-7_1 test_derived_text_archive_dll: vc-7_1 test_diamond_binary_archive: cw-9_4 gcc-3_3-darwin intel-win32-8_1 intel-win32-9_0 mingw-3_4_2 test_diamond_binary_archive_dll: cw-9_4 gcc-3_3-darwin intel-win32-8_1 intel-win32-9_0 mingw-3_4_2 test_diamond_text_archive: cw-9_4 gcc-3_3-darwin intel-win32-8_1 intel-win32-9_0 mingw-3_4_2 test_diamond_text_archive_dll: cw-9_4 gcc-3_3-darwin intel-win32-8_1 intel-win32-9_0 mingw-3_4_2 test_diamond_text_warchive: cw-9_4 gcc-3_3-darwin intel-win32-8_1 intel-win32-9_0 test_diamond_text_warchive_dll: cw-9_4 gcc-3_3-darwin intel-win32-8_1 intel-win32-9_0 test_diamond_xml_archive: cw-9_4 gcc-3_3-darwin intel-win32-8_1 intel-win32-9_0 mingw-3_4_2 test_diamond_xml_archive_dll: cw-9_4 gcc-3_3-darwin intel-win32-8_1 intel-win32-9_0 mingw-3_4_2 test_diamond_xml_warchive: cw-9_4 gcc-3_3-darwin intel-win32-8_1 intel-win32-9_0 test_diamond_xml_warchive_dll: cw-9_4 gcc-3_3-darwin intel-win32-8_1 intel-win32-9_0 test_exported_binary_archive: gcc-3.2.3-linux gcc-4.0.1-linux intel-9.0-linux vc-6_5 test_exported_binary_archive_dll: gcc-4.0.1-linux vc-6_5 test_exported_text_archive: gcc-3.2.3-linux gcc-4.0.1-linux vc-6_5 vc-7_1 test_exported_text_archive_dll: gcc-3.2.3-linux gcc-4.0.1-linux vc-6_5 vc-7_1 test_exported_text_warchive: gcc-4.0.1-linux vc-6_5 test_exported_text_warchive_dll: gcc-4.0.1-linux vc-6_5 test_exported_xml_archive: gcc-4.0.1-linux intel-8.1-linux vc-6_5 test_exported_xml_archive_dll: gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-6_5 test_exported_xml_warchive: gcc-3.2.3-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-6_5 test_exported_xml_warchive_dll: gcc-3.2.3-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-6_5 test_map_binary_archive: cw-8_3 cw-9_4 gcc-3_3-darwin intel-win32-8_1 intel-win32-9_0 mingw-3_4_2 test_map_binary_archive_dll: cw-9_4 gcc-3_3-darwin intel-win32-8_1 intel-win32-9_0 mingw-3_4_2 test_map_text_archive: cw-8_3 cw-9_4 gcc-3_3-darwin intel-win32-8_1 intel-win32-9_0 mingw-3_4_2 test_map_text_archive_dll: cw-9_4 gcc-3_3-darwin intel-win32-8_1 intel-win32-9_0 mingw-3_4_2 test_map_text_warchive: cw-8_3 cw-9_4 gcc-3_3-darwin intel-win32-8_1 intel-win32-9_0 test_map_text_warchive_dll: cw-9_4 gcc-3_3-darwin intel-win32-8_1 intel-win32-9_0 test_map_xml_archive: cw-8_3 cw-9_4 gcc-3_3-darwin intel-win32-8_1 intel-win32-9_0 mingw-3_4_2 test_map_xml_archive_dll: cw-9_4 gcc-3_3-darwin intel-win32-8_1 intel-win32-9_0 mingw-3_4_2 test_map_xml_warchive: cw-8_3 cw-9_4 gcc-3_3-darwin intel-win32-8_1 intel-win32-9_0 test_map_xml_warchive_dll: cw-9_4 gcc-3_3-darwin intel-win32-8_1 intel-win32-9_0 test_mi_text_archive: vc-7_1 test_mi_text_archive_dll: vc-7_1 test_no_rtti_binary_archive: vc-6_5 test_no_rtti_binary_archive_dll: vc-6_5 test_no_rtti_text_archive: vc-6_5 test_no_rtti_text_archive_dll: vc-6_5 test_no_rtti_text_warchive: vc-6_5 test_no_rtti_text_warchive_dll: vc-6_5 test_no_rtti_xml_archive: vc-6_5 test_no_rtti_xml_archive_dll: vc-6_5 test_no_rtti_xml_warchive: vc-6_5 test_no_rtti_xml_warchive_dll: vc-6_5 test_non_default_ctor2_text_archive: vc-7_1 test_non_default_ctor2_text_archive_dll: vc-7_1 test_non_default_ctor_text_archive: vc-7_1 test_non_default_ctor_text_archive_dll: vc-7_1 test_non_intrusive_text_archive: vc-7_1 test_non_intrusive_text_archive_dll: vc-7_1 test_null_ptr_text_archive: vc-7_1 test_null_ptr_text_archive_dll: vc-7_1 test_object_text_archive: vc-7_1 test_object_text_archive_dll: vc-7_1 test_polymorphic_binary_archive: borland-5_6_4 cw-8_3 cw-9_4 cw-9_5-darwin gcc-3_3-darwin gcc-3_4_3-sunos intel-win32-8_1 intel-win32-9_0 mingw-3_4_2 vc-6_5 vc-7_0 vc-7_1 test_polymorphic_binary_archive_dll: borland-5_6_4 cw-9_4 cw-9_5-darwin gcc-3_3-darwin gcc-3_4_3-sunos intel-win32-8_1 intel-win32-9_0 mingw-3_4_2 vc-6_5 vc-7_0 vc-7_1 test_polymorphic_text_archive: borland-5_6_4 cw-8_3 cw-9_4 cw-9_5-darwin gcc-3_3-darwin gcc-3_4_3-sunos intel-win32-8_1 intel-win32-9_0 mingw-3_4_2 vc-6_5 vc-7_0 vc-7_1 test_polymorphic_text_archive_dll: borland-5_6_4 cw-9_4 gcc-3_3-darwin gcc-3_4_3-sunos intel-win32-8_1 intel-win32-9_0 mingw-3_4_2 vc-6_5 vc-7_0 vc-7_1 test_polymorphic_text_warchive: borland-5_6_4 cw-8_3 cw-9_4 cw-9_5-darwin gcc-3_3-darwin gcc-3_4_3-sunos intel-win32-8_1 intel-win32-9_0 vc-6_5 vc-7_0 vc-7_1 test_polymorphic_text_warchive_dll: borland-5_6_4 cw-9_4 gcc-3_3-darwin gcc-3_4_3-sunos intel-win32-8_1 intel-win32-9_0 vc-6_5 vc-7_0 vc-7_1 test_polymorphic_xml_archive: borland-5_6_4 cw-8_3 cw-9_4 cw-9_5-darwin gcc-3_3-darwin gcc-3_4_3-sunos intel-win32-8_1 intel-win32-9_0 mingw-3_4_2 vc-6_5 vc-7_0 vc-7_1 test_polymorphic_xml_archive_dll: borland-5_6_4 cw-9_4 gcc-3_3-darwin gcc-3_4_3-sunos intel-win32-8_1 intel-win32-9_0 mingw-3_4_2 vc-6_5 vc-7_0 vc-7_1 test_polymorphic_xml_warchive: borland-5_6_4 cw-8_3 cw-9_4 cw-9_5-darwin gcc-3_3-darwin gcc-3_4_3-sunos intel-win32-8_1 intel-win32-9_0 vc-6_5 vc-7_0 vc-7_1 test_polymorphic_xml_warchive_dll: borland-5_6_4 cw-9_4 gcc-3_3-darwin gcc-3_4_3-sunos intel-win32-8_1 intel-win32-9_0 vc-6_5 vc-7_0 vc-7_1 test_primitive_text_archive: vc-7_1 test_primitive_text_archive_dll: vc-7_1 test_registered_text_archive: vc-7_1 test_registered_text_archive_dll: vc-7_1 test_set_binary_archive: cw-8_3 cw-9_4 gcc-3_3-darwin intel-win32-8_1 intel-win32-9_0 mingw-3_4_2 test_set_binary_archive_dll: cw-9_4 gcc-3_3-darwin intel-win32-8_1 intel-win32-9_0 mingw-3_4_2 test_set_text_archive: cw-8_3 cw-9_4 gcc-3_3-darwin intel-win32-8_1 intel-win32-9_0 mingw-3_4_2 test_set_text_archive_dll: cw-9_4 gcc-3_3-darwin intel-win32-8_1 intel-win32-9_0 mingw-3_4_2 test_set_text_warchive: cw-8_3 cw-9_4 gcc-3_3-darwin intel-win32-8_1 intel-win32-9_0 test_set_text_warchive_dll: cw-9_4 gcc-3_3-darwin intel-win32-8_1 intel-win32-9_0 test_set_xml_archive: cw-8_3 cw-9_4 gcc-3_3-darwin intel-win32-8_1 intel-win32-9_0 mingw-3_4_2 test_set_xml_archive_dll: cw-9_4 gcc-3_3-darwin intel-win32-8_1 intel-win32-9_0 mingw-3_4_2 test_set_xml_warchive: cw-8_3 cw-9_4 gcc-3_3-darwin intel-win32-8_1 intel-win32-9_0 test_set_xml_warchive_dll: cw-9_4 gcc-3_3-darwin intel-win32-8_1 intel-win32-9_0 test_shared_ptr_132_binary_archive: vc-6_5 vc-6_5-stlport test_shared_ptr_132_binary_archive_dll: vc-6_5 test_shared_ptr_132_text_archive: vc-6_5 vc-6_5-stlport test_shared_ptr_132_text_archive_dll: vc-6_5 test_shared_ptr_132_text_warchive: vc-6_5 vc-6_5-stlport test_shared_ptr_132_text_warchive_dll: vc-6_5 test_shared_ptr_132_xml_archive: vc-6_5 vc-6_5-stlport test_shared_ptr_132_xml_archive_dll: vc-6_5 test_shared_ptr_132_xml_warchive: vc-6_5 vc-6_5-stlport test_shared_ptr_132_xml_warchive_dll: vc-6_5 test_shared_ptr_binary_archive: borland-5_6_4 vc-6_5 test_shared_ptr_binary_archive_dll: borland-5_6_4 vc-6_5 test_shared_ptr_text_archive: borland-5_6_4 vc-6_5 test_shared_ptr_text_archive_dll: borland-5_6_4 vc-6_5 test_shared_ptr_text_warchive: borland-5_6_4 vc-6_5 test_shared_ptr_text_warchive_dll: borland-5_6_4 vc-6_5 test_shared_ptr_xml_archive: borland-5_6_4 vc-6_5 test_shared_ptr_xml_archive_dll: borland-5_6_4 vc-6_5 test_shared_ptr_xml_warchive: borland-5_6_4 vc-6_5 test_shared_ptr_xml_warchive_dll: borland-5_6_4 vc-6_5 test_split_text_archive: vc-7_1 test_split_text_archive_dll: vc-7_1 test_tracking_text_archive: vc-7_1 test_tracking_text_archive_dll: vc-7_1 test_unregistered_binary_archive: gcc-3.2.3-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux test_unregistered_binary_archive_dll: gcc-3.2.3-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux test_unregistered_text_archive: gcc-3.2.3-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1 test_unregistered_text_archive_dll: gcc-3.2.3-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1 test_unregistered_xml_archive: gcc-3.2.3-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux test_unregistered_xml_archive_dll: gcc-3.2.3-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux test_unregistered_xml_warchive: gcc-4.0.1-linux test_unregistered_xml_warchive_dll: gcc-4.0.1-linux |spirit| bug_000008: gcc-3_4_3-sunos grammar_mt_tests: gcc-3_4_3-sunos owi_mt_tests: gcc-3_4_3-sunos scoped_lock_tests: gcc-3_4_3-sunos scoped_lock_tests_debug: gcc-3_4_3-sunos

1 0

Boost regression notification (2005-10-11 [HEAD])
by Douglas Gregor 11 Oct '05

11 Oct '05

Boost regression test failures ------------------------------ Report time: 2005-10-11T05:00:14Z This report lists all regression test failures on release platforms. Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-HEAD/developer/issues… 333 failures in 13 libraries: concept_check (13) foreach (1) graph (2) mpl (1) parameter (13) python (4) regex (2) serialization (250) spirit (13) thread (11) tuple (1) type_traits (1) typeof (21) |concept_check| stl_concept_covering: cw-9_4 gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin intel-win32-9_0 intel-win32-9_0 mingw-3_4_2 msvc vc-7_1 |foreach| user_defined: msvc |graph| graphviz_test: vc-7_1 layout_test: intel-win32-9_0 |mpl| size_t: gcc-4_0-darwin |parameter| basics: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux efficiency: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux msvc macros: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux sfinae: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux msvc unnamed: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux vc-7_1 |python| crossmod_exception: vc-7_1 injected: vc-7_1 properties: vc-7_1 return_arg: vc-7_1 |regex| regex_regress_dll: vc-7_1 static_mutex_test: vc-7_1 |serialization| test_array_binary_archive_dll: vc-7_1 test_array_text_archive_dll: vc-7_1 test_array_text_warchive_dll: vc-7_1 test_array_xml_archive_dll: vc-7_1 test_array_xml_warchive_dll: vc-7_1 test_binary_binary_archive_dll: vc-7_1 test_binary_text_archive_dll: vc-7_1 test_binary_text_warchive_dll: vc-7_1 test_binary_xml_archive_dll: vc-7_1 test_binary_xml_warchive_dll: vc-7_1 test_class_info_load_binary_archive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_binary_archive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin vc-7_1 test_class_info_load_text_archive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_archive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin vc-7_1 test_class_info_load_text_warchive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_warchive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin vc-7_1 test_class_info_load_xml_archive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_archive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin vc-7_1 test_class_info_load_xml_warchive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_warchive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin vc-7_1 test_class_info_save_binary_archive_dll: vc-7_1 test_class_info_save_text_archive_dll: vc-7_1 test_class_info_save_text_warchive_dll: vc-7_1 test_class_info_save_xml_archive_dll: vc-7_1 test_class_info_save_xml_warchive_dll: vc-7_1 test_const_save_fail1: msvc test_const_save_fail2: msvc test_const_save_fail3: msvc test_contained_class_binary_archive_dll: vc-7_1 test_contained_class_text_archive_dll: vc-7_1 test_contained_class_text_warchive_dll: vc-7_1 test_contained_class_xml_archive_dll: vc-7_1 test_contained_class_xml_warchive_dll: vc-7_1 test_cyclic_ptrs_binary_archive_dll: vc-7_1 test_cyclic_ptrs_text_archive_dll: vc-7_1 test_cyclic_ptrs_text_warchive_dll: vc-7_1 test_cyclic_ptrs_xml_archive_dll: vc-7_1 test_cyclic_ptrs_xml_warchive_dll: vc-7_1 test_delete_pointer_binary_archive_dll: vc-7_1 test_delete_pointer_text_archive_dll: vc-7_1 test_delete_pointer_text_warchive_dll: vc-7_1 test_delete_pointer_xml_archive_dll: vc-7_1 test_delete_pointer_xml_warchive_dll: vc-7_1 test_demo_auto_ptr_dll: vc-7_1 test_demo_dll: vc-7_1 test_demo_exception_dll: vc-7_1 test_demo_fast_archive_dll: vc-7_1 test_demo_pimpl_dll: vc-7_1 test_demo_polymorphic_dll: vc-7_1 test_demo_shared_ptr_dll: vc-7_1 test_demo_xml_dll: vc-7_1 test_demo_xml_load_dll: vc-7_1 test_demo_xml_save_dll: vc-7_1 test_deque_binary_archive_dll: vc-7_1 test_deque_text_archive_dll: vc-7_1 test_deque_text_warchive_dll: vc-7_1 test_deque_xml_archive_dll: vc-7_1 test_deque_xml_warchive_dll: vc-7_1 test_derived_binary_archive_dll: vc-7_1 test_derived_class_binary_archive_dll: vc-7_1 test_derived_class_ptr_binary_archive_dll: vc-7_1 test_derived_class_ptr_text_archive_dll: vc-7_1 test_derived_class_ptr_text_warchive_dll: vc-7_1 test_derived_class_ptr_xml_archive_dll: vc-7_1 test_derived_class_ptr_xml_warchive_dll: vc-7_1 test_derived_class_text_archive_dll: vc-7_1 test_derived_class_text_warchive_dll: vc-7_1 test_derived_class_xml_archive_dll: vc-7_1 test_derived_class_xml_warchive_dll: vc-7_1 test_derived_text_archive_dll: vc-7_1 test_derived_text_warchive_dll: vc-7_1 test_derived_xml_archive_dll: vc-7_1 test_derived_xml_warchive_dll: vc-7_1 test_diamond_binary_archive_dll: vc-7_1 test_diamond_text_archive_dll: vc-7_1 test_diamond_text_warchive_dll: vc-7_1 test_diamond_xml_archive_dll: vc-7_1 test_diamond_xml_warchive_dll: vc-7_1 test_exported_binary_archive_dll: vc-7_1 test_exported_text_archive_dll: vc-7_1 test_exported_text_warchive_dll: vc-7_1 test_exported_xml_archive_dll: vc-7_1 test_exported_xml_warchive_dll: vc-7_1 test_list_binary_archive_dll: vc-7_1 test_list_ptrs_binary_archive_dll: vc-7_1 test_list_ptrs_text_archive_dll: vc-7_1 test_list_ptrs_text_warchive_dll: vc-7_1 test_list_ptrs_xml_archive_dll: vc-7_1 test_list_ptrs_xml_warchive_dll: vc-7_1 test_list_text_archive_dll: vc-7_1 test_list_text_warchive_dll: vc-7_1 test_list_xml_archive_dll: vc-7_1 test_list_xml_warchive_dll: vc-7_1 test_map_binary_archive_dll: msvc vc-7_1 test_map_text_archive_dll: msvc vc-7_1 test_map_text_warchive_dll: msvc vc-7_1 test_map_xml_archive_dll: vc-7_1 test_map_xml_warchive_dll: vc-7_1 test_mi_binary_archive_dll: vc-7_1 test_mi_text_archive_dll: vc-7_1 test_mi_text_warchive_dll: vc-7_1 test_mi_xml_archive_dll: vc-7_1 test_mi_xml_warchive_dll: vc-7_1 test_mult_archive_types_dll: vc-7_1 test_multiple_ptrs_binary_archive_dll: vc-7_1 test_multiple_ptrs_text_archive_dll: vc-7_1 test_multiple_ptrs_text_warchive_dll: vc-7_1 test_multiple_ptrs_xml_archive_dll: vc-7_1 test_multiple_ptrs_xml_warchive_dll: vc-7_1 test_no_rtti_binary_archive_dll: vc-7_1 test_no_rtti_text_archive_dll: vc-7_1 test_no_rtti_text_warchive_dll: vc-7_1 test_no_rtti_xml_archive_dll: vc-7_1 test_no_rtti_xml_warchive_dll: vc-7_1 test_non_default_ctor2_binary_archive_dll: vc-7_1 test_non_default_ctor2_text_archive_dll: vc-7_1 test_non_default_ctor2_text_warchive_dll: vc-7_1 test_non_default_ctor2_xml_archive_dll: vc-7_1 test_non_default_ctor2_xml_warchive_dll: vc-7_1 test_non_default_ctor_binary_archive_dll: vc-7_1 test_non_default_ctor_text_archive_dll: vc-7_1 test_non_default_ctor_text_warchive_dll: vc-7_1 test_non_default_ctor_xml_archive_dll: vc-7_1 test_non_default_ctor_xml_warchive_dll: vc-7_1 test_non_intrusive_binary_archive_dll: vc-7_1 test_non_intrusive_text_archive_dll: vc-7_1 test_non_intrusive_text_warchive_dll: vc-7_1 test_non_intrusive_xml_archive_dll: vc-7_1 test_non_intrusive_xml_warchive_dll: vc-7_1 test_null_ptr_binary_archive_dll: vc-7_1 test_null_ptr_text_archive_dll: vc-7_1 test_null_ptr_text_warchive_dll: vc-7_1 test_null_ptr_xml_archive_dll: vc-7_1 test_null_ptr_xml_warchive_dll: vc-7_1 test_nvp_binary_archive_dll: vc-7_1 test_nvp_text_archive_dll: vc-7_1 test_nvp_text_warchive_dll: vc-7_1 test_nvp_xml_archive_dll: vc-7_1 test_nvp_xml_warchive_dll: vc-7_1 test_object_binary_archive_dll: vc-7_1 test_object_text_archive_dll: vc-7_1 test_object_text_warchive_dll: vc-7_1 test_object_xml_archive_dll: vc-7_1 test_object_xml_warchive_dll: vc-7_1 test_optional_binary_archive_dll: vc-7_1 test_optional_text_archive_dll: vc-7_1 test_optional_text_warchive_dll: vc-7_1 test_optional_xml_archive_dll: vc-7_1 test_optional_xml_warchive_dll: vc-7_1 test_polymorphic_binary_archive_dll: vc-7_1 test_polymorphic_text_archive_dll: vc-7_1 test_polymorphic_text_warchive_dll: vc-7_1 test_polymorphic_xml_archive_dll: vc-7_1 test_polymorphic_xml_warchive_dll: vc-7_1 test_primitive_binary_archive_dll: vc-7_1 test_primitive_text_archive_dll: vc-7_1 test_primitive_text_warchive_dll: vc-7_1 test_primitive_xml_archive_dll: vc-7_1 test_primitive_xml_warchive_dll: vc-7_1 test_private_ctor_dll: vc-7_1 test_recursion_binary_archive_dll: vc-7_1 test_recursion_text_archive_dll: vc-7_1 test_recursion_text_warchive_dll: vc-7_1 test_recursion_xml_archive_dll: vc-7_1 test_recursion_xml_warchive_dll: vc-7_1 test_registered_binary_archive_dll: vc-7_1 test_registered_text_archive_dll: vc-7_1 test_registered_text_warchive_dll: vc-7_1 test_registered_xml_archive_dll: vc-7_1 test_registered_xml_warchive_dll: vc-7_1 test_reset_object_address_dll: vc-7_1 test_set_binary_archive_dll: vc-7_1 test_set_text_archive_dll: vc-7_1 test_set_text_warchive_dll: vc-7_1 test_set_xml_archive_dll: vc-7_1 test_set_xml_warchive_dll: vc-7_1 test_shared_ptr_132_binary_archive_dll: vc-7_1 test_shared_ptr_132_text_archive_dll: vc-7_1 test_shared_ptr_132_text_warchive_dll: vc-7_1 test_shared_ptr_132_xml_archive_dll: vc-7_1 test_shared_ptr_132_xml_warchive_dll: vc-7_1 test_shared_ptr_binary_archive_dll: vc-7_1 test_shared_ptr_text_archive_dll: vc-7_1 test_shared_ptr_text_warchive_dll: vc-7_1 test_shared_ptr_xml_archive_dll: vc-7_1 test_shared_ptr_xml_warchive_dll: vc-7_1 test_simple_class_binary_archive_dll: vc-7_1 test_simple_class_ptr_binary_archive_dll: vc-7_1 test_simple_class_ptr_text_archive_dll: vc-7_1 test_simple_class_ptr_text_warchive_dll: vc-7_1 test_simple_class_ptr_xml_archive_dll: vc-7_1 test_simple_class_ptr_xml_warchive_dll: vc-7_1 test_simple_class_text_archive_dll: vc-7_1 test_simple_class_text_warchive_dll: vc-7_1 test_simple_class_xml_archive_dll: vc-7_1 test_simple_class_xml_warchive_dll: vc-7_1 test_split_binary_archive_dll: vc-7_1 test_split_text_archive_dll: vc-7_1 test_split_text_warchive_dll: vc-7_1 test_split_xml_archive_dll: vc-7_1 test_split_xml_warchive_dll: vc-7_1 test_tracking_binary_archive_dll: vc-7_1 test_tracking_text_archive_dll: vc-7_1 test_tracking_text_warchive_dll: vc-7_1 test_tracking_xml_archive_dll: vc-7_1 test_tracking_xml_warchive_dll: vc-7_1 test_unregistered_binary_archive_dll: vc-7_1 test_unregistered_text_archive_dll: vc-7_1 test_unregistered_text_warchive_dll: vc-7_1 test_unregistered_xml_archive_dll: vc-7_1 test_unregistered_xml_warchive_dll: vc-7_1 test_variant_binary_archive_dll: vc-7_1 test_variant_text_archive_dll: vc-7_1 test_variant_text_warchive_dll: vc-7_1 test_variant_xml_archive_dll: vc-7_1 test_variant_xml_warchive_dll: vc-7_1 test_vector_binary_archive_dll: vc-7_1 test_vector_text_archive_dll: vc-7_1 test_vector_text_warchive_dll: vc-7_1 test_vector_xml_archive_dll: vc-7_1 test_vector_xml_warchive_dll: vc-7_1 test_void_cast_dll: vc-7_1 |spirit| action_tests_debug: gcc-3_4_3-sunos bug_000008: vc-7_1 distinct_tests_debug: gcc-3_4_3-sunos escape_char_parser_tests_debug: gcc-3_4_3-sunos grammar_def_test_debug: gcc-3_4_3-sunos grammar_mt_tests: vc-7_1 owi_mt_tests: vc-7_1 scoped_lock_tests: vc-7_1 scoped_lock_tests_debug: vc-7_1 switch_problem_debug: gcc-3_4_3-sunos switch_tests_single_debug: gcc-3_4_3-sunos traverse_tests: intel-win32-9_0 traverse_tests_debug: intel-win32-9_0 |thread| test_barrier: vc-7_1 test_condition: gcc-3_4_3-sunos vc-7_1 test_mutex: gcc-3_4_3-sunos vc-7_1 test_once: vc-7_1 test_read_write_mutex: vc-7_1 test_tss: gcc-3_4_3-sunos gcc-3_4_3-sunos vc-7_1 test_xtime: vc-7_1 |tuple| tuple_test_bench: gcc-3_4_3-sunos |type_traits| tricky_abstract_type_test: intel-win32-9_0 |typeof| data_member_native: cw-9_4 function_native: cw-9_4 msvc function_ptr_native: cw-9_4 function_ref_native: cw-9_4 lvalue_native: cw-9_4 msvc member_function_native: cw-9_4 modifiers_emulation: cw-9_4 modifiers_native: cw-9_4 noncopyable_native: cw-9_4 std_emulation: cw-9_4 std_native: cw-9_4 template_dependent_native: cw-9_4 template_enum_native: cw-9_4 template_int_native: cw-9_4 template_multiword_native: cw-9_4 template_tpl_native: cw-9_4 msvc template_type_native: cw-9_4 type_native: cw-9_4

1 0

[parameter] BOOST_PARAMETER_KEYWORD does not put identifiers in anonymous namespace.
by Martin Wille 11 Oct '05

11 Oct '05

Hi, the tutorial says: The declaration of the visitor keyword you see here is equivalent to: namespace graphs { namespace tag { struct visitor; } namespace { boost::parameter::keyword<tag::visitor>& visitor = boost::parameter::keyword<tag::visitor>::get(); } } However, BOOST_PARAMETER_KEYWORD(tag, visitor) expands to namespace tag { struct visitor; } ::boost::parameter::keyword<tag::visitor>& visitor = ::boost::parameter::keyword<tag::visitor>::get(); Regards, m Send instant messages to your online friends http://au.messenger.yahoo.com

2 2

Re: [boost] Boost regression notification (2005-10-06 [RC_1_33_0])
by Jonathan Wakely 11 Oct '05

11 Oct '05

(re-sending as the server that hosts this mail account rebooted as I sent the mail and it hasn't shown up in the archives yet ...) Martin Wille wrote: > Arkadiy Vertleyb wrote: > > "Douglas Gregor" <doug.gregor(a)gmail.com> wrote > > > > > >>>Is GCC's debug > >>>mode > >>>a release-critical platform ? > >> > >>No. > > > > > > How can this be? How useful is a feature that can be used in the release > > mode oinly? I think its usefullness is pretty close to zero... > I agree with your questioning, Arkadiy. I completely fail to understand the question. The debug mode cannot be used in "release mode" because it makes the stdlib non-conforming. It's useful for tracking down problems in your code, and as such is immensely useful, but it's not meant for production code in "release mode" What do you mean "a feature that can be used in the release mode only" ? > People will want to use the debug mode. It's probably the best thing > added to recent libstdc++ distributions. Severals bugs in Boost code > were discovered using _GLIBCXX_DEBUG. I'd consider it a big loss not to > be able to use it anymore. I'm not saying "you can't use it anymore" - just that the Boost release shouldn't be held up by debug-mode failures that don't affect any major platforms in their normal configuration. If you're willing, try running the tests with libstdc++ concept-checks enabled as well (#define _GLIBCXX_CONCEPT_CHECKS) and then let me know if you think the release should be held up for those bugs too. Personally I think they're more important than the debug-mode failures, since it's possible to configure GCC so that concept-checks are enabled by default, making parts of Boost unusable. But debug mode is always off by default. jon

5 9

Re: [boost] Boost Digest, Vol 1241, Issue 4
by Jared McIntyre 11 Oct '05

11 Oct '05

> Double check that a is polymorphic - that is, that it has at least one > virtual function. Then get back to us. Yup, the destructors are virtual (and dynamic_cast is working in both directions). However, it works now (see later comment). > nope, its correct. This is a little known quirk of C++ syntax. Your second > version won't compile on the most conforming compilers. Nifty. I swear that didn't compile when I used it on Friday, but now it does. Now that I have changed it to that format, ar.template register_type<derived_one>(), it works. Out of curiosity, what is the difference between calling it that way and calling ar.register_type<derived_one>()? I've not seen that type of format and would be interested in learning more about it. Thanks again, Jared

3 3

Boost regression notification (2005-10-10 [RC_1_33_0])
by Douglas Gregor 11 Oct '05

11 Oct '05

Boost regression test failures ------------------------------ Report time: 2005-10-10T14:07:23Z This report lists all regression test failures on release platforms. Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-RC_1_33_0/developer/i… 217 failures in 5 libraries: graph (1) iostreams (1) range (3) serialization (207) spirit (5) |graph| graphviz_test: cw-9_4 |iostreams| gzip_test: gcc-4_0-darwin |range| array: vc-6_5 vc-6_5-stlport vc-7_0 |serialization| test_binary_text_archive: vc-7_1 test_binary_text_archive_dll: vc-7_1 test_class_info_save_text_archive: vc-7_1 test_class_info_save_text_archive_dll: vc-7_1 test_demo_polymorphic: gcc-3_3-darwin gcc-3_4_3-sunos vc-7_1 test_demo_polymorphic_dll: gcc-3_3-darwin gcc-3_4_3-sunos vc-7_1 test_demo_xml_load: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin intel-win32-8_1 test_demo_xml_load_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_derived_text_archive: vc-7_1 test_derived_text_archive_dll: vc-7_1 test_diamond_binary_archive: gcc-3_3-darwin test_diamond_binary_archive_dll: gcc-3_3-darwin test_diamond_text_archive: gcc-3_3-darwin test_diamond_text_archive_dll: gcc-3_3-darwin test_diamond_text_warchive: gcc-3_3-darwin test_diamond_text_warchive_dll: gcc-3_3-darwin test_diamond_xml_archive: gcc-3_3-darwin test_diamond_xml_archive_dll: gcc-3_3-darwin test_diamond_xml_warchive: gcc-3_3-darwin test_diamond_xml_warchive_dll: gcc-3_3-darwin test_exported_binary_archive: gcc-3.2.3-linux gcc-4.0.1-linux intel-9.0-linux vc-6_5 test_exported_binary_archive_dll: gcc-4.0.1-linux vc-6_5 test_exported_text_archive: gcc-3.2.3-linux gcc-4.0.1-linux vc-6_5 vc-7_1 test_exported_text_archive_dll: gcc-3.2.3-linux gcc-4.0.1-linux vc-6_5 vc-7_1 test_exported_text_warchive: gcc-4.0.1-linux vc-6_5 test_exported_text_warchive_dll: gcc-4.0.1-linux vc-6_5 test_exported_xml_archive: gcc-4.0.1-linux intel-8.1-linux vc-6_5 test_exported_xml_archive_dll: gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-6_5 test_exported_xml_warchive: gcc-3.2.3-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-6_5 test_exported_xml_warchive_dll: gcc-3.2.3-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-6_5 test_map_binary_archive: gcc-3_3-darwin test_map_binary_archive_dll: gcc-3_3-darwin test_map_text_archive: gcc-3_3-darwin test_map_text_archive_dll: gcc-3_3-darwin test_map_text_warchive: gcc-3_3-darwin test_map_text_warchive_dll: gcc-3_3-darwin test_map_xml_archive: gcc-3_3-darwin test_map_xml_archive_dll: gcc-3_3-darwin test_map_xml_warchive: gcc-3_3-darwin test_map_xml_warchive_dll: gcc-3_3-darwin test_mi_text_archive: vc-7_1 test_mi_text_archive_dll: vc-7_1 test_no_rtti_binary_archive: vc-6_5 test_no_rtti_binary_archive_dll: vc-6_5 test_no_rtti_text_archive: vc-6_5 test_no_rtti_text_archive_dll: vc-6_5 test_no_rtti_text_warchive: vc-6_5 test_no_rtti_text_warchive_dll: vc-6_5 test_no_rtti_xml_archive: vc-6_5 test_no_rtti_xml_archive_dll: vc-6_5 test_no_rtti_xml_warchive: vc-6_5 test_no_rtti_xml_warchive_dll: vc-6_5 test_non_default_ctor2_text_archive: vc-7_1 test_non_default_ctor2_text_archive_dll: vc-7_1 test_non_default_ctor_text_archive: vc-7_1 test_non_default_ctor_text_archive_dll: vc-7_1 test_non_intrusive_text_archive: vc-7_1 test_non_intrusive_text_archive_dll: vc-7_1 test_null_ptr_text_archive: vc-7_1 test_null_ptr_text_archive_dll: vc-7_1 test_object_text_archive: vc-7_1 test_object_text_archive_dll: vc-7_1 test_polymorphic_binary_archive: gcc-3_3-darwin gcc-3_4_3-sunos vc-7_1 test_polymorphic_binary_archive_dll: gcc-3_3-darwin gcc-3_4_3-sunos vc-7_1 test_polymorphic_text_archive: gcc-3_3-darwin gcc-3_4_3-sunos vc-7_1 test_polymorphic_text_archive_dll: gcc-3_3-darwin gcc-3_4_3-sunos vc-7_1 test_polymorphic_text_warchive: gcc-3_3-darwin gcc-3_4_3-sunos vc-7_1 test_polymorphic_text_warchive_dll: gcc-3_3-darwin gcc-3_4_3-sunos vc-7_1 test_polymorphic_xml_archive: gcc-3_3-darwin gcc-3_4_3-sunos vc-7_1 test_polymorphic_xml_archive_dll: gcc-3_3-darwin gcc-3_4_3-sunos vc-7_1 test_polymorphic_xml_warchive: gcc-3_3-darwin gcc-3_4_3-sunos vc-7_1 test_polymorphic_xml_warchive_dll: gcc-3_3-darwin gcc-3_4_3-sunos vc-7_1 test_primitive_text_archive: vc-7_1 test_primitive_text_archive_dll: vc-7_1 test_registered_text_archive: vc-7_1 test_registered_text_archive_dll: vc-7_1 test_set_binary_archive: gcc-3_3-darwin test_set_binary_archive_dll: gcc-3_3-darwin test_set_text_archive: gcc-3_3-darwin test_set_text_archive_dll: gcc-3_3-darwin test_set_text_warchive: gcc-3_3-darwin test_set_text_warchive_dll: gcc-3_3-darwin test_set_xml_archive: gcc-3_3-darwin test_set_xml_archive_dll: gcc-3_3-darwin test_set_xml_warchive: gcc-3_3-darwin test_set_xml_warchive_dll: gcc-3_3-darwin test_shared_ptr_132_binary_archive: vc-6_5 vc-6_5-stlport test_shared_ptr_132_binary_archive_dll: vc-6_5 test_shared_ptr_132_text_archive: vc-6_5 vc-6_5-stlport test_shared_ptr_132_text_archive_dll: vc-6_5 test_shared_ptr_132_text_warchive: vc-6_5 vc-6_5-stlport test_shared_ptr_132_text_warchive_dll: vc-6_5 test_shared_ptr_132_xml_archive: vc-6_5 vc-6_5-stlport test_shared_ptr_132_xml_archive_dll: vc-6_5 test_shared_ptr_132_xml_warchive: vc-6_5 vc-6_5-stlport test_shared_ptr_132_xml_warchive_dll: vc-6_5 test_shared_ptr_binary_archive: borland-5_6_4 vc-6_5 test_shared_ptr_binary_archive_dll: borland-5_6_4 vc-6_5 test_shared_ptr_text_archive: borland-5_6_4 vc-6_5 test_shared_ptr_text_archive_dll: borland-5_6_4 vc-6_5 test_shared_ptr_text_warchive: borland-5_6_4 vc-6_5 test_shared_ptr_text_warchive_dll: borland-5_6_4 vc-6_5 test_shared_ptr_xml_archive: borland-5_6_4 vc-6_5 test_shared_ptr_xml_archive_dll: borland-5_6_4 vc-6_5 test_shared_ptr_xml_warchive: borland-5_6_4 vc-6_5 test_shared_ptr_xml_warchive_dll: borland-5_6_4 vc-6_5 test_split_text_archive: vc-7_1 test_split_text_archive_dll: vc-7_1 test_tracking_text_archive: vc-7_1 test_tracking_text_archive_dll: vc-7_1 test_unregistered_binary_archive: gcc-3.2.3-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux test_unregistered_binary_archive_dll: gcc-3.2.3-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux test_unregistered_text_archive: gcc-3.2.3-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1 test_unregistered_text_archive_dll: gcc-3.2.3-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1 test_unregistered_xml_archive: gcc-3.2.3-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux test_unregistered_xml_archive_dll: gcc-3.2.3-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux test_unregistered_xml_warchive: gcc-4.0.1-linux test_unregistered_xml_warchive_dll: gcc-4.0.1-linux |spirit| bug_000008: gcc-3_4_3-sunos grammar_mt_tests: gcc-3_4_3-sunos owi_mt_tests: gcc-3_4_3-sunos scoped_lock_tests: gcc-3_4_3-sunos scoped_lock_tests_debug: gcc-3_4_3-sunos

5 7

[Serialization] Major regressions on RC_1_33_0
by Douglas Gregor 11 Oct '05

11 Oct '05

The last round of changes to the Serialization library have caused major regressions (205, to be precise) on the RC_1_33_0 branch. If these regressions have not been fixed by Monday morning I will revert these changes automatically. Doug

6 16

BOOST_AUTO_TEST_CASE(tweak)
by troy d. straszheim 11 Oct '05

11 Oct '05

Something minor. The code: BOOST_UNIT_TEST_CASE(something) { ... } expands to struct something_id {}; static void something(); static boost::unit_test::ut_detail::auto_test_unit_registrar something_registrar( boost::unit_test::make_test_case( boost::unit_test::callback0<>(something), boost::unit_test::literal_string( "something", sizeof( "something" ) - 1 ) ), boost::unit_test::ut_detail::auto_tc_exp_fail< something_id>::value ); static void something() { ... } And if you're testing, say, smart_cast of something, you might naturally code (as I just did) BOOST_UNIT_TEST_CASE(smart_cast) { ... } which will contain static void smart_cast() and you'll get a fairly cryptic error, test_smart_cast.cpp:198: error: no matching function for call to 'boost::unit_test::callback0<boost::unit_test::ut_detail::unused>::callback0(<unknown type>)' The docs specify that > To use automatic registration facility you need to define a test case > as a zero arity free function, but instead of usual void tc_name(), > use following statement > > BOOST_AUTO_UNIT_TEST( tc_name ) > > BOOST_TEST_CASE hides all the machinery used to implement automatic > registration. The only requirements are that test case names are > unique within compilation unit and no two test case definition are > located on the same line. Which I didn't see until just now. The context implies that tc_name must be a valid function name, so I guess there's no problem. But it does seem a little redundant to write BOOST_AUTO_TEST_CASE(test_of_smart_cast) { ... } as it's clear you're writing a test. I had assumed the static function were instead named test_case_smart_cast() and hidden in a namespace, something like namespace boost::unit_test::ut_detail::user_tests { struct test_case_smart_cast_id {}; void test_case_smart_cast(); } [etc., etc.] void boost::unit_test::ut_detail::user_tests::test_case_smart_cast() { ... } for added safety against name collisions, as one sees in, e.g., boost::python: # define BOOST_PYTHON_MODULE_INIT(name) \ void init_module_##name(); \ Anyhow, just thinking out loud, not trying to nitpick. I also noticed that the header file auto_unit_test.hpp shows // deprecated #define BOOST_AUTO_UNIT_TEST( f ) BOOST_AUTO_TEST_CASE( f ) so the example in the docs uses the deprecated interface. Just FYI. Thanks for a very handy testing lib, -t

2 1

Re: [boost] [hash] documentation issues (was [TR1 Review] TR1 Formal Review Beginning)
by Alexander Nasonov 11 Oct '05

11 Oct '05

Daniel James wrote: > Alexander Nasonov wrote: >> 2. Adding new has_value may have side effects, for example, (a) hash<T> may >> compile for not customized type T although T doesn't necesarily have >> properly defined equality function; or (b) it may introduce overload >> resolution ambiguities, in worst case, hash<type_from_6_3_3_1> may stop >> working. > > I don't think this is nearly as bad as you think. Any type from TR1 will > only stop working if you declare hash_value in the boost or std > namespace - which you really shouldn't do. You are right. I was a way too pessimistic. > If a type has a hash_value function but no equality then boost::hash > will compile for it - but a hashed container won't, because it will > require the equality function. So the only time will boost::hash will > work is if it's used in another context where equality isn't required. That's not quite right. For example #include <iostream> #include <boost/functional/hash.hpp> struct Base { bool operator==(Base) const { return true; } }; std::size_t hash_value(Base) { return 0; // Base has no state } struct Derived : Base { int dummy; bool operator==(Derived other) const { return dummy == other.dummy; } }; int main() { Derived x; std::cout << boost::hash<Derived>()(x) << '\n'; } -- Alexander Nasonov

5 9

Any interest? complex_utils
by Neal Becker 11 Oct '05

11 Oct '05

I have uploaded a few complex number utilities to boost vault under Math-Numerics/complex-util.tar.gz. Included are 3 kinds of iterator adapters and a test program. Is there interest in further development of this as part of math/numerics library? (I use these myself all the time) If so, there will probably also be a few other small utilities.

3 2

Re: [boost] GUI coordinate units (Was: GUI foundations)
by brangdon＠cix.compulink.co.uk 10 Oct '05

10 Oct '05

In-Reply-To: <dic90t$l4e$1(a)sea.gmane.org> joel(a)boost-consulting.com (Joel de Guzman) wrote (abridged): > Sure they do text. I didn't say they didn't. I just said I didn't find any documentation on it. -- Dave Harris, Nottingham, UK.

2 1

Re: [boost] Interest in dimension/unit-checking library?
by Schrom, Brian T 10 Oct '05

10 Oct '05

I also agree. I find that I was starting to invent some of this in my chart library and a generic, complete solution would be wonderful to use in that context. > <big snip> > >Please to learn that work is still done - IMO we still badly need a good solution to the ubiquitous (but hard) problem of units & dimensions. > >Paul

1 0

serialization problem with binary archives on v1.33
by Keith McNeill 10 Oct '05

10 Oct '05

We are trying to upgrade from boost 1.31 (+ compaitable serialization) to boost v1.33. We have one particular test that is failing with what looks like serialization deserialing a bad pointer. In particular the bad pointer is the 3rd instance reference of a particular object. The 1st & 2nd deserialize fine the 3rd is bogus. This is code that works fine on 1.31 both binary & text mode. It works in 1.33 text mode, but fails in 1.33 binary mode. What is the best way to debug this problem? Is there anyway to inspect the binary archive to printout the contents...at least the pointers/addresses contained in the archive? I haven't been able to get it down to a simple test case (it is part of a large system). I could send out the binary and text archive if that would help. This is using g++ 3.3.4 on FC3 (32bit) & Also 3.3.4 on Red Hat Enterprise v3 on a 64bit platform. Keith mcneill(a)streambase.com

2 3

Re: [boost] BOOST_ASSERT and __assume on MSVC
by brangdon＠cix.compulink.co.uk 10 Oct '05

10 Oct '05

In-Reply-To: <4343103A.6010007(a)dcook.org> darren(a)dcook.org (Darren Cook) wrote (abridged): > I think it is fair to assume people don't have assert(false) in code > that is ready for release - it is just used temporarily during > debugging. No, it isn't fair to assume that. I have: if (e) { assert(false); throw "can't happen"; } or similar in release code. > But just to be sure OKAY_TO_USE_ASSUME should be off by default. A single monolithic switch isn't practical. There is no way to switch OKAY_TO_USE_ASSUME on without first checking whether every piece of code in the program is OK with it. > > If that is the behavior of __assume(false), or at least given > > that it is a reasonable interpretation of what it could do, then > > including __assume() in BOOST_ASSERT() seems a little dangerous. > > Which brings up back to the start of this thread :-). Quite so. I find I am repeating myself. -- Dave Harris, Nottingham, UK.

5 7

Re: [boost] BOOST_ASSERT and __assume on MSVC
by brangdon＠cix.compulink.co.uk 10 Oct '05

10 Oct '05

In-Reply-To: <4349965D.5030005(a)ezequal.com> chaos(a)ezequal.com (Jason Hise) wrote (abridged): > Isn't that an abuse of assert? No. The behaviour is well defined. > Why do you need both types of checks in the same place? To repeat what I said in my first post in this thread: Although I sympathise with the view that a failed assert should be considered undefined behaviour, I personally find the current documented behaviour quite useful. I sometimes use assert as a convenient way of saying, "issue a warning message, but only in debug builds." -- Dave Harris, Nottingham, UK.

1 0

Re: [boost] About timedlock....
by Jon Kalb 10 Oct '05

10 Oct '05

> -----Original Message----- > From: boost-bounces(a)lists.boost.org > [mailto:boost-bounces@lists.boost.org] On Behalf Of Arkadiy Vertleyb > Sent: Friday, October 07, 2005 8:52 AM > To: boost(a)lists.boost.org > Subject: Re: [boost] About timedlock.... > > "David Abrahams" <dave(a)boost-consulting.com> wrote > > > "Boost" <u0086000(a)cc.ncu.edu.tw> writes: > > > > > Hi, > > > > Please identify yourself appropriately. You do not represent Boost. > > If you insist on it, a different pseudonym is acceptable if > you intend > > to use it consistently in this forum. In our culture, though, > > individuals are generally known by their real names. > > According to Yahoo, there are 33 people in just the US whose > last name is "Boost" (unfortunately the search by the first > name is not possible). What happens if one of them > subscribes to this mailing list? > > ;-) > > Regards > Arkadiy They'll be asked to identify themselves by their first and last names. This will work until one of them names their son (or daughter) Org (or Moderator :-). > Regards > Boost, Org -- Jon Kalb

1 0

[Preprocessor] How to get the size of a tuple using variadic macros
by Yao Zhen 10 Oct '05

10 Oct '05

I am aware that variadic macros are not in the current C++ standard. However, it is declared that "the C++ standardization committee is likely to adopt C99's preprocessor extensions for the next version of the C++ standard." So here is a question about it. I have though that with the help of variadic macros, it would be nolonger necessary for us to povide size of preprocessor tuples manually. For instance, in fact it is easy to implement the BOOST_PP_TUPLE_ELEM macro more clearly as: #define TUPLE_ELEM(i, tuple) TUPLE_ELEM_ ## i tuple #define TUPLE_ELEM_0(a0, ...) a0 #define TUPLE_ELEM_1(a0, a1, ...) a1 #define TUPLE_ELEM_2(a0, a1, a2, ...) a2 #define TUPLE_ELEM_3(a0, a1, a2, a3, ...) a3 However, I failed to think out a way to implement TUPLE_SIZE. Is there any way to do this? If the answer is yes, it will be possible to eliminate all the manually specified size argument of all tuple manipulation macros. That would be a great news for preprocessor metaprogramming. Best regards, Zhen -- USTC Alumni Email System

2 1

[program_options] gcc 4.0.2 (cygwin) DLL tests
by David Abrahams 10 Oct '05

10 Oct '05

positional_options_test_dll and cmdline_test_dll seem to run forever and use unlimited memory. -- Dave Abrahams Boost Consulting www.boost-consulting.com

1 0

Boost regression notification (2005-10-10 [HEAD])
by Douglas Gregor 10 Oct '05

10 Oct '05

Boost regression test failures ------------------------------ Report time: 2005-10-10T05:00:26Z This report lists all regression test failures on release platforms. Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-HEAD/developer/issues… 103 failures in 10 libraries: concept_check (13) foreach (1) graph (2) mpl (1) parameter (13) serialization (39) spirit (8) thread (4) tuple (1) typeof (21) |concept_check| stl_concept_covering: cw-9_4 gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin intel-win32-9_0 intel-win32-9_0 mingw-3_4_2 msvc vc-7_1 |foreach| user_defined: msvc |graph| graphviz_test: vc-7_1 layout_test: intel-win32-9_0 |mpl| size_t: gcc-4_0-darwin |parameter| basics: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux efficiency: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux msvc macros: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux sfinae: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux msvc unnamed: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux vc-7_1 |serialization| test_class_info_load_binary_archive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_binary_archive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_archive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_archive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_warchive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_warchive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_archive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_archive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_warchive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_warchive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_const_save_fail1: msvc test_const_save_fail2: msvc test_const_save_fail3: msvc test_map_binary_archive_dll: msvc test_map_text_archive_dll: msvc test_map_text_warchive_dll: msvc test_non_default_ctor_binary_archive: vc-7_1 test_non_default_ctor_text_warchive: vc-7_1 test_null_ptr_xml_warchive_dll: vc-7_1 |spirit| action_tests_debug: gcc-3_4_3-sunos distinct_tests_debug: gcc-3_4_3-sunos escape_char_parser_tests_debug: gcc-3_4_3-sunos grammar_def_test_debug: gcc-3_4_3-sunos switch_problem_debug: gcc-3_4_3-sunos switch_tests_single_debug: gcc-3_4_3-sunos traverse_tests: intel-win32-9_0 traverse_tests_debug: intel-win32-9_0 |thread| test_condition: gcc-3_4_3-sunos test_mutex: gcc-3_4_3-sunos test_tss: gcc-3_4_3-sunos gcc-3_4_3-sunos |tuple| tuple_test_bench: gcc-3_4_3-sunos |typeof| data_member_native: cw-9_4 function_native: cw-9_4 msvc function_ptr_native: cw-9_4 function_ref_native: cw-9_4 lvalue_native: cw-9_4 msvc member_function_native: cw-9_4 modifiers_emulation: cw-9_4 modifiers_native: cw-9_4 noncopyable_native: cw-9_4 std_emulation: cw-9_4 std_native: cw-9_4 template_dependent_native: cw-9_4 template_enum_native: cw-9_4 template_int_native: cw-9_4 template_multiword_native: cw-9_4 template_tpl_native: cw-9_4 msvc template_type_native: cw-9_4 type_native: cw-9_4

1 0

[spirit][1.33.1] regressions and a fix
by John Maddock 10 Oct '05

10 Oct '05

The new spirit regressions for 1.33.1 here: http://engineering.meta-comm.com/boost-regression/CVS-RC_1_33_0/developer/i… appear to be caused by a conflict between the Jamfile and the BUILD environment variable. They're easily fixed with the following patch (tested on Windows only): RCS file: /cvsroot/boost/boost/libs/spirit/test/Jamfile,v retrieving revision 1.35 diff -r1.35 Jamfile 78c78 < template multi-threading : : : --- > template multi-threading : : 85c85 < template multi-threading : <dll>@boost/libs/thread/build/boost_thread : : --- > template multi-threading : <dll>@boost/libs/thread/build/boost_thread > : 92c92 < template normal : : : --- > template normal : : OK to commit? John.

2 2

Boost regression notification (2005-10-06 [RC_1_33_0])
by Douglas Gregor 10 Oct '05

10 Oct '05

Boost regression test failures ------------------------------ Report time: 2005-10-06T15:24:21Z This report lists all regression test failures on release platforms. Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-RC_1_33_0/developer/i… 228 failures in 7 libraries: foreach (1) graph (2) iostreams (13) multi_index (1) range (3) serialization (202) wave (6) |foreach| rvalue_const: vc-7_1 |graph| graphviz_test: cw-8_3 cw-9_4 |iostreams| gzip_test: cw-9_5-darwin gcc-2.95.3-stlport-4.6.2-linux gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin gcc-3_4_3-sunos gcc-4.0.1-linux gcc-4_0-darwin intel-8.1-linux intel-9.0-linux mingw-3_4_2 vc-7_1 |multi_index| test_serialization: cw-9_5-darwin |range| array: vc-6_5 vc-6_5-stlport vc-7_0 |serialization| test_binary_text_archive: vc-7_1 test_binary_text_archive_dll: vc-7_1 test_class_info_save_text_archive: vc-7_1 test_class_info_save_text_archive_dll: vc-7_1 test_delete_pointer_binary_archive: cw-9_5-darwin test_delete_pointer_binary_archive_dll: cw-9_5-darwin test_delete_pointer_text_archive: cw-9_5-darwin test_delete_pointer_text_warchive: cw-9_5-darwin test_delete_pointer_xml_archive: cw-9_5-darwin test_delete_pointer_xml_warchive: cw-9_5-darwin test_demo_polymorphic: cw-9_5-darwin test_demo_xml_load: gcc-3_3-darwin gcc-4_0-darwin intel-win32-8_1 test_demo_xml_load_dll: gcc-3_3-darwin gcc-4_0-darwin test_deque_binary_archive: cw-9_5-darwin test_deque_binary_archive_dll: cw-9_5-darwin test_deque_text_archive: cw-9_5-darwin test_deque_text_warchive: cw-9_5-darwin test_deque_xml_archive: cw-9_5-darwin test_deque_xml_warchive: cw-9_5-darwin test_derived_text_archive: vc-7_1 test_derived_text_archive_dll: vc-7_1 test_exported_binary_archive: gcc-3.2.3-linux gcc-4.0.1-linux intel-9.0-linux vc-6_5 test_exported_binary_archive_dll: gcc-4.0.1-linux vc-6_5 test_exported_text_archive: gcc-3.2.3-linux gcc-4.0.1-linux vc-6_5 vc-7_1 test_exported_text_archive_dll: gcc-3.2.3-linux gcc-4.0.1-linux vc-6_5 vc-7_1 test_exported_text_warchive: gcc-4.0.1-linux vc-6_5 test_exported_text_warchive_dll: gcc-4.0.1-linux vc-6_5 test_exported_xml_archive: gcc-4.0.1-linux intel-8.1-linux vc-6_5 test_exported_xml_archive_dll: gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-6_5 test_exported_xml_warchive: gcc-3.2.3-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-6_5 test_exported_xml_warchive_dll: gcc-3.2.3-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-6_5 test_list_binary_archive: cw-9_5-darwin test_list_binary_archive_dll: cw-9_5-darwin test_list_ptrs_binary_archive: cw-9_5-darwin test_list_ptrs_binary_archive_dll: cw-9_5-darwin test_list_ptrs_text_archive: cw-9_5-darwin test_list_ptrs_text_warchive: cw-9_5-darwin test_list_ptrs_xml_archive: cw-9_5-darwin test_list_ptrs_xml_warchive: cw-9_5-darwin test_list_ptrs_xml_warchive_dll: gcc-3_4_3-sunos test_list_text_archive: cw-9_5-darwin test_list_text_warchive: cw-9_5-darwin test_list_xml_archive: cw-9_5-darwin test_list_xml_warchive: cw-9_5-darwin test_map_binary_archive: cw-9_5-darwin test_map_binary_archive_dll: cw-9_5-darwin test_map_text_archive: cw-9_5-darwin gcc-3_4_3-sunos test_map_text_warchive: cw-9_5-darwin test_map_xml_archive: cw-9_5-darwin test_map_xml_warchive: cw-9_5-darwin test_mi_text_archive: vc-7_1 test_mi_text_archive_dll: vc-7_1 test_no_rtti_binary_archive: vc-6_5 test_no_rtti_binary_archive_dll: vc-6_5 test_no_rtti_text_archive: vc-6_5 test_no_rtti_text_archive_dll: vc-6_5 test_no_rtti_text_warchive: vc-6_5 test_no_rtti_text_warchive_dll: vc-6_5 test_no_rtti_xml_archive: vc-6_5 test_no_rtti_xml_archive_dll: vc-6_5 test_no_rtti_xml_warchive: vc-6_5 test_no_rtti_xml_warchive_dll: vc-6_5 test_non_default_ctor2_text_archive: vc-7_1 test_non_default_ctor2_text_archive_dll: vc-7_1 test_non_default_ctor_text_archive: vc-7_1 test_non_default_ctor_text_archive_dll: vc-7_1 test_non_intrusive_text_archive: vc-7_1 test_non_intrusive_text_archive_dll: vc-7_1 test_null_ptr_text_archive: vc-7_1 test_null_ptr_text_archive_dll: vc-7_1 test_object_text_archive: vc-7_1 test_object_text_archive_dll: vc-7_1 test_polymorphic_binary_archive: cw-9_5-darwin test_polymorphic_binary_archive_dll: cw-9_5-darwin test_polymorphic_text_archive: cw-9_5-darwin test_polymorphic_text_warchive: cw-9_5-darwin test_polymorphic_xml_archive: cw-9_5-darwin test_polymorphic_xml_warchive: cw-9_5-darwin test_primitive_text_archive: vc-7_1 test_primitive_text_archive_dll: vc-7_1 test_private_ctor: cw-9_5-darwin test_registered_text_archive: vc-7_1 test_registered_text_archive_dll: vc-7_1 test_reset_object_address: cw-9_5-darwin test_set_binary_archive: cw-9_5-darwin test_set_binary_archive_dll: cw-9_5-darwin test_set_text_archive: cw-9_5-darwin test_set_text_warchive: cw-9_5-darwin test_set_xml_archive: cw-9_5-darwin test_set_xml_warchive: cw-9_5-darwin test_shared_ptr_132_binary_archive: vc-6_5 vc-6_5-stlport test_shared_ptr_132_binary_archive_dll: vc-6_5 test_shared_ptr_132_text_archive: vc-6_5 vc-6_5-stlport test_shared_ptr_132_text_archive_dll: gcc-3_4_3-sunos vc-6_5 test_shared_ptr_132_text_warchive: vc-6_5 vc-6_5-stlport test_shared_ptr_132_text_warchive_dll: vc-6_5 test_shared_ptr_132_xml_archive: vc-6_5 vc-6_5-stlport test_shared_ptr_132_xml_archive_dll: vc-6_5 test_shared_ptr_132_xml_warchive: vc-6_5 vc-6_5-stlport test_shared_ptr_132_xml_warchive_dll: vc-6_5 test_shared_ptr_binary_archive: borland-5_6_4 vc-6_5 test_shared_ptr_binary_archive_dll: borland-5_6_4 vc-6_5 test_shared_ptr_text_archive: borland-5_6_4 vc-6_5 test_shared_ptr_text_archive_dll: borland-5_6_4 vc-6_5 test_shared_ptr_text_warchive: borland-5_6_4 vc-6_5 test_shared_ptr_text_warchive_dll: borland-5_6_4 vc-6_5 test_shared_ptr_xml_archive: borland-5_6_4 vc-6_5 test_shared_ptr_xml_archive_dll: borland-5_6_4 vc-6_5 test_shared_ptr_xml_warchive: borland-5_6_4 vc-6_5 test_shared_ptr_xml_warchive_dll: borland-5_6_4 vc-6_5 test_split_text_archive: vc-7_1 test_split_text_archive_dll: vc-7_1 test_split_text_warchive: gcc-3_4_3-sunos test_tracking_text_archive: vc-7_1 test_tracking_text_archive_dll: vc-7_1 test_unregistered_binary_archive: gcc-3.2.3-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux test_unregistered_binary_archive_dll: gcc-3.2.3-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux test_unregistered_text_archive: gcc-3.2.3-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1 test_unregistered_text_archive_dll: gcc-3.2.3-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1 test_unregistered_xml_archive: gcc-3.2.3-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux test_unregistered_xml_archive_dll: gcc-3.2.3-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux test_unregistered_xml_warchive: gcc-4.0.1-linux test_unregistered_xml_warchive_dll: gcc-4.0.1-linux test_variant_binary_archive: cw-9_5-darwin test_variant_binary_archive_dll: cw-9_5-darwin test_variant_text_archive: cw-9_5-darwin test_variant_text_warchive: cw-9_5-darwin test_variant_xml_archive: cw-9_5-darwin test_variant_xml_warchive: cw-9_5-darwin test_vector_binary_archive: cw-9_5-darwin test_vector_binary_archive_dll: cw-9_5-darwin test_vector_text_archive: cw-9_5-darwin test_vector_text_warchive: cw-9_5-darwin test_vector_xml_archive: cw-9_5-darwin test_vector_xml_warchive: cw-9_5-darwin test_void_cast: gcc-3_4_3-sunos test_void_cast_dll: gcc-3_4_3-sunos |wave| test_re2c_lexer: cw-9_4 test_slex_lexer: cw-9_4 testwave: cw-9_4 gcc-3.4.4-linux gcc-3_4_3-sunos gcc-4.0.1-linux

9 19

[spirit][1.33.1] MinGW+STLport errors...
by Rene Rivera 10 Oct '05

10 Oct '05

In this error http://tinyurl.com/8sqq6 [1] -- There is a use of swprintf(wchar_t*, size_t, const wchar_t*, ...). But AFAICT it's not "swprintf" that's the intended call, but "snwprintf" which takes a buffer length as the second arg. [1] http://engineering.meta-comm.com/boost-regression/CVS-RC_1_33_0/developer/o… -- -- Grafik - Don't Assume Anything -- Redshift Software, Inc. - http://redshift-software.com -- rrivera/acm.org - grafik/redshift-software.com -- 102708583/icq - grafikrobot/aim - Grafik/jabber.org

3 4

[ptr_container] boost::ptr_map
by Alexey Bakhvalov 10 Oct '05

10 Oct '05

ptr_map<>::insert(key, value) function is taking first argument by non-const reference. Is it missing 'const' there?

5 4

Re: [boost] GUI coordinate units (Was: GUI foundations)
by brangdon＠cix.compulink.co.uk 10 Oct '05

10 Oct '05

In-Reply-To: <4342E0EF.4050601(a)sympatico.ca> seefeld(a)sympatico.ca (Stefan Seefeld) wrote (abridged): > > Maybe there's a reason for that. I'm not saying don't do it, but I'd > > recommend doing some experiments that prove it's actually possible > > before investing too much. > > Definitely, there are reasons. But as with the Y2K bug, it is mostly a > question of how long into the future you plan. Surely it's more a question of how far into the past you support? > Imagine new 200 dpi devices being ready for production but not usable > as no GUIs are available that can deal with that high a resolution. I'm kind-of asking why we will succeed when other people have failed. It sounds like the answer is "anti-aliasing". The GUI will only support devices that have enough colours to do good anti-aliased rending. OK; that may be a reasonable answer. Most modern devices seem to have lots of colours even when they don't have lots of pixels. For example, my phone has only 208x320 pixels but 16 bits of colour. -- Dave Harris, Nottingham, UK.

3 2

Re: [boost] GUI coordinate units (Was: GUI foundations)
by brangdon＠cix.compulink.co.uk 09 Oct '05

09 Oct '05

In-Reply-To: <4342E209.2050006(a)yahoo.com.au> mw8329(a)yahoo.com.au (Martin Wille) wrote (abridged): > Did you look at the examples on the antigrain.com website? They show > that with good anti-aliasing and with subpixel accuracy you get very > good results even when the display resolution is lower than the > resolutions of the details of the displayed objects. The spirals at > http://tinyurl.com/836fe look pretty impressive, IMHO. I hadn't (but have now). I already knew about anti-aliasing, though. I work in desktop publishing. My employers have their own graphics library which uses subpixel accuracy and anti-aliasing. I didn't design it but I work on and with it. It seems roughly similar in functionality to the AGG project, except that we place a lot of importance on text and vectors and I can't find text mentioned on their manual page. We find that for sending output to printer or PDF or whatever, it's important to output text as text as much as possible and only output as bitmaps for features the target device doesn't support. Anyway, yes, anti-aliasing helps, and is the only way to deal with curves, but grid-fitting gives better results where possible. As Stefan Seefeld says later, we can't hide the pixels completely. -- Dave Harris, Nottingham, UK.

2 1

Re: [boost] GUI coordinate units (Was: GUI foundations)
by brangdon＠cix.compulink.co.uk 09 Oct '05

09 Oct '05

In-Reply-To: <di20dn$2lh$1(a)sea.gmane.org> joel(a)boost-consulting.com (Joel de Guzman) wrote (abridged): > Seriously, look at it the other way... most docs and layouts that > need accurate layouts (e.g CAD drawings) are in metric. I don't see this as an argument for metric, but as an argument for not imposing any particular unit system on apps. That said: currently output resolution is described in "dots per inch" - in imperial units. For example, screens are 96dpi or 72dpi, and some printers are 300dpi. Applications which naturally use metric have rounding issues whatever they do; you can't help them. You can help imperial ones by not forcing them to convert to metric as a spurious intermediate step. -- Dave Harris, Nottingham, UK.

2 1

Re: [boost] GUI coordinate units (Was: GUI foundations)
by brangdon＠cix.compulink.co.uk 09 Oct '05

09 Oct '05

In-Reply-To: <434426EF.5030808(a)yahoo.com.au> mw8329(a)yahoo.com.au (Martin Wille) wrote (abridged): > > But you aren't going to draw a PCB on screen with boost.GUI widgets. > > Why shouldn't a good GUI library be prepared for that use case? I think he's saying that the use case would be handled by a different component of the library. I'm coming around to the idea that the library should use ints and device pixels for its core graphics units. Or rather, some fraction of pixels: probably 100 or 256 units per pixel. All other units eventually get converted to this. The conversion is dependant on the device, and if a component needs to be device-independant it uses its own units and defers conversion until it knows what device it is using. Many widget calculations won't care what the units are at all. Some sizing happens top-down. The user drags out a window, the app gives half the space to one widget and half to the other. It doesn't care what the units are, it is just dividing by two. Some sizing happens bottom-up. Often this is driven by text. A button needs enough room to display the word "Cancel" in 12-point text. int height = 12 * device.points_to_gu(); Font font( "Arial", height ); int width = font.width( "Cancel" ); I don't think there is any need to force the width to be in absolute units. Both millimetres and inches would be wrong for someone. A PCB would be laid out with a CAD app, which would measure in millimetres. Part of its rendering pipeline would be a conversion from mm to graphic units. A dialog editor is a different kind of app. It might measure in points and have a different conversion. The Microsoft one uses what it calls "dialog units", which are scaled according to dialog's chosen font, which can in principle be changed by the end-user. We don't need to force the dialog editor to use the same internal units as the CAD app. When they need to communicate, they can use pixels units * 256 a lingua-franc. I do not think the need for a device-independant linga-franca is compelling enough for it to dominate the core GUI. -- Dave Harris, Nottingham, UK.

1 0

Boost regression notification (2005-10-09 [RC_1_33_0])
by Douglas Gregor 09 Oct '05

09 Oct '05

Boost regression test failures ------------------------------ Report time: 2005-10-09T14:02:08Z This report lists all regression test failures on release platforms. Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-RC_1_33_0/developer/i… 151 failures in 5 libraries: graph (1) iostreams (1) range (3) serialization (141) spirit (5) |graph| graphviz_test: cw-9_4 |iostreams| gzip_test: gcc-4_0-darwin |range| array: vc-6_5 vc-6_5-stlport vc-7_0 |serialization| test_binary_text_archive: vc-7_1 test_binary_text_archive_dll: vc-7_1 test_class_info_save_text_archive: vc-7_1 test_class_info_save_text_archive_dll: vc-7_1 test_demo_xml_load: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin intel-win32-8_1 test_demo_xml_load_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_derived_text_archive: vc-7_1 test_derived_text_archive_dll: vc-7_1 test_exported_binary_archive: gcc-3.2.3-linux gcc-4.0.1-linux intel-9.0-linux vc-6_5 test_exported_binary_archive_dll: gcc-4.0.1-linux vc-6_5 test_exported_text_archive: gcc-3.2.3-linux gcc-4.0.1-linux vc-6_5 vc-7_1 test_exported_text_archive_dll: gcc-3.2.3-linux gcc-4.0.1-linux vc-6_5 vc-7_1 test_exported_text_warchive: gcc-4.0.1-linux vc-6_5 test_exported_text_warchive_dll: gcc-4.0.1-linux vc-6_5 test_exported_xml_archive: gcc-4.0.1-linux intel-8.1-linux vc-6_5 test_exported_xml_archive_dll: gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-6_5 test_exported_xml_warchive: gcc-3.2.3-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-6_5 test_exported_xml_warchive_dll: gcc-3.2.3-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-6_5 test_mi_text_archive: vc-7_1 test_mi_text_archive_dll: vc-7_1 test_no_rtti_binary_archive: vc-6_5 test_no_rtti_binary_archive_dll: vc-6_5 test_no_rtti_text_archive: vc-6_5 test_no_rtti_text_archive_dll: vc-6_5 test_no_rtti_text_warchive: vc-6_5 test_no_rtti_text_warchive_dll: vc-6_5 test_no_rtti_xml_archive: vc-6_5 test_no_rtti_xml_archive_dll: vc-6_5 test_no_rtti_xml_warchive: vc-6_5 test_no_rtti_xml_warchive_dll: vc-6_5 test_non_default_ctor2_text_archive: vc-7_1 test_non_default_ctor2_text_archive_dll: vc-7_1 test_non_default_ctor_text_archive: vc-7_1 test_non_default_ctor_text_archive_dll: vc-7_1 test_non_intrusive_text_archive: vc-7_1 test_non_intrusive_text_archive_dll: vc-7_1 test_null_ptr_text_archive: vc-7_1 test_null_ptr_text_archive_dll: vc-7_1 test_object_text_archive: vc-7_1 test_object_text_archive_dll: vc-7_1 test_primitive_text_archive: vc-7_1 test_primitive_text_archive_dll: vc-7_1 test_registered_text_archive: vc-7_1 test_registered_text_archive_dll: vc-7_1 test_shared_ptr_132_binary_archive: vc-6_5 vc-6_5-stlport test_shared_ptr_132_binary_archive_dll: vc-6_5 test_shared_ptr_132_text_archive: vc-6_5 vc-6_5-stlport test_shared_ptr_132_text_archive_dll: vc-6_5 test_shared_ptr_132_text_warchive: vc-6_5 vc-6_5-stlport test_shared_ptr_132_text_warchive_dll: vc-6_5 test_shared_ptr_132_xml_archive: vc-6_5 vc-6_5-stlport test_shared_ptr_132_xml_archive_dll: vc-6_5 test_shared_ptr_132_xml_warchive: vc-6_5 vc-6_5-stlport test_shared_ptr_132_xml_warchive_dll: vc-6_5 test_shared_ptr_binary_archive: borland-5_6_4 vc-6_5 test_shared_ptr_binary_archive_dll: borland-5_6_4 vc-6_5 test_shared_ptr_text_archive: borland-5_6_4 vc-6_5 test_shared_ptr_text_archive_dll: borland-5_6_4 vc-6_5 test_shared_ptr_text_warchive: borland-5_6_4 vc-6_5 test_shared_ptr_text_warchive_dll: borland-5_6_4 vc-6_5 test_shared_ptr_xml_archive: borland-5_6_4 vc-6_5 test_shared_ptr_xml_archive_dll: borland-5_6_4 vc-6_5 test_shared_ptr_xml_warchive: borland-5_6_4 vc-6_5 test_shared_ptr_xml_warchive_dll: borland-5_6_4 vc-6_5 test_split_text_archive: vc-7_1 test_split_text_archive_dll: vc-7_1 test_tracking_text_archive: vc-7_1 test_tracking_text_archive_dll: vc-7_1 test_unregistered_binary_archive: gcc-3.2.3-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux test_unregistered_binary_archive_dll: gcc-3.2.3-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux test_unregistered_text_archive: gcc-3.2.3-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1 test_unregistered_text_archive_dll: gcc-3.2.3-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1 test_unregistered_xml_archive: gcc-3.2.3-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux test_unregistered_xml_archive_dll: gcc-3.2.3-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux test_unregistered_xml_warchive: gcc-4.0.1-linux test_unregistered_xml_warchive_dll: gcc-4.0.1-linux |spirit| bug_000008: gcc-3_4_3-sunos grammar_mt_tests: gcc-3_4_3-sunos owi_mt_tests: gcc-3_4_3-sunos scoped_lock_tests: gcc-3_4_3-sunos scoped_lock_tests_debug: gcc-3_4_3-sunos

1 0

Boost regression notification (2005-10-09 [HEAD])
by Douglas Gregor 09 Oct '05

09 Oct '05

Boost regression test failures ------------------------------ Report time: 2005-10-09T05:00:33Z This report lists all regression test failures on release platforms. Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-HEAD/developer/issues… 105 failures in 12 libraries: concept_check (13) foreach (1) functional/hash (1) graph (2) mpl (1) parameter (13) serialization (39) spirit (8) thread (4) tuple (1) typeof (21) wave (1) |concept_check| stl_concept_covering: cw-9_4 gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin intel-win32-9_0 intel-win32-9_0 mingw-3_4_2 msvc vc-7_1 |foreach| user_defined: msvc |functional/hash| container_fwd_test: msvc |graph| graphviz_test: vc-7_1 layout_test: intel-win32-9_0 |mpl| size_t: gcc-4_0-darwin |parameter| basics: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux efficiency: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux msvc macros: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux sfinae: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux msvc unnamed: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux vc-7_1 |serialization| test_class_info_load_binary_archive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_binary_archive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_archive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_archive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_warchive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_warchive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_archive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_archive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_warchive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_warchive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_const_save_fail1: msvc test_const_save_fail2: msvc test_const_save_fail3: msvc test_map_binary_archive_dll: msvc test_map_text_archive_dll: msvc test_map_text_warchive_dll: msvc test_non_default_ctor_binary_archive: vc-7_1 test_non_default_ctor_text_warchive: vc-7_1 test_null_ptr_xml_warchive_dll: vc-7_1 |spirit| action_tests_debug: gcc-3_4_3-sunos distinct_tests_debug: gcc-3_4_3-sunos escape_char_parser_tests_debug: gcc-3_4_3-sunos grammar_def_test_debug: gcc-3_4_3-sunos switch_problem_debug: gcc-3_4_3-sunos switch_tests_single_debug: gcc-3_4_3-sunos traverse_tests: intel-win32-9_0 traverse_tests_debug: intel-win32-9_0 |thread| test_condition: gcc-3_4_3-sunos test_mutex: gcc-3_4_3-sunos test_tss: gcc-3_4_3-sunos gcc-3_4_3-sunos |tuple| tuple_test_bench: gcc-3_4_3-sunos |typeof| data_member_native: cw-9_4 function_native: cw-9_4 msvc function_ptr_native: cw-9_4 function_ref_native: cw-9_4 lvalue_native: cw-9_4 msvc member_function_native: cw-9_4 modifiers_emulation: cw-9_4 modifiers_native: cw-9_4 noncopyable_native: cw-9_4 std_emulation: cw-9_4 std_native: cw-9_4 template_dependent_native: cw-9_4 template_enum_native: cw-9_4 template_int_native: cw-9_4 template_multiword_native: cw-9_4 template_tpl_native: cw-9_4 msvc template_type_native: cw-9_4 type_native: cw-9_4 |wave| testwave: gcc-3.3.6-linux

1 0

Still boostbook problems
by David A. Greene 09 Oct '05

09 Oct '05

I've been dealing with this issue (build log below)for a couple of months now. I've updated from the latest CVS, rebvuilt bjam, run the boostbook auto-setup, etc. The only difference from the CVS is that I've added documentation for my named template parameters implementation. This is preventing me from putting NTP up for viewing. Can anyone help? Thanks. -Dave ---------------------- cd ~/src/boost/install/ cd ~/src/boost/doc && ~/bin/bjam --v2 /home/greened/src/boost/tools/build/v2/build/toolset.jam:26: in using *** argument error * rule boostbook.init ( docbook-xsl-dir ? : docbook-dtd-dir ? : boostbook-dir ? ) * called with: ( /home/greened/src/boost/install/docbook-xsl-1.67.2 : /home/greened/src/boost/install/docbook-dtd-4.2 using xsltproc : /usr/bin/xsltproc : : : : : ) * extra argument using /home/greened/src/boost/tools/build/v2/tools/boostbook.jam:63:see definition of rule 'init' being called /home/greened/user-config.jam:63: in modules.load /home/greened/src/boost/tools/build/v2/build-system.jam:115: in load /home/greened/src/boost/tools/build/v2/kernel/modules.jam:261: in import /home/greened/src/boost/tools/build/v2/kernel/bootstrap.jam:172: in boost-build /home/greened/src/boost/boost-build.jam:12: in module scope Compilation exited abnormally with code 1 at Sat Oct 8 14:07:50

2 1

Re: [boost] GUI foundations
by brangdon＠cix.compulink.co.uk 09 Oct '05

09 Oct '05

In-Reply-To: <43426645.30304(a)torjo.com> john.lists(a)torjo.com (John Torjo) wrote (abridged): > And, about usability in code. Why would I want in my program, both: > gui::rect<pc,double> and gui::rect<pc,int> ? For my apps I have found there needs to be two levels. There's a device/raster level, which wants to use pixels and ints, and there's a logical/world level, which uses units like inches or cm and floating point. The device/raster level uses pixels and ints because that's what raster hardware uses. This is not something you can really abstract away from. For example, it's important to scroll by an integral number of pixels else anti-aliasing makes the lines change colour. The logical/world level needs to be device-independant. It probably needs to be scale-invariant too; for example, a rectangle that measures 2x3 needs to keep its aspect ratio if you halve its size. My employers actually use ints and very small units - 1/72000ths of an inch - which are also the units used by Postscript and PDF. That decision now seems dated to me and more and more of my geometry code is moving to floating point. It works better. It may be that boost doesn't need to tackle the logical/world level immediately. The window-manager stuff and the low-level drawing stuff can use pixels and ints. However, at least some programs will want a logical level too when they come to draw. > Just think of the many places you'll need to deal with geometry > (rectangle/point/size), and converting from one type of unit (px to cm, > cm to in, etc) to another. I'd rather explicit conversion than an attempt to abstract away the differences. Typically there is a world-to-device linear transform that does the conversion. A single matrix operation provides rotation, scrolling and zoom in addition to scaling from inches or centimetres or whatever. -- Dave Harris, Nottingham, UK.

3 3

serialization of vector<string>
by Ben Artin 08 Oct '05

08 Oct '05

I am using boost 1.32. When I serialize a string, no metadata is written, as implementation_level<string> is set to primitive_type in serialization/string.hpp. However, when I serialize a vector<string>, I end up with metadata, because implementation_level<vector<string> > is not set anywhere and therefore defaults to object_class_info. Every other primitive type appears to be covered by BOOST_SERIALIZATION_COLLECTION_TRAITS and therefore implementation_level<vector<T> > is object_serializable for every other primitive type. I checked in 1.33 and there don't appear to be any relevant changes, but I could be wrong. My question: is this an omission; that is, should implementation_level<vector<string> > be object_serializable? (And similarly for other collections of strings.) Thanks, Ben -- If this message helped you, consider buying an item from my wish list: <http://artins.org/ben/wishlist> I changed my name: <http://periodic-kingdom.org/People/NameChange.php>

2 1

Bugs assigned to "nobody"
by Marshall Clow 08 Oct '05

08 Oct '05

I have been working through the bug database, trying to get every bug a home. There are a few left (assigned to "nobody"), mostly having to do with the build system, that I'm not sure who is the best person to handle them. I would appreciate it if people could take a look at these and let me know who they should be assigned to. Thanks! Summary: BCB6 throw EExternelException Bug #: 596149 <http://sourceforge.net/tracker/index.php?func=detail&aid=596149&group_id=75…> Summary: boost and VC++ 6 with STLPORT problem Bug #: 618820 <http://sourceforge.net/tracker/index.php?func=detail&aid=618820&group_id=75…> Summary: 1.31.0 doesn't support inter-win32-stlport use intel8.0 Bug #: 918570 <http://sourceforge.net/tracker/index.php?func=detail&aid=918570&group_id=75…> Summary: failure in boost jam unit tests on cygwin Bug #: 940941 <http://sourceforge.net/tracker/index.php?func=detail&aid=940941&group_id=75…> Summary: vc-7_1-stlport native-wchar_t problem Bug #: 1070327 <http://sourceforge.net/tracker/index.php?func=detail&aid=1070327&group_id=7…> Summary: 'failed fileclone' when building with -j on 1.32.0 Bug #: 1102389 <http://sourceforge.net/tracker/index.php?func=detail&aid=1102389&group_id=7…> Summary: can't compile with intel-linux (icc 8) Bug #: 1105342 <http://sourceforge.net/tracker/index.php?func=detail&aid=1105342&group_id=7…> Summary: Can't build on cygwin Bug #: 1145183 <http://sourceforge.net/tracker/index.php?func=detail&aid=1145183&group_id=7…> Summary: Muss of 'host' and 'target' Bug #: 1178259 <http://sourceforge.net/tracker/index.php?func=detail&aid=1178259&group_id=7…> Summary: boost jam problem with parallel builds Bug #: 1234224 <http://sourceforge.net/tracker/index.php?func=detail&aid=1234224&group_id=7…> Summary: Build process doesn't generate DLL import libs on Cygwin Bug #: 1262967 <http://sourceforge.net/tracker/index.php?func=detail&aid=1262967&group_id=7…> Summary: html docs frequently missing key words Bug #: 1294420 <http://sourceforge.net/tracker/index.php?func=detail&aid=1294420&group_id=7…> -- -- Marshall Marshall Clow Idio Software <mailto:marshall@idio.com> It is by caffeine alone I set my mind in motion. It is by the beans of Java that thoughts acquire speed, the hands acquire shaking, the shaking becomes a warning. It is by caffeine alone I set my mind in motion.

1 0

Website still links to old mail archives
by Jonathan Wakely 08 Oct '05

08 Oct '05

http://boost.org/more/mailing_lists.htm is out of date, it links to the old MailMan archive. The version in CVS is right, so looks like someone just needs to update the copy on the website. jon

1 0

Boost regression notification (2005-10-08 [RC_1_33_0])
by Douglas Gregor 08 Oct '05

08 Oct '05

Boost regression test failures ------------------------------ Report time: 2005-10-08T13:36:20Z This report lists all regression test failures on release platforms. Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-RC_1_33_0/developer/i… 212 failures in 7 libraries: graph (1) iostreams (2) multi_index (1) range (3) serialization (198) spirit (5) wave (2) |graph| graphviz_test: cw-9_4 |iostreams| gzip_test: cw-9_5-darwin gcc-4_0-darwin |multi_index| test_serialization: cw-9_5-darwin |range| array: vc-6_5 vc-6_5-stlport vc-7_0 |serialization| test_binary_text_archive: vc-7_1 test_binary_text_archive_dll: vc-7_1 test_class_info_save_text_archive: vc-7_1 test_class_info_save_text_archive_dll: vc-7_1 test_delete_pointer_binary_archive: cw-9_5-darwin test_delete_pointer_binary_archive_dll: cw-9_5-darwin test_delete_pointer_text_archive: cw-9_5-darwin test_delete_pointer_text_warchive: cw-9_5-darwin test_delete_pointer_xml_archive: cw-9_5-darwin test_delete_pointer_xml_warchive: cw-9_5-darwin test_demo_polymorphic: cw-9_5-darwin test_demo_xml_load: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin intel-win32-8_1 test_demo_xml_load_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_deque_binary_archive: cw-9_5-darwin test_deque_binary_archive_dll: cw-9_5-darwin test_deque_text_archive: cw-9_5-darwin test_deque_text_warchive: cw-9_5-darwin test_deque_xml_archive: cw-9_5-darwin test_deque_xml_warchive: cw-9_5-darwin test_derived_text_archive: vc-7_1 test_derived_text_archive_dll: vc-7_1 test_exported_binary_archive: gcc-3.2.3-linux gcc-4.0.1-linux intel-9.0-linux vc-6_5 test_exported_binary_archive_dll: gcc-4.0.1-linux vc-6_5 test_exported_text_archive: gcc-3.2.3-linux gcc-4.0.1-linux vc-6_5 vc-7_1 test_exported_text_archive_dll: gcc-3.2.3-linux gcc-4.0.1-linux vc-6_5 vc-7_1 test_exported_text_warchive: gcc-4.0.1-linux vc-6_5 test_exported_text_warchive_dll: gcc-4.0.1-linux vc-6_5 test_exported_xml_archive: gcc-4.0.1-linux intel-8.1-linux vc-6_5 test_exported_xml_archive_dll: gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-6_5 test_exported_xml_warchive: gcc-3.2.3-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-6_5 test_exported_xml_warchive_dll: gcc-3.2.3-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-6_5 test_list_binary_archive: cw-9_5-darwin test_list_binary_archive_dll: cw-9_5-darwin test_list_ptrs_binary_archive: cw-9_5-darwin test_list_ptrs_binary_archive_dll: cw-9_5-darwin test_list_ptrs_text_archive: cw-9_5-darwin test_list_ptrs_text_warchive: cw-9_5-darwin test_list_ptrs_xml_archive: cw-9_5-darwin test_list_ptrs_xml_warchive: cw-9_5-darwin test_list_text_archive: cw-9_5-darwin test_list_text_warchive: cw-9_5-darwin test_list_xml_archive: cw-9_5-darwin test_list_xml_warchive: cw-9_5-darwin test_map_binary_archive: cw-9_5-darwin test_map_binary_archive_dll: cw-9_5-darwin test_map_text_archive: cw-9_5-darwin test_map_text_warchive: cw-9_5-darwin test_map_xml_archive: cw-9_5-darwin test_map_xml_warchive: cw-9_5-darwin test_mi_text_archive: vc-7_1 test_mi_text_archive_dll: vc-7_1 test_no_rtti_binary_archive: vc-6_5 test_no_rtti_binary_archive_dll: vc-6_5 test_no_rtti_text_archive: vc-6_5 test_no_rtti_text_archive_dll: vc-6_5 test_no_rtti_text_warchive: vc-6_5 test_no_rtti_text_warchive_dll: vc-6_5 test_no_rtti_xml_archive: vc-6_5 test_no_rtti_xml_archive_dll: vc-6_5 test_no_rtti_xml_warchive: vc-6_5 test_no_rtti_xml_warchive_dll: vc-6_5 test_non_default_ctor2_text_archive: vc-7_1 test_non_default_ctor2_text_archive_dll: vc-7_1 test_non_default_ctor_text_archive: vc-7_1 test_non_default_ctor_text_archive_dll: vc-7_1 test_non_intrusive_text_archive: vc-7_1 test_non_intrusive_text_archive_dll: vc-7_1 test_null_ptr_text_archive: vc-7_1 test_null_ptr_text_archive_dll: vc-7_1 test_object_text_archive: vc-7_1 test_object_text_archive_dll: vc-7_1 test_polymorphic_binary_archive: cw-9_5-darwin test_polymorphic_binary_archive_dll: cw-9_5-darwin test_polymorphic_text_archive: cw-9_5-darwin test_polymorphic_text_warchive: cw-9_5-darwin test_polymorphic_xml_archive: cw-9_5-darwin test_polymorphic_xml_warchive: cw-9_5-darwin test_primitive_text_archive: vc-7_1 test_primitive_text_archive_dll: vc-7_1 test_private_ctor: cw-9_5-darwin test_registered_text_archive: vc-7_1 test_registered_text_archive_dll: vc-7_1 test_reset_object_address: cw-9_5-darwin test_set_binary_archive: cw-9_5-darwin test_set_binary_archive_dll: cw-9_5-darwin test_set_text_archive: cw-9_5-darwin test_set_text_warchive: cw-9_5-darwin test_set_xml_archive: cw-9_5-darwin test_set_xml_warchive: cw-9_5-darwin test_shared_ptr_132_binary_archive: vc-6_5 vc-6_5-stlport test_shared_ptr_132_binary_archive_dll: vc-6_5 test_shared_ptr_132_text_archive: vc-6_5 vc-6_5-stlport test_shared_ptr_132_text_archive_dll: vc-6_5 test_shared_ptr_132_text_warchive: vc-6_5 vc-6_5-stlport test_shared_ptr_132_text_warchive_dll: vc-6_5 test_shared_ptr_132_xml_archive: vc-6_5 vc-6_5-stlport test_shared_ptr_132_xml_archive_dll: vc-6_5 test_shared_ptr_132_xml_warchive: vc-6_5 vc-6_5-stlport test_shared_ptr_132_xml_warchive_dll: vc-6_5 test_shared_ptr_binary_archive: borland-5_6_4 vc-6_5 test_shared_ptr_binary_archive_dll: borland-5_6_4 vc-6_5 test_shared_ptr_text_archive: borland-5_6_4 vc-6_5 test_shared_ptr_text_archive_dll: borland-5_6_4 vc-6_5 test_shared_ptr_text_warchive: borland-5_6_4 vc-6_5 test_shared_ptr_text_warchive_dll: borland-5_6_4 vc-6_5 test_shared_ptr_xml_archive: borland-5_6_4 vc-6_5 test_shared_ptr_xml_archive_dll: borland-5_6_4 vc-6_5 test_shared_ptr_xml_warchive: borland-5_6_4 vc-6_5 test_shared_ptr_xml_warchive_dll: borland-5_6_4 vc-6_5 test_split_text_archive: vc-7_1 test_split_text_archive_dll: vc-7_1 test_tracking_text_archive: vc-7_1 test_tracking_text_archive_dll: vc-7_1 test_unregistered_binary_archive: gcc-3.2.3-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux test_unregistered_binary_archive_dll: gcc-3.2.3-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux test_unregistered_text_archive: gcc-3.2.3-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1 test_unregistered_text_archive_dll: gcc-3.2.3-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1 test_unregistered_xml_archive: gcc-3.2.3-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux test_unregistered_xml_archive_dll: gcc-3.2.3-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux test_unregistered_xml_warchive: gcc-4.0.1-linux test_unregistered_xml_warchive_dll: gcc-4.0.1-linux test_variant_binary_archive: cw-9_5-darwin test_variant_binary_archive_dll: cw-9_5-darwin test_variant_text_archive: cw-9_5-darwin test_variant_text_warchive: cw-9_5-darwin test_variant_xml_archive: cw-9_5-darwin test_variant_xml_warchive: cw-9_5-darwin test_vector_binary_archive: cw-9_5-darwin test_vector_binary_archive_dll: cw-9_5-darwin test_vector_text_archive: cw-9_5-darwin test_vector_text_warchive: cw-9_5-darwin test_vector_xml_archive: cw-9_5-darwin test_vector_xml_warchive: cw-9_5-darwin |spirit| bug_000008: gcc-3_4_3-sunos grammar_mt_tests: gcc-3_4_3-sunos owi_mt_tests: gcc-3_4_3-sunos scoped_lock_tests: gcc-3_4_3-sunos scoped_lock_tests_debug: gcc-3_4_3-sunos |wave| test_re2c_lexer: cw-9_4 test_slex_lexer: cw-9_4

1 0

Boost regression notification (2005-10-08 [HEAD])
by Douglas Gregor 08 Oct '05

08 Oct '05

Boost regression test failures ------------------------------ Report time: 2005-10-08T05:00:44Z This report lists all regression test failures on release platforms. Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-HEAD/developer/issues… 101 failures in 11 libraries: concept_check (13) foreach (1) functional/hash (1) graph (2) mpl (1) parameter (13) serialization (36) spirit (8) thread (4) tuple (1) typeof (21) |concept_check| stl_concept_covering: cw-9_4 gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin intel-win32-9_0 intel-win32-9_0 mingw-3_4_2 msvc vc-7_1 |foreach| user_defined: msvc |functional/hash| container_fwd_test: msvc |graph| graphviz_test: vc-7_1 layout_test: intel-win32-9_0 |mpl| size_t: gcc-4_0-darwin |parameter| basics: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux efficiency: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux msvc macros: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux sfinae: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux msvc unnamed: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux vc-7_1 |serialization| test_class_info_load_binary_archive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_binary_archive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_archive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_archive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_warchive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_warchive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_archive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_archive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_warchive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_warchive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_const_save_fail1: msvc test_const_save_fail2: msvc test_const_save_fail3: msvc test_map_binary_archive_dll: msvc test_map_text_archive_dll: msvc test_map_text_warchive_dll: msvc |spirit| action_tests_debug: gcc-3_4_3-sunos distinct_tests_debug: gcc-3_4_3-sunos escape_char_parser_tests_debug: gcc-3_4_3-sunos grammar_def_test_debug: gcc-3_4_3-sunos switch_problem_debug: gcc-3_4_3-sunos switch_tests_single_debug: gcc-3_4_3-sunos traverse_tests: intel-win32-9_0 traverse_tests_debug: intel-win32-9_0 |thread| test_condition: gcc-3_4_3-sunos test_mutex: gcc-3_4_3-sunos test_tss: gcc-3_4_3-sunos gcc-3_4_3-sunos |tuple| tuple_test_bench: gcc-3_4_3-sunos |typeof| data_member_native: cw-9_4 function_native: cw-9_4 msvc function_ptr_native: cw-9_4 function_ref_native: cw-9_4 lvalue_native: cw-9_4 msvc member_function_native: cw-9_4 modifiers_emulation: cw-9_4 modifiers_native: cw-9_4 noncopyable_native: cw-9_4 std_emulation: cw-9_4 std_native: cw-9_4 template_dependent_native: cw-9_4 template_enum_native: cw-9_4 template_int_native: cw-9_4 template_multiword_native: cw-9_4 template_tpl_native: cw-9_4 msvc template_type_native: cw-9_4 type_native: cw-9_4

1 0

[Boost-bugs] [ boost-Bugs-1315712 ] Adding boost::is_complex to type_traits.hpp
by SourceForge.net 08 Oct '05

08 Oct '05

Bugs item #1315712, was opened at 2005-10-07 10:03 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=107586&aid=1315712&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: type_traits Group: None Status: Open Resolution: None Priority: 5 Submitted By: Edward Grace (ejgrace) Assigned to: John Maddock (johnmaddock) Summary: Adding boost::is_complex to type_traits.hpp Initial Comment: Following a discussion on boost-users I am adding this to the bug system so it doesn't get lost. Can someone add a boost::is_complex<T> trait so that checks for complex numbers can be made. This is a common requirement in templated scientific code as complex numbers sometimes need to be treated differently. Attached is my implementation, please feel free to incorperate it. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=107586&aid=1315712&group_… ------------------------------------------------------- This SF.Net email is sponsored by: Power Architecture Resource Center: Free content, downloads, discussions, and more. http://solutions.newsforge.com/ibmarch.tmpl _______________________________________________ Boost-bugs mailing list Boost-bugs(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/boost-bugs

3 5

[multi_array] summing columns as requested in c.l.c++.m?
by Larry Evans 08 Oct '05

08 Oct '05

Would multi_array be some help in solving the problem posed here: http://groups.google.com/group/comp.lang.c++.moderated/msg/d91a095b07513f46 ?

1 0

Request for technical notes
by John Calcote 08 Oct '05

08 Oct '05

I think it would be a good idea to provide some technical notes for various boost class implementations. For example, I have recently been studying smart pointers - I've ready Andrei Alexandrescu's discussion of the topic in his book, 'Modern C++ Design'. It's good, and fairly comprehensive, but doesn't cover all of the nuances of some of the boost smart pointer implementations. For those of us interested in learning more about the language, and more about boost classes and the rationale behind the implementation - and for those of us who simply don't have the technical background to "just know" the answer at a glance, as I'm sure some of you contributors do - why not provide a simple rationale for adding a particular member function to a particular class? I'm all for sharing, but I would like to know the reason for half the implementation. I believe this would give something new to the C++ community in a simpler way than has been done in the past - information generally gathered individually and painfully over years of study. Thanks, John Calcote Novell, Inc.

5 4

cpp_re.cpp, scanner.hpp
by Reed Kotler 08 Oct '05

08 Oct '05

I'm getting compiler warnings in cpp_re.cpp because the prototype for ReportErrorProc has char* as the second parameter and in cpp_re.cpp a string literal is being passed to it. I hate to turn off compiler warnings for such things because they often represent bugs. boost/wave/cpplexer/re2clex

2 1

problem comparing shared_ptr pointers
by Valentin Samko 07 Oct '05

07 Oct '05

Why is the shared counter used to compare shared_ptr objects, and not the container pointer? Until revision 1.24, the container pointer was used to compare shared_ptr objects, see http://cvs.sourceforge.net/viewcvs.py/boost/boost/boost/shared_ptr.hpp?r1=1… . This introduced a change in shared_ptr behaviour and introduced a case where (p1 < p2 && p1 == p2) is true where p1 and p2 are two shared pointers, see the included example. Was this change in behaviour intentional, and is this behaviour documented anywhere? Example: struct A {}; struct deleter1 { template<class T> void operator()(T*) const {} }; struct deleter2 { template<class T> void operator()(T*) const {} }; int main() { A* a = new A(); boost::shared_ptr<A> p1(a, deleter1()); boost::shared_ptr<A> p2(a, deleter2()); std::cout << "p1 < p2 = " << (p1 < p2) << std::endl ; std::cout << "p1 == p2 = " << (p1 == p2) << std::endl ; } Output: p1 < p2 = 1 p1 == p2 = 1 -- Valentin Samko - http://val.samko.info

4 5

Interesting Wave Build Error
by John Maddock 07 Oct '05

07 Oct '05

Quite alarming really, not Boost's fault though (see attached image). Occurs when building with VC7.1 + STLport 4.6.2. John.

2 3

multiton discussion
by Jason Hise 07 Oct '05

07 Oct '05

I am trying to decide on the best interface for the multiton to provide. Some background: The singleton interface consists of three smart pointer types: singleton_ptr, const_singleton_ptr, and singleton_ref. Instances of these always automagically refer to the singleton instance. With regard to multi threading, when an operation is performed through a singleton_ptr, an exclusive lock is obtained for the duration of the operation. A const_singleton_ptr behaves similarly, but it acquired a shared lock instead, and only const members of the singleton instance can be accessed. A singleton_ref is considered to be a dereferenced singleton_ptr, so it owns an exclusive lock on the instance for its entire lifetime. It is implicitly convertible to a raw reference to Type, and as such is ideal to use as a proxy to the instance which locks it for the duration of a function call. Ex: void foo ( Type & ); void bar ( ) { // pass the singleton to foo and simultaneously lock the operation foo ( singleton_ref < Type > ( ) ); } Ideally, I would like the multiton to provide a similar interface. I would picture doing this by providing a multiton_ptr, const_multiton_ptr, and multiton_ref, which all take a key to the instance as a constructor param. Question 1) Should multiton_ptrs be copy constructible or assignable? What about multiton_refs? Keep in mind that a multiton_ref owns a lock directly, and thus would need to switch locks if redirected to a different instance. Question 2) Should the multiton_ptr and const_multiton_ptr also function as iterators? If so, should dereferencing them result in a pointer to a pair < const Key &, Type & >, or just a regular pointer to Type? Also, since the container itself is not exposed, how should I provide access to 'begin' and 'end'? Is it sufficient to provide a multiton_ptr constructor which takes an enum, and have that enum define the values begin and end? Question 3) Although each singleton instance in a multiton has its own mutex (assuming a multi threaded policy), operations which can change the state of the multiton container itself also need to be locked with a separate mutex. Thus far, the only operation of this nature that I can see is when a pointer to an instance with a previously unused key is created. However, if client code is using a multiton_ptr as an iterator in a loop, that whole loop needs to be locked with the same mutex as well, lest another thread incidentally create a new instance while the loop is in progress. Should multiton_ptr provide public nested read and write lock types to give client code this access, or should it provide some sort of for_each algorithm instead, which does the locking automatically? Question 4) Should the container used by the multiton become an additional optional policy? A regular map just won't cut it if the multiton needs its instances to exist in shared memory. A few more notes: * The singleton and multiton no longer have any inheritance requirements. Hence, even singleton_ptr < int > is valid, along with any other type one can think of. * An uncreatable base is provided which does use CRTP. If used, uncreatable must also be provided with the factory to use internally. Use of this is completely optional, and makes it completely and absolutely impossible for client code to create singleton instances, no matter how hard it tries to hack around it. (If there is interest in the semantics of this, I will post a more complete description). If anyone feels my design is partially or completely off and has better ideas please let me know. -Jason

2 1

[ptr_container] Serialization?
by Jared McIntyre 07 Oct '05

07 Oct '05

Is there pre-existing code for using the boost::serialization library with the ptr_containers? Jared McIntyre

3 2

[iostreams][iterator] is_incrementable broken on gcc 4.0.2 (was: Re: gcc 4.0.2)
by Jonathan Turkanis 07 Oct '05

07 Oct '05

[I meant to post this on testing and devel] Martin Wille wrote: > Hi, > > > I've added gcc 4.0.2 to my set of toolsets. > > Unfortunately, there are a lot (25) of additional regressions for > 4.0.2. Mainly affected are: Iostreams, Iterator and Spirit. It looks like is_incrementable may be broken on gcc 4.0.2. See, e.g., http://tinyurl.com/7qlow http://tinyurl.com/9mlsu -- Jonathan Turkanis www.kangaroologic.com

1 0

Boost regression notification (2005-10-07 [RC_1_33_0])
by Douglas Gregor 07 Oct '05

07 Oct '05

Boost regression test failures ------------------------------ Report time: 2005-10-07T14:49:13Z This report lists all regression test failures on release platforms. Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-RC_1_33_0/developer/i… 246 failures in 6 libraries: graph (1) iostreams (33) multi_index (1) range (3) serialization (202) wave (6) |graph| graphviz_test: cw-9_4 |iostreams| auto_close_test: borland-5_6_4 code_converter_test: borland-5_6_4 component_access_test: borland-5_6_4 compose_test: borland-5_6_4 copy_test: borland-5_6_4 counter_test: borland-5_6_4 example_test: borland-5_6_4 filtering_stream_test: borland-5_6_4 flush_test: borland-5_6_4 gzip_test: cw-9_5-darwin gcc-2.95.3-stlport-4.6.2-linux gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin gcc-3_4_3-sunos gcc-4.0.1-linux gcc-4_0-darwin intel-8.1-linux intel-9.0-linux mingw-3_4_2 vc-7_1 invert_test: borland-5_6_4 line_filter_test: borland-5_6_4 newline_test: borland-5_6_4 pipeline_test: borland-5_6_4 regex_filter_test: borland-5_6_4 restrict_test: borland-5_6_4 seekable_filter_test: borland-5_6_4 stdio_filter_test: borland-5_6_4 symmetric_filter_test: borland-5_6_4 tee_test: borland-5_6_4 wide_stream_test: borland-5_6_4 |multi_index| test_serialization: cw-9_5-darwin |range| array: vc-6_5 vc-6_5-stlport vc-7_0 |serialization| test_binary_text_archive: vc-7_1 test_binary_text_archive_dll: vc-7_1 test_class_info_save_text_archive: vc-7_1 test_class_info_save_text_archive_dll: vc-7_1 test_delete_pointer_binary_archive: cw-9_5-darwin test_delete_pointer_binary_archive_dll: cw-9_5-darwin test_delete_pointer_text_archive: cw-9_5-darwin test_delete_pointer_text_warchive: cw-9_5-darwin test_delete_pointer_xml_archive: cw-9_5-darwin test_delete_pointer_xml_warchive: cw-9_5-darwin test_demo_polymorphic: cw-9_5-darwin test_demo_xml_load: gcc-3_3-darwin gcc-4_0-darwin intel-win32-8_1 test_demo_xml_load_dll: gcc-3_3-darwin gcc-4_0-darwin test_deque_binary_archive: cw-9_5-darwin test_deque_binary_archive_dll: cw-9_5-darwin test_deque_text_archive: cw-9_5-darwin test_deque_text_warchive: cw-9_5-darwin test_deque_xml_archive: cw-9_5-darwin test_deque_xml_warchive: cw-9_5-darwin test_derived_text_archive: vc-7_1 test_derived_text_archive_dll: vc-7_1 test_exported_binary_archive: gcc-3.2.3-linux gcc-4.0.1-linux intel-9.0-linux vc-6_5 test_exported_binary_archive_dll: gcc-4.0.1-linux vc-6_5 test_exported_text_archive: gcc-3.2.3-linux gcc-4.0.1-linux vc-6_5 vc-7_1 test_exported_text_archive_dll: gcc-3.2.3-linux gcc-4.0.1-linux vc-6_5 vc-7_1 test_exported_text_warchive: gcc-4.0.1-linux vc-6_5 test_exported_text_warchive_dll: gcc-4.0.1-linux vc-6_5 test_exported_xml_archive: gcc-4.0.1-linux intel-8.1-linux vc-6_5 test_exported_xml_archive_dll: gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-6_5 test_exported_xml_warchive: gcc-3.2.3-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-6_5 test_exported_xml_warchive_dll: gcc-3.2.3-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-6_5 test_list_binary_archive: cw-9_5-darwin test_list_binary_archive_dll: cw-9_5-darwin test_list_ptrs_binary_archive: cw-9_5-darwin test_list_ptrs_binary_archive_dll: cw-9_5-darwin test_list_ptrs_text_archive: cw-9_5-darwin test_list_ptrs_text_warchive: cw-9_5-darwin test_list_ptrs_xml_archive: cw-9_5-darwin test_list_ptrs_xml_warchive: cw-9_5-darwin test_list_ptrs_xml_warchive_dll: gcc-3_4_3-sunos test_list_text_archive: cw-9_5-darwin test_list_text_warchive: cw-9_5-darwin test_list_xml_archive: cw-9_5-darwin test_list_xml_warchive: cw-9_5-darwin test_map_binary_archive: cw-9_5-darwin test_map_binary_archive_dll: cw-9_5-darwin test_map_text_archive: cw-9_5-darwin gcc-3_4_3-sunos test_map_text_warchive: cw-9_5-darwin test_map_xml_archive: cw-9_5-darwin test_map_xml_warchive: cw-9_5-darwin test_mi_text_archive: vc-7_1 test_mi_text_archive_dll: vc-7_1 test_no_rtti_binary_archive: vc-6_5 test_no_rtti_binary_archive_dll: vc-6_5 test_no_rtti_text_archive: vc-6_5 test_no_rtti_text_archive_dll: vc-6_5 test_no_rtti_text_warchive: vc-6_5 test_no_rtti_text_warchive_dll: vc-6_5 test_no_rtti_xml_archive: vc-6_5 test_no_rtti_xml_archive_dll: vc-6_5 test_no_rtti_xml_warchive: vc-6_5 test_no_rtti_xml_warchive_dll: vc-6_5 test_non_default_ctor2_text_archive: vc-7_1 test_non_default_ctor2_text_archive_dll: vc-7_1 test_non_default_ctor_text_archive: vc-7_1 test_non_default_ctor_text_archive_dll: vc-7_1 test_non_intrusive_text_archive: vc-7_1 test_non_intrusive_text_archive_dll: vc-7_1 test_null_ptr_text_archive: vc-7_1 test_null_ptr_text_archive_dll: vc-7_1 test_object_text_archive: vc-7_1 test_object_text_archive_dll: vc-7_1 test_polymorphic_binary_archive: cw-9_5-darwin test_polymorphic_binary_archive_dll: cw-9_5-darwin test_polymorphic_text_archive: cw-9_5-darwin test_polymorphic_text_warchive: cw-9_5-darwin test_polymorphic_xml_archive: cw-9_5-darwin test_polymorphic_xml_warchive: cw-9_5-darwin test_primitive_text_archive: vc-7_1 test_primitive_text_archive_dll: vc-7_1 test_private_ctor: cw-9_5-darwin test_registered_text_archive: vc-7_1 test_registered_text_archive_dll: vc-7_1 test_reset_object_address: cw-9_5-darwin test_set_binary_archive: cw-9_5-darwin test_set_binary_archive_dll: cw-9_5-darwin test_set_text_archive: cw-9_5-darwin test_set_text_warchive: cw-9_5-darwin test_set_xml_archive: cw-9_5-darwin test_set_xml_warchive: cw-9_5-darwin test_shared_ptr_132_binary_archive: vc-6_5 vc-6_5-stlport test_shared_ptr_132_binary_archive_dll: vc-6_5 test_shared_ptr_132_text_archive: vc-6_5 vc-6_5-stlport test_shared_ptr_132_text_archive_dll: gcc-3_4_3-sunos vc-6_5 test_shared_ptr_132_text_warchive: vc-6_5 vc-6_5-stlport test_shared_ptr_132_text_warchive_dll: vc-6_5 test_shared_ptr_132_xml_archive: vc-6_5 vc-6_5-stlport test_shared_ptr_132_xml_archive_dll: vc-6_5 test_shared_ptr_132_xml_warchive: vc-6_5 vc-6_5-stlport test_shared_ptr_132_xml_warchive_dll: vc-6_5 test_shared_ptr_binary_archive: borland-5_6_4 vc-6_5 test_shared_ptr_binary_archive_dll: borland-5_6_4 vc-6_5 test_shared_ptr_text_archive: borland-5_6_4 vc-6_5 test_shared_ptr_text_archive_dll: borland-5_6_4 vc-6_5 test_shared_ptr_text_warchive: borland-5_6_4 vc-6_5 test_shared_ptr_text_warchive_dll: borland-5_6_4 vc-6_5 test_shared_ptr_xml_archive: borland-5_6_4 vc-6_5 test_shared_ptr_xml_archive_dll: borland-5_6_4 vc-6_5 test_shared_ptr_xml_warchive: borland-5_6_4 vc-6_5 test_shared_ptr_xml_warchive_dll: borland-5_6_4 vc-6_5 test_split_text_archive: vc-7_1 test_split_text_archive_dll: vc-7_1 test_split_text_warchive: gcc-3_4_3-sunos test_tracking_text_archive: vc-7_1 test_tracking_text_archive_dll: vc-7_1 test_unregistered_binary_archive: gcc-3.2.3-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux test_unregistered_binary_archive_dll: gcc-3.2.3-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux test_unregistered_text_archive: gcc-3.2.3-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1 test_unregistered_text_archive_dll: gcc-3.2.3-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1 test_unregistered_xml_archive: gcc-3.2.3-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux test_unregistered_xml_archive_dll: gcc-3.2.3-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux test_unregistered_xml_warchive: gcc-4.0.1-linux test_unregistered_xml_warchive_dll: gcc-4.0.1-linux test_variant_binary_archive: cw-9_5-darwin test_variant_binary_archive_dll: cw-9_5-darwin test_variant_text_archive: cw-9_5-darwin test_variant_text_warchive: cw-9_5-darwin test_variant_xml_archive: cw-9_5-darwin test_variant_xml_warchive: cw-9_5-darwin test_vector_binary_archive: cw-9_5-darwin test_vector_binary_archive_dll: cw-9_5-darwin test_vector_text_archive: cw-9_5-darwin test_vector_text_warchive: cw-9_5-darwin test_vector_xml_archive: cw-9_5-darwin test_vector_xml_warchive: cw-9_5-darwin test_void_cast: gcc-3_4_3-sunos test_void_cast_dll: gcc-3_4_3-sunos |wave| test_re2c_lexer: cw-9_4 test_slex_lexer: cw-9_4 testwave: cw-9_4 gcc-3.4.4-linux gcc-3_4_3-sunos gcc-4.0.1-linux

1 0

Boost regression notification (2005-10-07 [HEAD])
by Douglas Gregor 07 Oct '05

07 Oct '05

Boost regression test failures ------------------------------ Report time: 2005-10-07T05:00:16Z This report lists all regression test failures on release platforms. Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-HEAD/developer/issues… 105 failures in 11 libraries: concept_check (13) foreach (1) functional/hash (1) graph (2) mpl (1) parameter (13) serialization (40) spirit (8) thread (4) tuple (1) typeof (21) |concept_check| stl_concept_covering: cw-9_4 gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin intel-win32-9_0 intel-win32-9_0 mingw-3_4_2 msvc vc-7_1 |foreach| user_defined: msvc |functional/hash| container_fwd_test: msvc |graph| graphviz_test: vc-7_1 layout_test: intel-win32-9_0 |mpl| size_t: gcc-4_0-darwin |parameter| basics: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux efficiency: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux msvc macros: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux sfinae: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux msvc unnamed: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux vc-7_1 |serialization| test_class_info_load_binary_archive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_binary_archive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_archive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_archive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_warchive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_warchive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_archive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_archive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_warchive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_warchive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_const_save_fail1: msvc test_const_save_fail2: msvc test_const_save_fail3: msvc test_demo_auto_ptr: vc-7_1 test_demo_exception: vc-7_1 test_demo_fast_archive: vc-7_1 test_demo_fast_archive_dll: vc-7_1 test_map_binary_archive_dll: msvc test_map_text_archive_dll: msvc test_map_text_warchive_dll: msvc |spirit| action_tests_debug: gcc-3_4_3-sunos distinct_tests_debug: gcc-3_4_3-sunos escape_char_parser_tests_debug: gcc-3_4_3-sunos grammar_def_test_debug: gcc-3_4_3-sunos switch_problem_debug: gcc-3_4_3-sunos switch_tests_single_debug: gcc-3_4_3-sunos traverse_tests: intel-win32-9_0 traverse_tests_debug: intel-win32-9_0 |thread| test_condition: gcc-3_4_3-sunos test_mutex: gcc-3_4_3-sunos test_tss: gcc-3_4_3-sunos gcc-3_4_3-sunos |tuple| tuple_test_bench: gcc-3_4_3-sunos |typeof| data_member_native: cw-9_4 function_native: cw-9_4 msvc function_ptr_native: cw-9_4 function_ref_native: cw-9_4 lvalue_native: cw-9_4 msvc member_function_native: cw-9_4 modifiers_emulation: cw-9_4 modifiers_native: cw-9_4 noncopyable_native: cw-9_4 std_emulation: cw-9_4 std_native: cw-9_4 template_dependent_native: cw-9_4 template_enum_native: cw-9_4 template_int_native: cw-9_4 template_multiword_native: cw-9_4 template_tpl_native: cw-9_4 msvc template_type_native: cw-9_4 type_native: cw-9_4

1 0

Who's Using Boost?
by Andreas Pokorny 07 Oct '05

07 Oct '05

Hi, Just found another boost open source user, I could not yet find any statement about which libraries they use. The berlios svn-view service seems to be out of order Yake - http://www.yake.org/ The Yake Engine is a component-based, object-oriented engine written in C++ and primarily designed for VR applications and games. It abstracts typical low-level and middleware APIs and provides various low, mid and application level functionality as well as tools to create and import content. Who is updateing the "Who's Using Boost" page? "Last revised: August 05, 2005 at 12:40:04 GMT" I think it deserves a update. Regards Andreas Pokorny

3 4

About timedlock....
by Boost 07 Oct '05

07 Oct '05

Hi, I want to port program from vc.net to evc4, but the method timedlock has some problem on evc4.....error message as below: boost/thread/detail/lock.hpp(44) : error C2143: syntax error : missing ',' before '&' it seems that wince doesn't support the method timedlock.. I have no idea how to deal with it? Any suggestion? Best Regards.

4 3

About timedlock....
by Tony 07 Oct '05

07 Oct '05

Hi, I want to port program from vc.net to evc4, but the method timedlock has some problem on evc4.....error message as below: boost/thread/detail/lock.hpp(44) : error C2143: syntax error : missing ',' before '&' it seems that wince doesn't support the method timedlock.. I have no idea how to deal with it? Any suggestion? Best Regards.

1 0

Feature request: exception filter for Boost.Bind
by Alex Besogonov 07 Oct '05

07 Oct '05

Hello, world! Today I was browsing RSDN (Russian Software Developer Network) forums and found a great trick for exception handling (http://rsdn.ru/Forum/Message.aspx?mid=1420259&only=1) ============== void TheFunction() { try { ... } catch(...) { ExceptionFilter(); } } void ExceptionFilter() { try { throw; } catch(Exception1 const& e) { //Blah-blah 1 } catch(Exception2 const& e) { //Blah-blah 2 } catch(Exception3 const& e) { //Blah-blah 3 } catch(Exception4 const& e) { //Blah-blah 4 } catch(Exception5 const& e) { throw; //Just rethrow } catch(...) { //Something other } } ============== It turns out that this trick is explicitly permitted by the Standard (as it was pointed in this post: http://rsdn.ru/Forum/Message.aspx?mid=1420469&only=1) I think this trick can be really helpful in conjunction with Boost.Bind. It would be great to write something like this: ==================== boost::function<void()> func= boost::bind_with_filter(&SomeObj::func1,obj,logging_filter()); ==================== If SomeObj::func1 throws an exception then logging_filter will write it into the application's log and suppress its further propagation. Or another use-case: ==================== boost::function<void()> func=boost::bind_with_filter(&ComObject1::func,obj,com_error_translator()); ==================== com_error_translator will translate exceptions from Microsoft's _com_error to something like std::runtime_error. -- With respect, Alex Besogonov(cyberax(a)elewise.com)

2 1

About timedlock....
by Boost 07 Oct '05

07 Oct '05

Hi, I want to port program from vc.net to evc4, but the method timedlock has some problem on evc4..... error message as below: boost/thread/detail/lock.hpp(44) : error C2143: syntax error : missing ',' before '&' it seems that wince doesn't support the method timedlock.. I have no idea how to deal with it? Any suggestion? Best Regards.

1 0

bounded_blocking_queue, unbounded_blocking_queue
by Peter Dimov 07 Oct '05

07 Oct '05

Hello, I've been tasked to implement approximate C++ equivalents of http://java.sun.com/j2se/1.5.0/docs/api/java/util/concurrent/ArrayBlockingQ… http://java.sun.com/j2se/1.5.0/docs/api/java/util/concurrent/LinkedBlocking… http://java.sun.com/j2se/1.5.0/docs/api/java/util/concurrent/ConcurrentHash… (and I'm generously allowed to use the Boost license.) What I have so far is (synopsis): template<class V> class bounded_blocking_queue { public: // exclusive access explicit bounded_blocking_queue( size_t n ); ~bounded_blocking_queue(); // queries size_t size() const; // aproximate queue size // non-blocking bool try_push( V const & v ); bool try_pop( V & v ); // blocking void push( V const & v ); void pop( V & v ); }; with a "reference" two-lock implementation at http://www.pdimov.com/cpp/bounded_blocking_queue.cpp (with at least one race condition and at least two visibility bugs, but still...) and: template<class V> class unbounded_blocking_queue { explicit unbounded_blocking_queue(); ~unbounded_blocking_queue(); // non-blocking void push( V const & v ); bool try_pop( V & v ); // blocking void pop( V & v ); }; with a two-lock implementation at http://www.pdimov.com/cpp/unbounded_blocking_queue.cpp I appreciate any comments on the interface, the implementation, or whether it'd be a good idea to include these components in Boost.Threads. Thanks in advance for any feedback. Incidentally, I want to join the "catch(...) in thread_proxy is EVIL" camp. While developing these queues the catch(...) clause ate all access violations, transforming them into different access violations in totally unrelated parts of the code, making debugging a pain. I've removed the catch(...) in my local copy, and I think that we need to do the same in the CVS. Oh, and comments about the interface of the concurrent hash map are very much appreciated; my current line of thinking is that the only operation that is allowed to invalidate should be rehash() and it'd be the user's responsibility to call it during "quiet" periods when no other thread is holding an iterator or is inserting/removing elements. But if you have a better idea, please let me know! -- Peter Dimov http://www.pdimov.com

4 10

is something seriously wrong with zero_vector?
by Neal Becker 06 Oct '05

06 Oct '05

I noticed that creating a zero_vector with some size, and then iterating over it produced strange results. Then I noticed this: BOOST_UBLAS_INLINE const_iterator begin () const { return const_iterator (*this); } BOOST_UBLAS_INLINE const_iterator end () const { return const_iterator (*this); } Excuse me? Doesn't this mean begin() == end() and effectively size is always zero?

1 1

Boost regression notification (2005-10-04 [RC_1_33_0])
by Douglas Gregor 06 Oct '05

06 Oct '05

Boost regression test failures ------------------------------ Report time: 2005-10-04T15:03:13Z This report lists all regression test failures on release platforms. Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-RC_1_33_0/developer/i… 226 failures in 6 libraries: foreach (1) iostreams (13) multi_index (1) range (3) serialization (202) wave (6) |foreach| rvalue_const: vc-7_1 |iostreams| gzip_test: cw-9_5-darwin gcc-2.95.3-stlport-4.6.2-linux gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin gcc-3_4_3-sunos gcc-4.0.1-linux gcc-4_0-darwin intel-8.1-linux intel-9.0-linux mingw-3_4_2 vc-7_1 |multi_index| test_serialization: cw-9_5-darwin |range| array: vc-6_5 vc-6_5-stlport vc-7_0 |serialization| test_binary_text_archive: vc-7_1 test_binary_text_archive_dll: vc-7_1 test_class_info_save_text_archive: vc-7_1 test_class_info_save_text_archive_dll: vc-7_1 test_delete_pointer_binary_archive: cw-9_5-darwin test_delete_pointer_binary_archive_dll: cw-9_5-darwin test_delete_pointer_text_archive: cw-9_5-darwin test_delete_pointer_text_warchive: cw-9_5-darwin test_delete_pointer_xml_archive: cw-9_5-darwin test_delete_pointer_xml_warchive: cw-9_5-darwin test_demo_polymorphic: cw-9_5-darwin test_demo_xml_load: gcc-3_3-darwin gcc-4_0-darwin intel-win32-8_1 test_demo_xml_load_dll: gcc-3_3-darwin gcc-4_0-darwin test_deque_binary_archive: cw-9_5-darwin test_deque_binary_archive_dll: cw-9_5-darwin test_deque_text_archive: cw-9_5-darwin test_deque_text_warchive: cw-9_5-darwin test_deque_xml_archive: cw-9_5-darwin test_deque_xml_warchive: cw-9_5-darwin test_derived_text_archive: vc-7_1 test_derived_text_archive_dll: vc-7_1 test_exported_binary_archive: gcc-3.2.3-linux gcc-4.0.1-linux intel-9.0-linux vc-6_5 test_exported_binary_archive_dll: gcc-4.0.1-linux vc-6_5 test_exported_text_archive: gcc-3.2.3-linux gcc-4.0.1-linux vc-6_5 vc-7_1 test_exported_text_archive_dll: gcc-3.2.3-linux gcc-4.0.1-linux vc-6_5 vc-7_1 test_exported_text_warchive: gcc-4.0.1-linux vc-6_5 test_exported_text_warchive_dll: gcc-4.0.1-linux vc-6_5 test_exported_xml_archive: gcc-4.0.1-linux intel-8.1-linux vc-6_5 test_exported_xml_archive_dll: gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-6_5 test_exported_xml_warchive: gcc-3.2.3-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-6_5 test_exported_xml_warchive_dll: gcc-3.2.3-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-6_5 test_list_binary_archive: cw-9_5-darwin test_list_binary_archive_dll: cw-9_5-darwin test_list_ptrs_binary_archive: cw-9_5-darwin test_list_ptrs_binary_archive_dll: cw-9_5-darwin test_list_ptrs_text_archive: cw-9_5-darwin test_list_ptrs_text_warchive: cw-9_5-darwin test_list_ptrs_xml_archive: cw-9_5-darwin test_list_ptrs_xml_warchive: cw-9_5-darwin test_list_ptrs_xml_warchive_dll: gcc-3_4_3-sunos test_list_text_archive: cw-9_5-darwin test_list_text_warchive: cw-9_5-darwin test_list_xml_archive: cw-9_5-darwin test_list_xml_warchive: cw-9_5-darwin test_map_binary_archive: cw-9_5-darwin test_map_binary_archive_dll: cw-9_5-darwin test_map_text_archive: cw-9_5-darwin gcc-3_4_3-sunos test_map_text_warchive: cw-9_5-darwin test_map_xml_archive: cw-9_5-darwin test_map_xml_warchive: cw-9_5-darwin test_mi_text_archive: vc-7_1 test_mi_text_archive_dll: vc-7_1 test_no_rtti_binary_archive: vc-6_5 test_no_rtti_binary_archive_dll: vc-6_5 test_no_rtti_text_archive: vc-6_5 test_no_rtti_text_archive_dll: vc-6_5 test_no_rtti_text_warchive: vc-6_5 test_no_rtti_text_warchive_dll: vc-6_5 test_no_rtti_xml_archive: vc-6_5 test_no_rtti_xml_archive_dll: vc-6_5 test_no_rtti_xml_warchive: vc-6_5 test_no_rtti_xml_warchive_dll: vc-6_5 test_non_default_ctor2_text_archive: vc-7_1 test_non_default_ctor2_text_archive_dll: vc-7_1 test_non_default_ctor_text_archive: vc-7_1 test_non_default_ctor_text_archive_dll: vc-7_1 test_non_intrusive_text_archive: vc-7_1 test_non_intrusive_text_archive_dll: vc-7_1 test_null_ptr_text_archive: vc-7_1 test_null_ptr_text_archive_dll: vc-7_1 test_object_text_archive: vc-7_1 test_object_text_archive_dll: vc-7_1 test_polymorphic_binary_archive: cw-9_5-darwin test_polymorphic_binary_archive_dll: cw-9_5-darwin test_polymorphic_text_archive: cw-9_5-darwin test_polymorphic_text_warchive: cw-9_5-darwin test_polymorphic_xml_archive: cw-9_5-darwin test_polymorphic_xml_warchive: cw-9_5-darwin test_primitive_text_archive: vc-7_1 test_primitive_text_archive_dll: vc-7_1 test_private_ctor: cw-9_5-darwin test_registered_text_archive: vc-7_1 test_registered_text_archive_dll: vc-7_1 test_reset_object_address: cw-9_5-darwin test_set_binary_archive: cw-9_5-darwin test_set_binary_archive_dll: cw-9_5-darwin test_set_text_archive: cw-9_5-darwin test_set_text_warchive: cw-9_5-darwin test_set_xml_archive: cw-9_5-darwin test_set_xml_warchive: cw-9_5-darwin test_shared_ptr_132_binary_archive: vc-6_5 vc-6_5-stlport test_shared_ptr_132_binary_archive_dll: vc-6_5 test_shared_ptr_132_text_archive: vc-6_5 vc-6_5-stlport test_shared_ptr_132_text_archive_dll: gcc-3_4_3-sunos vc-6_5 test_shared_ptr_132_text_warchive: vc-6_5 vc-6_5-stlport test_shared_ptr_132_text_warchive_dll: vc-6_5 test_shared_ptr_132_xml_archive: vc-6_5 vc-6_5-stlport test_shared_ptr_132_xml_archive_dll: vc-6_5 test_shared_ptr_132_xml_warchive: vc-6_5 vc-6_5-stlport test_shared_ptr_132_xml_warchive_dll: vc-6_5 test_shared_ptr_binary_archive: borland-5_6_4 vc-6_5 test_shared_ptr_binary_archive_dll: borland-5_6_4 vc-6_5 test_shared_ptr_text_archive: borland-5_6_4 vc-6_5 test_shared_ptr_text_archive_dll: borland-5_6_4 vc-6_5 test_shared_ptr_text_warchive: borland-5_6_4 vc-6_5 test_shared_ptr_text_warchive_dll: borland-5_6_4 vc-6_5 test_shared_ptr_xml_archive: borland-5_6_4 vc-6_5 test_shared_ptr_xml_archive_dll: borland-5_6_4 vc-6_5 test_shared_ptr_xml_warchive: borland-5_6_4 vc-6_5 test_shared_ptr_xml_warchive_dll: borland-5_6_4 vc-6_5 test_split_text_archive: vc-7_1 test_split_text_archive_dll: vc-7_1 test_split_text_warchive: gcc-3_4_3-sunos test_tracking_text_archive: vc-7_1 test_tracking_text_archive_dll: vc-7_1 test_unregistered_binary_archive: gcc-3.2.3-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux test_unregistered_binary_archive_dll: gcc-3.2.3-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux test_unregistered_text_archive: gcc-3.2.3-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1 test_unregistered_text_archive_dll: gcc-3.2.3-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1 test_unregistered_xml_archive: gcc-3.2.3-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux test_unregistered_xml_archive_dll: gcc-3.2.3-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux test_unregistered_xml_warchive: gcc-4.0.1-linux test_unregistered_xml_warchive_dll: gcc-4.0.1-linux test_variant_binary_archive: cw-9_5-darwin test_variant_binary_archive_dll: cw-9_5-darwin test_variant_text_archive: cw-9_5-darwin test_variant_text_warchive: cw-9_5-darwin test_variant_xml_archive: cw-9_5-darwin test_variant_xml_warchive: cw-9_5-darwin test_vector_binary_archive: cw-9_5-darwin test_vector_binary_archive_dll: cw-9_5-darwin test_vector_text_archive: cw-9_5-darwin test_vector_text_warchive: cw-9_5-darwin test_vector_xml_archive: cw-9_5-darwin test_vector_xml_warchive: cw-9_5-darwin test_void_cast: gcc-3_4_3-sunos test_void_cast_dll: gcc-3_4_3-sunos |wave| test_re2c_lexer: cw-9_4 test_slex_lexer: cw-9_4 testwave: cw-9_4 gcc-3.4.4-linux gcc-3_4_3-sunos gcc-4.0.1-linux

4 3

Boost regression notification (2005-10-06 [HEAD])
by Douglas Gregor 06 Oct '05

06 Oct '05

Boost regression test failures ------------------------------ Report time: 2005-10-06T05:00:07Z This report lists all regression test failures on release platforms. Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-HEAD/developer/issues… 105 failures in 11 libraries: concept_check (13) foreach (1) functional/hash (1) graph (2) mpl (1) parameter (13) serialization (40) spirit (8) thread (4) tuple (1) typeof (21) |concept_check| stl_concept_covering: cw-9_4 gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin intel-win32-9_0 intel-win32-9_0 mingw-3_4_2 msvc vc-7_1 |foreach| user_defined: msvc |functional/hash| container_fwd_test: msvc |graph| graphviz_test: vc-7_1 layout_test: intel-win32-9_0 |mpl| size_t: gcc-4_0-darwin |parameter| basics: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux efficiency: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux msvc macros: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux sfinae: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux msvc unnamed: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux vc-7_1 |serialization| test_class_info_load_binary_archive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_binary_archive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_archive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_archive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_warchive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_warchive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_archive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_archive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_warchive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_warchive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_const_save_fail1: msvc test_const_save_fail2: msvc test_const_save_fail3: msvc test_demo_auto_ptr: vc-7_1 test_demo_exception: vc-7_1 test_demo_fast_archive: vc-7_1 test_demo_fast_archive_dll: vc-7_1 test_map_binary_archive_dll: msvc test_map_text_archive_dll: msvc test_map_text_warchive_dll: msvc |spirit| action_tests_debug: gcc-3_4_3-sunos distinct_tests_debug: gcc-3_4_3-sunos escape_char_parser_tests_debug: gcc-3_4_3-sunos grammar_def_test_debug: gcc-3_4_3-sunos switch_problem_debug: gcc-3_4_3-sunos switch_tests_single_debug: gcc-3_4_3-sunos traverse_tests: intel-win32-9_0 traverse_tests_debug: intel-win32-9_0 |thread| test_condition: gcc-3_4_3-sunos test_mutex: gcc-3_4_3-sunos test_tss: gcc-3_4_3-sunos gcc-3_4_3-sunos |tuple| tuple_test_bench: gcc-3_4_3-sunos |typeof| data_member_native: cw-9_4 function_native: cw-9_4 msvc function_ptr_native: cw-9_4 function_ref_native: cw-9_4 lvalue_native: cw-9_4 msvc member_function_native: cw-9_4 modifiers_emulation: cw-9_4 modifiers_native: cw-9_4 noncopyable_native: cw-9_4 std_emulation: cw-9_4 std_native: cw-9_4 template_dependent_native: cw-9_4 template_enum_native: cw-9_4 template_int_native: cw-9_4 template_multiword_native: cw-9_4 template_tpl_native: cw-9_4 msvc template_type_native: cw-9_4 type_native: cw-9_4

1 0

Re: [boost] Suggest who's developer information on more/getting_s tarted.html
by Martin Bonner 06 Oct '05

06 Oct '05

----Original Message---- From: Larry Evans [mailto:cppljevans@cox-internet.com] Sent: 06 October 2005 14:47 To: boost(a)lists.boost.org Subject: [boost] Suggest who's developer information on more/getting_started.html > PROBLEM: > > I had been a sandbox cvs developer, but I was unsure if that > also made me main cvs developer. This resulted in several > emails between me and mailto:boost-owner@lists.boost.org > before things were cleared up. > > SUGGESTED SOLUTION: > > apply the attached patch to: > > http://www.boost.org/more/getting_started.html > > This makes clear who has write access to the main cvs. > > FEEDBACK: > > Please let me know within the next 10 days if there are any objections > to this patch. If there are no objections, I will apply the patch > on day 11. > > TIA. There seem to be an AWFUL lot of changes in there that do not appear to have anything to do with clarifying who has write access to the main CVS. In fact, there are so many changes, I couldn't see what the visual change would be! Many of the changes seem to be changing between relative and absolute pathname, some are attributes reordered on elements, some are changes to the capitalization of elements. Have you used some sort of "smart" HTML editor that has reformatted the HTML under your feet? Alternatively, have you made your change to an old version of the text and Rene (or somebody) has tidied things up since? -- Martin Bonner Martin.Bonner(a)Pitechnology.com Pi Technology, Milton Hall, Ely Road, Milton, Cambridge, CB4 6WZ, ENGLAND Tel: +44 (0)1223 441434

2 1

Re: [boost] GUI coordinate units (Was: GUI foundations)
by Martin Bonner 06 Oct '05

06 Oct '05

----Original Message---- From: Joel de Guzman [mailto:joel@boost-consulting.com] Sent: 06 October 2005 02:59 To: boost(a)lists.boost.org Subject: Re: [boost] GUI coordinate units (Was: GUI foundations) > Stefan Seefeld wrote: >> Dave Harris wrote: >> >> >>> Why millimeter rather than inch or point? For text, there is a >>> strong argument for using imperial rather than metric units. A >>> point is 1/72th of an inch, so it converts nicely. Points don't >>> convert so well to millimeters. > > A point is simply 0.35277777777777777777777777777778 millimeters :-) So should we use boost::rational to store the positions? Then a point is 254/720 millimetres. Incidentally, the UK changed the legal definition of an inch to 25.4mm in (I think) the 50's. Does the US use the same definition, or a subtly different one? -- Martin Bonner Martin.Bonner(a)Pitechnology.com Pi Technology, Milton Hall, Ely Road, Milton, Cambridge, CB4 6WZ, ENGLAND Tel: +44 (0)1223 441434

1 0

Re: [boost] GUI coordinate units (Was: GUI foundations)
by brangdon＠cix.compulink.co.uk 06 Oct '05

06 Oct '05

In-Reply-To: <di0kc7$6th$1(a)sea.gmane.org> joel(a)boost-consulting.com (Joel de Guzman) wrote (abridged): > IMO, we should choose one representation and one unit. In my mind, > that would be float and millimeter (in addition to percentages). Why float rather than double? Generally picking float is an optimisation, and often a premature one. Sooner or later I think you will need the extra precision of double, and then you'll have an unnecessary conversion - possibly two, if the native device uses ints. Double => float => int. Why millimeter rather than inch or point? For text, there is a strong argument for using imperial rather than metric units. A point is 1/72th of an inch, so it converts nicely. Points don't convert so well to millimeters. Also, PDF and Postscript are points-oriented. I wouldn't buck the trend without a good reason. -- Dave Harris, Nottingham, UK.

3 2

Re: [boost] Boost Digest, Vol 1236, Issue 3
by Reed Kotler 05 Oct '05

05 Oct '05

thanks but it's not in 1.33.0. I have that version and it's not fixed there. maybe some later patch. I see that it's fixed at this URL you mention. Reed Kotler wrote: > I am working on getting a new compiler to work with BOOST. > > I'm getting an error compilng > graphviz_graph_parser.cppI am getting that "free" is undefined and the > error > seems legitmate but there are apparently other compilers failing due to > this > same problem so maybe there is something tricky here.free is wrapped so > it's in std but it is not visible at the point in the code. That was fixed 4 months ago... http://tinyurl.com/9doxw ...And is available if you use Boost 1.33.0.

2 2

Re: [boost] GUI coordinate units (Was: GUI foundations)
by brangdon＠cix.compulink.co.uk 05 Oct '05

05 Oct '05

In-Reply-To: <4342AC3C.1060100(a)sympatico.ca> seefeld(a)sympatico.ca (Stefan Seefeld) wrote (abridged): > Exactly. To be clear: moving from a 15" to a 17" monitor would, in my > ideal world, have *no* impact on the physical size of the displayed > graphics, but rather, would add ~ 1.4" in both dimensions to the useful > screen area. How many pixels your display has then only affects the > quality of the rendering, exactly as what you were looking for. Isn't that quite hard? Specifically, it sounds rather like the problem of drawing text nicely at various resolutions. Consider TrueType, or Type 1 Postscript fonts. The basic character shape is defined by vectors, by Bezier curves. To render it prettily, so that, for example, all the vertical strokes on an 'm' are the same thickness regardless of how the letter falls onto the pixel grid, you need to add what Adobe call hints and Microsoft call grid-fitting. Are you intending this system to be usable only on high-res desktop machines? Or are you including hand-held devices, phones and wotnot, that have relatively slow CPUs and where 640x320 is ambitiously high resolution? There is some discussion about TrueType grid-fitting about half-way down this page: http://www.microsoft.com/typography/otspec/TTCH01.htm > Of course, this requires a completely vector-graphics-based GUI, which > is still the exception. Maybe there's a reason for that. I'm not saying don't do it, but I'd recommend doing some experiments that prove it's actually possible before investing too much. -- Dave Harris, Nottingham, UK.

6 6

Boost regression notification (2005-10-05 [RC_1_33_0])
by Douglas Gregor 05 Oct '05

05 Oct '05

Boost regression test failures ------------------------------ Report time: 2005-10-05T14:35:12Z This report lists all regression test failures on release platforms. Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-RC_1_33_0/developer/i… 226 failures in 6 libraries: foreach (1) iostreams (13) multi_index (1) range (3) serialization (202) wave (6) |foreach| rvalue_const: vc-7_1 |iostreams| gzip_test: cw-9_5-darwin gcc-2.95.3-stlport-4.6.2-linux gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin gcc-3_4_3-sunos gcc-4.0.1-linux gcc-4_0-darwin intel-8.1-linux intel-9.0-linux mingw-3_4_2 vc-7_1 |multi_index| test_serialization: cw-9_5-darwin |range| array: vc-6_5 vc-6_5-stlport vc-7_0 |serialization| test_binary_text_archive: vc-7_1 test_binary_text_archive_dll: vc-7_1 test_class_info_save_text_archive: vc-7_1 test_class_info_save_text_archive_dll: vc-7_1 test_delete_pointer_binary_archive: cw-9_5-darwin test_delete_pointer_binary_archive_dll: cw-9_5-darwin test_delete_pointer_text_archive: cw-9_5-darwin test_delete_pointer_text_warchive: cw-9_5-darwin test_delete_pointer_xml_archive: cw-9_5-darwin test_delete_pointer_xml_warchive: cw-9_5-darwin test_demo_polymorphic: cw-9_5-darwin test_demo_xml_load: gcc-3_3-darwin gcc-4_0-darwin intel-win32-8_1 test_demo_xml_load_dll: gcc-3_3-darwin gcc-4_0-darwin test_deque_binary_archive: cw-9_5-darwin test_deque_binary_archive_dll: cw-9_5-darwin test_deque_text_archive: cw-9_5-darwin test_deque_text_warchive: cw-9_5-darwin test_deque_xml_archive: cw-9_5-darwin test_deque_xml_warchive: cw-9_5-darwin test_derived_text_archive: vc-7_1 test_derived_text_archive_dll: vc-7_1 test_exported_binary_archive: gcc-3.2.3-linux gcc-4.0.1-linux intel-9.0-linux vc-6_5 test_exported_binary_archive_dll: gcc-4.0.1-linux vc-6_5 test_exported_text_archive: gcc-3.2.3-linux gcc-4.0.1-linux vc-6_5 vc-7_1 test_exported_text_archive_dll: gcc-3.2.3-linux gcc-4.0.1-linux vc-6_5 vc-7_1 test_exported_text_warchive: gcc-4.0.1-linux vc-6_5 test_exported_text_warchive_dll: gcc-4.0.1-linux vc-6_5 test_exported_xml_archive: gcc-4.0.1-linux intel-8.1-linux vc-6_5 test_exported_xml_archive_dll: gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-6_5 test_exported_xml_warchive: gcc-3.2.3-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-6_5 test_exported_xml_warchive_dll: gcc-3.2.3-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-6_5 test_list_binary_archive: cw-9_5-darwin test_list_binary_archive_dll: cw-9_5-darwin test_list_ptrs_binary_archive: cw-9_5-darwin test_list_ptrs_binary_archive_dll: cw-9_5-darwin test_list_ptrs_text_archive: cw-9_5-darwin test_list_ptrs_text_warchive: cw-9_5-darwin test_list_ptrs_xml_archive: cw-9_5-darwin test_list_ptrs_xml_warchive: cw-9_5-darwin test_list_ptrs_xml_warchive_dll: gcc-3_4_3-sunos test_list_text_archive: cw-9_5-darwin test_list_text_warchive: cw-9_5-darwin test_list_xml_archive: cw-9_5-darwin test_list_xml_warchive: cw-9_5-darwin test_map_binary_archive: cw-9_5-darwin test_map_binary_archive_dll: cw-9_5-darwin test_map_text_archive: cw-9_5-darwin gcc-3_4_3-sunos test_map_text_warchive: cw-9_5-darwin test_map_xml_archive: cw-9_5-darwin test_map_xml_warchive: cw-9_5-darwin test_mi_text_archive: vc-7_1 test_mi_text_archive_dll: vc-7_1 test_no_rtti_binary_archive: vc-6_5 test_no_rtti_binary_archive_dll: vc-6_5 test_no_rtti_text_archive: vc-6_5 test_no_rtti_text_archive_dll: vc-6_5 test_no_rtti_text_warchive: vc-6_5 test_no_rtti_text_warchive_dll: vc-6_5 test_no_rtti_xml_archive: vc-6_5 test_no_rtti_xml_archive_dll: vc-6_5 test_no_rtti_xml_warchive: vc-6_5 test_no_rtti_xml_warchive_dll: vc-6_5 test_non_default_ctor2_text_archive: vc-7_1 test_non_default_ctor2_text_archive_dll: vc-7_1 test_non_default_ctor_text_archive: vc-7_1 test_non_default_ctor_text_archive_dll: vc-7_1 test_non_intrusive_text_archive: vc-7_1 test_non_intrusive_text_archive_dll: vc-7_1 test_null_ptr_text_archive: vc-7_1 test_null_ptr_text_archive_dll: vc-7_1 test_object_text_archive: vc-7_1 test_object_text_archive_dll: vc-7_1 test_polymorphic_binary_archive: cw-9_5-darwin test_polymorphic_binary_archive_dll: cw-9_5-darwin test_polymorphic_text_archive: cw-9_5-darwin test_polymorphic_text_warchive: cw-9_5-darwin test_polymorphic_xml_archive: cw-9_5-darwin test_polymorphic_xml_warchive: cw-9_5-darwin test_primitive_text_archive: vc-7_1 test_primitive_text_archive_dll: vc-7_1 test_private_ctor: cw-9_5-darwin test_registered_text_archive: vc-7_1 test_registered_text_archive_dll: vc-7_1 test_reset_object_address: cw-9_5-darwin test_set_binary_archive: cw-9_5-darwin test_set_binary_archive_dll: cw-9_5-darwin test_set_text_archive: cw-9_5-darwin test_set_text_warchive: cw-9_5-darwin test_set_xml_archive: cw-9_5-darwin test_set_xml_warchive: cw-9_5-darwin test_shared_ptr_132_binary_archive: vc-6_5 vc-6_5-stlport test_shared_ptr_132_binary_archive_dll: vc-6_5 test_shared_ptr_132_text_archive: vc-6_5 vc-6_5-stlport test_shared_ptr_132_text_archive_dll: gcc-3_4_3-sunos vc-6_5 test_shared_ptr_132_text_warchive: vc-6_5 vc-6_5-stlport test_shared_ptr_132_text_warchive_dll: vc-6_5 test_shared_ptr_132_xml_archive: vc-6_5 vc-6_5-stlport test_shared_ptr_132_xml_archive_dll: vc-6_5 test_shared_ptr_132_xml_warchive: vc-6_5 vc-6_5-stlport test_shared_ptr_132_xml_warchive_dll: vc-6_5 test_shared_ptr_binary_archive: borland-5_6_4 vc-6_5 test_shared_ptr_binary_archive_dll: borland-5_6_4 vc-6_5 test_shared_ptr_text_archive: borland-5_6_4 vc-6_5 test_shared_ptr_text_archive_dll: borland-5_6_4 vc-6_5 test_shared_ptr_text_warchive: borland-5_6_4 vc-6_5 test_shared_ptr_text_warchive_dll: borland-5_6_4 vc-6_5 test_shared_ptr_xml_archive: borland-5_6_4 vc-6_5 test_shared_ptr_xml_archive_dll: borland-5_6_4 vc-6_5 test_shared_ptr_xml_warchive: borland-5_6_4 vc-6_5 test_shared_ptr_xml_warchive_dll: borland-5_6_4 vc-6_5 test_split_text_archive: vc-7_1 test_split_text_archive_dll: vc-7_1 test_split_text_warchive: gcc-3_4_3-sunos test_tracking_text_archive: vc-7_1 test_tracking_text_archive_dll: vc-7_1 test_unregistered_binary_archive: gcc-3.2.3-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux test_unregistered_binary_archive_dll: gcc-3.2.3-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux test_unregistered_text_archive: gcc-3.2.3-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1 test_unregistered_text_archive_dll: gcc-3.2.3-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1 test_unregistered_xml_archive: gcc-3.2.3-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux test_unregistered_xml_archive_dll: gcc-3.2.3-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux test_unregistered_xml_warchive: gcc-4.0.1-linux test_unregistered_xml_warchive_dll: gcc-4.0.1-linux test_variant_binary_archive: cw-9_5-darwin test_variant_binary_archive_dll: cw-9_5-darwin test_variant_text_archive: cw-9_5-darwin test_variant_text_warchive: cw-9_5-darwin test_variant_xml_archive: cw-9_5-darwin test_variant_xml_warchive: cw-9_5-darwin test_vector_binary_archive: cw-9_5-darwin test_vector_binary_archive_dll: cw-9_5-darwin test_vector_text_archive: cw-9_5-darwin test_vector_text_warchive: cw-9_5-darwin test_vector_xml_archive: cw-9_5-darwin test_vector_xml_warchive: cw-9_5-darwin test_void_cast: gcc-3_4_3-sunos test_void_cast_dll: gcc-3_4_3-sunos |wave| test_re2c_lexer: cw-9_4 test_slex_lexer: cw-9_4 testwave: cw-9_4 gcc-3.4.4-linux gcc-3_4_3-sunos gcc-4.0.1-linux

1 0

Boost regression notification (2005-10-05 [HEAD])
by Douglas Gregor 05 Oct '05

05 Oct '05

Boost regression test failures ------------------------------ Report time: 2005-10-05T05:00:23Z This report lists all regression test failures on release platforms. WARNING: The following libraries have failing regression tests but do not have a maintainer on file. Once a maintainer is found, add an entry to libs/maintainers.txt to eliminate this message. utility/enable_if Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-HEAD/developer/issues… 137 failures in 13 libraries: concept_check (13) config (2) foreach (1) functional/hash (1) graph (2) mpl (1) parameter (13) serialization (36) spirit (8) thread (4) tuple (1) typeof (54) utility/enable_if (1) |concept_check| stl_concept_covering: cw-9_4 gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin intel-win32-9_0 intel-win32-9_0 mingw-3_4_2 msvc vc-7_1 |config| config_test: vc-7_1 limits_test: vc-7_1 |foreach| user_defined: msvc |functional/hash| container_fwd_test: msvc |graph| graphviz_test: vc-7_1 layout_test: intel-win32-9_0 |mpl| size_t: gcc-4_0-darwin |parameter| basics: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux efficiency: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux msvc macros: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux sfinae: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux msvc unnamed: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux vc-7_1 |serialization| test_class_info_load_binary_archive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_binary_archive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_archive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_archive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_warchive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_warchive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_archive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_archive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_warchive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_warchive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_const_save_fail1: msvc test_const_save_fail2: msvc test_const_save_fail3: msvc test_map_binary_archive_dll: msvc test_map_text_archive_dll: msvc test_map_text_warchive_dll: msvc |spirit| action_tests_debug: gcc-3_4_3-sunos distinct_tests_debug: gcc-3_4_3-sunos escape_char_parser_tests_debug: gcc-3_4_3-sunos grammar_def_test_debug: gcc-3_4_3-sunos switch_problem_debug: gcc-3_4_3-sunos switch_tests_single_debug: gcc-3_4_3-sunos traverse_tests: intel-win32-9_0 traverse_tests_debug: intel-win32-9_0 |thread| test_condition: gcc-3_4_3-sunos test_mutex: gcc-3_4_3-sunos test_tss: gcc-3_4_3-sunos gcc-3_4_3-sunos |tuple| tuple_test_bench: gcc-3_4_3-sunos |typeof| data_member_native: cw-9_4 intel-win32-9_0 intel-win32-9_0 function_native: cw-9_4 intel-win32-9_0 intel-win32-9_0 msvc function_ptr_native: cw-9_4 intel-win32-9_0 intel-win32-9_0 function_ref_native: cw-9_4 intel-win32-9_0 intel-win32-9_0 lvalue_native: cw-9_4 intel-win32-9_0 intel-win32-9_0 msvc member_function_native: cw-9_4 intel-win32-9_0 intel-win32-9_0 modifiers_emulation: cw-9_4 modifiers_native: cw-9_4 intel-win32-9_0 intel-win32-9_0 noncopyable_native: cw-9_4 intel-win32-9_0 intel-win32-9_0 odr_native: intel-win32-9_0 std_emulation: cw-9_4 std_native: cw-9_4 intel-win32-9_0 intel-win32-9_0 template_dependent_native: cw-9_4 intel-win32-9_0 intel-win32-9_0 template_enum_native: cw-9_4 intel-win32-9_0 intel-win32-9_0 template_int_native: cw-9_4 intel-win32-9_0 intel-win32-9_0 template_multiword_native: cw-9_4 intel-win32-9_0 intel-win32-9_0 template_tpl_native: cw-9_4 intel-win32-9_0 intel-win32-9_0 msvc template_type_native: cw-9_4 intel-win32-9_0 intel-win32-9_0 type_native: cw-9_4 intel-win32-9_0 intel-win32-9_0 |utility/enable_if| namespace_disambiguation: vc-7_1

1 0

graphviz
by Reed Kotler 05 Oct '05

05 Oct '05

I am working on getting a new compiler to work with BOOST. I'm getting an error compilng graphviz_graph_parser.cppI am getting that "free" is undefined and the error seems legitmate but there are apparently other compilers failing due to this same problem so maybe there is something tricky here.free is wrapped so it's in std but it is not visible at the point in the code.

2 1

Fwd from ms.p.vc.l: Boost with VC6
by Jeff Flinn 05 Oct '05

05 Oct '05

Just an FYI related to first time boost users efforts at installation. I'm forwarding this from microsoft.public.vc.language. I've answered this to the best of my abilities in that thread, and suggested that the OP join the boost.user list. Jeff "andré m.a" <a.m.a(a)videotron.ca> wrote in message news:%2%_e.4643$f_3.44986@weber.videotron.net... > hi there. > > It's been suggested my many that i use Boost libraries. > So i went to boost.org and downloaded the win32 files. > Unziped the boost folder into : > C:\Program Files\Microsoft Visual Studio\VC98\Include\ > > even added the boost directory in the IDE using : > tools>options>directories... > > I read the docs at boost and it says that for VC6 the files > (hpp) should work as is, but every time i try to compile > something im missing static libraries like : > libboost_program_options-vc6-sgd-1_33.lib is missing. > > Wich even google in its vast DB entries is unable to > produce a single hit for. > > Then again MSDN is discouraging using VC6 and suggest > i spend a lot of money for a .Net :-} > ( very amusing ) > > Any tips would be gigantically helpfull.

2 1

Re: [boost] GUI coordinate units (Was: GUI foundations)
by Martin Bonner 05 Oct '05

05 Oct '05

----Original Message---- From: Stefan Seefeld [mailto:seefeld@sympatico.ca] Sent: 04 October 2005 14:35 To: boost(a)lists.boost.org Subject: Re: [boost] GUI coordinate units (Was: GUI foundations) > Sizes are usually given in resolution-dependent coordinates (i.e. > pixels). If you change resolution, you typically don't do that to > expose more detail, but to make your desktop 'bigger' (by making > text, widgets, etc. smaller). This seems to be a common view among developers. I can only assume they are all still young with excellent eyesight. When I moved from 800x600 to 1024x768 what I really wanted was less fuzzy letters (not more letters). I moved from 1024x768 to 1280x1024 because I got given a 17" LCD monitor. Windows-XP doesn't make a bad fist of scaling everything back again to a reasonable size, but a lot of GUIs get a bit messed up because people have done everything in pixels rather than scalable graphics. -- Martin Bonner Martin.Bonner(a)Pitechnology.com Pi Technology, Milton Hall, Ely Road, Milton, Cambridge, CB4 6WZ, ENGLAND Tel: +44 (0)1223 441434

5 6

[Boost-bugs] [ boost-Bugs-1313543 ] range, VC 7.1, compile error.
by SourceForge.net 05 Oct '05

05 Oct '05

Bugs item #1313543, was opened at 2005-10-05 16:29 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=107586&aid=1313543&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Sergey Shandar (sergey_shandar) Assigned to: Nobody/Anonymous (nobody) Summary: range, VC 7.1, compile error. Initial Comment: Compiler: VC 7.1 Example: --------- #include <boost/range/iterator.hpp> template<class Container> typename boost::range_iterator<const Container>::type begin(const Container &X) { return 0; } int main() { char a[3]; int b = begin(a); return 0; } --------- The compile-time error message is --------- c:\Boost\include\boost-1_33\boost\range\iterator.hpp(37) : error C2825: 'C::iterator': cannot form a qualified name main.cpp(12) : see reference to class template instantiation 'boost::range_iterator<C>' being compiled with [ C=char [3] ] --------- It's a VC 7.1 bug but there is possibility to work around. Instead of using C::iterator by default (existing code shown below): --------- namespace boost { namespace detail { template< typename C > struct range_iterator { typedef BOOST_DEDUCED_TYPENAME C::iterator type; }; } } --------- Use C::iterator only if C is a class. Code showing the possible implementation is shown below --------- namespace boost { namespace detail { template< typename C, bool IsClass> struct range_iterator { typedef void type; }; template< typename C> struct range_iterator<C, true> { typedef BOOST_DEDUCED_TYPENAME C::iterator type; }; } } --------- ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=107586&aid=1313543&group_… ------------------------------------------------------- This SF.Net email is sponsored by: Power Architecture Resource Center: Free content, downloads, discussions, and more. http://solutions.newsforge.com/ibmarch.tmpl _______________________________________________ Boost-bugs mailing list Boost-bugs(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/boost-bugs

1 0

[Boost-bugs] [ boost-Feature Requests-1313447 ] Socket C++ library
by SourceForge.net 05 Oct '05

05 Oct '05

Feature Requests item #1313447, was opened at 2005-10-04 20:19 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=357586&aid=1313447&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: Socket C++ library Initial Comment: Without a socket library, C++ can't be on the net. Hope boost can do something ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=357586&aid=1313447&group_… ------------------------------------------------------- This SF.Net email is sponsored by: Power Architecture Resource Center: Free content, downloads, discussions, and more. http://solutions.newsforge.com/ibmarch.tmpl _______________________________________________ Boost-bugs mailing list Boost-bugs(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/boost-bugs

1 0

gui - previous discussions
by rasmus ekman 05 Oct '05

05 Oct '05

Hi, Some time ago I collected a pageful of links to the discussions on gui design in the mail archives. I just uploaded the page as is to the wiki: http://www.crystalclearsoftware.com/cgi-bin/boost_wiki/wiki.pl?BoostDevelGu… - also I very impolitely linked to it at the *top* of the wiki BoostGUI page. I thought it might be one resource for future discussions - it feels some of the threads cover a lot of the same ground. Uh, rephrase to a more positive note: There's quite a bit there to learn or at least consider if you're thinking about the design of a modern gui toolkit! Regards, re

1 0

Re: [boost] BOOST_ASSERT and __assume on MSVC
by brangdon＠cix.compulink.co.uk 04 Oct '05

04 Oct '05

In-Reply-To: <200509282055.j8SKtbXI017230(a)shannonhoon.balstatdev.susq.com> stewart(a)sig.com (Rob Stewart) wrote (abridged): > if (!e) > { > BOOST_ASSERT(false); > __assume(false); > } > > The optimizer can't elide the entire else clause because > BOOST_ASSERT(false) is in it. Do you agree that if the code was: int x = 0; if (!e) { ++x; __assume(false); } cout << x; then the compiler can elide the increment? At this stage I am trying to convince myself that you understand the point I was making, whether or not you agree with how it applies to BOOST_ASSERT. __assume(false) can have retrospective effects. -- Dave Harris, Nottingham, UK.

5 9

Re: [boost] Are there any interest in a pimpl library?
by Martin Bonner 04 Oct '05

04 Oct '05

----Original Message---- From: Asger Mangaard [mailto:tmb@tmbproductions.com] Sent: 27 September 2005 16:13 To: boost(a)lists.boost.org Subject: Re: [boost] Are there any interest in a pimpl library? >> Could you be more specific as to what functionality such a library >> would supply? If you already have an implementation then an example >> of it's use would be interesting. That was my immediate reaction too. >> It is my understanding that the pimpl idiom is fairly simple yet >> also class specific. I currently implement it like this: [snip classic pimpl idiom] > The only thing my library does is to initialize the forward declared > class, using heap or static memory through policies. Also, provides an > easy way of accessing the data. > > Eg. > > .hpp > > boost::pimpl<struct CMyData> m_MyData; > > .cpp > > struct CMyData > { > CMyData() > : m_Integer(0) > { > } > int m_Integer; > }; > > /// Data access > m_MyData->m_Integer = 2341; > > The CMyData will be initialized the first time its data members are > accessed. That means each use of m_MyData operator ->() has got to check whether the structure is initialized or not, and initialize it if so. Isn't it much easier to initialize the pimpl struct in the constructor of the outer class? I also don't see how much easier it can get to access the data than to write: pimpl->m_Integer -- Martin Bonner Martin.Bonner(a)Pitechnology.com Pi Technology, Milton Hall, Ely Road, Milton, Cambridge, CB4 6WZ, ENGLAND Tel: +44 (0)1223 441434

7 27

Re: [boost] [asio] init acceptor to reuse_address?
by BRIDGES Dick 04 Oct '05

04 Oct '05

Hi Chris. > -----Original Message----- > From: boost-bounces(a)lists.boost.org > [mailto:boost-bounces@lists.boost.org] On Behalf Of > Christopher Kohlhoff > Sent: Monday, October 03, 2005 3:01 PM > To: boost(a)lists.boost.org > Subject: Re: [boost] [asio] init acceptor to reuse_address? > > > Hi Dick, > > --- BRIDGES Dick <Dick.Bridges(a)us.thalesgroup.com> wrote: [snip] > > Mumbling something about defaulting modern socket libraries > > to SO_REUSEADDR, > > Do you think I should change the default to set SO_REUSEADDR to true? > At the moment I leave all options to default to whatever the OS > provides. Is there a good reason why all OSes (that I know of) have it > default to false I wonder? Or is it just historical? No. SO_REUSEADDR does increase the attack surface. Not a lot and less now than in the past but IMHO there's no point in helping the bad guys even a little bit if it's not required. Besides, I doubt all that many people would find it useful. My mumbling was aimed more toward myself than anything else - I have written a fair amount of "server" code and should have developed better habits by now. ;) [snip] > > asio::ipv4::tcp::endpoint endpoint(port); > acceptor_.open(endpoint.protocol()); > acceptor_.set_option(asio::socket_acceptor::reuse_address(true)); > acceptor_.bind(endpoint); > acceptor_.listen(); > acceptor_.async_accept(new_connection_->socket(), > boost::bind(&server::handle_accept, this, > asio::placeholders::error)); > > (From the new http example I've written: > http://cvs.sourceforge.net/viewcvs.py/asio/asio/src/examples/ > http/server/server.cpp?rev=1.1&view=markup). Hmmm. The copy of the library I downloaded on 14 September doesn't have socket_acceptor::reuse_address and linux.softpedia.com says the last update was 5 September. I used stream_socket::reuse_address instead and that worked. Is there a newer version of the library somewhere else? Other than that one substitution, this fixed the problem. I would like to see this initialization code pushed back down into the acceptor. Maybe something along the lines of an "option_policy", but I can't come up with anything to suggest that isn't more trouble than it's worth. Thanks - *AGAIN* - for the help. Regards, Dick

2 1

[relational] Relational Model Library
by Calum Grant 04 Oct '05

04 Oct '05

Hi all, I have recently completed a library for implementing relational models in C++. Using template metaprogramming, multi-index containers can be manipulated using SQL-style queries, while retaining type-safety and efficiency. The web page is http://visula.org/relational This might be an appropriate interface for the database library that was recently discussed. This is not the same as Relational Template Library, which uses an entirely different interface. Is there any interest in providing relational containers in Boost? Are there any features/improvements you can suggest for RML? Many thanks, Calum

13 44

boost::dynamic_array
by Boris 04 Oct '05

04 Oct '05

I stumbled about boost::dynamic_bitset in the documentation which is a runtime sized version of std::bitset. Now I wonder why there is no boost::dynamic_array. We have boost::array but just like with std::bitset you need to know the size at compile time. Is there any interest in boost::dynamic_array (I mean is anyone else interested except me :-)? Boris

7 9

Re: [boost] GUI coordinate units (Was: GUI foundations)
by Schrom, Brian T 04 Oct '05

04 Oct '05

>> Of course, this requires a completely vector-graphics-based GUI, which >> is still the exception. > > And that is one area I'd love to work on! This will require a new way of thinking > and quite a bit of work but I think it's the right way to go. [snip] ... > are implemented on the basis of Anti-Grain Geometry, so that, all the rendering > infrastructure is multi-platform. That's my definition of beautiful! I am also interested in pursuing this type of GUI. This would meet my needs more completely than current widgetlike toolkits.

1 0

Boost regression notification (2005-10-04 [HEAD])
by Douglas Gregor 04 Oct '05

04 Oct '05

Boost regression test failures ------------------------------ Report time: 2005-10-04T05:00:22Z This report lists all regression test failures on release platforms. Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-HEAD/developer/issues… 120 failures in 9 libraries: concept_check (12) graph (2) mpl (1) parameter (11) serialization (30) spirit (8) thread (4) tuple (1) typeof (51) |concept_check| stl_concept_covering: cw-9_4 gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin intel-win32-9_0 intel-win32-9_0 mingw-3_4_2 vc-7_1 |graph| graphviz_test: vc-7_1 layout_test: intel-win32-9_0 |mpl| size_t: gcc-4_0-darwin |parameter| basics: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux efficiency: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux macros: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux sfinae: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux unnamed: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux vc-7_1 |serialization| test_class_info_load_binary_archive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_binary_archive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_archive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_archive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_warchive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_warchive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_archive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_archive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_warchive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_warchive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin |spirit| action_tests_debug: gcc-3_4_3-sunos distinct_tests_debug: gcc-3_4_3-sunos escape_char_parser_tests_debug: gcc-3_4_3-sunos grammar_def_test_debug: gcc-3_4_3-sunos switch_problem_debug: gcc-3_4_3-sunos switch_tests_single_debug: gcc-3_4_3-sunos traverse_tests: intel-win32-9_0 traverse_tests_debug: intel-win32-9_0 |thread| test_condition: gcc-3_4_3-sunos test_mutex: gcc-3_4_3-sunos test_tss: gcc-3_4_3-sunos gcc-3_4_3-sunos |tuple| tuple_test_bench: gcc-3_4_3-sunos |typeof| data_member_native: cw-9_4 intel-win32-9_0 intel-win32-9_0 function_native: cw-9_4 intel-win32-9_0 intel-win32-9_0 function_ptr_native: cw-9_4 intel-win32-9_0 intel-win32-9_0 function_ref_native: cw-9_4 intel-win32-9_0 intel-win32-9_0 lvalue_native: cw-9_4 intel-win32-9_0 intel-win32-9_0 member_function_native: cw-9_4 intel-win32-9_0 intel-win32-9_0 modifiers_emulation: cw-9_4 modifiers_native: cw-9_4 intel-win32-9_0 intel-win32-9_0 noncopyable_native: cw-9_4 intel-win32-9_0 intel-win32-9_0 odr_native: intel-win32-9_0 std_emulation: cw-9_4 std_native: cw-9_4 intel-win32-9_0 intel-win32-9_0 template_dependent_native: cw-9_4 intel-win32-9_0 intel-win32-9_0 template_enum_native: cw-9_4 intel-win32-9_0 intel-win32-9_0 template_int_native: cw-9_4 intel-win32-9_0 intel-win32-9_0 template_multiword_native: cw-9_4 intel-win32-9_0 intel-win32-9_0 template_tpl_native: cw-9_4 intel-win32-9_0 intel-win32-9_0 template_type_native: cw-9_4 intel-win32-9_0 intel-win32-9_0 type_native: cw-9_4 intel-win32-9_0 intel-win32-9_0

1 0

Re: [boost] [mpl] sequence_wrapper change to handle enums
by Aleksey Gurtovoy 04 Oct '05

04 Oct '05

Larry Evans writes: > OTOH, I was thinking that maybe preprocess.cmd could just contain: > > gcc -E -C -P -I%(boost_root) "-D > BOOST_USER_CONFIG=<%(boost_root)/libs/mpl/preprocessed/include/%(mode)/u > ser.hpp>" > -D BOOST_MPL_CFG_NO_OWN_PP_PRIMITIVES %(file) >%(file_path) > > which could be read into a variable, compile_cmd, which would then be > used as: > > os.system( compile_cmd % { 'boost_root':boost_root, 'mode':mode, > 'file':file, 'file_path':file_path } ) > > does that sound OK? It would have to be '... -I%(boost_root)s' and similarly for other arguments, but otherwise that's an excellent idea! It eliminates the need for having two different 'preprocess' files. OK, the above is in the CVS now. Thank you! -- Aleksey Gurtovoy MetaCommunications Engineering

2 1

[typeof] More strange failures on como
by Arkadiy Vertleyb 04 Oct '05

04 Oct '05

A typeof test case defined as: [ run odr1.cpp odr2.cpp : : : <define>BOOST_TYPEOF_COMPLIANT : odr_emulation ] is failing in a way that looks like como didn't even start to compile odr1.cpp: http://engineering.meta-comm.com/boost-regression/CVS-HEAD/developer/output/ Bronek-bin-boost-libs-typeof-test-odr_emulation-test-como-4_3_3-vc7_1-debug. html There is the compiler output for odr2.cpp only, and then linker output that claims there is no odr1.obj. GCC, VC7.1 appear to be fine with this test... Any insights on the cause of the problem? Thanks, Arkadiy

1 0

[multi_array] range-checked element access
by Adrian Sheppard 04 Oct '05

04 Oct '05

Is there a good reason why multi_array, and perhaps other boost containers with an unchecked operator [], don't provide a range-checked element access function, like std::vector::at()? Perhaps I'm missing something obvious?. regards adrian sheppard

1 0

Serialization
by Stefan 04 Oct '05

04 Oct '05

Hi folks, I just tested the boost serialization library. I have a question: I need to serialize my objects and then transfer them via tcp connection. Right now I write them into a file like in the examples and then open this file again read it with getc into an array, then send it. Is there an easier way without writing to a file, since this would be a problem with my performance. This is what I do right now: const GPSData g(10,10,10.0); std::ostream teststream; std::ofstream ofs("filename"); boost::archive::text_oarchive oa(teststream); oa << g; ofs.close(); char serializedobj[100], c; FILE * fp; fp=fopen("filename", "rw"); int cnt=0; while((c=getc(fp)) !=EOF) { serializedobj[cnt]=c; cnt++; } serializedobj[cnt]='\0'; tcpclient->send(serializedobj); Thanks in advance, Stefan ___________________________________________________________ Was denken Sie über E-Mail? Wir hören auf Ihre Meinung: http://surveylink.yahoo.com/wix/p0379378.aspx

2 1

Re: [boost] [mpl] bug in mpl::at?
by Aleksey Gurtovoy 04 Oct '05

04 Oct '05

Geoffrey Romer writes: > Along the same lines, I'm now having similar trouble with the > 2-argument version of insert. Is this a known issue? Unlikely, but it's hard to say without seeing the code and the error. > > Fortunately, there's a pretty trivial workaround for this one... Given that a test case for the two-argument 'insert' form is present in both 'map' and 'set' tests (http://tinyurl.com/cuqjl) I suspect that you are doing something wrong. -- Aleksey Gurtovoy MetaCommunications Engineering

1 0

[mpl] bug in mpl::at?
by Geoffrey Romer 04 Oct '05

04 Oct '05

I asked this on boost-users with no luck, so I figured I'd kick it up to the experts: I'm trying to use the 3-argument version of the mpl::at metafunction, as described in the on-line manual, but I'm getting a compile error (using gcc 4.0.2): --- error: wrong number of template arguments (3, should be 2) /usr/include/boost/mpl/at_fwd.hpp:20: error: provided for 'template<class Sequence, class N> struct boost::mpl::at' --- Looking at at.hpp, at_fwd.hpp, and aux_/at_fwd.hpp, I don't see any sign of a 3-argument version of at; everything seems to be defined in terms of a 2-argument template. Am I doing something wrong, or is this a bug?

4 6

[asio] init acceptor to reuse_address?
by BRIDGES Dick 03 Oct '05

03 Oct '05

I submitted this question to boost-users Friday but it occurred to me that it should have been posted here. Apologies if I've erred. <original> I created a server something like this: handle_accept(){ do_the_right_thing(); } Class Foo { socket_acceptor acceptor_; Public: Foo(demuxer& d) : acceptor_( d, ipv4::tcp::endpoint(2525)){} Example(demuxer& d) { stream_socket* p = new stream_socket(d); acceptor_.async_accept(p, handle_accept); } } Everything works fine except when I (1) connect a client; (2) ^C the server; (3) try to restart the server - which, as expected, yields "Address already in use". Mumbling something about defaulting modern socket libraries to SO_REUSEADDR, I started trying to figure out where to call set_option(stream_socket::reuse_address(true)) - and can't work it out. I've set_option() on sockets and the acceptor but can't make the acceptor reuse the address as long as the connection that was established is still in TIME_WAIT. Do you have an example that shows how this can be done? </original> Regards, Dick Bridges

2 3

[Solved]:Serialization
by Stefan 03 Oct '05

03 Oct '05

Sorry guys, forget my earlier posting. I just looked at the c++ reference and saw, that there is a ostringstream, which is what I needed, I haven't done to much c++ yet, didn't know there was such a stream class :-( Cheers Stefan ___________________________________________________________ Was denken Sie über E-Mail? Wir hören auf Ihre Meinung: http://surveylink.yahoo.com/wix/p0379378.aspx

1 0

[scope_guard] New revision available + naming consideration
by Andrey Semashev 03 Oct '05

03 Oct '05

The new version is available in the Sandbox (I moved it into Function objects): http://boost-consulting.com/vault/index.php?action=downloadfile&filename=sc… Here is a shord summary about changes: - Various cosmetic changes, including macro and function names. - Exception support code (with_catcher policy) moved into a separate file. - Added a helper function "catching" to simplify use of with_catcher policy. - Unique names generating code moved into a separate file. By the way, maybe this code should better be in Boost.Preprocessor? See boost/guard/unique_names.hpp. - Revised the guard_ptr class, moved it up to boost namespace. It is now resided in guard_ptr.hpp. - The actions_trace class was considered to be too specific and was eliminated. The new guard_adapter class is supposed to expand the functionality of holding scope guards in containers to every STL-compatible container (sequental or associative) and even to the standard container wrappers such as stack, queue or priority_queue. See guard_adapter.hpp for more details. - I hope I've fixed problems with VC6 (and even maybe BCB) I've been reported, but I can't tell for sure since I can't try it. At least the code that uses scope_guard.hpp should work (once again, I hope). Maybe I'll have a chance to test it on VC6 in a week or two, but now I'm walking blindly. As always, I've tried it on VC7.1, ICL9 and MinGW (GCC 3.4.4). Few words about what I'm concerned about: - The naming of arm/disarm methods of scope guard. They are used to change the activity status of the guard. Personally, I feel fine with them but the commonly used name for disabling the guard is "dismiss" and I just can't figure out its suitable counterpart in English. I wonder if anyone have a proposal about this. - The naming of the function make_guarded_call (in previous version it was make_transaction) is what I'm not sure of. This function in addition to a scope_guard creation calls some another functor. The semantic is grouping the "do" and "undo" actions in the user code. Does anyone have a better name? - I have received a proposal of ability to allocate space for several scope_guards on the stack. In current implementation when using guard_adapter and guard_ptr with some container the guard objects will be allocated in the heap which might be slightly slower than if it would be on the stack. So the most probable implementation of such proposal shall be a separate static container. Does anyone have any thoughts about this? How much would you need such functionality? I think, I've reached some point release (unless anyone have proposal about namings). At least, the main scope guard implementation seems to be stable. So I would like to check in this version to CVS (or, maybe, if someone do this for me) if there are no arguments against this. Once I have done this I could start making BoostBook docs (now there are only doxygen-like comments in the code) and make some unit tests.

13 37

[Boost-bugs] [ boost-Bugs-1312222 ] many "virtual functions vs. non-virtual destructor" warnings
by SourceForge.net 03 Oct '05

03 Oct '05

Bugs item #1312222, was opened at 2005-10-03 12:20 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=107586&aid=1312222&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: serialization Group: None Status: Open Resolution: None Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Robert Ramey (ramey) Summary: many "virtual functions vs. non-virtual destructor" warnings Initial Comment: Hello, seems since RC1_1_33_0 the amount of warning has increased once more. Compling with gcc 4.02 with "-Wall -pedantic" It's pretty annyoing and floods the output unnecessary. Other parts of boost dont have this problem... ---- snip --- boost/boost/archive/binary_iarchive.hpp:33: warning: 'class boost::archive::binary_iarchive_i mpl<boost::archive::binary_iarchive>' has virtual functions but non-virtual destructor /home/rmichels/minimon/sdk/boost/boost/archive/binary_iarchive.hpp:76: warning: 'class boost::archive::binary_iarchive' has virtual functions but non-virtual destructor boost/boost/archive/detail/common_oarchive.hpp:31: warning: 'class boost::archive::detail::co mmon_oarchive<boost::archive::binary_oarchive>' has virtual functions but non-virtual destructor boost/boost/archive/basic_binary_oarchive.hpp:53: warning: 'class boost::archive::basic_binar y_oarchive<boost::archive::binary_oarchive>' has virtual functions but non-virtual destructor boost/boost/archive/basic_xml_iarchive.hpp:40: warning: 'class boost::archive::basic_xml_iarc hive<boost::archive::xml_iarchive>' has virtual functions but non-virtual destructor boost/boost/archive/xml_iarchive.hpp:39: warning: 'class boost::archive::xml_iarchive_impl<bo ost::archive::xml_iarchive>' has virtual functions but non-virtual destructor -------------------- There are some more ... Whats the purpose of not having virtual dtor but virtual functions? Could you please supply a solution, this stuff clutters output much. Regards, A. Focht ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=107586&aid=1312222&group_… ------------------------------------------------------- This SF.Net email is sponsored by: Power Architecture Resource Center: Free content, downloads, discussions, and more. http://solutions.newsforge.com/ibmarch.tmpl _______________________________________________ Boost-bugs mailing list Boost-bugs(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/boost-bugs

1 0

Boost regression notification (2005-10-03 [RC_1_33_0])
by Douglas Gregor 03 Oct '05

03 Oct '05

Boost regression test failures ------------------------------ Report time: 2005-10-03T15:12:19Z This report lists all regression test failures on release platforms. Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-RC_1_33_0/developer/i… 221 failures in 6 libraries: foreach (1) iostreams (13) multi_index (1) range (3) serialization (202) wave (1) |foreach| rvalue_const: vc-7_1 |iostreams| gzip_test: cw-9_5-darwin gcc-2.95.3-stlport-4.6.2-linux gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin gcc-3_4_3-sunos gcc-4.0.1-linux gcc-4_0-darwin intel-8.1-linux intel-9.0-linux mingw-3_4_2 vc-7_1 |multi_index| test_serialization: cw-9_5-darwin |range| array: vc-6_5 vc-6_5-stlport vc-7_0 |serialization| test_binary_text_archive: vc-7_1 test_binary_text_archive_dll: vc-7_1 test_class_info_save_text_archive: vc-7_1 test_class_info_save_text_archive_dll: vc-7_1 test_delete_pointer_binary_archive: cw-9_5-darwin test_delete_pointer_binary_archive_dll: cw-9_5-darwin test_delete_pointer_text_archive: cw-9_5-darwin test_delete_pointer_text_warchive: cw-9_5-darwin test_delete_pointer_xml_archive: cw-9_5-darwin test_delete_pointer_xml_warchive: cw-9_5-darwin test_demo_polymorphic: cw-9_5-darwin test_demo_xml_load: gcc-3_3-darwin gcc-4_0-darwin intel-win32-8_1 test_demo_xml_load_dll: gcc-3_3-darwin gcc-4_0-darwin test_deque_binary_archive: cw-9_5-darwin test_deque_binary_archive_dll: cw-9_5-darwin test_deque_text_archive: cw-9_5-darwin test_deque_text_warchive: cw-9_5-darwin test_deque_xml_archive: cw-9_5-darwin test_deque_xml_warchive: cw-9_5-darwin test_derived_text_archive: vc-7_1 test_derived_text_archive_dll: vc-7_1 test_exported_binary_archive: gcc-3.2.3-linux gcc-4.0.1-linux intel-9.0-linux vc-6_5 test_exported_binary_archive_dll: gcc-4.0.1-linux vc-6_5 test_exported_text_archive: gcc-3.2.3-linux gcc-4.0.1-linux vc-6_5 vc-7_1 test_exported_text_archive_dll: gcc-3.2.3-linux gcc-4.0.1-linux vc-6_5 vc-7_1 test_exported_text_warchive: gcc-4.0.1-linux vc-6_5 test_exported_text_warchive_dll: gcc-4.0.1-linux vc-6_5 test_exported_xml_archive: gcc-4.0.1-linux intel-8.1-linux vc-6_5 test_exported_xml_archive_dll: gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-6_5 test_exported_xml_warchive: gcc-3.2.3-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-6_5 test_exported_xml_warchive_dll: gcc-3.2.3-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-6_5 test_list_binary_archive: cw-9_5-darwin test_list_binary_archive_dll: cw-9_5-darwin test_list_ptrs_binary_archive: cw-9_5-darwin test_list_ptrs_binary_archive_dll: cw-9_5-darwin test_list_ptrs_text_archive: cw-9_5-darwin test_list_ptrs_text_warchive: cw-9_5-darwin test_list_ptrs_xml_archive: cw-9_5-darwin test_list_ptrs_xml_warchive: cw-9_5-darwin test_list_ptrs_xml_warchive_dll: gcc-3_4_3-sunos test_list_text_archive: cw-9_5-darwin test_list_text_warchive: cw-9_5-darwin test_list_xml_archive: cw-9_5-darwin test_list_xml_warchive: cw-9_5-darwin test_map_binary_archive: cw-9_5-darwin test_map_binary_archive_dll: cw-9_5-darwin test_map_text_archive: cw-9_5-darwin gcc-3_4_3-sunos test_map_text_warchive: cw-9_5-darwin test_map_xml_archive: cw-9_5-darwin test_map_xml_warchive: cw-9_5-darwin test_mi_text_archive: vc-7_1 test_mi_text_archive_dll: vc-7_1 test_no_rtti_binary_archive: vc-6_5 test_no_rtti_binary_archive_dll: vc-6_5 test_no_rtti_text_archive: vc-6_5 test_no_rtti_text_archive_dll: vc-6_5 test_no_rtti_text_warchive: vc-6_5 test_no_rtti_text_warchive_dll: vc-6_5 test_no_rtti_xml_archive: vc-6_5 test_no_rtti_xml_archive_dll: vc-6_5 test_no_rtti_xml_warchive: vc-6_5 test_no_rtti_xml_warchive_dll: vc-6_5 test_non_default_ctor2_text_archive: vc-7_1 test_non_default_ctor2_text_archive_dll: vc-7_1 test_non_default_ctor_text_archive: vc-7_1 test_non_default_ctor_text_archive_dll: vc-7_1 test_non_intrusive_text_archive: vc-7_1 test_non_intrusive_text_archive_dll: vc-7_1 test_null_ptr_text_archive: vc-7_1 test_null_ptr_text_archive_dll: vc-7_1 test_object_text_archive: vc-7_1 test_object_text_archive_dll: vc-7_1 test_polymorphic_binary_archive: cw-9_5-darwin test_polymorphic_binary_archive_dll: cw-9_5-darwin test_polymorphic_text_archive: cw-9_5-darwin test_polymorphic_text_warchive: cw-9_5-darwin test_polymorphic_xml_archive: cw-9_5-darwin test_polymorphic_xml_warchive: cw-9_5-darwin test_primitive_text_archive: vc-7_1 test_primitive_text_archive_dll: vc-7_1 test_private_ctor: cw-9_5-darwin test_registered_text_archive: vc-7_1 test_registered_text_archive_dll: vc-7_1 test_reset_object_address: cw-9_5-darwin test_set_binary_archive: cw-9_5-darwin test_set_binary_archive_dll: cw-9_5-darwin test_set_text_archive: cw-9_5-darwin test_set_text_warchive: cw-9_5-darwin test_set_xml_archive: cw-9_5-darwin test_set_xml_warchive: cw-9_5-darwin test_shared_ptr_132_binary_archive: vc-6_5 vc-6_5-stlport test_shared_ptr_132_binary_archive_dll: vc-6_5 test_shared_ptr_132_text_archive: vc-6_5 vc-6_5-stlport test_shared_ptr_132_text_archive_dll: gcc-3_4_3-sunos vc-6_5 test_shared_ptr_132_text_warchive: vc-6_5 vc-6_5-stlport test_shared_ptr_132_text_warchive_dll: vc-6_5 test_shared_ptr_132_xml_archive: vc-6_5 vc-6_5-stlport test_shared_ptr_132_xml_archive_dll: vc-6_5 test_shared_ptr_132_xml_warchive: vc-6_5 vc-6_5-stlport test_shared_ptr_132_xml_warchive_dll: vc-6_5 test_shared_ptr_binary_archive: borland-5_6_4 vc-6_5 test_shared_ptr_binary_archive_dll: borland-5_6_4 vc-6_5 test_shared_ptr_text_archive: borland-5_6_4 vc-6_5 test_shared_ptr_text_archive_dll: borland-5_6_4 vc-6_5 test_shared_ptr_text_warchive: borland-5_6_4 vc-6_5 test_shared_ptr_text_warchive_dll: borland-5_6_4 vc-6_5 test_shared_ptr_xml_archive: borland-5_6_4 vc-6_5 test_shared_ptr_xml_archive_dll: borland-5_6_4 vc-6_5 test_shared_ptr_xml_warchive: borland-5_6_4 vc-6_5 test_shared_ptr_xml_warchive_dll: borland-5_6_4 vc-6_5 test_split_text_archive: vc-7_1 test_split_text_archive_dll: vc-7_1 test_split_text_warchive: gcc-3_4_3-sunos test_tracking_text_archive: vc-7_1 test_tracking_text_archive_dll: vc-7_1 test_unregistered_binary_archive: gcc-3.2.3-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux test_unregistered_binary_archive_dll: gcc-3.2.3-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux test_unregistered_text_archive: gcc-3.2.3-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1 test_unregistered_text_archive_dll: gcc-3.2.3-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1 test_unregistered_xml_archive: gcc-3.2.3-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux test_unregistered_xml_archive_dll: gcc-3.2.3-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux test_unregistered_xml_warchive: gcc-4.0.1-linux test_unregistered_xml_warchive_dll: gcc-4.0.1-linux test_variant_binary_archive: cw-9_5-darwin test_variant_binary_archive_dll: cw-9_5-darwin test_variant_text_archive: cw-9_5-darwin test_variant_text_warchive: cw-9_5-darwin test_variant_xml_archive: cw-9_5-darwin test_variant_xml_warchive: cw-9_5-darwin test_vector_binary_archive: cw-9_5-darwin test_vector_binary_archive_dll: cw-9_5-darwin test_vector_text_archive: cw-9_5-darwin test_vector_text_warchive: cw-9_5-darwin test_vector_xml_archive: cw-9_5-darwin test_vector_xml_warchive: cw-9_5-darwin test_void_cast: gcc-3_4_3-sunos test_void_cast_dll: gcc-3_4_3-sunos |wave| testwave: gcc-3_4_3-sunos

1 0

Boost regression notification (2005-10-03 [HEAD])
by Douglas Gregor 03 Oct '05

03 Oct '05

Boost regression test failures ------------------------------ Report time: 2005-10-03T05:00:21Z This report lists all regression test failures on release platforms. Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-HEAD/developer/issues… 120 failures in 9 libraries: concept_check (12) graph (2) mpl (1) parameter (11) serialization (30) spirit (8) thread (4) tuple (1) typeof (51) |concept_check| stl_concept_covering: cw-9_4 gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin intel-win32-9_0 intel-win32-9_0 mingw-3_4_2 vc-7_1 |graph| graphviz_test: vc-7_1 layout_test: intel-win32-9_0 |mpl| size_t: gcc-4_0-darwin |parameter| basics: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux efficiency: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux macros: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux sfinae: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux unnamed: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux vc-7_1 |serialization| test_class_info_load_binary_archive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_binary_archive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_archive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_archive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_warchive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_warchive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_archive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_archive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_warchive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_warchive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin |spirit| action_tests_debug: gcc-3_4_3-sunos distinct_tests_debug: gcc-3_4_3-sunos escape_char_parser_tests_debug: gcc-3_4_3-sunos grammar_def_test_debug: gcc-3_4_3-sunos switch_problem_debug: gcc-3_4_3-sunos switch_tests_single_debug: gcc-3_4_3-sunos traverse_tests: intel-win32-9_0 traverse_tests_debug: intel-win32-9_0 |thread| test_condition: gcc-3_4_3-sunos test_mutex: gcc-3_4_3-sunos test_tss: gcc-3_4_3-sunos gcc-3_4_3-sunos |tuple| tuple_test_bench: gcc-3_4_3-sunos |typeof| data_member_native: cw-9_4 intel-win32-9_0 intel-win32-9_0 function_native: cw-9_4 intel-win32-9_0 intel-win32-9_0 function_ptr_native: cw-9_4 intel-win32-9_0 intel-win32-9_0 function_ref_native: cw-9_4 intel-win32-9_0 intel-win32-9_0 lvalue_native: cw-9_4 intel-win32-9_0 intel-win32-9_0 member_function_native: cw-9_4 intel-win32-9_0 intel-win32-9_0 modifiers_emulation: cw-9_4 modifiers_native: cw-9_4 intel-win32-9_0 intel-win32-9_0 noncopyable_native: cw-9_4 intel-win32-9_0 intel-win32-9_0 odr_native: intel-win32-9_0 std_emulation: cw-9_4 std_native: cw-9_4 intel-win32-9_0 intel-win32-9_0 template_dependent_native: cw-9_4 intel-win32-9_0 intel-win32-9_0 template_enum_native: cw-9_4 intel-win32-9_0 intel-win32-9_0 template_int_native: cw-9_4 intel-win32-9_0 intel-win32-9_0 template_multiword_native: cw-9_4 intel-win32-9_0 intel-win32-9_0 template_tpl_native: cw-9_4 intel-win32-9_0 intel-win32-9_0 template_type_native: cw-9_4 intel-win32-9_0 intel-win32-9_0 type_native: cw-9_4 intel-win32-9_0 intel-win32-9_0

1 0

Is there any interest in a library which provides an extensible logging facility?
by Genia Bezman 03 Oct '05

03 Oct '05

The library would provide the ability to route a message, with an arbitary severity, to any amount of "sinks". The library would support any amount of loggers, identifiable by a unique name (std::string), so that the exact same logger would always be returned for a certain name. Sinks would be defined by deriving from an abstract Sink class. The library would provide a couple of premade sinks (file sink, console sink; ideas welcome). Any given logging message will use a derived class of an abstract Severity class to denote its severity. The library would provide some (8 or so) premade Severity subclasses. Possible syntax would be something like this: In some header file: FileSink fs("log.txt"); LOGGER("My Logger").tie(fs); In some source file: LOGGER << Warning << "Testing logger" << 42 << 3.4 << 'a' << endl; LOGGER(name) would be defined as something like Logger::instance(name, __LINE__, __FILE__) In addition, there would be a way to specify output formatting on a per-logger basis, ideas for possible syntax very welcome (maybe a printf-like syntax?) Any input is appreciated.

2 1

[mpl] sequence_wrapper change to handle enums
by Larry Evans 03 Oct '05

03 Oct '05

Would it be OK for me to copy: boost-sandbox/boost/mpl/aux_/sequence_wrapper.hpp to: boost/boost/mpl/aux_/sequence_wrapper.hpp for the reasons cited here: http://aspn.activestate.com/ASPN/Mail/Message/boost/2640803 ? Also, it would also help *nix developers if: boost-sandbox/libs/mpl/preprocessed/preprocess.py were similarly moved. OK to do that?

2 1

Database libraries - again
by Maciej Sobczak 03 Oct '05

03 Oct '05

Considering the fact that there was some interest in the database library, I think it is a good time to revive the discussion: ------- We are pleased to announce that the new version of SOCI library is available for download. http://soci.sourceforge.net/ The important new feature in the library allows to operate on whole arrays of values (interfaced via std::vector), which can greatly increase application performance by reducing network round-trips in those queries that insert or retrieve many rows at once. -------- I think that this feature is mandatory if we discuss a "quality" library. The question is how to interface to it and how much generic interface can be provided wrt so-called bulk operations. At the moment, SOCI supports interfacing via std::vector, for example: std::vector<int> vec; // ... sql << "insert into numbers(val) values(:val)", use(vec); or: vec.resize(100); // some batch size Statement st = (sql.prepare << "select val from numbers", into(vec)); st.execute(); while (st.fetch()) { // here, vec has subsequent portions of the whole result } Your comments are welcome. I would like to acknowledge that Steve Hutton entirely contributed to the implementation of the bulk operations in this new release. You can visit Steve at <http://featurecomplete.com/> -- Maciej Sobczak : http://www.msobczak.com/ Programming : http://www.msobczak.com/prog/

2 4

[serialisation] Optimisation
by Martin Slater 03 Oct '05

03 Oct '05

Hi there, I've been looking at speed issues loading archives for the last few days and came across something that puzzles me. We are using binary_archive's for storing relatively large data sets (> 100mg) comprised largely of std::vectors of pod types, this was causing huge inefficencies as for each element it was serialising it seperately so I derived a new archive type with specialisations for std::vector load/save that dispatches on podness (?) so if pod it just block writes/read the entire vector. This gave us a massive speedup so it could be useful to include this by default in the provided binary archive as the reaction of a number of our developers when first looking at vtune before this optimisation was that Boost.serialisation was just rubbish as it was so slow. (let me know if you want to see the implementation, its only about 100 lines or so). The next slowest thing as revealed by vtune is the call to basic_iarchive_impl::register_type and inparticular this code :- cobject_type co(cobject_info_set.size(), bis); std::pair<cobject_info_set_type::const_iterator, bool> result = cobject_info_set.insert(co); with the call to extended_type_info_typeid_0::less_than caused by the std::set::insert call consuming nearly 8% of the time needed to load the archive. Tracing this through revealed there seems to be some effort to optimise this call by using extended_type_info::type_info_key which is used by type_info_key_cmp (extended_type_info.cpp) to give an early out but this code if(lhs.type_info_key == rhs.type_info_key) return 0; in type_info_key_cmp always compares true (a breakpoint set after never gets hit) which then causes operator<(const extended_type_info &lhs, const extended_type_info &rhs) to eventually call type_info::before to give ordering information which is where the slowness comes from. This always returns true as it is just a pointer to class static data declared in extended_type_info_typeid_0. The comment attached to the member in extended_type_info states // used to uniquely identify the type of class derived from this one // so that different derivations of this class can be simultaneously // included in implementation of sets and maps. const char * type_info_key; but I cannot see how this will ever be different for any types. I get the impression that it is intended to be different for all types and the test is just relying on its address being unique per specialization of extended_type_info_typeid but I may be well off the mark, can anyone (Robert?) clarify this for me please. thanks Martin ps. This is using vc7.1 compiler.

1 1

Re: [boost] Boost::Tcl
by Roman Yakovenko 03 Oct '05

03 Oct '05

> > I don't think that the same people are interested in interfacing to > *different* languages - that was the point. There are some > who want to > interface with Python, some who want to interface with Tcl, etc., but > I'm not aware of anyone who would ask for more than one language > binding. Thus, the only purpose of building a "universal" > binding would > be to have the potential of code reuse and would target not > final users, I have good example: http://www.gtk.org/bindings.html Roman Yakovenko

1 0

Partial template specialization for boost::array<T, 0> missing in CVS
by Boris 02 Oct '05

02 Oct '05

There is a partial template specialization at http://www.josuttis.com/cppcode/array.hpp for boost::array with 0 elements. However the template specialization is not in the CVS - any reason? I couldn't compile the template specialization however out of the box with VC++ 7.1: - I had to add #include <cassert>. - I had to get rid of makes_no_sense() and copy the function body into the functions which call makes_no_sense(). - I added a no-op void assign(const T& value) to boost::array<T,0> as this function is part of the interface of boost::array<T,N>. It would be nice if the template specialization is added to Boost.Array. Boris

1 0

documentation mailing list
by Arkadiy Vertleyb 02 Oct '05

02 Oct '05

Is it alive? My posts keep disappearing, and I dont see any other new messages... Regards, Arkadiy

2 2

Boost regression notification (2005-10-02 [HEAD])
by Douglas Gregor 02 Oct '05

02 Oct '05

Boost regression test failures ------------------------------ Report time: 2005-10-02T05:00:14Z This report lists all regression test failures on release platforms. Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-HEAD/developer/issues… 119 failures in 9 libraries: concept_check (12) graph (2) mpl (1) parameter (11) serialization (30) spirit (8) thread (4) tuple (1) typeof (50) |concept_check| stl_concept_covering: cw-9_4 gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin intel-win32-9_0 intel-win32-9_0 mingw-3_4_2 vc-7_1 |graph| graphviz_test: vc-7_1 layout_test: intel-win32-9_0 |mpl| size_t: gcc-4_0-darwin |parameter| basics: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux efficiency: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux macros: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux sfinae: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux unnamed: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux vc-7_1 |serialization| test_class_info_load_binary_archive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_binary_archive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_archive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_archive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_warchive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_warchive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_archive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_archive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_warchive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_warchive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin |spirit| action_tests_debug: gcc-3_4_3-sunos distinct_tests_debug: gcc-3_4_3-sunos escape_char_parser_tests_debug: gcc-3_4_3-sunos grammar_def_test_debug: gcc-3_4_3-sunos switch_problem_debug: gcc-3_4_3-sunos switch_tests_single_debug: gcc-3_4_3-sunos traverse_tests: intel-win32-9_0 traverse_tests_debug: intel-win32-9_0 |thread| test_condition: gcc-3_4_3-sunos test_mutex: gcc-3_4_3-sunos test_tss: gcc-3_4_3-sunos gcc-3_4_3-sunos |tuple| tuple_test_bench: gcc-3_4_3-sunos |typeof| data_member_native: cw-9_4 intel-win32-9_0 intel-win32-9_0 function_native: cw-9_4 intel-win32-9_0 intel-win32-9_0 function_ptr_native: cw-9_4 intel-win32-9_0 intel-win32-9_0 function_ref_native: cw-9_4 intel-win32-9_0 intel-win32-9_0 lvalue_native: cw-9_4 intel-win32-9_0 intel-win32-9_0 member_function_native: cw-9_4 intel-win32-9_0 intel-win32-9_0 modifiers_emulation: cw-9_4 modifiers_native: cw-9_4 intel-win32-9_0 intel-win32-9_0 noncopyable_native: cw-9_4 intel-win32-9_0 intel-win32-9_0 std_emulation: cw-9_4 std_native: cw-9_4 intel-win32-9_0 intel-win32-9_0 template_dependent_native: cw-9_4 intel-win32-9_0 intel-win32-9_0 template_enum_native: cw-9_4 intel-win32-9_0 intel-win32-9_0 template_int_native: cw-9_4 intel-win32-9_0 intel-win32-9_0 template_multiword_native: cw-9_4 intel-win32-9_0 intel-win32-9_0 template_tpl_native: cw-9_4 intel-win32-9_0 intel-win32-9_0 template_type_native: cw-9_4 intel-win32-9_0 intel-win32-9_0 type_native: cw-9_4 intel-win32-9_0 intel-win32-9_0

1 0

[typeof] strange failure on como
by Arkadiy Vertleyb 02 Oct '05

02 Oct '05

I got a strange failure on como in the test that had been OK for qiute a while. Does this error message make sense to anybody? Thanks, Arkadiy Test output: Bronek - typeof - function_ptr_emulation / como-4_3_3-vc7_1 Report Time: Sun, 2 Oct 2005 05:00:14 +0000 Compiler output [2005-10-02 02:40:02 UTC]: call "C:\Program Files\Microsoft Visual Studio .NET 2003\Vc7\..\Common7\Tools\vsvars32" >nul set "COMO_MS_INCLUDE=C:\Program Files\Microsoft Visual Studio .NET 2003\Vc7/include" set "PATH=;%PATH%" "como" --vc71 -c -e5 --no_version --no_prelink_verbose --display_error_numb er --long_long --diag_suppress=9,21,161,748,940,962 -D__STL_LONG_LONG -DBOO ST_TYPEOF_COMPLIANT --a -DBOOST_COMO_STRICT=1 --no_inlining /Zi /Od -D_WIN32 -DBOOST_SP_DISABLE_THREADS --exceptions -DBOOST_DISABLE_WIN32 --wchar_t -I"G:\boost" -I"G:\boost" -I"G:\boost" -o "G:\results\bin\boost\libs\typeof\test\function_ptr_emulation.test\como-4_3_ 3-vc7_1\debug\function_ptr_emulation.obj" "..\libs\typeof\test\function_ptr.cpp" como: could not rename function_ptr.int.c to _comointc.c. Failure while executing 'cl' compiler ...email Comeau for advice.

2 2

[fsm]
by Andy Little 02 Oct '05

02 Oct '05

Is fsm library not in boost 1.33.0 or have I lost it? regards Andy Little

2 5

Boost regression notification (2005-10-01 [RC_1_33_0])
by Douglas Gregor 01 Oct '05

01 Oct '05

Boost regression test failures ------------------------------ Report time: 2005-10-01T15:05:12Z This report lists all regression test failures on release platforms. Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-RC_1_33_0/developer/i… 79 failures in 5 libraries: foreach (1) iostreams (13) range (3) serialization (61) wave (1) |foreach| rvalue_const: vc-7_1 |iostreams| gzip_test: cw-9_5-darwin gcc-2.95.3-stlport-4.6.2-linux gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin gcc-3_4_3-sunos gcc-4.0.1-linux gcc-4_0-darwin intel-8.1-linux intel-9.0-linux mingw-3_4_2 vc-7_1 |range| array: vc-6_5 vc-6_5-stlport vc-7_0 |serialization| test_exported_binary_archive: vc-6_5 test_exported_binary_archive_dll: vc-6_5 test_exported_text_archive: vc-6_5 test_exported_text_archive_dll: vc-6_5 test_exported_text_warchive: vc-6_5 test_exported_text_warchive_dll: vc-6_5 test_exported_xml_archive: vc-6_5 test_exported_xml_archive_dll: vc-6_5 test_exported_xml_warchive: vc-6_5 test_exported_xml_warchive_dll: vc-6_5 test_list_ptrs_xml_warchive_dll: gcc-3_4_3-sunos test_map_text_archive: gcc-3_4_3-sunos test_no_rtti_binary_archive: vc-6_5 test_no_rtti_binary_archive_dll: vc-6_5 test_no_rtti_text_archive: vc-6_5 test_no_rtti_text_archive_dll: vc-6_5 test_no_rtti_text_warchive: vc-6_5 test_no_rtti_text_warchive_dll: vc-6_5 test_no_rtti_xml_archive: vc-6_5 test_no_rtti_xml_archive_dll: vc-6_5 test_no_rtti_xml_warchive: vc-6_5 test_no_rtti_xml_warchive_dll: vc-6_5 test_shared_ptr_132_binary_archive: vc-6_5 vc-6_5-stlport test_shared_ptr_132_binary_archive_dll: vc-6_5 test_shared_ptr_132_text_archive: vc-6_5 vc-6_5-stlport test_shared_ptr_132_text_archive_dll: gcc-3_4_3-sunos vc-6_5 test_shared_ptr_132_text_warchive: vc-6_5 vc-6_5-stlport test_shared_ptr_132_text_warchive_dll: vc-6_5 test_shared_ptr_132_xml_archive: vc-6_5 vc-6_5-stlport test_shared_ptr_132_xml_archive_dll: vc-6_5 test_shared_ptr_132_xml_warchive: vc-6_5 vc-6_5-stlport test_shared_ptr_132_xml_warchive_dll: vc-6_5 test_shared_ptr_binary_archive: borland-5_6_4 vc-6_5 test_shared_ptr_binary_archive_dll: borland-5_6_4 vc-6_5 test_shared_ptr_text_archive: borland-5_6_4 vc-6_5 test_shared_ptr_text_archive_dll: borland-5_6_4 vc-6_5 test_shared_ptr_text_warchive: borland-5_6_4 vc-6_5 test_shared_ptr_text_warchive_dll: borland-5_6_4 vc-6_5 test_shared_ptr_xml_archive: borland-5_6_4 vc-6_5 test_shared_ptr_xml_archive_dll: borland-5_6_4 vc-6_5 test_shared_ptr_xml_warchive: borland-5_6_4 vc-6_5 test_shared_ptr_xml_warchive_dll: borland-5_6_4 vc-6_5 test_split_text_warchive: gcc-3_4_3-sunos test_void_cast: gcc-3_4_3-sunos test_void_cast_dll: gcc-3_4_3-sunos |wave| testwave: gcc-3_4_3-sunos

1 0

Boost regression notification (2005-10-01 [HEAD])
by Douglas Gregor 01 Oct '05

01 Oct '05

Boost regression test failures ------------------------------ Report time: 2005-10-01T05:00:11Z This report lists all regression test failures on release platforms. Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-HEAD/developer/issues… 120 failures in 9 libraries: concept_check (12) graph (2) mpl (1) parameter (12) serialization (30) spirit (8) thread (4) tuple (1) typeof (50) |concept_check| stl_concept_covering: cw-9_4 gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin intel-win32-9_0 intel-win32-9_0 mingw-3_4_2 vc-7_1 |graph| graphviz_test: vc-7_1 layout_test: intel-win32-9_0 |mpl| size_t: gcc-4_0-darwin |parameter| basics: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux efficiency: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-4_0-darwin macros: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux sfinae: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux unnamed: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux vc-7_1 |serialization| test_class_info_load_binary_archive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_binary_archive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_archive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_archive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_warchive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_warchive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_archive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_archive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_warchive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_warchive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin |spirit| action_tests_debug: gcc-3_4_3-sunos distinct_tests_debug: gcc-3_4_3-sunos escape_char_parser_tests_debug: gcc-3_4_3-sunos grammar_def_test_debug: gcc-3_4_3-sunos switch_problem_debug: gcc-3_4_3-sunos switch_tests_single_debug: gcc-3_4_3-sunos traverse_tests: intel-win32-9_0 traverse_tests_debug: intel-win32-9_0 |thread| test_condition: gcc-3_4_3-sunos test_mutex: gcc-3_4_3-sunos test_tss: gcc-3_4_3-sunos gcc-3_4_3-sunos |tuple| tuple_test_bench: gcc-3_4_3-sunos |typeof| data_member_native: cw-9_4 intel-win32-9_0 intel-win32-9_0 function_native: cw-9_4 intel-win32-9_0 intel-win32-9_0 function_ptr_native: cw-9_4 intel-win32-9_0 intel-win32-9_0 function_ref_native: cw-9_4 intel-win32-9_0 intel-win32-9_0 lvalue_native: cw-9_4 intel-win32-9_0 intel-win32-9_0 member_function_native: cw-9_4 intel-win32-9_0 intel-win32-9_0 modifiers_emulation: cw-9_4 modifiers_native: cw-9_4 intel-win32-9_0 intel-win32-9_0 noncopyable_native: cw-9_4 intel-win32-9_0 intel-win32-9_0 std_emulation: cw-9_4 std_native: cw-9_4 intel-win32-9_0 intel-win32-9_0 template_dependent_native: cw-9_4 intel-win32-9_0 intel-win32-9_0 template_enum_native: cw-9_4 intel-win32-9_0 intel-win32-9_0 template_int_native: cw-9_4 intel-win32-9_0 intel-win32-9_0 template_multiword_native: cw-9_4 intel-win32-9_0 intel-win32-9_0 template_tpl_native: cw-9_4 intel-win32-9_0 intel-win32-9_0 template_type_native: cw-9_4 intel-win32-9_0 intel-win32-9_0 type_native: cw-9_4 intel-win32-9_0 intel-win32-9_0

1 0

A GUI decomposition
by Stefan Seefeld 01 Oct '05

01 Oct '05

Given the recurring interest this topic incites, I think it is important to start by clarifying what people really mean by 'C++ GUI'. For the more practically-minded, it is a means to portably and easily write Modern C++ (TM) applications that use a graphical interface, while for others it is an occasion to Do It Right This Time (TM). Can they both be satisfied with the same API ? I believe this should be possible by making educated use of abstraction and modularisation. I'm a little reminded of the discussion around a socket / network / asyncio API, as I believe the situation is similar. This is because the methodological challenge is the same: what is needed is not a single monolithic API but in fact a set of interdependent APIs, and it is hard to draw a clear line between them. Therefor, I'd suggest we split 'GUI' into distinct modules and try to model each individually, keeping in mind that a) they all have to be able to collaborate and b) each may be implemented either in terms of a 'native' backend as well as in a OS-independent way. To get to the meat, here are the domains I think should be discussed individually: * Imaging Model =============== This module is concerned with low-level drawing primitives (2D at first, but may be extended into 3D). The associated vocabulary includes canvas, painter, graphic context ('GC'), path, pencil, etc., etc., you get the idea. * Event / Messaging Mechanism ============================= This module provides whatever it takes for individual parts of an application to exchange messages, both, graphical as well as other. Designing this module is particularly challenging if this is to be generic as some backends are rather constraining in terms of message types that can be sent / received. This module should be able to provide a uniform view on both input events ('button click', 'pointer move'), region management ('expose', 'resize'), as well as high level widget-related ('slider dragged'). * Region ('Window') Management ============================== This module is concerned with providing users with regions to draw to and receive events for, independently on what these regions actually contain. The associated vocabulary includes region, map / unmap, resize, stack, layout. While people may be inclined to think of these regions more in terms of windows, or even widgets, I believe there is good reason to keep these two concepts separate, even though in most cases there may be a one-to-one mapping between the two. (Imagine a situation where windows (which typically are screen-aligned rectangular regions) are not enough to represent regions, i.e. where you want to track stacked *shaped* graphics.) * Widgets ========= This is probably what most developers think of as 'GUI'. It's all those building blocks that have a certain style, behavior, and associated state, with more or less complex logic to keep 'view' (and possibly 'controller') separate from the 'model'. Again, I suggest this separation in the hope that it will facilitate and focus further discussion. I believe all existing GUIs support the above concepts, even though they may not be as clearly separate as I suggest here. In particular, depending on the architecture some of these aspects might be hidden, for example if the work is split into a display server and a client, where users only program the client application. As prior discussions suggest there are widely differing views on who should be in control of styling. Using different backends (or policies) developers / users can have more or less fine-grained control over these issues. A simple implementation of the high level APIs would be a slim wrapper around existing libraries, while for fine-grained control more work is needed. It would thus be an interesting exercise to see whether existing GUIs can be mapped back to the above modules I suggest. Regards, Stefan

2 1

dummy
by Andy Little 01 Oct '05

01 Oct '05

1 3

[mpl] naming the math project
by Cromwell Enage 01 Oct '05

01 Oct '05

> --- Peder Holt wrote: > Do we have a good name for the project? > metamath or mpl_math or something new? I don't know what the current naming scheme would prescribe for an annex to a preexisting library, but I think Boost.MPL.Math, or MPL.Math for short, would make a fine name for use in discussions. "mpl_math" is just a file name I use when uploading to the vault, as is "metadouble" or "mpl_double" for your corresponding submissions. Cromwell D. Enage ______________________________________________________ Yahoo! for Good Donate to the Hurricane Katrina relief effort. http://store.yahoo.com/redcross-donate3/

3 2

gui
by Jonathan Benedicto 30 Sep '05

30 Sep '05

I hope that none of you mind my asking about something that has been debated vigorously before. But, what are the current developments towards including a GUI library into Boost ? Jonathan

1 0

Re: [boost] [asio] how detect deadline_timer expired state?
by BRIDGES Dick 30 Sep '05

30 Sep '05

Hi Chris, > -----Original Message----- > From: boost-bounces(a)lists.boost.org > [mailto:boost-bounces@lists.boost.org] On Behalf Of > Christopher Kohlhoff > Sent: Wednesday, September 28, 2005 6:36 PM > To: boost(a)lists.boost.org > Subject: Re: [boost] [asio] how detect deadline_timer expired state? > > > Hi Dick, [snip] > I didn't add an expired() method so as to not make it easy write code > with a race condition ;) (Although strictly speaking you could check > the duration returned by expires_from_now() for the same effect.) I haven't had time go to through the code so I didn't understand the value returned by expires_from_now() when called on timer that expired or had never been set. > The problem with a hypothetical expired() method is that if it returns > true it doesn't actually tell you whether the async_wait's handler has > been delivered yet, i.e. the timer expired but the handler could be > sitting in the demuxer's post queue. Makes perfect sense now that you point it out. State changes are now recorded in the wait handlers - where the state is actually changed. %>] > Another thing is that changing the timer's expiry time while there are > unexpired async_waits has no effect on those waits. In fact I should > change the documentation to make it clear that changing the > expiry time > while there are unexpired waits is "undefined". This design decision > was taken for efficiency reasons, i.e. to avoid having getting or > setting the expiry time need to access a synchronised resource (e.g. > the select_reactor). I agree the documentation should be changed. I experienced some of that "undefined" behavior before I switched to the cancel/set instruction sequence. 8) [snip] > Cheers, > Chris Regards, Dick

1 0

[pool] Why no singleton_object_pool?
by Joel Eidsath 30 Sep '05

30 Sep '05

In [boost.pool], why is there no singleton_object_pool? Or is it already possible to achieve the same behavior? Joel Eidsath

2 4

Re: [boost] What is Boost?
by Scott Schurr 30 Sep '05

30 Sep '05

Someone might take a peek at Scott Meyers "Effective C++, Third Edition". Chapter 55 is entitled, "Familiarize yourself with Boost." I bet there's an excellent summary in there. I'd take a look myself, but my copy is at home. Hope that helps.

1 0

[Review] xpressive
by Thomas Witt 30 Sep '05

30 Sep '05

Hi All, the xpressive review is now officially closed. That being said I know it's not a small library so if anybody(John?) feels like he can provide a review in the next few days I'll be happy to accept it. Thanks Thomas Review Manager xpressive

16 25

Boost regression notification (2005-09-30 [RC_1_33_0])
by Douglas Gregor 30 Sep '05

30 Sep '05

Boost regression test failures ------------------------------ Report time: 2005-09-30T14:19:07Z This report lists all regression test failures on release platforms. Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-RC_1_33_0/developer/i… 73 failures in 4 libraries: foreach (1) iostreams (13) range (3) serialization (56) |foreach| rvalue_const: vc-7_1 |iostreams| gzip_test: cw-9_5-darwin gcc-2.95.3-stlport-4.6.2-linux gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin gcc-3_4_3-sunos gcc-4.0.1-linux gcc-4_0-darwin intel-8.1-linux intel-9.0-linux mingw-3_4_2 vc-7_1 |range| array: vc-6_5 vc-6_5-stlport vc-7_0 |serialization| test_exported_binary_archive: vc-6_5 test_exported_binary_archive_dll: vc-6_5 test_exported_text_archive: vc-6_5 test_exported_text_archive_dll: vc-6_5 test_exported_text_warchive: vc-6_5 test_exported_text_warchive_dll: vc-6_5 test_exported_xml_archive: vc-6_5 test_exported_xml_archive_dll: vc-6_5 test_exported_xml_warchive: vc-6_5 test_exported_xml_warchive_dll: vc-6_5 test_no_rtti_binary_archive: vc-6_5 test_no_rtti_binary_archive_dll: vc-6_5 test_no_rtti_text_archive: vc-6_5 test_no_rtti_text_archive_dll: vc-6_5 test_no_rtti_text_warchive: vc-6_5 test_no_rtti_text_warchive_dll: vc-6_5 test_no_rtti_xml_archive: vc-6_5 test_no_rtti_xml_archive_dll: vc-6_5 test_no_rtti_xml_warchive: vc-6_5 test_no_rtti_xml_warchive_dll: vc-6_5 test_shared_ptr_132_binary_archive: vc-6_5 vc-6_5-stlport test_shared_ptr_132_binary_archive_dll: vc-6_5 test_shared_ptr_132_text_archive: vc-6_5 vc-6_5-stlport test_shared_ptr_132_text_archive_dll: gcc-3_4_3-sunos vc-6_5 test_shared_ptr_132_text_warchive: vc-6_5 vc-6_5-stlport test_shared_ptr_132_text_warchive_dll: vc-6_5 test_shared_ptr_132_xml_archive: vc-6_5 vc-6_5-stlport test_shared_ptr_132_xml_archive_dll: vc-6_5 test_shared_ptr_132_xml_warchive: vc-6_5 vc-6_5-stlport test_shared_ptr_132_xml_warchive_dll: vc-6_5 test_shared_ptr_binary_archive: borland-5_6_4 vc-6_5 test_shared_ptr_binary_archive_dll: borland-5_6_4 vc-6_5 test_shared_ptr_text_archive: borland-5_6_4 vc-6_5 test_shared_ptr_text_archive_dll: borland-5_6_4 vc-6_5 test_shared_ptr_text_warchive: borland-5_6_4 vc-6_5 test_shared_ptr_text_warchive_dll: borland-5_6_4 vc-6_5 test_shared_ptr_xml_archive: borland-5_6_4 vc-6_5 test_shared_ptr_xml_archive_dll: borland-5_6_4 vc-6_5 test_shared_ptr_xml_warchive: borland-5_6_4 vc-6_5 test_shared_ptr_xml_warchive_dll: borland-5_6_4 vc-6_5

1 0

Boost regression notification (2005-09-30 [HEAD])
by Douglas Gregor 30 Sep '05

30 Sep '05

Boost regression test failures ------------------------------ Report time: 2005-09-30T05:00:12Z This report lists all regression test failures on release platforms. Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-HEAD/developer/issues… 123 failures in 9 libraries: concept_check (12) graph (2) mpl (1) parameter (12) serialization (33) spirit (8) thread (4) tuple (1) typeof (50) |concept_check| stl_concept_covering: cw-9_4 gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin intel-win32-9_0 intel-win32-9_0 mingw-3_4_2 vc-7_1 |graph| graphviz_test: vc-7_1 layout_test: intel-win32-9_0 |mpl| size_t: gcc-4_0-darwin |parameter| basics: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux efficiency: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-4_0-darwin macros: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux sfinae: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux unnamed: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux vc-7_1 |serialization| test_class_info_load_binary_archive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_binary_archive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_archive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_archive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_warchive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_warchive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_archive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_archive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_warchive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_warchive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_set_xml_archive: vc-7_1 test_set_xml_warchive: vc-7_1 test_simple_class_ptr_text_warchive_dll: vc-7_1 |spirit| action_tests_debug: gcc-3_4_3-sunos distinct_tests_debug: gcc-3_4_3-sunos escape_char_parser_tests_debug: gcc-3_4_3-sunos grammar_def_test_debug: gcc-3_4_3-sunos switch_problem_debug: gcc-3_4_3-sunos switch_tests_single_debug: gcc-3_4_3-sunos traverse_tests: intel-win32-9_0 traverse_tests_debug: intel-win32-9_0 |thread| test_condition: gcc-3_4_3-sunos test_mutex: gcc-3_4_3-sunos test_tss: gcc-3_4_3-sunos gcc-3_4_3-sunos |tuple| tuple_test_bench: gcc-3_4_3-sunos |typeof| data_member_native: cw-9_4 intel-win32-9_0 intel-win32-9_0 function_native: cw-9_4 intel-win32-9_0 intel-win32-9_0 function_ptr_native: cw-9_4 intel-win32-9_0 intel-win32-9_0 function_ref_native: cw-9_4 intel-win32-9_0 intel-win32-9_0 lvalue_native: cw-9_4 intel-win32-9_0 intel-win32-9_0 member_function_native: cw-9_4 intel-win32-9_0 intel-win32-9_0 modifiers_emulation: cw-9_4 modifiers_native: cw-9_4 intel-win32-9_0 intel-win32-9_0 noncopyable_native: cw-9_4 intel-win32-9_0 intel-win32-9_0 std_emulation: cw-9_4 std_native: cw-9_4 intel-win32-9_0 intel-win32-9_0 template_dependent_native: cw-9_4 intel-win32-9_0 intel-win32-9_0 template_enum_native: cw-9_4 intel-win32-9_0 intel-win32-9_0 template_int_native: cw-9_4 intel-win32-9_0 intel-win32-9_0 template_multiword_native: cw-9_4 intel-win32-9_0 intel-win32-9_0 template_tpl_native: cw-9_4 intel-win32-9_0 intel-win32-9_0 template_type_native: cw-9_4 intel-win32-9_0 intel-win32-9_0 type_native: cw-9_4 intel-win32-9_0 intel-win32-9_0

1 0

Unit test FP comparisons - memory leaks in debug
by Paul A Bristow 30 Sep '05

30 Sep '05

I have tried to use the Boost 1.33 Unit test FP comparison with MSVC 8.0 beta 2 and the example test_fp_comparisons.cpp works as expected in release mode (runs 5 tests ok) (Though not auto - Had to run it myself). Defines WIN32;NDEBUG;_CONSOLE but in debug mode I get: ------ Rebuild All started: Project: unit_test_framework, Configuration: Debug Win32 ------ Deleting intermediate and output files for project 'unit_test_framework', configuration 'Debug|Win32' Compiling... xml_report_formatter.cpp xml_log_formatter.cpp unit_test_suite.cpp unit_test_parameters.cpp unit_test_monitor.cpp unit_test_main.cpp unit_test_log.cpp test_tools.cpp results_reporter.cpp results_collector.cpp progress_monitor.cpp plain_report_formatter.cpp framework.cpp i:\boost_1_33_0\boost/test/impl/framework.ipp(313) : warning C4244: 'initializing' : conversion from 'time_t' to 'unsigned int', possible loss of data execution_monitor.cpp compiler_log_formatter.cpp Generating Code... i:\boost_1_33_0\boost\lexical_cast.hpp(223) : warning C4701: potentially uninitialized local variable 'result' used Creating library... Creating browse information file... Microsoft Browse Information Maintenance Utility Version 8.00.50215 Copyright (C) Microsoft Corporation. All rights reserved. Build log was saved at "file://c:\temp\boost_test_library\Debug\BuildLog.htm" unit_test_framework - 0 error(s), 2 warning(s) ------ Rebuild All started: Project: test_fp_comparisons, Configuration: Debug Win32 ------ Deleting intermediate and output files for project 'test_fp_comparisons', configuration 'Debug|Win32' Compiling... test_fp_comparisons.cpp Linking... Auto run test Running 5 test cases... Detected memory leaks! Dumping objects -> {150} normal block at 0x003163F8, 12 bytes long. Data: <long double > 6C 6F 6E 67 20 64 6F 75 62 6C 65 00 {149} normal block at 0x003163C0, 8 bytes long. Data: < c1 0a1 > F8 63 31 00 30 61 31 00 {139} normal block at 0x00316168, 7 bytes long. Data: <double > 64 6F 75 62 6C 65 00 {138} normal block at 0x00316130, 8 bytes long. Data: <ha1 `41 > 68 61 31 00 60 34 31 00 {126} normal block at 0x00313498, 6 bytes long. Data: <float > 66 6C 6F 61 74 00 {125} normal block at 0x00313460, 8 bytes long. Data: < 41 > 98 34 31 00 00 00 00 00 Object dump complete. Build log was saved at "file://c:\temp\boost_test_library\Debug\BuildLog.htm" test_fp_comparisons - 0 error(s), 0 warning(s) ========== Rebuild All: 2 succeeded, 0 failed, 0 skipped ========== _CONSOLE;WIN32;_DEBUG,BOOST_TEST_NO_AUTO_LINK are defined. Can anyone throw any light on this please? Thanks Paul Paul A Bristow Prizet Farmhouse, Kendal, Cumbria UK LA8 8AB +44 1539 561830 +44 7714 330204 mailto: pbristow(a)hetp.u-net.com www.hetp.u-net.com

2 5

Re: [boost] [serialization]A question about the implementation of XML_name in basic_xml_oarchive.ipp
by Martin Bonner 30 Sep '05

30 Sep '05

On 9/28/05, David Abrahams <dave(a)boost-consulting.com> wrote: >>> Hmm... Also, is the apparent dependency on ASCII encoding truly >>> portable? Caleb Epstein wrote: >> Doubtful. Wouldn't testing for std::isalnum || '-' || '_' be a >> better idea? Perhaps not quite as performant (once the lookup table >> was made static), but certainly more portable and simpler to read. Simon Buchan wrote: > In most implementations, the is*()'s are implemented using exactly the > same method. Yes, but the table will be different on an EBCDIC implementation than they are on an ASCII implementation. The point is that the specified table hard codes ASCII, so when somebody runs it on an IBM mainframe it will give the wrong answer. -- Martin Bonner Martin.Bonner(a)Pitechnology.com Pi Technology, Milton Hall, Ely Road, Milton, Cambridge, CB4 6WZ, ENGLAND Tel: +44 (0)1223 441434

3 2

[serialization]A question about the implementation of XML_name in basic_xml_oarchive.ipp
by Sean Huang 30 Sep '05

30 Sep '05

I ran across the implementation of XML_name. It is a functor used to validate each single character in an XML name. The initialization of a stack-based look-up table everytime the functor is called puzzles me (see excerpt below). void operator()(CharType t) const{ unsigned char lookup_table[] = { 0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0, 0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0, 0,0,0,0,0,0,0,0,0,0,1,1,0,0,0,0, // -. 1,1,1,1,1,1,1,1,1,1,0,0,0,0,0,0, // 0-9 0,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1, // A- 1,1,1,1,1,1,1,1,1,1,1,0,0,0,0,1, // -Z _ 0,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1, // a- 1,1,1,1,1,1,1,1,1,1,1,0,0,0,0,0, // -z 0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0, 0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 }; if((unsigned)t > 127) return; if(0 == lookup_table[(unsigned)t]) boost::throw_exception( xml_archive_exception( xml_archive_exception::xml_archive_tag_name_error ) ); } Is there any reason why it was done this way? For threading issues? Thanks, Sean

7 8

Interest in color library.
by Adam Badura 30 Sep '05

30 Sep '05

16 51

[iostreams] Build Message Typo
by David Abrahams 30 Sep '05

30 Sep '05

It looks like a semicolon was omitted just before "ECHO" Building Boost.Iostreams with bzip2 support disabled. ECHO To enable bzip2, consult the Boost.Iostreams documentation -- Dave Abrahams Boost Consulting www.boost-consulting.com

2 1

[filesystem] GetFileAttributesExA and Windows 95
by Angus Leeming 29 Sep '05

29 Sep '05

Beman, you use the WinAPI call GetFileAttributesExA only twice in Boost.Filesystem, in _is_empty and file_size, but that means that the code won't run on Windows 95: file is linked to missing export KERNEL32.DLL:GetFileAttributesExA The msdn docs http://msdn.microsoft.com/library/en-us/fileio/fs/getfileattributesex.asp suggest that Win95 support requires only that you grab NewAPIs.h from the SDK Update Site. Here's an example of how it should be used: ========================================================================== http://codeproject.com/win32/harddiskspace.asp?df=100&forumid=15107&exp=0&s… #define COMPILE_NEWAPIS_STUBS #define WANT_GETDISKFREESPACEEX_WRAPPER then in the file where you use GetDiskFreeSpaceEx.... #include <newapis.h> ========================================================================== Alternatively, I append a naïve implementation of the two files using GetFileAttributes and GetFileSize. Is any of this useful? Regards, Angus BOOST_FILESYSTEM_DECL bool _is_empty( const path & ph ) { DWORD const attributes = GetFileAttributes( ph.string().c_str() ); if ( attributes & INVALID_FILE_ATTRIBUTES ) boost::throw_exception( filesystem_error( "boost::filesystem::is_empty", ph, fs::detail::system_error_code() ) ); if ( attributes & FILE_ATTRIBUTE_DIRECTORY ) return is_empty_directory( ph ); DWORD file_size_high = DWORD const file_size_low = ::GetFileSize( ph.string().c_str(), &file_size_high ); if ( file_size_low == INVALID_FILE_SIZE ) { if ( GetLastError() = NO_ERROR ) boost::throw_exception( filesystem_error( "boost::filesystem::is_empty", ph, fs::detail::system_error_code() ) ); return ( !file_size_high && !file_size_low ); } BOOST_FILESYSTEM_DECL boost::intmax_t file_size( const path & ph ) { DWORD const attributes = GetFileAttributes( ph.string().c_str() ); if ( attributes & INVALID_FILE_ATTRIBUTES ) boost::throw_exception( filesystem_error( "boost::filesystem::is_empty", ph, fs::detail::system_error_code() ) ); if ( attributes & FILE_ATTRIBUTE_DIRECTORY ) boost::throw_exception( filesystem_error( "boost::filesystem::file_size", ph, "invalid: is a directory", is_directory_error ) ); DWORD file_size_high = DWORD const file_size_low = ::GetFileSize( ph.string().c_str(), &file_size_high ); if ( file_size_low == INVALID_FILE_SIZE ) { if ( GetLastError() = NO_ERROR ) boost::throw_exception( filesystem_error( "boost::filesystem::is_empty", ph, fs::detail::system_error_code() ) ); return (static_cast<boost::intmax_t>( file_size_high ) << (sizeof( file_size_low )*8)) + file_size_low }

4 11

(no subject)
by Paul A Bristow 29 Sep '05

29 Sep '05

I had been using Boost test with 1.32 successfully #include <boost/test/test_tools.hpp> #include <boost/test/floating_point_comparison.hpp> // Extra test tool for FP comparison. but with 1.33 it fails to compile at using boost::unit_test_framework::unit_test_log; using boost::unit_test_framework::log_level; and used this to control the log threshold unit_test_log::instance().set_log_threshold_level_by_name("test_suite"); and to switch the log file unit_test_log::instance().set_log_stream(flog); // Switch to log file.// unit_test_log::instance().set_log_stream(cout); // Switch back to cout, But this has been removed in 1.33 but I am unclear how to replicate this sort of function. Suggestions? Thanks Paul Paul A Bristow Prizet Farmhouse, Kendal, Cumbria UK LA8 8AB +44 1539 561830 +44 7714 330204 mailto: pbristow(a)hetp.u-net.com www.hetp.u-net.com

2 1

[boostbook] BOOST_ROOT vs BOOST_BUILD_PATH
by Martin Wille 29 Sep '05

29 Sep '05

Hi, the installation script for Boostbook contains: elif test -r "$BOOST_ROOT/tools/build/v2/user-config.jam"; then JAM_CONFIG_IN="$BOOST_ROOT/tools/build/v2/user-config.jam"; Shouldn't BOOST_BUILD_PATH be checked, too? Regards, m Send instant messages to your online friends http://au.messenger.yahoo.com

2 5

OT - to Mr Daryle Walker
by Robert Kawulak 29 Sep '05

29 Sep '05

Dear Mr Daryle Walker, Did you get my e-mail about improvements to integer.hpp? I haven't got any response from you, maybe my message was rejected by some automatic filter? Best regards, Robert ---------------------------------------------------------------------- Tak niesamowity CZAT... >>> http://link.interia.pl/f18ba

1 0

Unit test framework with 1.33 - logging
by Paul A Bristow 29 Sep '05

29 Sep '05

Sorry - reposted with subject :-(( | -----Original Message----- | From: boost-bounces(a)lists.boost.org | [mailto:boost-bounces@lists.boost.org] On Behalf Of Paul A Bristow | Sent: 28 September 2005 19:41 | To: boost(a)lists.boost.org | Subject: [boost] (no subject) | | I had been using Boost test with 1.32 successfully | | #include <boost/test/test_tools.hpp> | #include <boost/test/floating_point_comparison.hpp> // Extra | test tool for | FP comparison. | | but with 1.33 it fails to compile at | | using boost::unit_test_framework::unit_test_log; | using boost::unit_test_framework::log_level; | | and used this to control the log threshold | | | unit_test_log::instance().set_log_threshold_level_by_name("tes | t_suite"); | | and to switch the log file | | unit_test_log::instance().set_log_stream(flog); // Switch to log | file.// unit_test_log::instance().set_log_stream(cout); | // Switch back to | cout, | | But this has been removed in 1.33 | | but I am unclear how to replicate this sort of function. | | Suggestions? | | Thanks | | Paul | | Paul A Bristow | Prizet Farmhouse, Kendal, Cumbria UK LA8 8AB | +44 1539 561830 +44 7714 330204 | mailto: pbristow(a)hetp.u-net.com www.hetp.u-net.com | | | | _______________________________________________ | Unsubscribe & other changes: | http://lists.boost.org/mailman/listinfo.cgi/boost |

2 2

Boost regression notification (2005-09-29 [RC_1_33_0])
by Douglas Gregor 29 Sep '05

29 Sep '05

Boost regression test failures ------------------------------ Report time: 2005-09-29T14:30:10Z This report lists all regression test failures on release platforms. Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-RC_1_33_0/developer/i… 77 failures in 7 libraries: foreach (1) graph (4) iostreams (12) random (1) range (3) serialization (55) spirit (1) |foreach| rvalue_const: vc-7_1 |graph| betweenness_centrality_test: gcc-3.4.4-linux dag_longest_paths: gcc-3.4.4-linux dijkstra_cc: gcc-3.4.4-linux relaxed_heap_test: gcc-3.4.4-linux |iostreams| gzip_test: cw-9_5-darwin gcc-2.95.3-stlport-4.6.2-linux gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin gcc-4.0.1-linux gcc-4_0-darwin intel-8.1-linux intel-9.0-linux mingw-3_4_2 vc-7_1 |random| random_test: gcc-3.3.6-linux |range| array: vc-6_5 vc-6_5-stlport vc-7_0 |serialization| test_exported_binary_archive: vc-6_5 test_exported_binary_archive_dll: vc-6_5 test_exported_text_archive: vc-6_5 test_exported_text_archive_dll: vc-6_5 test_exported_text_warchive: vc-6_5 test_exported_text_warchive_dll: vc-6_5 test_exported_xml_archive: vc-6_5 test_exported_xml_archive_dll: vc-6_5 test_exported_xml_warchive: vc-6_5 test_exported_xml_warchive_dll: vc-6_5 test_no_rtti_binary_archive: vc-6_5 test_no_rtti_binary_archive_dll: vc-6_5 test_no_rtti_text_archive: vc-6_5 test_no_rtti_text_archive_dll: vc-6_5 test_no_rtti_text_warchive: vc-6_5 test_no_rtti_text_warchive_dll: vc-6_5 test_no_rtti_xml_archive: vc-6_5 test_no_rtti_xml_archive_dll: vc-6_5 test_no_rtti_xml_warchive: vc-6_5 test_no_rtti_xml_warchive_dll: vc-6_5 test_shared_ptr_132_binary_archive: vc-6_5 vc-6_5-stlport test_shared_ptr_132_binary_archive_dll: vc-6_5 test_shared_ptr_132_text_archive: vc-6_5 vc-6_5-stlport test_shared_ptr_132_text_archive_dll: vc-6_5 test_shared_ptr_132_text_warchive: vc-6_5 vc-6_5-stlport test_shared_ptr_132_text_warchive_dll: vc-6_5 test_shared_ptr_132_xml_archive: vc-6_5 vc-6_5-stlport test_shared_ptr_132_xml_archive_dll: vc-6_5 test_shared_ptr_132_xml_warchive: vc-6_5 vc-6_5-stlport test_shared_ptr_132_xml_warchive_dll: vc-6_5 test_shared_ptr_binary_archive: borland-5_6_4 vc-6_5 test_shared_ptr_binary_archive_dll: borland-5_6_4 vc-6_5 test_shared_ptr_text_archive: borland-5_6_4 vc-6_5 test_shared_ptr_text_archive_dll: borland-5_6_4 vc-6_5 test_shared_ptr_text_warchive: borland-5_6_4 vc-6_5 test_shared_ptr_text_warchive_dll: borland-5_6_4 vc-6_5 test_shared_ptr_xml_archive: borland-5_6_4 vc-6_5 test_shared_ptr_xml_archive_dll: borland-5_6_4 vc-6_5 test_shared_ptr_xml_warchive: borland-5_6_4 vc-6_5 test_shared_ptr_xml_warchive_dll: borland-5_6_4 vc-6_5 |spirit| parametric_tests: gcc-3_4_3-sunos

1 0

Boost regression notification (2005-09-29 [HEAD])
by Douglas Gregor 29 Sep '05

29 Sep '05

Boost regression test failures ------------------------------ Report time: 2005-09-29T05:00:18Z This report lists all regression test failures on release platforms. Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-HEAD/developer/issues… 123 failures in 9 libraries: concept_check (12) graph (2) mpl (1) parameter (12) serialization (33) spirit (8) thread (4) tuple (1) typeof (50) |concept_check| stl_concept_covering: cw-9_4 gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin intel-win32-9_0 intel-win32-9_0 mingw-3_4_2 vc-7_1 |graph| graphviz_test: vc-7_1 layout_test: intel-win32-9_0 |mpl| size_t: gcc-4_0-darwin |parameter| basics: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux efficiency: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-4_0-darwin macros: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux sfinae: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux unnamed: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux vc-7_1 |serialization| test_class_info_load_binary_archive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_binary_archive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_archive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_archive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_warchive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_warchive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_archive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_archive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_warchive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_warchive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_set_xml_archive: vc-7_1 test_set_xml_warchive: vc-7_1 test_simple_class_ptr_text_warchive_dll: vc-7_1 |spirit| action_tests_debug: gcc-3_4_3-sunos distinct_tests_debug: gcc-3_4_3-sunos escape_char_parser_tests_debug: gcc-3_4_3-sunos grammar_def_test_debug: gcc-3_4_3-sunos switch_problem_debug: gcc-3_4_3-sunos switch_tests_single_debug: gcc-3_4_3-sunos traverse_tests: intel-win32-9_0 traverse_tests_debug: intel-win32-9_0 |thread| test_condition: gcc-3_4_3-sunos test_mutex: gcc-3_4_3-sunos test_tss: gcc-3_4_3-sunos gcc-3_4_3-sunos |tuple| tuple_test_bench: gcc-3_4_3-sunos |typeof| data_member_native: cw-9_4 intel-win32-9_0 intel-win32-9_0 function_native: cw-9_4 intel-win32-9_0 intel-win32-9_0 function_ptr_native: cw-9_4 intel-win32-9_0 intel-win32-9_0 function_ref_native: cw-9_4 intel-win32-9_0 intel-win32-9_0 lvalue_native: cw-9_4 intel-win32-9_0 intel-win32-9_0 member_function_native: cw-9_4 intel-win32-9_0 intel-win32-9_0 modifiers_emulation: cw-9_4 modifiers_native: cw-9_4 intel-win32-9_0 intel-win32-9_0 noncopyable_native: cw-9_4 intel-win32-9_0 intel-win32-9_0 std_emulation: cw-9_4 std_native: cw-9_4 intel-win32-9_0 intel-win32-9_0 template_dependent_native: cw-9_4 intel-win32-9_0 intel-win32-9_0 template_enum_native: cw-9_4 intel-win32-9_0 intel-win32-9_0 template_int_native: cw-9_4 intel-win32-9_0 intel-win32-9_0 template_multiword_native: cw-9_4 intel-win32-9_0 intel-win32-9_0 template_tpl_native: cw-9_4 intel-win32-9_0 intel-win32-9_0 template_type_native: cw-9_4 intel-win32-9_0 intel-win32-9_0 type_native: cw-9_4 intel-win32-9_0 intel-win32-9_0

1 0

[Test] and [bjam] questions re DLLS
by Robert Ramey 29 Sep '05

29 Sep '05

I am making a test program in order to test the operation of the serialization library when serializable type is serialized from within a dynamically loaded DLL. I've made a DLL which serializes to a polymorphic_?archive. I'm going to make a test program which calls the DLL. Here are my questions: [Test] My DLL has included <boost/test/test_tools.hpp> and test tool macros. Things compile fine. When I try to link I get a failure because I've got not test_main - I'm using the Test Execution Monitor. Now that I think about it - its not clear at all how to address this. Suppose the above is resolved. I run my test and I get a failure in the DLL, will the exception propagate across the DLL interface into the main executable? I would hope so buf I don't know for sure. [bjam] Assuming the above issues are resolved I will have two program modules: test_dll_main and test_dll_A (dll to serialize class A). Not each bjam target lands in its own directory of the form bin/boost/libs/serialization/<test_module_name>.test/<compiler_name>/debug/threading-multi/test_module_name.exe I would guess that the dll lands in bin/boost/libs/serialization/<test_dll_name>.test/<compiler_name>/debug/threading-multi/test_dll_name.dll So in my main test module I would need something like dlopen or LoadLibrary ("bin/boost/libs/serialization/<test_module_name>.test/<compiler_name>/debug/threading-multi/test_module_name.exe") which is going to be pretty inconvenient or make sure that the test_dll is placed in the same target directory as test_main - which I don't know how to make bjam do. Is there any information on how to go about building and testing DLLS/Shared Libraries? Robert Ramey

3 3

Re: [boost] GUI
by Greer, Joe 29 Sep '05

29 Sep '05

> Thats a good point, but is that not convention only? Its not required > behaviour. > Suppose I am on an XWindows system and I want MSWindows behaviour. That > point > about locale is a good one. A sequence of user actions must map to a > state-machine that finally maps the sequence of clicks into a particular > function such as Maximise, Minimise, etc. Maybe its possible to load the > map If you want to have your application certified or branded on a particular platform, then you must follow the style guidelines. Most of the guidelines aren't written in stone, but gratuitous differences will prevent you from getting your app branded. For many, this is important. I think that any GUI should do its best to isolate the app logic from the presentation style and allow for OS specific GUI behaviors to be isolated away from the main program logic in order to facilitate easy porting to various OS-s rather than trying too hard to make it seamless, but vanilla. For example, something a simple as prompting for a file, Windows provides an API call for this that puts up the appropriate dialog box to navigate to the file and select it. The box may be different depending upon which version of Windows the app is running on, but the application doesn't have to care and they will know that the boxes are arranged in the appropriate order, have the right tab stops and shortcuts etc. Every ported app I have seen gets this wrong and it is amazing how jarring that is. I imagine that Mac users would feel the same, if they were prompted with a box that doesn't meet the Mac guidelines. This kind of thing is important for commercial apps. I am not sure how to accomplish this separation of app logic vs GUI logic, but it needs done if you want it used on non-unix systems. A GUI that is tailored to allow unix developers to port to Windows and Mac gets a big yawn from me. I would like a system that encourages developers from every platform to write their apps in a way that allows it to work everywhere and to do that, things need to be able to follow different style guidelines. I'm rambling now, so I will quit. :) Joe

1 0

Re: [boost] [cstdint] uintptr_t and intptr_t are missing
by Martin Bonner 29 Sep '05

29 Sep '05

----Original Message---- From: Joaquin M Lopez Munoz [mailto:joaquin@tid.es] > Is BOOST_HAS_INTPTR_TYPES supposed to inform whether there > are vendor-provided ::intrptr_t/::uintrptr_t types? If so, I > fail to see its utility, since boost::intrptr_t/boost::untrptr_t > can be provided universally. Not if the compiler doesn't HAVE a integral type which can hold a pointer. For example, a compiler for Intel processors with 32 bit longs, no long long, and 16:32 pointers. -- Martin Bonner Martin.Bonner(a)Pitechnology.com Pi Technology, Milton Hall, Ely Road, Milton, Cambridge, CB4 6WZ, ENGLAND Tel: +44 (0)1223 441434

3 3

[integer] Create (u)int_natural_t
by Daryle Walker 29 Sep '05

29 Sep '05

The "int" type was supposed to match the processor's natural built-in integer processor. That was easy to maintain in the 16- and 32-bit eras, but got screwed up when we started 64-bit computing. The C and C++ communities decided to expand its integer types by keeping the current types at their 32-bit-era sizes and extended the type system with a "long long" instead of moving "int" and "long" up and adding a "short short". Now we don't have a convenient way to name the best integer type in a portable fashion. I suggest we add a "int_natural_t" typedef to <boost/cstdint.hpp> to name the best integer type (and a corresponding "uint_natural_t"). We would have to research what that type is for each compiler and/or platform combination and use #conditionals. -- Daryle Walker Mac, Internet, and Video Game Junkie darylew AT hotmail DOT com

2 1

[serialization] JSON: a potential archive format?
by Daryle Walker 29 Sep '05

29 Sep '05

I was wandering around the web and saw a specification page about JSON (JavaScript Object Notation). Maybe it could be used as a new archive format for the serialization library. I looked at "Introducing JSON" @ <http://www.crockford.com/JSON/>. -- Daryle Walker Mac, Internet, and Video Game Junkie darylew AT hotmail DOT com

1 0

[asio] how detect deadline_timer expired state?
by BRIDGES Dick 29 Sep '05

29 Sep '05

I'm performing an async_wait() on a deadline_timer. Based upon some independent event (e.g., a keystroke) I want to [re]set the timer and, if it was expired, 'fire' an event indicating that the system has changed state from not_running to running. Maybe I'm missing something obvious, but it seems that deadline_timer should have a method to test whether or not the timer had expired (i.e., bool expired() ). BTW: This library is a joy. When does the review period start? ;) Regards, Dick Bridges

2 1

[review] results xpressive
by Thomas Witt 28 Sep '05

28 Sep '05

Hi All, I am happy to announce that xpressive has been accepted into boost. That being said I would like to thank Eric for writing such a high quality library and all the reviewers for the significant time they spent in reviewing the library. I have received some very detailed in depth reviews of the library. This has made my job really easy. Thanks! While xpressive is accepted without conditions I'd like to point out that the test coverage should be improved in the future. Thomas Review Manager xpressive Thomas Witt witt(a)acm.org

3 2

Re: [boost] BOOST_ASSERT and __assume on MSVC
by brangdon＠cix.compulink.co.uk 28 Sep '05

28 Sep '05

In-Reply-To: <200509261722.j8QHMRms015648(a)shannonhoon.balstatdev.susq.com> stewart(a)sig.com (Rob Stewart) wrote (abridged): > > (e) is false, then the __assume tells us the sequence won't be > > executed at all, and both it and the BOOST_ASSERT can be optimised > > away. Whatever it > > If (e) is false, then BOOST_ASSERT takes some action, be it > invoking assert() or something else. Only if it's not optimised away. Here's my thinking. For clarity I'll write it like this, factoring out the common sub-expression: if (e) { BOOST_ASSERT( true ); __assume( true ); } else { BOOST_ASSERT( false ); __assume( false ); } The compiler knows that __assume(false) can never be reached so it can optimise away the whole "else" clause - provided it can prove that the BOOST_ASSERT always returns. In general it is dangerous to put other stuff in the same control block as __assume(false), because you don't know how clever the compiler will be about proving stuff like that. In this case you could argue that the compiler /cannot/ prove that BOOST_ASSERT will return; indeed in many cases it won't return. Even so I think it is a bit dangerous, but I suppose it doesn't really matter. -- Dave Harris, Nottingham, UK.

2 1

[Boost-bugs] [ boost-Bugs-1307179 ] c_local_adjustor is not thread-safe due to using localtime()
by SourceForge.net 28 Sep '05

28 Sep '05

Bugs item #1307179, was opened at 2005-09-28 19:59 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=107586&aid=1307179&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: date_time Group: None Status: Open Resolution: None Priority: 5 Submitted By: Krzysztof Lichota (klichota) Assigned to: Jeff Garland (az_sw_dude) Summary: c_local_adjustor is not thread-safe due to using localtime() Initial Comment: c_local_adjustor is not thread-safe due to using localtime(). It should be changed to use localtime_r() or, at least, docs should mention that it is not thread-safe. The same applies to all other boost units using localtime(). ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=107586&aid=1307179&group_… ------------------------------------------------------- This SF.Net email is sponsored by: Power Architecture Resource Center: Free content, downloads, discussions, and more. http://solutions.newsforge.com/ibmarch.tmpl _______________________________________________ Boost-bugs mailing list Boost-bugs(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/boost-bugs

1 0

Boost regression notification (2005-09-28 [RC_1_33_0])
by Douglas Gregor 28 Sep '05

28 Sep '05

Boost regression test failures ------------------------------ Report time: 2005-09-28T14:11:11Z This report lists all regression test failures on release platforms. Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-RC_1_33_0/developer/i… 76 failures in 7 libraries: bind (1) foreach (1) graph (4) iostreams (11) random (1) range (3) serialization (55) |bind| bind_cv_test: gcc-4_0-darwin |foreach| rvalue_const: vc-7_1 |graph| betweenness_centrality_test: gcc-3.4.4-linux dag_longest_paths: gcc-3.4.4-linux dijkstra_cc: gcc-3.4.4-linux relaxed_heap_test: gcc-3.4.4-linux |iostreams| gzip_test: cw-9_5-darwin gcc-2.95.3-stlport-4.6.2-linux gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin gcc-4.0.1-linux gcc-4_0-darwin intel-8.1-linux intel-9.0-linux vc-7_1 |random| random_test: gcc-3.3.6-linux |range| array: vc-6_5 vc-6_5-stlport vc-7_0 |serialization| test_exported_binary_archive: vc-6_5 test_exported_binary_archive_dll: vc-6_5 test_exported_text_archive: vc-6_5 test_exported_text_archive_dll: vc-6_5 test_exported_text_warchive: vc-6_5 test_exported_text_warchive_dll: vc-6_5 test_exported_xml_archive: vc-6_5 test_exported_xml_archive_dll: vc-6_5 test_exported_xml_warchive: vc-6_5 test_exported_xml_warchive_dll: vc-6_5 test_no_rtti_binary_archive: vc-6_5 test_no_rtti_binary_archive_dll: vc-6_5 test_no_rtti_text_archive: vc-6_5 test_no_rtti_text_archive_dll: vc-6_5 test_no_rtti_text_warchive: vc-6_5 test_no_rtti_text_warchive_dll: vc-6_5 test_no_rtti_xml_archive: vc-6_5 test_no_rtti_xml_archive_dll: vc-6_5 test_no_rtti_xml_warchive: vc-6_5 test_no_rtti_xml_warchive_dll: vc-6_5 test_shared_ptr_132_binary_archive: vc-6_5 vc-6_5-stlport test_shared_ptr_132_binary_archive_dll: vc-6_5 test_shared_ptr_132_text_archive: vc-6_5 vc-6_5-stlport test_shared_ptr_132_text_archive_dll: vc-6_5 test_shared_ptr_132_text_warchive: vc-6_5 vc-6_5-stlport test_shared_ptr_132_text_warchive_dll: vc-6_5 test_shared_ptr_132_xml_archive: vc-6_5 vc-6_5-stlport test_shared_ptr_132_xml_archive_dll: vc-6_5 test_shared_ptr_132_xml_warchive: vc-6_5 vc-6_5-stlport test_shared_ptr_132_xml_warchive_dll: vc-6_5 test_shared_ptr_binary_archive: borland-5_6_4 vc-6_5 test_shared_ptr_binary_archive_dll: borland-5_6_4 vc-6_5 test_shared_ptr_text_archive: borland-5_6_4 vc-6_5 test_shared_ptr_text_archive_dll: borland-5_6_4 vc-6_5 test_shared_ptr_text_warchive: borland-5_6_4 vc-6_5 test_shared_ptr_text_warchive_dll: borland-5_6_4 vc-6_5 test_shared_ptr_xml_archive: borland-5_6_4 vc-6_5 test_shared_ptr_xml_archive_dll: borland-5_6_4 vc-6_5 test_shared_ptr_xml_warchive: borland-5_6_4 vc-6_5 test_shared_ptr_xml_warchive_dll: borland-5_6_4 vc-6_5

1 0

Boost regression notification (2005-09-28 [HEAD])
by Douglas Gregor 28 Sep '05

28 Sep '05

Boost regression test failures ------------------------------ Report time: 2005-09-28T05:00:20Z This report lists all regression test failures on release platforms. Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-HEAD/developer/issues… 124 failures in 11 libraries: concept_check (12) graph (2) mpl (1) parameter (12) python (3) serialization (30) spirit (8) thread (4) tuple (1) typeof (50) wave (1) |concept_check| stl_concept_covering: cw-9_4 gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin intel-win32-9_0 intel-win32-9_0 mingw-3_4_2 vc-7_1 |graph| graphviz_test: vc-7_1 layout_test: intel-win32-9_0 |mpl| size_t: gcc-4_0-darwin |parameter| basics: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux efficiency: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-4_0-darwin macros: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux sfinae: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux unnamed: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux vc-7_1 |python| back_reference: vc-7_1 slice: vc-7_1 virtual_functions: vc-7_1 |serialization| test_class_info_load_binary_archive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_binary_archive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_archive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_archive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_warchive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_warchive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_archive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_archive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_warchive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_warchive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin |spirit| action_tests_debug: gcc-3_4_3-sunos distinct_tests_debug: gcc-3_4_3-sunos escape_char_parser_tests_debug: gcc-3_4_3-sunos grammar_def_test_debug: gcc-3_4_3-sunos switch_problem_debug: gcc-3_4_3-sunos switch_tests_single_debug: gcc-3_4_3-sunos traverse_tests: intel-win32-9_0 traverse_tests_debug: intel-win32-9_0 |thread| test_condition: gcc-3_4_3-sunos test_mutex: gcc-3_4_3-sunos test_tss: gcc-3_4_3-sunos gcc-3_4_3-sunos |tuple| tuple_test_bench: gcc-3_4_3-sunos |typeof| data_member_native: cw-9_4 intel-win32-9_0 intel-win32-9_0 function_native: cw-9_4 intel-win32-9_0 intel-win32-9_0 function_ptr_native: cw-9_4 intel-win32-9_0 intel-win32-9_0 function_ref_native: cw-9_4 intel-win32-9_0 intel-win32-9_0 lvalue_native: cw-9_4 intel-win32-9_0 intel-win32-9_0 member_function_native: cw-9_4 intel-win32-9_0 intel-win32-9_0 modifiers_emulation: cw-9_4 modifiers_native: cw-9_4 intel-win32-9_0 intel-win32-9_0 noncopyable_native: cw-9_4 intel-win32-9_0 intel-win32-9_0 std_emulation: cw-9_4 std_native: cw-9_4 intel-win32-9_0 intel-win32-9_0 template_dependent_native: cw-9_4 intel-win32-9_0 intel-win32-9_0 template_enum_native: cw-9_4 intel-win32-9_0 intel-win32-9_0 template_int_native: cw-9_4 intel-win32-9_0 intel-win32-9_0 template_multiword_native: cw-9_4 intel-win32-9_0 intel-win32-9_0 template_tpl_native: cw-9_4 intel-win32-9_0 intel-win32-9_0 template_type_native: cw-9_4 intel-win32-9_0 intel-win32-9_0 type_native: cw-9_4 intel-win32-9_0 intel-win32-9_0 |wave| testwave: gcc-3.3.6-linux

1 0

[Boost-bugs] [ boost-Bugs-1307106 ] extended_type_info crash on global dtors (arm)
by SourceForge.net 28 Sep '05

28 Sep '05

Bugs item #1307106, was opened at 2005-09-28 09:47 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=107586&aid=1307106&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: serialization Group: None Status: Open Resolution: None Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Robert Ramey (ramey) Summary: extended_type_info crash on global dtors (arm) Initial Comment: Hello, i'm struggling with boost::serialization lib again ... I am using RC0_1.33 which has fixed some serialization stuff for me (1.33 was totally unusable for me due to that bugs). Now i seem to have encountered another problem... I am using the boost framework in cross platform projects: gcc 3.4.4: cygwin (win32), linux x86, linux arm gcc 4.0.1: cygwin (win32), linux x86, linux arm msvc 7.1: win32 After upgrading to 1.33/RC0 i get crashes on linux "ARM" processor platform (binaries). "pure virtual function call " -> SIGABRT The cross compiler is verified to work fine (3.4.4). After endless hours of debugging (thanks to that gdb/gdbserver 6.3 trash) i tracked it down to a specific serialization problem? Attached is a shortened gdb/server session (target = arm7tdmi)... It only occurs on arm platform (little endian), the same compiler on x86 (gcc 3.4.4) produces valid code. No crashes. Boost 1.32 worked flawlessly on all platforms with same compilers but it doesnt count because serialization has changed much between 1.32 and 1.33 (= could be anything) >From what i can see, the "return less_than(rhs); " operation is called on"boost::serialization::extended_type_info" object, resulting in pure virtual function call. I have no clue where to search/begin for error ... i can only debug on target (arm processor bord) with gdbserver which make it a mess (global dtors). I verified the "extended_type_info_typeid.cpp" code is linked in and the function: BOOST_SERIALIZATION_DECL(bool) extended_type_info_typeid_0::less_than(const extended_type_info &rhs) const { return 0 != get_eti().before( static_cast<const extended_type_info_typeid_0 &>(rhs).get_eti() ); } does exist in code. This is the offending snippet: ------------------------------------------------- BOOST_SERIALIZATION_DECL(bool) extended_type_info::operator<(const extended_type_info &rhs) const { int i = type_info_key_cmp(rhs); if(i < 0) return true; if(i > 0) return false; return less_than(rhs); <---- pure virtual function call !!! } ------------------------------------------------- The object instance itself seems ok, though i dont know how to validate vtable stuff because im not gdb expert. What gives? Regards, A. Focht ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=107586&aid=1307106&group_… ------------------------------------------------------- This SF.Net email is sponsored by: Power Architecture Resource Center: Free content, downloads, discussions, and more. http://solutions.newsforge.com/ibmarch.tmpl _______________________________________________ Boost-bugs mailing list Boost-bugs(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/boost-bugs

1 0

Are we seriously planning to release 1.33.1 in a few days?
by David Abrahams 28 Sep '05

28 Sep '05

The regression reports for RC_1_33_0 are still showing 78 failures. Can we get rid of those in time? Is it working to alert developers to regressions in their libraries? -- Dave Abrahams Boost Consulting www.boost-consulting.com

2 1

'noncopyable' : base class undefined
by Jing-Hsuan 28 Sep '05

28 Sep '05

Hi, I attempt to port program from x86 to arm, so I move the code from vc7.1 to evc4. But I encounter some problem.... By include <boost/utility.hpp>, I use class noncopyable to a base class, and derive my own class from noncopyable. In vc7.1 it works fine, while evc4 doesn't. Error message: error C2504: 'noncopyable' : base class undefined Any suggestion? Best Regards.

2 1

[serialization] a pattern for serialization and plugins
by Thomas Conway 28 Sep '05

28 Sep '05

Hi all, I'm trying to use the serialization library for the first time and I'm wondering if there is an extant solution for the problem I'm trying to solve. I have an application which has dynamicly loaded plugin modules. The application structure is something like: main app: ---- class base { ... template <class Archive> void serialize(Archive& pAr, unsigned int pVer) { ... } ... }; class baseFactory { shared_ptr<base> create(...) = 0; }; ---- plugin: ---- class myPluginN : public base { ... template <class Archive> void serialize(Archive& pAr, unsigned int pVer) { ... } }; class myPluginNFactory : public baseFactory { shared_ptr<base> create(...); }; extern "C" { void* makeFactory(); } ---- Now the problem is that by my reading of the serialization library documentation, the registration of derived classes is going to present difficulties. If I understand things correctly, derived classes need to be registered, and the archive contains a "tag" for each derived class. Now in this instance the set of derived classes is dynamic, and I don't want to require the set of derived classes to be the same in order to be able to load a structure. Of course, all the derived classes that are used in the structure must be loaded (of course, I'd like to serialization code to attempt to load any that are required but not already loaded), but I don't want the archive to depend on any derived classes that are not used. So the question really is: is this a solved problem? And if so, what is the solution? Also, the structures contain pointers to members of other structures (e.g. class Foo { .... }; class Bar { Foo foo; }; class Baz { Foo* fooPtr; }; ... shared_ptr<Bar> bar(new Bar); shared_ptr<Baz> baz(new Baz); baz->fooPtr = &(bar->foo); ) Will the obvious serialization code Bar::serialize(...) { ar & foo; } Baz::serialize(...) { ar & fooPtr; } do the right thing? thanks to anyone who can shed some light, Tom

2 1

[BGL] compile error in python bindings
by Georg Baum 28 Sep '05

28 Sep '05

Hi, when I try to compile the python bindings of Boost.Graph (current CVS) I get the compilation errors shown in the attached log file. This is with gcc version 3.3.4 (pre 3.3.5 20040809) on Linux. The errors are introduced with the recent changes related to named parameters of biconnected_components.hpp: http://cvs.sourceforge.net/viewcvs.py/boost/boost/boost/graph/biconnected_c… Does anybody have a clue what to do? Should the python bindings be converted to the named parameter version? If yes, how? Georg

2 2

[serialization docs] Ping?
by Kim Barrett 28 Sep '05

28 Sep '05

This is in regard to the discussion of the "equivalence" of a serialized object and the deserialized counterpart. It also touches on the Serializable concept and some recent discussion of how classes without default constructors can be handled, and a few other things besides. (Sorry about the entanglement, but I'm not sure how to separate some of these issues.) (Note that I also haven't read *all* of the mail on this subject yet.) The Common Lisp committee (X3J13) needed to deal with essentially the same problem. First, a bit of background. Because CL supports programmatic construction of code which can then be passed to the compiler, and the code "syntax" supports a quoting form for referring to a literal constant, there was a need to address what it meant for various kinds of objects to appear in such a context. And the resulting objects may be referred to in code will be compiled to a file for later loading into the same or some completely different runtime environment. Earlier versions of the language simply listed all the cases for the "built-in" types, and a simple mechanism for the simple record type provided by the language (things defined with defstruct, if you care). But with the addition of OO concepts in various implementations that eventually led to CLOS (the CL Object System), it was realized that this wasn't sufficient. The term that was eventually adopted was "similar" or "similar as constants" where further disambiguation was needed. I think that would be a good term for the serialization library to adopt, as it avoids an implications related to operator== and the ambiguity around the word "equivalent". A protocol was designed to permit instances of arbitrary user-defined classes to be saved and loaded. (Sound familiar? Note that support for different data formats for that saving and restoring was only addressed to the extent that different CL implementations likely had different compiled file formats and were not required to be compatible; something like the idea of binary / text / XML / whatever archives was not addressed, and never even came up, so far as I can recall. A missed opportunity there.) The relevant part of the specification is Section 3.2.4, "Literal Objects in Compiled Files", which can be found at: http://www.lisp.org/HyperSpec/Body/sec_3-2-4.html and in the definition of make-load-form, found here: http://www.lisp.org/HyperSpec/Body/stagenfun_make-load-form.html#make-load-… (Let me know if / where translation between CL terminology and C++ terminology would be helpful and I'll give it a shot.) The CL term "externalizable object" corresponds to the Serializable concept for the serialization library. Corresponding to the Save / Load Archive compatibility concept, CL says: "The \term{file compiler} must cooperate with the \term{loader} in order to assure that in each case where an \term{externalizable object} is processed as a \term{literal object}, the \term{loader} will construct a \term{similar} \term{object}." Substituting serialization library terminology into that quote: The saving archive must cooperate with the loading archive in order to assure that in each case where a serializable object is saved, the loading archive will construct a similar object. I think it should be reasonably straightforward to massage this into a statement about whether a saving archive and a loading archive are compatible. The CL protocol for loading involved a two step process. First, a constructor is called with some arguments. Then, optionally, an initialization form is called called, which contains references to the constructed object in order to perform additional modifications to it. I *think* this protocol is strictly more powerful than that presently specified by the serialization library. An example of a class that I don't know how to "serialize" is a "symbol" lazily constructed on named lookup; the save/load_construct_data mechanism is inadequate for this. (There are also object graphs containing reference cycles that might not be serializable but are CL externalizable, because the reference cycle can be broken by using the two stage protocol. I haven't looked to see whether the serialization library installs an object in the "pointer table" (whatever it is called) at allocation time or only after it has been initialized via deserialization.) Attempting to translate the CL protocol into C++ terminology, I think it would consist of first calling a static factory function associated with the type, passing it the archive as an argument, and then calling a member function on the object, again passing the archive as an argument.

4 9

Re: [boost] [vacpp] Problems porting to z/OS - was Errors compiling multi_index hashed.cpp
by Christopher Cambly 27 Sep '05

27 Sep '05

David Crayford wrote: > Sean Perry <perry <at> ca.ibm.com> writes: > >> >> What version of the compiler are you using. It appears that you are >> using >> the v1r2 compiler. I suggest trying the v1r6 compiler. >> > Sean, > > I'm using the V1R6 compiler, unless the build is bad. I've copied the > boost libraries into HFS files in USS and compiling on z/OS using a path > option. If you guys in Toronto can help in any way it will be a very big > help. > The reason we ask is that the message: "/FTS1/tmp/doc/boost/mpl/aux_/integral_wrapper.hpp", line 85.30: CCN5431 (S) The declarator cannot be qualified with the enclosing namespace "mpl_". seems to be a V1R2 specific message. Our RCS shows the message was removed from the compiler prior to the V1R6 release. The compiler macros on zOS are __IBMCPP__ == 41020 for V1R2 and __IBMCPP__ == 41060 for V1R6. Could you please verify the compiler version for us by compiling the following: //begin t.C #if (__IBMCPP__ == 41020) #error Using V1R2 #endif #if (__IBMCPP__ == 41060) #error Using V1R6 #endif //end t.C We are a little confused as to the source of this message. Thanks, Chris IBM XL Compiler Development

1 0

Sourceforge bug database
by Peter Dimov 27 Sep '05

27 Sep '05

We still have hundreds of open bug reports in the SF database. Is this acceptable for an organization of Boost's caliber? Don't we need a 'QA wizard'? -- Peter Dimov http://www.pdimov.com

5 5

Re: [boost] What is Boost?
by Jost, Andrew 27 Sep '05

27 Sep '05

> From: boost-bounces(a)lists.boost.org > [mailto:boost-bounces@lists.boost.org] On Behalf Of David Abrahams > We really need a section at the top of the page titled "What > is Boost?" Are you thinking of a section to replace "Welcome to Boost.org", or perhaps just a new subheading? Something like this: WELCOME TO BOOST.ORG! What is Boost: ... Getting started: ... Background: ... > * Boost is a collection of C++ libraries > - Free for any use > - Extensively peer-reviewed > - Extensively Tested (replace first sentence with the following) What is Boost: Boost is an organization of developers dedicated to the advancement of C++. Boost provides a collection of C++ libraries that improve the utility and portability of C++. Boost uses a highly collaborative, peer-reviewed development process. Boost libraries are completely free for any use, and are thoroughly tested on several platforms. "We emphasize libraries that work..." (possibly make further edits to existing passage) > * When you download Boost, you get the whole collection > > * There are some dependencies among libraries, but they are not > tightly coupled > > * There is a tool (bcp) for extracting the parts you want and their > dependencies. > > * Many boost libraries can be used just by putting the library > collection's top directory in your #include path. Complete > instructions for getting started are at: ___ > > * The important features of the Boost directory structure are: > - boost > - libs > - more > - tools > (with rough descriptions of each) Perhaps this could be added under the "Getting started:" subheading? That is, unless it would make that section too long. The current page is nicely formatted into digestible chucks -- I would be wary of breaking up the visual flow. -Andy

1 0

Boost regression notification (2005-09-27 [HEAD])
by Douglas Gregor 27 Sep '05

27 Sep '05

Boost regression test failures ------------------------------ Report time: 2005-09-27T05:00:25Z This report lists all regression test failures on release platforms. Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-HEAD/developer/issues… 88 failures in 8 libraries: bind (14) concept_check (10) graph (1) mpl (1) parameter (12) serialization (33) typeof (16) wave (1) |bind| bind_rv_sp_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin gcc-3_4_3-sunos mingw-3_4_2 mem_fn_rv_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin gcc-3_4_3-sunos mingw-3_4_2 |concept_check| stl_concept_covering: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin intel-win32-9_0 mingw-3_4_2 vc-7_1 |graph| graphviz_test: vc-7_1 |mpl| size_t: gcc-4_0-darwin |parameter| basics: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux efficiency: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-4_0-darwin macros: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux sfinae: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux unnamed: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux vc-7_1 |serialization| test_class_info_load_binary_archive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_binary_archive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_archive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_archive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_warchive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_warchive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_archive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_archive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_warchive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_warchive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_polymorphic_xml_archive_dll: vc-7_1 test_polymorphic_xml_warchive: vc-7_1 test_polymorphic_xml_warchive_dll: vc-7_1 |typeof| data_member_native: intel-win32-9_0 function_native: intel-win32-9_0 function_ptr_native: intel-win32-9_0 function_ref_native: intel-win32-9_0 lvalue_native: intel-win32-9_0 member_function_native: intel-win32-9_0 modifiers_native: intel-win32-9_0 noncopyable_native: intel-win32-9_0 std_native: intel-win32-9_0 template_dependent_native: intel-win32-9_0 template_enum_native: intel-win32-9_0 template_int_native: intel-win32-9_0 template_multiword_native: intel-win32-9_0 template_tpl_native: intel-win32-9_0 template_type_native: intel-win32-9_0 type_native: intel-win32-9_0 |wave| testwave: gcc-3.3.6-linux

4 4

Sandbox CVS access
by Cromwell Enage 27 Sep '05

27 Sep '05

Howdy, howdy. It's been almost a year and a half since my last dance with the Sandbox CVS. I'm trying to follow <http://www.bsdconsulting.no/wincvs-ssh/> to get myself reacquainted, and I reached the point where PuTTY logs in successfully, but the host says I can't execute anything there; no checkouts or anything using my account. Do I need "reactivation" or something like that? My SourceForge account is "expaler". Cromwell D. Enage __________________________________ Yahoo! Mail - PC Magazine Editors' Choice 2005 http://mail.yahoo.com

3 4

Boost regression notification (2005-09-27 [RC_1_33_0])
by Douglas Gregor 27 Sep '05

27 Sep '05

Boost regression test failures ------------------------------ Report time: 2005-09-27T15:10:08Z This report lists all regression test failures on release platforms. Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-RC_1_33_0/developer/i… 78 failures in 7 libraries: bind (1) foreach (1) graph (5) iostreams (12) random (1) range (3) serialization (55) |bind| bind_cv_test: gcc-4_0-darwin |foreach| rvalue_const: vc-7_1 |graph| betweenness_centrality_test: gcc-3.4.4-linux dag_longest_paths: gcc-3.4.4-linux dijkstra_cc: gcc-3.4.4-linux dijkstra_heap_performance: gcc-3.4.4-linux relaxed_heap_test: gcc-3.4.4-linux |iostreams| gzip_test: cw-9_5-darwin gcc-2.95.3-stlport-4.6.2-linux gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin gcc-4.0.1-linux gcc-4_0-darwin intel-8.1-linux intel-9.0-linux mingw-3_4_2 vc-7_1 |random| random_test: gcc-3.3.6-linux |range| array: vc-6_5 vc-6_5-stlport vc-7_0 |serialization| test_exported_binary_archive: vc-6_5 test_exported_binary_archive_dll: vc-6_5 test_exported_text_archive: vc-6_5 test_exported_text_archive_dll: vc-6_5 test_exported_text_warchive: vc-6_5 test_exported_text_warchive_dll: vc-6_5 test_exported_xml_archive: vc-6_5 test_exported_xml_archive_dll: vc-6_5 test_exported_xml_warchive: vc-6_5 test_exported_xml_warchive_dll: vc-6_5 test_no_rtti_binary_archive: vc-6_5 test_no_rtti_binary_archive_dll: vc-6_5 test_no_rtti_text_archive: vc-6_5 test_no_rtti_text_archive_dll: vc-6_5 test_no_rtti_text_warchive: vc-6_5 test_no_rtti_text_warchive_dll: vc-6_5 test_no_rtti_xml_archive: vc-6_5 test_no_rtti_xml_archive_dll: vc-6_5 test_no_rtti_xml_warchive: vc-6_5 test_no_rtti_xml_warchive_dll: vc-6_5 test_shared_ptr_132_binary_archive: vc-6_5 vc-6_5-stlport test_shared_ptr_132_binary_archive_dll: vc-6_5 test_shared_ptr_132_text_archive: vc-6_5 vc-6_5-stlport test_shared_ptr_132_text_archive_dll: vc-6_5 test_shared_ptr_132_text_warchive: vc-6_5 vc-6_5-stlport test_shared_ptr_132_text_warchive_dll: vc-6_5 test_shared_ptr_132_xml_archive: vc-6_5 vc-6_5-stlport test_shared_ptr_132_xml_archive_dll: vc-6_5 test_shared_ptr_132_xml_warchive: vc-6_5 vc-6_5-stlport test_shared_ptr_132_xml_warchive_dll: vc-6_5 test_shared_ptr_binary_archive: borland-5_6_4 vc-6_5 test_shared_ptr_binary_archive_dll: borland-5_6_4 vc-6_5 test_shared_ptr_text_archive: borland-5_6_4 vc-6_5 test_shared_ptr_text_archive_dll: borland-5_6_4 vc-6_5 test_shared_ptr_text_warchive: borland-5_6_4 vc-6_5 test_shared_ptr_text_warchive_dll: borland-5_6_4 vc-6_5 test_shared_ptr_xml_archive: borland-5_6_4 vc-6_5 test_shared_ptr_xml_archive_dll: borland-5_6_4 vc-6_5 test_shared_ptr_xml_warchive: borland-5_6_4 vc-6_5 test_shared_ptr_xml_warchive_dll: borland-5_6_4 vc-6_5

1 0

Compiler Status page outdated?
by David Abrahams 27 Sep '05

27 Sep '05

http://www.boost.org/status/compiler_status.html looks like it is in need of some attention. The links pointing to http://boost.sourceforge.net/regression-logs/ all need to be changed to point at the meta-comm tables. The former view is wrong for most users, and many of the links on that page point to the wrong places, too. Also, the "how to read the tables" stuff describes a table format we're not really generating for most platforms. I hate to just complain, but I've never even edited the page, can't take the time to fix it right now, and don't know who might be responsible for it (if anyone). I hope someone can step up to fix it. Thanks, -- Dave Abrahams Boost Consulting www.boost-consulting.com

1 0

Review status page out of date?
by David Abrahams 27 Sep '05

27 Sep '05

http://www.boost.org/more/formal_review_schedule.html seems to me to be quite outdated, and maybe inconsistent, too (e.g. TR1 is under review now but it appears in the queue after policy_ptr, which hasn't been reviewed yet). This seems to be a recurring problem. I'm wondering if it would be a good idea to bring on a co-review-wizard to ease the administrative burden of this job, so the page would stay current? Tom? -- Dave Abrahams Boost Consulting www.boost-consulting.com

1 0

Are there any interest in a pimpl library?
by Asger Mangaard 27 Sep '05

27 Sep '05

More precisely one cpp and one hpp file that implements the pimpl idiom? Regards, Asger Mangaard

2 2

[Boost-bugs] [ boost-Bugs-1305885 ] Exception safety in class "thread"
by SourceForge.net 27 Sep '05

27 Sep '05

Bugs item #1305885, was opened at 2005-09-27 06:54 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=107586&aid=1305885&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: threads Group: None Status: Open Resolution: None Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Mike Glassford (glassfordm) Summary: Exception safety in class "thread" Initial Comment: If an exception is thrown during the copying of the "threadfunc" object in function "thread_proxy", the new thread silently ends and the constructor of class "thread" never returns. Therefore I would suggest to put a copy of "threadfunc" in the "thread_param" object (instead of a reference) and move it to the local variable in function "thread_proxy" via "threadfunc.swap()". In this way a potential exception would be thrown in the constructor of class "thread" and could be handled by the application. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=107586&aid=1305885&group_… ------------------------------------------------------- SF.Net email is sponsored by: Tame your development challenges with Apache's Geronimo App Server. Download it for free - -and be entered to win a 42" plasma tv or your very own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php _______________________________________________ Boost-bugs mailing list Boost-bugs(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/boost-bugs

1 0

Re: [boost] Boost Digest, Vol 1227, Issue 2
by ajb＠spamcop.net 27 Sep '05

27 Sep '05

G'day all. Quoting Paul A Bristow <pbristow(a)hetp.u-net.com>: > I have been exploring the use of Stephen Moshier's Cephes Library in C > (which the author has agreed to make available under the Boost license) > to provide an implmentation of many of these functions, Excellent! I added the list of functions in TR1 to the wiki (SpecialFunctions). Could you (or someone) please go through the list and add anything that's already in Cephes? Then we can take a look at what's left. > AND the other missing, and in many cases MUCH more important IMHO, math > 'special' functions, > mainly requiring the Incomplete beta function, > as I proposed > > http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2004/n1668.pdf > > but which was rejected as 'too difficult' - for which I suspect means 'too > expensive'). Certainly not "too expensive" in terms of computing resources; as I understand it, incomplete beta is no harder to compute than gamma. Perhaps they meant too difficult to get a useful TR out that people would actually be able to implement in reasonable time? Cheers, Andrew Bromage

3 4

Re: [boost] g++4 problems?
by Michael Stevens 27 Sep '05

27 Sep '05

On Monday 26 Sep 2005 Darren Cook <darren(a)dcook.org> wrote: > Has anyone had trouble with complex template code when moving from gcc > 3.4 to gcc 4.0.1? I don't see anything in the release notes that matches > the problem I'm getting, which looks like this (fuller error message > attached below): > > no matching function for call to > boost::smart_assert::Private::smart_assert_alloc<boost::smart_assert::assert_context_func>::destroy(std::pair<const > int, boost::smart_assert::assert_context_func>*) > > candidates are: > void __gnu_cxx::__mt_alloc_base<_Tp>::destroy(_Tp*) > [with _Tp = boost::smart_assert::assert_context_func] Darren, I didn't look in detail at your code. There is however a very significant change in how GCC determines template ambiguity that was introduced between gcc-4.0.0 and gcc-4.0.1 Have a look at http://gcc.gnu.org/bugzilla/show_bug.cgi?id=12536 This changes the handling of template partial ordering to be compatible with C++ standard DR214. I'm not sure that it might not have introduced some other side effects. To determine this I would have to understand what the new text of the standard (with DR214) specifies. And this is not so easy :-) A the moment I have a test case as a candidate for a GCC bug report. // Effect of DR214 FIX (Bug 19203) on 2 simple function template cases template <class E> class expression { }; // ef - deduction of E is via expression template<class E> void ef (expression<E> e); template<class R, class E> void ef (expression<E> e); // sf - deduction of S is simple template<class S> void sf (S s); template<class R, class S> void sf (S s); void test() { expression<int> a; ef (a); // ok ef<char> (a); // ok ef<int> (a); // Ambiguous in 4.0.1 when R == E sf (a); // ok sf<char> (a); // ok sf<int> (a); // unambiguous } I believe there is nothing fundementaly different in deducing the two forms of template parameters 'expression<E>' OR 'S'. All the best, Michael Stevens

1 0

call_traits
by Jason Hise 27 Sep '05

27 Sep '05

Why doesn't the following compile? I get the error "foo: function does not take 1 arguments" on VC8. #include <boost/call_traits.hpp> template < typename P1 > void foo ( typename ::boost::call_traits < P1 >::param_type p1 ) { } int main ( ) { foo ( 42 ); // error here return 0; } (Background info: I would like to use this technique to generate optimized forwarding functions that do not know anything about the function being forwarded to. Overloads taking any number of params would be generated with the boost preprocessor library.) -Jason

3 9

[typeof] can't find test results
by Arkadiy Vertleyb 26 Sep '05

26 Sep '05

Hi All, >From looking at the regression results (HEAD) it seems that a few sites ran the tests on 9/24. However, I don't see the results of some typeof tests I put in a few days ago, on 9/20. What could be a possible reason of this? Regards, Arkadiy

1 1

[signals] Minor patch suggestion for last_value.hpp
by Ames Andreas 26 Sep '05

26 Sep '05

Hello all, I have the problem that signal's default combiner last_value is OOTB only usable with non-empty signals, unless the return type is void. The attached patch tries to circumvent this by returning an optional<T> instead of a T. cheers, aa -- Andreas Ames | Programmer | Comergo GmbH | Voice: +49 69 7505 3213 | andreas . ames AT comergo . com Index: boost/boost/last_value.hpp =================================================================== RCS file: /cc/CVSGlobal/tools/extern/boost/boost/last_value.hpp,v retrieving revision 1.1.1.1 diff -u -r1.1.1.1 last_value.hpp --- last_value.hpp 2005/08/09 03:52:52 1.1.1.1 +++ last_value.hpp 2005/09/26 17:22:32 @@ -12,16 +12,17 @@ #include <cassert> +#include <boost/optional.hpp> + namespace boost { template<typename T> struct last_value { - typedef T result_type; + typedef optional<T> result_type; template<typename InputIterator> - T operator()(InputIterator first, InputIterator last) const + optional<T> operator()(InputIterator first, InputIterator last) const { - assert(first != last); - T value = *first++; + optional<T> value; while (first != last) value = *first++; return value;

1 0

Re: [boost] BOOST_ASSERT and __assume on MSVC
by brangdon＠cix.compulink.co.uk 26 Sep '05

26 Sep '05

In-Reply-To: <200509211851.j8LIp8VY019052(a)shannonhoon.balstatdev.susq.com> stewart(a)sig.com (Rob Stewart) wrote (abridged): > That misses what BOOST_ASSUME should do when > BOOST_DISABLE_ASSERTS is not defined. With BOOST_ASSERT enabled, > BOOST_ASSUME should call both BOOST_ASSERT and __assume(): Why? Consider the sequence: BOOST_ASSERT(e); __assume(e) Suppose (e) is true. Then BOOST_ASSERT does nothing, so why invoke it? If (e) is false, then the __assume tells us the sequence won't be executed at all, and both it and the BOOST_ASSERT can be optimised away. Whatever it is you want BOOST_ASSERT to do, you can't rely on it happening. It will depend on how clever the optimiser is, which will vary from platform to platform. In addition, it evaluates (e) twice. That's bad practice for a macro. It would be acceptable if it were necessary (and we certainly hope (e) has no side effects and that its value doesn't change between the assert and the assume) but here there is no need for it. -- Dave Harris, Nottingham, UK.

2 1

Boost regression notification (2005-09-26 [RC_1_33_0])
by Douglas Gregor 26 Sep '05

26 Sep '05

Boost regression test failures ------------------------------ Report time: 2005-09-26T14:54:08Z This report lists all regression test failures on release platforms. Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-RC_1_33_0/developer/i… 78 failures in 7 libraries: bind (1) foreach (1) graph (5) iostreams (11) random (1) range (3) serialization (56) |bind| bind_cv_test: gcc-4_0-darwin |foreach| rvalue_const: vc-7_1 |graph| betweenness_centrality_test: gcc-3.4.4-linux dag_longest_paths: gcc-3.4.4-linux dijkstra_cc: gcc-3.4.4-linux dijkstra_heap_performance: gcc-3.4.4-linux relaxed_heap_test: gcc-3.4.4-linux |iostreams| gzip_test: cw-9_5-darwin gcc-2.95.3-stlport-4.6.2-linux gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin gcc-4.0.1-linux gcc-4_0-darwin intel-8.1-linux intel-9.0-linux vc-7_1 |random| random_test: gcc-3.3.6-linux |range| array: vc-6_5 vc-6_5-stlport vc-7_0 |serialization| test_contained_class_xml_archive: gcc-3.2.3-linux test_exported_binary_archive: vc-6_5 test_exported_binary_archive_dll: vc-6_5 test_exported_text_archive: vc-6_5 test_exported_text_archive_dll: vc-6_5 test_exported_text_warchive: vc-6_5 test_exported_text_warchive_dll: vc-6_5 test_exported_xml_archive: vc-6_5 test_exported_xml_archive_dll: vc-6_5 test_exported_xml_warchive: vc-6_5 test_exported_xml_warchive_dll: vc-6_5 test_no_rtti_binary_archive: vc-6_5 test_no_rtti_binary_archive_dll: vc-6_5 test_no_rtti_text_archive: vc-6_5 test_no_rtti_text_archive_dll: vc-6_5 test_no_rtti_text_warchive: vc-6_5 test_no_rtti_text_warchive_dll: vc-6_5 test_no_rtti_xml_archive: vc-6_5 test_no_rtti_xml_archive_dll: vc-6_5 test_no_rtti_xml_warchive: vc-6_5 test_no_rtti_xml_warchive_dll: vc-6_5 test_shared_ptr_132_binary_archive: vc-6_5 vc-6_5-stlport test_shared_ptr_132_binary_archive_dll: vc-6_5 test_shared_ptr_132_text_archive: vc-6_5 vc-6_5-stlport test_shared_ptr_132_text_archive_dll: vc-6_5 test_shared_ptr_132_text_warchive: vc-6_5 vc-6_5-stlport test_shared_ptr_132_text_warchive_dll: vc-6_5 test_shared_ptr_132_xml_archive: vc-6_5 vc-6_5-stlport test_shared_ptr_132_xml_archive_dll: vc-6_5 test_shared_ptr_132_xml_warchive: vc-6_5 vc-6_5-stlport test_shared_ptr_132_xml_warchive_dll: vc-6_5 test_shared_ptr_binary_archive: borland-5_6_4 vc-6_5 test_shared_ptr_binary_archive_dll: borland-5_6_4 vc-6_5 test_shared_ptr_text_archive: borland-5_6_4 vc-6_5 test_shared_ptr_text_archive_dll: borland-5_6_4 vc-6_5 test_shared_ptr_text_warchive: borland-5_6_4 vc-6_5 test_shared_ptr_text_warchive_dll: borland-5_6_4 vc-6_5 test_shared_ptr_xml_archive: borland-5_6_4 vc-6_5 test_shared_ptr_xml_archive_dll: borland-5_6_4 vc-6_5 test_shared_ptr_xml_warchive: borland-5_6_4 vc-6_5 test_shared_ptr_xml_warchive_dll: borland-5_6_4 vc-6_5

2 1

Boost regression notification (2005-09-26 [HEAD])
by Douglas Gregor 26 Sep '05

26 Sep '05

Boost regression test failures ------------------------------ Report time: 2005-09-26T05:00:12Z This report lists all regression test failures on release platforms. Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-HEAD/developer/issues… 191 failures in 15 libraries: bind (14) concept_check (14) filesystem (8) foreach (7) graph (4) math (3) mpl (2) parameter (18) python (1) regex (1) serialization (43) spirit (2) thread (24) typeof (46) wave (4) |bind| bind_rv_sp_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin gcc-3_4_3-sunos mingw-3_4_2 mem_fn_rv_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin gcc-3_4_3-sunos mingw-3_4_2 |concept_check| stl_concept_covering: cw-9_4 gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin intel-win32-9_0 intel-win32-9_0 mingw-3_4_2 msvc vc-7_1 vc-7_1 |filesystem| convenience_test: msvc default_name_check_test: msvc fstream_test: msvc large_file_support_test: msvc operations_test: msvc operations_test_dll: msvc path_test: msvc path_test_dll: msvc |foreach| user_defined: cw-8_3 cw-9_4 cw-9_5-darwin msvc vc-6_5 vc-6_5-stlport vc-7_0 |graph| graphviz_test: vc-7_1 vc-7_1 vc-7_1 layout_test: intel-win32-9_0 |math| octonion_test: gcc-4_0-darwin quaternion_test: gcc-4_0-darwin special_functions_test: gcc-4_0-darwin |mpl| size_t: gcc-4_0-darwin gcc-4_0-darwin |parameter| basics: borland-5_6_4 gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux efficiency: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-4_0-darwin msvc macros: borland-5_6_4 gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux sfinae: borland-5_6_4 gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux msvc unnamed: borland-5_6_4 gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux vc-7_1 |python| data_members: msvc |regex| static_mutex_test: msvc |serialization| test_class_info_load_binary_archive: cw-9_5-darwin gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_binary_archive_dll: cw-9_5-darwin gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_archive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_archive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_warchive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_warchive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_archive: cw-9_5-darwin gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_archive_dll: cw-9_5-darwin gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_warchive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_warchive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_const_save_fail1: msvc test_const_save_fail2: msvc test_const_save_fail3: msvc test_map_binary_archive_dll: msvc test_map_text_archive_dll: msvc test_map_text_warchive_dll: msvc test_no_rtti_text_archive: vc-7_1 test_no_rtti_text_warchive: vc-7_1 test_non_intrusive_xml_warchive_dll: vc-7_1 |spirit| traverse_tests: intel-win32-9_0 traverse_tests_debug: intel-win32-9_0 |thread| test_barrier: msvc test_barrier_lib: intel-9.0-linux msvc test_condition: msvc test_condition_lib: intel-9.0-linux msvc test_mutex: msvc test_mutex_lib: intel-9.0-linux msvc test_once: msvc test_once_lib: intel-9.0-linux msvc test_read_write_mutex: msvc test_read_write_mutex_lib: intel-9.0-linux msvc test_thread: msvc test_thread_lib: intel-9.0-linux msvc test_tss: msvc test_tss_lib: intel-9.0-linux msvc test_xtime: msvc test_xtime_lib: intel-9.0-linux msvc |typeof| data_member_emulation: cw-9_4 data_member_native: intel-win32-9_0 intel-win32-9_0 function_emulation: cw-9_4 function_native: intel-win32-9_0 intel-win32-9_0 msvc function_ptr_emulation: cw-9_4 function_ptr_native: intel-win32-9_0 intel-win32-9_0 function_ref_emulation: cw-9_4 function_ref_native: intel-win32-9_0 intel-win32-9_0 lvalue_emulation: cw-9_4 lvalue_native: intel-win32-9_0 intel-win32-9_0 msvc member_function_emulation: cw-9_4 member_function_native: intel-win32-9_0 intel-win32-9_0 modifiers_emulation: cw-9_4 modifiers_native: cw-9_4 intel-win32-9_0 intel-win32-9_0 noncopyable_native: intel-win32-9_0 std_native: intel-win32-9_0 template_dependent_native: intel-win32-9_0 template_enum_native: intel-win32-9_0 template_int_emulation: cw-9_4 template_int_native: intel-win32-9_0 intel-win32-9_0 template_multiword_native: intel-win32-9_0 template_tpl_emulation: cw-9_4 template_tpl_native: intel-win32-9_0 intel-win32-9_0 msvc template_type_emulation: cw-9_4 template_type_native: intel-win32-9_0 intel-win32-9_0 type_emulation: cw-8_3 cw-9_4 cw-9_4 type_native: intel-win32-8_1 intel-win32-9_0 intel-win32-9_0 intel-win32-9_0 |wave| test_re2c_lexer: intel-9.0-linux test_slex_lexer: intel-9.0-linux testwave: gcc-3.3.6-linux intel-9.0-linux

1 0

[config] Borland's standard library bug
by Robert Kawulak 26 Sep '05

26 Sep '05

Hi, I've discovered a bug of Borland's compiler (version 5.6.4 for Win32) standard library implementation - the errno is not a macro (as it should be according to The Standard - 17.4.1.2. p. 5), furthermore it's only in the std namespace (17.4.1.2. p. 4). Because of the second problem I'd suggest to add using std::errno line to the boost/config/compiler/borland.hpp file to make errno global as it should be, or maybe a macro BOOST_ERRNO which would evaluate to std::errno for Borland and just errno for other implementations. Am I right and how to do this/who's responsible for that? Thanks and best regards, Robert ---------------------------------------------------------------------- Jestem niesamowita... ;-) >>> http://link.interia.pl/f18b8

2 1

Re: [boost] [math] Proposed TR1 additions
by ajb＠spamcop.net 26 Sep '05

26 Sep '05

G'day all. John Maddock wrote: > Those of a mathematical inclination, might be interested to note that the > only substantive code in the TR1 submission currently under review is some > proposed additions to Boost.Math: mainly the inverse complex number trig > functions. Sorry, I haven't been keeping up with this. Do I read it as meaning that [tr.num.sf] is not present in the current submission? Cheers, Andrew Bromage

3 2

g++4 problems?
by Darren Cook 26 Sep '05

26 Sep '05

Has anyone had trouble with complex template code when moving from gcc 3.4 to gcc 4.0.1? I don't see anything in the release notes that matches the problem I'm getting, which looks like this (fuller error message attached below): no matching function for call to boost::smart_assert::Private::smart_assert_alloc<boost::smart_assert::assert_context_func>::destroy(std::pair<const int, boost::smart_assert::assert_context_func>*) candidates are: void __gnu_cxx::__mt_alloc_base<_Tp>::destroy(_Tp*) [with _Tp = boost::smart_assert::assert_context_func] (despite the namespace this is not an official boost library, but I hope this does not count as too off-topic) Darren g++ -Wall -Werror -g3 -DBOOST_SMART_ASSERT_MODE=1 -DBWIDTH=9 -DBHEIGHT=9 -Wno-reorder -c -o test_main.9.o test_main.cpp /usr/lib/gcc/i386-redhat-linux/4.0.1/../../../../include/c++/4.0.1/bits/stl_tree.h: In member function 'void std::_Rb_tree<_Key, _Val, _KeyOfValue, _Compare, _Alloc>::destroy_node(std::_Rb_tree_node<_Val>*) [with _Key = int, _Val = std::pair<const int, boost::smart_assert::assert_context_func>, _KeyOfValue = std::_Select1st<std::pair<const int, boost::smart_assert::assert_context_func> >, _Compare = std::less<int>, _Alloc = boost::smart_assert::Private::smart_assert_alloc<boost::smart_assert::assert_context_func>]': /usr/lib/gcc/i386-redhat-linux/4.0.1/../../../../include/c++/4.0.1/bits/stl_tree.h:1096: instantiated from 'void std::_Rb_tree<_Key, _Val, _KeyOfValue, _Compare, _Alloc>::_M_erase(std::_Rb_tree_node<_Val>*) [with _Key = int, _Val = std::pair<const int, boost::smart_assert::assert_context_func>, _KeyOfValue = std::_Select1st<std::pair<const int, boost::smart_assert::assert_context_func> >, _Compare = std::less<int>, _Alloc = boost::smart_assert::Private::smart_assert_alloc<boost::smart_assert::assert_context_func>]' /usr/lib/gcc/i386-redhat-linux/4.0.1/../../../../include/c++/4.0.1/bits/stl_tree.h:570: instantiated from 'std::_Rb_tree<_Key, _Val, _KeyOfValue, _Compare, _Alloc>::~_Rb_tree() [with _Key = int, _Val = std::pair<const int, boost::smart_assert::assert_context_func>, _KeyOfValue = std::_Select1st<std::pair<const int, boost::smart_assert::assert_context_func> >, _Compare = std::less<int>, _Alloc = boost::smart_assert::Private::smart_assert_alloc<boost::smart_assert::assert_context_func>]' /usr/lib/gcc/i386-redhat-linux/4.0.1/../../../../include/c++/4.0.1/bits/stl_map.h:92: instantiated from here /usr/lib/gcc/i386-redhat-linux/4.0.1/../../../../include/c++/4.0.1/bits/stl_tree.h:389: error: no matching function for call to 'boost::smart_assert::Private::smart_assert_alloc<boost::smart_assert::assert_context_func>::destroy(std::pair<const int, boost::smart_assert::assert_context_func>*)' /usr/lib/gcc/i386-redhat-linux/4.0.1/../../../../include/c++/4.0.1/ext/mt_allocator.h:614: note: candidates are: void __gnu_cxx::__mt_alloc_base<_Tp>::destroy(_Tp*) [with _Tp = boost::smart_assert::assert_context_func] ... (then more of the same) ...

1 1

thread yield
by Jason Hise 26 Sep '05

26 Sep '05

Can the yield function of boost::thread be used to immediately wake up a thread that is sleeping? I would like to use this to make sure that certain threads get the chance to exit before the process terminates, without join resulting in the whole program sleeping. -Jason

5 14