- Boost - lists.preview.boost.org

[accumulators] serialization support
by Zoran Angelov 22 Nov '10

22 Nov '10

Hi, Have anyone considered for boost.accumulators having a serialization support? It will be helpful for example in situations where data is being accumulated/sampled on long time intervals, and persistence of boost.accumulators objects is impossible. Something like this: boost/accumulators/statistics/count.hpp: . . . template<typename Sample, typename Tag> struct immediate_mean_impl : accumulator_base { // for boost::result_of typedef typename numeric::functional::average<Sample, std::size_t>::result_type result_type; template<typename Args> immediate_mean_impl(Args const &args) : mean(numeric::average(args[sample | Sample()], numeric::one<std::size_t>::value)) { } template<typename Args> void operator ()(Args const &args) { std::size_t cnt = count(args); this->mean = numeric::average( (this->mean * (cnt - 1)) + args[parameter::keyword<Tag>::get()] , cnt ); } result_type result(dont_care) const { return this->mean; } template <typename Archive> void serialize(Archive &ar, const unsigned int version) { ar & BOOST_SERIALIZATION_NVP(mean); } private: result_type mean; }; . . . The problem is that members, storing the state are private. Thanks

2 2

[1.45][signals2] Can't build PDF docs?
by John Maddock 21 Nov '10

21 Nov '10

I'm trying to build the signals2 docs for the PDF doc distribution, but I'm failing with: warning: failed to load external entity "hello_world_def_code_snippet.xml" tutorial.xml:50: element include: XInclude error : could not load hello_world_def_code_snippet.xml, and no fallback was found warning: failed to load external entity "hello_world_single_code_snippet.xml" tutorial.xml:52: element include: XInclude error : could not load hello_world_single_code_snippet.xml, and no fallback was found warning: failed to load external entity "hello_def_code_snippet.xml" tutorial.xml:63: element include: XInclude error : could not load hello_def_code_snippet.xml, and no fallback was found etc... I can see that process_snippets.exe is being invoked, but I can't find the output xml files anywhere. This occurs if I either build from within the doc/pdf directory, or the libs/signals2/doc directory. Any ideas? Thanks, John.

3 6

[1.45] Beta version of PDF docs available.
by John Maddock 21 Nov '10

21 Nov '10

There's a beta build of the PDF docs for 1.45 here: http://sourceforge.net/projects/boost/files/boost-docs/1.45.0/boost_1_45_pd… If library authors could check for the usual snafu's, and I'll build the final versions in a few days. Regards, John.

3 2

[Guild] Recruiting & Instructions, rough first draft
by Jim Bell 20 Nov '10

20 Nov '10

Here's some writing I threw down a little while ago. Please comment, here or privately. Copy my text for reference. It's on my website partly because I've done some formatting (emphasizing), as you'll see. It's rough, and lacks some crucial detail. http://jc-bell.com/contributions/boost-guild/boost-guild-recruit http://jc-bell.com/contributions/boost-guild/boost-ticket-handling http://jc-bell.com/contributions/boost-guild/boost-regression-troubleshooti… Cheers! -Jim

4 6

Boost 1.45.0 Release Notice
by Beman Dawes 20 Nov '10

20 Nov '10

Release 1.45.0 of the Boost C++ Libraries is now available. These open-source libraries work well with the C++ Standard Library, and are usable across a broad spectrum of applications. The Boost license encourages both commercial and non-commercial use. This release contains numerous enhancements and bug fixes for existing libraries. For details, see http://www.boost.org/users/news/version_1_45_0 The release can be downloaded directly from SourceForge. See http://sourceforge.net/projects/boost/files/boost/1.45.0/ To install this release on your system, see http://www.boost.org/doc/libs/release/more/getting_started/index.html Thanks, --The Boost release team Beman Dawes Daniel James Eric Niebler Rene Rivera Vladimir Prus

1 0

[1.45.0] Release candidates available
by Beman Dawes 19 Nov '10

19 Nov '10

See http://boost.cowic.de/rc/ Please download the file for your favorite platform, try a build, and let us know if it works OK. We like some independent confirmation before pushing the files up to SourceForge. Thanks, --Beman

13 20

The cpp-netlib Release 0.8 is Out Now!
by Dean Michael Berris 19 Nov '10

19 Nov '10

Hi Everyone, advanced apologies for the cross-post. To those interested and watching the cpp-netlib project's progress, this afternoon Philippine time I just packaged and released the latest installment of the cpp-netlib project. Release 0.8 features: * An asynchronous HTTP server template, supporting asynchronous handler invocation and asynchronous writing to the established HTTP connection on the handler side. An example of one use for this is included in the library which implements a simple static web server, benchmarked with Apache AB on a dual core Intel Core 2 CPU with 2GB RAM to be able to serve a 10kb file at 4700 requests per second on 64-bit Linux 2.6.36. You can find out more about the example here: http://goo.gl/5mVuY * More in-depth documentation covering the HTTP Client and Server APIs, now hosted online as well. Read the documentation at http://cpp-netlib.github.com/0.8/ * A simple thread pool implementation that uses Boost.Asio underneath, with a simple API for posting nullary function objects as tasks. The number of threads to run is configurable as a constructor parameter -- this is especially required by the asynchronous HTTP server template, where handlers are queued to be executed. The library is released under the Boost Software License, and is being developed for future submission to the Boost C++ Library. You can download the latest and previous releases from http://github.com/cpp-netlib/cpp-netlib/downloads. Have a great day everyone and I look forward to your very valuable feedback! -- Dean Michael Berris deanberris.com

1 0

Boost bug sprint?
by Marshall Clow 19 Nov '10

19 Nov '10

Since we're now at November 13th, and I originally proposed starting the bug sprint "after the 1.45" release, and "On November 15th", I think that something's gotta give. So, I'm proposing that we start the bug sprint on Saturday, November 27th, and run through Sunday, December 5th (9 days, two weekends, one work week). That way people who work on boost as part of their day jobs will have a full week to participate, while those who do "nights and weekends" will have plenty of time as well. What does everyone think? -- Marshall

12 26

LLVM license compatibility with BSL
by vicente.botet 19 Nov '10

19 Nov '10

Hi, I have found quite useful to adapt the test for llvm/libc++ ratio/chrono to test Boost.Ratio and Boost.Chrono. But Anthony has signaled me that maybe there is a compatibility problem with the license included in these files. //===----------------------------------------------------------------------===// // // The LLVM Compiler Infrastructure // // This file is distributed under the University of Illinois Open Source // License. See LICENSE.TXT for details. // //===----------------------------------------------------------------------===// Is the LLVM License (http://llvm.org/docs/DeveloperPolicy.html#license) compatible with the Boost Software License? Can we include files with this comment on a Boost library? Best, _____________________ Vicente Juan Botet Escribá http://viboes.blogspot.com/

11 22

What's so cool about Boost.MPI?
by David Abrahams 18 Nov '10

18 Nov '10

Just wanted to call some attention to this article I wrote about Boost.MPI: http://daveabrahams.com/2010/09/03/whats-so-cool-about-boost-mpi/ I think it might be useful to link that from the Boost.MPI docs, too. -- Dave Abrahams BoostPro Computing http://www.boostpro.com

2 2

[Probing interest] -- automatization of writing predicates.
by Petr Pilař 18 Nov '10

18 Nov '10

Hi folks, I often find myself in a situation where I need a simple comparison predicate for filtering, look-up, etc. Writing such predicates can get tedious over time and adds unnecessary "bloat", especially when you use the predicate only once. For that reason I have automated this process and I'm interested whether others might find it useful as well. Usage example: auto_predicate(&ClassName::getter, compareWithMe) -- this returns functor which compares the returned value with compareWithMe using == operator. auto_predicate(&ClassName::getter, compareWithMe, comparator) -- this returns functor which compares the returned value with compareWithMe using the given comparator. (Note: getter return type does not have to match compareWithMe type have you supplied comparator with proper signature.) Best regards, Petr Pilař.

3 3

Boost.FileSystem dependency on Boost.System
by Matthew Gwynne 18 Nov '10

18 Nov '10

Hi, It seems when compiling anything using Boost.FileSystem that the Boost.System library is also linked. Is this always the case? I can't see any clear documentation of this on the Boost.FileSystem page. If this is the case, is there a nice list of all such dependencies somewhere, as this is currently causing us certain issues? Thanks! Matthew Gwynne http://cs.swan.ac.uk/~csmg/

1 0

for_each abstraction
by Karsten Ahnert 18 Nov '10

18 Nov '10

Hi, I need something like an abstraction layer for iterations over some range. Consider for example the following three statements, which all do the same, but the loop inside each for_each is different: // thrust is an STL-like interface for CUDA [1] thrust::device_vector< double > a1( 3 ); thrust::for_each( a1.begin() , a1.end() , op() ); std::vector< double > a2( 3 ); __gnu_parallel::for_each( a2.begin() , a2.end() , op() ); std::vector< double > a3( 3 ); std::for_each( a3.begin() , a3.end() , op() ); //maybe even fusion::vector< double , double , double > a4; fusion::for_each( a4 , op() ); Is there a way or some part of a boost-library which handles the above three statements in a unique manner? I want to write algorithms which are independent of the specific for_each implementation. Best regards, Karsten [1] http://code.google.com/p/thrust/

5 13

[config] macro for unified initialization syntax?
by Eric Niebler 17 Nov '10

17 Nov '10

Is there a config macro for the presence/absence of C++0x uniform initialization syntax? http://en.wikipedia.org/wiki/C%2B%2B0x#Uniform_initialization If not, I suggest BOOST_NO_UNIFORM_INITIALIZATION_SYNTAX. A quick test shows that gcc-4.5 in 0x mode has it. -- Eric Niebler BoostPro Computing http://www.boostpro.com

2 2

[1.45] Beta 1 release candidates
by Beman Dawes 17 Nov '10

17 Nov '10

[1.45] Beta 1 release candidates are available at http://boost.cowic.de/rc/ As usual, please report success or failure doing builds. We like to get reports of successful builds on several varied platforms before the files are pushed out to SourceForge and the formal announcement made. Thanks, --Beman

8 14

Interest in B-tree library for Boost?
by Beman Dawes 17 Nov '10

17 Nov '10

A Boost B-tree library would provide disk-based associative containers that scale all the way from really, really, small to really, really, large. B-trees perform well on hardware ranging from ancient floppy disk drives all the way up to humongous disk arrays. They are the technology behind most high-performance disk file systems and databases. If you don't know what a B-tree is, or think that "B-tree" is an abbreviation for "Binary tree", you might want to read the Wikipedia B-Tree article: http://en.wikipedia.org/wiki/B-tree. Knuth and other computer science texts also supply descriptions. See http://mysite.verizon.net/beman/btree/index.html for a more complete description of the proposed library. A preliminary implementation is available. Download http://mysite.verizon.net/beman/btree/btree-preview-1.zip, and unpack into a current Boost distribution. A few existing Jamfiles will be overwritten. The only compilers tested and working so far are VC++ 10 and GCC/MinGW 4.5. You can view the library online at http://github.com/Beman/Boost-Btree There is no detailed documentation yet, but if you know how to use std::map and other standard library associative containers, you already know most of what you need to know. Critical differences are documented in the Library Characteristics section of the index.html page referenced above. Initial timing tests have been very encouraging. The time test compares the btree_map implementation to std::map. As expected, a btree_map is many times slower than a std::map, given a cold operating system file cache and constraining the btree_map's caching to a minimum. But at the other extreme, when the O/S file cache is warm and the btree_map's cache is as large as the file, the btree_map is very similar in speed to std::map.The btree library's code is still very new, so timings and everything else may be subject to lots of revision. Any interest? --Beman

14 37

[build] bjam in boost/tools/build/v2/test doesn't work
by Jim Bell 17 Nov '10

17 Nov '10

Running bjam in boost/tools/build/v2/test doesn't (seem to) run build's regressions. Instead, I get: jamfile.jam:8: in modules.load rule project-root unknown in module Jamfile</F:/tmp/boost-MinGW-32/trunk/boost/t ools/build/v2/test>. F:/tmp/boost-MinGW-32/trunk/boost/tools/build/v2/build\project.jam:314: in load- jamfile F:/tmp/boost-MinGW-32/trunk/boost/tools/build/v2/build\project.jam:62: in load F:/tmp/boost-MinGW-32/trunk/boost/tools/build/v2/build\project.jam:168: in proje ct.find F:/tmp/boost-MinGW-32/trunk/boost/tools/build/v2\build-system.jam:569: in load F:\tmp\boost-MinGW-32\trunk\boost\tools\build\v2\test\..\kernel\modules.jam:283: in import F:\tmp\boost-MinGW-32\trunk\boost\tools\build\v2\test\..\kernel\bootstrap.jam:14 2: in boost-build F:\tmp\boost-MinGW-32\trunk\boost\tools\build\v2\test\boost-build.jam:14: in mod ule scope If I run "python absolute_sources.py" (to pick that test as an example), I get very little (and it doesn't match regression test output): F:\tmp\boost-MinGW-32\trunk\boost\tools\build\v2\test\TestCmd.py:60: Deprecation Warning: The popen2 module is deprecated. Use the subprocess module. import popen2 Am I close? I realize that build is a different animal. Are there instructions for running its tests in isolation? (Could those instructions be put in boost/tools/build/v2/index.html?)

1 0

[python] [1.45] select_holder test failing
by Eric Niebler 17 Nov '10

17 Nov '10

Dave, The python "select_holder" test is failing across a large number of platforms on the release branch including all clang and gcc compilers. Can you please look into this prior to 1.45? Thanks, -- Eric Niebler BoostPro Computing http://www.boostpro.com

5 8

Boost.Build -q fix for 1.45
by Vladimir Prus 16 Nov '10

16 Nov '10

On IRC, Philipp Reh reported that 1.45 beta will fail if Boost.Build is invoked with -q, and any configuration test fails. The reason is that while Steven fixed this on trunk some time ago, I failed to merge to release branch. Since this bug means that Boost will outright not build in some cases, and since the fix is not really new, I think it should be checked in to release branch even at this point. The proposed diff is this: http://codepad.org/eoeawRoG Any objections before I go ahead? - Volodya

3 2

[clang] Using a stable clang for testing
by Daniel James 16 Nov '10

16 Nov '10

Hi, I posted about this on the testing list, but got no response, so I thought I'd try again here. To properly support clang, we need at least one release tester to use the stable clang release. According to config_info (which is at libs/config/test/config_info.cpp) the stable version is: "Clang version 2.8 (branches/release_28)", but the release tests are using "Clang version 2.8 (trunk 111264)" and "Clang version 2.9 (trunk 119008)". Would it be possible for someone to use the released version? Daniel

2 1

[netlib] 0.8-beta now available!
by Dean Michael Berris 16 Nov '10

16 Nov '10

Hi Everyone, advanced apologies for cross-posting. I've just tagged and uploaded archives of the cpp-netlib 0.8-beta which features: * An asynchronous server template, allowing for server-side streaming of data, asynchronous writing and reading facilities for server-side handlers, and a thread pool implementation that's temporarily using Boost.Asio's io_service for application-specific asynchronous handlers to run from. * A `ready(...)` wrapper to check for whether an asynchronous client's response is ready. The documentation has also been updated to feature a brand-new reference manual detailing the implementation, caveats, and public API of the HTTP client and server templates. You can go ahead and download the 0.8-beta and report issues you find either directly to me or through the mailing lists (Boost.User, Boost.Devel, and the cpp-netlib developers mailing lists). The target release for 0.8 will be this Friday, November 19, 2010. As usual, you can download the 0.8-beta package from GitHub at: https://github.com/cpp-netlib/cpp-netlib/downloads You can also check out the documentation for 0.8-beta at: http://cpp-netlib.github.com/0.8-beta Thanks everyone and I look forward to most appreciated feedback! -- Dean Michael Berris deanberris.com

5 14

[parameter] Boost.Parameter Constructors in Template Classes
by Dean Michael Berris 16 Nov '10

16 Nov '10

Hi Everyone, I'm not sure whether this is more appropriate for the users list or the developers list so I sent the email to both. I'm using Boost's SVN Trunk r66609 and I tried to compile the (attached) file to follow the pattern described by the Boost.Parameter tutorial (http://www.boost.org/doc/libs/1_44_0/libs/parameter/doc/html/index.html#par…) but unfortunately I get an error deep in the preprocessor code that Boost.Parameter uses. What I'm trying to do is to make a template class support parameterized constructors, and only have optional parameters and no required ones. The idea is: template <class Tag> struct base; template <class Tag> struct derived : base<Tag> { BOOST_PARAMETER_CONSTRUCTOR(...); }; Has anybody been able to make this work? Thanks and I definitely hope to hear from you soon. PS. I am also going to file this as a bug in Boost.Parameter so that it doesn't get lost in the mailing list churn. ;) -- Dean Michael Berris deanberris.com

2 3

[Review] Formal Review of Proposed Boost.Chrono Library LAST DAY TODAY
by Anthony Williams 15 Nov '10

15 Nov '10

Hi everyone, The review of Vicente Botet's Chrono library is underway; TODAY IS THE LAST DAY. If you haven't already submitted a review, please do so today. What is it? ======== Boost.Chrono aims to implement the new time facilities in C++0x, as proposed in N2661 - A Foundation to Sleep On (http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2008/n2661.htm) That document provides background and motivation for key design decisions and is the source of a good deal of information in this documentation. See the current C++0x working draft at http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2010/n3126.pdf for details of what was accepted. The Boost.Chrono library provides: * A means to represent time durations: managed by the generic duration class . Examples of time durations include days, minutes, seconds and nanoseconds, which can be represented with a fixed number of clock ticks per unit. All of these units of time duration are united with a generic interface by the duration facility. * A type for representing points in time: time_point. A time_point represents an epoch plus or minus a duration. The library leaves epochs unspecified. A time_point is associated with a clock. * Several clocks, some of which may not be available on a particular platform: system_clock, monotonic_clock and high_resolution_clock. A clock is a pairing of a time_point and duration, and a function which returns a time_point representing now. * To make the timing facilities more generally useful, Boost.Chrono provides a number of additional clocks that are thin wrappers around the operating system's time APIs, thereby allowing the extraction of read (wall clock) time, user CPU time, system CPU time, - process_real_cpu_clock, captures real (wall clock) CPU times. - process_user_cpu_clock, captures user-CPU times. - process_system_cpu_clock, captures system-CPU times. - A tuple-like class __process_cpuclock_, that captures real, user-CPU, and system-CPU times together. - A thread_clock thread monotonic clock, when supported by a platform. * Boost.Chrono also includes typeof registration for duration and time_point to permit using emulated auto with C++03 compilers. * Boost.Chrono also provides I/O for duration and time_point. It builds on <boost/ratio/ratio_io.hpp> to provide readable and flexible formatting and parsing for types in <boost/chrono.hpp> (subject to Vicente rewriting the parsing code under the BSL). The duration unit names can be customized through a new facet: duration_punct. Getting the library ============= The latest version of this library may be downloaded from vault: http://www.boostpro.com/vault/index.php?action=downloadfile&filename=chrono… SVN: http://svn.boost.org/svn/boost/sandbox/chrono Boost.Chrono depends on Boost.Ratio http://www.boostpro.com/vault/index.php?action=downloadfile&filename=ratio.… and optionaly Boost.System Header Only http://www.boostpro.com/vault/index.php?action=downloadfile&filename=system…. and the docs may be viewed here HTML: http://svn.boost.org/svn/boost/sandbox/chrono/libs/chrono/doc/html/index.ht… PDF: http://svn.boost.org/svn/boost/sandbox/chrono/libs/chrono/doc/chrono.pdf You can get all these information also (which should avoid some long links) from http://svn.boost.org/trac/boost/wiki/LibrariesUnderConstruction#Boost.Chrono Writing a review ================ If you feel this is an interesting library, then please submit your review to the developer list (preferably), or to the review manager. 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. Anthony Review Manager for the proposed Boost.Chrono library -- Author of C++ Concurrency in Action http://www.stdthread.co.uk/book/ just::thread C++0x thread library http://www.stdthread.co.uk Just Software Solutions Ltd http://www.justsoftwaresolutions.co.uk 15 Carrallack Mews, St Just, Cornwall, TR19 7UL, UK. Company No. 5478976

5 6

[function] function wrapping with no exception safety guarantee
by Daniel Walker 15 Nov '10

15 Nov '10

Hi all, A few weeks ago, there was a request to remove boost::function's dependency on boost::throw_exception when the user ensures that boost::function is always initialized before attempting a call. https://svn.boost.org/trac/boost/ticket/4646 Providing an alternative invocation method in addition to the call operator is an unattractive solution for many reasons; e.g. boost::function would be less function-like syntacticly. Instead, why not provide an alternative function wrapper with no exception safety guarantee and no dependency on boost::throw_exception? Thanks to Boost.Function's implementation design, which uses preprocessor metaprogramming to generate many function wrappers with different arities, it is simple to generate a function wrapper with no exception safety guarantee. I have submitted a feature request with a patch that implements boost::unsafe_function -- a function wrapper with no exception safety guarantee -- along with tests and updated documentation. https://svn.boost.org/trac/boost/ticket/4720 unsafe_function's API and semantics are identical to boost::function except that the behavior of operator() is undefined when uninitialized. Also, swap, constructor and assignment operators have been added to allow an unsafe_function to wrap the target of a boost::function and vice versa. unsafe_function is primarily useful in certain environments in which exceptions and/or compiler optimizations are unavailable, such as some embedded systems. On contemporary PC hardware, unsafe_function typically would not have an advantage over boost::function. For example, with object code generated by gcc -O2, I could only detect a ~1% difference between the two in terms of runtime costs using a simple benchmark; i.e. less than a nanosecond. However, with -O1, unsafe_function costs ~15% less than boost::function due to the lack of overhead from the strong exception safety guarantee. Thoughts? Daniel Walker

19 127

[1.45][thread] TSS showstopper?
by John Maddock 15 Nov '10

15 Nov '10

The recent changes to Boost.Thread in both Trunk and Release branches have broken one of the regex tests: testing.capture-output ..\..\..\bin.v2\libs\regex\test\regex_regress_threaded.test\msvc-10.0\debug\asynch-exceptions-on\threading-multi\regex_regress_threaded.run ====== BEGIN OUTPUT ====== TSS Initialisation failed with message: boost::thread_resource_error **** error return code: -1 ******** errors detected; see standard output for details ******** EXIT STATUS: 1 ====== END OUTPUT ====== I assume it's quite likely that if this effects the regex lib, then it will equally impact on user code that uses thread_specific_pointer? Regards, John.

3 7

Re: [boost] [Boost-commit] svn:boost r66577 - trunk/libs/numeric/ublas/test
by Jürgen Hunold 15 Nov '10

15 Nov '10

Hi David, This commit On Sunday, 14. November 2010 20:34:07 david.bellot(a)gmail.com wrote: > Author: david.bellot > Date: 2010-11-14 14:34:04 EST (Sun, 14 Nov 2010) > New Revision: 66577 > URL: http://svn.boost.org/trac/boost/changeset/66577 > > Log: > update jamfile > > Text files modified: > trunk/libs/numeric/ublas/test/Jamfile.v2 | 2 ++ > 1 files changed, 2 insertions(+), 0 deletions(-) > > Modified: trunk/libs/numeric/ublas/test/Jamfile.v2 > ============================================================================ --- trunk/libs/numeric/ublas/test/Jamfile.v2 (original) > +++ trunk/libs/numeric/ublas/test/Jamfile.v2 2010-11-14 14:34:04 EST > (Sun, 14 Nov 2010) @@ -134,4 +134,6 @@ > ] > [ run test_assignment.cpp > ] > + [ test_boost_ublas_size_0.cpp > + ] > ; just broke the test. First, the call is totally wrong, should read "run test_boost-..." ../libs/numeric/ublas/test/Jamfile.v2:138: in modules.load rule test_boost_ublas_size_0.cpp unknown in module Jamfile</home/hunold/src/devel/boost/libs/numeric/ublas/test>. Second,test_boost_ublas_size_0.cpp is missing from svn. error: Unable to find file or target named error: 'test_boost_ublas_size_0.cpp' error: referred from project at error: '.' Please add at least the missing file. Yours, Jürgen -- * Dipl.-Math. Jürgen Hunold ! Ingenieurgesellschaft für * voice: ++49 511 262926 57 ! Verkehrs- und Eisenbahnwesen mbH * fax : ++49 511 262926 99 ! Lister Straße 15 * juergen.hunold(a)ivembh.de ! www.ivembh.de * * Geschäftsführer: ! Sitz des Unternehmens: Hannover * Prof. Dr.-Ing. Thomas Siefer ! Amtsgericht Hannover, HRB 56965 * PD Dr.-Ing. Alfons Radtke !

1 0

[1.45] Where are we in the release process?
by John Maddock 14 Nov '10

14 Nov '10

I'm asking because someone's just assigned a Boost.Interval issue to me: https://svn.boost.org/trac/boost/ticket/4799#comment:1 Seems like there is a trivial fix in Trunk, but as the library appears not to have been maintained for while, it looks like none of the patches that some folks have applied to Trunk have been merged to release :-( On a related note, I believe there are quite a few old and unmerged changes to the Utility lib as well. We really need to figure out a better way of dealing with this... John.

6 13

Minimizing Dependencies within Generic Classes for Faster and Smaller Programs
by vicente.botet 14 Nov '10

14 Nov '10

Hi, I have found this paper "Minimizing Dependencies within Generic Classes for Faster and Smaller Programs" http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2009/n2911.pdf quite iteresting. The gain in performances and reduced space could be considerable. I was wondering if Boost should not take this as a guideline and whether the Boost authors would check his libraries to see if this technique could improve its performances, in particular for all the container and the the forthcomming Boost.Container libraries. I would be interested in knowing if this has been adopted for C==0x containers. Good reading, _____________________ Vicente Juan Botet Escribá http://viboes.blogspot.com/

10 18

Standard stream from C fopen()
by Claude 14 Nov '10

14 Nov '10

Hi! I Use this code for make a standard stream from a C fopen() FILE* : FILE *fd = fopen("Prova", "w"); if (fd) { // io::stream_buffer<io::file_descriptor_source> fpstream (fileno(fd)); //std::istream in (&fpstream); istream in = boost::iostreams::file_descriptor(fileno(fd)); } But I obtain an error (G++ on Linux Ubuntu): [...] error: conversion from ‘boost::iostreams::file_descriptor’ to non-scalar type ‘std::istream’ requested| [...] error: call of overloaded ‘path(const int&)’ is ambiguous| [...] Why? What is the correct method? -- View this message in context: http://boost.2283326.n4.nabble.com/Standard-stream-from-C-fopen-tp3040002p3… Sent from the Boost - Dev mailing list archive at Nabble.com.

4 8

[1.45.0] Permission to merge trunk to release for Boost.Optional
by Fernando Cacciola 13 Nov '10

13 Nov '10

Hi, As reported by Eric Niebler, the release brunch did not had the swap member that existed in the trunk for a long time. I just merged it locally and run the tests on the release branch. Can I commit the changes? P.S: The test suite changed as well due to the different swap. P.S.2: I've also been reported on a couple of minor documentation issues, so I've fixed this on both the trunk and the release branch. P.S.3: Going over all the differences I've found a trivial change in the testsuite for value_initialized: The trunk version uses the lightweight "minimal" test tools instead of the full test tools. I've merged this one as well. Can I commit these changes to the release branch? --- Fernando Cacciola SciSoft Consulting, Founder http://www.scisoft-consulting.com

6 9

[FunctionTypes] Removing the ClassTransform when invoking parameter_types
by Edward Diener 12 Nov '10

12 Nov '10

When invoking boost::function_types::parameter_types with a member function pointer as the first template parameter, what do I susbstitute as the second template parameter so that no transform is done ?

2 1

[exception] [1.44] you own a showstopper
by Eric Niebler 12 Nov '10

12 Nov '10

Emil, The following bug in exception is marked as a Showstopper for the 1.44 release. What are your plans for it? If you're planning on fixing it, can you do so soon? If you feel it is not a showstopper, can you set its priority appropriately? https://svn.boost.org/trac/boost/ticket/4768 Thanks, -- Eric Niebler BoostPro Computing http://www.boostpro.com

3 6

Type traits extension & Bitfield reviews
by Joel Falcou 12 Nov '10

12 Nov '10

I've just seen these libraries hanging out in the review queue for quite some time now. Considering their potential usefulness adn my personnal interest, I consider stepping up as a review manager for these. What's the formal sequence to follow to apply for such a task ?

7 10

[inspect] added new check for C-style assert macro (was: [property_tree][showstopper][1.45] missing include in string_path.hpp)
by Eric Niebler 12 Nov '10

12 Nov '10

On 11/11/2010 3:49 PM, Sebastian Redl wrote: > On 11.11.2010, at 21:38, Eric Niebler wrote: >> If BOOST_ASSERT is *always* to be preferred over C's assert macro, >> then we should probably add that to the inspection report, right? > > That would probably a good idea. I just modified the inspect tool to check for the presence of C-style assert in Boost code. Everybody should be using BOOST_ASSERT. (Right?) Here's the result of running the new check over Boost trunk: http://pastebin.com/NttTw3BJ Beman, the inspection report looks like it was last run in June. What's up? http://boost.cowic.de/rc/inspect-trunk.html -- Eric Niebler BoostPro Computing http://www.boostpro.com

4 11

[1.45][filesystem/io] Streaming operator
by Chard 12 Nov '10

12 Nov '10

The filesystem path streaming operator (>>) has a bug in 1.44, documented here: https://svn.boost.org/trac/boost/ticket/4716 A patch has been provided, and has been implemented on the trunk, detailed here: http://lists.boost.org/boost-commit/2010/08/27576.php Any chance of this being merged to the release branch for 1.45? [.../boost/io/detail/quoted_manip.hpp] --

1 0

Re: [boost] [Boost-users] What's so cool about Boost.MPI?
by Matthias Troyer 12 Nov '10

12 Nov '10

On 5 Nov 2010, at 20:04, Riccardo Murri wrote: > On Fri, Nov 5, 2010 at 3:51 PM, Peter Foelsche <foelsche(a)sbcglobal.net> wrote: >> Can somebody explain to me, what is so great about mpi or boost/mpi? > > Daunting task, but I'll give it a try :-) > > MPI is a library interface[1] to ease some common communication > patterns in scientific/HPC software. In particular, MPI provides > library functions for: > > 1. Reliable delivery of messages between two concurrent processes; > there are functions for both synchronous and asynchronous > communication. > > 2. Collective communication of the running processes: e.g., one > process broadcasting a message to all others; all processes > broadcasting to all; scattering a large array to all running > processes, etc. > > 3. "Remote shared memory": a process can expose a memory buffer that > all others can directly read/write. > > 4. Parallel I/O, where many processes access (possibly interleaved) > portions of a file independently. > > Despite being non-trivial features to implement on top of a standard > TCP socket interface, MPI implementations are mostly into performance: > they can usually take advantage of special hardware (e.g., Infiniband > or Myrinet interconnects) and use the native protocols (instead of > TCP/IP) to provide faster communication speed. > > A "message" in usual socket programming is just a flat array of bytes. > A "message" in MPI is a (potentially non-contiguous portion) of a C or > FORTRAN data structure; MPI can handle C structures and > multi-dimensional C-style arrays, and multi-dimensional arrays of C > structures (containing multi-dimensional arrays, etc.). However, > since MPI is implemented as a library, you have to tdescribe to MPI > the in-memory layout of the data structures you want to send as a > message; thus "duplicating" work that is done by the compiler. You > can imagine that this quickly gets tedious and unwieldy once you start > having non-trivial data structures, possibly with members of unknown > length (e.g., a list). > > This is where Boost.MPI comes to the rescue: if you can provide > Boost.Serialization support for your classes, you can send them as MPI > messages with no extra effort: no need for lengthy calls to > MPI_Type_create_struct() etc. And it does this with minimal or even > no overhead! (Plus you also get a nice C++ interface to MPI > functionality, whereas the MPI C calls are quite low-level.) > > > .. [1] MPI proper is a specification; there are several > implementations of the spec (e.g., OpenMPI, MPICH, MVAPICH, plus > many vendor/proprietary one), but they are all compatible at the > source level. > > Best regards, > Riccardo Nice summary! Matthias

5 8

[1.45.0] Beta 1 available from SourceForge
by Beman Dawes 11 Nov '10

11 Nov '10

Boost release1.45.0 beta 1 is now available from SourceForge. For those who downloaded release candidate 1, note that beta 1 was build from a slightly later release candidate. See http://sourceforge.net/projects/boost/files/ This release contains numerous enhancements and bug fixes for existing libraries. For details of what's in the release, see http://beta.boost.org/users/news/version_1_45_0. Note that the links to files on this web page are for the final release - use the SourceForge link above to get the beta files. Please download the beta, give it a try, and report any problems you encounter. There are still a few serious bugs outstanding, and we will be working on clearing those before the final release. Thanks, -- The Boost Release Team

7 9

Re: [boost] [serialization][thread] possible regressions?
by Eric Niebler 11 Nov '10

11 Nov '10

On 11/11/2010 1:41 PM, Robert Ramey wrote: > Anthony Williams wrote: >> Eric Niebler <eric(a)boostpro.com> writes: >> >>> I don't know whether this is a serialization issue or a thread issue. >>> Robert, Anthony, can you two weigh in? >> >> Looks like a serialization problem to me. > > I would agree - but its hard to reproduce from here. I don't see this as > quick fix - it would require some time and help from the person who can > actually reproduce it. Thanks, Robert. This is now https://svn.boost.org/trac/boost/ticket/4842 Ruediger, anything you can do to help Robert with this one would be much appreciated. -- Eric Niebler BoostPro Computing http://www.boostpro.com

1 0

Problem with boost deserialization.
by Esteban RG 11 Nov '10

11 Nov '10

Hi, I need serialization in a project of mine. I have reduced my options to boost and ProtocolBuffer, but in order to be able to decide which one to use, I am trying to build a timing test for serialization and deserialization. Let me explain a little about my setup: a) Platform: - windows 7, 64bit version - visual studio 2008 express edition x32 b) Additional library: - ACE library for High resolution timer. The code (an explanations) that I have used to implement the comparison is at follows: I build a class with four different lists of boost/serialization/list like documentation states: std::list<unsigned int> &lint_; std::list<ACE_INT64> &llong_; std::list<float> &lfloat_; std::list<std::string> &lstring_; The test is increasing the size of every list simultaneously. Then it gets serializated and deserializated and finally I get the time results for this process. However there is one issue: Serialization always works, but deserialization fails during execution time whenever the lists are bigger than 10 elements, throws a exception "input stream error" into boost/serialization/throw_exception.hpp as seen with the debugger in the variable/const std::exception const &e (boost library) Visual studio shows this message: Unhandled exception at 0x765cb727 in prTestBoostSerialization2.exe: Microsoft C++ exception: boost::archive::archive_exception at memory location 0x003fc564.. my class definition is: #include <boost/archive/binary_oarchive.hpp> #include <boost/archive/binary_iarchive.hpp> #include <boost/serialization/string.hpp> #include <boost/serialization/list.hpp> //#include <boost/serialization/version.hpp> //#include <boost/serialization/split_member.hpp> #include <iostream> #include <list> #include <string> class BoostSerializationClass { public: // Not required because al member are public // friend class boost::serialization::access; BoostSerializationClass(std::list<unsigned int> &lint , std::list<float> &lfloat , std::list<ACE_INT64> &llong , std::list<std::string> &lstring) : lint_(lint), lfloat_(lfloat), llong_(llong), lstring_(lstring) { //std::cout << std::endl << " max size " << lint_.max_size(); //std::cout << std::endl << " " << llong_.max_size(); //std::cout << std::endl << " " << lfloat_.max_size(); //std::cout << std::endl << " " << lstring_.max_size(); } std::list<unsigned int> &lint_; std::list<ACE_INT64> &llong_; std::list<float> &lfloat_; std::list<std::string> &lstring_; }; namespace boost { namespace serialization { template<class Archive> void serialize(Archive &ar, BoostSerializationClass &c , const unsigned int version){ ar & c.lint_; ar & c.llong_; ar & c.lfloat_; ar & c.lstring_; } } } ----------------------- And main function is: #include <iostream> #include <fstream> //#include <cstdlib> #include <ace/OS.h> #include <ace/Time_Value.h> #include <ace/High_Res_Timer.h> // high resolution timer // include for BOOST #include "../prTestProtocolBuffers/BoostSerializationClass.h" #include <boost/archive/binary_oarchive.hpp> #include <boost/archive/binary_iarchive.hpp> //#include <list> <- dont include this use boost/serialization/list #include <boost/serialization/list.hpp> void gen_random_string(std::string &s, const int len); int ACE_TMAIN(int argc, ACE_TCHAR* argv[]){ //int lengthList = 5; //int lengthList = 10; int lengthList = 15; //int lengthList = 50; // int lengthList = 100; // int lengthList = 1000; std::list<unsigned int> listInteger,listInteger2; std::list<float> listFloat,listFloat2; std::list<ACE_INT64> listLongs,listLongs2; std::list<std::string> listString,listString2; int rint = 0; float rfloat = 0.f; ACE_INT64 rint64 = 0; std::string rstring = ""; std::cout << std::endl << "Begin random generate message. Please be patient."; // Generate random fields for messages for (int i=0 ; i<lengthList ; i++){ listInteger.push_back( rand() ); listFloat.push_back( (float)rand()/(float)RAND_MAX ); listLongs.push_back( rand()*rand()*rand() ); gen_random_string(rstring, lengthList); listString.push_back( rstring ); } // BOOST SERIALIZATION ACE_High_Res_Timer hrTimerBoost; // Load fields into BoostSerializableClass BoostSerializationClass boostSerializationClass( listInteger, listFloat, listLongs, listString); std::ofstream obfile("boost-file.bin"); boost::archive::binary_oarchive oba(obfile); //ACE_Time_Value btvStart = ACE_OS::gettimeofday(); hrTimerBoost.start(); oba & boostSerializationClass; // boost serialization; obfile.close(); hrTimerBoost.stop(); ACE_hrtime_t usecsBoost; hrTimerBoost.elapsed_microseconds(usecsBoost); //ACE_Time_Value btvEnd = ACE_OS::gettimeofday(); //ACE_Time_Value tvIncBoost( btvEnd.sec() - btvStart.sec() , btvEnd.msec() - btvStart.msec() ); std::cout << std:: endl << " ===== BOOST SERIALIZATION =====" ; //std::cout << std::endl << tvIncBoost.sec() << " seconds " << tvIncBoost.msec() << " mseconds" << std::endl ; std::cout << std::endl << usecsBoost << " micro seconds " << std::endl ; // BOOST DESERIALIZACION BoostSerializationClass boostSerializationClass2( listInteger2, listFloat2, listLongs2, listString2); std::ifstream ibfile("boost-file.bin"); boost::archive::binary_iarchive iba(ibfile); //btvStart = ACE_OS::gettimeofday(); hrTimerBoost.reset(); hrTimerBoost.start(); iba & boostSerializationClass2; ibfile.close(); hrTimerBoost.stop(); hrTimerBoost.elapsed_microseconds(usecsBoost); //btvEnd = ACE_OS::gettimeofday(); //tvIncBoost = ACE_Time_Value( btvEnd.sec() - btvStart.sec() , btvEnd.msec() - btvStart.msec() ); std::cout << std:: endl << " ===== BOOST DE-SERIALIZATION =====" ; //std::cout << std::endl << tvIncBoost.sec() << " seconds " << tvIncBoost.msec() << " mseconds" << std::endl ; std::cout << std::endl << usecsBoost << " micro seconds " << std::endl ; ACE_OS::system("pause"); return 0; } //////////////////////////////////////////////////////////////////////////////////////////////////////////// void gen_random_string(std::string &s, const int len) { static const char alphanum[] = "0123456789" "ABCDEFGHIJKLMNOPQRSTUVWXYZ" "abcdefghijklmnopqrstuvwxyz"; s.clear(); for (int i = 0; i < len ; ++i) { s.push_back(rand() % (sizeof(alphanum) - 1) ); } } Can anyone of you help me with this? Any help would be truly appreciated. Thanks in advance.

4 4

[task][fiber] question about memory leaks
by Dorogan' Konstantin 11 Nov '10

11 Nov '10

Sorry for my "good" english. :) I'am try to use boost.task 0.4.2 in my project. I found some leaks in the files handle.hpp and task.hpp related use_count member initialization. So boost::intrusive_ptr can't release allocated resources. After fixing promblem of the use_count initialization, i ran my unit tests again, but some leaks still living. I discovered that the problem is in the boost.fiber (v 0.5.1). If i try to run compiled unit tests of the boost.fiber manually, the garbage collector of the boost.test shows the leaks. In hopes of finding the place of data leaks, I perform these tests under Rational Purify, but Puify reports that no leaks were detected. Is the garbage collector of the boost.test lies, or the leaks is real!? Tested environment: Windows 7 x64, Windows XP boost 1.42.0 boost.context 0.2.0 boost.task 0.4.2 boost.fiber 0.5.1

