- Boost - lists.preview.boost.org

[GTL] redesign checked into sandbox
by Simonson, Lucanus J 14 May '08

14 May '08

I checked a gtl project into the sandbox so that I can keep postings to the list more brief while allowing people to see the up to date and correctly compiling state of the re-design and re-implementation of the library interfaces. The main header file is gtl.h, which includes the others and defines free functions that may rely on any of the geometry concepts when instantiating the template function. A recent change is to the design is that rather than using SFINAE to overload a free function on return type I now call a meta-function that looks up from the related concept and provides the correct return type based upon the args given (see get() in gtl.h). This eliminates the need to register the return type in a specialized traits class since the concept can provide it for the given type generically. Log: initial checkin Added: sandbox/gtl/ sandbox/gtl/boost/ sandbox/gtl/gtl/ sandbox/gtl/gtl/geometry_traits.h (contents, props changed) sandbox/gtl/gtl/gtl.h (contents, props changed) sandbox/gtl/gtl/interval_concept.h (contents, props changed) sandbox/gtl/gtl/interval_data.h (contents, props changed) sandbox/gtl/gtl/interval_traits.h (contents, props changed) sandbox/gtl/gtl/isotropy.h (contents, props changed) sandbox/gtl/gtl/point_3d_concept.h (contents, props changed) sandbox/gtl/gtl/point_3d_data.h (contents, props changed) sandbox/gtl/gtl/point_3d_traits.h (contents, props changed) sandbox/gtl/gtl/point_concept.h (contents, props changed) sandbox/gtl/gtl/point_data.h (contents, props changed) sandbox/gtl/gtl/point_traits.h (contents, props changed) sandbox/gtl/gtl/polygon_concept.h (contents, props changed) sandbox/gtl/gtl/polygon_data.h (contents, props changed) sandbox/gtl/gtl/polygon_traits.h (contents, props changed) sandbox/gtl/gtl/post_concept_definitions.h (contents, props changed) sandbox/gtl/gtl/post_geometry_traits_definitions.h (contents, props changed) sandbox/gtl/gtl/rectangle_concept.h (contents, props changed) sandbox/gtl/gtl/rectangle_data.h (contents, props changed) sandbox/gtl/gtl/rectangle_traits.h (contents, props changed) The code in the sandbox is intended to conform to boost standards. Feel free to point out instances where I may have failed to do so. Thanks, Luke

5 33

[Boost][ProgramOptions] Interest in a CGI parameters parser?
by Bruno Lalande 14 May '08

14 May '08

Hello, Yesterday I had to write a program that compiles 2 forms of executables: a standalone version that takes its parameters from the command line, and another one that serves as a CGI program and thus takes exactly the same parameters but from stdin (POST method). I naturally chose Boost.ProgramOptions for the first one, and did the job by myself for the second one. I finally realized that I was doing fundamentally the same thing as what a ProgramOptions parser basically does: parsing a name=value series of variables, checking unknown values, assign them to variables, etc... plus a few formatting work to handle URL format specificities. So in the end I was wondering if a "cgi_query_parser" would be appreciated as an addition to the parsers already present in Boost.ProgramOptions? I can directly see the benefits inside my own program since the 2 versions would only differ on one line of code. >From a more general point of view, it could be a simple way to have a CGI support somewhere in Boost. If such a thing can be interesting, I can take a few time to implement it. Regards Bruno

7 16

Re: [boost] [endian] Request formal review
by Neil Mayhew 14 May '08

14 May '08

On 2006-06-22 at 13:35:36, Beman Dawes wrote: > There is an update to my endian proposal available at ... > > The docs can be read online at ... > > This update: > > * Reflects all comments received to date. > * Makes the proposal part of the Boost integer library. > * Docs have been updated and expanded. > * Native endianness has be implemented. > > The proposal is mostly done at this point and is essentially ready for > a formal review. Did anything ever come of this? I've been searching through all the list postings on this, dating back to 2000, and it doesn't look like this library ever made it into boost proper. It's exactly what I've been looking for, and I would really like to use it in my work, but I can't justify that if it's not an official part of boost. I also would hate to reinvent this particular wheel. Please could someone get this moving again? Also, where would I now find the version of this code that was put up for review? The links in the original message are no longer current. --Neil

1 1

svnmerge spews all over trac...
by Rene Rivera 13 May '08

13 May '08

Having an svnmerge command like in this case <http://svn.boost.org/trac/boost/changeset/45029> spew commentary all over existing trac items like this one <http://svn.boost.org/trac/boost/ticket/1889>, just seems like a really bad thing. Is this yet another reason not to use svnmerge? Or is it operator (not to pick on Eric) error that can be averted in the future? Or could it be the trac comment plugin causing this, and svnmerge is blameless? -- -- Grafik - Don't Assume Anything -- Redshift Software, Inc. - http://redshift-software.com -- rrivera/acm.org (msn) - grafik/redshift-software.com -- 102708583/icq - grafikrobot/aim,yahoo,skype,efnet,gmail

5 8

[asio] question on boost::asio::ssl::stream::async_shutdown expected behaviour
by Carlo Medas 13 May '08

13 May '08

Hi guys, I've question on behaviour of boost::asio::ssl::stream::async_shutdown I would expect that this should behave as any other async method of ASIO: both in case of succeed or error it should call my handler on completion. At some point in my code I call: > m_sslSocket.async_shutdown(boost::bind(&TestClient::handle_sslshutdown, this, boost::asio::placeholders::error)); > void TestClient::handle_sslshutdown(const boost::system::error_code& error) > { > std::cout << "SSL shutdown completed with error <"<<error.message()<<">\n"; > socket_.lowest_layer().close(); > std::cout << "Lower TCP layer closed\n"; > } But it's never called on successful shutdown, it's called only if the other peer previously yet closed the connection, thus resulting in an error. So my handler is called with relative error code; in positive case, my handler is never called. What am I missing? Something here in client code or something in the server code? Thanks in advance and best regards, Carlo Medas

2 3

Trac open bugs - by assignee
by Marshall Clow 13 May '08

13 May '08

