- Boost - lists.boost.org

Review Request : Boost.Range Extension
by Akira Takahashi 11 Jun '12

11 Jun '12

Hi, Neil Groves and Boosters. OvenToBoost is a project that intend to add some features of Oven Range Library into Boost.Range. I'd like to request a review. Features: - Additional Range Adaptors (taken, taken_while, dropped, dropped_while, elements, elements_key, memoized, outdirected) - Extensions for using Lambda (regular function, regular operator) - Infinite Range (iteration function) - and additional range utilities. Future Plan: I have written primary features. If these features are accept, I'd like to implement/add following features: - Range of Range Adaptors (concatenated, transposed) - Cyclic Range - Range Utilities for String Source Code: https://github.com/faithandbrave/OvenToBoost Document: http://dl.dropbox.com/u/1682460/git/OvenToBoost/libs/range/doc/html/index.h… Regards, Akira >>======================== Akira Takahashi mailto:faithandbrave@gmail.com site: https://sites.google.com/site/faithandbrave/about/en

4 24

From an user to developers
by Oodini 10 Jun '12

10 Jun '12

Hello, I am an user, and I am currently reviewing all the Boost libraries. But for a common user, some needs are not satisfied in the libraries descriptions. The Boost organization should compel the libraries authors to put in their documentation : 1. the history of all releases, with notes for each release 2. the motivation of their library 3. when they offer services similar to the ones provided by the STL, why did they feel the need to complete it, and what are the differences 3. for the relevant libraries, their status regarding the new features of C++11 (are they obsolete ? do they remain some differences ? ex : Array, Chrono, DateTime), especially the ones related to TR1 An homogeneous structure for the documentation would be welcome.

5 6

[1.50] OK to merge documentation changes?
by John Maddock 10 Jun '12

10 Jun '12

I have some documentation changes that I'd like to merge: * Corrected typos in Boost.Math docs. * Updated some scripts and Jamfiles for correct PDF doc build generation. Is there a good time to commit these to release, or is it all to late for 1.50 now? Thanks, John.

2 1

[git/modularization] Suggested names for branches?
by Beman Dawes 10 Jun '12

10 Jun '12

At the C++Now! session discussing moving to git and modularization, I showed the usual git flow overview graphic from http://nvie.com/posts/a-successful-git-branching-model/ showing the workflow for a library. Someone (Dave?) mentioned that the git flow choices for branch names were not what we would like for Boost. I agree, but don't recall the exact suggestions for more appropriate names. The three branches in question, with the git-flow names in parens, were the main development branch (develop), release prep branches (?), and the branch with actual releases (master). Is there a better usual convention for these names? I have a vague memory of someone mentioning "master" for the main development branch, "release" for the branch with the actual releases, and maybe "beta-x.xx.x" for release prep branches. To try to avoid an extended bicycle shed discussion, perhaps people could mention names they have actually seen used and know worked well. --Beman

8 14

Re: [boost] [review] Multiprecision review scheduled for June 8th - 17th, 2012
by Marc Glisse 09 Jun '12

09 Jun '12

