- Boost - lists.boost.org

[GTL] clipping and merge of general polygons with attributes
by Simonson, Lucanus J 08 Jun '08

08 Jun '08

I am currently porting pre-existing internal code for performing scanline based merge of arbitrary-angle planar polygons into GTL. The algorithm carries generic property values associated with the input polygons through to the output. That means that if polygon A has property X and polygon B has property Y the output of merge would be potentially three types of polygons, those with property X, those with property Y and those with property {X, Y}. This is essentially the 2D version of the interval set operations proposed by Joachim Faulhaber. Obviously, it can be used as the foundation for general Boolean operations: e.g. the intersection between all polygons with property X and all polygons with property Y is simply the portion of the output with property {X, Y}. I wanted to ask Bruno and Barend to comment on whether they think this algorithm would be useful and solicit the boost community in general to comment on my progress designing the interfaces to it. I looked at Barend's library and could only find rectangle clipping, did I miss it, or is a comparable capability not provided by Barend's geometry library? I also looked at the documentation for Mateusz Loskot's geos library, but was only able to find linestring intersection algorithms, and the geometry container and polygon container types didn't obviously support Boolean operations, though I could have missed it. I would have expected that it would. I have added arbitrary angle polygon data types and concepts to GTL to support the API the algorithm will provide. These are different from those proposed by Barend, though the concepts should be compatible with his data types. My concepts for polygons center around the idea that they should be able to provide iterator range semantics for getting and setting their contents. I have concepts for the following struct polygon_90_concept {...}; struct polygon_90_with_holes_concept : polygon_90_concept {...}; struct polygon_45_concept : polygon_90_concept {...}; struct polygon_45_with_holes_concept : virtual polygon_45_concept, polygon_90_with_holes_concept {...}; struct polygon_concept : polygon_45_concept {...}; struct polygon_with_holes_concept : virtual polygon_concept, polygon_45_with_holes_concept {...}; A polygon_90 is a polygon that is restricted to axis-parallel edges, and has angles that are all multiple of 90-degrees. A polygon_45 is a polygon that has angles that are all multiple of 45-degrees. A polygon is a polygon with arbitrary angles. The concepts inherit from each other to share some implementation, such as the holes, and to allow some measure of polymorphism of polygon types. For instance, the result of a Boolean operation on 90-degree geometry could be stored to arbitrary angle polygons at the output with the same generic function call as would be used to store to 90-degree polygons because an arbitrary angle polygon can represent 90-degree angle data. The high level overview of the API proposal is that generic free functions detect the conceptual type of geometry objects that are called on and redirect the call to the function of the same name defined within the appropriate geometry concept, sometimes with tag dispatching to select between different versions of the function within the concept. For example contains: template <typename geometry_type_1, typename geometry_type_2> bool contains(const geometry_type_1& geometry_object, const geometry_type_2& contained_geometry_object, bool consider_touch = true) { return geometry_concept<geometry_type_1>::type::contains(geometry_object, contained_geometry_object, consider_touch, typename geometry_concept<geometry_type_2>::type()); } might be called on a rectangle and a point, a polygon and a rectangle, or any other sensible combination of geometry objects, provided that the associated concept structs define the algorithm required conforming to the syntax expected. For example, the rectangle contains point function is defined as follows: template <typename rectangle_type, typename point_type> static bool contains(const rectangle_type& rectangle, const point_type point_contained, bool consider_touch, point_concept tag) { return interval_concept::contains(get<HORIZONTAL>(rectangle), point_concept::get<HORIZONTAL>(point_contained), consider_touch, no_type()) && interval_concept::contains(get<VERTICAL>(rectangle), point_concept::get<VERTICAL>(point_contained), consider_touch, no_type()); } This indirection leads to some welcome benefits to usability. It leads to very simple and straightforward syntax errors in incorrectly formed user code, for instance, say the user calls vertical(user_point_object), which shouldn't work because vertical expects a rectangle or prism, the compiler generates the fairly readable error: gtl.hpp: In function typename component_type<geometry_type>::type vertical(const geometry_type&) [with geometry_type = point_data<int>]: main.cpp:14: instantiated from here gtl.hpp:125: error: vertical is not a member of point_concept , telling the user only where their mistake was (main.cpp:14) and what is wrong (vertical is not a member of point_concept), which is exactly the information the user needs to fix their error and not more. Other syntax errors may result in substitution failure such as if the user calls center(user_point_object), which shouldn't work because a point doesn't have a center, the compiler generates a substitution failure error instead: main.cpp:14: instantiated from here post_geometry_traits_definitions.hpp:24: error: no type named center_type in struct point_concept::registration<point_data<int> > main.cpp: In function void foo(): main.cpp:14: error: no matching function for call to center(point_data<int>&) main.cpp: In function bool testRectangle(): , informing the user that point doesn't provide a center_type and giving them the very clear error that there is no function center() which takes their data type. In the case that the user has not registered their type with the library the error will look like: ... gtl.hpp:125: error: <function name> is not a member of no_type I could change the name of no_type to undefined_concept to make it a little more obvious what is going on. I am currently considering adding a coordinate_concept and coordinate_traits to the library because for 32-bit integer we would like to use 64-bit integer for area types and double for Euclidean distance, but for floating point coordinates we would just use the coordinate type for those. With the need for numerical robustness of arbitrary geometry algorithms looming the use of more advanced coordinate data types looks likely, which might necessitate traits. As always, I welcome any feedback that will help me improve the library and make it conform to boost standards/expectations for eventual review when I have completed the re-write. You can find the up-to-date re-write of the library in sandbox/gtl. Thanks, Luke

