March 2008 - Boost - lists.preview.boost.org

[thread] Docs don't build on release branch
by Darren Garvey 19 Mar '08

19 Mar '08

Hi Anthony, The Jamfile.v2 in libs/thread/doc/ seems to be missing a 'using quickbook ;' I quite like the new organisation. Do you have any idea how stable this API is likely to be though, with it tracking the C++0x standard proposals? Regards, Darren

4 9

[gsoc2008] interest for component library?
by Themis Bourdenas 19 Mar '08

19 Mar '08

Hi, I want to propose a project for participation in Google SoC 2008 with boost. My proposal is a software component library for C++. The goal is the creation of a library that assists component based software development, bringing a well defined, existing model to C++. Is there any interest for such a library? nesC is an extension to the C language developed in UC Berkeley to support development in real-time embedded systems running tinyOS. The extensions to the C language are around the notion of components/modules and their orchestration (configuration) in order to deploy a running application. They use a meta-compiler that transforms nesC code to ANSI C, which then actually runs on the motes. Of course the nesC programming model is not tied to real-time systems and translates in large systems as well. My proposal is to provide the same model in a C++ library, without the need of a meta-compiler, but providing a DSEL. If you are unfamiliar with nesC, you can find more in http://nescc.sourceforge.net/, but below I'll give a quick overview and glossary of the terms used in the model and how they can translate in C++. - interface -- an abstract class that defines an API contains commands and events - module -- a class that is a concrete implementation of one or more interfaces, it provides and uses one or more interfaces - provide -- the relationship of a module that provides an interface is similar to the inheritance relationship, the module implements the interface's declared commands and triggers its declared events - use -- a module that uses an interface implies that it requires the existence of a module that implements that interface - command -- an exported function declared in an interface, implemented by a module - event -- a signal declared in an interface, fired by a module - configuration -- a specification of wiring (mapping) of modules to interfaces, constructing an entity that can be considered as a composite module (aka orchestration of components) - wiring -- instantiation of a module and attachment to an interface that is used by another module or configuration The benefits of component based development are obvious; clean architectural dissemination of software, self-containment of modules and orchestration of new services and applications based on already existing ones. I have adjusted the basic concepts behind nesC as presented in its web site to translate to general programming: - separation of construction and composition: programs are built out of components, which are assembled ("wired") to form whole applications. - specification of component behavior in terms of set of interfaces. Interfaces may be provided or used by components. The provided interfaces are intended to represent the functionality that the component provides to its user, the used interfaces represent the functionality the component needs to perform its job. - interfaces are bidirectional; they specify a set of functions to be implemented by the interface's provider (commands) and a set of signals fired to the interface's user (events). This allows a single interface to represent a complex interaction between components (e.g., registration of interest in some event, followed by a callback when that event happens). - components can be statically linked to each other via their interfaces, furthermore components should be linked dynamically (at run-time) allowing modification of program's behavior. Below I give an example of orchestration for an IDE application where you want to setup the environment to handle C++ sources. Setup compilers, source documents, runtime env, source editor etc. configuration cpp_ide { module<ide>.interface<Compiler> -> module<gcc> module<ide>.interface<SourceFile> -> module<CppSource> module<ide>.interface<Editor> -> module<CppEditor> module<ide>.interface<Output> -> module<Console> } In the above simple example we create a configuration of the ide module, namely cpp_ide, wiring its interfaces to some implemented modules. The notation of module<> and interface<> is to help you distinguish between different entities. Alternatively, you could setup the environment for e.g. python given that you implement the proper modules, reusing code from some common modules (e.g. console and the ide infrastructure). I want to support both static configurations like this and dynamic configuration, (e.g. setup an environment depending on configuration files). Of course the true benefits of components come from the fact that they can be dynamically loaded at runtime. I intend to use the boost.extension library, which seems to have reached a stable state, for facilitating this requirement. That would require components to just depend on interfaces instead of actual implementation. In addition, I want to expand the library to interoperate with boost.reflection so that a module's interface can be wired with an arbitrary module as long as it provides the functional requirements set by the interface. In the latter case detection of incompatibilities between modules (i.e. missing functions) are postponed and handled during runtime, as they can not be resolved statically. So, please give me some feedback on whether such a library would be an interesting contribution to boost and if you want me to elaborate on my ideas for the project. Cheers, Themis

1 0

