July 2010 - Boost - lists.boost.org

[xint] Design Question
by Chad Nelson 09 Jul '10

09 Jul '10

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I'm adding an "unsigned" option to the XInt library, so that fixed-length integers act exactly like their built-in counterparts. That in itself is not a problem, since unsigned fixed-length integers have a well-known and standard behavior. The problem is: what should the library do if the user asks for an unsigned *non*-fixed-length integer? The options I've come up with so far, in order of my personal preference: A: Make the unsigned option part of the fixed-length option, so it *can't* be specified separately. (The most elegant solution, but perhaps not the most useful.) B: Refuse to compile (or if I can't find a way to do that, instantiate) it, on the grounds that the combination can't logically be supported. C: Throw an exception if any calculation results in a negative number. (Not very useful, but logical because under the built-in types' unsigned rules, a negative number in an unlimited-length library would be infinitely long.) D: Force any negative numbers to a different value, such as zero or maybe their positive counterparts. (I can't think of any use for this, I just put it here for completeness.) Can anyone think of a potential reason for options C or D? Or a reason to prefer option B? Or maybe come up with a different idea entirely? - -- Chad Nelson Oak Circle Software, Inc. * * * -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkwY2EYACgkQp9x9jeZ9/wSZuACgqIjJ85p0wUrwhCR/tcvY8QUL bagAniFZU/UGwKfpK7juhuWYxXwMb2Ar =qvcJ -----END PGP SIGNATURE-----

7 24

[quickbook] Question about macros and templates
by Andrey Semashev 09 Jul '10

09 Jul '10

Hi, I'm writing docs in quickbook and stumbled upon a problem. I have this document structure: main.qbk [include a.qbk] [include b.qbk] [include c.qbk] [include x.qbk] [include y.qbk] [include z.qbk] [xinclude r.xml] In files a, b and c I define macros that would unfold into headerref, classref, etc. for the items described in the auto-generated r.xml Reference. I want to use these macros in x, y and z, both in text and code samples. The problem is that, it seems, quickbook doesn't unfold these macros in x, y and z. My guess is that the scope of the macros is limited to the files they are defined in. Is that true? I tried to do the same with templates. It seems that templates are visible in x, y and z, but still are not unfolded in code samples. Is there a way around this problem? Thanks.

2 2

Python port development
by Vladimir Prus 09 Jul '10

09 Jul '10

Hi, as many here probably know, the strategic direction for Boost.Build is the use of Python as implementation language, which should bring a lot of benefits. For more detailed rationale, see: https://trac.lvk.cs.msu.su/boost.build/wiki/PythonPort The port has got so far as to build "hello, world" with gcc, but then stalled. Fortunately, my employer, CodeSourcery, has a sabbatical program, and completing a Python port of Boost.Build was approved as the goal of my own sabbatical. I'll have 4 almost-full-time weeks, starting next Monday, Jule 12. Of course, I'll be asking for feedback, so don't be surprised when I start to post design questions. Thanks, -- Vladimir Prus http://vladimir_prus.blogspot.com Boost.Build: http://boost.org/boost-build2

3 2

Vault: `BGL` directory
by Daniel Trebbien 08 Jul '10

08 Jul '10

Would someone please delete the `BGL` directory on the Vault? I created it before I found the more-suitable `Algorithms/graph` directory.

1 0

[python] boost-1.44 apply patch br#3843
by Neal Becker 08 Jul '10

08 Jul '10

I'd like to see this patch applied for 1.44. Seems pretty harmless. The purpose is so that BOOST_PYTHON_MODULE macro will expand it's arguments, so that this code will work: #define MY_NAME BOOST_PP_CAT(ldpc_,SIMCASE) BOOST_PYTHON_MODULE(MY_NAME) {... https://svn.boost.org/trac/boost/attachment/ticket/3843/boost_python_module…

2 1

Re: [boost] Maintenance NOT suspended
by Christophe Henry 08 Jul '10

08 Jul '10

>I hereby apologize to the community for my earlier announcement and request that you accept a retraction Thanks for taking this courageous decision! >> So, concretely, what is the problem? Do you have no time handling the >> feature requests or is svn the problem? > >I'll prepare a proper response to these questions in a separate message, but I wanted to head off any damage immediately. As I made the suggestion, count me in. After you explain what you need, hopefully more will volunteer. Regards, Christophe

1 0

[thread][VS2010] shared_mutex woo's
by Hartmut Kaiser 08 Jul '10

08 Jul '10

This: #include <boost/thread.hpp> int main() { boost::shared_mutex mtx; boost::upgrade_lock<boost::shared_mutex> l(mtx); boost::upgrade_to_unique_lock<boost::shared_mutex> ul(l); return 0; } still fails on VC21010. Defining BOOST_NO_RVALUE_REFERENCES makes this compile, though. Regards Hartmut --------------- Meet me at BoostCon www.boostcon.com

3 3

[Fusion] Permission to update release branch and roll in dependencies
by Tobias Schwinger 08 Jul '10

08 Jul '10

Dear release team, we're about to freeze the next release. I'd like to kindly ask for your permission to address the issues discussed in this thread http://thread.gmane.org/gmane.comp.lib.boost.devel/198532/ before it's too late, again. Reportedly the outdated files do - other than hoped in that thread - NOT work anymore - and neither do the new and documented ones for the lack of dependencies. So, what I'd like to do is: o merge trunk changes into the Functional module of Fusion o add Forward o optionally add Factory Please check the new mini libraries for "release compliance" and give me a go on the fix. Would be too bad to go with a partially defunct Fusion in two releases for bureaucratic reasons. Please also note that rolling back to a proper previous version might involve more changes and will complicate future merges for us. Regards, Tobias

6 8

Name conflict: boost/range/adaptor/replaced.hpp and boost/algorithm/string/replace.hpp
by Jeremy Maitin-Shepard 08 Jul '10

08 Jul '10

I found that these two header files (the second one being required indirectly by including boost/exception/all.hpp) cannot be used together, because they both attempt to bring a definition of replace_range into the boost namespace. This is with boost-1.43.

1 0

boost.atomic library works on Linux but not on Windows -- please help
by Anqing Xu 07 Jul '10

07 Jul '10

Hi, In search of a std:atomic<T> implementation, I decided to give boost.atomic library a try. My initial investigation found it worked fine under linux. However it does not work on Windows. Here is a little test program to demonstrate: #include <iostream> #include <boost/atomic.hpp> #include <boost/lockfree/detail/tagged_ptr.hpp> #include <boost/lockfree/detail/freelist.hpp> int main() { boost::lockfree::caching_freelist<int> pool(3); int* pInt1 = pool.allocate(); *pInt1 = 1; int* pInt2 = pool.allocate(); *pInt2 = 2; int* pInt3 = pool.allocate(); *pInt3 = 3; pool.deallocate(pInt1); pool.deallocate(pInt2); pool.deallocate(pInt3); int* pInt4 = pool.allocate(); int* pInt5 = pool.allocate(); int* pInt6 = pool.allocate(); } The test uses boost.lockfree library, which you can download from http://tim.klingt.org/git?p=boost_lockfree.git If you set a break point, say in fallback.hpp, you will see that on Windows it falls back to spinlock. Can somebody please suggest how to fix this? I suspect the issue has something to do with intptr_t type. I looked into the code but quickly started to have headache. Atomic library uses template metaprogramming and is not easy to understand. -Anqing

1 0