- Boost - lists.boost.org

extension / reflection project status?
by Janek Kozicki 04 Feb '08

04 Feb '08

Hello, What is the status of Boost extension / reflection library? (is this a single library or two separate?) Currently I'm mainly concerned about the "extension" part. Was it submitted for review? Or do you want to submit them both together to go in a single review, and for that you plan to first finish the "reflection" part? Because as I understand (am I right?) the extension library is quite finished and should be ready to use, eg. in my app? Can you provide some "official" URL for documentation and download? best regards, and big thanks for your hard work! -- Janek Kozicki |

1 0

[rfc] I/O Chain Library, Preview Release 2
by Sebastian Redl 04 Feb '08

04 Feb '08

Hi, I'm proud to announce preview release 2 of my I/O Chain library. Preview 1 was announced here: http://lists.boost.org/Archives/boost/2007/11/131079.php IOChains is a component-based I/O library similar to Boost.Iostreams, but built from scratch instead of being based on the C++ iostreams interface. It currently supports binary I/O of primitives only, but will be extended to cover text, too. It is built to be type-safe and fast. The main changes since Preview 1 are: Most importantly: The archive actually contains the code. :-) 1) Tested under Visual C++.Net 2003, i.e. VC++ 7.1. 2) Endian conversion is now supported. 3) Supports reading and writing fixed-point numbers. 4) Supports reading and writing stdin, stdout and stderr. (Not Win32, yet.) This also demonstrates the utility of the command interface. 5) A bit-level access pseudo-component was added. 6) A rationale section was added to the documentation. 7) A few example programs were added. (Not tested in Win32, but except for the password reader, they should work.) The code can be found at: http://stud3.tuwien.ac.at/~e0226430/iochain-preview-2.tar.bz2 <http://stud3.tuwien.ac.at/%7Ee0226430/iochain-preview-1.tar.bz2> The installation is still not trivial. Boost doesn't appear very suited to develop new libraries outside the tree, it seems. 1) Unpack the archive. 2) Make boost-build.jam point to your trunk Boost.Build, or delete the file if you already have a boost-build.jam in place. 3) Edit Jamroot: set the constant REALBOOST at the very top to point to your trunk Boost. 4) If you want to use the zlib component, add an entry to your user-config.jam for zlib. On Linux, this should be as trivial as lib zlib : : <name>z ; On Win32, it might look like this: lib zlib : : <file>"c:/path/to/zlib/zlib1.lib" : : <include>"c:/path/to/zlib" ; The documentation doesn't build due to some problems I have with Boost.Build. A pre-built version can be found here: http://stud3.tuwien.ac.at/~e0226430/iochain/ If you want to build the docs yourself, remove the <tag> requirement from Jamroot. A note about Visual C++: newer compilers than 7.1 should work, unless they exhibit this bug: http://groups.google.com/group/comp.lang.c++.moderated/browse_thread/thread… If they do, you need to grep the source for BOOST_WORKAROUND and adjust the version number. Oh, and let me know. Older versions will most definitely not work. Minor new features: 1) The content of an erasure can change. 2) Bug fixes. 3) Minor refactorings. 4) Best practice: all public implementation classes now have protected destructors. Have fun, and please tell me what you think. Sebastian Redl

1 0

[review] Review of Flyweight library started January 21 and still running!
by Ion Gaztañaga 03 Feb '08

03 Feb '08

Hi all, The formal review of Flyweight library started January 21 and will end January 30, we have a few nice reviews, but I'm sure that those who haven't reviewed it are also interested in the library ;-). The library solves quite a common programming pattern, is small and very well documented. So don't be afraid to try it! Information for reviewers: *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. *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 -

6 20

preview of a template geometry library
by Tom Brinkman 03 Feb '08

03 Feb '08

My geometry needs are fairly simple. At this point, I just need them to create simple graphic primitaves, such as coloring in polygons, determining interesection points, simplyfing lines, etc. All these things appear to be addressed in this library, so I'm looking forward to following this library progress. I've created my own versions of many of these algorithms, but more as a learning excercise and they are not very good. In any event, I would be available if you want to chat offline for some reason.

1 0

BoostCon Call for Sessions
by Jeff Garland 03 Feb '08

03 Feb '08

