July 2010 - Boost - lists.preview.boost.org

Questions regarding new visibility stuff
by Robert Ramey 12 Jul '10

12 Jul '10

I found the page with the updated config documentation on the trunk. a) What happens if the library is being compiled as a static library? The documentation says that BOOST_SYMBOL_EXPORT is always defined. So can I assume that if a static library is being built then it's defined a empty? The serialization library now contains things like #ifdef BOOST_HAS_DECLSPEC // defined in config system Which I believe is undefined for when the library is being built statically. So things currently work. What do I replace the #ifdef above with - if anything. I believe that exporting symbols from an imported static library would create all sorts of interesting surprises. b) the serialization library contains ... #if defined(__BORLANDC__) #define BOOST_ARCHIVE_DECL(T) T __export #define BOOST_ARCHIVE_OR_WARCHIVE_DECL(T) T __export #else #define BOOST_ARCHIVE_DECL(T) __declspec(dllexport) T #define BOOST_ARCHIVE_OR_WARCHIVE_DECL(T) __declspec(dllexport) T #endif This addresses the fact that with borland, the placement of the __export and typename differs in sequence from the rest. I haven't tested borland in a long time and it's broken for the serialization library anyway (and no one has complained) so I suppose you can just ignore this - but I'd thought I'd mention it. c) When will these new macros get checked into the release branch? d) It turns out that I've had to deal with this a lot more than anyone would want to. In my case, I've divided the code into two separate libraries - serialization.dll and wserialization.dll. The second includes only those parts which depend on wide character types. The motiviation is that one only needs the part he is really using. Problems come up as wserialization import symbols from serialization so the import/export issue get's sort of complicated. User programs have the same issue as I've found in making dll/plugin tests. I don't have a real point here, just noting my experiences with this issue. Robert Ramey

2 4

boost_1.43.0 gcc-4.4.1 failure
by Neal Becker 12 Jul '10

12 Jul '10

Is this failure known/expected? "g++" -ftemplate-depth-128 -O3 -finline-functions -Wno-inline -Wall - fPIC -DBOOST_ALL_DYN_LINK=1 -DBOOST_ALL_NO_LIB=1 -DNDEBUG -I"." -c -o "bin.v2/libs/wave/build/gcc-4.4.1/release/instantiate_cpp_exprgrammar.o" "libs/wave/src/instantiate_cpp_exprgrammar.cpp" ...failed gcc.compile.c++ bin.v2/libs/wave/build/gcc-4.4.1/release/instantiate_cpp_exprgrammar.o... rpm -q gcc gcc-4.4.1-2.fc11.i586

1 0

[gsoc] boost.heap snapshot
by Tim Blechmann 12 Jul '10

12 Jul '10

hi all, i have uploaded a snapshot of boost.heap [1] and the initial documentation to [2]. feedback / suggestions are more than welcome! especially i would like to hear some thoughts about the interface, and if someone requests a specific heap implementation, it is also a good time to ask for it now ... cheers, tim [1] http://tim.klingt.org/code/attachments/download/28/boost_heap_110710.tar.gz [2] http://tim.klingt.org/boost_heap -- tim(a)klingt.org http://tim.klingt.org ... to make life worth living ... Keith Rowe on making music

2 2

Differences between 'trunk' and 'release' right before 1.44 code freeze
by Marshall Clow 12 Jul '10

12 Jul '10