1 0

[1.45] Release v trunk, as of r66483
by Jim Bell 11 Nov '10

11 Nov '10

Here's a list of all differences between release and trunk, as of r66483 (this morning). I won't slam the mailing list with its contents, so it's here instead: http://jc-bell.com/files/release-v-trunk-r66483.csv Organized by Folder (2nd column), and it might have a stray false positive or negative since I apply a patch to test. FYI.

5 10

Re: [boost] [msm] Event deferring causes stack overflow
by Christophe Henry 10 Nov '10

10 Nov '10

<snip> >It is not that nice for 2 reasons: > >1. It makes state machine behavior description more splinted in our case to several files ( not a big deal). >2. I have created our own defer functor which logs the event deferral with our logging framework >is there a way do similar function in a state like the no_transition for deferred events where I can implement some generic logging ?. Hi Richard, No, it's not nice. Luckily, last night brought fresh ideas and I implemented a fix. It has to run all regression tests to be 100% sure but it looks good so you can give it a try. For your logging functor, you have to provide a typedef inside the functor definition (like Defer is now doing in functor_row.hpp): typedef int deferring_action; This activates the normal deferred handling and the stack overflow is gone. The fix can be downloaded from the trunk (revision 66490). Unfortunately, it is too late to make it into the 1.45 so be careful if you switch to the new boost release :( I also didn't have time to actualize the doc yet. HTH, Christophe

1 0

[boost.log] Using stream manipulators to influence record formatting per sink
by Jamie Allsop 10 Nov '10

10 Nov '10

So I've been using the previously reviewed log library by Andrey Semashev with some degree of success. One thing however has caused me a great deal of trouble and I'm sure with a couple of changes would become a lot easier. Basically I have an application that outputs tabular data in the logs. I have objects that know how to stream themselves either as an ascii table or as an html table. I have a custom defined manipulator that can be set for a stream that the objects can check the value of, and stream themselves either as text or html as appropriate. In using the log library I face two major challenges. The first is how can I set the manipulator to the desired value so that the log record will be aware of the manipulator while building its message? It is not possible to do this by calling set_formatter() on the sink since the this receives *an already composed* record.message() string. My work-around for this is a lot more complex than I'd like it to be and I'll detail it here in the hope that it provides some insight to Andrey so that he might be able to offer a nicer alternative more in-keeping with his library. So starting at the beginning I have objects that implement streaming something like this: ---- template< class CharT, class Traits> friend std::basic_ostream< CharT, Traits>& operator<<( std::basic_ostream<CharT, Traits>& Ostream, const my_class& Value ) { if( log::output_format::value_in( Ostream ) == log::output_format::text ) { write_text( Ostream, Value ); } else if( log::output_format::value_in( Ostream ) == log::output_format::html ) { write_html( Ostream, Value ); } return Ostream; } ---- where 'value_in()' simply retrieves the value from the stream. Now during logging a temporary stream object is created that must have this manipulator applied. What I'd like to do is be able to specify if I want this manipulator applied on a per-sink basis. In much the same way as I can define a specific formatter for a sink, or a specific filtering rule for a sink. Currently there is no way to do that (at least not without a *lot* of effort) so I'll address this later. Instead I'll consider how we can deal with this be setting this desire globally by using a global attribute. We could write something like this: ---- log::output_format::type OutputFormat = log::output_format::html; std::pair< boost::log::core::attribute_set_type::iterator, bool > OutputFormatAttribute = boost::log::core::get()->add_global_attribute ( "OutputFormat", boost::make_shared< boost::log::attributes::constant<log::output_format::type> >( OutputFormat ) ); ---- Later we can extract this value to decide if we need the manipulator applied to the stream that is used to compose the log record message. We can use a helper object that is aware of all the manipulators that are to be applied and have it the log record stream based on attributes that represent them. For example, given a class called 'manipulators' we can define this insertion operator as: ---- template< class CharT, class TraitsT > inline std::basic_ostream<CharT,TraitsT>& operator<< ( std::basic_ostream<CharT,TraitsT>& Ostream, const manipulators& Manipulators ) { Manipulators.apply( Ostream ); return Ostream; } ---- where apply could be implemented (in our case) as this: --- template< class CharT, class TraitsT > void apply( std::basic_ostream<CharT,TraitsT>& Ostream ) const { boost::log::basic_record<CharT> Record( RecordHandle_ ); apply_output_format( Ostream, Record ); } private: ---- template< class CharT, class TraitsT > void apply_output_format( std::basic_ostream<CharT,TraitsT>& Ostream, const boost::log::basic_record<CharT>& Record ) const { log::output_format::type OutputFormat = log::output_format::text; boost::log::extract<log::output_format::type> ( "OutputFormat", Record.attribute_values(), boost::lambda::var( OutputFormat ) = boost::lambda::_1 ); if( OutputFormat == log::output_format::text ) { Ostream << log::set_output_format( log::output_format::text ); } else if( OutputFormat == log::output_format::html ) { Ostream << log::set_output_format( log::output_format::html ); } } ---- This then requires that the insertion operator is called as part of the streaming for any log record. In order to achieve this I need to write my own logging macros that do essentially what the severity logging macros do already but with the addition of streaming a 'manipulator' object at the same time so that the manipulators I want added can be applied to the stream that is constructed during that process. Here is the key macro that I need to write which gets substituted in a chanin of macros: ---- #define MY_LOG_STREAM_WITH_PARAMS_INTERNAL(logger, rec_var, params_seq)\ for (::boost::log::record_handle rec_var = (logger).open_record((BOOST_PP_SEQ_ENUM(params_seq))).handle(); !!rec_var; rec_var.reset())\ ::boost::log::aux::make_pump_stream((logger), rec_var).stream() << log::manipulators(rec_var) ---- The important part is this: ---- log::manipulators(rec_var) ---- The stream object is created and immediately passed an instance log::manipulators passing the RecordHandle to the constructor. Finally then I can have manipulators passed down to the stream that is used to create the log record message, and in my case allow the logged objects to either stream themselves as text or as html. A downside of this is that this only works with global attributes. So either all log sinks would one format or the other. Given that it is generally desirable to treat different sinks differently (and often the reason they exist) it would be much nice if there was the concept of sink-level attributes. These could be added to the record's attribute set along with the source and global attributes. Currently there is no way (it seems) to associate any state with a sink or make any decision during logging that relates to a sink. We can set a custom formatter that applies to the log message created but that has no effect on the record message itself. (Decorators only seem to be for post-processing of the record message). We can also set a custom filter to determine whether a log record gets logged by a given sink. It seems odd then that we have no way to to be able to say (for example) that a given sink will have an attribute that indicates that all messages through that sink should be in a certain format (for those objects that support the formatting). From looking at the code this does not appear to be a major issue so hopefully it could be supported. It would also be highly desirable to be able to specify manipulators directly that could then be applied to the record message stream itself. Supporting this at the global and sink level should be possible. If we had sink-level attributes the technique I described could be used to simulate this, even though it is somewhat kludgey. Most directed to Andrey, but I'd welcome comments and suggestions from others familiar with the log library. Jamie

2 3

[icl] The Interval Container Library (ICL) moved to the Boost trunk
by Joachim Faulhaber 10 Nov '10

10 Nov '10

Dear All, thank you again for you welcoming comments on the latest version of the now renamed Interval Container Library ICL (formerly Interval Template Library ITL). And thanks to Hartmut for your "invitation" to move the library to the Boost trunk. This might be a small step for Boost but it's a big step for me ;-) I am not sure what has to be done now, so my test suite will be executed in the daily tests that is summarized in the trunk summary on the Boost web-site. I have added my lib into the list in status/Jamfile.v2. I am also wondering how I get information about and deal with errors from those tests on platforms that I can not run on my machine. I didn't find anything about those topics on the Wiki so far. Maybe someone can provide some guidance :) Thanks, Joachim

1 0

[boost.log] set_open_handler() and set_close_handler() for text_multifile_backend?
by Jamie Allsop 10 Nov '10

10 Nov '10

I think it makes a lot of sense for these methods to be available for the text_multifile_backend as they are for the text_file_backend. My use case is that I am logging data out in html format and being able to log data out as individual html files for browsing through later on. Being able to have an html header and footer added as files are opened and closed makes a lot of sense for this backend. Jamie

2 4

[optional] swap not a member of boost::optional
by Eric Niebler 10 Nov '10

10 Nov '10

It seems like boost::optional has a swap member function on trunk but not on release, and it's been this way for a few releases already. Can we get this inconsistency resolved? I've been bitten by it a few times already when merging things to the release branch. -- Eric Niebler BoostPro Computing http://www.boostpro.com

1 1

[graph] Kudos!
by K. Noel Belcourt 10 Nov '10

10 Nov '10

Hi, Just wanted to say nice job to Jeremiah Willcock!! Found this killer graph on page 5: http://www.sandia.gov/LabNews/ln11-05-10/labnews11-05-10.pdf I probably cut the citation off (it reads: Graph courtesy of Jeremiah Willcock, Indiana University). Guessing this was generated with pBGL? -- Noel

1 0

[fusion] rev. 66411 breaks VC 8.0
by Ralf W. Grosse-Kunstleve 10 Nov '10

10 Nov '10

minimal.cpp: #include <boost/fusion/sequence/comparison/less_equal.hpp> cl /c /EHsc /I..\hot\boost minimal.cpp Gives the error below. It works with rev. 66410 but not 66411 (and still not with current 66472): % svn log -v -c66411 ------------------------------------------------------------------------ r66411 | cschmidt | 2010-11-06 05:21:18 -0700 (Sat, 06 Nov 2010) | 1 line Changed paths: M /trunk/boost/fusion/container/deque/deque.hpp A /trunk/boost/fusion/container/deque/detail/is_sequence_impl.hpp M /trunk/boost/fusion/container/vector/detail/vector_n.hpp M /trunk/boost/fusion/sequence/comparison/detail/enable_comparison.hpp M /trunk/boost/fusion/support/detail/is_mpl_sequence.hpp M /trunk/boost/fusion/support/is_sequence.hpp M /trunk/boost/fusion/support/sequence_base.hpp Fusion: removed fusion::sequence_root; Fixes #2335 ------------------------------------------------------------------------ ..\hot\boost\boost/fusion/sequence/comparison/less_equal.hpp(48) : error C2039: 'is_native_fusion_sequence' : is not a member of 'boost::fusion::detail' ..\hot\boost\boost/fusion/sequence/comparison/less_equal.hpp(48) : error C2065: 'is_native_fusion_sequence' : undeclared identifier ..\hot\boost\boost/fusion/sequence/comparison/less_equal.hpp(48) : error C2974: 'boost::disable_if' : invalid template argument for 'Cond', type expected ..\hot\boost\boost/utility/enable_if.hpp(59) : see declaration of 'boost ::disable_if' ..\hot\boost\boost/fusion/sequence/comparison/less_equal.hpp(48) : error C2988: unrecognizable template declaration/definition ..\hot\boost\boost/fusion/sequence/comparison/less_equal.hpp(48) : error C2059: syntax error : ',' ..\hot\boost\boost/fusion/sequence/comparison/less_equal.hpp(48) : error C2039: 'type' : is not a member of '`global namespace'' ..\hot\boost\boost/fusion/sequence/comparison/less_equal.hpp(55) : error C2039: 'is_native_fusion_sequence' : is not a member of 'boost::fusion::detail' ..\hot\boost\boost/fusion/sequence/comparison/less_equal.hpp(55) : error C2974: 'boost::disable_if' : invalid template argument for 'Cond', type expected ..\hot\boost\boost/utility/enable_if.hpp(59) : see declaration of 'boost ::disable_if' ..\hot\boost\boost/fusion/sequence/comparison/less_equal.hpp(56) : error C2039: 'type' : is not a member of '`global namespace'' ..\hot\boost\boost/fusion/sequence/comparison/less_equal.hpp(57) : error C2143: syntax error : missing ';' before '{' ..\hot\boost\boost/fusion/sequence/comparison/less_equal.hpp(57) : error C2447: '{' : missing function header (old-style formal list?)

2 2

Showstopper ticket #4736 not in trunk or release
by Jim Bell 10 Nov '10

10 Nov '10

The patch for showstopper ticket # 4736 isn't in either the trunk or release branches as of this morning (r66453). Did it get missed?

3 7

MinGW's last thread/tss problem: fixable?
by Jim Bell 10 Nov '10

10 Nov '10

Thread is still failing test_tss_lib, now with this... ../libs/thread/test/test_tss.cpp(181): error in "test_tss": Support of automatic tss cleanup for native threading API not available If I understand this correctly, the tss cleanup will never be called for a thread created via the native API. There's no global function that can force a clean-up because nothing can force the underlying thread mechanism to return the thread-specific value for a thread that's already exited. I see some subtle magic in libs/thread/src/win32/tss_pe.cpp, some even for __MINGW32_... Is this for static libs? Any chance we can make that work for MinGW's gcc-4.3.3 and gcc-4.4.0? Also, I think the docs need a "Note" section describing this issue, say thread_local_storage.html, inside the section "Cleanup at thread exit".

2 1

Re: [boost] [Review] Formal Review of Proposed Boost.Chrono LibraryStarts TOMORROW
by Aaron Graham 10 Nov '10

10 Nov '10

See this gcc bugzilla entry for a discussion I've had about chrono support in the gcc implementation. http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41861 Unfortunately, monotonic_clock support, even if it exists, is a transparent lie. It's not so much a problem with the chrono library as it is a problem with the thread library's use of chrono. A monotonic clock is used to provide somewhat accurate/reliable wait times even in the face of changing clocks, especially in the case of mutexes and condition variables. When condition::wait_until is called with a monotonic_clock time_point, that time_point is translated to a system_clock time_point. If the system_clock is changed (via NTP, adjtime, settimeofday, etc) between when convert_to<system_clock> is called and when the underlying posix call is made, the very reason for using monotonic_clock defenestrates and splatters all over the pavement. Depending on the magnitude of the clock change, wait_until could hang forever. In my opinion, all convert_to calls in the thread library should go to the monotonic_clock, if available. Not system_clock. I couldn't get the gcc people to understand this, so I won't be able to use <chrono> in the standard library sans modification. Maybe boost will get it right? Let me know if I'm missing a subtle point that moots my concerns. Other than that, I think the this library is great. I need it badly. I haven't looked over all the code yet, but what I've seen looks good.

3 2

mkl+boost problems
by Andrey Asadchev 10 Nov '10

10 Nov '10

Hello. mkl (intel blas) has "mkl_cblas.h" file which in turn includes " mkl_types.h" file which defines P4 macro variable: 70 /** CPU codes for int MKL_CPU_DETECT(void) **/ 71 #ifdef _IPF 72 #define ITP 0 73 #else 74 #ifdef _EM64T 75 #define NI 0 76 #define CT 1 77 #define MNI 2 78 #define PNR 3 79 #else 80 #define DEF 0 81 #define PIII 1 82 #define P4 2 83 #define P4P 3 84 #define P4M 4 85 #endif 86 #endif This P4 variable creates havoc of MPL templates which have P4 template parameters names. What to do?

9 10

Re: [boost] [msm] Event deferring causes stack overflow
by Christophe Henry 09 Nov '10

09 Nov '10

> Hi All > > We have found a serious problem in msm back end for event deferring. > I case there is a composite state and the outer state machine defers 2 > events when it is in the composite state, the 1st event deferred fine > in the deferred queue of the outer state machine. > Than the 2nd event is processed and this is deferred as well as a part > of this deferral msm back end dispatches the 1st event but it is still > deferred and saved again in the deferred queue but than msm processes > the deferred queue again as an action of the deferral of the 1st event > and dispatches the 2nd event again which is deferred and the cycle > repeats itself until the system runs out of call stack. Hi, No, it's not that serious, but still not nice. The problem is that the principle of the Defer functor is not working and I am wondering if I should keep it. To make short, Defer is an action, and for all front-ends, actions return void. This has the unintended effect of marking the transition results as "handled" instead of "deferred", which breaks my defensive measures. If you replace the transitions by the standard UML method of marking the state as deferring (through the deferred_events typedef), you have no more stack overflow. Now I understand that the Defer functor is cool and offering to remove it is guaranteed to cause disappointment, so I see 2 possibilities: - explaining its limitations in the doc - making a change to all front-ends for this special case to work around the fact that actions return void For the meantime, use the "normal" way and I will see if I find a workaround. Cheers, Christophe

2 1

[mpl] mpl::c_str fails for mpl::push_back
by vicente.botet 09 Nov '10

09 Nov '10

Hi, the following results in a compile error for msvc-10.0. It works for gcc-3.4, gcc-4.3, gcc-4.5. typedef mpl::vector_c<char, 'h','e','l','l','o',' ','w','o','r','l','d'> hello; typedef mpl::push_back<hello, mpl::char_<'!'> >::type hello2; BOOST_TEST((std::string(mpl::c_str<hello2>::value)== "hello world!")); // line 59 C:\cygwin\boost\v44\boost/mpl/string.hpp(592) : error C2039: 'value_type' : is not a member of 'boost::mpl::vector12<T0,T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11>' with [ T0=boost::mpl::integral_c<char,104>, T1=boost::mpl::integral_c<char,101>, T2=boost::mpl::integral_c<char,108>, T3=boost::mpl::integral_c<char,108>, T4=boost::mpl::integral_c<char,111>, T5=boost::mpl::integral_c<char,32>, T6=boost::mpl::integral_c<char,119>, T7=boost::mpl::integral_c<char,111>, T8=boost::mpl::integral_c<char,114>, T9=boost::mpl::integral_c<char,108>, T10=boost::mpl::integral_c<char,100>, T11=boost::mpl::char_<33> ] io\match_pass.cpp(59) : see reference to class template instantiation 'boost::mpl::c_str<Sequence>' being compiled with [ Sequence=hello2 ] Is this a known bug? Best, _____________________ Vicente Juan Botet Escribá http://viboes.blogspot.com/

