September 2007 - Boost - lists.preview.boost.org

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

15 Oct '07

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

3 2

[asio] order of initialization problem with boost::asio::error::system_category
by David Deakins 14 Oct '07

14 Oct '07

I am getting failures of the error.cpp regression test for asio that seem to be related to an order of initialization problem with the new boost::asio::error::system_category. It appears that asio::error::system_category is a const reference initialized by error::detail::get_system_category(), which simply returns boost::system::system_category. The problem seems to be that boost::system::system_category is itself a const reference to the actual system_category_const object created in Boost.System's error_code.cpp file. If it happens that the boost::asio::error::system_category reference is initialized before the boost::system::system_category reference, then boost::asio::error::system_category is a copy of the uninitialized boost::system::system_category reference rather than a reference to the system_category_const object. Attempting to use the category-related functions of an error_code created from the asio system_category enums then triggers an access violation. Of course, if boost::system::system_category is initialized first, then everything is fine. Hopefully that all made sense. Thanks, -Dave

3 2

[ANN] Xpressive 2.0 pre
by Eric Niebler 12 Oct '07

12 Oct '07

It's a poorly kept secret that I've been adding new features to Xpressive on CVS HEAD for a while now. So here are the features already implemented (documentation forthcoming) for Xpressive 2.0: << Semantic Actions >> Specify code to execute when parts of a regex match, a-la Spirit's semantic actions. Eg.: if you want to parse a string of name/value pairs into a std::map, you might: std::map<std::string, int> result; std::string str("aaa=>1 bbb=>23 ccc=>456"); // Like "(\\w+)=>(\\d+)": sregex pair = ( (s1= +_w) >> "=>" >> (s2= +_d) ) [ ref(result)[s1] = as<int>(s2) ]; sregex rx = pair >> *(+_s >> pair); if(regex_match(str, rx)) { assert(result["aaa"] == 1); assert(result["bbb"] == 23); assert(result["ccc"] == 456); } The actions are placed on a queue and executed in order only when the regex match succeeds. << Custom Assertions >> Use the check() function to create a boolean predicate that can participate in the match. Here's a regex that recognizes two integers only if the first is less than the second: sregex rx = ( (s1= +_d) >> ' ' >> (s2= +_d) ) [ check( as<int>(s1) < as<int>(s2) ) ]; Unlike actions, predicates execute immediately. You can also define the predicate out-of-line as a function object. << Dynamic Regex Grammars with Named Regexes >> Using regex_compiler, you can map a name to a regex object, and then refer to that regex from another by name. In this way, you can build grammars from regexes at runtime. sregex_compiler comp; sregex rx = comp.compile("^bar(?$RE)baz$"); comp.compile("(?$RE=)\\d+ \\d+"); There's an alternate syntax for associating a name with a regex that you can use to nest a static regex in a dynamic one. Eg., the last line above could be: comp["RE"] = +_d >> ' ' >> +_d; With these changes, you can now nest static and dynamic regexes within each other freely, giving you lots of flexibility to build grammars and modify them on the fly. << Named Captures >> For dynamic regular expressions, you can create a named capture with (?P<name> ...). You can refer back to the named capture with (?P=name). In substitution strings (for use with regex_replace()), you can refer back to a named capture with \\g<name> when using the format_perl or format_all flags. And more .... I'd like to give props to Dave Jenkins who has been doing m4d things with this stuff already, and who has given me a laundry list of other features he'd like. The new features are only available in CVS HEAD, for now. Feedback is welcome. -- Eric Niebler Boost Consulting www.boost-consulting.com

3 7

Runtime Dynamic Dispatch Library (0.2)
by Dean Michael Berris 12 Oct '07

12 Oct '07

Hi Everyone, This version of the Dispatcher uses Boost.Fusion and Boost.Function. It also contains the strategized_map template (and test) which is basically an associative container which allows you to strategize the index validation and routing of the index. The strategized_map though is currently undocumented, though the unit tests already provide hints on how to use it. This release has been tested on Linux with GCC version 4.1.2 and Windows with MSVC 8.0 (Visual C++ 2005) against Boost's Subversion trunk. Comments and suggestions would be most appreciated. Please feel free to download the package(s) from Sourceforge: http://tinyurl.com/2cbzyl Or from the Boost Vault: http://tinyurl.com/24m2y2 This still does not implement the multiple-signature feature which I'm still contemplating on putting in, but this is already useful by itself. Please let me know if you would like to see some more compelling features you'd like to see in this library so that I can put them in before I formally submit it for review. Those who want to help cleaning up the code (and maybe doing some funky pre-processor programming) and implementing more features are welcome -- please let me know so that I can grant you write access to the subversion repository at Sourceforge. Have a great weekend everyone! -- Dean Michael C. Berris Software Engineer, Friendster, Inc. [http://cplusplus-soup.blogspot.com/] [mikhailberis(a)gmail.com] [+63 928 7291459] [+1 408 4049523]