As far as I know, the code freeze for the 1.44 release is scheduled for tomorrow, July 12th. There are about 40 files that exist on the release branch only (do not, or no longer) exist on the trunk. Are these files that were deleted on the trunk and the deletions were never 'merged' to the release branch? There are almost 100 files that exist on the trunk that do not exist at all on the release branch. I'm confident that some of these are "works in progress", not ready for the 1.44 release. I'm also confident that others are work that should be in the 1.44 release - but I certainly can't tell the difference. There are also about 2000 files that differ (some in minor ways, some significantly) between the trunk and the release branch. If you fixed a bug during the bug sprint, you need to merge your changes to the release branch! Here's a list of the files that exist only "on one side". The attached HTML file shows all the differences. Files that exist only in 'release/' boost/asio/detail/gcc_fenced_block.hpp boost/smart_ptr/enable_shared_from_this2.hpp doc/test/accumulators.tag doc/test/dvips.version doc/test/gs.version doc/test/html/images/accumulators doc/test/latex.version libs/math/doc/html/standalone_HTML.manifest libs/range/doc/html/range/reference/adaptors/adaptors_reference.html libs/range/doc/reference/adaptors/adjacent_filtered.html libs/range/doc/reference/adaptors/copied.html libs/range/doc/reference/adaptors/filtered.html libs/range/doc/reference/adaptors/indexed.html libs/range/doc/reference/adaptors/indirected.html libs/range/doc/reference/adaptors/map_keys.html libs/range/doc/reference/adaptors/map_values.html libs/range/doc/reference/adaptors/replaced.html libs/range/doc/reference/adaptors/replaced_if.html libs/range/doc/reference/adaptors/reversed.html libs/range/doc/reference/adaptors/sliced.html libs/range/doc/reference/adaptors/strided.html libs/range/doc/reference/adaptors/tokenized.html libs/range/doc/reference/adaptors/transformed.html libs/range/doc/reference/adaptors/uniqued.html libs/spirit/example/scheme/detail libs/spirit/example/scheme/out.txt libs/spirit/example/scheme/sexpr.hpp libs/spirit/example/scheme/sexpr_test.cpp libs/spirit/example/scheme/sexpr_test.txt libs/spirit/example/scheme/simple_print.hpp libs/spirit/example/scheme/test/generate_qiexpr libs/spirit/example/scheme/test/parse_qiexpr libs/spirit/example/scheme/test/sexpr libs/spirit/example/scheme/utree_test.cpp libs/test/example/cla/Jamfile libs/test/example/est_example1.cpp libs/test/example/est_example2.cpp libs/test/example/unit_test_example_011.cpp libs/test/example/unit_test_example_012.cpp libs/test/test/CMakeLists.txt Files that exist only in 'trunk/' boost/asio/detail/gcc_hppa_fenced_block.hpp boost/asio/detail/gcc_sync_fenced_block.hpp boost/detail/extended_integer.hpp boost/iterator/function_input_iterator.hpp boost/random/detail/generator_seed_seq.hpp boost/random/detail/operators.hpp boost/random/discrete_distribution.hpp boost/random/extreme_value_distribution.hpp boost/random/seed_seq.hpp boost/random/shuffle_order.hpp boost/random/weibull_distribution.hpp boost/signals2/detail/foreign_ptr.hpp boost/smart_ptr/enable_shared_from_raw.hpp boost/test/included/execution_monitor.hpp boost/test/prod_tools.hpp boost/test/utils/setcolor.hpp boost/typeof/unsupported.hpp libs/exception/doc/source libs/filesystem/test/resize_file_test.txt libs/filesystem/test/xx libs/graph/quickbook libs/interprocess/proj/vc7ide/intermodule_singleton_test.vcproj libs/interprocess/test/intermodule_singleton_test.cpp libs/io/doc/quoted_manip.html libs/io/test/quoted_manip_test.cpp libs/iterator/doc/function_input_iterator.html libs/iterator/doc/function_input_iterator.rst libs/iterator/test/function_input_iterator_test.cpp libs/multi_array/example/resize_from_other.cpp libs/multi_array/test/reverse_view.cpp libs/parameter/doc/README.txt libs/parameter/test/literate libs/ptr_container/test/const_element_containers.cpp libs/python/example/quickstart/bin libs/random/example/password.cpp libs/random/test/chi_squared_test.hpp libs/random/test/test_binomial.cpp libs/random/test/test_binomial_distribution.cpp libs/random/test/test_discrete.cpp libs/random/test/test_discrete_distribution.cpp libs/random/test/test_extreme_value.cpp libs/random/test/test_extreme_value_distribution.cpp libs/random/test/test_gamma.cpp libs/random/test/test_gamma_distribution.cpp libs/random/test/test_poisson.cpp libs/random/test/test_poisson_distribution.cpp libs/random/test/test_seed_seq.cpp libs/random/test/test_weibull.cpp libs/random/test/test_weibull_distribution.cpp libs/range/doc/html/range/reference/algorithms/range_algorithm_introduction.html libs/range/doc/html/range/reference/overview.html libs/range/test/algorithm_test/copy_n.cpp libs/range/test/algorithm_test/remove_copy.cpp libs/range/test/algorithm_test/remove_copy_if.cpp libs/range/test/algorithm_test/replace_copy.cpp libs/range/test/algorithm_test/replace_copy_if.cpp libs/range/test/algorithm_test/reverse_copy.cpp libs/range/test/algorithm_test/rotate_copy.cpp libs/range/test/algorithm_test/search_n.cpp libs/range/test/algorithm_test/swap_ranges.cpp libs/range/test/algorithm_test/unique_copy.cpp libs/range/test/replace_copy.cpp libs/smart_ptr/test/enable_shared_from_raw_test.cpp libs/spirit/doc/Missing.txt libs/spirit/doc/html/spirit/lex/reference/concepts libs/spirit/example/scheme/test/qi/calc.scm libs/test/doc/Jamfile.v2 libs/test/doc/html/utf/user-guide/test-output/FPT.html libs/test/doc/src/Jamfile.v2 libs/test/doc/src/btl-toc.xml libs/test/doc/src/btl.xml libs/test/doc/src/execution-monitor.xml libs/test/doc/src/faq.xml libs/test/doc/src/minimal-testing.xml libs/test/doc/src/program-execution-monitor.xml libs/test/doc/src/snippet libs/test/doc/src/tutorial.hello-the-testing-world.xml libs/test/doc/src/tutorial.intro-in-testing.xml libs/test/doc/src/tutorial.new-year-resolution.xml libs/test/doc/src/utf.testing-tools.xml libs/test/doc/src/utf.tutorials.xml libs/test/doc/src/utf.usage-recommendations.xml libs/test/doc/src/utf.user-guide.runtime-config.xml libs/test/doc/src/utf.users-guide.fixture.xml libs/test/doc/src/utf.users-guide.test-organization.xml libs/test/doc/src/utf.users-guide.test-output.xml libs/test/doc/src/utf.users-guide.xml libs/test/doc/src/utf.xml libs/test/doc/src/xsl libs/test/doc/utf-boostbook.jam libs/test/example/test_example1.cpp libs/test/example/test_example2.cpp libs/test/example/unit_test_example_13.cpp libs/units/example/autoprefixes.cpp tools/build/v2/test/exit_status.py tools/build/v2/tools/doxygen tools/build/v2/tools/xsltproc tools/release/merge2release.bat -- Marshall