[fusion] BOOST_FUSION_ADAPT_STRUCT
by Eric Niebler 19 Mar '08

19 Mar '08

Say I have a struct D that derives from B, like: struct B { int i1; } struct D : B { int i2; } I can adapt B to be a Fusion sequence with: BOOST_FUSION_ADAPT_STRUCT(B, (int, i1)) Now I want to adapt D. Do I have to enumerate B's members again, or is there a way to express the inheritance relationship so that it Just Works? -- Eric Niebler Boost Consulting www.boost-consulting.com

1 0

[1.35.0] RC2?
by Beman Dawes 19 Mar '08

19 Mar '08

Thanks to help from a lot of Boosters, many of the issues with RC1 have been fixed. Does anyone have any last minute issues they would like to bring up before we issue RC2? --Beman

4 5

Trac open bugs - by assignee
by Marshall Clow 19 Mar '08

19 Mar '08

[ 225 open bugs today, 225 yesterday ] If you are maintaining a library, and have not logged into the trac system at <http://svn.boost.org/trac/boost/>, please do so ASAP. Until you do that, no tickets can be assigned to you, and will remain under "None". Instructions on working with tickets can be found at: <http://svn.boost.org/trac/boost/wiki/TicketWorkflow> and a mapping of user names to "real names" can be found at: <http://svn.boost.org/trac/boost/report/16> Bug summary 23 djowel 21 az_sw_dude 14 grafik 13 vladimir_prus 12 doug_gregor 12 dgregor 12 dave 11 no-maintainer 11 agurtovoy 10 bemandawes 8 anthonyw 7 turkanis 7 jsiek 6 johnmaddock 5 witt 5 igaztanaga 4 ramey 4 ebf 3 nesotto 3 matias 3 kaalus 3 danielw 3 None 2 shammah 2 rogeeff 2 pavol_droba 2 nasonov 2 jmaurer 2 hkaiser 2 danieljames 2 aaron_windsor 1 urzuga 1 t_schwinger 1 speedsnail 1 samuel_krempp 1 pdimov 1 marshall 1 garcia 1 fcacciola 1 dlwalker None 1493 SVN files making it through to install None 1644 Boost.Test missing documentation file BOOST_CHECK_CLOSE_FRACTION.html None 1697 [utility][noncopyable] ADL barrier broken by msvc-9.0 aaron_windsor 1622 Adjacency list needs to handle self-edges correctly aaron_windsor 778 top-level configure is broken agurtovoy 1001 gcc 4.1.2 segfaults on mpl/test/apply.cpp agurtovoy 1051 MPL header ordering triggers bug agurtovoy 1099 unable to iterate through a "non-explicitly-declared" mpl::set agurtovoy 1215 Boost 1.34.1_ mpl: Wrong workaround detection using MinGW32 (or.hpp_ line #33) agurtovoy 1317 has_xxx randomly broken in msvc agurtovoy 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 1640 [Thread] warnings from VC9 + warning level 4 anthonyw 1657 Bug in boost::threads sample 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 1386 date_time documentation Jamfile breaks building of boost docs 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 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 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 danielw 1044 Argument pack inaccessable in a functions return type danielw 1054 Parameter takes an "infinite" amount of time to compile with the Intel compiler. danielw 1097 keyword.hpp generates many warnings C4180: qualifier applied to function type has no meaning; ignored dave 1010 linking boost.python on freebsd dave 1019 iterator_facade::pointer should be the return type of operator-> (DR 445) dave 1085 Python rules for compiling in Mac OS X dave 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 865 Use of C++0x keyword as identifier dave 910 gcc strict-aliasing problems with python 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 1395 Write Tests for Python Bindings dgregor 1630 gcc-4.3: adjacency_list.hpp includes deprecated header dgregor 1680 long long and wchar_t support in MPI dgregor 556 Bundled graph properties dgregor 732 Johnson All-Pairs needs better "no path" information dgregor 736 Const correctness violation djowel 1170 Emit Warnings instead of # symbols in the syntax highlighter djowel 1171 Quickbook title output djowel 1172 non-utf djowel 1176 Space after inline code djowel 1206 Escaping from within code? djowel 1273 CR+LF newlines in position_iterator djowel 1276 spirit problem with _GLIBCXX_DEBUG djowel 1277 Closing section like [pre with } causes Quickbok to crash djowel 1280 sections in imported source files get put inside <para> elements in docbook output djowel 1281 Quickbook produces invalid BoostBook/DocBook XML djowel 1324 tuple should have a swap() that operates element-by-element djowel 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) dlwalker 613 boost/crc.hpp uses non-standard conforming syntax doug_gregor 1021 [Graph][reverse_graph] Problem using reverse_graph adapter with an adapted user defined graph doug_gregor 1076 compile error: disconnecting struct with operator()() doesn't work in VS2005 SP1 doug_gregor 375 LEDA graph adaptors do not handle hidden nodes properly doug_gregor 402 random_vertex/random_edge are unnecessarily inefficient doug_gregor 403 Document copy_component doug_gregor 447 reverse_graph and constness of property maps doug_gregor 708 Dijkstra no_init version should not require VertexListGraph doug_gregor 733 Numbered headers don't work with "preferred" syntax doug_gregor 735 Fruchterman-Reingold grid performance can be improved doug_gregor 738 Memory leaks with signal::connect? doug_gregor 829 Implicit graph not implement doug_gregor 852 Problem with Boost and GCC 4.1 ebf 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 grafik 1041 Cygwin requires PATH setting. grafik 1322 trac rejects patch attachment as spam 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 1571 boost bugtracker displays a patch incorrectly 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 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 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 1314 Using SSE-intrinsics in VC8 causes static assert in type_with_alignment.hpp johnmaddock 1411 Fix BOOST_PARTIAL_SPECIALIZATION_EXPLICT_ARGS johnmaddock 1446 POSIX API doesn't use C locale johnmaddock 1451 error: use of C99 long long integer constant johnmaddock 1626 [type_traits] "bad_alloc is not a member of std" in has_virtual_destructor_test.cpp jsiek 1531 segfault in dynamic_bitset::reference assign operator jsiek 1540 Poisson distribution very slow for large mean (and may also overflow). 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 marshall 1252 [pool] severe overhead with unaligned sizes. matias 1406 Understanding the Tables outdated matias 1651 incorrect typedefs in examples matias 1676 Dead links on Boost.Test example documentation. nasonov 1220 lexical_cast requires RTTI 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 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 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 pdimov 1106 shared_ptr<T> should not convert to shared_ptr<U> when T* doesn't convert to U* ramey 1285 [serialization] problem when including shared_ptr_132.hpp ramey 1628 Lack of wide character support prevents boost.serialization from linking ramey 1662 boost::serialization for boost::optional - missing include ramey 1689 [serialization] Update a link rogeeff 1383 signal.h features not found on Mac OS rogeeff 1542 [test] compiler errors when building with stdcxx library 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 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 urzuga 574 [boost::lambda] Compile error with libstdc++ debug mode vladimir_prus 1165 more quoting problems vladimir_prus 1274 Useless error message vladimir_prus 1321 invalid docbook in tool documentation 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 469 multitoken broken vladimir_prus 689 [program_options] Endless loop with long default arguments witt 1046 Boost.Python quickstart instructions mention nonexistent target 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