3 13

[msm] Event deferring causes stack overflow
by Richard Szabo 09 Nov '10

09 Nov '10

Hi All We have found a serious problem in msm back end for event deferring. I case there is a composite state and the outer state machine defers 2 events when it is in the composite state, the 1st event deferred fine in the deferred queue of the outer state machine. Than the 2nd event is processed and this is deferred as well as a part of this deferral msm back end dispatches the 1st event but it is still deferred and saved again in the deferred queue but than msm processes the deferred queue again as an action of the deferral of the 1st event and dispatches the 2nd event again which is deferred and the cycle repeats itself until the system runs out of call stack. please find the code to reproduce the problem in attachment. thanks for the help in advance. Br. Richie

1 0

Boost and (Microsoft's) _SECURE_SCL
by Martin B. 09 Nov '10

09 Nov '10

Boost and Microsoft's _SECURE_SCL Long story short of this post: Are there any plans (left) to add additional name mangling to the boost libs on Windows to address the problem of mismatched _SECURE_SCL setting? The Microsoft (Dinkumware) _SECURE_SCL=1 macro [1],[2] adds additional checks to standard library iterators/containers, rendering them ABI incompatible with _SECURE_SCL setting 0 vs. 1. This in turn leads to crashes when using a wrong combination of this flag. For example: [3] This has been discussed numerous times before: [4], [5], [6] -- see [5] for a list of further links to more threads. A trac issue [7] to add a specific build option has been closed as invalid. What I have been unable to determine is what the status is on supporting an additional *name mangling scheme* for the _SECURE_SCL option. From what I can discern from the current Getting Started page [8], not only do we not support any such name mangling, but the _SECURE_SCL macro (or the new _ITERATOR_DEBUG_LEVEL macro in VS2010) is not even mentioned on the Getting Started page. Since Visual Studio 2005 defaulted to _SECURE_SCL=1 and boost just uses the default, many people hit this when they used _SECURE_SCL=0 to improve performance in their release builds. (Which, as an aside, doesn't yield too much, as the real showstopper is the - independent! - _HAS_ITERATOR_DEBUGGING macro and that is only active in debug builds anyway.) In Visual Studio 2010, the situation is reversed, as Microsoft decided to now default to _SECURE_SCL=0. That means the people who change it to 1 in their release build for additional security will be bitten by the problem. (Or not, as it seems that they added some link-time checks in VS2010 to detect mismatches regarding the _ITERATOR_DEBUG_LEVEL. [9]) OK, so now again: Are there any plans (left) to add additional name mangling to the boost libs on Windows to address the problem of mismatched _SECURE_SCL setting? -- Or are we just going to ignore the issue since VS2010 defaults to the "boost preferred" - off - option now anyway? By "boost preferred" I mean that from some of the discussions it seemed to me that there was doubts w/rgd to complexity issues etc. when _SECURE_SCL is on. cheers, Martin p.s.: FWIW, here's how /I/ compile my release version of boost 1.44 on VS2005: bjam.exe --build-type=complete variant=release toolset=msvc-8.0 threading=multi define=_SECURE_SCL=0 --with-regex --with-program_options --with-test --with-serialization stage [1] Visual Studio 2005 - _SECURE_SCL : http://msdn.microsoft.com/en-us/library/aa985896%28VS.80%29.aspx [2] Visual Studio 2010 - _SECURE SCL : http://msdn.microsoft.com/en-us/library/aa985896%28v=VS.100%29.aspx [3] access violation with _SECURE_SCL turned off : http://lists.boost.org/boost-users/2009/02/45137.php [4] _SECURE_SCL for msvc (2009) : http://thread.gmane.org/gmane.comp.lib.boost.devel/185898/focus=185987 [5] MSVC _SECURE_SCL causes ABI change, ODR violation - mangle library names? : http://lists.boost.org/boost-users/2008/10/41253.php [6] Re: Bug/Incompatibility: Visual C++ 2005 checkediteratorslead to major crashes : http://thread.gmane.org/gmane.comp.lib.boost.devel/144082/focus=144089 [7] Add build option to define _secure_scl=0 + add runtime check to ensure no ODR violation : https://svn.boost.org/trac/boost/ticket/2086 [8] Boost 1.44 Getting Started on Windows : http://www.boost.org/doc/libs/1_44_0/more/getting_started/windows.html [9] Visual STuduio 2010 - detect_mismatch : http://msdn.microsoft.com/en-us/library/ee956429.aspx

5 11

encryption?
by Brian Wood 09 Nov '10

09 Nov '10

I recall a few threads on the subject of a fledgling Boost Encryption library, but haven't seen anything about it recently. Could someone update me on this? I've used OpenSSL enough to desire a C++ alternative. (Imagine some existing Boost libs written in C.) -- Brian Wood Ebenezer Enterprises http://webEbenezer.net (651) 251-9384 "The kingdom of heaven is like a treasure hidden in the field, which a man found and hid again; and from joy over it he goes and sells all that he has and buys that field."

1 0

[function] new implementation
by Domagoj Saric 09 Nov '10

09 Nov '10

Hi, <...those that followed the latest function related discussions can skip the first paragraph...> For about a year and half now (or even more but that's about how long I've been involved in the matter) there have been repeated discussions/requests/complaints about various aspects of Boost.Function. Most of those fall into one or more of these categories: - overall code speed overhead - overall code bloat overhead - lack of configurability - dependencies on RTTI and exception handling with the most frequently brought up specific issue being the various implications (in all of the above mentioned areas) of the hardcoded throw-on-empty behaviour... Unfortunately Boost.Function code remained virtually unchanged (except for the added RTTI emulation for platforms w/o RTTI support) with all of the issues still remaining... The new implementation proposal @: https://svn.boost.org/svn/boost/sandbox/function/boost/function http://www.boostpro.com/vault/index.php?&direction=0&order=&directory=Funct… Objects solves or at least provides drastic improvements for all of the mentioned issues. It is intended as a drop in replacement for the current implementation and as such I have so far tested it in the following ways: - compiling some real world code: VC10, GCC 4.2.1, LLVM-GCC 4.2.1, GCC 4.5.1, GCC 4.6, Clang 2.0, Clang 2.8 - compiling and running a real world project: VC10, Clang 2.8 - building Boost trunk: VC10, GCC 4.2.1, GCC 4.5.1, Clang 2.0 - running Boost regression tests for Function, Signals, Signals2, Thread, Program Options and Graph libraries: VC10, GCC 4.2.1, Clang 2.0. (All of the tests passed except for two bogus assertion failure boxes that pop up with VC10 and the Program Options tests during the automated regression test procedure that OTOH do not popup when I run the same tests manually through the VC10 IDE, i.e. the tests finish successfully...I tried to make sure all the relevant compiler switches were the same in both cases so I am out of ideas what else can make the difference.....) Next, let me give you a comparison of for-size-optimized code generated by VC10 with both the current and the proposed implementation for a short code snippet demonstrating invocation, construction and assignment: struct X { int foo( int const x ) const { return x + y; }; int y; }; int main( int /*argc*/, char * * /*argv*/ ) { using namespace boost; X x; function<int(int)> foof( boost::bind( &X::foo, &x, _1 ) ); foof( 0 ); function<int(int)> barf; barf = foof; barf( 1 ); return 0; } Notice in new_function_code_listing.txt how all of the wrapper code in the new Function was completely transparent to the compiler and was completely inlined to relatively simple machine code with direct calls to/through the vtable pointers...while OTOH in current_function_code_listing.txt the code generated for the "barf = foof;" assignement alone is several times larger than the entire code generated for the new Function implementation. The small asm snippet of the generated invoker/'thunk'/'trampoline' code also demonstrates the effects of various tweaks done to minimize or all together remove the need for any stack adjustment on the invoker side... The new implementation of course has the same semantics and exception safety guarantee levels as the original/current one. Listing all of the improvements and detailed implementation changes here in the first post would be quite cluttering as they are quite numerous. Those that desire more tests and details right now, can follow this trail: http://lists.boost.org/Archives/boost/2010/01/160908.php As for the dependencies issue this is solved in several ways: - use of exception handling: new code uses guard objects instead of explicit exception handling and provides a way to change on-empty-behaviour so that the EH code/dependency can easily be removed/disabled - use of RTTI (for getting the type of the stored function object): this can be globally disabled with the BOOST_FUNCTION_NO_RTTI macro. BOOST_NO_RTTI is not used for this purpose for backward compatibility reasons: in the current implementation it actually turns on RTTI emulation...The idea is to also add per instantiation RTTI on-off configurability... 'Configurability' will probably be the most controversial issue/change because it required the addition of an extra template parameter through which an MPL list of policies can be specified at compile-time. This parameter is properly defaulted to allow existing code to compile without changes while providing current Boost.Function behaviour (e.g. on-empty- behaviour). As all the performed tests showed this to also be true in practice the proposed code should IMO go in as a straight drop-in replacement but, of course, I might have missed some important higher level detail/concern so this is open to discussion... Currently two policies are supported: - on throw behaviour (with throw-on-empty, nop-on-empty and assert-on-empty handlers provided) - whether the function instantiation should mark itself (i.e. its operator()) as nothrow. Additional policies my be added later, for example: - sizeof and/or alignment of the SBO buffer - default allocator - per instantiation RTTI on/off ... Finally, there is one more addition, somewhat 'unholy' as it brings in the concept of binding into Boost.Function but considering its efficiency and/or verbosity benefits (and the fact that the first issue can be 'explained away' by saying that this is not actually 'binding' but a workaround for the lack-of-delegates-support C++ language deficiency). The addition is in the form of two more assign() member function overloads (one for a free function that has the exact signature as the Boost.Function instantiation, and one for a member function that has a matching signature with the addition of a this pointer) that allow assignment of (suitably typed) plain (free or member) functions specified as non-type-template parameters. This allows for the removal of the extra indirect-call-through-function-pointer otherwise incurred by traditional assignment of function pointers (not functors), which is actually a rather common use case. For example, in the above example given, one can now write: foof.assign<X, &X::foo>( x ); and get a trivial invoker with the X::foo() target function inlined straight in... -- "What Huxley teaches is that in the age of advanced technology, spiritual devastation is more likely to come from an enemy with a smiling face than from one whose countenance exudes suspicion and hate." Neil Postman

7 27

Will test/doc be merged?
by Jim Bell 08 Nov '10

08 Nov '10

Looks like a lot of changes to test/doc and subdirectories were committed to the trunk on 6/10/2010. They fix at least one problem I saw. (doc/html/index.html, BOOST_TEST_PASSPOINT points to "Logging floating point type numbers", which is in the mis-named file BOOST_TEST_PASSPOINT.html.) Anyone know the status? Can it be merged into the release?

1 0

[multi_index] scalar insert interface
by Maxim Yegorushkin 08 Nov '10

08 Nov '10

Hey guys, In ordered_index there are two scalar insert overloads: std::pair<iterator,bool> insert(const value_type& x); iterator insert(iterator position,const value_type& x); The second version is lacking the bool result, which is sometimes required. In my source code of boost-1_42 I patched the second version like this: ==== .../ordered_index.hpp#2 (text) ==== @@ -97,6 +99,16 @@ struct ordered_unique_tag{}; struct ordered_non_unique_tag{}; +template<class T, class U> +struct auto_cast_pair : std::pair<T, U> +{ + typedef std::pair<T, U> base_pair; + auto_cast_pair(base_pair const& b) : base_pair(b) {} + using base_pair::operator=; + operator T&() { return this->first; } + operator T const&() const { return this->first; } +}; + template< typename KeyFromValue,typename Compare, typename SuperMeta,typename TagList,typename Category @@ -274,14 +286,14 @@ return std::pair<iterator,bool>(make_iterator(p.first),p.second); } - iterator insert(iterator position,value_param_type x) + auto_cast_pair<iterator,bool> insert(iterator position,value_param_type x) { BOOST_MULTI_INDEX_CHECK_VALID_ITERATOR(position); BOOST_MULTI_INDEX_CHECK_IS_OWNER(position,*this); BOOST_MULTI_INDEX_ORD_INDEX_CHECK_INVARIANT; std::pair<final_node_type*,bool> p=this->final_insert_( x,static_cast<final_node_type*>(position.get_node())); - return make_iterator(p.first); + return std::pair<iterator,bool>(make_iterator(p.first),p.second); } template<typename InputIterator> Now it automatically figures which return value one wants. Just an idea. -- Max

4 5

[mpl] map insert
by vicente.botet 08 Nov '10

08 Nov '10

Hi, in /libs/mpl/doc/refmanual/map.html insert<m,x>::type point to the description of insert<m,pos,x>::type. In addition I don't find the descrition of insert<m,x>::type in libs/mpl/doc/refmanual/intrinsic-metafunctions.html Can this be added? Best, _____________________ Vicente Juan Botet Escribá http://viboes.blogspot.com/

2 2

Re: [boost] [Boost-commit] svn:boost r66442 - in trunk/boost: math/tools test test/impl
by Jürgen Hunold 08 Nov '10

08 Nov '10

Hi ! On Sunday, 7. November 2010 21:05:06 admin(a)thefireflyproject.us wrote: > Author: wash > Date: 2010-11-07 15:05:04 EST (Sun, 07 Nov 2010) > New Revision: 66442 > URL: http://svn.boost.org/trac/boost/changeset/66442 > > Log: > Clang hand-holding, mostly for issues caused by Clang defining GCC macros. I do not think that removing the inclusion of "fenv.h" for clang is the right solution. According to http://llvm.org/bugs/show_bug.cgi?id=6907 it is a known compiler bug that clang fails to correctly load "fenv.h" in certain environments (several gcc versions installed...) I've been working around this by simply adding (see below) > Text files modified: > trunk/boost/math/tools/config.hpp | 2 +- > trunk/boost/test/execution_monitor.hpp | 15 ++++++++------- > trunk/boost/test/impl/execution_monitor.ipp | 18 +++++++++--------- > 3 files changed, 18 insertions(+), 17 deletions(-) > > Modified: trunk/boost/math/tools/config.hpp > =========================================================================== > === --- trunk/boost/math/tools/config.hpp (original) > +++ trunk/boost/math/tools/config.hpp 2010-11-07 15:05:04 EST (Sun, 07 > Nov 2010) @@ -255,7 +255,7 @@ > } // namespace tools > }} // namespace boost namespace math > > -#if (defined(__linux__) && !defined(__UCLIBC__)) || defined(__QNX__) || > defined(__IBMCPP__) +#if (defined(__linux__) && !defined(__UCLIBC__) && > !defined(__clang__)) || defined(__QNX__) || defined(__IBMCPP__) > > #include <fenv.h> #if defined(__clang__) #include </usr/include/fenvh.> #else for my local working copies. > return ~old_cw & BOOST_FPE_ALL; > -#elif defined(__GLIBC__) && defined(__USE_GNU) > +#elif defined(__GLIBC__) && defined(__USE_GNU) && !defined(BOOST_CLANG) > > ::feclearexcept(BOOST_FPE_ALL); And this actually removes fp-Support from Boost.Test. Not good. Please find a better solution. And/Or mark the relevant places with Todo containing a reference to the clang bug report. Yours, Jürgen -- * Dipl.-Math. Jürgen Hunold ! Ingenieurgesellschaft für * voice: ++49 511 262926 57 ! Verkehrs- und Eisenbahnwesen mbH * fax : ++49 511 262926 99 ! Lister Straße 15 * juergen.hunold(a)ivembh.de ! www.ivembh.de * * Geschäftsführer: ! Sitz des Unternehmens: Hannover * Prof. Dr.-Ing. Thomas Siefer ! Amtsgericht Hannover, HRB 56965 * PD Dr.-Ing. Alfons Radtke !

3 4

[mpl] What about wstring, u16string and u32string
by vicente.botet 08 Nov '10

08 Nov '10

Hi, I was considering to use mpl::string to implement chrono_io but I see that there are not the couterparts wstring, u16string and u32string. Without these classes I could not use the mpl strings. Is there a possibility to add these classes to Boost.Mpl? Best, _____________________ Vicente Juan Botet Escribá http://viboes.blogspot.com/

3 2

Re: [boost] [Boost-commit] svn:boost r66441 - in trunk/tools/build/v2: . engine/src engine/src/modules tools
by Jürgen Hunold 08 Nov '10

08 Nov '10

Hi ! On Sunday, 7. November 2010 20:51:11 admin(a)thefireflyproject.us wrote: > Modified: trunk/tools/build/v2/engine/src/modules/order.c > =========================================================================== > === --- trunk/tools/build/v2/engine/src/modules/order.c (original) +++ > trunk/tools/build/v2/engine/src/modules/order.c 2010-11-07 14:51:05 > EST (Sun, 07 Nov 2010) @@ -50,8 +50,8 @@ > > if (colors[adjacent_vertex] == white) > do_ts(graph, adjacent_vertex, colors, result_ptr); > - else if (colors[adjacent_vertex] == gray) > - ; /* This is loop. Not sure what to do... */ > + //else if (colors[adjacent_vertex] == gray) > + //; /* This is loop. Not sure what to do... */ > } > colors[current_vertex] = black; > **result_ptr = current_vertex; Are you sure that you really wanted to commit this ? Yours, Jürgen -- * Dipl.-Math. Jürgen Hunold ! Ingenieurgesellschaft für * voice: ++49 511 262926 57 ! Verkehrs- und Eisenbahnwesen mbH * fax : ++49 511 262926 99 ! Lister Straße 15 * juergen.hunold(a)ivembh.de ! www.ivembh.de * * Geschäftsführer: ! Sitz des Unternehmens: Hannover * Prof. Dr.-Ing. Thomas Siefer ! Amtsgericht Hannover, HRB 56965 * PD Dr.-Ing. Alfons Radtke !

3 3

Re: [boost] [ptr_container] [1.45] you own a showstopper
by Thorsten Ottosen 07 Nov '10

07 Nov '10

Den 07-11-2010 23:05, Eric Niebler skrev: > Thorsten, > > The following bug in ptr_container is marked as a Showstopper for the > 1.45 release. What are your plans for it? If you're planning on fixing > it, can you do so soon? If you feel it is not a showstopper, can you set > its priority appropriately? > > https://svn.boost.org/trac/boost/ticket/4598 Should hav been fixed for a day or more. -Thorsten

2 2

[ptr_container] [1.45] you own a showstopper
by Eric Niebler 07 Nov '10

07 Nov '10

Thorsten, The following bug in ptr_container is marked as a Showstopper for the 1.45 release. What are your plans for it? If you're planning on fixing it, can you do so soon? If you feel it is not a showstopper, can you set its priority appropriately? https://svn.boost.org/trac/boost/ticket/4598 Thanks, -- Eric Niebler BoostPro Computing http://www.boostpro.com

1 0

[property_tree] [1.44] you own a showstopper
by Eric Niebler 07 Nov '10

07 Nov '10

Sebastian, The following bug in property_tree is marked as a Showstopper for the 1.44 release. What are your plans for it? If you're planning on fixing it, can you do so soon? If you feel it is not a showstopper, can you set its priority appropriately? Thanks, -- Eric Niebler BoostPro Computing http://www.boostpro.com

1 1

[function] does calling boost::function from boost::function involve nested virtual calls?
by Mostafa 07 Nov '10

07 Nov '10

Hi all, Correct me if I'm wrong, using boost::function involves a virtual function call. If so, then does nesting boost::function calls result in nested (multiple) virtual function calls? For example: int foo(float); boost::function<int (float)> f1 = foo; boost::function<double (int)> f2 = f1; Does f2(5) result in two virtual functions being called on the part of boost::function? (I couldn't find the answer in the documentation and reading the source code I got lost in the macros.) Thanks, Mostafa

2 1

[build] print test failing on release
by Eric Niebler 06 Nov '10

06 Nov '10

Volodya, can you investigate the failure of the Boost.build "print" test on the release branch? It's currently failing across all platforms. Thanks, -- Eric Niebler BoostPro Computing http://www.boostpro.com

2 3

[type traits] is_virtual_base_of causes C4250 (class inherits member via dominance) with VS 2005
by Martin B. 06 Nov '10

06 Nov '10

Hi! I didn't find any references to this, so I thought I'd let you know that boost::is_virtual_base_of<Base, Derived> will cause (harmless) C4250 when evaluating to true. (VC++ 2005) I hit this when using the BOOST_CLASS_EXPORT macro from Boost.Serialization, as this uses is_virtual_base_of internally. cheers, Martin ps: For code see: http://stackoverflow.com/q/4091166/321013

3 2

[icl/itl] Interval Container Library ready for inclusion
by Joachim Faulhaber 06 Nov '10

06 Nov '10

Dear list! After the review of the Interval Template Library in February and its acceptance for inclusion, I worked on a number of suggestions and proposals from the reviewers, in order to improve the design and quality of the library. The library is now renamed to Boost.Icl: Interval Container Library. I have completed a release icl-4.0.0, where those suggestions are implemented. Apart from typos and flaws in the docs that might be there after renaming, this will be the version for inclusion into the next boost release (1.46.0). The now renamed library has a new path in the sandbox: https://svn.boost.org/svn/boost/sandbox/icl/ The sources are also in the vault http://www.boostpro.com/vault/index.php?&direction=0&order=&directory=Conta… and on sourceforge (extended version) http://sourceforge.net/projects/itl/ The BoostBook docs are online available here: http://www.joachim-faulhaber.de/boost_icl/doc/libs/icl/doc/html/index.html Many of the proposals from the reviewers were agreed upon during the discussion on the library. In particular I took into account suggestions by Jeff Flinn (JF), Luke Simonson (LS), Barend Gehrels (BG), Vicente Botet (VB), Thomas Klimpel (TK), Paul A. Bristow (PB), Robert Stewart (RS), John Reid (JR) and Markus Werle (MW). Some suggestions by Phil Endecott, Jerry Jeremiah, Brian Wood, Barend Gehrels, Luke Simonson and John Reid are not or not yet implemented for different reasons but they may be considered for the future evolution of the library. * The library has been renamed from Interval Template Library (ITL) to Interval Container Library (ICL) Its namespace is now icl instead of itl. (Renaming was suggested by MW). * Introduction of dynamically bounded and statically bounded intervals (JF,JR,VB) + The 'universal' interval class itl::interval has been replaced by + dynamically bounded discrete_interval and continuous_interval http://www.herold-faulhaber.de/boost_icl/doc/libs/icl/doc/html/boost_icl/ex… + statically bounded right_open_interval, left_open_interval closed_interval and open_interval and a uniform set of namespace global functions or interval_concept for them. Statically bounded intervals don't carry information about their interval bounds and use less memory. (JF,JR) http://www.herold-faulhaber.de/boost_icl/doc/libs/icl/doc/html/boost_icl/ex… + The interval class templates are now quite small. The functions are namespace global functions that make up an interval concept (JF,LS) + Added functions 'distance' and 'inner_complement' for intervals.(JR) http://www.herold-faulhaber.de/boost_icl/doc/libs/icl/doc/html/boost_icl/fu… * User defined interval types are now customizable (JF) + An interval_traits and dynamic_interval_traits template describes the generic properties of the interval concept ... + and allows to customize the icl library for user defined interval types. http://www.herold-faulhaber.de/boost_icl/doc/libs/icl/doc/html/boost_icl/ex… * Extraction of namespace global functions. (LS,JF,RS) + Member functions have been extracted form class templates as long as they are not needed to maintain type invariants. + The sets of namespace global functions build concepts icl::element_set, icl::element_map, icl::interval_set, icl::interval_map + Some functions have been renamed to conform existing standards (ISO/OGC). (BG) + std::set and other stl conformant set types are models of the icl's element_set concept. Class template icl::set has been removed. + Member functions for element iterations are extracted from the interval container class templates. (LS) * Names, referred to as 'colorful terminology' have been renamed (TK,VB,PB) + neutron -> identity_element + unon -> unit_element + ... and also their occurrence in composite identifiers If you find bugs in the library or typos or other flaws in the docs, please let me know so I can fix them before inclusion of the library into the next boost release. Enjoy, Joachim

5 4

bjam in lib/<x>/test is equivalent to run.py
by Jim Bell 06 Nov '10

06 Nov '10

