- Boost - lists.boost.org

Logging update?
by Colin Caughie 13 Mar '08

13 Mar '08

Hi, It's a while now since the review of John Torjo's Logging library was concluded, and I'm curious to know what the result was. Is it still being considered? Thanks, Colin

4 11

customizing complex data structures such as graphs and meshes
by Ares Lagae 13 Mar '08

13 Mar '08

I discovered an interesting pattern that makes it easy to customize elements in complex data structures. For example, customizing nodes and edges of a graph, or vertices edges and faces of a mesh. I found it interesting and wanted to share it. I have attached an example involving graphs, although I currently use it to customize 3D meshes. Maybe it is of interest to anyone. I am open for comments and suggestions. -- Ares Lagae Computer Graphics Research Group, Katholieke Universiteit Leuven http://www.cs.kuleuven.be/~ares/ // ----------------------------------------------------------------------------- // general node, edge, graph #include <vector> template <typename GraphType> class node { public: node() {} }; template <typename GraphType> class edge { public: typedef GraphType graph_type; typedef typename graph_type::node_iterator node_iterator; edge() {} edge(node_iterator node_0, node_iterator node_1) { nodes_[0] = node_0; nodes_[1] = node_1; } private: node_iterator nodes_[2]; }; template < template <typename> class NodeType, template <typename> class EdgeType > class graph { public: typedef graph graph_type; typedef node<graph_type> node_base_type; typedef edge<graph_type> edge_base_type; typedef NodeType<graph_type> node_type; typedef EdgeType<graph_type> edge_type; typedef typename std::vector<node_type>::iterator node_iterator; typedef typename std::vector<edge_type>::iterator edge_iterator; node_iterator insert(const node_type& node) { return nodes_.insert(nodes_.end(), node); } edge_iterator insert(const edge_type& edge) { return edges_.insert(edges_.end(), edge); } private: std::vector<node_type> nodes_; std::vector<edge_type> edges_; }; // ----------------------------------------------------------------------------- // custom my_node, my_edge template <typename GraphType> class my_node : public GraphType::node_base_type { public: typedef GraphType graph_type; typedef typename graph_type::node_base_type node_base_type; my_node() : node_base_type() {} // custom members }; template <typename GraphType> class my_edge : public GraphType::edge_base_type { public: typedef GraphType graph_type; typedef typename graph_type::edge_base_type edge_base_type; typedef typename graph_type::node_iterator node_iterator; my_edge() : edge_base_type() {} my_edge(node_iterator node_0, node_iterator node_1) : edge_base_type(node_0, node_1) {} // custom members }; // ----------------------------------------------------------------------------- // main int main(int argc, char* argv[]) { { // graph using node and edge typedef graph<node, edge> graph_type; graph_type g; graph_type::node_iterator ni1 = g.insert(graph_type::node_type()); graph_type::node_iterator ni2 = g.insert(graph_type::node_type()); graph_type::edge_iterator ei = g.insert(graph_type::edge_type(ni1, ni2)); } { // graph using my_node and edge typedef graph<my_node, edge> graph_type; graph_type g; graph_type::node_iterator ni1 = g.insert(graph_type::node_type()); graph_type::node_iterator ni2 = g.insert(graph_type::node_type()); graph_type::edge_iterator ei = g.insert(graph_type::edge_type(ni1, ni2)); } { // graph using my_node and my_edge typedef graph<my_node, my_edge> graph_type; graph_type g; graph_type::node_iterator ni1 = g.insert(graph_type::node_type()); graph_type::node_iterator ni2 = g.insert(graph_type::node_type()); graph_type::edge_iterator ei = g.insert(graph_type::edge_type(ni1, ni2)); } { // graph using node and my_edge typedef graph<node, my_edge> graph_type; graph_type g; graph_type::node_iterator ni1 = g.insert(graph_type::node_type()); graph_type::node_iterator ni2 = g.insert(graph_type::node_type()); graph_type::edge_iterator ei = g.insert(graph_type::edge_type(ni1, ni2)); } }

1 0

[announce] Dynamic object factory v3
by Marco Costalba 13 Mar '08

13 Mar '08

Yet another object factory announce! Sorry to announce another version, but I think "this is the last one" (tm) ;-) Small, easy to read, self-contained, feature complete, compiler friendly, and really really nice (at least for my coding style taste). I spent a lot of time polishing this toy. IMHO could be an example of C++ template programming for beginners/intermediate users. Interested people could find it in boost vault under the name factory_24_2_08.zip, of course any feedback is welcomed. Thanks for your attention Marco

