March 2011 - Boost - lists.boost.org

[random] Missing file 'integer_log2.hpp' in trunk
by sguazt 13 Mar '11

13 Mar '11

Hello, Header 'random/detail/seed_impl.hpp' needs the file 'random/detail/integer_log2.hpp', but this file does not exist. Could you commit it? Thanks, -- Marco

2 1

[docs][boostbook] FOP 1.0 is broken
by Ronald Garcia 13 Mar '11

13 Mar '11

Howdy, Just an FYI. Apache FOP 1.0 has a bug that causes it to crash with an exception when building boost PDF documentation. This bug has been fixed in the FOP repository, so nightly builds of fop do not exhibit it.

3 2

Javascript in Boost.Serialization docs
by Bryce Lelbach 13 Mar '11

13 Mar '11

As per http://www.boost.org/development/requirements.html#Documentation, ECMAScript/JavaScript is not acceptable in Boost documentation (explained in http://www.boost.org/development/requirements.html#JavaScript= ). Boost.Serialization's sidebar uses JavaScript to expand/close tabs. Is this policy no longer valid? If so, can someone update the aforementioned refere= nces? Otherwise, can the JS from the Boost.Serialization docs be removed? -- Bryce Lelbach aka wash boost-spirit.com px.cct.lsu.edu

1 0

[PATCH] [config] Disable threads on Carbon, since MPTasks aren't supported
by Joshua Juran 13 Mar '11

13 Mar '11

Disable threads on Carbon, since MPTasks aren't supported Boost.Thread hasn't supported MPTasks since 1.33.1. Prevent the definition of BOOST_HAS_THREADS in the non-pthreads case so spinlocks compile (which are needed for smart pointers).

2 4

[1.46.1] Boost 1.46.1 Release available
by Beman Dawes 12 Mar '11

12 Mar '11

Release 1.46.1 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 is a bug fix release that is otherwise the same as 1.46.0. For details, including download links, see http://www.boost.org/users/news/version_1_46_1 The release can also be downloaded directly from SourceForge. See http://sourceforge.net/projects/boost/files/ 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

3 5

Re: [boost] [XInt] CoW/Move Timings
by pavel 12 Mar '11

12 Mar '11

on 12.03.2011 at 15:04 Dave Abrahams wrote : > Well, since you asked, your email address is rather weirdly > constructed; it's almost as though you desire to assault the > sensibilities of some of your fellow Boosters. We tend to use our > real names here and in any case try to promote a civil and > professional respect in our interactions. If you care about how your > communications here is perceived and understood, I suggest finding a > handle that doesn't make such an aggressive statement. i got that account long before i joined boost list being a student of the first(?) grade but since you ask i got a new account i hope it's more "friendly" than the previous one -- Pavel P.S. if you notice a grammar mistake or weird phrasing in my message please point it out

2 1

Re: [boost] [xint] Boost.XInt formal review
by Ivan Sorokin 12 Mar '11

12 Mar '11

On 06.03.2011 05:23, Chad Nelson wrote: >> I believe that arbitrary precision arithmetic library is very useful. >> But I don't think that in it's current status XInt is appropriate for >> boost. > After your reply I changes my mind. As I see you had considered all my suggestions long before I posted them. If they really lead to unavoidable performance penalty I think current implementation is a good trade-off. I vote for inclusion XInt into boost. >> One more thought about "secure" option. There are no standard >> containers with this option. I think either both standard containers >> and integer_t should have such option or both shouldn't have. This is >> yet another argument for container parametrization. > > I'm not sure I understand your argument. Are you saying that because > there are no standard containers with a zero-memory-before-releasing > option, that the library shouldn't provide one either? > Yes. Why integer_t should be an exception?

10 19

[1.46.1] Release candidates available
by Beman Dawes 12 Mar '11

12 Mar '11

Release candidate files for 1.46.1 are available at http://boost.cowic.de/rc/ As always, the release managers would appreciate it if you download the candidate of your choice and give building it a try. Please report both success and failure, and anything else that is noteworthy. This helps ensure the candidates build OK before we push them out to SourceForge. Thanks, --The release managers

10 19

[xint] Review ending in 2 days
by Vladimir Prus 12 Mar '11

12 Mar '11

Boosters, I just wanted to remind that review of the Boost.XInt library, by Chad Nelson, is about to end at March 11. So, if you plan to submit a review, please do it now. The documentation for the current version is available at: http://www.oakcircle.com/xint_docs/ The source code is available via Subversion at: http://svn.boost.org/svn/boost/sandbox/xint or can be downloaded at: http://www.boostpro.com/vault/index.php?action=downloadfile&filename=xint.z… Here are the important points: 1. All comments are appreciated. Even if you don't have the time for in-depth study of everything, comments on parts of the library are welcome. In particular, if you are already using logging in your applications and have specialized requirements, you might want to directly check how the proposed library handles them. 2. The reviews and all comments should be submitted to the developers list, boost(a)lists.boost.org and the email should have "[xint]" prefix in the subject to make sure it's not missed. The deadline for reviews is 23:59, March 11, PST, or 2:59, March 12, EST, or 7:59 March 12, UK time, 10:59, March 12 MSK 4. The general review checklist is provided below: - 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? Thanks, Volodya -- Vladimir Prus Mentor Graphics +7 (812) 677-68-40

3 2

[Filesystem.v3] Request to rename imbue to something else like global_locale
by Artyom 11 Mar '11

11 Mar '11

Hello, The static member function boost::filesystem::path::imbue(std::locale const &) Is very misleading. In the C++ standard library imbue usually refers to specific object like specific stream and not referred to global object. And because it is possible to write: boost::filesystem::path p; p.imbue(some_locale); p="some_file.txt"; Which looks like you change p's locale and not global locale. I'd recommend, provide static member function boost::filesystem::path::global_locale With same semantics as imbue and deprecate imbue. Artyom

3 4