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

Re: [boost] accumulators::histogram
by Hansi Hansi 02 Feb '08

02 Feb '08

I have looked another time to the implementation of the histogram. If we want to implement it in the same class density, than it is needed to provide default parameter for density_cache_size or min/max. Is it possible to ensure that either density_cache_size or min/max is provided as parameter? Sorry for the question but I'm not so familiar with parameters... Best regards Hansjörg _______________________________________________________________________ Jetzt neu! Schützen Sie Ihren PC mit … [View More]

4 4

BoostCon: Attn all Lib Developers
by Jeff Garland 02 Feb '08

02 Feb '08

I'd appreciate if any boost library authors that are planning to come to BoostCon could let me know (just email me) -- I'd like to get you signed up for an Author's Corner session. People on the program committee can ignore this.... Thx, Jeff

1 0

[1.35.0] Volunteer[s] wanted: Building release snapshots
by Beman Dawes 02 Feb '08

02 Feb '08

In the past, the release manager has waited until a release is almost ready, and then started building and posting release candidates. Getting set up to generate the release candidates takes longer than expected. The release candidates themselves turn out to be missing files or have other problems that take longer than expected to resolve. I propose we start building daily release snapshots, regardless of where we are in a release cycle. I'm calling these "snapshots" rather than "… [View More]

4 4

Licensing Your Library Under the BSL (WAS Re: preview of a template geometry library)
by Dean Michael Berris 01 Feb '08

01 Feb '08

On Feb 2, 2008 2:49 AM, Frank Mori Hess <frank.hess(a)nist.gov> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On Friday 01 February 2008 07:33 am, Barend Gehrels wrote: > > > > Of course you can download and look at the sourcecode, no problem. It is > > stated like this because it is not yet open source, it is not yet > > submitted or accepted by boost and at no other open source site. > > Therefore I cannot state there that it is … [View More]

4 5

Review Request:boost.lexer
by Ben Hanson 01 Feb '08

01 Feb '08

Hi There, I have posted boost.lexer to the Boost File Vault and would like to request a review. Hartmut has integrated my library 'lexertl' into Spirit already, so this is the boost version of that library. Thanks, Ben Hanson

3 2

[Boost.build] Install_name wrong on OS X dylibs with latest CVS
by Mike Jackson 01 Feb '08

01 Feb '08

I just checked out and built boost on OS X 10.4 and there is a problem with the "install_name" or "rpath" on the dynamic libraries that are built. The "install_name" that is embedded in the libraries are basically useless as they do not contain a correct path to the libraries. Example for the filesystem is: 532:[mjackson@Thor:boost]$ otool -L /Users/Shared/Sandbox/boost- install/lib/libboost_filesystem-1_35.dylib /Users/Shared/Sandbox/boost-install/lib/libboost_filesystem-1_35.dylib: … [View More]

3 4

Gauging interest for MT async signals utility
by Roland Schwarz 01 Feb '08

01 Feb '08

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Behaviour of standard signal.h / csignal is known to be different on windows and posix platforms. While on posix typically there is no provision for the thread context the signal handler will run, on windows the operating system delivers signals into a separate dedicated thread. This makes it possible e.g. to use locking primitives without risk for deadlock. I wrote a little utility that mimics that behavior on posix platforms by blocking all … [View More]

1 0

[1.35.0] Host for release snapshots?
by Beman Dawes 01 Feb '08

01 Feb '08

If we are going to generate release snapshots nightly, we need a site to host them. Is Sourceforge a possibility? I seem to recall the Sourceforge release mechanism isn't particularly friendly to nightly snapshots. Ideas? --Beman

2 2

[1.35.0] Building the release?
by Beman Dawes 01 Feb '08

01 Feb '08

I'm starting to test build release candidate files for 1.35.0. The 1.34.0 and 1.34.1 release candidates were build by hand, IIUC. There is a Python script to do that job (boost-root/tools/release/make_tarballs.py), but it is out of date. I'm starting to work on updating it. What does such a script have to do? * Export SVN branches/release with the correct line endings for POSIX and Windows. * Build the quickbook/boostbook docs. * Set various file permissions. * Build the actual .zip, .gz,… [View More]

6 12

[review] Review of Flyweight library begins today January 7
by Ion Gaztañaga 01 Feb '08

01 Feb '08

The formal review of Flyweight library, proposed by Joaquín M. López Muñoz, begins today (sorry for the late announcement): *Description:* Flyweights are small-sized handle classes granting constant access to shared common data, thus allowing for the management of large amounts of entities within reasonable memory limits. Boost.Flyweight makes it easy to use this common programming idiom by providing the class template flyweight<T>, which acts as a drop-in replacement for const T. … [View More]*Online docs:* http://tinyurl.com/2sstyr http://svn.boost.org/svn/boost/sandbox/flyweight/libs/flyweight/index.html *Download:* http://tinyurl.com/hrdm6 http://www.boost-consulting.com/vault/index.php?&direction=0&order=&directo… *Notes:* 1) We've seen some suggestions in the mailing list for Flyweight. Joaquín has nicely explained a couple of issues that we'd like to address/discuss in the review: http://tinyurl.com/33ghtf http://svn.boost.org/svn/boost/sandbox/flyweight/libs/flyweight/doc/review_… 2) Flyweight needs Boost 1.35 elements because the library depends on libraries like Interprocess for some features/tests. Since SVN snapshot tarballs seem to be missing these days, those who want to try flyweight can download a working SVN-HEAD snapshot here: http://igaztanaga.drivehq.com/boost_trunk.tar.bz2 3) Serialization tests won't work. This feature is expected to work when some new features (discussed in the mailing list between Joaquín and Robert Ramey) are added in Boost.Serialization. Those are expected for Boost 1.36. What to include in Review Comments ================================== Your comments may be brief or lengthy, but basically the Review Manager needs your evaluation of the library. If you identify problems along the way, please note if they are minor, serious, or showstoppers. Here are some questions you might want to answer in your review: * What is your evaluation of the design? * What is your evaluation of the implementation? * What is your evaluation of the documentation? * What is your evaluation of the potential usefulness of the library? * Did you try to use the library? With what compiler? Did you have any problems? * How much effort did you put into your evaluation? A glance? A quick reading? In-depth study? * Are you knowledgeable about the problem domain? And finally, every review should answer this question: * Do you think the library should be accepted as a Boost library? Be sure to say this explicitly so that your other comments don't obscure your overall opinion. Ion Gaztañaga - Review Manager - [View Less]

9 18