3 4

[python] BOOST_PYTHON_MODULE() causing .lib generation?
by Robert Dailey 13 Mar '08

13 Mar '08

Hi, I'm currently using MSVC 9 with Boost 1.34.1. When I create a boost module using BOOST_PYTHON_MODULE(), I notice that my application is generating a .lib and .exp files when my application is a .exe (I'm embedding python, not extending into a library). I have no need for my application to generate a .lib file, is there a way I can disable the generation of this library file? Thanks.

4 12

[python] Crash when running variant=debug-python libraries
by Robert Dailey 13 Mar '08

13 Mar '08

Hi, First off I am using Boost 1.34.1 and I have built the libraries myself using the following command line. My compiler is MSVC 9.0. *bjam --toolset=msvc --layout=system link=shared threading=multi variant=debug-python stage* The code I'm running has worked fine using *variant=debug*, however it crashes with an "access violation" against NULL with *variant=debug-python*, which I had assumed defined BOOST_DEBUG_PYTHON. My goal was to get the debug Boost.Python library to link against the debug python25 shared library (it seemed to work). Below is the code I'm compiling. BEGIN CODE --------------------------------------------- #define BOOST_PYTHON_DEF( func ) boost::python::def( #func, func ) using namespace boost::python; static char const* PrintHelloWorld() { return "Hello World!"; } BOOST_PYTHON_MODULE(Script) { BOOST_PYTHON_DEF( PrintHelloWorld ); } object GetNamespace( char const* mod ) { object theModule = import( mod ); return theModule.attr( "__dict__" ); } void BeginPythonTest() { try { Py_Initialize(); initScript(); object main = GetNamespace( "__main__" ); object sys = GetNamespace( "sys" ); list path( sys["path"] ); path.insert( 0, "python" ); sys["path"] = path; main["Script"] = import( "Script" ); main["rocket"] = import( "rocket" ); exec_file( "pythontest.py", main, main ); Py_Finalize(); } catch( error_already_set const& /*err*/ ) { PyErr_Print(); } catch( std::invalid_argument const& /*err*/ ) { PyErr_Print(); } } --------------------------------------------- END CODE And, for your reference, the callstack at the time of the crash (note that it may be a little bit mangled): *> boost_python-mt-gy.dll!boost::python::objects::function::function(const boost::python::objects::py_function & implementation={...}, const boost::python::detail::keyword * const names_and_defaults=0x7ffdb000, unsigned int num_keywords=3435973836) Line 104 + 0xb bytes C++ 0012f520() boost_python- mt-gy.dll!boost::detail::function::void_function_ref_invoker0<void (__cdecl*)(void),void>::invoke(boost::detail::function::function_buffer & function_obj_ptr={...}) Line 191 C++ boost_python-mt-gy.dll!boost::function0<void,std::allocator<boost::function_base> >::operator()() Line 692 + 0x11 bytes C++ boost_python-mt-gy.dll!boost::python::handle_exception_impl(boost::function0<void,std::allocator<boost::function_base> > f={...}) Line 26 C++ boost_python-mt-gy.dll!boost::python::handle_exception<void (__cdecl*)(void)>(void (void)* f=0x00474695) Line 29 + 0x2c bytes C++ boost_python-mt-gy.dll!boost::python::detail::init_module(const char * name=0x0055ea08, void (void)* init_function=0x00474695) Line 39 + 0x9 bytes C++ rocket_test_Debug.exe!initScript() Line 15 + 0x30 bytes C++ rocket_test_Debug.exe!BeginPythonTest() Line 34 C++*

2 2

Re: [boost] Problem linking Boost Unit Test Library on windows(1.33.0)
by Duft Markus 12 Mar '08

12 Mar '08