[ 308 open bugs today, 302 last Tuesday ] If you are maintaining a library, and have not logged into the trac system at <http://svn.boost.org/trac/boost/>, please do so ASAP. Until you do that, no tickets can be assigned to you, and will remain under "None". Instructions on working with tickets can be found at: <http://svn.boost.org/trac/boost/wiki/TicketWorkflow> and a mapping of user names to "real names" can be found at: <http://svn.boost.org/trac/boost/report/16> Bug summary 33 djowel 26 az_sw_dude 24 dgregor 22 grafik 19 dave 18 vladimir_prus 16 bemandawes 12 ramey 12 no-maintainer 11 turkanis 11 jsiek 11 anthonyw 11 agurtovoy 9 rogeeff 9 nesotto 5 igaztanaga 5 danieljames 4 witt 4 pavol_droba 4 kaalus 4 johnmaddock 4 ebf 4 None 3 samuel_krempp 3 nasonov 2 troyer 2 shammah 2 marshall 2 jmaurer 2 hkaiser 2 garcia 2 danielw 1 urzuga 1 t_schwinger 1 speedsnail 1 matias 1 jano_gaspar 1 gmelquio 1 fcacciola 1 dlwalker 1 aaron_windsor 1 <Blank> <Blank> 1750 Autolink library name not in sync with actually build lib None 1736 Headers containing non ASCII characters cause MS VC to issue warning 4819 in some locales None 1900 Missing documentation for mpl::print in the MPL library None 1901 Missing documentation for mpl::for_each in the MPL library None 1907 name of library files on mingw aaron_windsor 1622 Adjacency list needs to handle self-edges correctly agurtovoy 1001 gcc 4.1.2 segfaults on mpl/test/apply.cpp agurtovoy 1051 MPL header ordering triggers bug agurtovoy 1099 unable to iterate through a "non-explicitly-declared" mpl::set agurtovoy 1215 Boost 1.34.1_ mpl: Wrong workaround detection using MinGW32 (or.hpp_ line #33) agurtovoy 1317 has_xxx randomly broken in msvc agurtovoy 1469 [mpl] nested typedef of set has two different meanings agurtovoy 1476 always<> is not nullary. agurtovoy 1528 g++ 4.3.0 reports error because of redeclaration of next agurtovoy 1549 Boost.MPL: 'index_of' algorithm is not documented agurtovoy 1568 duplicate include guards agurtovoy 588 mpl::remove compile error with gcc 4.1.0 anthonyw 1154 tss destruction segfaults in conjunction with dlopen/dlclose anthonyw 1168 [thread] tss crashes randomly anthonyw 1268 xtime_cmp changes to deal with overflow were reverted anthonyw 1470 Boost.Thread: Compilation errors with non-__cdecl calling convention anthonyw 1805 thread creation crashes with /Zp1 switch in VS2005 compiler anthonyw 1813 Signed/Unsigned warning in win32/condition_variable anthonyw 1825 thread.hpp injects windows.h and breaks user application. anthonyw 1826 Auto detection of threadapi and target-os broken under cygwin gcc anthonyw 1867 Missing member functions in shared_mutex (win32) anthonyw 876 xtime documentation incomplete anthonyw 881 errors when build with Apache stdcxx az_sw_dude 1028 typo in boost header: date_time/time_defs.hpp az_sw_dude 1078 from_iso_string cannot read the output from to_iso_string az_sw_dude 1098 Urgent libboost-date-time1.33.1 : bugs on ia64 ? az_sw_dude 1147 date_time library contains global #define ERROR az_sw_dude 1160 warning: month_format shadows a member of this az_sw_dude 1162 warning: ticks shadows a member of this az_sw_dude 1289 posix_time::time_facet forgets to pass a_ref argument to base class az_sw_dude 1299 change in typedef stringstream_type in format_date_parser.hpp causing compilation error az_sw_dude 1306 invalid docbook in date_period.xml az_sw_dude 1384 Linking problem with date_time library on Visual C++ 2008 Express az_sw_dude 1524 format_date_parser.hpp(221) : cannot convert parameter 1 az_sw_dude 1574 operator<< for boost::posix_time::ptime ignores ostream flags az_sw_dude 1674 date_time::date_formatting.hpp: incorrectly formats year using global locale az_sw_dude 1695 add correct namespace to class to fix compilation bug az_sw_dude 1726 boost/date_time/posix_time/time_formatters.hpp incorrectly formats fractional seconds using global locale az_sw_dude 1740 date_time includes <windows.h> az_sw_dude 1788 local_time::local_time_period streaming operators not implemented az_sw_dude 1859 boost::gregorian::to_tm() doesn't fill in tm_zone on Mac OS X az_sw_dude 1878 Documention Corrections - Various date_time Pages az_sw_dude 1903 [date_time] - 1.34+ c_local_adjustor derefs null pointer for dates >2038 az_sw_dude 287 wrong usage of ios_base::narrow az_sw_dude 316 date_time type conversion warning az_sw_dude 604 from_ftime incorrectly processes FILETIME filled with zeros az_sw_dude 642 operator<< for gregorian::date_duration not found az_sw_dude 889 Insane Dependencies az_sw_dude 890 date_time library supports only the current dst rule bemandawes 1378 filesystem path invalid name for hidden files (LINUX) bemandawes 1389 filesystem::ostream << boost::format generates operator ambigious error (in MSVC++) bemandawes 1458 Darwin Tiger throws std::runtime_error: locale::facet::_S_create_c_locale name not valid bemandawes 1578 bug in readdir_r_simulator() in a multi-threaded environment bemandawes 1583 Serious flaw in boost::filesystem filename handling (opensuse) bemandawes 1589 [filesystem] 'mbstate_t' : is not a member of 'std' bemandawes 1606 filesystem/src/exception.cpp doesn't build with gcc bemandawes 1613 Link Errors against file_system on OS X with Intel Version 10.1 C++ compilers bemandawes 1682 path_traits needs imbue() bemandawes 1701 boost::filesystem::remove_all - segmentation fault with wpath on Linux bemandawes 1711 Boost Serialization export facility broken on gcc 4.1_ 4.2 bemandawes 1767 missing file: boost/filesystem/cerrno.hpp bemandawes 1768 system: error_code.cpp #defines macros without checking whether already defined bemandawes 1840 name check functions have different behavior wrt empty string bemandawes 1876 portable_file_name() returns true for '.' and '..' bemandawes 752 directory_iterator doesn't work with catch danieljames 1554 When BOOST_HASH_NO_EXTENSIONS is defined hash doesn't support new string types. danieljames 1555 When BOOST_HASH_NO_EXTENSIONS is defined hash doesn't support boost::system::error_code danieljames 1742 Some bugs in http://www.boost.org/doc/libs/1_35_0 danieljames 1743 Documentation has incorrect Build & Link settings for some libraries danieljames 1818 The tables in status reports jump all over the place. danielw 1054 Parameter takes an "infinite" amount of time to compile with the Intel compiler. danielw 1097 keyword.hpp generates many warnings C4180: qualifier applied to function type has no meaning; ignored dave 1010 linking boost.python on freebsd dave 1019 iterator_facade::pointer should be the return type of operator-> (DR 445) dave 1085 Python rules for compiling in Mac OS X dave 1179 [boost.python] can not export a union in VC2005sp1 dave 1181 [boost.python] can modify enum value dave 1387 Review / update docs to reflect changes dave 1460 Python classes with multiple bases are convertible only to the first class in the lists dave 1482 boost::python::throw_error_already_set should be marked noreturn dave 1516 [python] Failing VC9 regression tests dave 1599 [python] '_set_se_translator': identifier not found dave 1697 [utility][noncopyable] ADL barrier broken by msvc-9.0 dave 1730 No debug libs on Windows by default dave 1744 [getting started] No information on building static libraries with bjam under Windows dave 1851 Issue with proxies and rvalues dave 1860 zip_iterator::value_type should not be reference dave 1887 [doc] input_iterator_archetype is not a valid InputIterator dave 1890 Missing parameters in example code dave 865 Use of C++0x keyword as identifier dave 910 gcc strict-aliasing problems with python dgregor 1009 Improper overflow handling in shortest paths algorithms dgregor 1021 [Graph][reverse_graph] Problem using reverse_graph adapter with an adapted user defined graph dgregor 1076 compile error: disconnecting struct with operator()() doesn't work in VS2005 SP1 dgregor 1164 Floyd Warshall broken with unsigned edge weights dgregor 1192 [boostbook] problem when two files have the same name dgregor 1199 configure doesn't work with path containing whitespaces (MacOS X) dgregor 1310 [result_of] const-qualified function pointer doesn't work dgregor 1326 Unable to check graph isomorphism using LEDA adapter dgregor 1391 dominator_tree_test on Borland/CodeGear outputs overly long line dgregor 1630 gcc-4.3: adjacency_list.hpp includes deprecated header dgregor 1910 function::swap should avoid doing memory allocations dgregor 375 LEDA graph adaptors do not handle hidden nodes properly dgregor 402 random_vertex/random_edge are unnecessarily inefficient dgregor 403 Document copy_component dgregor 447 reverse_graph and constness of property maps dgregor 556 Bundled graph properties dgregor 708 Dijkstra no_init version should not require VertexListGraph dgregor 732 Johnson All-Pairs needs better "no path" information dgregor 733 Numbered headers don't work with "preferred" syntax dgregor 735 Fruchterman-Reingold grid performance can be improved dgregor 736 Const correctness violation dgregor 738 Memory leaks with signal::connect? dgregor 829 Implicit graph not implement dgregor 852 Problem with Boost and GCC 4.1 djowel 1170 Emit Warnings instead of # symbols in the syntax highlighter djowel 1171 Quickbook title output djowel 1172 non-utf djowel 1176 Space after inline code djowel 1206 Escaping from within code? djowel 1273 CR+LF newlines in position_iterator djowel 1276 spirit problem with _GLIBCXX_DEBUG djowel 1277 Closing section like [pre with } causes Quickbok to crash djowel 1280 sections in imported source files get put inside <para> elements in docbook output djowel 1281 Quickbook produces invalid BoostBook/DocBook XML djowel 1324 tuple should have a swap() that operates element-by-element djowel 1396 wrong result_of invocation around transform_view djowel 1436 [quickbook] inline code inside headings djowel 1484 Quickbook produces illegal docbook for some docinfo fields. djowel 1500 [Spirit/Phoenix] C4512 Compiler warnings from VC8 djowel 1570 Some boost headers aren't ready for gcc 4.3 djowel 1600 duplicate include guard djowel 1601 distane of boost::tuple djowel 1607 Tuple Library Documentation Changes djowel 1610 [MSVC/STLport] [tree/common.hpp] Standard library requirements violation(incomplete type as vector parameter) djowel 1614 vector workaround needed for MSVC9 djowel 1617 spirit gcc-4.3 fix djowel 1619 [Fusion] C4512 warnings from VC9 (Visual Studio 2008) djowel 1651 incorrect typedefs in examples djowel 1763 wrong AST when parser_tag==0 djowel 1764 wrong AST when parser_tag==0 djowel 1844 Quickbook matches forward slashes (for italics) with slashes in links djowel 1864 [Documentation]There is no documentation for repetivive_view djowel 1872 [Spirit2] 'assignment operator could not be generated' warnings from VC9 djowel 1891 quickbook executable receives <dependency> djowel 1892 boost::spirit::static_ causes link error (using wave) djowel 1893 Documentation Corrections to map.html djowel 1894 fusion\support\tag_of.hpp_ boost::fusion::traits dlwalker 613 boost/crc.hpp uses non-standard conforming syntax ebf 1507 [variant] C4512 warnings from VC8.0 ebf 1548 [variant][docs]typo: formal arg_ operand_ should be v in times_two arglist ebf 1654 recursive variants do not handle nested variants correctly. ebf 993 Variant should use least common multiple of alignments_ rather than maximum fcacciola 1666 Visualizer for boost::optional garcia 1581 Boost.MultiArray: Resizing bug if the index is not 0-based garcia 1741 Review schedule out of date gmelquio 1886 Typo in Interval documentation grafik 1041 Cygwin requires PATH setting. grafik 1322 trac rejects patch attachment as spam grafik 1406 Understanding the Tables outdated grafik 1417 Regresson tests hang in Darwin (Tiger) grafik 1430 Regression fails under Cygwin grafik 1433 Trac's spam detection rejects too many valid messages grafik 1512 Broken link to vacpp in bjam docs. grafik 1513 Broken link to bcpp in bjam docs. grafik 1576 cannot read non-ASCII output messages grafik 1577 Some commands don't work because hStdInput == 0 grafik 1663 build.bat cannot set/reset ERRORLEVEL grafik 1733 Website layout overlays on IE7 grafik 1735 [website] Wrong HTML on main documentation page. grafik 1738 Boost Jam details and download link grafik 1739 Search box and Google link grafik 1753 Python docs: bad link to the Jamroot grafik 1771 Statechart TOC mangled. grafik 1776 Documentation page renders incorrectly in Safari 3.1 on OS X grafik 1906 Trac site too hard to find grafik 616 Boost Jam_ and non english directorys grafik 959 linking fails when Boost is compiled with STLport 5.1.* on Linux (names mismatch) grafik 986 Problem building Python modules on boost 1.34.0 hkaiser 1079 boost-1.34.0 fails to compile. concept checks not satisfied. hkaiser 1670 wave almost unusably slow on real-world input igaztanaga 1080 boost::interprocess win32 global file mapping issue igaztanaga 1210 interprocess::barrier hangs during second use under linux (boost 1.33.1) igaztanaga 1390 Interpocess: managed shared memory failing completely under OS X igaztanaga 1634 boost::interprocess::vector cannot contain volatile int igaztanaga 1635 Incomplete include guard in boost/intrusive jano_gaspar 1852 copy constructor does not copy capacity jmaurer 351 Diff in state of mersenne_twister gen between GCC3.41 & CW9 jmaurer 599 uniform_01 copies engine instead of using a reference johnmaddock 1081 Empty string rejected as perl-style regex johnmaddock 1446 POSIX API doesn't use C locale johnmaddock 1451 error: use of C99 long long integer constant johnmaddock 1863 Boost.Regex unstable with Borland Turbo C++ 2006 jsiek 1531 segfault in dynamic_bitset::reference assign operator jsiek 1540 Poisson distribution very slow for large mean (and may also overflow). jsiek 1755 Boost.tokenizer is broken for wide characters - patch attached jsiek 1798 met an error using boost::tokenizer in multi-times in vs2005_ unicode jsiek 1888 Why doesn't InputIterator require that reference is convertible to value_type? jsiek 1909 Documentation is out of sync jsiek 575 Calling subgraph::global_to_local on a root graph jsiek 636 strange compiling problem for transitive_closure jsiek 815 remove_edge core dumps on self-circle jsiek 875 No iterator based constructor for adjacency_matrix jsiek 900 graphml reader namespace handling is broken kaalus 1184 property_tree assignment (operator) bug kaalus 1604 property_tree xml parser doesn't compile with gcc kaalus 1678 Boost.property_tree::read_xml does not parse UNICODE file with BOMs kaalus 1914 Boost.PropertyTree JSON parser in SVN trunk does not compile with Spirit2 changes marshall 1252 [pool] severe overhead with unaligned sizes. marshall 1854 Interval is not available as a component in the SVN system matias 1822 header dependency in boost/serialization/map.hpp nasonov 1220 lexical_cast requires RTTI nasonov 1847 Can't compile without <locale> header_ boost::lexical_cast problem nasonov 754 boost::any - typeid comparison across shared boundaries nesotto 1629 range/iterator_range.hpp bug nesotto 1675 [range] VC8 - compiler warnings when including range/array headers nesotto 1694 NDEBUG vs. BOOST_ASSERT in iterator_range.hpp nesotto 1748 [ptr_container] compiler warnings from VC9 nesotto 1754 Illegal HTML in range docs. nesotto 1785 assign::list_of works poorly with class constructors nesotto 1795 [ptr_container] minor documentation typo nesotto 1842 boost::sub_rage::front error nesotto 1908 boost::size(std::set<T> const& s) causes compile errors with msvc no-maintainer 1068 Mersenne twister disables streaming for Visual C++ no-maintainer 1222 lambda::ret<T> should declare result_type. no-maintainer 1270 uniform_smallint doesn't compile with lagged_fibonacci random number generators no-maintainer 1515 [lambda] C4512 warnings from VC8.0 no-maintainer 1544 uniform_01 w/ref template param causes ref to ref error no-maintainer 1546 Method boost::random::uniform_int::operator()(engine_ value) is missing no-maintainer 1572 [lambda] smart pointer const-ness affects its contents no-maintainer 1632 Default Interval rounding policies incomplete no-maintainer 1691 [Random] Brokem MSVC workaround no-maintainer 1856 minstd_rand returning different values in 1.35.0 than in 1.34.1 no-maintainer 781 Lambda: (_1 + "y")(string("x")) Doesn't Compile no-maintainer 819 uniform_int<> with type's maximum availaible range error pavol_droba 1152 rle_example fails pavol_droba 1385 begin must be boost-qualified pavol_droba 1761 StringAlgo: Error in an example pavol_droba 1827 String algorithm composite header doesn't include join ramey 1708 Can't serialize class with private destructor ramey 1734 BOOST_STATIC_WARNING can't be passed a dependent expression ramey 1747 [serialization] unreferenced formal parameter warnings from VC9 ramey 1807 boost::archive::xml_archive_exception does not store error code and reports wrong message text ramey 1812 Boost.Serialization fails to build on Cygwin ramey 1823 Archive concept: Incomplete description? ramey 1824 serialization keeps using wchar_t if BOOST_NO_STD_WSTRING is set ramey 1836 bug in serializing wide character strings ramey 1837 Base class missed in binary_wiarchive ramey 1849 Deserialization of std::string overwrites non-copied contents. ramey 1857 IA64_ GCC 4.3_ redefinition of 'struct boost::serialization::implementation_level<std::vector<long int_ std::allocator<long int> > >' ramey 1877 Documentation Corrections - Archive Concepts rogeeff 1383 signal.h features not found on Mac OS rogeeff 1542 [test] compiler errors when building with stdcxx library rogeeff 1644 Boost.Test missing documentation file BOOST_CHECK_CLOSE_FRACTION.html rogeeff 1676 Dead links on Boost.Test example documentation. rogeeff 1723 No subprocess can be started in init_unit_test_suite rogeeff 1746 Online documentation for 1.35.0 is out of date for current lib version rogeeff 1839 Test fails if child process exits with non-zero code rogeeff 1866 Typos in Boost Test documentation rogeeff 1869 Typo in Unit Test Framework documentation samuel_krempp 1699 Compile warning about initialization order. samuel_krempp 1801 Typo in documentation. samuel_krempp 859 boost::format ignores a user defined locale shammah 290 perfomance: memory cleanup for pool takes too long shammah 386 boost::pool_allocator breaks with vector of vectors speedsnail 1138 Problems with TSS and static thread library t_schwinger 1653 wave executable erroneously required for build of function_types lib troyer 1774 serialization: file written with 1.34.1 can't be read in with 1.35 troyer 1778 Possible regression in 1.35 serialization of 2D arrays turkanis 1523 [iostreams] VC8/VC9 compiler warnings turkanis 1545 [boost/rational.hpp] 'noskipws' is not a member of 'std' turkanis 1579 gzip compressor should model DualUseFilter turkanis 1580 Add static assert to prohibit instantiating a chain with mode dual_use turkanis 1649 Fix definition of JavaScript menu to avoid long chains of functions turkanis 1656 Consider implementing flush() for symmetric filters turkanis 1671 type mismatch of buffer size parameter causes overload resolution to fail turkanis 1727 Sample code in documentation does not compile_ has namespace errors. turkanis 1870 zlib_base function names must differ from their zlib counterpart turkanis 1875 Boost.Iostreams warnings with GCC -Wall -W -std=c++98 -pedantic turkanis 1896 boost::iostreams::gzip_decompressor silently ignores multiple members urzuga 574 [boost::lambda] Compile error with libstdc++ debug mode vladimir_prus 1132 program_options documentation error. vladimir_prus 1165 more quoting problems vladimir_prus 1274 Useless error message vladimir_prus 1527 [program_options] Second (and subsequent) lines in tabbed text not aligned correctly vladimir_prus 1530 Program options documentation - Overview - Syntactic Information example typo vladimir_prus 1537 no value given in 'mysql_password =' vladimir_prus 1584 cryptic bbv2 error building quickbook vladimir_prus 1587 [program_options] crashes if value part missing in external configuration file vladimir_prus 1588 [program_options] crashes if value part missing in external configuration file vladimir_prus 1645 Invalid unicode support for default_value vladimir_prus 1679 added 4-way universal binary support from mac osx (ppc_ ppc64_ i386_ x86_64) vladimir_prus 1809 Allow empty values in conf file vladimir_prus 1880 documentation bug vladimir_prus 1904 undefined reference to `boost::program_options::options_description::m_default_line_length' vladimir_prus 1911 scanner.jam needs to import module errors vladimir_prus 469 multitoken broken vladimir_prus 689 [program_options] Endless loop with long default arguments vladimir_prus 850 program_options strips off escaped quotes in some situations witt 583 Fixes for build on IBM pSeries for AIX and Linux witt 834 Homepage regression links witt 957 The "Getting Started" page does not mention the stdlib option witt 973 zip_iterator has value_type == reference -- -- Marshall Marshall Clow Qualcomm, Inc. <mailto:mclow@qualcomm.com> The famous British scientist, Lord Kelvin, said: "When you measure what you are speaking about and express it in numbers, you know something about it, but when you cannot (or do not) measure it, when you cannot (or do not) express it in numbers, then your knowledge is of a meagre and unsatisfactory kind."