Compelled as I am to audit everything, I had to compare running bjam in the lib/<x>/test directory with run.py. I'm confident that they do produce (essentially) the same compile, link, and execute commands. Notes, from a regression-runner's POV: * They use different directories: run.py uses {boost-root}/../results/bin.v2/..., and bjam uses {boost-root}/bin.v2/... * run.py sets up bjam with a lot of flags, like --debug-configuration [shouldn't matter for most people] -d2 [important for many, described below] -lxxx [that's lower-case L, with a time-out in seconds: potentially important] preserve-test-targets=off [not sure if this matters or not] * run.py runs from the boost/status directory, I think. Might matter for some tests. Not sure about straight bjam. To make your own script to rebuild/rerun a particular test, run bjam with -d+2 (i.e., -d2) and direct the output to a file. Then copy the compile & link commands out of that file. The -lxxx command (e.g., -l120) matters if a test could hang (e.g., <https://svn.boost.org/trac/boost/ticket/4766>).

3 5

Re: [boost] [Boost-users] [icl/itl] Interval Container Library ready for inclusion
by Joachim Faulhaber 05 Nov '10

05 Nov '10

2010/11/5 Jeff Flinn <TriumphSprint2000(a)hotmail.com>: > Hartmut Kaiser wrote: >>> >>> After the review of the Interval Template Library in February and its >>> acceptance for inclusion, I worked on a number of suggestions and >>> proposals from the reviewers, in order to improve the design and quality >>> of the library. The library is now renamed to Boost.Icl: Interval >>> Container Library. >>> >>> I have completed a release icl-4.0.0, where those suggestions are >>> implemented. Apart from typos and flaws in the docs that might be there >>> after renaming, this will be the version for inclusion into the next >>> boost >>> release (1.46.0). >>> >>> The now renamed library has a new path in the sandbox: >>> https://svn.boost.org/svn/boost/sandbox/icl/ >>> >>> The sources are also in the vault >>> >>> http://www.boostpro.com/vault/index.php?&direction=0&order=&directory=Cont >>> ainers >>> >>> and on sourceforge (extended version) >>> http://sourceforge.net/projects/itl/ >>> >>> The BoostBook docs are online available here: >>> >>> http://www.joachim-faulhaber.de/boost_icl/doc/libs/icl/doc/html/index.html >> >> Joachim, that's great news. Many people are waiting for this! > > Awesome! I'm looking forward to working with the final result. > >> Why don't you just go ahead and move everything into Boost trunk. That >> does >> not disrupt any release procedures, but gives you the benefit of running >> the >> tests on a daily basis on a broad range of platforms. Additionally it >> simplifies things for people working from Boost SVN trunk wanting to use >> your library. > > Yep, that would be great. Thank you all for your welcoming remarks on the new version of the Interval Container Library. Yes, I am prepared to move this version of the ICL into the Boost trunk, but I don't have write permission yet. How do I get it? Are there any special policies to follow when working with the Boost trunk? Best regards, Joachim

2 1

[Boost.config] User.hpp for new PGI 10.9 compiler
by K. Noel Belcourt 05 Nov '10

05 Nov '10

Hi, Can a Boost.config developer take a look at the attached user.hpp generated by the configure script for the pgi-10.9 toolset? Are there any obvious changes necessary to boost/config/compiler/pgi.hpp? Thanks. -- Noel

2 5

Best method of checking for ==, <, streamability
by Christopher Jefferson 05 Nov '10

05 Nov '10

A user recently posted on boost-users asking for operator== support in boost::any. I have added this support to my private version, which extends spirit's implementation of any. I am interested in cleaning this up and submitting it to replace boost::any, if everyone is happy with this. The major issue is that my implementation requires type support operator==, operator< , hash and operator<< / operator>>. Are there any techniques in boost for detecting the presence of these operators which are sufficiently reliable they could be used in boost::any? Apologises for this question, but I have lost track of how well such checks can be implemented. Thanks, Christopher Jefferson

5 4

How about a call for bug-fix volunteers?
by Jim Bell 05 Nov '10

05 Nov '10

Library authors shouldn't have to bear the burden of bug reports for their libraries alone. Even maintaining their regression tests across all platforms isn't realistic (and isn't being done). So what if we try to recruit a couple helpers for each library? I see two avenues where we can use some volunteer help to improve boost's quality. 1. Dandelion pickers: look at failed/yellow regression tests and try to fix them. Volunteers could pick a platform they have access to, and try to work across all libraries. You might be surprised at how easy many are to fix. 2. Ticket triage: pick a library and go through all open tickets. Change severity, resolve, request more information, try to map to an existing regression test, interact with the submitter in the comments. (I think Trac needs a "requesting more information" state.) Even a brief 'triage' on each would be helpful, and help users feel they're being heard. (Trac needs to track this, too.) Write new regressions from legitimate issues. Recruiting pitch: it's a great way to improve your skills--troubleshooting, C++, platform-specific expertise, communication. Not so glamorous, but important and great experience. Perhaps we could assign a little of each to each SoC person. Maybe put the word out on Slashdot. See previous topic threads (http://lists.boost.org/Archives/boost/2010/10/index.php) "Report # 29 (aka 1.45 blockers) is too narrow" "[1.45] Beta final schedule" "[1.45] Thread issues"

14 18

Named subexpressions using \k<name>
by Chris Dragon 04 Nov '10

04 Nov '10

I have a user who says they have a bunch of expressions written for the Oniguruma regex library that use \k<name> syntax. According to http://www.boost.org/doc/libs/1_44_0/libs/regex/doc/html/boost_regex/syntax… Boost.regex should also support that syntax, but it does not seem to work. For example: boost::regex_replace( std::string("xyyz"), boost::regex(".*(?<first>x)(?<second>y).*", boost::regex_constants::perl), std::string("$+{second}\\k<first>"), boost::match_default | boost::format_all | boost::match_extra); results in "yk<first>" This result shows that $+{second} evaluated to "y" but \k<first> evaluated to "k<first>". I thought maybe the \k<name> syntax was only supported as a backreference within the first regex instead of the replace string, but this doesn't work either: boost::regex_replace( std::string("xyyz"), boost::regex(".*(?<first>x)(?<second>y)\\k<second>.*", boost::regex_constants::perl), std::string("$+{second}"), boost::match_default | boost::format_all | boost::match_extra); The result is "xyyz" meaning nothing was replaced (the regex did not match). However, if modify the regex to use \\g{name} syntax, it works: boost::regex_replace( std::string("xyyz"), boost::regex(".*(?<first>x)(?<second>y)\\g{second}.*", boost::regex_constants::perl), std::string("$+{second}"), boost::match_default | boost::format_all | boost::match_extra); The result is "y". Am I doing something wrong or have I found a bug? I'm using the latest stable 1_44_0 release compiled from source in VC9 and I also tried the pre-compiled library (http://sourceforge.net/projects/boost/files/boost-binaries/1.44.0/libboost_…) The OS is Windows 7. Thanks for the help!

2 2

[Boost.Timer] Why timer doesn't have a specific windows version using QueryPerformanceCounter() and QueryPerformanceFrequency()?
by dlaugt＠free.fr 04 Nov '10

04 Nov '10

Hi, Boost.Timer is based on the C function clock(). On windows, this function gives a precision of 1 millisecond only as CLOCKS_PER_SEC is equal to 1000. Why Boost.Timer doesn't use for windows QueryPerformanceCounter() and QueryPerformanceFrequency()? These functions give a precision around 2 microseconds. Daniel.

3 2

[build][doc] Testing section and run rule
by Mateusz Loskot 04 Nov '10

04 Nov '10

Hi, I'm looking for reference about run rule and the only thing I can find is this short reference: http://www.boost.org/doc/tools/build/doc/html/bbv2/reference/rules.html pointing to the Testing section which is currently blank: http://www.boost.org/doc/tools/build/doc/html/bbv2/tutorial/testing.html Would there be any chance to get this part updated? I'm looking for details about the run rule arguments: rule run ( sources + : args * : input-files * : requirements * : target-name ? : default-build * ) I'd appreciate if someone could explain what is the differences: sources vs input-files or args vs input-files. Best regards, -- Mateusz Loskot, http://mateusz.loskot.net Charter Member of OSGeo, http://osgeo.org Member of ACCU, http://accu.org

2 2

gcc-4.5.1 warnings (ISO C++ 1998 does not support ‘long long’)
by Neal Becker 03 Nov '10

03 Nov '10

boost-1.44.0 + gcc-4.5.1: Lots of these warnings ./boost/config/suffix.hpp:497:18: warning: ISO C++ 1998 does not support ‘long long’

2 1

Will 1.45 incorporate active regression tickets?
by Jim Bell 03 Nov '10

03 Nov '10

Will 1.45 incorporate active regression tickets? I.e., report {30} <https://svn.boost.org/trac/boost/report/30> Several of these could be incorporated without too much work. I think a scan of these would be worth the release managers' time.

3 9

Unicode Library
by Emery Denuccio 02 Nov '10

02 Nov '10

Hey guys, about three years ago I mentioned I was working on a unicode library for boost and there was some interest then. I guess professional work got in the way and I never got around to polishing it up and submitting for review. I was digging through an old hard drive and found the source. It still lacks a few features, but is pretty damn cool. I threw up on on github if anyone wants to take a look and possibly help me get rolling on it again. Here: http://github.com/imori/boost.unicode Thanks, -em

3 2

[chrono] review version
by vicente.botet 02 Nov '10

02 Nov '10

Hi, I have made some modifications to Boost.Chrono before the review (Version 0.7.0). The library can be downloaded from http://www.boostpro.com/vault/index.php?action=downloadfile&filename=chrono… and the documentation is online on the sandbox http://svn.boost.org/svn/boost/sandbox/chrono/libs/chrono/doc/html/index.ht… or in PDF format http://svn.boost.org/svn/boost/sandbox/chrono/libs/chrono/doc/chrono.pdf Boost.Chrono depends on Boost.Ratio http://www.boostpro.com/vault/index.php?action=downloadfile&filename=ratio.… and optionaly Boost.System Header Only http://www.boostpro.com/vault/index.php?action=downloadfile&filename=system…. Next follows the major changes: [*Features:] * Boost_Chrono is now a configurable header only lib that allows the user to choose in addition if the windows file is included or not. * Added clock_string<> traits. * Define chrono_io for all the clocks * Add input of process_times representation [*Implementation:] * Moved some details to static_integer directory. * Use of detail/win files to avoid the use of windows.h file. * Completed the error_code handling. * Works now with BOOST_SYSTEM_NO_DEPRECATED. [*Fixes:] * Fix some warnings. * Fix original error on Mac * Don't fix the link with boost_system to static. [*Test:] * Added test on process and thread clocks. * Moved to lightweight_test.hpp. * Able to test multiple configurations. [*Doc:] * Removed some not useful parts as the history, the test and the tickets. Best, _____________________ Vicente Juan Botet Escribá http://viboes.blogspot.com/

2 2

[iostreams] Inconsistency of "faiture" of writes in Sinks and filters
by Artyom 02 Nov '10

02 Nov '10

Hello, I implement the sink device that sometimes may fail on writes. When Sink is implemented it should throw an exception on fault. To notify the stream on error. However it is not always works this way. I've got the exception to "leak" to the main program when I combine in the filter gzip_comressor() filter that writes to output device that its Sink is full. When I call reset on the filter the exception in leaking to the program instead of being caught. Is it bug or (accidental) feature? On the other hand, if I don't throw but rather return 0, I get into infinite loop in the boost::iostreams::non_blocking_adapter::write when I call filter.reset(). So I how can I write a sink device that reports errors? In following example the exception is caught when filter.reset() is called: #include <boost/iostreams/stream.hpp> #include <boost/iostreams/filtering_stream.hpp> #include <boost/iostreams/filter/gzip.hpp> #include <boost/iostreams/tee.hpp> #include <iostream> class my_small_device : public boost::iostreams::sink { int count; public: my_small_device() : count(1000) {} std::streamsize write(char const *d,std::streamsize n) { if(count < n) throw std::runtime_error("Device is full"); count-=n; return n; } }; int main() { try { using namespace boost::iostreams; boost::iostreams::stream<my_small_device> output(my_small_device(),10); { boost::iostreams::filtering_ostream filter; filter.push(gzip_compressor()); filter.push(output); for(int i=0;i<10000000;i++) { if(!(filter << i << '\n')) { std::cerr << "Fail!" << std::endl; break; } } std::cout << "Closing filter" << std::endl; filter.reset(); } std::cout << "ok" << std::endl; return 0; }catch(std::exception const &e) { std::cerr << "Catched " << e.what() << std::endl; return 1; } } Thanks, Artyom

1 2

Issues with intel's compiler and newer builds of GCC
by Bryce Lelbach 02 Nov '10

02 Nov '10

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 While working on getting icc to not choke on Serialization (the Boost test boxes indicated that icc was failing to build with the addition of my changes), I came across a very nasty bug the occurs when using icc with version 4.5 or higher of GNU's standard library - GNU's <iomanip> uses what are either illegal or C++0x semantics which icc doesn't support. Serialization uses <iomanip>, and icc seems to select the latest version of libstd++ installed on a Linux machine as it's default standard library (I have been unable to find an Intel standard library - I'm assuming such a thing doesn't exist). When using an older version of libstd++, icc + Serialization compiled fine. I removed all uses of IO parameterized manipulators in Serialization (there were only maybe half a dozen cases)*, and got icc to compile Serialization with libstd++ v4.5. Is there any chance the linux/darwin Intel build bots can be set up to use libstd++ v4.4, if they're not already using it? Intel is apparently aware of this issue, but it won't be fixed until their next major release (http://software.intel.com/en-us/forums/showthread.php?t=74691) If the build bots aren't using v4.5 of GNU's standard library, then I'm at a loss as to why Serialization is failing to build on them. My only other thought is that the timeout for the build cycle is too low - the failures indicate that the error is a timeout after 300 seconds. On a more general note, is Intel on Linux/Darwin a "supported" Boost compiler? Unless I've missed something, Intel doesn't provide a standard library, and I find it a bit troubling that they ship their compiler to use GNU's standard library by default. Intel is far behind GCC in C++0x support, and newer versions of the GNU standard library have been making increasing use of GCC's C++0x support. Unless icc starts shipping with an older version of libstd++/use a compiler neutral standard library such as the Apache standard library/starts to catch up with GCC's C++0x support, I imagine that using icc to compile C++ code that makes use of the standard library will become increasing difficult. * I also had to modify proto/debug.hpp to not use <iomanip>. Eric, when I was having an issue with typeinfo in proto/debug.hpp a couple days ago, you mentioned that proto/debug.hpp shouldn't be included by proto/proto.hpp? If that's accurate, is there any chance that change could be made, and if not, can I commit my changes to proto/debug.hpp or send them to you as a patch for review? - -- Bryce Lelbach aka wash http://groups.google.com/group/ariel_devel -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAky+c7cACgkQO/fqqIuE2t4DZQCfUnhGAsqX4GDZu3Ze7BvrPBRL XRkAn33vWcTm1RuXk2iuQWH0+bp+RVUf =mHwK -----END PGP SIGNATURE-----

7 9

[build_extensions][patch] General update and minor fixes
by Mateusz Loskot 02 Nov '10

02 Nov '10

Hi, First, I'm not sure if this is the right place to send patch to the build_extensions which live in the sandbox, I'm continuing to have complete build of Boost.GIL tests on Linux with 3rd-party dependencies configured using the build_extensions. It's trial and error process during which I've applied number of updates to .jam scripts for raster support libraries. The patch summary: zlib: added/removed .c source files jpeg: added/removed .c source files libtiff: - added missing tif_unix.c for <target-os>linux (not sure why <target-os>unix: could not kick in) - configure #define integral types required by tiffiop.h - added tiffxx target with C++ wrapper library (tif_stream.cxx) I have successfully used the extensions with the following libraries: jpeg-8a libpng-1.4.1 tiff-3.9.2 zlib-1.2.4 with GCC 4.4.5 on Linux 64-bit. I'm quite sure some of the changes could be mastered in much better way, but I lack of Boost.Build zen. Best regards, -- Mateusz Loskot, http://mateusz.loskot.net Charter Member of OSGeo, http://osgeo.org Member of ACCU, http://accu.org

1 0

[gil][io_new] Problems with templates
by Christian Henning 01 Nov '10

01 Nov '10

Hi there, problems have been resolved. Thanks to everyone who tried helping! Regards, Christian

1 0

[range] - Proposal to change the indexed range adaptor
by Neil Groves 01 Nov '10

01 Nov '10

Fellow maintainers and developers, Having gained experience using the Boost.Range library changes I submitted for Boost 1.43, I have become dissatisfied with my indexed adaptor. Currently the underling index_iterator has a return type identical to the wrapped iterator, and the index is extracted via a method call on the iterator. While this works for the case where one is writing algorithms to explicitly utilise the underlying iterator, it is clearly a poor design choice since it severly limits the interoperation with other algorithms. I feel that I have made a mistake. I propose that a breaking change is made to the index range adaptor so that it returns a pair<original_reference_type, index_type>. How do you feel about this change? Do you have alternative suggestions? Regards, Neil Groves

5 7

boost::optional - rvalue references
by Daniel Larimer 01 Nov '10

01 Nov '10

I have been looking to optimize my code using rvalue references when they are supported; however, I currently use boost::optional which does not know how to handle / forward rvalue references. In fact even the in_place() utilities do not work to forward the rvalue into the proper constructor. My latest profiling shows that assigning a large vector to an optional is eating up 5% of my CPU time and I could replace this with a std::move() if boost::optional supported it. I have attached an updated optional.hpp with the minimum changes necessary to support the following: test v ( 99 ); test A ( 400 ); boost::optional<test> i2(std::move(v)); i2 = std::move(A); Such that if test were a vector and 99 and 400 were the sizes, the end result is v & A are of size 0 and i2 is of size 400 and no copy constructors are called (only moves). What is the plan for updating more of boost to take advantage of rvalue references?

2 1

Get PID from local socket?
by Rush Manbert 01 Nov '10

01 Nov '10

I am using boost ASIO to do socket communications between an app and a daemon running on the same machine. The communications go through a Unix Domain Socket on the Mac and a named pipe on Windows. I'm looking for a way that the client app could obtain the PID of the daemon process, starting with the connected socket. I have tried calling local_endpoint() and remote_endpoint(), but the only information there seems to be the socket path (at least on the Mac). My google searches have turned up nothing, and they actually suggest that there is no way to achieve this on the Mac, even if I were using the "normal" socket API. Does anyone know whether this is possible and how to do it? Thanks, Rush

2 1

[gsoc] Boost.Process done
by Boris Schaeling 31 Oct '10

31 Oct '10

Here are the results of the Boost.Process project within this year's Google Summer of Code program: We have a complete library to manage system processes now! If you like to play around with the library download the ZIP file from <http://www.highscore.de/boost/gsoc2010/process.zip>. As it's a header-only library simply copy the files to your Boost folder. If you like to quickly check the documentation click on <http://www.highscore.de/boost/gsoc2010/>. The library is now complete and basically ready for a review. As there have been so many Boost.Process drafts before (after all the first version was created 2006) this library's version number is 0.4. This will somehow make it possible to refer to the various drafts if it's necessary. For now I would appreciate if the library's test cases are run on as many platforms as possible. After copying the files from the ZIP file to the Boost folder change to libs/process/test/ and run bjam - that's all! What has been changed? * All previous Boost.Process drafts including Ilya's 2008 version from the vault have been thoroughly studied to create a better version. From the multiple Boost.Process drafts which have been floating around since 2006 we took the best ideas and created a new unified version. * The design and implementation of the library have been simplified. The library's API is smaller, and the implementation is easier to understand. It should be possible to benefit from this library as quickly as possible. Even developers who have no experience in managing system processes should be able to do so easily. * There are no POSIX and Windows specific classes anymore (posix_context, posix_child, win32_context, win32_child etc. have been dropped). Instead of trying to support each and every feature platforms provide extension points have been defined. They enable library users to "link in" those platform specific features they are interested in. * For the first time there is full support for synchronous and asynchronous operations. While asynchronous operations are built on top of Boost.Asio synchronous operations can be utilized without that library. Developers don't need to include any Boost.Asio headers and don't need to learn about Boost.Asio if they don't need asynchronous operations. * Stream behaviors define if and how standard streams can be used by a child process. While the various stream behaviors were defined as an enumeration or a boost::variant in previous Boost.Process drafts they are now implemented as classes. This makes it possible for developers to create new stream behaviors. * The code to start child processes on POSIX platforms has been carefully adapted to support multi-threaded applications (it turned out that this code was wrong in all Boost.Process drafts so far). The documentation explains what you need to take care of if you want to create child processes in a multi-threaded application on POSIX platforms. * The documentation is new and has been shortened and simplified. There is a user guide which can be read in 10 minutes and introduces all the major features of the library. The documentation is now also based on Quickbook. * The test cases have been restructured to simplify them. They can now be run without patching Boost.Test and without setting a path to a helper executable in the source files - it's now all automatic. They are all passed successfully with MSVC 9 (2008) and g++ 4.2.1. What is currently missing? * Pipelines are not (yet) supported. If you have been using boost::process::launch_pipeline() there is nothing in this Boost.Process draft you can use instead. Depending on feedback this feature will be added again (there was simply no time yet to do this). We hope that after four years, two Google Summer of Code programs and countless drafts this new version will finally become the official Boost.Process library so many have been waiting for. Boris and Felipe

18 182

[rational] PATCH: Use ordered_euclidean_ring_operators
by Mario Lang 30 Oct '10

30 Oct '10

Hi. Below is a patch which makes rational.hpp use grouped arithmetic operators. While we are at it, use ordered_euclidean_ring_operators instead of just ordered_field_operators. While it might sound strange at first, mod can make sense even for rational numbers. For instance, Common Lisp, which has a native rational type, works fine if mod is used on rational numbers... template <typename IntType> rational<IntType>& rational<IntType>::operator%= (const rational<IntType>& r) { return *this -= r * floor(rational_cast<double>(*this / r)); } I am aware that the use of floor() is probably problematic. I am all open for comments and suggestions for improvements. -- Thanks, ⡍⠁⠗⠊⠕

1 0

[graph] PATCH to eliminate gcc 4.2 warnings when compiling boost/graph/read_dimacs.hpp
by Daniel Trebbien 30 Oct '10

30 Oct '10

Attached is a patch that changes the definition of `err_message` in boost/graph/read_dimacs.hpp@66260 from: static char *err_message[] to: static const char *err_message[] This will eliminate the warnings that were recorded at: http://www.boost.org/development/tests/trunk/developer/output/Sandia-gcc-4-… Daniel

2 1

Is it time for another bug sprint? (Post 1.45 release, I mean)
by Marshall Clow 30 Oct '10

30 Oct '10

What do people think? -- Marshall

11 17

[regex] Disabling ICU check when building with bjam, 1.44
by Cliff Green 30 Oct '10

30 Oct '10

This is on Boost 1.44, g++ 4.1.2 on Linux (RHEL 5.x, can't remember the x at the moment), although it applies generally to building regex. I can't find a way to easily "disable" the "ICU installed" check and resulting functionality / build. I chatted on IRC, and the only way some (experienced Boost) developers could come up with was to change: alias icu_options : : : : [ check-target-builds has_icu : $(ICU_OPTS) : ] ; to alias icu_options : : : : ; in Jamfile.v2. My situation / use case: Our build system has ICU installed. Our deployment system has exactly the same OS and runtime environment, except that the ICU package is not installed. I would like to build regex without the "check that ICU is installed to determine whether the enable ICU" logic in the jamfiles. The regex documentation has an: "-sHAVE_ICU=1" example, but "-sHAVE_ICU=0" doesn't work, and tracing through the jamfiles / boost build I couldn't find where that option is honored / processed. There's also a BOOST_HAS_ICU macro that is defined or undefined in various ways, but adding define=BOOST_HAS_ICU 0 to bjam also didn't appear to do anything (and I tried some other ways to undefine BOOST_HAS_ICU, including in the jamfile, but nothing seemed to work). The docs also mention that the default is to not enable / build with ICU, but that doesn't seem to be the case (with 1.44). (From the first line of ICU build section: "A default build of this library does not enable Unicode support via ICU. There is no need to enable ... ".) So I'm confused (as well as some other regulars on IRC), and either the documentation needs updating, jamfiles need updating, or my understanding needs updating. For now, the workaround mentioned above works fine, and the resulting regex.so file does not have any ICU external library dependencies (which is what is desired for our deployment environment). Thanks! Cliff

2 2

[assign] list_inserter regression test failure on VC10 / release branch
by Richard Webb 30 Oct '10

30 Oct '10

Another minor regression test fix: The list_inserter regression test (libs\assign\test\list_inserter.cpp) was fixed for VC10 on the Trunk in revision 62737, but hasn't yet been merged to the release branch. (the change also fixes one of the errors from GCC/C++0x, but the test still fails for other reasons).

1 0

[1.45] Beta next week?
by Beman Dawes 30 Oct '10

30 Oct '10

I've been too busy to do much on 1.45, but don't see any reason we can't get a beta out next week more or less as scheduled. If anyone know of any showstoppers, please let us know what the problem is. Thanks, --Beman

11 35

[mpl] anyone fancy merging the for_each test to the release branch?
by Richard Webb 29 Oct '10

29 Oct '10

Does anyone feel like merging libs/mpl/test/for_each.cpp (revision 65167) to the release branch? It's only a minor change to the test itself, but it clears a failure on VC10 and various C++0x GCCs.

3 2

[quickbook] Code links not working
by Edward Diener 29 Oct '10

29 Oct '10

I can not seem to get the quickbook code links to work. Nothing is being generated from the code link. As an example, to test them out I have in quickbook: This is a test of a macro reference - [macroref VMD_DATA_SIZE Test Macro reference] . and in my doxygen generated XML I see: <library-reference id="variadic_macro_data_reference"> <title>Variadic Macro Data Reference </title> <header name="boost/variadic_macro_data/VariadicMacroData.hpp"> <macro name="VMD_DATA_SIZE" kind="functionlike"> etc. but the output shows: This is a test of a macro reference - . Any ideas to get this to work would be appreciated.

12 20

[Thread][Release] Boost.Thread and 1.45 release
by Anthony Williams 29 Oct '10

29 Oct '10

Hi, I've fixed all the outstanding "showstopper" bugs in boost.thread on trunk (including the thread interruption issue, #2330), apart from #3847 (https://svn.boost.org/trac/boost/ticket/3847) - "Unable to statically link thread lib on ia64" I don't know how to fix this, and this platform doesn't appear to be actively tested. Is it OK to merge the other fixes to the release branch? Anthony -- Author of C++ Concurrency in Action http://www.stdthread.co.uk/book/ just::thread C++0x thread library http://www.stdthread.co.uk Just Software Solutions Ltd http://www.justsoftwaresolutions.co.uk 15 Carrallack Mews, St Just, Cornwall, TR19 7UL, UK. Company No. 5478976

3 8

[constrained_value] Constrained Value review results
by Gordon Woodhull 29 Oct '10

29 Oct '10

Greetings, Substituting for Jeff Garland, I am pleased to present the results from the constrained_value review. The library is available at http://rk.dl.pl/f/constrained_value.zip The documentation is at http://rk.dl.pl/r/constrained_value Enjoy! Gordon 1. History The idea for a constrained value library goes back to at least 2004; Christopher Diggins proposed a mini-library at that time. In 2007 Joe Gottman suggested that Jeff Garland's constrained_value.hpp in date_time could be a top-level library. Concurrently, Robert Kawulak (henceforth RK) was working on his own library for the purpose, which he also started in 2004, unaware of the others. RK announced his library on November 11, 2007. Discussion continued into 2008; on June 19, RK announced his library was ready for review and it was put in the queue. The review began on December 1 2008 and continued until around December 15 (with some trailing discussion of the definition of invariant and why exceptions should not be used to check invariants). Gordon Woodhull reviewed the thread's 260 messages in the summer of 2010 and produced this report, dividing the issues raised between those where there was consensus on a change, those where no resolution was found, and those where the author and requesters (mostly) agreed that no change was needed. 2. Votes Eight people voted for acceptance of the library; there were no "no" votes. However, many people stated conditions on acceptance. Thanks to Chris (indy271828(a)sympatico.ca) Vicente Botet, Zach Laine, John Maddock, Thorsten Ottosen, Stjepan Rajko, Daryle Walker, and Gordon Woodhull for providing reviews. (In addition, Paul Bristow provided a review which looks like a yes but does not explicitly say so.) Thanks also to David Abrahams, Kim Barrett, Neal Becker, Paul Bristow, Edward Diener, Jeff Flinn, Joe Gottman, Mathias Guanard, Mika Heiskanen, Giovanni Pierro Deretta, Thomas Klimpel, Michael Marcin, OvermindDL1, John Phillips, raindog, Ravi (lists_ravi(a)lavabit.com) Johan Råde, Sebastian Redl, Peter Simons, Steven Watanabe, Utku Yaman, and Deane Yang for participating in a very active discussion. 3. Issues to be Addressed Floating point By far the most contentious issue in the review was the statement in the library documentation that floating point is not supported, and a few reviewers made fixing this a condition on acceptance. The issue is that the x87 math instructions (which are the default for 32-bit Intel compiles) utilize 80-bit registers which are then rounded down to 64 bits when a double value is written to memory. This can cause two values which were not equal to become equal later, with fairly unpredictable behavior depending on optimization and what code intervenes between calculating a value and comparing it. One solution is simply not to use the x87 math instructions by enabling the SSE2 math instructions instead. However, users may want the extra precision, and there is no way for a library to control this option. A few reviewers confused this issue with the frequent need for fuzzy comparison with epsilon; it was shown that the bug can still appear with epsilon-based comparisons. Jeff Garland points out that the Boost Numeric Interval library, http://www.boost.org/doc/libs/1_42_0/libs/numeric/interval/doc/interval.htm has also dealt with the x87 and NaN problems. It uses the round-trip-to-memory approach for x87. There is potential to create constraints for constrained_value using numeric::interval, and perhaps any other fixes for floating point belong in that library. Many solutions were proposed; after debate there were four left standing: * Force the new value to be written to memory Kim Barrett suggested the following function, noting that it should not force a memory write unless the value is in a register. inline double exact(double const& x) { return *const_cast<double const volatile*>(&x); } Gordon Woodhull has tested this against example provided by Thomas Klimpel in a message titled "floating point FUD" of January 23, 2010 (http://article.gmane.org/gmane.comp.lib.boost.devel/198817) and it does work. However, many people objected to this solution because of efficiency concerns: it requires a round-trip to memory (or at least to cache) for every assignment. * Only allow >= or <= for floating point types, and make sure the bounds are truncated 80- to 64-bit truncation can cause two values to become equal, but if one of them is already truncated, it cannot cause them to swap order. Since it is likely that the value will be changed much more frequently than the bound, it would suffice to apply truncation just to the bounds when they are set, e.g. with the exact() function above. However it does not seem that this solution can work if the bounds are dynamically calculated; the library supports bounds being returned by an inlined function. Johan Råde also suggested that it might be possible to implement < and > in terms of <= and >= and the std::nextafter function. * Force the processor to use 64-bit precision Johan Råde mentions a floating point control register which could be used in http://article.gmane.org/gmane.comp.lib.boost.devel/183760 There were also mentions of possible assembly code solutions, but none were provided and this was generally unpopular because it requires someone very knowledgeable to maintain it. John Phillips argued that reducing the precision will "lose significance faster than expected". * Another interesting solution was suggested by Stjepan Rajko: that the test might not be the same as the invariant. This is what testing with epsilon would guarantee. If the value passes the test it is guaranteed to satisfy the invariant, but only the test and not the invariant is in code. So some values might be rejected which are okay, but no bad value is accepted. RK felt that any floating point solution should be implemented separately from constrained_value, because he does not have the expertise. But he should be willing to document the scope of the problem better, including the SSE2 compiler flags that avoid the problem altogether. The first solution (truncation of the value) does not seem to require any changes to the library. Truncating the bounds might require some extra customization points. NaN Another problem with floating point is NaN, which compares false with everything. It might be okay if the bounds inclusion test always returned false. But the closed range is implemented as !(x < lower) && !(upper < x). Stjepan Rajko suggested that it should always be compare(lower, x) && compare(x, upper) where compare is < for excluded bounds and <= for included. It seems like this solution would work well for floats but not necessarily for user-defined types, which might only define operator<(). Substitutability with the underlying type A few people requested the ability to set a compiler flag in order to substitute the constrained_value with the underlying type. This is not exactly possible, unless the user is willing to explicitly extract the value using static_cast<T>(cv). The library does provide unconstrained<> which in most cases optimizes away, but the interface is not perfectly compatible with the underlying type. Constraints not copied when operators used The use of operators invokes implicit conversion to the underlying type, which means that in a statement like constrained_value x(10, constraint(...)), y(-x); y ends up with uninitialized constraints. Steven Watanabe suggested that the operators could be overloaded, but RK argued that the behavior would be application-specific: "For some applications returning a constrained value would be OK (but again there is the problem that the constraint may reject the modified value) while for others it's better to return the underlying type." Constrained strings Jeff Garland offered that he has written constrained_string classes for allowing values from a set of strings, and for validation against a regex. RK said he might add a constraint type which validates against set<T>, and affirmed that a regex validator would be nice too. Bounding on only one side Utku Yaman and others requested a way to bound integers on only one side. RK noted that you could set one of the bounds to the maximum or minimum possible integer, but this is verbose. Default arguments would be confusing, and RK thought maybe he would supply lower_saturating_int and upper_saturating_int. Note that there is a more general problem, especially if floating point is allowed. (Also consider e.g. fixed point, rational.) Recoverable error policy - error policy changing the value There were some objections to the error policy taking three parameters - the new value, the member value, and the constraint. Does it really need to change the member value? Yes, RK explained, because this is a recoverable error policy. Vicente Botet asked that the concept be called RecoverableErrorPolicy. Serialization Neal Becker requested support for serialization. RK agreed this is worth looking into and pointed out a couple of difficulties. One, a way to not serialize empty (or static) policies is needed. Two, non-default constructible types such as odd_number might require use of load_construct_data() / save_construct_data() instead of serialize(). Rename bounded_int This class name does not convey the fact that the bounds are specified at compile time. Neal Becker suggested compile_time_bounded or static_bounded. RK says the first name is too long, and the second might imply that the bounds are static members (which is also a legitimate use case). sizeof static constrained types == sizeof underlying type Assuming that the empty base class optimization is being applied correctly, which seems to be the case, if the constraint and the error policy are empty, the size of the constrained value should be the same as the size of the underlying type. However, this was not the case on all platforms, at least at the time of the review. The library should include sizeof tests in its test suite so that potential users know if there is unexpected overhead on their platform. Specify static bounds as open<0>, closed<100> for bounded<> and bounded_int<> Requested by Vicente Botet. If possible, this would reduce the number of template arguments and would be more clear than the current bounds exclusion boolean parameters. Some default constructions may throw If zero does not satisfy the constraint, then a default-constructed constrained value may throw an exception. (There are other examples, like non-empty string.) Many reviewers requested a means to provide a default value, which can be done by wrapping the underlying type, but RK felt a default value class was out of scope. At the very least this should be documented and probably an example given. Examples Vicente Botet requested: * an example showing how to create a constrained class by derivation and/or containment which adds/removes methods from the constrained value interface * a date example where changing the month affects the bounds for the day. * example of static bounding on only one side * example of bounds calculated at runtime by a function ("runtime dynamic bounding") Others: * example of constraints with static members - allows shared mutable constraints with no overhead per instance. Tests! Many reviewers were offended that there were no tests in the review version. RK said he would write some. Documentation * document the concepts and provide tests with concept archetypes. It turns out that these are documented briefly in the doxygen documentation of constrained<> at http://tinyurl.com/39v8o6r, but many reviewers were expecting a section in the main document. * Stjepan Rajko pointed out that the constraint can't depend on mutable members of the underlying type, and wondered if there were other implicit requirements, such as the way copy construction or swapping works. He requested these be documented. * Gordon Woodhull suggests a section on space efficiency and which configurations should allow the size to be optimized to the same size as the underlying type, and spelling out in each example what the cost in space is. * Thorsten Ottosen requested benchmarks of non-checking unconstrained against just using the underlying type. RK offered that he had looked at the generated assembly on some platforms. 4. Unresolved debates Error policy is allowed to change constraint Vicente Botet objected to the "bounded object with memory" example, which tracks extremal values by setting the bounds to include any new values. And Thorsten Ottosen objected to the inefficiency of change_constraint using construct-and-swap: it's not necessary to swap the constraint unless it might be changed by the error policy. This seems to be an example of a monitored value, which RK does not want to write himself, so does it belong in this library? RK argued that it does no harm, so why not allow? Double-checking and disabling assertions A number of people were concerned with the inefficiency of first checking the constraint, and then also asserting that the constraint is satisfied after the assignment has happened or the error handler has been called. But RK argued that it was necessary to check the invariant to make sure that the assignment operator and the error handler are doing their job. Besides, it is possible to disable the asserts with either BOOST_DISABLE_ASSERTS or NDEBUG. There was some discussion of adding an assert policy or a specific macro (with no clear conclusion). Disabling checks There is unconstrained, which offers a way to replace one constrained type with an unconstrained type, but Chris (indy271828(a)sympatico.ca) requested a way to disable all checks with a single macro. It might not be good enough to use a single error policy and select between throwing version and an assign-anyway version, because the compiler won't always optimize this away. More members, less free functions Thorsten Ottosen thought that any functions which change the state of the object should be members, not free functions. In particular, change_constraint might be less efficient than possible because the construct-and-swap requires copying the constraint. This does seem to be partly an ideological debate. Specific classes instead of a general super-template Vicente Botet requested that the interface use specific classes instead of typedefs: currently many of the specializations, like bounded<>, are metafunctions that apply some parameters to the generic constrained_value and return a new type, and then the specific operations are free functions. Instead these could be full classes with member functions. RK argued that this would result in unnecessary duplication. Way to disable the arithmetic operators Vicente Botet requested a solution in code or in documentation for users who don't want the arithmetic operators defined. 5. Ideas not requiring any action Monitored Values Stjepan Rajko suggested (and Vicente Botet expanded on the idea) that constrained value is really a special case of a more general "monitored value" class, in which a monitor policy decides how to handle any assignment. So constrained value would be a monitored value where the monitor policy checks a constraint, possibly calls an error policy, and then asserts the constraint. RK did not want to implement this and resisted suggestions to allow the assertion to be disabled in order to allow this use case, because without an invariant, it's not really a constrained value. But he suggested that monitored value could be implemented by someone else and constrained value could be re-implemented in terms of it. "Monitored value" might not be the best name for the general class, because "monitor" suggests something passive, rather than something which controls the outcome of assignment. A way to run a function on a constrained value Stjepan Rajko requested a way to make a copy of the value, run a function on it, and then reassign back, preferring the syntax call_using_copy(f, x) to x = f(x). But he notes this could be written as a free function. Multiple ranges Edward Diener requested a way to supply multiple ranges, but agreed that the syntax would be unattractive. Assertions instead of exceptions Thorsten Ottosen requested a way to have only assertions and no exceptions, and RK pointed out that this can be done either by specifying an error policy which asserts, or even with an assign-anyway error policy, which leaves the invariant checking in place. Exclude bounds parameter Vicente Botet found it confusing that bounded_int takes false to mean include bounds and true to mean exclude the bounds. RK explained that this is an artifact of the way within_bounds is templated on a type which can be either a compile-time or a runtime value, e.g. mpl::true_ or bool; this technique means there can be no default argument to the constructor and thus the more common option must be false, the default constructed value of bool. Constraints between several variables. Vicente Botet suggested a sort of constrained_tuple where if you set one field it would affect the constraints for the other fields. E.g. a date object where the month and year would affect the valid range for the day. With the current interface you'd have to set the whole date at once. Constrained values as sets of instances Exploring the problem domain, Vicente Botet suggested another possible implementation of constrained value where the constrained value type keeps track of which instances satisfy the constraint. This class would offer a split operation which moves any instances which satisfy a more specific constraint into the new set. Changing the constraint would similarly return the set of instances which are now excluded.

12 49

Boost Threading Shared Memory
by Tanya Gillis 29 Oct '10

29 Oct '10

I have a question regarding Boost threads, and am awaiting acceptance into the Boost Threads forum. I was wondering if anyone can help me. I am creating a multithreaded application using Boost threading, and would like to know how shared memory is implemented by Boost for threading. Each thread creates an object separately, and that object has a private member variable. We are seeing in our application that that member variable is looking the same, as if it was shared among the threads. Is this plausible? How does it work? Thanks.

2 1

Call for interest - BOOST_AUTO_FUNCTION
by Matt Calabrese 28 Oct '10

28 Oct '10

I've been noticing that a lot of times in 0x code I've found it useful to create a very simple "auto function" macro that uses trailing return type syntax with decltype with 1-liner functions that automatically repeats the same expression in both the return type and the return statement. #define AUTO_FUN( name, param_list, expression ) \ auto name param_list -> decltype( expression ) { return expression; } There are two big advantages to this. The first and most obvious one is that it reduces redundancy when you have a 1-line function template which has a difficult to deduce return type that you generally would use decltype on, and the more subtle benefit is that since the exact expression is repeated in the return type you automatically get "perfect-fit" SFINAE. By that I mean it provides a quick way to SFINAE-out potential instantiations before instantiating the implementation. Because of this, even though a return type may be simple to deduce without decltype, the macro is still a valuable tool since it can cause substitution to fail if the body of a function template would fail to instantiate. You get very basic, automatic, syntax-only concept checking for free. It's a simple macro, but I find that it gets lots of use. As an example: http://codepaste.net/iqzbiz The above example is a simple "multi_cast" that chains several static_casts in a row (the example code shows a potential use-case). The subtlety here is that the return type is easily deducible without the need for decltype (the return type would just be "TargetType"). Instead, the macro is used because it causes substitution to fail if the body of the function would fail during instantiation. So when using "multi_cast" here, If someone attempts to do a cast where any of the intermediate types is not a valid conversion, rather than getting a complicated error nested inside of several instantiations, you get a single error message at the top-level call-site stating that there is no match for the function call (well, at least it's a simple to read error in gcc... *cough*). This works because if the body of any of the calls would have an error, substitution would instead fail, meaning substitution would fail for the caller, all the way back up to the top without any bodies being instantiated. In other words, it's SFINAEs all the way down :| I find this type of functionality to be very useful, particularly in libraries. In fact, I find myself using it for just about all 1-line function templates. Do others agree that this would be a worthwhile addition to boost? Documentation should be quick to write up. The macro would of course be renamed to something along the lines of BOOST_AUTO_FUNCTION If anyone thinks multi_cast would be useful, let me know and I'll also spin off a separate thread for that, though I'm tempted to think it's more of a curiosity than something that would get much use. -- -Matt Calabrese

11 54

New video from Boostcon
by Marshall Clow 28 Oct '10

28 Oct '10

Roshan Naik: Logic Paradigm for C++ http://blip.tv/file/4307883 Some people have asked about Doug Gregor's Clang talk. Unfortunately, Doug's employer nixed recording that one. -- Marshall

1 0

Bidirectional streams/archives - Frames
by vicente.botet 28 Oct '10

28 Oct '10

Hi, The use I have is to implement binary messages that are user through protocol stacks. When sending a message, lower layers add usualy headers and trailers to payload comming from the upper layer. When receiveing a message, lower layers extract its corresponding headers and trailers before passing the payload to the upper layer. I'm thinking in generalizing the stream or archive concept, so we could in addition to been able to read from the begining and write at the end, been also able to read from the end and write from the begining; a kind of bidirectional stream or archive. I was thinking in namming the concept "frame", as frames are usualy composed of header, payload and trailer. Do you have other namming sugestion? Could this concept have any interest for Boost? Please, let me know if there is already someting on Boost or the standard library that could help me. Best, _____________________ Vicente Juan Botet Escribá

2 2

spirt status?
by Robert Ramey 28 Oct '10

28 Oct '10

What is the situation of the spirit library in the trunk? The serialization library now depends upon the latest spirit to parse xml archives. But now serialization can't be built for a number of compilers which previously could handle this library. This was not a surprise to me as its not unusual to require some tweaks to get this to work. But now I'm surprised that this hasn't resolved the issue. The newer version of spirit has been around for at least a year, and the serializaiton library xml grammar is very simple compared to other spirit applications so I didn't anticipate any major problems - but it seems that we now ahve them. Could spirit library developers take a look at this and give us an idea of what we should do about this? Is anyone working on this? Should we just roll back and try again before the next release? Robert Ramey

7 11

[gil][io_new] Problems with templates
by Christian Henning 27 Oct '10

27 Oct '10

Hi there, I don't see the woods because of all the trees. Could someone get the latest code from here: http://code.google.com/p/gil-contributions/source/browse/#svn/trunk and try to compile the following code: #include <boost/gil/extension/io_new/tiff_all.hpp> using namespace std; using namespace boost; using namespace gil; int main() { typedef mpl::vector< gray8_image_t , gray16_image_t , rgb8_image_t , gil::detail::gray1_image_t > my_img_types; any_image< my_img_types > runtime_image; read_image( "C:/gil_contributions/test_images/tiff/test.tif" , runtime_image , tiff_tag() ); return 0; } Why do I have this static assertion in read.hpp[662]? I don't understand why the two buffer types are different. Any help is very welcome, Christian

2 4

Google Code-in 2010 (another Google program like Summer of Code)
by Boris Schaeling 27 Oct '10

27 Oct '10

Boost is invited to become a mentoring organization in the Google Code-in 2010 program. If you have never heard about it (like me :): It's basically Google Summer of Code for pre-university students (the most important requirement is that participants are between 13 and 18 years old). This program is organized as a contest though: It's not so much about mentoring but setting up tasks in eight categories (writing code, documenting, translating etc.). Students will pick then tasks, and judges from participating organizations decide who won. :) While I've no idea if there is any interest to participate in this new program (are there any pre-university students on this mailing list for example?) I wanted to forward the invitation at least. As the deadline to apply as a mentoring organization is 29 October there is not much time left to decide either. Boris

4 7

[interprocess] Documentation for containers is missing
by vicente.botet 27 Oct '10

27 Oct '10

Hi, the documentation for the containers is missing since 1.44. Ion, could you se what can be done? Best, _____________________ Vicente Juan Botet Escribá http://viboes.blogspot.com/

2 1

Review Request: Boost.Process
by Boris Schaeling 27 Oct '10

27 Oct '10

I would like to ask for a formal review of Boost.Process (draft version 0.4). * The source code can be found in the Boost Vault (search for process.zip or click on <http://www.boostpro.com/vault/index.php?action=downloadfile&filename=proces…>). The source code can also be downloaded from <http://www.highscore.de/boost/gsoc2010/process.zip>. * The documentation can be found online at <http://www.highscore.de/boost/gsoc2010/>. If you wonder why the library looks like as it does today I recommend to read the thread at <http://thread.gmane.org/gmane.comp.lib.boost.devel/207594/> which was a kind of unofficial review. :-) Boris

5 8

[function] function wrapping and exception safety recap
by Daniel Walker 27 Oct '10

27 Oct '10

Hi all, While it's fresh on my mind, I just want to recap the previous discussion and to make sure this is brought to Doug's attention. http://thread.gmane.org/gmane.comp.lib.boost.devel/209304 To summarize, there have been several complaints from users who don't use RTTI about boost::function's dependency on Boost.Exception. boost::function has a strong exception safety guarantee and uses boost::throw_exception to implement it. This affords users sophisticated options as to how exceptions are actually thrown (or not thrown in RTTI-free environments), since boost::throw_exception can be defined/customized by the user. This is a great feature for some, but others would prefer a function object wrapper that behaved more like a function pointer; i.e. no exception safety guarantee and no RTTI dependency. The following feature request and patch try to answer this demand by adding a new function object wrapper to the Boost.Function family of wrappers: boost::unsafe_function. boost::unsafe_function is simple to generate with only slight modification to the code that generates the existing boost::function/functionN family. https://svn.boost.org/trac/boost/ticket/4720 Some concerns have been raised regarding the efficiency of the NULL pointer check in boost::function's operator(), but I believe this is a side issue at best and possibly a case of premature optimization. In optimized object code, the overhead of the pointer check is so small that it is difficult to detect (from simple benchmarks with MSVC Release mode and gcc -02). Regardless, in circumstances where aggressive compiler optimization is unavailable, unsafe_function could be used to address this concern as well. (I measured a ~15% reduction in time with gcc -01, for example.) Of course, as Peter and Emil pointed out, one could eliminate the pointer check in boost::function if its default "empty" state actually wrapped a valid function, e.g. throw_bad_function_call(). This may be a good idea by itself, but again, this is tangential to the present feature request to provide a function object wrapper that is independent of boost::throw_exception and RTTI. Finally, there have been suggestions to alter boost::function's exception safety guarantee directly through either policies or constructor options. These solutions are functionally similar to unsafe_function, so preferences between them may be a matter of personal taste. Personally, I like having two distinct class templates for two orthogonal levels of exception safety. Also, I like that anytime I encounter an instance of boost::function, I know it has the same strong exception safety guarantee it has always had, without having to wonder how it was instantiated or constructed. So, in this case, my preference is to expand the Boost.Function family of function object wrappers, rather than alter boost::function itself. Daniel Walker

7 22

[Backtrace] Any interest in portable stack trace?
by Artyom 26 Oct '10

26 Oct '10

Hello, Is there any interest in getting portable stack trace to boost - get something similar to Java's printStackTrace. Basics: 1. Getting stack trace of return pointers 2. Converting this pointers to human readable trace Extras: 1. Create exception classes that capture stack trace on throw (only pointers) 2. Print a trace on catch Supported Platforms: Linux, Mac OS X, Solaris and Windows >= XP using MSVC. Tested on: Linux x86_64, GCC, Linux x86, GCC Linux x86_64, Intel Windows XP 32bit, MSVC 2008 How implemented: Linux/Mac/Solaris with GCC: Capture trace using backtrace Convert trace using dladdr + with demangling Requires: compilation with -rdynamic for fetching symbols Linux/Mac/Solaris with Other compilers: Capture trace using backtrace Convert trace using backtrace_symbols (no demangling) Requires: compilation with -rdynamic for fetching symbols Windows/MSVC Capture trace using RtlCaptureStackBackTrace (XP and Above) Convert trace using dbghelp.lib using SymFromAddr Requires: debug info (PDB files) for fetching symbols All other: Create an empty trace For example: #include <boost/backtrace.hpp> #include <iostream> int foo() { throw boost::runtime_error("My Error"); return 10; } int bar() { return foo()+20; } int main() { try { std::cout << bar() << std::endl; } catch(std::exception const &e) { std::cerr << e.what() << std::endl; std::cerr << boost::trace(e); } } Prints: My Error 0x403fe1: boost::stack_trace::trace(void**, int) + 0x1b in ./test_backtrace 0x405451: boost::backtrace::backtrace(unsigned long) + 0x65 in ./test_backtrace 0x4054d2: boost::runtime_error::runtime_error(std::string const&) + 0x32 in ./test_backtrace 0x40417e: foo() + 0x44 in ./test_backtrace 0x40425c: bar() + 0x9 in ./test_backtrace 0x404271: main + 0x10 in ./test_backtrace 0x7fd612ecd1a6: __libc_start_main + 0xe6 in /lib/libc.so.6 0x403b39: __gxx_personality_v0 + 0x99 in ./test_backtrace Initial Source Code: http://art-blog.no-ip.info/files/backtrace.tar.gz Any interest? Artyom

14 27

Report # 29 (aka 1.45 blockers) is too narrow
by Jim Bell 26 Oct '10

26 Oct '10

I think that boost report # 29 (https://svn.boost.org/trac/boost/report/29) is too narrow a query. If you remove the "Milestone" filter you get nearly fifty tickets marked Showstopper, going back 22 months. A ticket's originator may not know what milestone to fill in, and his/her ticket shouldn't be lost because of that. I think they all need review.

8 15

Seek within a file stream using large offsets - reactivation
by Mateusz Loskot 26 Oct '10

26 Oct '10

Hi, I need to solve problem with seeking streams for large files. The problem leaks on Windows 32 and 64 bit, but the solution I'm looking for needs to be portable to Unix too. I have discussed this issue on #boost IRC and it looks Boost.IOStreams does not provide any cure for it. I've just found this problem was discussed 5 years ago. http://lists.boost.org/Archives/boost/2005/03/83087.php with some interesting suggestions: http://lists.boost.org/Archives/boost/2005/03/83140.php I'm wondering, has been there any motion on any level, Boost or C++ standard, to solve it? I'm looking for recommendation of any solution that would be sensible for this problem. (I can't ask my clients to move to STLport :-)) Best regards, -- Mateusz Loskot, http://mateusz.loskot.net Charter Member of OSGeo, http://osgeo.org Member of ACCU, http://accu.org

1 0

Re: [boost] [Backtrace] Any interest in portable stack trace?
by Brian Wood 26 Oct '10

26 Oct '10

On Oct 20, 2010, at 3:47 PM, Artyom wrote: > > > Initial Source Code: > > http://art-blog.no-ip.info/files/backtrace.tar.gz > > > Any interest? I'm not able to access that link so far today. I'm getting a server not found error. Brian Wood Ebenezer Enterprises http://webEbenezer.net

2 1

Phoenix as a Boost library
by Edward Diener 26 Oct '10

26 Oct '10

I am curious to know if Phoenix will ever be released as a Boost library, or is it meant to be forever coupled with Spirit ? I have avoided it because it has never been released separately or had its documentation appear among the list of Boost libraries. I got the impression that it would be released separately, and expected to see it in Boost 1.44, but evidently that did not happen.

9 31

[Boost.Serialization] Detecting if Boost.Serialization is supported for a type
by Ioannis Papadopoulos 25 Oct '10

25 Oct '10

Hi, I have two methods of serialization and I would like to choose between them. One is Boost.Serialization and the other is my hand-made one. Is there any (relatively) portable way that can allow to find out if Boost.Serialization is supported either through the intrusive or the non-intrusive way without requiring from the user to add more in her class to define the serialization method? Thanks

2 4

Interface for configuring third-party dependencies
by Vladimir Prus 24 Oct '10

24 Oct '10

Boosters, it seems that increasing number of upcoming libraries want to depend on third- party dependencies (Locale and GIL.IO being examples) and it would be nice to agree beforehand on an interface that is acceptable to everybody. This email attempts to suggest such interface. = Configuring location of dependencies = In general, for each external dependencies Boost.Build should try to check if it's available without configuration -- that is, in locations normally searched by the compiler/linker. If that fails, user has two way to help the search process. First, it will be possible to specify environment variables (either in OS environment, or using Boost.Build -sVAR=VALUE command-line option). For example, given a name of external dependency of 'zlib', the used variables are: - ZLIB_INCLUDE_PATH - ZLIB_LIBRARY_PATH - ZLIB_LIBRARY_NAME - ZLIB_ROOT The first two specify where the headers ahd libraries are located. The third specifies how the library file itself is named (and has sensible defaults most of the times). ZLIB_ROOT is a shortcut to set both include path and library path to $root/include and $roo/lib respectively. This approach is fairly easy to use for one-off builds of Boost by users. Second, it will possible to specify external dependencies in user-config.jam, or any other configuration file. This approach is slightly more complicated, as one has to edit a config file, but retains configuration and permits to specify multiple configuration for an external dependency -- which is not possible using environment variables. Roughly, the syntax will be: using zlib : condition <target-os>windows : include-path whatever : library-path something-else ; The 'condition' parameter specifies when this declaration will be picked up. Other parameters mirror the environment variables above. = Controlling use of external dependencies = Sometimes, it might be desirable to disable use of external dependency even when it's available. To than end, for each external dependency a new feature should be provided, for example: use-zlib When a value of "off" is specified, zlib won't be used by any boost component. Also, for every specific library that uses an external dependency, a more specific feature will be defined, for example: iostream.use-zlib to control use of that dependency in specific library. Does anybody have comments on this? Thanks, -- Vladimir Prus http://vladimir_prus.blogspot.com Boost.Build: http://boost.org/boost-build2

8 17

[interprocess][iostreams] trac#4234
by Domagoj Saric 23 Oct '10

23 Oct '10

As part of my work on GIL.IO2 (https://svn.boost.org/svn/boost/sandbox/gil/boost/gil/extension/io2/detail) I've somewhat improved/generalized the original 'proof of claim' code from the post mentioned in the ticket (https://svn.boost.org/trac/boost/ticket/4234) However, in the same process I've gone through the Interprocess implementation of memory mapped files and AFAICT the various platform specific distinctions seem unnecessary: - AFAIK the POSIX 'anonymous inheritable' shared memory functionality is also available on Win32 - kernel-life time shared memory emulation with memory mapped files on Windows is also unnecessary. It can be either provided directly by bypassing the Win32 APIs using the native NT API (I volunteer to help with the implementation or can do it from scratch by myself) or a new distinction can be made (that does not have anything platform specific in its interface) such that a user can choose between a handle/process life time (which I suppose would be enough most of the time, because what use is there for a client to map a shared memory region after the server has already terminated) or kernel life time shared memory regions (which would then be emulated on Win32)...AFAICT the only thing the Win32 API lacks for this is getting the size of the mapped region which could perhaps be emulated by passing the size at the begining of the mapped region... -- "What Huxley teaches is that in the age of advanced technology, spiritual devastation is more likely to come from an enemy with a smiling face than from one whose countenance exudes suspicion and hate." Neil Postman

3 4

Anyone have access to Sun Studio 12 compiler?
by Marshall Clow 23 Oct '10

23 Oct '10

I have a bug report on that compiler (Sparc, Solaris 9) that I don't have any way to reproduce. Thanks! -- Marshall There are only two hard problems in computer science: cache invalidation, naming things, and off-by-one errors.

3 5

Git mirror
by Vladimir Prus 23 Oct '10

23 Oct '10

It seems like there's a git repo that is supposed to mirror SVN, at: http://gitorious.org/boost/svn/commits/master But the last commit there is from Sep 15. Is this the way it should be? - Volodya

4 5

Re: [boost] [Boost.Serialization] Detecting if Boost.Serialization is supported for a type
by Ben Hendrickson 23 Oct '10

23 Oct '10

Loannis Papadopoulos wrote: > I successfully made a template supports_boost_serialization<T> that > detects if T::serialize() exists. > > However, I cannot address the case of a stand-alone serialize() function > - since there is a generic boost::serialization::serialize(Archive&, T&, > const unsigned int), there is not way (that I know of) to figure out if > non-intrusive serialization exists for a specific T. Another hard case is inherited serialize methods - consider class T inheriting from class B, and B::serialize() exists. Does your implementation of supports_boost_serialization<T> detect that? If it does, I am interested in how. Ben

2 2

need to get boost compiled so I can get Shareaza built
by Kevin Simonson 22 Oct '10

22 Oct '10

I'm trying to get the Shareaza source code to build in my local directory. When I try to build the only error I'm getting now is "Cannot open include file: 'boost/cstdint.hpp': No such file or directory". So it looks like I need to compile Boost. Some time back I went to the sourceForge "Developers.GettingStarted.Boost" page (I'd been referred there by a document that said I needed to compile Boost to be able to build Shareaza), and followed its instructions to the point of copying "bjam.exe" into my "boost_1_44_0\boost_1_44_0" directory, next to "boost.css". The next thing it said to do was to open "a command prompt window, and navigate it to the boost_1_33_1 folder where bjam.exe is located," and then paste "the text below onto the command line, and press Enter." The text in question was "{{{1}}}". I assumed that what this meant was to execute "bjam {{{1}}}". But when I actually did execute "bjam {{{1}}}" I got the messages: warning: No toolsets are configured. warning: Configuring default toolset "msvc". warning: If the default is wrong, your build may not work correctly. warning: Use the "toolset=xxxxx" option to override our guess. warning: For more configuration options, please consult warning: http://boost.org/boost-build2/doc/html/bbv2/advanced/configuration.html notice: could not find main target {{{1}}} notice: assuming it is a name of file to create. nBuilding the Boost C++ Libraries.nn warning: Graph library does not contain MPI-based parallel components. note: to enable them, add "using mpi ;" to your user-config.jam warning: skipping optional Message Passing Interface (MPI) library. note: to enable MPI support, add "using mpi ;" to user-config.jam. note: to suppress this message, pass "--without-mpi" to bjam. note: otherwise, you can safely ignore this message. don't know how to make <e>{{{1}}} ...found 1 target... ...can't find 1 target... The docs said executing this command would cause a "C:\Boost" directory to be created, but one wasn't, so even if the error messages didn't look discouraging, it's pretty clear that I didn't accomplish what I needed to to get Shareaza compiled. And running the Shareaza build afterwards generated the complaint about "boost/cstdint.hpp" anyway. So my question is, what do I have to do to get Boost compiled, so that I can go on and build Shareaza? I'd appreciate any information you can give me. Kevin S

4 4

[1.45] Thread issues
by Bryce Lelbach 22 Oct '10

22 Oct '10

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 https://svn.boost.org/trac/boost/ticket/3847 https://svn.boost.org/trac/boost/ticket/3882 https://svn.boost.org/trac/boost/ticket/4614 https://svn.boost.org/trac/boost/ticket/4632 https://svn.boost.org/trac/boost/ticket/4258 https://svn.boost.org/trac/boost/ticket/4736 A few of these are related or similiar in nature. Long story short, Boost.Thread has some rather serious issues on mingw. One report indicates that statically linking Boost.Thread with VC8 and VC10 is broken. These are quite serious. The library maintainers have not responded to any of these tickets. The mingw problems are reproducible for me, the supposed VC problem appears to work for me. - -- Bryce Lelbach aka wash http://groups.google.com/group/ariel_devel -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkzAlJEACgkQO/fqqIuE2t65YQCeNKpTO1+9IdAGleAPY+3XFIeC wIQAoImdTt1vpQjvxc0+hJ4jyQ9G9QaA =vck0 -----END PGP SIGNATURE-----

6 8

[fusion] tuple missing from sequence models?
by Mateusz Loskot 22 Oct '10

22 Oct '10

Hi, The boost::tuple seems to be missing (intentionally?) from the models of conforming to the forward sequence concept: http://www.boost.org/doc/libs/1_44_0/libs/fusion/doc/html/fusion/sequence/c… Though, the later chapter states it's adapted: http://www.boost.org/doc/libs/1_44_0/libs/fusion/doc/html/fusion/adapted.ht… Best regards, -- Mateusz Loskot, http://mateusz.loskot.net Charter Member of OSGeo, http://osgeo.org Member of ACCU, http://accu.org

2 2

[test] export bug or [graph] test mis-configured?
by Jim Bell 22 Oct '10

22 Oct '10

Boost.graph's stoer_wagner_test won't link on mingw32, with multiple definitions of various unit_test::test_case::... symbols. All symbols seem to be found in test/impl/unit_test_suite.ipp. Dynamic libraries for both boost_test_exec_monitor and boost_unit_test_framework are linked in. The compile has: -DBOOST_ALL_NO_LIB=1 -DBOOST_TEST_DYN_LINK=1 -DBOOST_TEST_NO_AUTO_LINK=1 So is this graph test's compile or link wrong (but being forgiven on other platforms), or is test (notably unit_test_suite.ipp) not exporting symbols as it should (and that's being forgiven on other platforms)? The same problem (conceptually) is happening on msvc8, though it calls out more than just unit_test_suite.ipp.

1 0

[quickbook] Lists with paragraphs
by Edward Diener 21 Oct '10

21 Oct '10

Is there any way to specify a list with paragraphs embedded in each list item, such as a final result of: 1. Some data here. Some more data here. Maybe some code here. 2. Other data here More code here. In other words I can normally do this with lists by not separating lines which form individual paragraphs, but I want the spacing and paragraphs for each list item.

2 2

Unify multi_array and ublas matrix
by Gonsolo 21 Oct '10

21 Oct '10

Hi! Is there a plan to unify Boost's multi_arrays and ublas matrices? It seems to me those concepts are very similar. g

1 0

Re: [boost] [Backtrace] Any interest in portable stack trace?
by nimaca2001＠libero.it 21 Oct '10

21 Oct '10

> Linux, Solaris and Mac OS X have functions backtrace and backtrace_symbols > in libc: See: http://linux.die.net/man/3/backtrace > > Windows starting from XP has RtlCaptureBackTrace in kernel32.dll: > See http://msdn.microsoft.com/en-us/library/ff552119(VS.85).aspx > > So the rest is translate symbols, under Unixes I have dladdr and under Windows > dbghelp. How difficult would be a separate translation made with the map file instead of PDB file? (My main goal is to get the backtrace with raw addressed and traslate them 'at home' without spreading around rarely used stuff) Marco

1 0

Re: [boost] [1.45] Beta final schedule
by Jim Bell 20 Oct '10

20 Oct '10

>> > >> > Can we petition to hold up this release for some important bug fixes to >> > catch up to it? > This idea has some traction with me. ... > Ticket numbers? So far... https://svn.boost.org/trac/boost/ticket/4736 https://svn.boost.org/trac/boost/ticket/4698 https://svn.boost.org/trac/boost/ticket/4747 Less important, but would remove more yellow from the regression table... https://svn.boost.org/trac/boost/ticket/4735

7 9

svn.boost.org down?
by John Maddock 20 Oct '10

20 Oct '10

SVN seems to be working Ok, but something has taken Trac down, any ideas anyone? Cheers, John.

3 3

Thoughts for a GUI (Primitives) Library
by Gwenio 20 Oct '10

20 Oct '10

As it stands, neither Boost nor C++ has any support for GUI applications. Therefore I am suggesting a library that provides the bare minimum required to create a GUI application. My thoughts on what this library would contain are as follows: - Types for controls (contexts bound to the extent of their parent) and windows (contexts that remain separate from their parents). - An event handler class that is passed when controls and windows are created that contains all information needed to handle events for the new context. - Functions for generating events (if applicable) and (a) function(s) to initiate message handling (unless the event loop is run in its own thread like in Java). - Functions to access and manipulate the data of the contexts (size, position, z-order, ect). - Miscellaneous other types used for support (such as for screen positions). - A way to retrieve the native concept of a window/control. As you can see, there are no controls/widgets/ect defined, either from the library or using the native versions. Such things can be added later, if people can ever agree on how they should be implemented. It needs a lot of refining, but I believe this covers the *minimum* support that is needed for a GUI.

22 78

Re: [boost] [1.45] Beta final schedule
by Jim Bell 20 Oct '10

20 Oct '10

> Message: 5 > Date: Tue, 19 Oct 2010 15:09:50 -0700 > From: Eric Niebler <eric(a)boostpro.com> > To: boost(a)lists.boost.org > Subject: Re: [boost] [1.45] Beta final schedule > Message-ID: <4CBE172E.90602(a)boostpro.com> > Content-Type: text/plain; charset=ISO-8859-1 > >> > >> > So far... >> > >> > https://svn.boost.org/trac/boost/ticket/4736 >> > https://svn.boost.org/trac/boost/ticket/4698 >> > https://svn.boost.org/trac/boost/ticket/4747 >> > >> > Less important, but would remove more yellow from the regression table... >> > https://svn.boost.org/trac/boost/ticket/4735 > Can you comment on whether these are regressions from previous releases? 1.44 had the first three, which is what (eventually) led me to this list (and pitching in to fix them).

2 1

Re: [boost] Understanding the test matrix
by Jim Bell 20 Oct '10

20 Oct '10

> The release test matrix seems to be telling me that there are many failures > on different platforms, and in fact > that there is no platform with no failures on all libraries, or libraries > with no failures on all platforms. We just > live with that, is that right? > > Do all the failures get fixed before an actual release is made, or noted in > the release notes? I think the original philosophy was that it should work on mainstream, modern compilers/platforms, but not necessarily on your old/outlier, and here's a matrix of what's been tested. I'm okay with that. Also, a single unexpected regression failure marks the whole library as fail/yellow on the main matrix. And something like serialization not linking cascades to several other libraries showing failed (e.g., date_time on mingw32). It should be that way, but it shakes the casual observer's confidence in all of boost. All this to say, maximizing the green on that regression matrix is worth the work, and worth holding up a release, IMHO. Also, many fixes are not as simple as just looking at the test results for a compiler/platform you have little experience with and can't test first-hand. (E.g., Ticket # 4736 -- it's clear the author was looking for the failure, but the only thing that made progress was my running it in gdb on that particular platform.)

1 0

Understanding the test matrix
by Robert Jones 20 Oct '10

20 Oct '10

Following on from some recent posts I had a look at the development area on the site, and would appreciate some clarification that I'm understanding it correctly. Firstly, I'm assuming that releases are made from area summarised under "Development -> Testing -> Release Summary" and development is carried out on trunk, so the release area is supposed to stable-ish and trunk not particularly? Is it correct that in some areas there are substantial divergence between trunk and release, sometimes reaching far back in time? The release test matrix seems to be telling me that there are many failures on different platforms, and in fact that there is no platform with no failures on all libraries, or libraries with no failures on all platforms. We just live with that, is that right? Do all the failures get fixed before an actual release is made, or noted in the release notes? Thx - Rob.

1 0

[system] Undocumented deprecated throws variable
by vicente.botet 20 Oct '10

20 Oct '10

Hi Beman, The documentation doesn't states explicitly that the throws variable is deprecated (see section "Deprecated names"). In addition the section "Semantics of throws object" explaining how this variable should be used must be rewritten to show the usage of the function throws(). Could this be changed for 1.45? Best, _____________________ Vicente Juan Botet Escribá http://viboes.blogspot.com/

1 2

Re: [boost] [1.45] Beta final schedule
by Jim Bell 19 Oct '10

19 Oct '10

Can we petition to hold up this release for some important bug fixes to catch up to it? I think gcc-mingw-4.x is an important platform (Qt SDK for Win32 ships with it), and it needs a few key ones.

2 1

Re: [boost] [exception] ostringstream like
by Fabien Castan 19 Oct '10

19 Oct '10

> No, I mean that if you do advanced string manipulation in the exception > itself, you may screw up, adn cause a bad_alloc beign thrown and masking > your own exception. Create an error sentence with some values inside is not really an advanced string manipulation. You can have 2 kinds of errors: bug inside a custom operator<< or a memory problem. There is no particular reason to not have sufficient memory to create an error sentence when throwing something like a logic_error. > Just make your own, informative exception type deriving from logic_error. The problem is not really the kind of exception, but an easy way to create message with boost exception tag system. The idea is to create a new base class for tags allowing to use an ostringstream with tags, which is not possible. typedef ::boost::error_info<struct tag_message,std::ostringstream> message; This little class only remap operator+ call to operator<< on an internal ostringstream. typedef ::boost::error_info<struct tag_message,::boost::error_info_sstream> message; I use it in my code, but I ask here if we can hope to see such things in boost exception. I would prefer to use a standard boost object rather than a custom class.

4 3

[regex] Regex does not build current release branch with GCC
by Jeremiah Willcock 19 Oct '10

19 Oct '10

I am using GCC 4.1.2 (toolset "gcc"), and the current release branch produces the error: Performing configuration checks - has_icu builds : yes /dev/shm/release/tools/build/v2/build/feature.jam:485: in validate-value-string from module feature error: "msvc:<linkflags>delayimp.lib" is not a known value of feature <toolset> error: legal values: "gcc" (then a long backtrace) Removing the delayimp.lib line from libs/regex/build/Jamfile.v2 works around the problem but probably would cause problems on VC++. -- Jeremiah Willcock

1 0

[1.45] Beta final schedule
by Beman Dawes 19 Oct '10

19 Oct '10

Major changes should already have been merged to trunk. Last minute bug fixes should be merged to trunk by the end of Monday, October 25th. The beta will go out as soon after that as most release branch tests have cycled, typically three or four days later. --Beman

2 1

Re: [boost] What's so cool about Boost.MPI?
by Thorsten Ottosen 19 Oct '10

19 Oct '10

Den 19-10-2010 14:59, Mathias Gaunard skrev: > On 18/10/10 23:41, David Abrahams wrote: >> >> Just wanted to call some attention to this article I wrote about >> Boost.MPI: >> >> http://daveabrahams.com/2010/09/03/whats-so-cool-about-boost-mpi/ >> >> I think it might be useful to link that from the Boost.MPI docs, too. > > While the library seems nice (it bridges serialization with MPI), I > don't really see anything in there that makes me think it's "so cool". > > So after reading it, I felt a bit like the question "What's so cool > about Boost.MPI?" remained unanswered. The semi-automatic, but very easy to maintain, way of creating/maintaining the MPI type maps (via Boost.Serialization), IIUC. -Thorsten

3 2

Re: [boost] [review result] mini-review of update to Boost.Assign
by Thorsten Ottosen 19 Oct '10

19 Oct '10

Den 18-10-2010 21:01, Mathias Gaunard skrev: > On 18/10/10 19:38, Thorsten Ottosen wrote: >> I would like to thank Erwann for his hard work so far, and hope he >> submits a Boost.Assign v2 in the near future. > > I have a possibly silly question: > > Does it use Boost.Proto? I don't suspect it, but only Erwan can answer that. -Thorsten

1 0

Re: [boost] [review result] mini-review of update to Boost.Assign
by Thorsten Ottosen 19 Oct '10

19 Oct '10

Den 18-10-2010 21:01, Mathias Gaunard skrev: > On 18/10/10 19:38, Thorsten Ottosen wrote: >> I would like to thank Erwann for his hard work so far, and hope he >> submits a Boost.Assign v2 in the near future. > > I have a possibly silly question: > > Does it use Boost.Proto? I don't suspect it, but only Erwan can answer that. -Thorsten

1 0

[filesystem] temp_dir_path()
by Jeff Flinn 19 Oct '10

19 Oct '10

The need for portably obtaining 'the' temporary-directory-path has been brought up a few times(but never addressed AFAICT), and I am now in the need for this as well. Windows has the GetTempPath, which follows a specific order of looking for a temporary directory path. If GetTempPath returns 0, GetLastError provides a system error. Posix relies on getEnv("TMPDIR"), which returns 0 if the environment variable does not exist. The following windows and posix implementation would be in the detail namespace: BOOST_FILESYSTEM_DECL path temp_dir_path(system::error_code* ec) { # ifdef BOOST_POSIX_API const char* val = getenv("TMPDIR"); return val? path(val) : path(); # else // Windows std::vector<Path::value_type> buf(GetTempPathW(0, NULL)); if(GetTempPathW(buf.size(), &buf[0])) return path(buf.begin(), buf.end()); int errval(::GetLastError()); if (ec) ec->assign(errval, system_category()); return path() # endif } Questions: - should Posix return an empty path or an error when empty? - should Windows provide a more 'temp-path' centric error? - should both verify the path exists? - if the path does not exist should one be created? Thanks, Jeff

7 26

Fw: Interlibrary version cchecking
by Robert Ramey 19 Oct '10

19 Oct '10

"Robert Ramey" <ramey(a)rrsd.com> wrote in message news:<hsdfuq$prj$1(a)dough.gmane.org>... > Turns out that the idea of a single boost library deployment has come up a > couple of times here at BoostCon 2010. While preparing my presentation I > considered the problem of what would happen if one installed one library > which depended on an newer version of a different library than the user > already had installed. I actually woke up in the middle of the night > imagining someone would ask about that during my talk. I puzzled about it > for some time and the day before I found a way to address it - in my own > mind at least. It also seems that it turns out that there are tools that > can also manage this. > > It's not that I don't trust tools but I wear a belt AND suspenders. So I > would like a method which guarentees that when I build one library, I don't > accidently include code from a prerequisite library which is a version so > old that things won't work. I would also like to know that I'm not > accidently running with a DLL built with an old version. > > Basically each library includes a file "manifest.hpp". This get's included > when any header get's includes (once at most due to include guards). This > includes a static assert that checks that the prequiste libraries are of > sufficiently recent version that a dependent library (or user application) > requires. There is also a manifest.cpp file included in the library which > checks any prequiste DLLS. This would be an exheedingly small overhead to > avoid what could be an incredibly large headache. > > I just verified that the code compiles so at this point it's only an idea. > But it seems that some kind of check like this is un-avoidable of one want's > to deploy libraries as needed rather than as a monolithic distribution. > > FYI - no one asked me about this problem at my presentation. Add one more > confirmation of Murphy's law. > > Robert Ramey > > >

5 8

[accu london] Steve Love talks on Interface Versioning in C++
by Mateusz Loskot 19 Oct '10

19 Oct '10

Folks, I hope I'm not spamming and perhaps there are people on the list who are based in London and would find this talk interesting: What: Steve Love talks on Interface Versioning in C++ When: 21 October 2010 at 6.30pm for 7:00pm http://accu.org/index.php/accu_branches/accu_london/accu_london_oct_2010 Best regards, -- Mateusz Loskot, http://mateusz.loskot.net Charter Member of OSGeo, http://osgeo.org Member of ACCU, http://accu.org

1 0

Accelerating algorithms with SIMD - Segmented iterators and alternatives
by Mathias Gaunard 19 Oct '10

19 Oct '10

Hi, I have, along with Joel Falcou, been looking a bit at how we can integrate SIMD into iterator-based algorithms to accelerate them. Unfortunately, there are a couple of issues. The basic idea is to provide a range adaptor that adapts of range of PODs, where N consecutive PODs are stored contiguously, into a range of vectors (or "packs") of those PODs of size N. Therefore, instead of: std::vector<float> tab(20); float sum = boost::accumulate(tab, 0); we can write something like: std::vector< float, simd::allocator<float> > tab(20); float sum = simd::sum( boost::accumulate( simd::packed_range<4>(tab), simd::zero_ ) ); Which does the same but using SSE instructions, adding four floats at a time, and typically providing a 4x speed-up. This can be applied to have the same result for any binary operation which is commutative and associative (which unfortunately isn't the case of many operations, but can still be useful). Here, however, it works because 1) the memory is well aligned thanks to the use of our custom allocator and 2) the size, 20, is a multiple of the pack size, 4. We'd be interested in providing a mechanism where we could also support ranges of data aligned at an arbitrary address and of an arbitrary size. The SSE would only be used in the middle, the borders being handled element per element. A first solution consists in padding the beginning and the end with zeroes. Say you have 1 2 3 4 5 6 7 with only 3 being aligned well enough for SSE usage. so we'd turn that into | 0 0 1 2 | 3 4 5 6 | 7 0 0 0 |. However, it is very important that the code to deal with borders does not affect the efficiency of the code in the middle. This is not possible with the normal iterator/range design. Our data is clearly cut into three segments: the beginning that is not aligned, the data that is rightly aligned and sized, and the data at the end that is not big enough to fill a whole pack. Therefore, segmented iterators could provide us with a solution to do this efficiently; but so could other solutions as well. Wouldn't it be better to be able to use the mechanism so that you could deal with the borders in an element-per-element way while you could deal with the middle bit in a vector-per-vector way? With C++ iterators, you pull data, but if we could use an iteration paradigm where you push data instead, such as calling a function object for each element, we could call an overloaded function that would be able to accept both a single element and a pack. Such a solution would also provide the speed benefits of segmented iterators, and all high-level standard algorithms can be expressed with this iteration paradigm just as well as with iterators. I have already suggested such an alternative to segmented iterators (where I had a few misconceptions about segmented iterators, I thought they broke compatibility, but they don't, they still maintain the legacy non-segmented interface) there: <http://thread.gmane.org/gmane.comp.lib.boost.user/61636/focus=61647>, with an example of how you could use that to iterate over a binary tree there: <http://www.boostpro.com/vault/index.php?action=downloadfile&filename=genera…> Converting from those things to a pair of iterators is possible through the use of a coroutine, as demonstrated in the example. I would like to have feedback on the general idea of providing tools to use SIMD with iterators and related algorithms, and ideas about whether there is sufficient interest in the alternative to iterators for me to develop them. The intent would be to submit both the alternative to iterators and the SIMD helpers to Boost.

24 120

boost utf-8 code conversion facet has security problems
by Patrick Horgan 18 Oct '10

18 Oct '10

I've been meaning to mention this for some time. The boost utf-8 code conversion facet implements an early spec of utf-8 that allows up to 6 byte representations but current specs, and security issues suggest it should only support up to four. See http://en.wikipedia.org/wiki/UTF-8 and in particular the section on invalid byte sequences. It also has some stuff wrong, like do_length() is supposed to only tell you length of valid code sequences, but the boost implementation doesn't check for validity. This has long since been superseded by newer specs that allow only 1-4 byte representations. The issue is that the longer representations let you alias characters, so if someone is filtering out certain chars for security reasons, for sql or http requests, for example, someone can bypass the filter by using a different representation of a character, and inject their naughty stuff just when you think you've got them stopped. In addition to no more 5 and 6 byte utf-8 chars, there are some other first and second byte codes that are forbidden because they would alias other characters. Current specs, see std 63 (also currently rfc 3629), and The Unicode Standard Version 5.2, specify how to correctly implement the conversion. I think that everything you need to know, however, to implement do_in() and do_length() correctly is in this table (notice that start and end of valid second byte range varies in different unicode code ranges): /* Table 3-7. Well-Formed UTF-8 Byte Sequences from version 5.2 of the Unicode Standard Code Points First Byte Second Byte Third Byte Fourth Byte U+0000..U+007F 00..7F U+0080..U+07FF C2..DF 80..BF U+0800..U+0FFF E0 A0..BF 80..BF U+1000..U+CFFF E1..EC 80..BF 80..BF U+D000..U+D7FF ED 80..9F 80..BF U+E000..U+FFFF EE..EF 80..BF 80..BF U+10000..U+3FFFF F0 90..BF 80..BF 80..BF U+40000..U+FFFFF F1..F3 80..BF 80..BF 80..BF U+100000..U+10FFFF F4 80..8F 80..BF 80..BF */ So, you have to do more checking, but it's still efficient. I have test code that checks all this. I'm willing to help in various ways. o I have an implementation of the utf-8 code conversion facet that implements do_in, do_out, and do_length that I did. You can have the source to jump start the fix. o I'm willing to make changes to the boost one and contribute a patch with a little guidance. o I'm willing to just figure that now that I've pointed it out, someone who owns this code will be motivated to fix it, it's not too hard. o Also willing to give you the test code to check with. Probably a lot different than how boost implements test code. o Willing to give peace a chance;) It should really be fixed. There's a lot of bad guys out there that know about these sorts of problems, plus, there aren't many open source implementations of utf-8 code conversion facets, so folks are likely to emulate/steal this. btw mine's freely available to anyone who requests it. wc -l * 232 codecvt_utf8_facet.cpp 29 codecvt_utf8_facet.hpp 14 Makefile 510 testcodecvt.cpp Funny the test code is twice the size of the code. Patrick

5 9

Fwd: [String algo] Breaking change between 1.41 and 1.44 in split
by Christophe Henry 18 Oct '10

18 Oct '10

As I got no answer on the user list, I try again. Is the library still maintained? ---------- Forwarded message ---------- From: Christophe Henry <christophe.j.henry(a)googlemail.com> Date: 2010/10/13 Subject: [String algo] Breaking change between 1.41 and 1.44 in split To: boost-users(a)lists.boost.org Hi, I noticed a breaking change in the split function when the input string is empty. Consider the following example: #include <string> #include <vector> #include <iostream> #include <boost/algorithm/string/split.hpp> #include <boost/algorithm/string/classification.hpp> int main() { std::vector<std::string> result; std::string empty_string; boost::algorithm::split( result, empty_string,boost::algorithm::is_any_of( "\t" ),boost::algorithm::token_compress_off); std::cout << "result size: " << result.size() << std::endl; return 0; } With boost 1.41 I get: result_size: 1 With 1.44 I get: result_size: 0 Meaning that splitting an empty string now has a new meaning. All I found to this subject was that 1 seems to be the correct answer (http://lists.boost.org/Archives/boost/2005/07/90266.php) Furthermore, there has been, according to the release notes, no change to string algo since the 1.41. This brings me to the question, before I start updating my code, is this change a design decision or an accident? Thanks, Christophe

2 2

[review result] mini-review of update to Boost.Assign
by Thorsten Ottosen 18 Oct '10

18 Oct '10

Dear all, Here follows the result of the result of Erwann Rogard's update to Boost.Assign: **************************** The update is not accepted **************************** This is not because the new functioanlity/interface was not seen as an improvement, but because Erwann has chosen to implement a full replacement (or Assign v2) based on the feedback he got during the review. The feedback meant that the new "update" would be much larger than what was present in the mini-review, and the new library should therefore be subject of its own full review. I would like to thank Erwann for his hard work so far, and hope he submits a Boost.Assign v2 in the near future. I would also like to thank the following people who participated in the mini-review: Christopher Jefferson Diederick C. Niehorster John Bytheway kind regards Thorsten, review manager

1 0

[pool] detail/mutex.hpp may include windows.h and pollute namespace with windows definitions.
by Paul Blampspied 18 Oct '10

18 Oct '10

I have been making an effort to write Windows independent code. In particular I avoid including windows.h in any of my headers (some implementation files include it). I have had a problem using Boost/pool as the mutex header includes windows.h (causing nameclashes with some of my existing code, which has always relied on the absence of windows.h). Possible inclusion of windows.h is documented in the section on mutex. My question is 'Is it really necessary or desirable ?'. Is there a Boost policy on the inclusion of OS specific headers which create a large number of declarations in the global namespace ? The section which uses windows.h is: #ifdef BOOST_WINDOWS class win32_mutex { private: ::CRITICAL_SECTION mtx; win32_mutex(const win32_mutex &); void operator=(const win32_mutex &); public: win32_mutex() { ::InitializeCriticalSection(&mtx); } ~win32_mutex() { ::DeleteCriticalSection(&mtx); } void lock() { ::EnterCriticalSection(&mtx); } void unlock() { ::LeaveCriticalSection(&mtx); } }; #endif // defined(BOOST_WINDOWS) I believe that the appropriate declarations of InitializeCriticalSection, DeleteCriticalSection, EnterCriticalSection, LeaveCriticalSection could be provided explicitly in this file and hence avoid including windows.h and the subsequent namespace 'pollution'. An alternative of using a Boost multithreading library is suggested in the documentation. This would be ideal, but my proposal would solve problem now, relatively effortlessly. PS. I did a quick edit and got it to work (at least on Vista). The change to the if-endif block is shown below. It could be done much better. # ifdef BOOST_WINDOWS //#include <windows.h> typedef char CRITICAL_SECTION[24]; //24 is sizeof(CRITICAL_SECTION) ! typedef CRITICAL_SECTION *LPCRITICAL_SECTION; #define WINAPI __stdcall extern void WINAPI InitializeCriticalSection( __out LPCRITICAL_SECTION lpCriticalSection ); extern void WINAPI DeleteCriticalSection( __inout LPCRITICAL_SECTION lpCriticalSection ); extern void WINAPI EnterCriticalSection( __inout LPCRITICAL_SECTION lpCriticalSection ); extern void WINAPI EnterCriticalSection( __inout LPCRITICAL_SECTION lpCriticalSection ); void WINAPI LeaveCriticalSection( __inout LPCRITICAL_SECTION lpCriticalSection ); # endif many regards, Paul

7 13

[property_tree] Copy constructor and assignment operator in xml_writer_settings class
by Mateusz Loskot 18 Oct '10

18 Oct '10

Hi, What is recommended or required policy regarding copy operations for types which consist of const data members, within Boost? I'm having problem with understanding why the xml_writer_settings class do not have the copying operations disabled. Perhaps it should be patched? Quick chat on the #boost IRC channel confirms it could be improved. I'm looking forward comments. [1] https://svn.boost.org/trac/boost/browser/trunk/boost/property_tree/detail/x… Best regards, -- Mateusz Loskot, http://mateusz.loskot.net Charter Member of OSGeo, http://osgeo.org Member of ACCU, http://accu.org

4 7

is_convertible_basic_impl and OpenMP - compile error
by Remi 18 Oct '10

18 Oct '10

Hi, I'd like to report nasty behaviour of boost when used inside OpenMP loops. In the following example compile error is generated under Visual 2008, if "default(none)" is used for OpenMP variable data sharing attribute clauses (which is the recommended choice). #define BOOST_ALL_NO_LIB 1 #include <boost/graph/adjacency_list.hpp> #include <omp.h> int main(int argc, char* argv[]) { typedef boost::adjacency_list<boost::vecS, boost::vecS, boost::undirectedS> GraphType; typedef GraphType::adjacency_iterator GraphAdjacencyIterator; const unsigned int vertex_count( 20 ); typedef std::pair<int, int> EdgeType; std::vector<EdgeType> edges; const GraphType graph( edges.begin(), edges.end(), vertex_count, edges.size() ); int i( 0 ); #pragma omp parallel for schedule(static, 1) default(none) private(i) shared(vertex_count, graph) for ( i = 0; i < vertex_count; ++i ) { const std::pair<GraphAdjacencyIterator, GraphAdjacencyIterator> adjacent ( boost::adjacent_vertices(i, graph) ); } return 0; } "\boost\boost/type_traits/is_convertible.hpp(263) : error C3052: '_m_from' : variable doesn't appear in a data-sharing clause under a default(none) clause"

2 2

Version information for Boost library
by Edward Diener 18 Oct '10

18 Oct '10

Does Boost have any policy regarding the way version information should be attached to a library ?

4 6

Does boost support ccache?
by Alexander Churanov 18 Oct '10

18 Oct '10

Folks, I've encountered an issue: boost libraries fail to build under ccache. The questions are: 1) Are boost libraries and ccache compatible? 2) If not, should I file a new bug? One of users contacted me and reported failure to build boost libraries version 1.43 on FreeBSD 7.3 (GCC 4.2.1). There were, however, no failures on the FreeBSD ports build cluster. Quick comparison of logs revealed that build cluster does not use ccache - compilation cache tool for C++ and other languages. Removing ccache from the toolchain fixed the issue, so it is an acceptable workaround. The logs are available here: http://alexanderchuranov.com/boost-issues/ccahe-freebsd-7-boost-1.43/ The original filed issue is here: http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/151454 The patches for boost-libs port are here: http://www.freebsd.org/cgi/cvsweb.cgi/ports/devel/boost-libs/files/ Alexander Churanov, maintainer of devel/boost-* ports for FreeBSD

2 1

Question about commercial software and boost license
by marc_elias＠terra.es 18 Oct '10

18 Oct '10

Hi, I'm working in a company that want to use boost libraries to a commercial software. I have a pair of questions: 1. Is it possible to distribute under the boost license a commercial software (so the source code won't be exposed) programmed with static boost libraries? 2. And with linked libraries to an executable? Thanks in advance! MARC

3 2

[1.45] Release notes
by Daniel James 18 Oct '10

18 Oct '10

Hello all, Once more, it's time to prepare the release notes. If you want to add to them yourself, you can edit the source files in subversion here: http://svn.boost.org/svn/boost/website/public_html/beta/feed/history/ Or if you prefer, you can email me the details and I'll add it for you. Because the relevant web pages are now served as static files rather than as dynamic php pages, rebuilding the feeds won't change the web site. The process for generating the pages was a quick hack and is pretty horrible, so it's probably best if you leave that to me for this release. I'm writing a new python script to do all of this (the only requirement will be a quickbook executable), so hopefully it'll be a lot easier next time. Daniel

1 0

[network] cpp-netlib 0.7 ready to be released
by Dean Michael Berris 18 Oct '10

18 Oct '10

Hi Guys, I just wanted to give everyone interested a heads up on the progress being made on the cpp-netlib project (which I'm working on full-time at the moment). Basically: * There's now an asynchronous/active HTTP client implementation that returns response objects that encapsulate futures. This uses the Boost.Asio asynchronous socket interfaces to implement reads/writes on the active object. * The documentation has been moved from Quickbook to ReStructuredText and generated with Sphinx (and they look really nice if I may say so myself: http://mikhailberis.github.com/cpp-netlib/) * The message concept has been fleshed out and now requires external modifiers. * Requirement for OpenSSL has been dropped, now by default doesn't support HTTPS unless specified. This impending 0.7 release also uses more template metaprogramming tools from Boost.MPL to implement the tag dispatch mechanism to modify behaviors of the classes based on these tags. Policies were introduced and are chosen depending on the characteristics of the tags provided. Development on 0.8 shall include: * A more feature-complete HTTP server template that supports a worker thread pool where handlers get invoked, and where handlers can write data to the connection asynchronously. * A streaming HTTP client interface to support passing a raw stream associated with a socket to a handler function or as part of the response object returned. * A preliminary XMPP client implementation. * The beginnings of a web service framework on top of the HTTP server to allow for a more web-framework like feel, similar to how web frameworks like Tornado Web (http://tornadoweb.org/) Target release of 0.8 will be the first week of November. The development of cpp-netlib targets an end-of-year submission to the Boost Library, and hopefully those interested in the project can go ahead and try it out now so that I and the other developers can work on feature requests before that time -- and so that early evaluations can guide the direction of the development before December. Thanks everyone and I look forward to hearing from you! Note: You can find the documentation for cpp-netlib (which I presented at BoostCon 2010) at http://mikhailberis.github.com/cpp-netlib -- Dean Michael Berris deanberris.com

5 7

boost.foreach overhead
by Christopher Lux 18 Oct '10

18 Oct '10

On 10/9/2010 John Carmack of id Software wrote on his Twitter account: “@ID_AA_Carmack: It took 69 single steps to get past a BOOST_FOREACH() statement. Madness.” This made me think again about the overhead introduced with boost foreach. Is the overhead really this large as he makes it sound? Are there heuristics to when to use foreach according to the expected iteration counts? Regards -chris -- Christopher Lux | | Bauhaus-Universität Weimar | Faculty of Media - Virtual Reality Systems Group | Tel. +49 (0) 3643 - 58 3734

11 11

[network] cpp-netlib 0.7 released!
by Dean Michael Berris 18 Oct '10

18 Oct '10

Hi Everyone! So, I've been busy the past few hours doing a final push to get 0.7 out the door so that starting tomorrow I can start working on the 0.8 branch to improve the server-side HTTP implementation. Now, it's official, 0.7 is out the door and is ready for prime-time. ;-) In case you'd like to try it out, it's header only and you can download the 0.7 release from: http://github.com/cpp-netlib/cpp-netlib/downloads This has numerous improvements and enhancements over the 0.6 version, and has a more robust definition of the concepts included in the library. Now anybody can start extending cpp-netlib with their own protocol implementations using the common message type. If you want your work to integrate cleanly with the project, you can go ahead and fork my repository (as the project's "benevolent dictator for life") and submit pull requests in case you want to get your implementation/fixes/extensions into the main library distribution. As earlier stated, 0.8 will be a server-side focused development effort which will include a lot of cool things not just an improved HTTP server interface. If you'd like to discuss the effort or join the development, please feel free to send email to either the Boost Developer mailing list (because this library will be submitted for review and inclusion in Boost around December 2010) or the cpp-netlib developers mailing list. Thanks to everyone who's expressed interest, and those who have offered suggestions on the improvements to be made to the library. I hope everyone had a great weekend too! -- Dean Michael Berris deanberris.com

3 3

[OT] Calling Overmind
by John Phillips 18 Oct '10

18 Oct '10

Overmind, Would you please either contact me (John Phillips), or Ron Garcia off list? Thanks. John

1 0

3rd- party reliance for upcoming boost.GIL.IO library
by Christian Henning 17 Oct '10

17 Oct '10

Hi there, We are going to submit the Boost.GIL.IO extension for review and the package relies on 3rd-party libraries; can anyone suggest minimum solution for finding those libraries which would be usable for reviewers to build and run tests/examples? The library is pretty much ready for review and can be found here: http://gil-contributions.googlecode.com/files/boost_review.zip or via SVN, here: http://code.google.com/p/gil-contributions/source/browse/#svn/trunk/gil_2 Thanks, Christian

2 2

[unordered] error: template argument required for ‘struct set_extractor’
by Mateusz Loskot 17 Oct '10

17 Oct '10

Hi, I'm experiencing strange problem with unordered_map.hpp file. I'm using Boost 1.44 with GCC 4.2.1 from XCode on Mac OS X. Compiling simple test: $ cat foo.cpp #include <boost/unordered_map.hpp> int main() {} $ g++ -o foo.o foo.cpp In file included from /usr/local/include/boost/unordered/detail/equivalent.hpp:11, from /usr/local/include/boost/unordered/unordered_map.hpp:19, from /usr/local/include/boost/unordered_map.hpp:16, from foo.cpp:1: /usr/local/include/boost/unordered/detail/extract_key.hpp:31: error: template argument required for ‘struct set_extractor’ /usr/local/include/boost/unordered/detail/extract_key.hpp:77: error: template argument required for ‘struct map_extractor’ I've looked at the preprocessed file and there is something that disturbs me - templates of set_extractor and map_extractor are getting "changed". Comparing preprocessed file against source from boost/unordered/detail/extract_key.hpp I see 1) set_extractor a) original code template <class ValueType> struct set_extractor { typedef ValueType value_type; typedef ValueType key_type; b) preprocessed output struct set_extractor { template <class ValueType> struct apply { typedef ValueType value_type; typedef ValueType key_type; 2) map_extractor a) original code template <class Key, class ValueType> struct map_extractor { typedef ValueType value_type; typedef BOOST_DEDUCED_TYPENAME boost::remove_const<Key>::type key_type; b) preprocessed output struct map_extractor { template <class ValueType> struct apply { typedef ValueType value_type; typedef typename remove_const<typename ValueType::first_type>::type key_type; As you can see, the set_exctractor and map_exctractor templates have lost template parameters declarations and some extra nested struct has been generated: template <class ValueType> struct apply Folks on #boost at IRC suggested it may be caused by MPL magic. I haven't noticed any such problem with GCC 4.4 on Linux with Boost 1.43 There has been similar issue reported, but the problem was ALLOC macro defined by RICE library, what rather is not my case: http://lists.boost.org/boost-users/2010/05/59340.php Does anyone have an idea what's happening? Best regards, -- Mateusz Loskot, http://mateusz.loskot.net Charter Member of OSGeo, http://osgeo.org Member of ACCU, http://accu.org

2 3

[CfP] 5th Annual BoostCon, Aspen (CO, USA), May 15-20, 2011
by Hartmut Kaiser 16 Oct '10

16 Oct '10

Please distribute. ------------------ 5TH ANNUAL BOOST CONFERENCE 2011 Aspen CO, USA, May 15 - 20, 2011, www.boostcon.com CALL FOR PARTICIPATION We invite you to submit session proposals to the 5th Annual Boost Conference: BoostCon 2011 (Aspen CO, USA, May 15 - 20, 2011). Traditionally the main face-to-face event for all things Boost (www.boost.org) BoostCon 2011 will present leading speakers from the whole C++ community. >From using the Boost libraries to writing and maintaining them, from evangelizing to deploying Boost within your organization, from infrastructure and process to vision and mission, and the new C++ Standard, BoostCon brings together the sessions, the colleagues, and the inspiration to support your work with C++ and Boost in particular for the next year. To reflect the breadth of the Boost community, the conference includes sessions aimed at three constituencies: Boost end-users, hard-core Boost library and tool developers, and academics focusing on researcher. The program fosters interaction and engagement within and across those groups, with an emphasis on hands-on, participatory sessions. SESSION TOPICS Topics of interest include, but are not restricted to, the following: * General tutorial sessions introducing one or more Boost libraries * In-depth sessions on using specific Boost libraries * Case studies on using Boost * Experts panels * Advanced sessions on implementation techniques used within Boost libraries * C++0x and how it changes life for users and library writers * Development workshops to extend or enhance existing Boost libraries * Workshops on design process * Infrastructure workshops such as Build tools, Website, Testing * Concepts and Generic Programming * Hardware and infrastructure presentations focused on how libraries can make better use of the technology * Software development tools and their application to C++ and or Boost * Other topics likely to be of great interest to Boost users and developers Interactive and collaborative sessions are encouraged, as this is the nature of both the on-line Boost community and the style of learning and participation that has proven most successful at such events. Sessions can be tutorial based, with an emphasis on interaction and participant involvement, or workshop based, whether hands-on programming or paper-based, discussion-driven collaborative work. SESSION FORMATS Presentations ------------- Presentations focus on a practitioner's ideas and experience with anything relevant to Boost and Boost users. Panels ------------- Panels feature three or four people presenting their ideas and experiences relating to Boost's relevant, controversial, emerging, or unresolved issues. Panels may be conducted in several ways, such as comparative, analytic, or historic. Tutorials ------------- Tutorials are sessions at which instructors teach conference participants specific Boost-relevant skills. Workshops ------------- Workshops provide an active arena for advancements in Boost-relevant topics. Workshops provide the opportunity for experienced practitioners to develop new ideas about a topic of common interest and experience. Author's Corner Presentations These were introduced at BoostCon 2008, and were a great success. They are short (30 minute) sessions, focusing on tips on usage and design. In addition, we're looking to uncover the hidden design gems in Boost libraries. Tool Vendors Presentations We actively encourage tool vendors and ISP's to submit proposals for a special Tool Vendors Session Track aimed at products related to Boost and C++ (compilers, libraries, tools, etc.). Other formats may also be of interest. Don't hold back a proposal just because it doesn't fit into a pigeonhole. SUBMITTING A PROPOSAL Standard Sessions are 90 minutes. You may submit a proposal for fractions or multiples of 90-minutes. Fractional proposals will be grouped into 90 minute sessions covering related topics. Longer sessions, such as tutorials and classes, will be assigned 90 minute, three hour (i.e. half day), or six hour (i.e. full day) time slots. Please include: * The working title. * Type of session: presentation, panel, tutorial, workshop, authors corner, vendor track, other. * A paragraph or two describing the topic covered, suitable for the conference web site. * Proposed length: 10-20 minute short talks, 45 minutes, 90 minutes, half day, full day. * Alternate lengths, if you are willing to make adjustments: 10-20 minute short-talks, 45 minutes, 90 minutes, half-day, full day. * Audience: users, developers, both. * Level: basic, intermediate, advanced. * A biography, suitable for the conference web site. * Your contact information (will not be made public). SUBMISSION DETAILS All submissions have to be done through the EasyChair conference management system: http://www.easychair.org/conferences/?conf=boostcon2011. If you have not already registered at EasyChair, you will need to do so in order to submit your proposal. All submissions will go through a peer review process. Authors are invited (but are not required) to submit PDF versions of full papers of up to 10 pages in ACM conference proceedings format (see http://www.acm.org/sigs/publications/proceedings-templates) The full papers are not required unless you want them published in the proceedings. All accepted proposals will be made available in the Association for Computing Machinery (ACM) Digital Library (approval pending). Best papers, after further reviews, will be considered to be book chapters or journal articles in a renowned journal. The session materials go on the BoostCon website and will be available to attendees. For general information on the BoostCon 2011 paper submission or the scope of technical papers solicited, please refer to the conference website at www.boostcon.com. For any other questions about the submission process or paper format, please contact the Program Committee at boostcon2011(a)easychair.com. If you have any technical problems with EasyChair, please contact EasyChair for help. Note: Presenters must agree to grant a non-exclusive perpetual license to publish submitted materials, either electronically or in print, in any media related to BoostCon. IMPORTANT DATES Proposal submissions due: December 10th, 2011. Proposals decisions sent (tentative program available): January 17th, 2011. Fully scheduled program available: February 7th, 2011. Session materials due: April 15th, 2011. Hartmut Kaiser, email: hartmut.kaiser(a)gmail.com (Program Committee Chair) David Abrahams, email: dave(a)boostpro.com (Conference Chair) On behalf of the conference organizers

1 0

[Pointer Container] Modification of pointer containers to allow const elements
by Gerardo Hernández 16 Oct '10

16 Oct '10

The following code snippet: boost::ptr_vector<const int> v; v.push_back(new int); produces the following error message (Visual C++ 9, boost 1.44): boost\ptr_container\ptr_sequence_adapter.hpp(249) : error C2664: 'std::vector<_Ty,_Ax>::push_back' : cannot convert parameter 1 from 'const int *' to 'void *const &' The problem is that the underlying type of boost::ptr_vector<T> is always vector<void*>, no matter T is const. This prevents push_back() method from maintaining const-correctness. The rest of the pointer containers contain an equivalent problem and this has been a TODO for some time. According to Thorsten Ottosen (library author) ( https://svn.boost.org/trac/boost/ticket/3832 ): "The fix is basically just some meta-functions taking into account that T might be const, and if so, instantiate container<const void*> instead of container<void*>" To the vector problem, this means that the underlying type should be: vector<typename boost::mpl::if_<boost::is_const<T>, const void*, void*> > I have sucessfully applied this approach to the pointer containers that mimic STL counterparts (see attachment) and I guess it should work for the others. I need feedback on whether this is a completely correct approach and if so I would like to contribute a modification. Gerardo.

5 10

[optional] memory use for optional refs and ptrs
by Rutger ter Borg 15 Oct '10

15 Oct '10

Hello, I'm looking into boost::optional<> as a replacement for some of my code which has to deal with optional values. However, it seems that cases which are usually space-efficient optionals (e.g., ptrs in the form of a null-ptr) do not have template specializations. In other words, boost optional templates store a bool and the memory footprint of its template parameter, regardless of type. I.e., optional references and pointers take their space plus the space of an extra bool. Is there a reason for this? Thanks, Rutger

15 42

New Boostcon sessions uploaded
by Marshall Clow 14 Oct '10

14 Oct '10

Michael Caisse: Using Spirit V2: Qi and Karma http://blip.tv/dashboard/episode/4162161 Stephan T. Lavavej: Data Structure Visualizers in Visual Studio 2010 http://blip.tv/dashboard/episode/4162044 Matt Calabrese, Zachary Laine: Instantiations Must Go! http://blip.tv/dashboard/episode/4161957 Jeremy Siek: Generic Programming And the Boost Graph Library http://blip.tv/dashboard/episode/4161923 More to come (I'm shooting for one session every other day)..... -- Marshall

13 24

C++0x trailing return type
by Matt Calabrese 14 Oct '10

14 Oct '10

I'd like to introduce a macro to Boost.Config called BOOST_NO_TRAILING_RETURN_TYPE for checking if a compiler supports 0x trailing return types I.E. auto foo() -> void; Is there general agreement that this is an appropriate name for the macro? Now for a small rant -- in a recent thread, I talked about introducing a simple BOOST_AUTO_FUNCTION macro which I'll request review for shortly, as a way to simulate automatic return type deduction when writing functions and function templates. In experimenting with the macro, I have hit what I believe is either a bug in GCC or what I would consider a huge failing of C++0x trailing return types (someone please aid me in figuring this out). One of the main reasons why trailing return types are helpful is that the arguments to the function or function template you are writing are able to be refered to when forming the return type, however, when dealing with non-static member functions, it seems to me that you are not able to refer to "this" or non-static members. This greatly reduces the usefulness of trailing return types, as all of the reasons why you would want to refer to the parameters apply with the same rationale to why you would want to refer to members and "this". I've skimmed through the standard and see no explicit mention of or examples of using trailing return types in this manner. Perhaps someone here can help parse the standard-ese to clarify? I'd hope that you could refer to non-static members, but I see no evidence of that. One example of why this is frustrating in practice can be seen in the following hypothetical code for a Boost.Variant-style template with an "emplace" member-function that is intended to construct an object in-place similar to the emplace family of member functions of C++0x containers: http://codepaste.net/u5nfis Here, the trailing return type is used almost exclusively for extended SFINAE, though you often wish to refer to members in other cases as well where SFINAE isn't of any concern. The overall goal with the implementation of emplace being as such is to attempt to force substitution to fail if any of the following cases were true: if "Type" does not have a constructor taking the forwarded arguments if "Type" is not one of the types that is able to be stored in the template and possibly even something else I've missed (...which is a good thing...) Essentially we want substitution to fail if the instantiation of the body would fail, giving a very basic equivalent to low-level, syntax-only, automatic concept-checking. The benefit of this speaks for itself. Here, at least in my opinion, such code is very concise, very powerful, and surprisingly readable. Without such functionality of trailing return types we can only do marginally better than we've been doing for the past 10 years. So if someone could help me determine whether or not what I'm trying to do is standard I'd be grateful, and if such functionality is not standard, is it too late for it to be added? It seems to me that the benefits with respect to library development here are too great for a community like Boost to ignore, though I myself am not familiar enough with the standardization process to make an impact. Thanks. It appears this rant has overshadowed the original question, though please don't forget to respond. -- -Matt Calabrese

4 3

Schedule on www.boost.org
by Rene Eng 14 Oct '10

14 Oct '10

Hi all Following the release schedule on www.boost.org, preparations for the release 1.45 are already underway. But I have not read anything here on the mailing list yet. Could somebody please either confirm the intention to keep those release dates, or otherwise adjust the dates in the release schedule? Thank you very much in advance René Eng -- “Dubito ergo cogito; cogito ergo sum. (I doubt, therefore I think; I think therefore I am)” René Descartes

2 1

[geometry]
by Paul Blampspied 13 Oct '10

13 Oct '10

I have been looking at the advance version of [boost][geometry]. I think it is very useful and very well worked out. I have a question. Does [geometry] support the idea of a frame of reference ? I believe not, but it may be that I have missed some way of achieving this. By reference frame I mean that some points are not directly comparable if they are in different frames of reference. This is distinct from different coordinate systems (I think). For example we could have two geographic coordinate systems, one referring to lat./long. on earth and another to Mars. the points on these two reference frames should not be comparable and should give a compile error. Can this be done in [geometry] ? More interestingly we could use two distinct reference frames for convenience, even though there is a known relation between them. It would be nice if point conversions between the two frames could be carried out (possibly implicitly). For example, I would like to do something like this: ShiftAndRotateTransform<EgocentricFrame, WorldFrame> EgoFrame_WorldFrame_Transform(10, 20, 90); //Shift by [10,20] and rotate 90deg. WorldFrame Test() { WorldFrame p1 = EgoFrame(0,0); EgocentricFrame p2 = WorldFrame(p1); return p2; //IMPORTANT - p2 is implicitly transformed to WorldFrame when returned from Test function. } I have managed to implement a very simple scheme which allows this to compile and work successfully, but I am not completely satisfied with my homebrew scheme. In particular, I am forced to declare the WorldFrame and EgoFrame classes and provide all the constructors for them. It is necessary to explicitly provide constructors for all the reference frames which can be converted - implying that this is known at the time the class is written. It is more flexible to use overloaded functions, because these can be added as required e.g. //The second argument is the output point which is modified. ChangeReferenceFrame(WorldFrame &p1, EgocentricFrame &p2); ChangeReferenceFrame(EgocentricFrame &p1, WorldFrame &p2); ChangeReferenceFrame(EgocentricFrame &p1, SomeNewFrameType &p2); However the syntactic convenience and possibility of implicit conversion is lost. I wonder if some sleight of template magic could allow the extensibility of the second approach with the usability of the first. The starting point would be to allow a class representing the transform between the two frames of reference to be declared. This should attempt to define as much of the machinery as possible. It seems to me that these facilities have no impact on the existing design of [geometry], but concern an extension to allow reference frames to be defined and related.

2 3

License question
by David Bellot 13 Oct '10

13 Oct '10

Hi guys, I'm working on a new library for some specific A.I and machine learning problems and I will release it as a Free Software of course. However, I wonder if you guys can enlighten me regarding license. This library will be template-based for some parts and compiled for other parts. I don't want to restrict users in what they're doing with the library, I mean they can use it for open-source or closed-source products. However, I want to decently protect my work and because it's template-based and can be used in commercial products, I don't want someone to do closed-source fork of it and all those kind of things... I selected to candidates: Boost and LGPL. So question: - do I have to use a Boost license or a LGPL license ? - and why not using GPL directly or is it too restrictive ? Thanks for your help, David (also boost::ublas maintainer when not doing statistics ;-) ) -- David Bellot, PhD david.bellot(a)gmail.com http://david.bellot.free.fr

5 5

Re: [boost] [function] function wrapping with no exception safety guarantee
by Dave Abrahams 12 Oct '10

12 Oct '10

On Tuesday, October 12, 2010, Emil Dotchevski <emil(a)revergestudios.com> wrote: > On Tue, Oct 12, 2010 at 4:04 PM, Daniel Walker > <daniel.j.walker(a)gmail.com> wrote: >> Formally, boost::function invocation has strong exception safety if >> invoking the target function has strong exception safety. > > This makes no sense at all. Invoking boost::function always has strong > exception safety guarantee. In no way it can make the state of the > boost::function object inconsistent, because it does not modify its > state. Sounds like you're talking about the basic guarantee here. > _____________________________________________ -- Dave Abrahams BoostPro Computing http://www.boostpro.com

2 1

Nightly tests failed with filesystem problem
by Belcourt, Kenneth 12 Oct '10

12 Oct '10

Hi, Tests failed last night for a problem with v3/src/operations.cpp. gcc.compile.c++ /scratch/boost/boost/bin.v2/libs/filesystem/build/ gcc-4.1.2/release/link-static/v3/src/operations.o "g++" -ftemplate-depth-128 -O3 -finline-functions -Wno-inline -Wall - DBOOST_ALL_NO_LIB=1 -DBOOST_SYSTEM_STATIC_LINK=1 -DNDEBUG -I"/scratch/ boost/ boost" -c -o "/scratch/boost/boost/bin.v2/libs/filesystem/build/ gcc-4.1.2/release/link-static/v3/src/operations.o" "/scratch/boost/ boost/libs/filesystem/v3/src/operations.cpp" /scratch/boost/boost/libs/filesystem/v3/src/operations.cpp: In function ‘boost::filesystem3::file_type<unnamed>::query_file_type(const boost::filesystem3::path&, boost::system::error_code*)’: /scratch/boost/boost/libs/filesystem/v3/src/operations.cpp:467: error: no matching function for call to ‘symlink_status(const boost::filesystem3::path&, boost::system::error_code*&)’ /scratch/boost/boost/boost/filesystem/v3/operations.hpp:209: note: candidates are: boost::filesystem3::file_status boost::filesystem3::symlink_status(const boost::filesystem3::path&) /scratch/boost/boost/boost/filesystem/v3/operations.hpp:211: note: boost::filesystem3::file_status boost::filesystem3::symlink_status(const boost::filesystem3::path&, boost::system::error_code&) Can someone please take a look? Thanks. -- Noel

1 0

[proto] Writing a transform to get at an inner constant of a transform result type
by Sebastian Redl 12 Oct '10

12 Oct '10

Hi, The subject is probably very confusing. I'm back to playing with a proto-based library for vector types. I have a basic underlying vector template, simd_impl: template <typename T> struct simd_impl { static const size_t size = VECTOR_BYTES / sizeof(T); // data }; And I have a grammar, Simd struct Simd : proto::or_< SimdLiteral, SimdUnary, SimdVectorBinary, SimdMixedBinary > {}; where SimdLiteral is an enumeration of proto::terminal<simd_impl<T>> where T are various underlying types, SimdUnary are unary operations, SimdVectorBinary are combinations of two vectors, and SimdMixedBinary are combinations of vectors with scalars. SimdVectorBinary is currently defined approximately like this: struct SimdVectorBinary : proto::or_< proto::when<proto::plus<Simd, Simd>, exec::simd_plus(Simd(_left), Simd(_right))>, // more operators here > {}; Now I want to validate, in the grammar, that you only add two vectors of the same arity together. That is, I'm fine with adding simd_impl<long> and simd_impl<int> together if they have the same size, because both have the same number of elements, but adding simd_impl<short> and simd_impl<int> together doesn't work, as one has twice the number of elements as the other. But I can't figure out how to write a grammar that validates this. I've started something like this: struct VSizeMatches : proto::if_<mpl::equal_to<Arity(proto::_left), Arity(proto::right)>()> {}; but I think that's wrong, and I can't figure out how to write Arity anyway. Basically, I have to find the simd_impl<T> type that the result of my Simd transform has and then access the size member. But I'm kinda afraid that this will get me into a world of trouble with prematurely instantiated templates. Any advice? Sebastian

2 2

Re: [boost] [Review] Formal Review of Proposed Boost.RatioLibrary IS UNDERWAY
by Tan, Tom (Shanghai) 12 Oct '10

12 Oct '10

Hi, Here my review. ----- Original Message ----- From: "Anthony Williams" <anthony.ajw(a)gmail.com> Subject: [boost] Reminder: [Review] Formal Review of Proposed Boost.RatioLibrary IS UNDERWAY >> Here are some questions you might want to answer in your review: >> >> - What is your evaluation of the design? As others already mentioned, it follows the C++ Standards Committee's current Working Paper. That's good. >> - What is your evaluation of the implementation? - Code is clear and easy to read and understood. - BOOST_INTMAX_C is the only macro that's defined in ratio.hpp but not staring with BOOST_RATIO_. As the name suggests, it'll be better 1) if placed in boost/cstdint.hpp, or 2)be named as BOOST_RATIO_INTMAX_C indicating that it's used for boost.ratio only, I personally prefer option 1). - I would expect the comments are better cleaned up and the style unified. Right now, //, //-, //~, /**/ are all used, which seems confusing. I personally like the style adopted in boost.asio. >> - What is your evaluation of the documentation? - It's always a pleasure to read documents generated with BoostBook Documentation Format, - In the tutorial section, it'll be great if more examples are appended so that one example for each supported arithmetic and comparison operations, considering boost.ratio is a small one, doing so won't explode the tutorial section but gives a more complete picture of the lib. >> - What is your evaluation of the potential usefulness of the library? I can think of two scenarios: 1) It could quite useful in physical measurement of time, length, weight and the like where values of different units are being calculated. 2) It could be useful in expressing large rational number (Can anyone please let me know whether ratio is short for rational or a complete word itself? It seems either is OK, though I still wonder) >> - Did you try to use the library? With what compiler? Did you have any problems? Yes, indirectly through using boost.chrono, which is based on boost.ratio. VC10 on Windows 7, GCC4.4 w/ mingwin on widows 7. GCC4.4 on Ubuntu 10.4 No problem with the latest version from boost sandbox. >> - How much effort did you put into your evaluation? A glance? A quick reading? In-depth study? I did have some in-depth reading of previous versions of the code & documentation while I was started using boost.chrono, though not line by line. I also did a deep reading of C++ Standards Committee's current Working Paper (n2661in order to understand the why and how of ratio class then. While doing this review, I had a thorough reading of the code and documentation, which costs about half a day (including expressing my comments in English). >> - Are you knowledgeable about the problem domain? Intermediate. >> - Do you think the library should be accepted as a Boost library? Yes.

3 2

construe_cast, call for interest and feedback
by Jeroen Habraken 11 Oct '10

11 Oct '10

Hi, I'm proud to say I've tagged a version 0.2 of construe_cast some minutes ago. For those unfamiliar with the library (it's the first time I'm posting this to the boost mailinglist), it's a library which builds upon boost.spirit to create a cast-like operator aiming to provide an alternative to lexical_cast providing greater speed and flexibility. The current code can be found at http://github.com/VeXocide/construe_cast and should be compatible with boost version 1.42.0 and up. What can it do, in short, boost::construe_cast<int>("23") and boost::construe_cast<std::string>(23); (and a lot of other types, basically the ones boost.spirit supports). Secondly, since this release, boost::construe_cast<std::string, tag::bin>(23) resulting in a std::string("10111") and visa versa. The user has the ability to add functionality here by implementing extra tags, by default tag::bin, tag::oct and tag::hex are implemented, with more to follow. What I'm hoping to add the coming weeks: - Documentation, I'm somewhat ashamed to say this hasn't been written yet, however, this will be tackled shortly. - Support for different encodings, it currently uses standard (ASCII) and standard_wide for wchar_t, with more to follow. - A nothow version, like lexical_cast it currently throws when it encounters a run-time, an interface returning false or a default value will be included (the exact interface hasn't been decided upon yet). Performance, now this is where it gets hard. I've done some basic benchmarking and it's somewhere between one and five times as fast as lexical_cast, depending on what you're casting. Good compilers (I've notices this with gcc 4.4 and up for example) are actually capable of optimizing boost::construe_cast<int>("23") to the integer 23 at compile-time which makes it tricky to benchmark. If anyone with more benchmarking experience is willing to look into this, please do. Again, thanks to everyone who helped me get this far, and Hartmut in particular. There seems to be little to add at the moment, I'm looking forward to your opinions and insights. Regards, Jeroen Habraken P.S. I've had a few responses about the name, construe is an english word (http://www.thefreedictionary.com/construe) and I'm using construe_cast as a working name. If people are ever going to consider this for inclusion with boost, changing the name will surely be the least of my worries.

11 20

[units] missing merge of autoprefix to release
by Jürgen Hunold 11 Oct '10

11 Oct '10

Hi ! I was quite surprised that the "autoprefix" feature is not available in the current release branch. I found that the merge from the development branch to trunk was done in r62532. The issue is https://svn.boost.org/trac/boost/ticket/3660 Any chance this can be merged to release ? Yours, Jürgen -- * Dipl.-Math. Jürgen Hunold ! Ingenieurgesellschaft für * voice: ++49 511 262926 57 ! Verkehrs- und Eisenbahnwesen mbH * fax : ++49 511 262926 99 ! Lister Straße 15 * juergen.hunold(a)ivembh.de ! www.ivembh.de * * Geschäftsführer: ! Sitz des Unternehmens: Hannover * Prof. Dr.-Ing. Thomas Siefer ! Amtsgericht Hannover, HRB 56965 * PD Dr.-Ing. Alfons Radtke !

2 3

[Review] Formal Review of Proposed Boost.Ratio Library FINAL DAY
by Anthony Williams 11 Oct '10

11 Oct '10

Hi everyone, Today is the FINAL DAY for the review of Vicente Botet' Ratio library. If you haven't already posted a review, please do so today. What is it? ======== Portable implementation of the C++0x Standard Library's compile-time rational arithmetic working on C++03 and C++0x compilers. See the current C++0x working draft at http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2010/n3126.pdf Boost.Ratio provides: * A class template, ratio, for specifying compile time rational constants such as 1/3 of a nanosecond or the number of inches per meter. ratio represents a compile time ratio of compile time constants with support for compile time arithmetic with overflow and division by zero protection * It provides a textual representation of boost::ratio<N, D> in the form of a std::basic_string. Other types such as boost::duration can use these strings to aid in their I/O. This library is header-only and is designed to be generic and useful in a lot of areas of math and numerics C++ programming, in particular it is absolutely needed for the proposed Boost.Chrono and Boost.Stopwatches libraries which are currently in the review queue. Getting the library ============= The latest version of this library may be downloaded from vault: http://www.boostpro.com/vault/index.php?action=downloadfile&filename=ratio.… SVN: http://svn.boost.org/svn/boost/sandbox/chrono (directories boost/ratio and libs/ratio) and the docs may be viewed here html: http://svn.boost.org/svn/boost/sandbox/chrono/libs/ratio/doc/html/index.html pdf: http://svn.boost.org/svn/boost/sandbox/chrono/libs/ratio/doc/ratio.pdf You can get all these information also (which should avoid some long links) from http://svn.boost.org/trac/boost/wiki/LibrariesUnderConstruction#Boost.Ratio It is worth noting that the tests included in the zip file are relatively sparse. Vicente has an extensive suite of tests licensed under the LLVM license. He has posted a message on the Boost Developers mailing list regarding the license requirements for tests (See http://thread.gmane.org/gmane.comp.lib.boost.devel/208978) and is awaiting the outcome of that discussion before making the tests available. Writing a review ================ If you feel this is an interesting library, then please submit your review to the developer list (preferably), or to the review manager. 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. Anthony Review Manager for the proposed Boost.Ratio library -- Author of C++ Concurrency in Action http://www.stdthread.co.uk/book/ just::thread C++0x thread library http://www.stdthread.co.uk Just Software Solutions Ltd http://www.justsoftwaresolutions.co.uk 15 Carrallack Mews, St Just, Cornwall, TR19 7UL, UK. Company No. 5478976

2 1

Boost Evolution
by Robert Ramey 11 Oct '10

11 Oct '10

Boost is getting bigger and bigger. This is a good thing. The Boost header directory and boost namespace is also getting bigger and bigger. This is starting to become a problem. I would like to see: a) new libraries not add headers to boost directory or namespace. - with the possible exception - of "convenience headers" which include all the other headers for a library. Personally I don't like these, but since one doesn't have to use them its not a huge deal. b) authors of existing libraries which are implemented in boost directory/namespace would be encouraged to migrate them to a lower level. c) a couple of "catch all" namespaces/headers would be required such as "utility" for small libraries. I'm somewhat confused about "detail". If it's an implemenation detail of a particular library it should be in that library. If its a useful function which is shared by several libraries, it should be in something like: "unreviewed". And of course these should have thier test and documenations in the corresponding "lib" subdirectory. As boost get's bigger and bigger, it gets harder and harder to install just a part of it. But installing just a part of it is what users need to become confident about it. I realize that we've been circling around this topic for a while, I just want to keep it alive. Robert Ramey

9 16

[Review] Final Few Days for Formal Review of Proposed Boost.Ratio Library
by Anthony Williams 10 Oct '10

10 Oct '10

Hi everyone, If you have already posted a review, then thank you. For the rest of you: the review of Vicente Botet' Ratio library runs until October 11th, 2010 (this coming Monday), so please submit your reviews. What is it? ======== Portable implementation of the C++0x Standard Library's compile-time rational arithmetic working on C++03 and C++0x compilers. See the current C++0x working draft at http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2010/n3126.pdf Boost.Ratio provides: * A class template, ratio, for specifying compile time rational constants such as 1/3 of a nanosecond or the number of inches per meter. ratio represents a compile time ratio of compile time constants with support for compile time arithmetic with overflow and division by zero protection * It provides a textual representation of boost::ratio<N, D> in the form of a std::basic_string. Other types such as boost::duration can use these strings to aid in their I/O. This library is header-only and is designed to be generic and useful in a lot of areas of math and numerics C++ programming, in particular it is absolutely needed for the proposed Boost.Chrono and Boost.Stopwatches libraries which are currently in the review queue. Getting the library ============= The latest version of this library may be downloaded from vault: http://www.boostpro.com/vault/index.php?action=downloadfile&filename=ratio.… SVN: http://svn.boost.org/svn/boost/sandbox/chrono (directories boost/ratio and libs/ratio) and the docs may be viewed here html: http://svn.boost.org/svn/boost/sandbox/chrono/libs/ratio/doc/html/index.html pdf: http://svn.boost.org/svn/boost/sandbox/chrono/libs/ratio/doc/ratio.pdf You can get all these information also (which should avoid some long links) from http://svn.boost.org/trac/boost/wiki/LibrariesUnderConstruction#Boost.Ratio It is worth noting that the tests included in the zip file are relatively sparse. Vicente has an extensive suite of tests licensed under the LLVM license. He has posted a message on the Boost Developers mailing list regarding the license requirements for tests (See http://thread.gmane.org/gmane.comp.lib.boost.devel/208978) and is awaiting the outcome of that discussion before making the tests available. Writing a review ================ If you feel this is an interesting library, then please submit your review to the developer list (preferably), or to the review manager. 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. Anthony Review Manager for the proposed Boost.Ratio library -- Author of C++ Concurrency in Action http://www.stdthread.co.uk/book/ just::thread C++0x thread library http://www.stdthread.co.uk Just Software Solutions Ltd http://www.justsoftwaresolutions.co.uk 15 Carrallack Mews, St Just, Cornwall, TR19 7UL, UK. Company No. 5478976

3 3

Variadic Data Library in sandbox
by Edward Diener 09 Oct '10

09 Oct '10

I have put in the sandbox the Variadic Macro Data library, or VMD. This library supplies variadic macro functionality and integrates variadic macros with the Boost PP library without changing the latter in any way. The library in the sandbox is in the variadic_macro_data folder. The library is a header-only library of macros. There is documentation and tests and the appropriate jamfiles for both. To build the documentation you need doxygen but I have also provided documentation in an html subfolder. The main use of the library is to be able to pass variadic data to macros, and in particular to extract variadic data elements or convert variadic data to Boost PP data types for use by Boost PP. The library also enhances the Functionality of Boost PP tuple data. Installation is simply to take the boost and lib subfolders of the library and copy them to a Boost installation, preferable the trunk where support for variadic macros has been added in Boost config in the form of a BOOST_NO_VARIADIC_MACROS which is defined for compilers/versions which do NOT support variadic macros. To use the macros in the library, just "#include <boost/variadic_macro_data/VariadicMacroData.hpp>". Compilers which support variadic macros are gcc 3.0 and above and VC8 ( VS2005 ) and above among a few others. There is a discussion in the doc of why you might choose to use variadic macros rather than a Boost PP data type in a macro tailored for end-users. Comments, suggestions, and bug reports are welcome. Edward Diener

2 2

[Locale] Stream manipulator bug
by Alexander Lamaison 09 Oct '10

09 Oct '10

The latest version of Boost.Locale is doing something wierd to stream manipulators. For example, the following code should print 63:2c:7f. If you uncomment the line that sets the global locale to use a boost::locale instance, it prints 990:440:127. It seems to be ignoring the std::hex manipulator and doing something strange with std::width. #include <iomanip> #include <iostream> #include <sstream> #include <string> #include <vector> #include <boost/locale.hpp> std::string hexify() { std::ostringstream hex_hash; hex_hash << std::hex << std::setfill('0'); unsigned int data[] = {99, 44, 127}; for(size_t i = 0; i < 3; ++i) { if (!hex_hash.str().empty()) hex_hash << ":"; hex_hash << std::setw(2) << data[i]; } return hex_hash.str(); } int main() { using boost::locale::generator; generator gen; //std::locale::global(gen("")); std::cout << hexify() << std::endl; } This is on Windows 7 with Boost.Locale compiled to only use the Win32 backend. Alex -- Easy SFTP for Windows Explorer (http://www.swish-sftp.org)

2 1

[Review] Boost.Ratio
by joel falcou 09 Oct '10

09 Oct '10

So here is my review of Boost.Ratio *- What is your evaluation of the design?* It's a strictly (or at least as struct as possible) implementation of the standard proposal. Code is clear and easily followed. *- What is your evaluation of the implementation?* It's very OK and straightforward. I'll reiterate the question about providing MPL or Fusion adaptors as an optional features (unless I missed them :x) *- What is your evaluation of the documentation?* Good *- What is your evaluation of the potential usefulness of the library?* Ratio fills a gap in the MPl-like data type and enables new interesting design to be done. *- Did you try to use the library? With what compiler? Did you have any problems? * I tried it using gcc 4.4 and 4.5 and icc 11. No problem so far. *- How much effort did you put into your evaluation? A glance? A quick reading? In-depth study? * I quickly glanced over the code as I knew it from its inception and followed it so I only had to look some new stuff. I tried some non trivial task , including some attempt at MPL like CT linear system solver using rational. boost.ratio proved itself useful in this task. *- Are you knowledgeable about the problem domain? * Yes. *- Do you think the library should be accepted as a Boost library?* Yes

2 3

[Boost][Proto] Fw:[Spirit-general] Patch for compiling Karma without RTTI
by Bryce Lelbach 08 Oct '10

08 Oct '10

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Forwarding from the spirit-general mailing list. Begin forwarded message: Date: Fri, 08 Oct 2010 12:01:55 +0800 From: Joel de Guzman <joel(a)boost-consulting.com> To: spirit-general(a)lists.sourceforge.net Subject: Re: [Spirit-general] Patch for compiling Karma without RTTI On 10/8/2010 10:34 AM, Bryce Lelbach wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Summary: > > 0x0.) There's a workaround header for compilers without > typeinfo/typeid in boost/detail/sp_typeinfo.hpp. It has a few macros > that uses real typeid/typeinfo if it exists, and the workaround if > not. The workaround was broken on GCC 4.5.1 and clang (rebuilt daily > from upstream trunk). I fixed the problem (static initialization > jazz). > > 0x1.) Spirit's hold_any uses typeinfo/typeid. I changed it to use > the aforementioned macros. > > 0x2.) Some debugging stuff in one proto file used RTTI. I changed > it to use the aforementioned macros. > > I haven't had a need for Qi/Lex yet. I'm currently putting the > finishing touches on the ariel driver. My intention is to use Qi for > my lightweight command line parsing needs, because it will be less > painful than spending half an hour browsing through LLVM doxygen to > figure out how their cl parser works. So, there might be another one > of these patches in the morning. > > Patch was generated via svn diff from the top of my local copy of the > Boost trunk (on Debian GNU/Linux). I suggest sending an email to the Boost mailing list non-spirit related patches (and accompanying explanations). We don't have control over those parts (e.g. proto and boost/detail/sp_typeinfo.hpp) Regards, - -- Joel de Guzman http://www.boostpro.com http://spirit.sf.net - ------------------------------------------------------------------------------ Beautiful is writing same markup. Internet Explorer 9 supports standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 & L3. Spend less time writing and rewriting code and more time creating great experiences on the web. Be a part of the beta today. http://p.sf.net/sfu/beautyoftheweb _______________________________________________ Spirit-general mailing list Spirit-general(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/spirit-general - -- Bryce Lelbach aka wash http://groups.google.com/group/ariel_devel -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkyumQMACgkQO/fqqIuE2t63WwCg2lT+hIeoy9xISTU73PwRE/FD G9sAoNQwHDIMMPYO1GbDiWYP0lco/crH =iU+P -----END PGP SIGNATURE-----

4 4

Re: [boost] [Spirit-general] construe_cast, call for interest and feedback
by Jeroen Habraken 07 Oct '10

07 Oct '10

On 7 October 2010 22:43, Aaron Graham <aaron(a)aarongraham.com> wrote: > I'm excited about construe_cast. I always liked the flexibility of > lexical_cast, but tend not to use it as much as I could because of its > performance relative to other mechanisms. > Does gcc still convert "23" at compile time if you disable builtins? > (-fno-builtin) > #include <boost/construe_cast.hpp> int main(int, char**) { return boost::construe_cast<int>("23"); } compiled using gcc 4.5.1, g++-4.5 test.cpp -o test -O3 -I . -I ../library/boost-trunk/ -fno-builtin will generate the following code: Dump of assembler code for function main: 0x0000000100000e20 <main+0>: push %rbp 0x0000000100000e21 <main+1>: mov $0x17,%eax 0x0000000100000e26 <main+6>: mov %rsp,%rbp 0x0000000100000e29 <main+9>: leaveq 0x0000000100000e2a <main+10>: retq 0x0000000100000e2b <main+11>: nopl 0x0(%rax,%rax,1) thus as you can see, it's still able to perform the optimization. Jeroen

1 0

[Review] Formal Review of Proposed Boost.Ratio Library Starts TODAY
by Anthony Williams 07 Oct '10

07 Oct '10

Hi everyone, The review of Vicente Botet' Ratio library starts TODAY (October 2nd) and lasts until October 11th, 2010, unless an extension occurs. What is it? ======== Portable implementation of the C++0x Standard Library's compile-time rational arithmetic working on C++03 and C++0x compilers. See the current C++0x working draft at http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2010/n3126.pdf Boost.Ratio provides: * A class template, ratio, for specifying compile time rational constants such as 1/3 of a nanosecond or the number of inches per meter. ratio represents a compile time ratio of compile time constants with support for compile time arithmetic with overflow and division by zero protection * It provides a textual representation of boost::ratio<N, D> in the form of a std::basic_string. Other types such as boost::duration can use these strings to aid in their I/O. This library is header-only and is designed to be generic and useful in a lot of areas of math and numerics C++ programming, in particular it is absolutely needed for the proposed Boost.Chrono and Boost.Stopwatches libraries which are currently in the review queue. Getting the library ============= The latest version of this library may be downloaded from vault: http://www.boostpro.com/vault/index.php?action=downloadfile&filename=ratio.… SVN: http://svn.boost.org/svn/boost/sandbox/chrono (directories boost/ratio and libs/ratio) and the docs may be viewed here html: http://svn.boost.org/svn/boost/sandbox/chrono/libs/ratio/doc/html/index.html pdf: http://svn.boost.org/svn/boost/sandbox/chrono/libs/ratio/doc/ratio.pdf You can get all these information also (which should avoid some long links) from http://svn.boost.org/trac/boost/wiki/LibrariesUnderConstruction#Boost.Ratio It is worth noting that the tests included in the zip file are relatively sparse. Vicente has an extensive suite of tests licensed under the LLVM license. He has posted a message on the Boost Developers mailing list regarding the license requirements for tests (See http://thread.gmane.org/gmane.comp.lib.boost.devel/208978) and is awaiting the outcome of that discussion before making the tests available. Writing a review ================ If you feel this is an interesting library, then please submit your review to the developer list (preferably), or to the review manager. 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. Anthony Review Manager for the proposed Boost.Ratio library -- Author of C++ Concurrency in Action http://www.stdthread.co.uk/book/ just::thread C++0x thread library http://www.stdthread.co.uk Just Software Solutions Ltd http://www.justsoftwaresolutions.co.uk 15 Carrallack Mews, St Just, Cornwall, TR19 7UL, UK. Company No. 5478976

6 12

[Concept Check] ContiguousIterator
by joel falcou 07 Oct '10

07 Oct '10

Using BCC, s there any way to refine RandomAccessIterator so the cocnept captures the fact that the address of two consecutive value iterated over are contiguous in memory ? I can't get any proper expression to check for this in a proper way.

6 7

[xpressive] Support for multi-capture and balancing groups
by Erik Rydgren 07 Oct '10

07 Oct '10

Hi! My company have been using pcre for a long while but there has been gripes about it only returning the last matched value from a capture group. Because of this I have been searching for a C++ regex engine that can handle the same stuff as the .NET implementation can do, to no avail. During my searches I've stumbled on several forum threads where others have been searching for the same thing but it doesn't seem to exist a regular expression library in C/C++ that handles both named captures and multicapture. Found boost.xpressive and it had almost everything we need. It's open source, fast, got flexible api and named captures. But alas, just as all other C and C++ based implementations I have found, it lacked multiple captures. So, I added it. On top of that I added support for balancing groups (http://blog.stevenlevithan.com/archives/balancing-groups) But the syntax for the pop capture and capture conditional is slightly different then the .NET version to better fit xpressive. Syntax for pop capture: dynamic: (?P<-name>stuff) static: (name -= stuff) Syntax for capture conditional: dynamic: (?P(name)stuff) static: (name &= stuff) There is no support for the (?<name-othername>stuff) construct. All captures made by a group is stored in sub_match::captures which is a vector of sub_match_capture objects. A sub_match_capture behaves like a stripped down sub_match. It can be put in an ostream and has a length and helper function for returning a string. The changes are in the vault and can be found here: http://tinyurl.com/3aak7mp It can be unpacked against trunk from 2010-10-02 or the 1.44.0 release. I've run the dynamic regression tests without errors and I have added some tests for the new functionality. The code it only tested on Visual Studio 2010 since I don't have access to any other compiler. Please give feedback on my changes since I would love to see them in an official release. Thanks in advance. Regards, Erik

3 6

[fusion] for_each
by Christophe Henry 06 Oct '10

06 Oct '10

Hi, I have 2 fusion containers: a small vector (my_vec) and a bigger set (my_set). I want to overwrite the elements of the set with elements from the vector whenever they have the same type. Sounds simple: struct update { update(my_set_type& to_overwrite_):to_overwrite(to_overwrite_){} template<typename T> void operator()(T& elt) /*const?*/ { boost::fusion::at_key<T>(to_overwrite)=elt; } my_set_type& to_overwrite; }; boost::fusion::for_each(my_vec,update(my_set)); Except that this won't compile because the operator() is required to be const, which is sad, because it was very simple. This leaves me with the unattractive option of inverting the set and the vector inside update. Now, I iterate on the set's elements and overwrite them when found in the vector. This is unattractive because 1) the code gets really ugly 2) it could be slower (the set is bigger) and 3) it has a much bigger compile-time cost (I resorted to an enable_if of fusion::result_of::find and I make it short, it is actually much worse). I thought of using transform, but this will be slower as I will need to transform every element of the set, even for a vector of size 1. Am I missing something? If not, would it be possible to remove this constraint? Thanks, Christophe