2 2

A few questions about Phoenix, Boost.Bind, and FC++
by Daniel Walker 08 Jun '08

08 Jun '08

Hello, With all the recent discussion about Functional Programming, I thought I'd take a closer look at some of the FP libraries that I haven't really used before, and I started last night by browsing through Phoenix's documentation. This led me to a few questions: Does Phoenix allow side-effects or is it "pure" functional like Fusion and FC++? Does it allow modification of arguments by reference - either builtin references or reference_wrapper? What is the status of the Phoenix msvc port? The documentation seems to indicate that it's possible but not necessarily forthcoming. Is there any immediate plan to make Phoenix interoperable with the coming standard library's std::bind, std::placeholders, std::is_bind_expression, and std::is_placeholder? Regarding Boost.Bind, will it eventually support is_bind_expression? I mean will it treat types for which is_bind_expression is true as full-blown bind sub-expressions? (I know it's a matter of time and work and testing to get this, and I'd be willing to help out, write test cases, whatever's needed.) Also, Peter, weren't you thinking of proposing operator overloads for bind expressions in C++0x? I think you have some already implemented in Boost.Bind. Do you think operator overloads are likely to make it into the final draft? Finally, I noticed the Phoenix documentation cites BLL and FC++ as major influences. I'm fairly familiar with BLL (with its implementation and usage, rather than its history) but not at all familiar with FC++. I hope at least to skim through the documentation over the next few days. However, one thing I noticed right away while reading about Phoenix was that it borrows the term rank-2 polymorphic function from FC++. I'm just learning this terminology, so I'm trying to gain confidence that I understand it. From briefly skimming (McNamara, 2000) in JFP, I'm under the impression that a rank-2 polymorphic function can only have two parametric types, i.e. two template parameters. So, for example, std::make_pair is rank-2 polymorphic, and FC++ has functions that will produce pairs when called with two different types. A rank-n polymorphic function can have arbitrarily many different template parameters; an example would be std::make_tuple. Doesn't Phoenix actually support rank-n polymorphism? For example, isn't the following a rank-3 polymorphic function in Phoenix and couldn't you write similar function objects for higher ranks? struct tupler_ { template<class> struct result; template<class F, class T0, class T1, class T2> struct result<F(T0,T1,T2)> { typedef tuple<T0,T1,T2> type; }; template<class T0, class T1, class T2> tuple<T0,T1,T2> operator()(T0 t0, T1 t1, T2 t2) const { return make_tuple(t0,t1,t2); } }; phoenix::function<tupler_> tupler; One last thing - I noticed that FC++ was submitted for inclusion in Boost a few years back. What ever happened with that? Thanks in advance! Daniel Walker

7 17

Property Tree Library status?
by Jonathan Biggar 08 Jun '08

08 Jun '08

Is this finally going to make it into a release? 1.36? -- Jon Biggar Floorboard Software jon(a)floorboard.com jon(a)biggar.org

3 4

Multisignature function v1.2.2
by Marco Costalba 08 Jun '08

08 Jun '08

