- Boost - lists.boost.org

[Graph] compile error while inheriting boost graph
by Sandeep Gupta 01 Jun '08

01 Jun '08

Hi, My attempt to inherit boost graph failed. The compiler complains that it is not aware of boost graph classes. Would appreciate if someone can tell if this due to boost intricacies or just regular mistake in the syntax. //Declare boost graph within namespace boostd namespace boostd { typedef adjacency_list<listS, listS, ... > Graph; typedef graph_traits<Graph>::vertex_descriptor Vertex; } class DerivedGraph: public boostd::Graph{ public: class Node: public boostd::Vertex{ //error on this line }; }; The compiler complains error: expected class-name before '{' token Thanks sandeep

2 1

Non pre-emptible Boost.Thread
by Edd Dawson 31 May '08

31 May '08

Hello, A while ago, I implemented the Boost.Thread API in terms of Windows Fibers and <uncontext.h> functionality. The result is the ability to run code written with boost threads in a single OS thread. I find it useful for writing tests where determinism is important i.e. to test algorithmic correctness in isolation from synchronization- related concerns. I haven't updated it to mirror the new 1.35 API yet, but I was wondering if any other boost users would be interested in this or if it might be thought suitable for inclusion in the boost library collection. More information is available here: http://www.mr-edd.co.uk/?page_id=91 Direct link to source code: http://www.mr-edd.co.uk/files/coco/coco-0.2.0.zip Kind regards, Edd

5 13

[thread] warnings when linking with the dynamic thread library on cygwin
by vicente.botet 31 May '08

31 May '08

Hello, I have a warning when linking with the thread library. /usr/lib/gcc/i686-pc-cygwin/3.4.4/../../../../i686-pc-cygwin/bin/ld: warning: auto-importing has been activated without --enable-auto-import specified on the command line. When I set <library>/boost/thread//boost_thread/<link>static; instead of <library>/boost/thread//boost_thread; this works without warnings. What I need to do to link dynamically without warnings? Best regards Vicente ================== Command $ bjam The jamfile contains using testing ; if ! $(BOOST_ROOT) { BOOST_ROOT = [ modules.peek : BOOST_ROOT ] ; } project : : requirements <include>$(BOOST_ROOT) <include>../../.. <threading>multi <target-os>cygwin <threadapi>pthread <variant>debug <library>/boost/test//boost_unit_test_framework/<link>static <threading>multi <library>/boost/thread//boost_thread; Link warning: gcc.compile.c++ ..\..\..\bin.v2\libs\sync\test\include_concurrent_component.test\gcc-3.4.4\debug\target-os-cygwin\threadapi-pthread\threading-multi\include_concurrent_component.o **passed** ..\..\..\bin.v2\libs\sync\test\include_concurrent_component.test\gcc-3.4.4\debug\target-os-cygwin\threadapi-pthread\threading-multi\include_concurrent_component.test gcc.compile.c++ ..\..\..\bin.v2\libs\sync\test\static_thread_group_test.test\gcc-3.4.4\debug\target-os-cygwin\threadapi-pthread\threading-multi\static_thread_group_test.o gcc.link ..\..\..\bin.v2\libs\sync\test\static_thread_group_test.test\gcc-3.4.4\debug\target-os-cygwin\threadapi-pthread\threading-multi\static_thread_group_test.exe /usr/lib/gcc/i686-pc-cygwin/3.4.4/../../../../i686-pc-cygwin/bin/ld: warning: auto-importing has been activated without --enable-auto-import specified on the command line. This should work unless it involves constant data structures referencing symbols from auto-imported DLLs.Info: resolving vtable for boost::detail::thread_data_baseby linking to __imp___ZTVN5boost6detail16thread_data_baseE (auto-import) testing.capture-output ..\..\..\bin.v2\libs\sync\test\static_thread_group_test.test\gcc-3.4.4\debug\target-os-cygwin\threadapi-pthread\threading-multi\static_thread_group_test.run 1 fichier(s) copi?(s). **passed** ..\..\..\bin.v2\libs\sync\test\static_thread_group_test.test\gcc-3.4.4\debug\target-os-cygwin\threadapi-pthread\threading-multi\static_thread_group_test.test ...updated 6 targets... --------------------------- Vicente Juan Botet Escriba

1 0

[thread] is there an interestoin a static thread group?
by vicente.botet 31 May '08

31 May '08