4 6

[Range] Composite Range
by Robert Jones 06 Oct '10

06 Oct '10

Is there any facility supported in Boost to provide a 'composite' range? I.e., a range that might be a vector, followed by a bit of list, followed by a pair of iterators? I guess the iterator classification of such a range would be the lowest common denominator of the classifications of all the component iterators, and I don't even want to think about how sort() would work, but it might be quite handy. - Rob.

3 4

[Review] Formal Review: Boost.Ratio
by Anthony Williams 06 Oct '10

06 Oct '10

Hi everyone, The review of Vicente Botet' Ratio library starts October 2nd and lasts until October 11th, 2010, unless an extension occurs. What is it? ======== Portable implementation of the C++0x Standard Library's compile-time rational arithmetic working on C++03 and C++0x compilers. See the current C++0x working draft at http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2010/n3126.pdf Boost.Ratio provides: * A class template, ratio, for specifying compile time rational constants such as 1/3 of a nanosecond or the number of inches per meter. ratio represents a compile time ratio of compile time constants with support for compile time arithmetic with overflow and division by zero protection * It provides a textual representation of boost::ratio<N, D> in the form of a std::basic_string. Other types such as boost::duration can use these strings to aid in their I/O. This library is header-only and is designed to be generic and useful in a lot of areas of math and numerics C++ programming, in particular it is absolutely needed for the proposed Boost.Chrono and Boost.Stopwatches libraries which are currently in the review queue. Getting the library ============= The latest version of this library may be downloaded from vault: http://www.boostpro.com/vault/index.php?action=downloadfile&filename=ratio.… SVN: http://svn.boost.org/svn/boost/sandbox/chrono (directories boost/ratio and libs/ratio) and the docs may be viewed here html: http://svn.boost.org/svn/boost/sandbox/chrono/libs/ratio/doc/html/index.html pdf: http://svn.boost.org/svn/boost/sandbox/chrono/libs/ratio/doc/ratio.pdf You can get all these information also (which should avoid some long links) from http://svn.boost.org/trac/boost/wiki/LibrariesUnderConstruction#Boost.Ratio It is worth noting that the tests included in the zip file are relatively sparse. Vicente has an extensive suite of tests licensed under the LLVM license. He has posted a message on the Boost Developers mailing list regarding the license requirements for tests (See http://thread.gmane.org/gmane.comp.lib.boost.devel/208978) and is awaiting the outcome of that discussion before making the tests available. Writing a review ================ If you feel this is an interesting library, then please submit your review to the developer list (preferably), or to the review manager. 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. Anthony Review Manager for the proposed Boost.Ratio library -- Author of C++ Concurrency in Action http://www.stdthread.co.uk/book/ just::thread C++0x thread library http://www.stdthread.co.uk Just Software Solutions Ltd http://www.justsoftwaresolutions.co.uk 15 Carrallack Mews, St Just, Cornwall, TR19 7UL, UK. Company No. 5478976