1 0

Boost.Test SIGCHLD catching causes tests to fail
by Kevin Harris 13 May '08

13 May '08

I'm trying to update my project to use boost 1.35. There is behavior in the test library to catch SIGCHLD and consider it an error. Is there a reason for this? I have cases where my tests really do need to execute something (to test some execution code). For our purposes, the default behavior of SIGCHLD is correct, and reporting it as an error is wrong. The other signals (SIGILL, SIGFPE, SIGSEGV, SIGBUS, etc.) are all good to catch, as they usually indicate a real error. Is there some way to configure this separately from the rest of the errors properly detected and reported by BOOST_TEST_CATCH_SYSTEM_ERRORS=yes? Here's some output: Platform: linux Compiler: GNU C++ version 4.1.3 20070929 (prerelease) (Ubuntu 4.1.2-16ubuntu2) STL : GNU libstdc++ version 20070929 Boost : 1.35.0 unknown location(0): fatal error in "test_real_execute": child has exited; pid: 1000; uid: 22286; exit value: 0 test_execute.cpp(106): last checkpoint Note that in that output the PID and UID are backwards. I couldn't find any way to configure this separately, so for my own use I'm just going to put a few #ifdefs around the SIGCHLD code (like the SIGPOLL handling) in boost/test/impl/execution_monitor.ipp unless someone has a better idea. Thanks. -Kevin-