14 85

[review] Review of Exception begins today
by Tobias Schwinger 09 Oct '07

09 Oct '07

The formal review of the Exception library, proposed by Emil Dotchevski, begins today. The library provides an exception class that can transport arbitrary values, thus freeing the user from designing custom exception classes. The library can be downloaded at http://tinyurl.com/24wtwu and its documentation can be read online at http://tinyurl.com/2bkojl . What to include in Review Comments ================================== Your comments may be brief or lengthy, but basically the Review Manager needs your evaluation of the library. If you identify problems along the way, please note if they are minor, serious, or showstoppers. Here are some questions you might want to answer in your review: * What is your evaluation of the design? * What is your evaluation of the implementation? * What is your evaluation of the documentation? * What is your evaluation of the potential usefulness of the library? * Did you try to use the library? With what compiler? Did you have any problems? * How much effort did you put into your evaluation? A glance? A quick reading? In-depth study? * Are you knowledgeable about the problem domain? And finally, every review should answer this question: * Do you think the library should be accepted as a Boost library? Be sure to say this explicitly so that your other comments don't obscure your overall opinion. We're looking forward to your evaluation of this Boost candidate! Tobias Schwinger - Review Manager -

12 31

[serialization] patches to fix DLL support on Windows
by David Deakins 09 Oct '07

09 Oct '07

Currently, there are a small collection of bugs in the trunk version of Boost.Serialization that prevent the libraries from compiling as a Windows DLL. Most of these problems relate to missing dllimport/dllexport directives or, in a couple places, to directives that shouldn't be there. Attached are patches to several files to correct these issues. Thanks, -Dave Index: codecvt_null.cpp =================================================================== --- codecvt_null.cpp (revision 39562) +++ codecvt_null.cpp (working copy) @@ -7,6 +7,7 @@ // License, Version 1.0. (See accompanying file LICENSE_1_0.txt or copy at // http://www.boost.org/LICENSE_1_0.txt) +#define BOOST_ARCHIVE_SOURCE #include <boost/archive/codecvt_null.hpp> // codecvt implementation for passing wchar_t objects to char output Index: codecvt_null.hpp =================================================================== --- codecvt_null.hpp (revision 39562) +++ codecvt_null.hpp (working copy) @@ -20,6 +20,7 @@ #include <cstddef> #include <boost/config.hpp> +#include <boost/archive/detail/auto_link_archive.hpp> namespace std{ #if defined(__LIBCOMO__) @@ -58,7 +59,7 @@ template<> class codecvt_null<wchar_t> : public std::codecvt<wchar_t, char, std::mbstate_t> { - virtual std::codecvt_base::result + virtual BOOST_ARCHIVE_DECL(std::codecvt_base::result) do_out( std::mbstate_t & state, const wchar_t * first1, @@ -68,7 +69,7 @@ char * last2, char * & next2 ) const; - virtual std::codecvt_base::result + virtual BOOST_ARCHIVE_DECL(std::codecvt_base::result) do_in( std::mbstate_t & state, const char * first1, Index: interface_iarchive.hpp =================================================================== --- interface_iarchive.hpp (revision 39562) +++ interface_iarchive.hpp (working copy) @@ -32,7 +32,7 @@ namespace archive { namespace detail { -class BOOST_ARCHIVE_DECL(BOOST_PP_EMPTY()) basic_pointer_iserializer; +class BOOST_ARCHIVE_OR_WARCHIVE_DECL(BOOST_PP_EMPTY()) basic_pointer_iserializer; template<class Archive> class interface_iarchive @@ -51,9 +51,9 @@ } template<class T> - const BOOST_ARCHIVE_DECL(BOOST_PP_EMPTY()) basic_pointer_iserializer * + const basic_pointer_iserializer * register_type(T * = NULL){ - const BOOST_ARCHIVE_DECL(BOOST_PP_EMPTY()) basic_pointer_iserializer & bpis = + const basic_pointer_iserializer & bpis = pointer_iserializer<Archive, T>::get_instance(); this->This()->register_basic_serializer(bpis.get_basic_serializer()); return & bpis; Index: interface_oarchive.hpp =================================================================== --- interface_oarchive.hpp (revision 39562) +++ interface_oarchive.hpp (working copy) @@ -32,7 +32,7 @@ namespace archive { namespace detail { -class BOOST_ARCHIVE_DECL(BOOST_PP_EMPTY()) basic_pointer_oserializer; +class BOOST_ARCHIVE_OR_WARCHIVE_DECL(BOOST_PP_EMPTY()) basic_pointer_oserializer; template<class Archive> class interface_oarchive @@ -51,9 +51,9 @@ } template<class T> - const BOOST_ARCHIVE_DECL(BOOST_PP_EMPTY()) basic_pointer_oserializer * + const basic_pointer_oserializer * register_type(const T * = NULL){ - const BOOST_ARCHIVE_DECL(BOOST_PP_EMPTY()) basic_pointer_oserializer & bpos = + const basic_pointer_oserializer & bpos = pointer_oserializer<Archive, T>::get_instance(); this->This()->register_basic_serializer(bpos.get_basic_serializer()); return & bpos; Index: basic_oarchive.hpp =================================================================== --- basic_oarchive.hpp (revision 39562) +++ basic_oarchive.hpp (working copy) @@ -71,16 +71,15 @@ public: // note: NOT part of the public interface void register_basic_serializer( - const BOOST_ARCHIVE_DECL(BOOST_PP_EMPTY()) basic_oserializer & bos + const basic_oserializer & bos ); void save_object( const void *x, - const BOOST_ARCHIVE_DECL(BOOST_PP_EMPTY()) basic_oserializer & bos + const basic_oserializer & bos ); void save_pointer( const void * t, - const BOOST_ARCHIVE_DECL(BOOST_PP_EMPTY()) - basic_pointer_oserializer * bpos_ptr + const basic_pointer_oserializer * bpos_ptr ); void save_null_pointer(){ vsave(NULL_POINTER_TAG);