Hello Martin! First of all thanks for the answer. Martin Schulz <> wrote: > Hello Markus, > > you should not link your _application_ against boost test at all. > IMHO, you should compile the test cases in a separate executable that > runs all tests one after the other. I had completely wrong information here. Our setup is exactly the one you described. The console app which links against the test framework doesn't link. Our main application links fine though (without the test framework of course)... The error message is (sorry for the german messages... Damn i18n :)): libboost_unit_test_framework.a(unit_test_main.obj) : error LNK2005: _main ist bereits in _check_owerrdialogs.o definiert. libboost_unit_test_framework.a(framework.obj) : error LNK2019: Verweis auf nicht aufgelöstes externes Symbol ""class boost::unit_test::test_suite * __cdecl init_unit_test_suite(int,char * * const)" (?init_unit_test_suite@@YAPAVtest_suite@unit_test@boost@@HQAPAD@Z)" in Funktion ""void __cdecl boost::unit_test::framework::init(int,char * * const)" (?init@framework@unit_test@boost@@YAXHQAPAD@Z)". wamas-test_global_checkowerrdialogs__check_owerrdialogs.exe : fatal error LNK1120: 1 nicht aufgelöste externe Verweise. Basically it says, there is allready a main in the test framework, and that there is no init_unit_test_suite which it would require. > > The simplest way to avoid any link hassle there is to have a single > cpp > file containing > > #define BOOST_AUTO_TEST_MAIN > #include <boost/test/auto_unit_test.hpp> > #include <boost/test/included/unit_test_framework.hpp> I looked into the test program he is trying to link. It has a main() which does some initialization, and the adds some test cases. Should this be changed to be a init_unit_test_suite instead of main? If yes, does this work on all platforms, or is this just a windows thing? Also i cannot find BOOST_AUTO_TEST_MAIN anywhere in the source, and boost/test/unit_test.hpp is included instead of auto_unit_test.hpp. unit_test_framework.hpp is also not included... Cheers, Markus > > And compile this (together with your test cases) into a command line > executable. That way, the linker has a little bit more to do on each > compiler run, but you do avoid any mismatch of compiler options and > the > like. > > Yours, > >> -----Original Message----- >> From: boost-bounces(a)lists.boost.org > [mailto:boost-bounces@lists.boost.org] >> On Behalf Of Duft Markus >> Sent: Donnerstag, 28. Februar 2008 08:42 >> To: boost(a)lists.boost.org >> Subject: [boost] Problem linking Boost Unit Test Library on windows >> (1.33.0) >> >> Hi! >> >> I have a problem linking our application on windows. Somebody added >> test cases using the boost unit test library, and since then windows >> won't link anymore. The problem is, that the boost library contains >> a "main" and doesn't seem to contain a "init_unit_test_suite" >> function (am I missing a library?). It works on all other systems, >> is windows unsupported there? >> >> Is there any more information I should gather for you to see the >> problem, or is this a known issue (I remember seeing something on the >> list about this, but I think it was about a newer boost version. Can >> any eventually made changes be expressed as a patch for 1.33.0 so I >> can locally fix the issue, and won't need an upgrade)? >> >> Cheers, Markus >> _______________________________________________ >> Unsubscribe & other changes: >> http://lists.boost.org/mailman/listinfo.cgi/boost > _______________________________________________ > Unsubscribe & other changes: > http://lists.boost.org/mailman/listinfo.cgi/boost

3 8

Request interest on a Locally Unique Identifier library
by vicente.botet 12 Mar '08

12 Mar '08