2 1

boost.parameter defaults
by Tim Blechmann 11 Jul '10

11 Jul '10

hi all, i am currently having a hard time to figure out, how to use boost.parameter with default template arguments. i have a signature: typedef parameter::parameters<optional<tag::a>, optional<tag::b> > foo_signature; template <class X, class A = boost::parameter::void_, class B = boost::parameter::void_> class foo {}; now, how do i set a default parameter for one of the template arguments? it is either not documented, or i am missing the point, where it is explained ... thanks, tim -- tim(a)klingt.org http://tim.klingt.org Which is more musical, a truck passing by a factory or a truck passing by a music school? John Cage

3 3

[fiber] with assembler
by Oliver Kowalke 11 Jul '10

11 Jul '10

I've uploaded a new version of boost.fiber to boost vault. It provides assembler for x86 (32/64bit) - PowerPC and ARM are planed. Performance of the raw context-switch is 6-12 times faster than swapcontext(POSIX). Mutexes, condition- and event-variables suspend fibers waiting on those sync. primitives and can be shared by fiber running on different threads (schedulers).

2 2

library proposal : odeint
by Karsten Ahnert 11 Jul '10

11 Jul '10

Hi, I proposed a library for solving ordinary differential equations some months ago. Since this time, we have worked a lot on this topic and we would like to start a discussion about the needs and the design of the library. The library odeint ("odeint" comes from integration of ordinary differential equations ) can be found in the sandbox and some preliminary documentation is also available: http://svn.boost.org/svn/boost/sandbox/odeint/ http://svn.boost.org/svn/boost/sandbox/odeint/libs/numeric/odeint/doc/html/… One of our main aims is the independence on a specific container or array type, such that the library can work with ODEs defined on arbitrary topologies, like networks, lattices , grids, etc. So, any comments on this library are highly welcome, as well as contributions (of any kind). Best regards, Karsten