[random] VC9 failures on release branch (was [release] Outdated vc9 testing?)
by Richard Webb 19 Mar '08

19 Mar '08

> Forwarded from the testing list (see http://article.gmane.org/gmane.comp.lib.boost.testing/5658) Beman Dawes <bdawes <at> acm.org> writes: > > Richard Webb wrote: > >>Looking at those results reminds me that the Release version of random still >>contains the failure raised in the ticket @ >>http://svn.boost.org/trac/boost/ticket/1423, which was fixed in Trunk a while >>back. Is it worth merging that change into the release branch? > > Yes, as long as it is stable on trunk, and can done right away. > > --Beman > Anyone with SVN access feel like merging this change across to the release branch? Thanks, Richard Webb

3 3

Logging library review results
by Gennadiy Rozental 19 Mar '08

19 Mar '08

This is unfortunately delayed results review of Logging library submitted by John Torjo. I read through the submitted reviews and here is a short summary: - 2 Tom Brinkman | evaluate it again, if a more boost friendly, lambda style public interface is present + 7 Steven Watanabe | all the issues with destructors and exceptions absolutely must be fixed + 7 Vadim | with some improvements to documentation and ease-of-use - 0 Phil Endecott | not in its current form + 9 Jurko Gospodnetic | seems good enough - 3 Jamie Allsop | changes that are needed are too numerous to warrant a 'yes and tidy-up' vote - 2 Christian Holmquist | the documentation is written with other scenarios in mind - 4 Sean Hunt | approach is a little too generic and forces the user to jump through hoops + 9 Arnstein Ressem | compiler and valgrind warnings has to be fixed before submission + 6 Loic Joly | yes, knowing this library will probably evolve anyway + 7 Paul A Pristow | expecting some quite major revisions of documentation, and perhaps implementation - 3 Amit | Not in its current form. with some changes library would have support -1/2 Paul Bexter | spread too thin - 4 Scott Woods | logging facility should be targeted slightly differently + 10 Bruce Sharpe | need exactly this functionality - 1 Andrey Semashev | expect something different and more elaborate from the logging library (The number after the vote is my own estimation of review vote in 0-10 grade). Paul Bexter did not express clear vote, but submitted an opinion supporting Amit position. In the end we came to 8 negative 7 positive votes with average 4.9 grade. Essentially opinions split right in a middle. Oh, how familiar these days ;) I must say this puts me in a quite a spot. The library obviously has great potential, but quite unacceptable by many in it's current form. While praising it's flexibility in many aspects, the reviewers expressed wide variety of serious concerns regarding design, implementation and documentation. Well, I can't delay it any more. ;) Under the circumstances, I prefer to err on a side of caution. The logging library submission is NOT accepted in it's current form. My biggest concern, as many others expressed here before, is that we do need the logging library. So I can't be any more encouraging to John to resubmit an updated version for review within any reasonably short time, once issues brought during review are addressed. I am not going to list all the issues here - you will need to look through quite detailed reviews, but I want to emphasize most prominent ones: * The library would gain from clean separation of framework and solution. What I mean here is that there should be separate layer which defines only generic concepts and another layer for specific solutions provided by library. My personal suggestion is to use layered design, where each layer is more feature-rich, but more targeted. * Library should support wide variety of "simple cases" out of the box and with minimal efforts required by users. *Each* usage scenario should be well documented and supported by example. * Library shouldn't try to be too smart. All optimizations and advanced features should be eliminated. At least not in a review version. This includes any kind of optimized strings or scenario based log selection. Later on you may start adding them based on user input. * I recommend to start some kind of pool for simple/common cases on the dev list before you jump to support them. Library should clearly state that other more advanced usage cases are supportable as well. The same recommendation applies to the general set of supported features by the library out of the box. * Macros usage should be marginally reduced. Documentation should explain how to write them, but not force them as the only solution. * You may consider supporting lambda like API an one of the alternatives. * Unicode support strategy needs to be fixed * Documentation require major revision. Obviously I can't put it as a requirement, but my personal recommendation - drop doxigen. IMO you can't have professional documentation based on this format. Plus it's unnecessarily pollute your code. Boostbook and Quickbook are much more attractive solutions. Also many reviewers expressed desire for more formal tone in user's guide and reference. (Another personal comment - where did you find word "gather" usage as noun? I personally would prefer something like "entry") Yet again I'd like to express our gratitude to the John for his efforts and hopes that he'll be able to see this library though to the eventual success. It has great potential. Gennadiy Rozental -- Review Manager --

3 3

xpressive fixes, ok to merge to release?
by Eric Niebler 19 Mar '08

19 Mar '08

I found some fixes that I made to trunk a while back and neglected to merge to release. They've been on trunk for a while and have caused no problems there. OK to merge? Changeset: http://svn.boost.org/trac/boost/changeset/43506 Fixes: http://svn.boost.org/trac/boost/ticket/1564 Changeset: http://svn.boost.org/trac/boost/changeset/43177 Fixes: http://svn.boost.org/trac/boost/ticket/1625 Also, I've corrected some minor docs inaccuracies and would like to merge those changes as well: Changeset: http://svn.boost.org/trac/boost/changeset/43718 -- Eric Niebler Boost Consulting www.boost-consulting.com

1 0

Logging library review results
by Tom Brinkman 19 Mar '08

19 Mar '08

I think that the library should have a very simple "use" case. It should have "no" learning curve, except for advanced uses. The advanced features should only be incorporated into the library after the "simple" cases are finished.

1 0

Logging library review results
by Tom Brinkman 19 Mar '08

19 Mar '08

>> you can't put string literals in a template Shur you can. I do it all the time. See "static_string" in previous post.

1 0