3 3

GTL - geometric template library - determining interest
by Suto, Gyuszi 08 Oct '07

08 Oct '07

> Hello, > > I am trying to determine interest to submit GTL to boost. > > History/Background > ================== > GTL is a geometric library that implements basic rectilinear, fixed > point 1D, 2D and 3D types. It was developed over the past decade > inside Intel's own EDA CAD department mainly to support advanced > physical design tools that create/check/manipulate the massive layout > that goes into our microprocessors. GTL comes from a codestream that > successfully weathered through several major microprocessor tapeouts. > The management agreed to pursue the open-sourcing of GTL via boost > (with the boost license) - with all the obvious benefits of doing so. > Comparison to other geometric libraries ============================= We are aware of the various other libraries available. What GTL brings to the table: * parametrized fixed-precision cartesian coordinates * industrial strength code base * directly usable on any user type via template traits - based on C++ concepts * massive capacity * bone-crushing speed * isotropic API * ease of use > Implemented Rectilinear Types > ========================================= > 1D Types: Interval > 2D Types: Point, Segment, Rectangle, Polygon, PolygonSet > 3D Types: Point3D, Segment3D, LayeredRectangle, RectangularPrism > Polygons ======== This is by far the most algorithmically advanced type and functionality that we have. 1. full set of boolean operations on polygon sets (or, and, subtract, xor, etc) 2. runtime (all n*log(n) or better) - it is at par or better than other implementations that we're aware of 3. ease of use - simple, intuitive API functions 4. no memory management required by user 5. providing polygon set type that's complete 6. isotropic API // example 1 // construct default empty polygons sets that will be rectangularized // in the given orientation (on demand) gtl::PolygonSet a(VERTICAL), b(HORIZONTAL), c(VERTICAL); a += gtl::Rectangle(4, 5, 60, 70); // add a rectangle to polygon set a a += gtl::Rectangle(gtl::Interval(20, 30), gtl::Interval(40, 100)); // construct a rectangle from 2 intervals, add it to a // .. similar additions to b and c // intersect a with b (with a boolean and) - subtract from it a rectangle, // bloat the north edges of the result by 55 units c += ((a * b) - gtl::Rectangle(10, 10, 2000, 3000)).bloat(NORTH, 55); std::vector<gtl::Rectangle> v; c.get(v); // populate v with the vertical rectangles that make up c > Isotropy > ======== > A variety of directional types in 1D, 2D, 3D with states like: LOW, > HIGH, NORTH, HORIZONTAL, UP, etc > A set of operations on these types like: forward(), backward(), > toward(), left(), turn(), perpendicular(), etc. > > All API functions are isotropic, i.e. they take arguments of > directions/orientations. None of the function names contain words like > X, Y, Up, deltaX, horizontal, etc. With isotropy, you can do elegant > things like: > > // example 2 > gtl::Rectangle a, b; > > // bloat rectangle of a toward rectangle b by b's half delta in that > orientation > // do nothing if no trivial direction from a to b exists > a.bloatInDirection(a.toward(b), b.delta(a.toward(b))/2); > > Writing this example in a non-isotropic fashion requires much more > lines of code, lots of if statements, four to eight different > scenarios, etc. Much more code, much less readable, not flexible at > all. > > Functionality > ============= > GTL has pretty much all the functionality that one would expect from > these types. You can get/set components, you can do booleans (ands, > ors) subtractions, bloats, shrinks. You can construct a rectangle out > of 2 points, 2 intervals, 4 coordinates, etc. You can construct a > polygon set from n rectangles, from a polgyon or a polygon set. You > can get the polygon as a set of rectangles (rectangularized > horizontally or vertically), etc. > > // example 3 > gtl::Rectangle a; > gtl::Segment s = a.get(EAST); // returns the right (vertical) edge of > the rectangle as a 2D segment. > // get the north edge of rectangle a as a segment > // get generalized intersection with segment s - as a rectangle > // bloat the rectangle's EAST side by 5 > // get the center of that rectangle as a point > a.get(NORTH).getGeneralizedIntersection(s).bloat(EAST, 5).getCenter(); > > > Data decoupling via template specialization > =========================================== > GTL can operate on any user data without the need for copying. User > will need to write a tiny, template specialization interface to his > data, that makes GTL interpret user data as the GTL type of interest. > This makes the use of GTL in existing applications trivial. > > // example 4 > class UserData{ > int a, b, c; > int x, y, z; > }; > > // if user wants gtl to interpret a, c, x, z > // as the coordinates of a rectangle, he will write > #include <Gtl.h> > template <> > class gtl::RectangleInterface<UserData> { > // need to write 3 functions only - get(), set(), create() > }; > > typedef gtl::RectangleImpl<UserData> Rectangle; > Rectangle r1(10, 20, 30, 40); > std::cout << r1.get(gtl::SOUTH) << std::endl; // prints 20 - y low > coordinate > > > David Abrahams suggested to write this description as a brief email. I > just realized that I'm past 2 pages already. There's much more to say > about GTL. Will do that when/if appropriate. We're eager to get > feedback from you. > thanks, > Gyuszi Suto > Intel, Hillsboro, Oregon >