8 13

Maintenance suspended
by David Abrahams 10 Jul '10

10 Jul '10

All --- I tried, I really did, to resolve the trunk and release branches of my libraries for the upcoming release. But the truth is that I'm finding Boost's current interdependent structure and the sluggishness of SVN on a project of our size just makes everything too hard to do. I'm now just declaring openly what has effectively been true for the past couple of months: I'm not maintaining my libraries until I complete the transition to Git that goes along with using Ryppln (http://ryppl.org) I'm sorry, I know it's not good or right, but I know it's going to be for the best in the long run. That should all happen fairly quickly now, anyway. -- David Abrahams BoostPro Computing http://boostpro.com

8 13

[Query] Cross Compiling for mipsel-linux
by Alapkumar Sinha 10 Jul '10

10 Jul '10

Hi, Pardon me if it is not the right forum to ask the below question. I am trying to build the boost library for mipsel-linux. I followed the following procedure. 1. Changed user-config.jam a. using gcc : mipsel : mipsel-linux-g++ ; 2. Then called bjam as: ./bjam --toolset=gcc-mipsel When I do this I am getting the following error. /******/ gcc.compile.c++ bin.v2/libs/math/build/gcc-mipsel/release/threading-multi/cyl_bessel_i.o /tmp/ccgLCiZn.s: Assembler messages: /tmp/ccgLCiZn.s:14975: Error: opcode not supported on this processor: mips1 (mips1) `ll $3,4($4)' /tmp/ccgLCiZn.s:14977: Error: opcode not supported on this processor: mips1 (mips1) `sc $5,4($4)' /tmp/ccgLCiZn.s:15063: Error: opcode not supported on this processor: mips1 (mips1) `ll $3,8($4)' /tmp/ccgLCiZn.s:15065: Error: opcode not supported on this processor: mips1 (mips1) `sc $10,8($4)' /tmp/ccgLCiZn.s:15105: Error: opcode not supported on this processor: mips1 (mips1) `ll $3,4($4)' And so on /******/ Can someone help me on where I am going wrong? Regards, Alap ________________________________ This Email may contain confidential or privileged information for the intended recipient (s) If you are not the intended recipient, please do not use or disseminate the information, notify the sender and delete it from your system. ______________________________________________________________________

2 1

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

10 Jul '10

David Abrahams wrote: > All --- > >> I tried, I really did, to resolve the trunk and release branches of my libraries for the upcoming release. >But the truth is that I'm finding Boost's current interdependent structure and the sluggishness of SVN on >a project of our size just makes everything too hard to do. I'm now just declaring openly what has >effectively been true for the past couple of months: I'm not maintaining my libraries until I complete the >transition to Git that goes along with using Ryppln (http://ryppl.org) I'm sorry, I know it's not good or >right, but I know it's going to be for the best in the long run. That should all happen fairly quickly now, anyway. > > -- > David Abrahams > BoostPro Computing > http://boostpro.com > Dave, having a single library to maintain I probably cannot fully appreciate your situation. However, I would like to attract your attention to the very special position you have in this community, especially among newcomers I count myself with. Seeing dave (I mean THE dave! ;-) ) not maintaining his libraries creates a precedent and sends a wrong signal, which deals a blow to boost's credibility. Companies could wonder, waow, if the community cannot even help dave maintain his libraries, in which state must be others? Also considering that ryppl is so far not a reality yet and not even agreed on, we need a solution for the time being. Why not simply request help from the community to which you brought so much? I'm sure that many would be happy to help you on this. So, concretely, what is the problem? Do you have no time handling the feature requests or is svn the problem? If it is just about merging and doing some mechanical svn-related tasks, this is a very workable solution and I gladly offer my help. If it is about feature requests, this is a more complicated one (but seemingly unrelated to svn) and you could also ask for support on this list. Surely, someone competent will step forward and free you from much work. You could simply review patches before commit. It would also help the community by having more than one person familiar with your libraries. Christophe PS: Thinking about it more, it would be a good idea if every boost author would mentor one or several "young" members who could take over when the author's situation changes. In any company, we usually try to avoid having only one person knowing a subject. Maybe a boostcon would be a good place where authors would explain the inside of their library?

5 7

[serialization] tests broken on release branch?
by Richard Webb 09 Jul '10

09 Jul '10

I'm getting error: Unable to find file or target named error: 'test_diamond_complex.cpp' error: referred from project at error: '../libs/serialization/test' on the release branch regression tests.

2 1

[Format] Broken on release branch?
by Richard Webb 09 Jul '10

09 Jul '10

The release branch test results are showing new failures in a number of libs, several of which look to be because of a breakage in Format -> looks like it might have been partially merged from Trunk, and has some bits missing?

2 1

[trac] spam
by Steven Watanabe 09 Jul '10

09 Jul '10

AMDG #4350 was spammed an hour ago. https://svn.boost.org/trac/boost/ticket/4350 In Christ, Steven Watanabe

1 0

Mentoring (Was: Maintenance suspended)
by Christophe Henry 09 Jul '10

09 Jul '10

>>On Jul 8, 2010, at 8:39 PM, Joel de Guzman wrote: >> >> On 7/8/10 8:28 PM, Christophe Henry wrote: >> >>> PS: >>> Thinking about it more, it would be a good idea if every boost author >>> would mentor one or several "young" members who could take over when >>> the author's situation changes. In any company, we usually try to >>> avoid having only one person knowing a subject. >>> Maybe a boostcon would be a good place where authors would explain the >>> inside of their library? >> >> This is exactly what happened to Fusion and now happening to Phoenix >> with the past and present GSOC projects. > >Hey, that's a great idea. To actually institute such a program requires someone to come up with "young" >members who are ready and willing to be mentored. Christophe, would you like to take that project on? It's the key point, to find interested and competent potential "young" (or not ;-) ) members. It seems to me pretty clear that the most motivated candidates are to be found at the boostcon. I will happily take that project on if my idea is viable, and it would be: Authors (and I offer myself as testperson) prepare a talk or a paper where they show the inside of their library, as detailed as possible. - Participants get to learn some of the advanced techniques used in boost libraries - Boost gains an extended circle of possible contributors - Authors prepare a succession if needed later, or the possibility of having more people able to implement changes / fixes. They also get an in-depth review by very clever guys (honestly, I am every year impressed). Preparing others is especially important for people like me who are developing a library alone. Looks to me like a win/win scenario :) This can be coupled with GSOC projects. After learning the inside of a library, these participants could extend it. Alternatively, we can organize this with participants of this list, but it would require a greater deal of work for authors who would have to write down a lot. Some thoughts about it? Potential candidates (as speaker or attendee)? Christophe

6 9

Re: [boost] Parsing boost 1.43 with gcc-xml (bug #4324 - fixed in trunk)
by Benoît Leveau 09 Jul '10

09 Jul '10

Steven Watanabe wrote: > Benoît Leveau wrote: > > I have problems parsing boost 1.43 with gcc-xml, due to the lack of > > several preprocessor flags in /boost/config/compiler/gcc_xml.hpp. > > > > I saw this problem has been fixed in the trunk 4 weeks ago: > > /trunk/boost/config/compiler/gcc_xml.hpp > > Revision 62666: Disable all C++0x features in GCC-XML for now. Fixes #4324. > > > > I am not familiar with the details of the release process, so I'm > > wondering if a patched 1.43 version will be released? > > This bug is quite serious as it prevents boost from being parsed by > > gccxml (which, I guess, is listed as a supported compiler), > > and 1.44 hasn't been released yet, which leaves no option other than > > patching my local copy with the fix from the trunk. > > I would prefer to use an official release as it's not for a personal > > project, but will do the patch if I have to. > > > > 1.44 is scheduled for August 2nd. If you need this fix now, you'll > have to patch your copy. Ok, that's what I thought.. Thanks for the answer! Benoit

1 0

[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