Hi everyone, I'm starting a library to manage Locally Unique Identifiers (LUID). I'd like to ask if there is interest in a such library? I haven't found on the net any reference to such a library. Please could you point me to some libraries addressing this kind of problem or whatever could be related to this domain, algorithms, ... If there is an interest, I would like to know which are the minimal features such a library should have for a first review, and which one could be left for a second one. Best regards _____________________ Vicente Juan Botet Escriba Next follows my first thoughts: Boost.LUID simplifies the generation of locally unique identifiers in a configurable context. Locally Unique Identifier or LUID is a special type of identifier used in software applications in order to provide a reference number which is unique in a given context (hence, "Locally" in opposition to "Globally" or "Universally"). Each generated LUID is guaranteed to be unique in its context. LUID could have many applications. Some examples follow: creating unique identifiers in a database tables, network messages may be identified with a LUID to ensure that this messages are associated to a given session, transactions may be identified by LUIDs. Note. Please let me know other applications of LUIDs you can have. Reduced identifier size An attractive feature of LUIDs when compared to alternatives is the minimal size used by this identifiers, that depends on the number of instances a given context can have (usually 4 bytes). This allows to use them in protocols fixing the size of the references exchanged to less that 16 bytes(as it is the case of UUID and GUID). Usually LUIDs are represented by unsigned integers and have an upper bound value. Usable as random access index in constant time Another aspect, and not less interesting is that the access to the information they identify can be done in constant time. Recovering unused identifiers A first implementation could consists in a monotonic counter. The drawback of having a small size is that the number of unique identifier is more limited. This limit will finish by been reached if the application runs a long time. To paliate to this, we need a mechanism to recover the unused identifiers once the identified information is removed. Depending on the application the recovered identifiers should be discarded, reused immediately or frozen during a given duration or a number of times. Usually they are reused in a first reusable first reused order (fifo), but depending on the implementation this could not be always the more efficient policy. So the user can either constraint this fifo order or let undefined this aspect. Managing the lack of identifiers In any case we need to manage with the overflow case, i.e. when there are no more free identifiers. The user could prefer an exception, return an invalid value, use errno, or call to a user defined function which could try to recover from this situation, changing the upper bound for example. Ensuring coherency on reusable identifiers All this seams to work up to the user do not release the same identifiers twice. This is an expensive task, but usually the applications has its own way to do it. If this is not the case the application could ask to the luid generator to ensure that. Synchronization on multi threaded or multi process applications The generation of new LUIDs and the recovering of unused LUIDs must be synchronized. So LUID are better adapted to systems where these operations are done in a reduced scope. Depending on this scope: single thread, multi-threaded process or a node,i.e. multiple process, the synchronization mechanisms vary. In a single thread scope no synchronization is needed. Synchronization on a multi-threaded process can be ensured using a thread mutex and so one. In addition the synchronization can be ensured internally by the generator, or externally by the user, i.e. the user has already a synchronization mechanism. LUIDs are not adapted to distributed system (multiple nodes generating and recovering luids) because it needs a coordination between the different nodes which will take too much time. UUIDs and GUIDs are more adapted to this situation. Anyway if the size constraint can not be avoided, one of the nodes could play the master role and the others behaves as slaves. Master and slaves need to work together. This library do not pretend to take in account this use case but, could be the base of such approach. Persistency Another aspect is the lifetime of the information to be identified by the luids. It can be the lifetime of the process, the host machine lifetime or persists to a shut down of the host machine using the filesystem. Optimization The last aspect will be the optimization. Different application have different needs, some have space constraints, and mot of the others have speed constraints. One possible design could request to declare a variable for each luid generator and use functions like make and release. typedef boost::luid::luidg<uint32, ...> X_luid_generator; X_luid_generator x_luidg; //// uint32 uid = luidg.make(); ... luidg.release(uid); As the uid have a meaning only associated to the information it identifies, usually the use of this functions should be done implicitly when the information is stored on a container is removed. typedef boost::luid::luidg<uint32> X_luid_mgr; typedef my_multi_index<X, ..., luid_generator<X_luid_mgr> > X_container; // construct the container, constructing a X_luid_mgr X_container x_cont(...); X x; ... // inserts the element in the container and // returns the new luid associated to the inserted element (luidg.make()) unisgned int uid = x_cont.insert(x); // this uid could be shared with other applications ... // later on the application use the uid to obtain the context X* x=x_cont.get(uid); // do something ... // removes the element identified by uid and release the uid. (luidg.release(uid)) x_cont.remove(uid); This library could use the following Boost libraries - Boost.DynamicBitSet to store the recovered luids - Boost.Integer to obtain the default bounds - Boost.Interprocess to lock on inter_node scope - Boost.Intrusive to store the recovered luids in fifo order - Boost.Interprocess to store on shared memory when the lifetime is longer than the process one. - Boost.Parameters to pass the constructor parameters - Boost.Parameters to configure the template parameters - Boost.Threads to lock on multi_threaded scope I wonder if this library could be used to extend the Boost.MultiIndex library with luid unique keys. The number of user functions provided by LUID generator are quite simple: * make: make a new luid (constant time complexity) * release: release an luid (could check that the luid is not already free) (constant time complexity without ensuring coherency) * error: the value returned when no more luids are available (constant time complexity) * set_upper_bound: sets the new upper bound (could have linear time complexity when coherency is required) * get_upper_bound: get the current upper bound (constant time complexity) * count: get the number of used luids (chould be constant time complexity if a counter is used) * clear: release all the used ressources and reset them as they were after construction (could have linear time complexity)

1 0

linker errors using boost::thread with dev-c++ 4.9.9.2 (gcc 3.4.2) on win2k, plz help
by matthieu 12 Mar '08