(sorry for the broken thread, I wasn't subscribed yet) A few quick comments: * gmpxx != mpfr_class * the version of gmpxx in the repository hasn't used any temporary for the example given in the introduction for a while, it is only because of a slow release cycle that you haven't seen it yet (will be in 5.1). * the example about using 0 vs 11 temporaries doesn't mention what happens to the boost package if we disable expression template. Does it use a single temporary (using rvalue-references) or plenty? * having an implicit narrowing conversion from double to bigint is a bad idea, it should be explicit (it isn't completely obvious from the doc if that is the case). * you could get good results with a backend that uses gmp's mpn_* functions but not the mpz_t type. * what about infinite precision floats? By that I mean something like bigint*2^n, where operations + - * are computed exactly. It can be quite a bit faster than rationals, when it is sufficient. * if I want reference-counting, I guess that should be done in a back-end. -- Marc Glisse

5 22

C++Now! keynote videos are available
by Marshall Clow 08 Jun '12

08 Jun '12

Howard's was not recorded Daveed: http://www.youtube.com/watch?v=8SOCYQ033K8 Sean: http://www.youtube.com/watch?v=iGenpw2NeKQ The full list of videos is at: http://www.youtube.com/user/BoostCon (more will be added soon) -- Marshall Marshall Clow Idio Software <mailto:mclow.lists@gmail.com> A.D. 1517: Martin Luther nails his 95 Theses to the church door and is promptly moderated down to (-1, Flamebait). -- Yu Suzuki

1 0

basic information: code post
by Majid Qureshi 08 Jun '12

08 Jun '12

Hi I am new to boost mailing list. I am wondering if I wish to submit my template class for review to be added as part of boost library, what do I need to do? and please advise if I am not suppose to send email to this mailing list for any such proposal. Also what mailing list do I need to send such emails? Very much appreciated.Thanks

2 1

[Who's using boost?] Sankel Software
by David Sankel 08 Jun '12

08 Jun '12

Sankel Software Sankel Software has been using boost for over 10 years to develop high performance and customized CAD/CAM applications, industrial control, computer artistry, and business software. If it wasn't for Boost, we would have stopped using C++ long ago. Its libraries allow us to write more concise code and, more importantly, give us the tools to implement higher level constructs such as denotational semantics based, top-down program design. Home Page: http://sankelsoftware.com Here is a list of the libraries we currently use: - Boost.Any - Boost.Serialization - Boost.Array - Boost.Assign - Boost.Bind - Boost.Integer - Boost.DateTime - Boost.Foreach - Boost.Function - Boost.Fusion - Boost.Variant - Boost.Optional - Boost.LexicalCast - Boost.SmartPtr - Boost.Math - Boost.MPL - Boost.MultiIndex - Boost.Operators - Boost.Signals2 - Boost.Thread - Boost.Tuple - Boost.TypeTraits - Boost.Utility - David -- David Sankel Sankel Software www.sankelsoftware.com 585 617 4748 (Office)

1 0

[1.50.0] Release branch open for bug fixes and doc updates
by Beman Dawes 07 Jun '12

07 Jun '12

The final release is scheduled for Monday, June 25th. The release candidate is scheduled to to be built Thursday, June 21st. That gives us two weeks to apply post-beta bug fixes and doc updates. Let's try a slightly more streamlined procedure for this post-beta period; until Monday, June 18th permission is not required to merge bug fixes and documentation updates. Starting June 18th permission of a release manager is required for all merges. As always, New libraries and new features are not allowed during a post-beta period. Thanks, --Beman

2 1

[1.50] Can't build quickbook PDF docs.
by John Maddock 07 Jun '12

07 Jun '12

Just a note that the quickbook docs don't build as a PDF due to XML validation failures at the FO stage: fop.render.pdf ..\..\bin.v2\tools\quickbook\doc\msvc-10.0\debug\link-static\threading-multi\quickbook.pdf M:/download/programs/xep/xep.bat ..\..\bin.v2\tools\quickbook\doc\msvc-10.0\debug\link-static\threading-multi\quickbook.fo ..\..\bin.v2\tools\quickbook\doc\msvc-10.0\debug\link-static\threading-multi\quickbook.pdf (document [system-id file:/M:/data/boost/branches/release/doc/pdf/../../bin.v2/tools/quickbook/doc/msvc-10.0/debug/link-static/threading-multi/quickbook.fo] (validate [error] Element 'fo:block' cannot be a child of 'fo:root'. [error] Element 'fo:block' cannot be a child of 'fo:root'. [error] Element 'fo:block' cannot be a child of 'fo:root'. [error] Attribute 'space-before.optimum' cannot occur at element 'fo:block'. [error] Attribute 'space-before.minimum' cannot occur at element 'fo:block'. [error] Attribute 'space-before.maximum' cannot occur at element 'fo:block'. [error] Attribute 'id' cannot occur at element 'fo:inline'. [error] Attribute 'break-before' cannot occur at element 'fo:block'. [error] Attribute 'id' cannot occur at element 'fo:block'. [error] Attribute 'margin-left' cannot occur at element 'fo:block'. [error] Attribute 'font-family' cannot occur at element 'fo:block'. [error] Attribute 'keep-together.within-column' cannot occur at element 'fo:block'. [error] Attribute 'keep-with-next.within-column' cannot occur at element 'fo:block'. [error] Attribute 'font-family' cannot occur at element 'fo:block'. [error] Attribute 'font-weight' cannot occur at element 'fo:block'. [error] Attribute 'keep-with-next.within-column' cannot occur at element 'fo:block'. [error] Attribute 'space-before.minimum' cannot occur at element 'fo:block'. [error] Attribute 'space-before.optimum' cannot occur at element 'fo:block'. [error] Attribute 'space-before.maximum' cannot occur at element 'fo:block'. [error] Attribute 'text-align' cannot occur at element 'fo:block'. [error] Attribute 'start-indent' cannot occur at element 'fo:block'. [error] Attribute 'marker-class-name' cannot occur at element 'fo:marker'. [error] Element 'fo:marker' should be a descendant of 'flow'. [error] Attribute 'font-size' cannot occur at element 'fo:block'. [error] Attribute 'id' cannot occur at element 'fo:inline'. [error] Attribute 'internal-destination' cannot occur at element 'fo:basic-link'. [error] Attribute 'color' cannot occur at element 'fo:inline'. [error] Attribute 'space-before.optimum' cannot occur at element 'fo:block'. [error] Attribute 'space-before.minimum' cannot occur at element 'fo:block'. [error] Attribute 'space-before.maximum' cannot occur at element 'fo:block'. [error] Attribute 'id' cannot occur at element 'fo:block'. [error] Attribute 'border-color' cannot occur at element 'fo:block'. [error] Attribute 'border-width' cannot occur at element 'fo:block'. [error] Attribute 'border-style' cannot occur at element 'fo:block'. [error] Attribute 'padding-left' cannot occur at element 'fo:block'. [error] Attribute 'padding-right' cannot occur at element 'fo:block'. [error] Attribute 'padding-top' cannot occur at element 'fo:block'. [error] Attribute 'padding-bottom' cannot occur at element 'fo:block'. [error] Attribute 'widows' cannot occur at element 'fo:block'. [error] Attribute 'orphans' cannot occur at element 'fo:block'. [error] Attribute 'font-size' cannot occur at element 'fo:block'. [error] Attribute 'hyphenate' cannot occur at element 'fo:block'. etc. Any ideas? Thanks, John.

2 1