6 12

Re: [boost] boost::exception questions
by Tom Brinkman 08 Oct '07

08 Oct '07

> 3) Support for linking multiple error tags in a single expression > might be useful and help in standarizing errors throughout an application. > > throw boost:::exception() << > boost::error_info<tag_errorno,tag_filename,tag_size,tag_width>( > (1,"output.txt",100,200); >> Could you clarify what you mean? Well, I could do something like this: typedef boost::error_info<tag_errorno, tag_filename,tag_size,tag_width> error_t; throw error_t(1,"output.txt",100,200); If this error was common throughtout an application, this typedef would make the code more readable. Many boost components support variable number of template arguments. It would be trivial to implement I think. You could even default the template arguments, to shorten the expression even further, such as: typedef boost::standard_error<> standard_error_t; throw standard_error_t(); You could do this instead of the "ugly" macros that you have for the "_LINE_", "_FILE_" and "_FUNCTION_". >> Usage of the stream operator (<<) for data insertion. I like using (<<) for data insertion and see no reason to remove it.

6 27

GTL - geometric template library - determining interest
by Tom Brinkman 08 Oct '07

08 Oct '07

Count me as very interested. This is a needed library and I would be interested in making shur that it is compatible and usable with boost::gil. (the graphics library)

10 27

[thread]tss.cpp
by Sean Huang 05 Oct '07

05 Oct '07

Shouldn't the fix for ticket #906 on 1_34 branch be merged to trunk? The details are here: http://lists.boost.org/Archives/boost/2007/04/120128.php The trunk version of thread library is causing our application to crash. Regards, Sean

2 1