12 Mar '08

Hi guys, I've just install Dev-Cpp 4.9.9.2, download boost 1.34.1 and boost-jam 3.1.16, extract the archive, build bjam, then finaly build boost (all libraries). Everything was fine. Take lots of time, lots of space.. Now I just try to compile and execute a boost example for the threads: "tennis.cpp" and I've linker Errors :'( Is there a known problem for these Dev-Cpp release or is it just a configuration problem on my computer? I'm under windows 2000 sp4 (at work...) You'll find all the info under. Thanks in advance for the help, Mat Here is the log from Dev-c++: Compiler: Default compiler Executing g++.exe... g++.exe "D:\Apps\boost_1_34_1\libs\thread\example\tennis.cpp" -o "D:\Apps\boost_1_34_1\libs\thread\example\tennis.exe" -I"D:\Apps\boost_1_3 4_1" -I"C:\Dev-Cpp\lib\gcc\mingw32\3.4.2\include" -I"C:\Dev-Cpp\include\c+ +\3.4.2\backward" -I"C:\Dev-Cpp\include\c++\3.4.2\mingw32" -I"C:\Dev-Cpp\i nclude\c++\3.4.2" -I"C:\Dev-Cpp\include" -L"C:\Dev-Cpp\lib" -L"D:\Apps\bo ost_1_34_1\stage\lib" C:\DOCUME~1\MATTHI~1\LOCALS~1\Temp/ccY9aaaa.o(.text+0x442):tennis.cpp: undefined reference to `boost::thread::thread(boost::function0<void, std::allocator<boost::function_base> > const&)' C:\DOCUME~1\MATTHI~1\LOCALS~1\Temp/ccY9aaaa.o(.text+0x500):tennis.cpp: undefined reference to `boost::thread::thread(boost::function0<void, std::allocator<boost::function_base> > const&)' C:\DOCUME~1\MATTHI~1\LOCALS~1\Temp/ccY9aaaa.o(.text+0x566):tennis.cpp: undefined reference to `boost::xtime_get(boost::xtime*, int)' C:\DOCUME~1\MATTHI~1\LOCALS~1\Temp/ccY9aaaa.o(.text+0x57b):tennis.cpp: undefined reference to `boost::thread::sleep(boost::xtime const&)' C:\DOCUME~1\MATTHI~1\LOCALS~1\Temp/ccY9aaaa.o(.text+0x7ad):tennis.cpp: undefined reference to `boost::thread::join()' C:\DOCUME~1\MATTHI~1\LOCALS~1\Temp/ccY9aaaa.o(.text+0x7b8):tennis.cpp: undefined reference to `boost::thread::join()' C:\DOCUME~1\MATTHI~1\LOCALS~1\Temp/ccY9aaaa.o(.text+0x7cd):tennis.cpp: undefined reference to `boost::thread::~thread()' C:\DOCUME~1\MATTHI~1\LOCALS~1\Temp/ccY9aaaa.o(.text+0x7e2):tennis.cpp: undefined reference to `boost::thread::~thread()' C:\DOCUME~1\MATTHI~1\LOCALS~1\Temp/ccY9aaaa.o(.text+0x80f):tennis.cpp: undefined reference to `boost::thread::~thread()' C:\DOCUME~1\MATTHI~1\LOCALS~1\Temp/ccY9aaaa.o(.text+0x83c):tennis.cpp: undefined reference to `boost::thread::~thread()' C:\DOCUME~1\MATTHI~1\LOCALS~1\Temp/ccY9aaaa.o(.text+0x8b8):tennis.cpp: undefined reference to `boost::mutex::mutex()' C:\DOCUME~1\MATTHI~1\LOCALS~1\Temp/ccY9aaaa.o(.text+0x909):tennis.cpp: undefined reference to `boost::mutex::~mutex()' C:\DOCUME~1\MATTHI~1\LOCALS~1\Temp/ccY9aaaa.o(.text$_ZN5boost9condition10not ify_allEv[boost::condition::notify_all()]+0x10):tennis.cpp: undefined reference to `boost::detail::condition_impl::notify_all()' C:\DOCUME~1\MATTHI~1\LOCALS~1\Temp/ccY9aaaa.o(.text$_ZN5boost9condition4wait INS_6detail6thread11scoped_lockINS_5mutexEEEEEvRT_[void boost::condition::wait<boost::detail::thread::scoped_lock<boost::mutex> >(boost::detail::thread::scoped_lock<boost::mutex>&)]+0x68):tennis.cpp: undefined reference to `boost::lock_error::lock_error()' C:\DOCUME~1\MATTHI~1\LOCALS~1\Temp/ccY9aaaa.o(.text$_ZN5boost9condition4wait INS_6detail6thread11scoped_lockINS_5mutexEEEEEvRT_[void boost::condition::wait<boost::detail::thread::scoped_lock<boost::mutex> >(boost::detail::thread::scoped_lock<boost::mutex>&)]+0xa4):tennis.cpp: undefined reference to `boost::lock_error::~lock_error()' C:\DOCUME~1\MATTHI~1\LOCALS~1\Temp/ccY9aaaa.o(.text$_ZN5boost6detail6thread1 1scoped_lockINS_5mutexEE4lockEv[boost::detail::thread::scoped_lock<boost::mu tex>::lock()]+0x5b):tennis.cpp: undefined reference to `boost::lock_error::lock_error()' C:\DOCUME~1\MATTHI~1\LOCALS~1\Temp/ccY9aaaa.o(.text$_ZN5boost6detail6thread1 1scoped_lockINS_5mutexEE4lockEv[boost::detail::thread::scoped_lock<boost::mu tex>::lock()]+0x97):tennis.cpp: undefined reference to `boost::lock_error::~lock_error()' C:\DOCUME~1\MATTHI~1\LOCALS~1\Temp/ccY9aaaa.o(.text$_ZN5boost6detail6thread1 1scoped_lockINS_5mutexEE6unlockEv[boost::detail::thread::scoped_lock<boost:: mutex>::unlock()]+0x5b):tennis.cpp: undefined reference to `boost::lock_error::lock_error()' C:\DOCUME~1\MATTHI~1\LOCALS~1\Temp/ccY9aaaa.o(.text$_ZN5boost6detail6thread1 1scoped_lockINS_5mutexEE6unlockEv[boost::detail::thread::scoped_lock<boost:: mutex>::unlock()]+0x97):tennis.cpp: undefined reference to `boost::lock_error::~lock_error()' C:\DOCUME~1\MATTHI~1\LOCALS~1\Temp/ccY9aaaa.o(.text$_ZN5boost9condition7do_w aitINS_5mutexEEEvRT_[void boost::condition::do_wait<boost::mutex>(boost::mutex&)]+0x10):tennis.cpp: undefined reference to `boost::detail::condition_impl::enter_wait()' C:\DOCUME~1\MATTHI~1\LOCALS~1\Temp/ccY9aaaa.o(.text$_ZN5boost9condition7do_w aitINS_5mutexEEEvRT_[void boost::condition::do_wait<boost::mutex>(boost::mutex&)]+0x30):tennis.cpp: undefined reference to `boost::detail::condition_impl::do_wait()' C:\DOCUME~1\MATTHI~1\LOCALS~1\Temp/ccY9aaaa.o(.text$_ZN5boost6detail6thread8 lock_opsINS_5mutexEE4lockERS3_[boost::detail::thread::lock_ops<boost::mutex> ::lock(boost::mutex&)]+0xd):tennis.cpp: undefined reference to `boost::mutex::do_lock()' C:\DOCUME~1\MATTHI~1\LOCALS~1\Temp/ccY9aaaa.o(.text$_ZN5boost6detail6thread8 lock_opsINS_5mutexEE6unlockERS3_[boost::detail::thread::lock_ops<boost::mute x>::unlock(boost::mutex&)]+0xd):tennis.cpp: undefined reference to `boost::mutex::do_unlock()' C:\DOCUME~1\MATTHI~1\LOCALS~1\Temp/ccY9aaaa.o(.text$_ZN5boost6detail6thread8 lock_opsINS_5mutexEE6unlockERS3_RPv[boost::detail::thread::lock_ops<boost::m utex>::unlock(boost::mutex&, void*&)]+0x14):tennis.cpp: undefined reference to `boost::mutex::do_unlock(void*&)' C:\DOCUME~1\MATTHI~1\LOCALS~1\Temp/ccY9aaaa.o(.text$_ZN5boost6detail6thread8 lock_opsINS_5mutexEE4lockERS3_RPv[boost::detail::thread::lock_ops<boost::mut ex>::lock(boost::mutex&, void*&)]+0x14):tennis.cpp: undefined reference to `boost::mutex::do_lock(void*&)' C:\DOCUME~1\MATTHI~1\LOCALS~1\Temp/ccY9aaaa.o(.text$_ZN5boost9conditionD1Ev[ boost::condition::~condition()]+0x46):tennis.cpp: undefined reference to `boost::detail::condition_impl::~condition_impl()' C:\DOCUME~1\MATTHI~1\LOCALS~1\Temp/ccY9aaaa.o(.text$_ZN5boost9conditionC1Ev[ boost::condition::condition()]+0x51):tennis.cpp: undefined reference to `boost::detail::condition_impl::condition_impl()' collect2: ld returned 1 exit status Execution terminated My g++ version: C:\Dev-Cpp\bin>g++ -v Using built-in specs. Configured with: ../gcc/configure --with-gcc --with-gnu-ld --with-gnu-as --host=mingw32 --tar get=mingw32 --prefix=/mingw --enable-threads --disable-nls --enable-language s=c,c++,f77 ,ada,objc,java --disable-win32-registry --disable-shared --enable-sjlj-excep tions --enable-libgcj --disable-java-awt --without-x --enable-java-gc=boehm --disable-libgcj-debug --ena ble-interpreter --enable-hash-synchronization --enable-libstdcxx-debug Thread model: win32 gcc version 3.4.2 (mingw-special) C:\Dev-Cpp\bin> Thread libs in my lib folder: D:\Apps\boost_1_34_1\stage\lib>ls -lh | grep thread -rwxrwxrwx 1 Administrators ???????? 165K Mar 12 11:10 boost_thread-mgw34-mt-1_34_1.a -rwxrwxrwx 1 Administrators ???????? 332K Mar 12 11:10 boost_thread-mgw34-mt-1_34_1.dll -rwxrwxrwx 1 Administrators ???????? 418K Mar 12 11:04 boost_thread-mgw34-mt-d-1_34_1.a -rwxrwxrwx 1 Administrators ???????? 3.8M Mar 12 11:04 boost_thread-mgw34-mt-d-1_34_1.dll -rwxrwxrwx 1 Administrators ???????? 110K Mar 12 11:22 libboost_thread-mgw34-mt-1_34_1.a -rwxrwxrwx 1 Administrators ???????? 7.1M Mar 12 11:20 libboost_thread-mgw34-mt-d-1_34_1.a -rwxrwxrwx 1 Administrators ???????? 110K Mar 12 11:33 libboost_thread-mgw34-mt-s-1_34_1.a -rwxrwxrwx 1 Administrators ???????? 7.1M Mar 12 11:30 libboost_thread-mgw34-mt-sd-1_34_1.a D:\Apps\boost_1_34_1\stage\lib> Rq: if I copy these files directly in the Dev-Cpp lib folder (C:\Dev-Cpp\lib) and don't put my -L arg in the compilation command, the result is the same :'(