Hi all, I have upload in Vault the file msf-1.2.2.zip with a new version of multi signature boost::function extension New in this version is a workaround for a rare compile error in MSVC due to a bug in the compiler that requires a using::operator() declaration also in a class where there are no other operator() defined ! I have also added in the examples a runtime object factory, i.e. where the key to query the factory for an object of a chosen class is a runtime variable, not a compile time constant or something similar. Factory allows to pass any number and type of arguments to ctor of the chosen class. Functionality is similar to factory_24_2_08.zip already in Vault, but this time I've used all the arsenal of boost, namely: fusion, switch (in sandbox, the Vault version is broken), mpl and of course the multi signature function (MSF) that is the core of the factory. Due to this I think the implementation is the most minimal, clean and simple that I know. A peculiarity of this implementation is that MSF uses its polymorphic function object support to bind c'tors wrappers in a naturally and very clean way. This is a good example of how it is possible to take advantage of polymorphic function support in real code. Thanks Marco

1 0

[property tree] code conversion
by Johan Råde 07 Jun '08

07 Jun '08

The rapid xml parser used by the property tree reads the input stream using stream buffer iterators. This means that if the stream has been imbued with a locale with a code conversion facet, then the code conversion facet is never invoked. It may be better if the stream were read using stream iterators. --Johan Råde

1 0

[future] Early draft of wait for multiple futures interface
by Johan Torp 07 Jun '08

07 Jun '08

We've been discussing the need to implement a mechanism to wait for multiple futures in a separate thread: www.nabble.com/Review-Request%3A-future-library-%28Gaskill-version%29-to166… I've come up with some interfaces which I find intuitive and useful. I've never implemented thread waiting, so please let me know if you think something like this is viable. ------------------------------ Proposal ------------------------------ A future can be constructed and thereafter wait on four different "future conditions" * a promise * a future_switch * a future_barrier * another future Each condition has a specified return type and the futures you create from it must match this type. They all have the same possible states - isn't ready, has value or an expression. I have left these and alot of other details out of the interface below for conciseness. ------------------------------ Interface drafts ------------------------------ /// Future condition which is ready when any of the added conditions is ready. Has an arbitrary return-type template<class ReturnType> class future_switch { public: /// Direct return template<class FutureConditionWithMatchingReturnType> void add_case(FutureConditionWithMatchingReturnType f); /// Possibility to perform custom functor, bind state, perform some logic etc before fulfilling it's condition template<class FutureCondition, class FutureTypeToReturnTypeFunctor> void add_case(FutureCondition f, FutureTypeToReturnTypeFunctor case); /// Only valid in is_ready state. Removes last fulfilled futurecondition and enables new futures to be /// constructed. Existing futures will have copied the value or exception already and will still work. void remove_ready_case(); bool empty() const; }; /// Future condition which is ready when all added futures are. /// This interface is less promising and has some flaws. Maybe you can get inspired by it though. template<class ReturnType> class future_barrier { public: future_barrier(const function<ReturnType()>& onReady); template<class FutureCondition> void add_condition(const future<FutureType>& f); }; ------------------------------ Example usage ------------------------------ template<class T> future_switch<T> operator||(const future<T>& lhs, const future<T>& rhs) { future_switch<T> sw; sw.add_case(lhs); sw.add_case(rhs); return sw; } template<class T> T and_impl(const future<T>& lhs, const future<T>& rhs) { return lhs.get() && rhs.get(); } template<class T> future_barrier<T> operator&&(const future<T>& lhs, const future<T>& rhs) { // Rather large runtime insecurity, we might forget to add lhs and rhs as conditions to the barrier future_barrier b(bind(&and_impl, lhs, rhs)); b.add_condition(lhs); b.add_condition(rhs); return b; } // This is an experimental use case for using switch as a dynamic set of future conditions // It handles three future responses and calls the three functions on the next lines bool handle_response_a(ResponseA r); bool handle_response_b(ResponseB r); bool handle_response_c(ResponseC r); void handle_pending_requests(const future<ResponseA>& a, const future<ResponseB >& b, const future<ResponseC >& c) { future_switch<void> sw; sw.add_case(a, &handle_repsonse_a); sw.add_case(b, &handle_repsonse_b); sw.add_case(c, &handle_repsonse_c); bool all_ok = true; while (!sw.empty()) { // Will automatically remove ok:ed futures from sw future<bool> next_response_was_ok(sw); bool all_ok = all_ok && next_response_was_ok.get(); sw.remove_ready_case(); } return all_ok; } ------------------------------ Some comments ------------------------------ There is a lot to improve here. I'd appreciate it if we could focus on determining whether this is a viable solution and the way we want to go before diving into details. These abstractions has the following property: A Users can compose conditions and poll them without the need of waiting. B We do not need to spawn extra threads for waiting - we only wait on the "outmost" future C Threads needn't awake and poll readiness - assuming the and/or logic is handled by waitingcode. D No "user logic" from the future-blocking threads propagate to the promise-fulfilling thread. E It's possible to implement efficient laziness by keeping readiness/waiting logic internal in the future library "wait for all" can be implemented without adding future_barrier, by simply calling wait() on all futures. We lose property A and E for "wait for all" if we do it this way. The blocking thread will awake unnecessarily many times. Property C means promise-fullfilling threads need to do some basic and/or logic. I think this can be implemented in a safe and efficient manner, O(log(N)) for barrier/all and O(1) for switch/any. I also think it is much preferable to waking and switching to future-blocking threads which re-check readiness conditions. Note property D. Whatever mechanism we choose I think it's desirable to be able to easily "lift" existing functions to futures; R foo(A1 a1, A2 a2, A3 a3) should be easily rewritable as; future<R> foo(future<A1> a1, A2 a2, future<A3> a3) // Some parameters need not be lifted Johan -- View this message in context: http://www.nabble.com/-future--Early-draft-of-wait-for-multiple-futures-int… Sent from the Boost - Dev mailing list archive at Nabble.com.