3 2

[Pool] Arbitrary sized elements?
by Phil Bouchard 13 May '08

13 May '08

Greetings: I was wondering if they were any intent to add a derivative of Boost.Pool which will handle types of arbitrary sizes. It won't benefit from speed optimization but certainly from its members functions such as is_from(), obliteration properties and independent memory area. This is basically were shifted_ptr is heading to because allocated blocks from new_sh() cannot be mixed with global allocations. If there isn't any intent to do so then I'll experiment using mmap() functions and Win32 variants. Thanks, -Phil

1 1

[Regex] Word boundary pattern does not match
by Teddy Brielle 13 May '08

13 May '08

Hi, I use the boost v1.35 regex library on Windows XP. I would like to find the '*' character from an input string only if this character is not bound to a word (for replacement purpose). I then use the following regular expression pattern to find occurrences in my input string: \B\*\B But this regular expression seems not to match any '*' character of the following input string: * test *test test* * te*st * I would expect that the regular expression would match the 1st, 4th and 6th '*' character. I have performed further tests with the pattern \b*\b, which works and matches the 5th '*' character. Here is the code I use : void Replace(std::string& string, std::string& pattern, std::string& replacementString) { try { std::string newString; // Looking for matching substrings (case insensitive) boost::regex expression (CStringToStdString(pattern), boost::regex::perl|boost::regex::icase); std::string::const_iterator start = string.begin(); std::string::const_iterator end = string.end(); boost::match_results<std::string::const_iterator> what; boost::match_flag_type flags = boost::match_default; while (boost::regex_search(start, end, what, expression, flags)) { // Replace the matching occurrence with the replacement string newString = newString + std::string(start, what[0].first); newString = newString + replacementString; // Next... start = what[0].second; } newString = newString + std::string(start, string.end()); string = newString; } catch (std::runtime_error e) { // Return string as is. TRACE(e.what()); } } and here are the provided parameters: string = "* test *test test* * te*st *"; pattern = "\\B\\*\\B"; replacementString = ""; Have I done something wrong in my pattern or in my code (match flags,...) ? Thanks in advance for your help. Regards, Teddy

2 1

Newbie question on asio and TCP/IP
by Me here 13 May '08

13 May '08

Hi, I'm writing program with asio from 1.35.0 to read the data from a hardware device which sends data to my PC to port 7000. The sample below fails on Windows with exception code 10022, text "An invalid argument was supplied". Where's the fault? Can someone help please? Alexander ----------- sample code ------------- #include <iostream> #include <boost/asio.hpp> using boost::asio::ip::udp; int main(int argc, char* argv[]) { try { boost::asio::io_service io_service; udp::endpoint sender_endpoint( udp::v4(), 7000 ); udp::socket socket(io_service); socket.open( udp::v4() ); char packet[1024]; size_t len = socket.receive_from( boost::asio::buffer(packet), sender_endpoint); std::cout << "Works\n"; } catch(const std::exception& e) { std::cerr << e.what() << std::endl; } return 0; } ____________________________________________________________________________________ Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now. http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ

2 1

[asio] 1.35.0 documentation to pdf problem?
by Jonathan Biggar 13 May '08

13 May '08

I'm trying to build a .pdf of boost.asio documentation, but it fails with this message (and two more identical errors with different stack traces): > javax.xml.transform.TransformerException: org.apache.fop.fo.ValidationException: > file:/home/corvette/jon/tech/boost-1.35.0/libs/asio/doc/../../../bin.v2/libs/as > io/doc/gcc-4.1.2/debug/standalone_doc.fo:24047:598: Error(24047/598): fo:list-bl > ock is missing child elements. > Required Content Model: marker* (list-item)+ > at org.apache.fop.cli.InputHandler.transformTo(InputHandler.java:168) > at org.apache.fop.cli.InputHandler.renderTo(InputHandler.java:115) > at org.apache.fop.cli.Main.startFOP(Main.java:166) > at org.apache.fop.cli.Main.main(Main.java:197) Anybody have any suggestions or better luck? -- Jon Biggar Floorboard Software jon(a)floorboard.com jon(a)biggar.org

2 1

Compilation error in mutex.hpp
by Stas Khirman 13 May '08

13 May '08

Just found a compilation problem in include/boost-1_35/boost/pool/detail/mutex.hpp line 67. While compiling with VS2005 under WinXp, got compilation error "C2872: 'CRITICAL_SECTION' : ambiguous symbol". ( project is quite complicated, with many includes and soon) Fix is trivial: ::CRITICAL_SECTION mtx; // note "::" to resolve symbol mix-up.

1 0

How to review futures?
by John Phillips 13 May '08

13 May '08

I'm looking to see if there are any good ideas for how to review the two futures libraries that are both currently in the queue. Since they are two different approaches to the same problem domain, isolated sequential reviews does not seem to be a good idea. So far, the best thought I've had on the subject is to run a single review that includes both libraries, where it is explicitly part of the review to discuss which parts of which realizations are the best choice. This process will need to keep the proposals before the committee in mind, but it is a way to compare and contrast the strengths of the two in close proximity. If we do this, there are a couple of questions that should be added to the usual review process. * Which interface choices are best suited to the problem domain? * Should Boost offer competing implementations of this feature? * Should the libraries be melded together? * Should a subset of the approved library be restricted to only the facilities and interface in the standardization committee proposal? There are my initial thoughts. I would like to hear from others on this, as well. I especially would like to hear from the authors and from anyone who has been involved in the evolving standards proposal. Thanks for your ideas. John Phillips Review Wizard

5 7

[smart_ptr] Proposal to add new_shared function
by Andrey Semashev 12 May '08

12 May '08

Hi, I've seen this topic floating around but it seems it didn't make it into boost for some reason. I propose to add a new helper function for shared_ptr, namely new_shared. The function would dynamically allocate an object and return shared_ptr that points to it. The function provides the following benefits: - It may perform better than allocating the object and constructing shared_ptr explicitly. Obviously, it allows to get rid of the additional allocation for the counter object. - The function is effectively a safer replacement for the core operator new. It solves the frequently missed memory leak pointed out by Meyers: foo(shared_ptr< A >(new A), bar()); I've made a quick implementation that supports the following: - Arbitrary number of constructor arguments. C++0x features (variadic templates and rvalue references) are supported in addition to the traditional and more limited C++03 version. - Support for custom deleters, which are now more "destroyers" because a deleter used with the new_shared function should not free memory from the destroyed object. - Support for custom allocators. It is through allocators the memory for both the object and the counter are allocated and deallocated. - The shared_ptr implementation is intact, the new feature is a pure addition (however, it could be made a bit more effective with a little help from shared_ptr). The implementation is available in the Vault: http://tinyurl.com/6sxtpg Some quick examples of use: shared_ptr< A > p1 = new_shared< A >(); // default ctor shared_ptr< B > p2 = new_shared< B >(x, y, z); // parametrized ctor shared_ptr< C > p3 = new_shared< C >(ref(x)); // passing references // using custom deleter shared_ptr< D > p4 = new_shared< D >(use_deleter(d)); // using custom allocator shared_ptr< E > p5 = new_shared< E >(use_allocator(a)); // you can mix the above cases shared_ptr< F > p6 = new_shared< F >( use_deleter(d), use_allocator(a), x, ref(y)); shared_ptr< G > p7 = new_shared< G >( use_allocator(a), use_deleter(d), z); The use_allocator and use_deleter arguments may be in either order, but must be the first arguments of new_shared, if used. Do you think this would be a reasonable addition to Boost.SmartPtr?

2 2

GCC Visibility Support
by Steven Dodd 12 May '08

12 May '08

I think it would be worthwhile to extend Boost to support GCC's (relatively) new visibility features. For those unfamiliar with GCC's visibility features, please read the following articles for background: http://gcc.gnu.org/wiki/Visibility http://developer.apple.com/technotes/tn2007/tn2185.html Please forgive any ignorance displayed in the following proposal - I'm new to Boost, and only more-so to Boost library development! I've reviewed all of the messages I could find on the mailing list related to this subject, but didn't see one that provided a comprehensive proposal for adding full visibility support. So here goes: There are essentially two use-cases which need to be addressed: ( 1 ) Compiling Boost with restricted visibility In this case, the user wants to gain the full benefits of restricted symbol visibility, and so they want to compile both their own code and Boost with restricted symbol visibility. That is, they want to build Boost with some combination of the GCC flags: -fvisibility=hidden, -fvisibility-inlines-hidden, and -fvisibility-ms-compat (OS X specific). In order to build Boost properly with restricted symbol visibility, Boost needs to be configured to mark all public symbols as such. On Windows, Boost already does this by (A) defining BOOST_HAS_DECLSPEC in <config/platform/win32.hpp>, and (B) defining and using library-specific _DECL macros (e.g. BOOST_FILESYSTEM_DECL = __declspec(dllexport) or __declspec(dllimport) depending on whether the library is being built, or used). What needs to be done to support GCC's symbol visibility restriction is to generalize the support already in place for Windows, along the following lines: - Rename BOOST_HAS_DECLSPEC to BOOST_HAS_SYM_CONTROL, and define this symbol in appropriate config headers. For GCC, this should be an optional feature, and I'm not sure of how to best allow users to enable/disable it (e.g. how to integrate it as a Boost.Build option). Change all locations to use the new name. - Introduce macro, BOOST_SYM_EXPORT, and define as __declspec(dllexport) on Windows, and as __attribute__((visibility("default"))) for GCC. Change all locations currently hard-coding __declspec( dllexport ) to use BOOST_SYM_EXPORT instead. - Introduce macro, BOOST_SYM_IMPORT, and define as __declspec(dllimport) on Windows, and as __attribute__((visibility("default"))) for GCC. Change all locations currently hard-coding __declspec( dllimport ) to use BOOST_SYM_IMPORT instead. This approach should work "out-of-the-box" when using GCC's -fvisibility-ms-compat mode (MSVC++ compatibility mode), since it already works on Windows. However, this approach will likely be incomplete when using GCC's -fvisibility=hidden mode. Reason being, unlike the visibility-ms-compat mode, this mode does not automatically mark types with "vague linkage" as visible (e.g. type_info). As a result, exceptions thrown in one DSO will not be caught in other DSOs. It is beyond my understanding of Boost to propose a comprehensive set of changes required to address the problem. ( 2 ) Compiling Boost with normal visibility, but enabling linkage into user-code compiled with restricted visibility In this case, the user wants to build their own code with restricted symbol visibility, but wants to link against a copy of Boost compiled with default visibility (e.g. most likely, a pre-built Boost binary). Presently, upon doing so, the user will find themselves faced with a slew of linker warnings regarding the mismatch in visibility levels between Boost symbols compiled into user-code vs. in the Boost libraries. In order to resolve this issue properly (e.g. not just silence the linker), Boost needs to be modified to wrap all Boost types in "default" visibility instructions, like so: #pragma GCC visibility push(default) ... boost types ... #pragma GCC visibility pop Boost's existing ABI facility is sufficient for this task, were it employed consistently by all Boost libraries (unfortunately, as far as I can tell, it is not): - Create file <boost/config/abi/gcc_default_visibility_prefix.hpp> with the following contents: #pragma GCC visibility push(default) - Create file <boost/config/abi/gcc_default_visibility_suffix.hpp> with the following contents: #pragma GCC visibility pop - In the appropriate config header, define BOOST_ABI_PREFIX as "boost/config/abi/gcc_default_visibility_prefix.hpp", define BOOST_ABI_SUFFIX as "boost/config/abi/gcc_default_visibility_suffix.hpp", and define BOOST_HAS_ABI_HEADERS. Note: this should be the default for GCC, however, if the user has requested restricted symbol visibility, as in use-case (1), then these BOOST*ABI macros must not be defined, or the prefix/suffix headers at least need to conditionally define the visibility based on some other macro definition... I look forward to comments! Cheers, Steven Dodd sdodd<at>view22<dot>com

1 0

[graph] [serialization] serialized descriptors
by Carlos Rafael Giani 12 May '08

12 May '08

Hello, there is utility code for serializing an adjancency_list graph to an archive in the BGL. But I wonder about two things: 1) I have a list of descriptors in my program. This list is a selection of vertices. If I want to serialize my program's states, I need to serialize the graph as well as this selection. This means I have to serialize references to vertices. Now AFAIK I cannot simply serialize descriptors, because they essentially are pointers. I need a persistent ID. Is there existing functionality for this? If not, I have to either use one of the vertex properties as ID, or autogenerate IDs (for example, by using casting the descriptors to an intptr_t and using this value as ID) and upon deserialization use these for mapping the right descriptors back into the list. 2) One vertex property is a map of boost::any values. map < string, any > to be exact. Does the BGL serialize the properties? If so, how does it deal with boost::any constructs?

2 2

[thread] thread_group create_thread template function
by vicente.botet 12 May '08

12 May '08

Hi, the thread_group::create_thread takes a const function0<void> parameter: thread* create_thread(const function0<void>& threadfunc); The function0 implies already a memory allocation. The templated version look like: template <class Threadable> thread* thread_group::create_thread(Threadable threadfunc) { // No scoped_lock required here since the only "shared data" that's // modified here occurs inside add_thread which does scoped_lock. std::auto_ptr<thread> thrd(new thread(threadfunc)); add_thread(thrd.get()); return thrd.release(); } Which works faster because no need to allocate memory for the boost::function0<void()>. Anthony, if there is nothing wrong, could this substitute the create_thread function in next Boost::thread release? Best regards _____________________ Vicente Juan Botet Escriba

2 2

GCC 4.3/ia64 build of 1.35 fails on polymorphic_iarchive
by Steve M. Robbins 12 May '08

12 May '08

Bernd, Did you solve the issue reported in [1]? The Debian build for ia64 fails in the same way [2]: In file included from libs/serialization/src/polymorphic_iarchive.cpp:18: ./boost/archive/polymorphic_iarchive.hpp:88: error: 'virtual void boost::archive::polymorphic_iarchive_impl::load(int64_t&)' cannot be overloaded ./boost/archive/polymorphic_iarchive.hpp:84: error: with 'virtual void boost::archive::polymorphic_iarchive_impl::load(long int&)' ./boost/archive/polymorphic_iarchive.hpp:89: error: 'virtual void boost::archive::polymorphic_iarchive_impl::load(uint64_t&)' cannot be overloaded ./boost/archive/polymorphic_iarchive.hpp:85: error: with 'virtual void boost::archive::polymorphic_iarchive_impl::load(long unsigned int&)' ...failed gcc.compile.c++ bin.v2/libs/serialization/build/gcc-4.3.1/release/polymorphic_iarchive.o... [1] http://article.gmane.org/gmane.comp.lib.boost.devel/172455 [2] http://buildd.debian.org/fetch.cgi?&pkg=boost1.35&ver=1.35.0-1&arch=ia64&st… Thanks, -Steve

1 0

[thread] is this reverse_lock class a source of errors?
by vicente.botet 11 May '08

11 May '08

Hi, Consider the following situations: { unique_lock<mutex> lock(smtx); // ... some writing operations { // non locked block reverse_lock< unique_lock<mutex> > rlock(lock); // ... some code not needing the mutex to be locked } // locked again // ... } or { shared_lock<mutex> lock(smtx); // ... some reading operations { // non locked block reverse_lock< shared_lock<mutex> > rlock(lock); // ... some code not needing the mutex to be locked } // locked again // ... } Do you think this usage is souhaitable or is this source of errors? The class reverse_lock can be defined as follows: template <typename Locker> class reverse_lock { BOOST_CONCEPT_ASSERT((MovableLockConcept<Locker>)); public: reverse_lock(Locker& locker) : locker_(locker) /*< Store reference to locker >*/ , tmp_locker_(locker.move()) /*< Move ownership to temporaty locker >*/ , was_locked_(false) { #ifndef BOOST_SYNC_REVERSE_LOCK_DONT_CHECK_OWNERSHIP /*< Define BOOST_SYNC_REVERSE_LOCK_DONT_CHECK_OWNERSHIP if you don't want to check locker ownership >*/ if (tmp_locker_.mutex()==0) { locker_=tmp_locker_.move(); /*< Rollback for coherency purposes >*/ throw lock_error(); } #endif if (tmp_locker_) { /*< ensures it is unlocked >*/ tmp_locker_.unlock(); was_locked_=true; } } ~reverse_lock() { if (was_locked) { tmp_locker_.lock(); } locker_=tmp_locker_.move(); /*< Move ownership to nesting locker >*/ } private: Locker& locker_; Locker tmp_locker_; bool was_locked_; reverse_lock(); }; Comments? _____________________ Vicente Juan Botet Escriba

5 6

[future] Integrating recent future lib into old-ish threadpool lib
by Chris Fairles 10 May '08

10 May '08

There's a nice threadpool library (http://threadpool.sourceforge.net) mentioned on a previous thread that I took a look at and noticed it had a basic future impl. of its own. Given that there's a future library under review, I swapped out the original future impl. in the schedule function, plus added a lazy_schedule (from the examples @ http://braddock.com/~braddock/future/ ) for fun. I replaced everything in future.hpp from the threadpool lib with: /* * Copyright (c) 2005-2007 Philipp Henkel * * Use, modification, and distribution are subject to the * Boost Software License, Version 1.0. (See accompanying file * LICENSE_1_0.txt or copy at http://www.boost.org/LICENSE_1_0.txt) * * http://threadpool.sourceforge.net * * Chris Fairles, May 2008 - Modified to replace custom future implementation with boost-reviewed version */ #pragma once #include <boost/future/future.hpp> namespace boost { namespace threadpool { template<class Pool, class F> future<typename result_of< F() >::type> schedule(Pool& pool, F const& task) { typedef typename result_of< F() >::type result_type; promise<result_type> prom; pool.schedule(future_wrapper<result_type>(task, prom)); return future<result_type> (prom); } template<class Pool, class F> future<typename result_of< F() >::type> lazy_schedule(Pool& pool, F const& task) { typedef typename result_of< F() >::type result_type; promise<result_type> prom; future<void> guard = prom.get_needed_future(); guard.add_callback(bind(&Pool::schedule, pool, future_wrapper<result_type>(task, prom))); return future<result_type> (prom); } } } // namespace boost::threadpool where #include <boost/future/future.hpp> is the header for the lib under review (and pardon the pragma windowism). I haven't tested it throughly but on msvc9, the most trivial of cases work (including catching exceptions) so YMMV. Ex. int task_int_1() { throw std::exception("task_int_1 exception"); return 1; } int task_int_2() { return 2; } int main() { pool tp; tp.size_controller().resize(2); future<int> result1 = schedule(tp, &task_int_1); future<int> result2 = schedule(tp, &task_int_2); try { int val = result1 + result2; std::cout << "you will never see this value... " << val << std::endl; } catch (std::exception const& ex) } std::cerr << ex.what() << std::endl; } } Something to play around with anyway. Cheers, Chris

1 0

[thread] lockable traits and concepts classes adding proposal
by vicente.botet 10 May '08

10 May '08

Hello boosters , While writtig a synchronization library I have needed some lockable traits and concepts. If you think that these classes are of general use it will be a pleasure for me, if Anthony accepts, to included them on the Boost.Thread library. Otherwise I will left them in my sync library. For the moment all is defined in a sync (as synchronization) namespace and directory but this is without importance. Attached a short introduction as well as the header files. Of course all this is subject to discusion, naming and file structure changes, ... For each one of the mutex in the thread library, we need to * make the mutex inherit from the helper lock_traits_base or * have nested typedefs or * specialize each one of the traits templates As an external library I have do this in a non-intrusive way as for example: template<> struct timed_interface_tag<boost::mutex> { typedef hasnt_timed_interface_tag type; }; template<> struct reentrancy_tag<boost::mutex> { typedef non_recursive_tag type; }; template<> struct category_tag<boost::mutex> { typedef exclusive_lock_tag type; }; template<> struct scope_tag<boost::mutex> { typedef multi_threaded_tag type; }; But if included in the Thread library it will be better to use one of the intrusive methods. I have also other classes that could be of general interest. * A make_..._lockable set of mixin class will make lockable the derived class. It can be used as follows: class X : public make_exclusive_lockable<X, boost::mutex> { } X x; unique_lock<X> lock(x); * a ..._synchronization_family set of classes that can be used as follows: template <class SyncFamily> message_queue; typedef message_queue<thread_synchonization_family> my_mt_message_queue; typedef message_queue<null_synchonization_family> my_st_message_queue; The null_synchonization_family needs a null_mutex and a null_condition classes. * To finish, I'm working on a filter_matching_lockables meta-function which take as parameter a vector of lockables types and will filter the lockables types not satisfying a list of traits. The use shoul be somthing like typedef filter_matching_lockables<vector<boost::mutex, boost::recursive_mutex, ...>, and_<is_exclusive_lock<_>, not_<is_recursive_lock<_> > >::type candidates. and a find_best_lock which choose between the lockables given as parameter the best one following a given criterium. Of course, there is yet a lot of work to complete, add lock concepts, document, tests, document, tests ... between others, that I will be please to do even if included in the Thread library. As you see there is nothing new, neither complex, only some helper classes that currently are missing in boost. Have a good code reading and please let me know what do you think. _____________________ Vicente Juan Botet Escriba

1 0

[result_of][patch] decltype-based implementation
by Daniel Walker 10 May '08

10 May '08

Hello, With all the recent discussion about result_of and now that decltype has started to trickle into compilers, I thought it might be a good time for Boost to provide a result_of along the lines of the typeof-based implementation described in N1454. I've attached a patch to Ticket #862, which does this. http://svn.boost.org/trac/boost/ticket/862 This is an old bug report that apparently got a little mangled during the SVN migration, but I think result_of/lambda compatibility is a familiar problem. My patch fixes the problem of using result_of with lambda on compilers that support decltype. It does not preclude fixes to the problem on C++03 platforms, such as Shunsuke Sogame's Egg and Marco Costalba's multi-signature function, for example. It also makes boost::result_of more compliant with the current C++0x std::result_of described in N2588. My patch differs from N2588 in that std::result_of only supports function call expressions of the form f(x). I read this as precluding support for member function pointers, which are invoked with expressions of the form o->*f(x). My patch reuses the pointer specialization from the current implementation, so that boost::result_of can continue support both. It also may differ from N2588 in terms of the lvalue/rvalue specifications. I'm not sure that I understand this correctly, and I would be grateful if someone would look over it to see if my implementation should be changed for better conformance. The patch also includes updates to the documentation and tests. I tested with msvc 9, gcc 3.4, and gcc 4.3. Thanks for your consideration! Daniel Walker

2 2

[config] Type in config/abi_suffix.hpp file
by Alexei Alexandrov 10 May '08

10 May '08

Hi, there is a minor inconsistency I noted in config/abi_suffix.hpp file. This line # error Header boost/config/abi_prefix.hpp must only be used after boost/config/abi_prefix.hpp should be # error Header boost/config/abi_suffix.hpp must only be used after boost/config/abi_prefix.hpp -- Alexei Alexandrov

2 1

Re: [boost] Profiling template instantiations
by Boris Gubenko 09 May '08

09 May '08

Steven Watanabe wrote: > Ok. It would be great if compilers supported this directly. Just fyi: the cxx compiler has verbose template instantiation mode. On Tru64, for example: x.cpp ----- #include <map> int main() { map<int, int> m; return m.size(); } cosf.zko.hp.com> cxx -V Compaq C++ V7.1-006 for Compaq Tru64 UNIX V5.1B (Rev. 2650) Compiler Driver V7.1-006 (cxx) cxx Driver cosf.zko.hp.com> cxx -ptv -c x.cpp cxx: Info: /usr/lib/cmplrs/cxx/V7.1-006/include/cxx/tree.cc, line 84: automatically instantiating void _RWrwstd::_RWrb_tree<int, std::pair<const int, int> , _RWrwstd::_RWselect1st<std::pair<const int, int> , int> , std::less<int> , std::allocator<std::pair<const int, int> > > ::_RWdeallocate_buffers() void _RWrb_tree<_Key, _Val, _KeyOf, _Comp, _Alloc>::_RWdeallocate_buffers () ------------------------------------------------------^ cxx: Info: /usr/lib/cmplrs/cxx/V7.1-006/include/cxx/tree.cc, line 549: automatically instantiating void _RWrwstd::_RWrb_tree<int, std::pair<const int, int> , _RWrwstd::_RWselect1st<std::pair<const int, int> , int> , std::less<int> , std::allocator<std::pair<const int, int> > > ::_RWerase(_RWrwstd::_RWrb_tree<int, std::pair<const int, int> , _RWrwstd::_RWselect1st<std::pair<const int, int> , int> , std::less<int> , std::allocator<std::pair<const int, int> > > ::_RWrb_tree_node *) void _RWrb_tree<_Key, _Val, _KeyOf, _Comp, _Alloc>::_RWerase (_RWlink_type x) ------------------------------------------------------^ cxx: Info: /usr/lib/cmplrs/cxx/V7.1-006/include/cxx/tree.cc, line 301: automatically instantiating _RWrwstd::_RWrb_tree<int, std::pair<const int, int> , _RWrwstd::_RWselect1st<std::pair<const int, int> , int> , std::less<int> , std::allocator<std::pair<const int, int> > > ::iterator _RWrwstd::_RWrb_tree<int, std::pair<const int, int> , _RWrwstd::_RWselect1st<std::pair<const int, int> , int> , std::less<int> , std::allocator<std::pair<const int, int> > > ::erase(_RWrwstd::_RWrb_tree<int, std::pair<const int, int> , _RWrwstd::_RWselect1st<std::pair<const int, int> , int> , std::less<int> , std::allocator<std::pair<const int, int> > > ::iterator) _RWrb_tree<_Key, _Val, _KeyOf, _Comp, _Alloc>::erase (iterator position) -------------------------------------------------^ cxx: Info: /usr/lib/cmplrs/cxx/V7.1-006/include/cxx/tree.cc, line 565: automatically instantiating _RWrwstd::_RWrb_tree<int, std::pair<const int, int> , _RWrwstd::_RWselect1st<std::pair<const int, int> , int> , std::less<int> , std::allocator<std::pair<const int, int> > > ::iterator _RWrwstd::_RWrb_tree<int, std::pair<const int, int> , _RWrwstd::_RWselect1st<std::pair<const int, int> , int> , std::less<int> , std::allocator<std::pair<const int, int> > > ::erase(_RWrwstd::_RWrb_tree<int, std::pair<const int, int> , _RWrwstd::_RWselect1st<std::pair<const int, int> , int> , std::less<int> , std::allocator<std::pair<const int, int> > > ::iterator, _RWrwstd::_RWrb_tree<int, std::pair<const int, int> , _RWrwstd::_RWselect1st<std::pair<const int, int> , int> , std::less<int> , std::allocator<std::pair<const int, int> > > ::iterator) _RWrb_tree<_Key, _Val, _KeyOf, _Comp, _Alloc>::erase (iterator first, -------------------------------------------------^ cosf.zko.hp.com> ----- Original Message ----- From: <boost(a)lists.boost.org> To: <boost(a)lists.boost.org> Sent: Thursday, May 08, 2008 8:29 PM Subject: Re: [boost] Profiling template instantiations > AMDG > > Simonson, Lucanus J wrote: >> Ingenious, you are automatically inserting a compile time error into >> every basic block of the template code to be profiled, compiling the >> translation unit and counting how many error are generated for each >> template to get a count of how many times the compiler tries (and fails) >> to instantiate the template. >> > > Actually it only generates warnings. Otherwise, the compiler is liable > to stop before it finishes compiling everything. > >> There may be a more direct way to extract this information with VTune >> related profiling features provided in icc. I'll follow up and let you >> know. >> > > Ok. It would be great if compilers supported this directly. > > In Christ, > Steven Watanabe > > _______________________________________________ > Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost >

3 3

Re: [boost] Profiling template instantiations
by Boris Gubenko 09 May '08

09 May '08

Steven Watanabe wrote: > I only see function template instantiations, I'm more interested in > class template instantiations because that's where the metaprogramming > is done. Am I missing something? What example in my previous mail shows is names of member functions of class templates being automatically instantiated, along with template arguments they are instantiated on. The output of verbose template instantiation mode serves us well for building common instantiation libraries and this is, probably, why reporting of class template instantiations was never requested. I'm not suggesting cxx as a replacement for your tool. As I said in the previous mail, this is fyi :-) Thanks, Boris ----- Original Message ----- From: <boost(a)lists.boost.org> To: <boost(a)lists.boost.org> Sent: Friday, May 09, 2008 10:38 AM Subject: Re: [boost] Profiling template instantiations > > AMDG > > Boris Gubenko wrote: >> Steven Watanabe wrote: >> >>> Ok. It would be great if compilers supported this directly. >>> >> >> Just fyi: the cxx compiler has verbose template instantiation >> mode. On Tru64, for example: >> >> <snip> >> > > > I only see function template instantiations, I'm more interested in > class template instantiations because that's where the metaprogramming > is done. Am I missing something? > > I'd also like to have all template instantiations, not just those > that are triggered from inside other template instantiations. > (Although this doesn't make a huge difference) > > In Christ, > Steven Watanabe > > _______________________________________________ > Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost >

2 1