5 6

[fusion] for_each
by Christophe Henry 06 Oct '10

06 Oct '10

I think it's at least partly my mistake. It took me some time to manage a limited example not compiling: #include <boost/fusion/container/set.hpp> #include <boost/fusion/container/vector.hpp> #include <boost/fusion/include/at_key.hpp> #include <boost/fusion/include/for_each.hpp> #include <boost/fusion/include/as_vector.hpp> struct A { int adata; }; struct B { int bdata; }; struct C { int cdata; }; typedef boost::fusion::set<A, B, C> my_set_type; typedef boost::fusion::vector<A, B> my_vector_type; struct update { update(my_set_type& to_overwrite_):to_overwrite(to_overwrite_){} template<typename T> void operator()(T& elt) const { boost::fusion::at_key<T>(to_overwrite)=elt; } my_set_type& to_overwrite; }; int main() { my_set_type my_set; my_vector_type my_vec; boost::fusion::for_each(boost::fusion::as_vector(my_vec),update(my_set)); } Now it will compile if you replace boost::fusion::as_vector(my_vec) by my_vec or T& by T const&. Ok so it seems my problem description is wrong and I needed to know that as_vector returns a const vector, right? Thanks, Christophe

1 0

Differences between Boost.Thread and std?
by David Abrahams 05 Oct '10