8 43

Polymorphic function (was: Multi signature boost::function v1.0)
by Marco Costalba 07 Jun '08

07 Jun '08

On Sat, May 31, 2008 at 8:23 AM, Marco Costalba <mcostalba(a)gmail.com> wrote: > >> Sorry for the delay. I just put it on vault. > > I'm just back after a week off-line due to my job. This is a great > news, I'm going to download right now. > > More to come... > Hi Daniel, I have downloaded and tested Function Objects/polymorphic_function.zip from boost vault. Very nice stuff! really! a lot of new tricks to learn ;-) I have immediately replaced boost::function with boost::functional::polymorphic_function in msf-1.2 (also under vault, but in base directory) and gave it a spin. Unfortunately I was not able to make it work. Some boost::function API, necessary for msf-1.2, are not supported: operator==(), empty(), clear(), contains() I said, ok not a biggie, I can just use polymorphic_function::target() and build something similar myself. But what stopped me is that target() does not seem to work. int foo1(char) { return -1; } boost::functional::polymorphic_function<int(char)> poly_fun(foo1); poly_fun.target(); // compile error here ! Under gcc 4.2.3 I have test.cpp: In function 'int main(int, char**)': test.cpp:88: error: no matching function for call to 'boost::functional::polymorphic_function<int ()(char), false>::target()' I have checked the code and especially the SFINAE conditions in RANK_N_ACCESSOR, but I failed to understand why it doesn't work. Thanks Marco

2 3

Trac open bugs - by assignee
by Marshall Clow 07 Jun '08

07 Jun '08