2 1

[proto] docs unclear (to me) for: "Expression Nodes as Fusion Sequences"
by Markus Werle 12 Mar '08

12 Mar '08

Hi! In the section "Expression Nodes as Fusion Sequences" you show the follwing code struct fun_t {}; terminal<fun_t>::type const fun = {{}}; // ... fusion::for_each( fusion::transform( // pop_front() removes the "fun" child fusion::pop_front(fun(1,2,3,4)) // Extract the ints from the terminal nodes , functional::arg<>() ) , display() ); It did not became clear to me why a terminal<fun_t>::type can be initialized with 4 integer arguments. I thought terminal<fun_t>::type is equivalent to expr< tag::terminal, args0< fun_t >, 0 > and should take no args at all. Could you clarify this? Markus

2 5

shifted_ptr w/ make_shifted_ptr
by Phil Bouchard 12 Mar '08

12 Mar '08

Ok, I replaced former macro with make_shifted_ptr<>() constructor and allocator function. Like previously mentionned the template parameters of that function add the "const" modifier; therefore it cannot emulate constructors having non-const references. I was reading about the new variadic template arguments that was added in the new compiler... I haven't tried it yet but I am afraid the same problem will happen. Furthermore, I decided not to replace type of "owned<>::p_" with "optional<>" because it doesn't reflect the same purpose and adds an unwanted boolean flag. Regards, -Phil

1 0