05 Oct '10

Hi All, Is there a document somewhere describing the differences between Boost.Thread and what's being proposed for C++0x? Thanks, -- Dave Abrahams BoostPro Computing http://www.boostpro.com

3 2

Re: [boost] [fusion] for_each
by Christophe Henry 05 Oct '10

05 Oct '10

>> I have 2 fusion containers: a small vector (my_vec) and a bigger set >> (my_set). I want to overwrite the elements of the set with elements >> from the vector whenever they have the same type. Sounds simple: >> >> struct update >> { >> update(my_set_type& to_overwrite_):to_overwrite(to_overwrite_){} >> template<typename T> >> void operator()(T& elt) /*const?*/ >> { >> boost::fusion::at_key<T>(to_overwrite)=elt; >> } >> my_set_type& to_overwrite; >> }; >> >> boost::fusion::for_each(my_vec,update(my_set)); >> >> Except that this won't compile because the operator() is required to >> be const, which is sad, because it was very simple. > > And it won't compile *with* the const? I don't think the const'ness of > the member function affects the const'ness of the referent of to_overwrite. No, it won't compile ;-)

2 1

[serialization] assert missing
by Andrew Sutton 05 Oct '10

05 Oct '10

The header 'boost/serialization/item_version_type.hpp' seems to be missing an include on boost/assert.hpp (or cassert) that was causing some compilation failures in the graph_parallel tests (under GCC-4.4.3 on GNU/Linux x86_64). The test case brings this in by including serialization/list.hpp. My first thought was to simply stick an appropriate #include in the item_version_type. Would there be any problems committing this change? Andrew