[ 313 open bugs today, 313 yesterday ] [ I will be on vacaion next week, so the next report will be Monday the 16th..... ] 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 34 djowel 28 az_sw_dude 27 dgregor 24 grafik 21 dave 18 bemandawes 15 ramey 15 agurtovoy 13 vladimir_prus 12 no-maintainer 11 jsiek 9 rogeeff 9 nesotto 5 kaalus 5 igaztanaga 5 danieljames 5 anthonyw 5 None 4 witt 4 pavol_droba 4 ebf 3 turkanis 3 samuel_krempp 3 nasonov 3 johnmaddock 3 danielw 2 troyer 2 shammah 2 marshall 2 jmaurer 2 hkaiser 2 gmelquio 2 garcia 1 urzuga 1 troy 1 t_schwinger 1 speedsnail 1 matias 1 jano_gaspar 1 guwi17 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 1907 name of library files on mingw None 1927 MacOS (Darwin) should use the -headerpad_max_install_name option None 1990 xpressive: passing temporary regex to sregex_token_iterator causes runtime assertion None 1994 headers out of order somewhere in program_options/function/functional 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 1900 Missing documentation for mpl::print in the MPL library agurtovoy 1901 Missing documentation for mpl::for_each in the MPL library agurtovoy 1916 [mpl] MPL_HAS_XXX_TRAIT_DEF bug in MSVC71 agurtovoy 1992 boost::mpl::zip_view does not support use as a metafunction with ::type agurtovoy 588 mpl::remove compile error with gcc 4.1.0 anthonyw 1154 tss destruction segfaults in conjunction with dlopen/dlclose anthonyw 1470 Boost.Thread: Compilation errors with non-__cdecl calling convention 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) 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 1933 special_values not found when compiling date_time/time.hpp az_sw_dude 1934 iterator reference zero when reading time zone [with patch] 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 1840 name check functions have different behavior wrt empty string bemandawes 1876 portable_file_name() returns true for '.' and '..' bemandawes 1962 Doesn't measure wall clock time bemandawes 1971 remove_all is not documented bemandawes 1972 boost::filesystem::remove() throws on self referenced symlinks 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 1923 Unordered move implementation doesn't work in Borland. 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 danielw 1966 Need VC8 workaround 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 1931 Boost.Python headers won't compile with GCC 4.3 dave 1952 The operation static_cast<std::string>(boost::python::extract<std::string>(...)) crashes Python. Seems to create reference counting problem. 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 1943 (minor) configuring with header-only libraries. dgregor 1945 Update CMake configuration introduction for CMake 2.6.0 dgregor 1986 Missing IncidenceGraph requirement in topological_sort docs 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 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 djowel 1920 lexical_cast with tuple target fails_ because of cleared skipws flag djowel 1953 spirit doesn't use quickbook proper 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 gmelquio 1944 Interval library pow function doesn't work with mpq_class and similar 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 1930 The userman.pdf boost-build documentation is outdated grafik 1940 broken links 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 guwi17 1974 ambiguous call to ref in vector_of_vector.hpp when using bind.hpp 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 1975 windows_shared_memory implicitly commits virtual memory 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 1451 error: use of C99 long long integer constant johnmaddock 1988 Boost.Config macros badly added. 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 kaalus 1955 gcc-4.x and gcc-4.3 fixes 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 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 ramey 1941 polymorphic archive interface doesn't match other archive interfaces ramey 1942 Pointers to elements in a std::map are not serilaized correctly ramey 1954 gcc-4.3 doesn't compile collection_traits.hpp ramey 1973 [gcc43] Backport trunk fixes into release branch 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 troy 1981 tests when ceratain build variants turned off 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 1579 gzip compressor should model DualUseFilter turkanis 1649 Fix definition of JavaScript menu to avoid long chains of functions turkanis 1656 Consider implementing flush() for symmetric filters urzuga 574 [boost::lambda] Compile error with libstdc++ debug mode vladimir_prus 1132 zero_tokens clarification 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 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 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 1967 bjam bug? iostreams + zlib won't build for VC8 or MinGW with small hack to Jamfile.v2 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

shared_ptr - system specific timing tests
by Sid Sacek 07 Jun '08

07 Jun '08

boost::shared_ptr<> uses a locking mechanism when copies of a variable are made in order to increment the counter correctly in a multi-threaded application. For example: int main( int, char ** ) { boost::shared_ptr< ABC > sp1( new ABC ); for ( int i = 0; i < 1000000; ++i ) { boost::shared_ptr< ABC > sp2 = sp1; } return 0; } I would like to know if there are any platform-specific timing tests that have been performed where operational speed results have been recorded. I want to know what kind of performance I should expect to achieve on different operating systems upon duplication and destruction of shared pointers. Thanks, -Sid Sacek

1 0

Updated version of futures library
by Anthony Williams 06 Jun '08

06 Jun '08

Hi all, I've updated my futures library to include wait_for_any() and wait_for_all(). The provided overloads allow either waiting on up to five futures known at compile time: unique_future<int> f1; shared_future<std::string> f2; unique_future<double> f3; unsigned const ready_index=wait_for_any(future1,future2,future3); or on a container of futures: std::vector<jss::shared_future<int> > futures; std::vector<jss::shared_future<int> >::iterator const future= jss::wait_for_any(futures.begin(),futures.end()); In the first instance, they can be of distinct types, but in the latter, all the futures in the container must be of the same type. The documentation is available at http://www.justsoftwaresolutions.co.uk/files/futures_documentation.html and the files and tests are available at http://www.justsoftwaresolutions.co.uk/files/n2561_futures_revised_20080530… Anthony -- Anthony Williams | Just Software Solutions Ltd Custom Software Development | http://www.justsoftwaresolutions.co.uk Registered in England, Company Number 5478976. Registered Office: 15 Carrallack Mews, St Just, Cornwall, TR19 7UL

9 49