The second annual Boost conference will take place in Aspen, Colorado, May 5-9. BoostCon is the main face-to-face event for all things Boost, from generic-programming techniques to Boost community, from using Boost libraries to writing Boost libraries, from deployment considerations to promoting the use of Boost more widely, from TR1 to TR2. Given the range and interests of last year's participants, the event again promises to be intense and in depth. We invite you to propose a session. See the BoostCon home page at www.boostcon.com for more information. Session formats Presentations focus on a practitioner’s ideas and experience with anything relevant to Boost and Boost users. 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 are formally prepared sessions at which instructors teach conference participants specific Boost-relevant skills. 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 focus on tips on usage and design. In addition, we're looking to uncover the hidden design gems hidden in boost libraries -- see below for more. Other formats may also be of interest. Don't hold back a proposal just because it doesn't fit into a pigeonhole. 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 libraries * Case studies on using Boost * Experts panels * Advanced sessions on implementation techniques used within Boost libraries * TR1 (and TR2) * Development workshops to extend or enhance existing Boost libraries * Workshops on design process * Infrastructure workshops o Build tools o Website o Testing * C++0x and how it will change life for users and library writers * Concepts and Generic Programming * 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 online 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. Author's Corner Presentations Based on user feedback from last year, we'd like to encourage Boost library authors to do short sessions (typically 30 minutes) providing an overview of their libraries, tips on usage and design. In particular, we're looking to uncover the hidden design gems that underlie so many boost libraries. Standard outline for a presentation is as follows -- feel free to deviate as needed. * Library Purpose / Motivations * Library Genesis & History o why you developed it o when it was accepted o how it has evolved * Library Concepts * Library Usage Overviews and Tips * Library Design Decisions / Design Gems * Question / Answer 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 of the session * Type of session: presentation/panel/tutorial/workshop/other * A paragraph or two describing the session, suitable for the conference web site * Proposed length: 45/90 minutes, half/full day * Alternate length, if any: 45/90 minutes, half/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) Please submit via email to conference at boost-consulting.com, with a subject that begins "BoostCon proposal" Timeline Proposals due As soon as possible. Proposals will be accepted on a first-come-first-served basis. Proposals acceptances sent As soon as accepted. Session materials due April 15, 2008. The session material go on the BoostCon CD handed out to attendees. Other arrangements Like Boost itself, BoostCon is strictly non-profit. Conference organizers are not paid for their time. Any surplus money will be rolled over into the succeeding year BoostCon budget. BoostCon provides free admission for all 90 minute and longer session presenters. This year we also hope to have enough revenue to pay presenters of longer sessions a small honorarium.

1 1

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 McAfee und WEB.DE. 30 Tage kostenlos testen. http://www.pc-sicherheit.web.de/startseite/?mc=022220

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 "candidates", since they are really only release candidates late in the release cycle. Building snapshots on a daily basis would have these benefits: * The mechanical procedure would become smooth, and so could eliminate one of the delays that plague the current release process. * The snapshots could be inspected, tested, and otherwise checked for quality control on an ongoing basis. Since release tarball problems could be detected and fixed earlier in the release cycle, this could reduced or eliminated a source of delays. * The release workload could better distributed, since generation of snapshots could be handled by someone other than the release manager. Comments? Would anyone like to volunteer to take this on? They would need a high speed internet connection as the files involved are quite large. --Beman

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 open source at this moment. > > However, for review purposes it is allowed to look in it. > > If this is not sufficient I can change the statement. > > It sounds like you think you need to get the library accepted into boost > before you can license it under the BSL. You don't need permission from > anyone but the copyright owner to release your source code under the BSL. > The boost license doesn't place any obligations on you to make any special > arrangements for distribution of the source code. > I am not a lawyer, but I don't think your code needs to be accepted into Boost to be released under the Boost Software License. I have a few libraries already under the BSL but not (yet) in Boost, released in the wild. I also seem to recall that the default license for all 'unlicensed' work is "All Rights Reserved." Again though, IANAL. -- Dean Michael C. Berris Software Engineer, Friendster, Inc. [http://cplusplus-soup.blogspot.com/] [mikhailberis(a)gmail.com] [+63 928 7291459] [+1 408 4049523]

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