1 0

[Review] Formal Review of Proposed Boost.Ratio Library Starts TODAY
by nimaca2001＠libero.it 05 Oct '10

05 Oct '10

> > - What is your evaluation of the design? > - What is your evaluation of the implementation? Take this as the review from an average C++ user that uses uses simple boost stuff like shared_ptr or bind but is scared of things like MPL or Spirit. > - What is your evaluation of the documentation? Well written, I would have omitted some appendixes (F and G). > > - Did you try to use the library? With what compiler? Did you have any problems? Tried the provided samples and some self written one on MSVC 9 without problems despite the fact I was using an old version of boost (1.41) as base. > > - How much effort did you put into your evaluation? A glance? A quick > - reading? In-depth study? About one hour to read the docs and compile a few tests > > And finally, every review should answer this question: > > - Do you think the library should be accepted as a Boost library? Yes

2 1

[fusion] [intro] ADAPT_STRUCT extensions
by Stefan Strasser 04 Oct '10

04 Oct '10

Hi, in the discussion about the library I called "Intro" at the time it has been suggested to use BOOST_FUSION_ADAPT_STRUCT of Boost.Fusion for data member access. based on that I'd like to propose two extensions to ADAPT_STRUCT, which I think are useful beyond my use case: 1) ADAPT_STRUCT can adapt public data members only. with the modifications I uploaded here: http://svn.boost.org/svn/boost/sandbox/intro/boost/fusion/adapted/struct/ all data members can be adapted. for example: class A{ private: friend class fusion::access; int a; }; BOOST_FUSION_ADAPT_STRUCT(A,(int,a) ) 2) adaption of a class including its base class members. for example: struct A{ int a; }; struct B{ int b; }; struct C : A,B{ int c; } BOOST_FUSION_ADAPT_STRUCT(A,(int,a) ) BOOST_FUSION_ADAPT_STRUCT(B,(int,b) ) BOOST_FUSION_ADAPT_DERIVED( C, (A)(B), (int,c) ) an instance of C is now a fusion sequence of size 3. http://svn.boost.org/svn/boost/sandbox/intro/boost/fusion/adapted/struct/ad… private inheritance is supported as above, virtual inheritance is not. I'm not sure if virtual inheritance can be supported.

8 30

Boost.SQL?
by Roland Bock 04 Oct '10

04 Oct '10

Hi, currently I am working on a set of header files which are supposed to make the life of C++ developers easier when in comes to interacting with databases (based on SQL). Goals are: * Stay close to SQL syntax * Do as much type checking as possible * prevent oversights and typical security holes, e.g. by forgetting to escape strings The basic idea is, that given a table definition, it should be possible to * offer a lot of checks at compile time for building a query * make it hard to misinterpret the results Until now, I have been concentrating on table definitions and select statements. Here's a very simplistic example, assuming a table definition "my_table" and a database connection "db": // ------------------------------------------------------------------------- using boost; typedef my_table<> t; typedef sql::select_record<t> record; std::string name("Peter"); ... std::vector<record> records = db.select<record>( sql::where(t::id() > 1000 && t::first_name() == name), sql::order_by(t::priority()(sql::desc)), sql::limit(17)); // the values can be accessed by their name // and are of the correct type, e.g. records.front().first_name_; // is a string records.front().middle_name_; // optional<string> because the table definition says that it can be NULL // In case of a select from more than one table, the values can also be accessed like this records.front().my_table_.first_name; // ------------------------------------------------------------------------- I wonder if there would be interest for such a library in boost.

17 44

[config] additions for gcc 4.0.1 and IBM V11.1.0.0duetoMSM compile errors
by Christophe Henry 04 Oct '10

04 Oct '10

John Maddock wrote: > The updated test is passing as well, looks like this may be a case of adding > a BOOST_WORKAROUND for Apple's GCC and see if it fixes things. I added some #if for Apple's gcc and the IBM compiler. A look at the regression tests (http://www.boost.org/development/tests/trunk/developer/msm.html) shows: - all problems with Apple's gcc 4.0.1 are gone (waow cool! Better than expected) - IBM's compiler manages a few test cases more (for others, it just crashes or gives a run-time error status 139 which does not bring me much further) This is in my eyes a proof that for these compilers, BOOST_NO_NESTED_FRIENDSHIP and BOOST_NO_MEMBER_TEMPLATE_FRIENDS should be defined. If these features only work sometimes, then they should not be seen as supported. We now have 2 possibilities: - we change boost.config to reflect this situation and I update my code accordingly - we don't and I have to keep my #if. Solution 2 is not great for me because I'm duplicating boost.config and it litters my code with stuff less clear than BOOST_NO_NESTED_FRIENDSHIP and BOOST_NO_MEMBER_TEMPLATE_FRIENDS. In any case, it'd be good if we could decide on it this week on it so that this makes it to the 1.45. Thanks, Christophe

1 0

[btree] build advice needed
by Phil Endecott 04 Oct '10

04 Oct '10

Dear Beman & others, At the risk of appearing ignorant and being told the RTM, can someone please help me to build btree? I am attempting to do this on a smallish ARM Linux box where building the whole of Boost is impractical (but which should otherwise be very similar to an x86 Linux system). So far: # apt-get install g++ (etc) # apt-get install boost-build # apt-get install bjam # apt-get install git $ git clone git://github.com/Beman/Boost-Btree btree $ cd btree/libs/btree/build $ bjam error: Could not find parent for project at '.' error: Did not find Jamfile or project-root.jam in any parent directory. As it says, there is no project-root.jam or Jamfile in any parent; this makes me think that perhaps it is expecting this to be part of a larger Boost tree. Or, maybe I just don't know the right incantations. What's the easiest way to go about this? If I do need to get other Boost source code, if there some git magic that will do it for me? Thanks, Phil.

3 3