- Boost - lists.boost.org

[thread] no documented thread move support functions on reference documentation
by vicente.botet 08 Nov '08

08 Nov '08

Hi, the following move support functions are not docummented on the reference documentation. #ifdef BOOST_HAS_RVALUE_REFS template <class F> thread(F&& f); thread(thread&& other); thread& operator=(thread&& other); thread&& move(); #else #ifdef BOOST_NO_SFINAE #else template <class F> explicit thread(F f,typename disable_if<boost::is_convertible<F&,detail::thread_move_t<F> >, dummy* >::type=0) #endif template <class F> explicit thread(detail::thread_move_t<F> f); thread(detail::thread_move_t<thread> x); thread& operator=(detail::thread_move_t<thread> x); operator detail::thread_move_t<thread>(); detail::thread_move_t<thread> move(); #endif Even if the semantics of these functions could be induced for completud it will be good to add them to the reference documentation. The ticket is Ticket #2486 Thanks, Vicente

1 0

[flyweight] post-review version available
by JOAQUIN M. LOPEZ MUÑOZ 08 Nov '08

08 Nov '08

Hello, I'm happy to announce the availability of the post-review version of Boost.Flyweight: *Online docs:* http://tinyurl.com/2sstyr http://svn.boost.org/svn/boost/sandbox/flyweight/libs/flyweight/index.html *Download as .zip:* http://tinyurl.com/hrdm6 http://www.boost-consulting.com/vault/index.php?&direction=0&order=&directo… *Check out from SVN:* https://svn.boost.org/svn/boost/sandbox/flyweight *Tested with:* MSVC++ 8.0 and GCC 3.4.4. Compilation reports most welcome. Older compilers like MSVC++ 6.5 are no longer supported. *What's new:* I've tried to address most of the suggestions and comments raised during the review. The two most important changes are: 1. Alberto Barbati's insightful review has led to the introduction of so-called key-value flyweights (http://tinyurl.com/5mnwjp ). This type of flyweights is meant for the situations where constructing the underlying type is expensive and must be avoided except if absolutely necessary. I think the design is robust enough and covers the variants (inner/outer key) that arose during the discussion with Alberto. 2. A comprehensive performance section is provided (http://tinyurl.com/5ap5kt ). *What's pending* 1. Some of the suggestions given at the review, like reducing intermodule_holder to static_holder when permissible (Vicente Botet) or studying read/write locking policies are still pending or have been postponed to later releases of the library. I felt the current state is sufficiently robust for publication. 2. Serialization support is currently broken, pending the resolution of a proposed feature to add to Boost.Serialization (run-time archive helpers). I'd be very grateful if you can take a look at the post- review version of Boost.Flyweight (specially if you were a reviewer), test it and comment on it, with emphasis on the new features like key-value flyweights. If people are happy with this revision my target release for inclusion will be Boost 1.38. Thank you, Joaquín M López Muñoz Telefónica, Investigación y Desarrollo

7 12

[serialization] Query archive consumed?
by David Abrahams 07 Nov '08

07 Nov '08

Hi, I'd like to verify that there's no data left in a particular archive once I've deserialized my stuff out of it. Is there an appropriate check I can use? Thanks, -- Dave Abrahams BoostPro Computing http://www.boostpro.com

2 1

[threadpool] v15 - final version (?)
by Oliver Kowalke 07 Nov '08

07 Nov '08

Hello, version 15 of threadpool is out - I hope it is the final version. The code doesn't use fibers - fork/join is implemented via recursive execution of tasks (in task::get()). Only tasks in the local worker-queue will be recursivly executed. The work-thread will block in task::get() if the local worker-queue is empty (happens if at least one other worker-thread has stolen a task from the local queue). regards, Oliver -- GMX Download-Spiele: Preizsturz! Alle Puzzle-Spiele Deluxe über 60% billiger. http://games.entertainment.gmx.net/de/entertainment/games/download/puzzle/i…

1 0

Why doesn't boost::exception derive from std::exception?
by Michael Marcin 07 Nov '08

07 Nov '08

Why doesn't boost::exception derive from std::exception? -- Michael Marcin

2 1

[1.37.0] boost test crashes under cygwin gcc-4.x
by Mat Marcus 06 Nov '08

06 Nov '08

When I run a simple test application with a single (empty) BOOST_AUTO_TEST_CASE, boost test causes a crash under cygwin using gcc-4.x. It also crashes for non-empty auto test cases. For example, the boost test regressions crash: ### user-config.jam contains: using gcc : 4.3.2 : /bin/g++-4.exe ; ## cygwin gcc 4.x compiler $ cd /asl/staff/mmarcus/sandbox/boost_libraries/libs/test $ ../../tools/jam/src/bin.cygwinx86/bjam.exe gcc-4.3.2 link=static -q gives: $ ../../tools/jam/src/bin.cygwinx86/bjam.exe gcc-4.3.2 link=static -q ...patience... ...found 1528 targets... ...updating 341 targets... gcc.link ../../bin.v2/libs/test/example/unit_test_example_11.test/gcc-4.3.2/debug/link-static/unit_test_example_11 testing.capture-output ../../bin.v2/libs/test/example/unit_test_example_11.test/gcc-4.3.2/debug/link-static/unit_test_example_11.run ====== BEGIN OUTPUT ====== EXIT STATUS: 53 ====== END OUTPUT ====== (failed-as-expected) ../../bin.v2/libs/test/example/unit_test_example_11.test/gcc-4.3.2/debug/link-static/unit_test_example_11.run **passed** ../../bin.v2/libs/test/example/unit_test_example_11.test/gcc-4.3.2/debug/link-static/unit_test_example_11.test gcc.link ../../bin.v2/libs/test/example/unit_test_example_12.test/gcc-4.3.2/debug/link-static/unit_test_example_12 **passed** ../../bin.v2/libs/test/example/unit_test_example_12.test/gcc-4.3.2/debug/link-static/unit_test_example_12.test gcc.link ../../bin.v2/libs/test/example/est_example1.test/gcc-4.3.2/debug/link-static/est_example1 testing.capture-output ../../bin.v2/libs/test/example/est_example1.test/gcc-4.3.2/debug/link-static/est_example1.run ====== BEGIN OUTPUT ====== EXIT STATUS: 53 ====== END OUTPUT ====== PATH=//bin://lib://lib32://lib64:$PATH export PATH "../../bin.v2/libs/test/example/est_example1.test/gcc-4.3.2/debug/link-static/est_example1" > "../../bin.v2/libs/test/example/est_example1.test/gcc-4.3.2/debug/link-static/est_example1.output" 2>&1 status=$? echo >> "../../bin.v2/libs/test/example/est_example1.test/gcc-4.3.2/debug/link-static/est_example1.output" echo EXIT STATUS: $status >> "../../bin.v2/libs/test/example/est_example1.test/gcc-4.3.2/debug/link-static/est_example1.output" if test $status -eq 0 ; then cp "../../bin.v2/libs/test/example/est_example1.test/gcc-4.3.2/debug/link-static/est_example1.output" "../../bin.v2/libs/test/example/est_example1.test/gcc-4.3.2/debug/link-static/est_example1.run" fi verbose=0 if test $status -ne 0 ; then verbose=1 fi if test $verbose -eq 1 ; then echo ====== BEGIN OUTPUT ====== cat "../../bin.v2/libs/test/example/est_example1.test/gcc-4.3.2/debug/link-static/est_example1.output" echo ====== END OUTPUT ====== fi exit $status ...failed testing.capture-output ../../bin.v2/libs/test/example/est_example1.test/gcc-4.3.2/debug/link-static/est_example1.run... ...failed updating 1 target... ...updated 7 targets... ### Similar problems occur with when I use a manually-compiled gcc-4.3.0. In that case, my output for an empty auto test case looks like: ====== BEGIN OUTPUT ====== Running 1 test case... *** No errors detected 2 [main] any_regular_test 66836 _cygtls::handle_exceptions: Exception: STATUS_ACCESS_VIOLATION 413574 [main] any_regular_test 66836 open_stackdumpfile: Dumping stack trace to any_regular_test.exe.stackdump EXIT STATUS: 35584 ====== END OUTPUT ====== Stepping through in gcc shows that things run fine through the end of main, but then a problem occurs at static destruction time. My gdb skills are not sufficient to give much more info. These problems are new to 1.37.0--I've been using the unit tests successfully up through 1.36.0 (with the alt stack patch). The stack dump file for the manually-compiled gcc-4.3.0 follows. Can someone offer a suggestion? Thanks, Mat ### Exception: STATUS_ACCESS_VIOLATION at eip=610C38B4 eax=00000001 ebx=00000001 ecx=61108B2C edx=00BE0000 esi=61102F64 edi=FFFFFFF9 ebp=0022CAC8 esp=0022CA40 program=c:\asl\staff\mmarcus\sandbox\built_artifacts\test\unit_tests\any_regular\any_regular_test.test\gcc-4.3.0\debug\architecture-x86\asl-dev\instruction-set-i486\link-static\target-os-cygwin\threadapi-pthread\threading-multi\any_regular_test.exe, pid 66836, thread main cs=001B ds=0023 es=0023 fs=003B gs=0000 ss=0023 Stack trace: Frame Function Args 0022CAC8 610C38B4 (004742A0, 00BE2BE0, 00000001, 004311E0) 0022CB58 00428850 (004742A0, 61102EDC, 0022CB78, 610046C2) 0022CB78 0040682F (004737DC, 61004690, 00000000, 0022CBE0) 0022CBA8 610F7DD3 (00000000, 00000000, 0022CBD8, 00000000) 0022CBC8 610E1558 (00000000, 00000000, 0022CD98, 610060E0) 0022CBD8 61004DD1 (00000000, 00BE2580, 00BE0090, 0022CB60) 0022CD98 610060E0 (00000000, 0022CDD0, 61005450, 0022CDD0) 61005450 61004416 (0000009C, A02404C7, E8611021, FFFFFF48) 2046399 [main] any_regular_test 66836 _cygtls::handle_exceptions: Exception: STATUS_ACCESS_VIOLATION 2114906 [main] any_regular_test 66836 _cygtls::handle_exceptions: Error while dumping state (probably corrupted stack)

5 7

[serialization] load-only or save-only types?
by David Abrahams 06 Nov '08

06 Nov '08

Hi, I want to send out instances of one type and receive the same data format but build instances of a different type. Obviously I can just define serialize() for each of them, but can I define only save for the outgoing type and load for the incoming one, causing serialization in the other direction to be a compile-time error? Not a big deal, but it would be more expressive that way. TIA, -- Dave Abrahams BoostPro Computing http://www.boostpro.com

3 5

make_shared and allocate_shared for classes with private constructors
by Michael Marcin 06 Nov '08

06 Nov '08

I have some classes that derive from enable_shared_from_this which I've given private constructors and static creation methods which return a shared_ptr. This prevents someone from using the class inappropriately. It seems obvious that at a minimum using make_shared internally here would be an improvement. Unfortunately this requires that make_shared be made a friend for every arity and probably won't work with the variadic template implementation of make_shared. Is it possible to make declaring friendship for make_shared and allocate_shared simpler? I thinking something like serialization does with friend class boost::serialization::access. Thanks, -- Michael Marcin

2 3

location for PDF docs?
by Eric Niebler 06 Nov '08

06 Nov '08

I can't remember if we ever settled on a location for PDF documentation. Did we? And should we make it official by linking to it from boost.org? FWIW, I've uploaded a PDF version of Proto's docs to: http://www.boostpro.com/vault/index.php?directory=PDF%20Documentation Aside: Proto's reference section for 1.37 is /much/ improved. -- Eric Niebler BoostPro Computing http://www.boostpro.com

6 28

[FileSystem] portable Temp, Desktop & Applications directories?
by Jeff Flinn 06 Nov '08

06 Nov '08

Is there any existing facility to get in particular the path to the user's temp directory in FileSystem? I couldn't find one in boost_1_35_0, but I've might have missed it. Any plans for this functionality? On Win and Mac there's getenv TEMP/TmpDir, or is there a better way. Thanks, Jeff

3 3