Hi, The Boost.Thread library provides a thread_group class for a collection of threads that are related in some fashion. This collection is dynamic, i.e. we can add and remove threads to this collection. When this collection is known at the group creation and can not change a static thread group could be useful. This template class thread_tuple_n will have the same operations than a thread_group, join_all, interrupt_all and size and could be used as follows: void free_function() { // .... } class X { public: void mf() { // .... } }; class Y { public: void operator()() { // .... } }; X x; Y y; thread_tuple_3 tt(free_function, make_pair(&X::mf, x), y); // ... tt.interrupt_all(); // ... tt.join_all(); Best _____________________ Vicente Juan Botet Escriba

1 1

[announce] Multi signature boost::function v1.0
by Marco Costalba 31 May '08

31 May '08

Hi all, this is the first official version of multi-signature boost::function extension (MSF) pushed to Boost Vault under the name msf-1.0.zip A multi-signature boost:function 'f' allows something like this int foo1(char) { return -1; } char foo2(string) { return 'x'; } f = foo1; f = foo2; assert( f('x') == -1 ); assert( f("hello") == 'x' ); New in this version: - Feature complete: all boost::function API has been naturally extended - Documented and added a tutorial according to boost standards, see tutorial.html - Added a dynamic dispatcher and an object factory examples that use MSF as a building block - Rewritten part of the code to be even simpler and easy to understand - Fixed case of functors with const and/or volatile operator() - Compiler friendly: tested with gcc3.4, gcc4.2, MSVC - No known issues This library extension, although flexible and IMHO powerful is notably very simple and small, so I would like to ask if someone is interested to add this code in some way directly to boost.function Thanks Marco

7 48

[filesystem] "leaf"
by David Abrahams 31 May '08

31 May '08

I was just reviewing the filesystem docs and came across "leaf()". I'm sure this isn't the first time I've seen it, but this time I picked up a little semantic dissonance. Normally we think of "leaf" in the context of a tree as being a thing with no children. An interior node like a directory that has files or other directories in it is usually not called a "leaf." I wonder if this is the best possible name? Is there a precedent we can draw on in some other language/library? In python, it's os.path.basename(p). Perl, php, and the posix basename command seem to do something similar. -- Dave Abrahams BoostPro Computing http://www.boostpro.com

16 58

[spirit] trunk: circular dependency parse <-> construct <-> assign_to (?)
by troy d. straszheim 31 May '08

31 May '08

Hey Hartmut, Joel, I started playing with spirit-2/lex (on the trunk), specifically examples/lex/example4.cpp, thought I'd try to parse some python. I've hit an error that was already asked about a month or so ago. It appears to be because this guy: http://svn.boost.org/trac/boost/browser/trunk/boost/spirit/home/qi/detail/a… doesn't have 'construct' overloads for various types (conversion to unsigned is the one that comes up in the example). I dug around and found construct.hpp, http://svn.boost.org/trac/boost/browser/trunk/boost/spirit/home/qi/detail/c… which does have them, but they forward to parse(), using proto placeholders from over in support/placeholders.hpp. This ends up coming round again to assign_to. At this point I can't decide whether this is going to be detangleable or not. I thought I'd ask for some hints on what things are supposed to look like in the end, if so. In any event, the code is absolutely fascinating. Time well spent. Thanks, -t

3 20

[thread] link errors on cygwin/release
by Emil Dotchevski 30 May '08

30 May '08

(cygwin/debug links fine) ../../../../bin/lib/re_0_02_0/impl/test/test-wfmo.test/gcc-3.3.3/release/link-static/threading-multi/test-wfmo.o:test-wfmo.cpp:(.text$_ZN5boost6detail16thread_data_baseC2Ev[boost::detail::thread_data_base::thread_data_base[not-in-charge]()]+0xd1): undefined reference to `boost::condition_variable::condition_variable[in-charge]()' ../../../../bin/lib/re_0_02_0/impl/test/test-wfmo.test/gcc-3.3.3/release/link-static/threading-multi/test-wfmo.o:test-wfmo.cpp:(.text$_ZN5boost6detail16thread_data_baseC2Ev[boost::detail::thread_data_base::thread_data_base[not-in-charge]()]+0x147): undefined reference to `boost::condition_variable::condition_variable[in-charge]()' ../../../../bin/lib/re_0_02_0/impl/test/test-wfmo.test/gcc-3.3.3/release/link-static/threading-multi/test-wfmo.o:test-wfmo.cpp:(.text$_ZN5boost6detail16thread_data_baseC2Ev[boost::detail::thread_data_base::thread_data_base[not-in-charge]()]+0x231): undefined reference to `boost::condition_variable::~condition_variable [in-charge]()' Incidentally, I have a question: are boost::condition_variable and boost::mutex destruction-safe on all of the supported platforms? I'm debugging some sort of race in a test which creates/destroys condvar/mutex objects and 2 threads many times in a loop. Thanks, Emil Dotchevski Reverge Studios, Inc. http://www.revergestudios.com/reblog/index.php?n=ReCode

2 2

BoostCon library in a week (sequence)
by Tom Brinkman 30 May '08

30 May '08

I use these extensions to "for_each" alot. You can add them to your list if you want. template<typename _InIt, typename _InIt2, typename _Fn1> inline _Fn1 for_each(_InIt _First, _InIt _Last, _InIt2 _First2, _Fn1 _Func) { for (; _First != _Last; ++_First,++_First2) _Func(*_First,*_First2); return (_Func); } template<typename _InIt, typename _InIt2, typename _InIt3, typename _Fn1> inline _Fn1 for_each(_InIt _First, _InIt _Last, _InIt2 _First2, _InIt3 _First3, _Fn1 _Func) { for (; _First != _Last; ++_First,++_First2,++_First3) _Func(*_First, *_First2, *_First3); return (_Func); } template<typename _InIt, typename _InIt2, typename _InIt3, typename _InIt4, typename _Fn1> inline _Fn1 for_each(_InIt _First, _InIt _Last, _InIt2 _First2, _InIt3 _First3, _InIt4 _First4, _Fn1 _Func) { for (; _First != _Last; ++_First,++_First2,++_First3,++_First4) _Func(*_First, *_First2, *_First3, *_First4); return (_Func); } template<typename _InIt, typename _InIt2, typename _InIt3, typename _InIt4, typename _InIt5, typename _Fn1> inline _Fn1 for_each(_InIt _First, _InIt _Last, _InIt2 _First2, _InIt3 _First3, _InIt4 _First4, _InIt5 _First5, _Fn1 _Func) { for (; _First != _Last; ++_First,++_First2,++_First3,++_First4,++_First5) _Func(*_First, *_First2, *_First3, *_First4, *_First5); return (_Func); }

1 0

[endian] Updated version available in the file vault
by Beman Dawes 30 May '08

30 May '08

There's an updated version available in the file vault. Changes include: * Use of namespaces to simulate C++0x scoped enums. * Addition of operator= for improved efficiency. * Updated docs, including new FAQ entries. * Jamfile.v2 added. See http://tinyurl.com/4bswsh Does this look ready for formal review? Comments appreciated! --Beman

4 5