- Boost-users - lists.boost.org

Linking problems with 'scoped_static_mutex_lock' from regex library?!
by Arno 06 Mar '06

06 Mar '06

Hi all, I have successfully build boost 1.33.1 on solaris 2.8 with SunStudio 10 with stlport and try now to build my application what was running with boost 1.31 on windows. I have had no problems during compiling my stuff all seems to be fine, but when I am linking I get some unreferenced symbols in my code what I didn't know, because I don't know, that I am using it. So the linker said, that he can't find 'boost::scoped_static_mutex_lock::~scoped_static_mutex_lock()' and 'boost::scoped_static_mutex_lock::scoped_static_mutex_loc(boost::static_mutex&,bool) '. After a littele bit of investigation I found the definition of this class in a Header 'regex/pending/static_mutex.hpp'. I link actualy the libraries 'libboost_regex-sw-1_33_1', 'libboost_thread-sw-mt-1_33_1' and 'libboost_date_time-sw-1_33_1' to my application have I to link something more or do I have to make something else to get these build running! Thanks for any help! regards Arno

2 1

Re: [Boost-users] Getting started with Boost: what did you need to know?
by Merrill Cornish 06 Mar '06

06 Mar '06

David, At the risk of annoying some Boost developers... My single biggest complaint is the Boost documentation-- not so much that the libraries are undocumented, but that it's so hard to find your way through the documentation that is provided. There is the documentation on the Boost site rooted under Libraries | Documentation. Then there is the documentation under doc/html in the Boost source tree. Then there is the documentation under libs/<libraryName>/doc in the source tree. Sometimes, they are the same, sometimes, the libs documentation has extra stuff. Why? A side effect of having HTML documentation is that there is no index--a valuable tool when you are trying find your way through new territory. The Boost documentation standard recommends having a table of contents-like list of topics on the first page of a library's documentation. Sounds good, but since there usually isn't any paragraphing levels shown, what you get is a list of topics, some of which repeat with no indication of which are subtopics of which. The naming of documentation files can be misleading also. The discussion of mutexes (with no specific mention of threads) is called "thread" while the discussion of threading (with no specific mention of mutexes) is call "threads" [note the plural]. Or, maybe it's the other way around. The available documentation takes a scatter gun approach at to the intended audience. Under mutexes (whatever its name), there is a treatise (as I remember) on all possible mutex alternatives. It's only later that the reader discovers none of them are actually implemented. Similarly, the serialization documentation has a long discussion on shared pointers in a file named shared_ptr.html. Another file named shared_ptr2.html starts out by saying that about the stuff you just read in shared_ptr.html "Unfortunately, this way of doing it suffered from some undesirable features." This is a lot like giving someone detailed driving directions only to say, "if you go this far, you've taken a wrong turn." The documentation is written so that in order to do almost anything, you have to read everything, including all of the "here are all the wrong turns I took in developing this library" pages. For example, the documentation for the serialization library seems straightforward, but you'll probably miss the special macro you are supposed to use if you are serializing an abstract class. The Boost documentation is serverly in the need of global editing. Merrill

4 4

[BGL] Why this is not compiled?
by Dmitry Bufistov 06 Mar '06

06 Mar '06

Hi all, I'm trying to compile the following code and have some compiler errors (MSVC 8). // TestBoostGraph1.cpp : Defines the entry point for the console application. // #include "stdafx.h" #include <string> #include <boost/graph/adjacency_list.hpp> #include <boost/graph/adjacency_matrix.hpp> #include <boost/graph/graphviz.hpp> #include <boost/graph/iteration_macros.hpp> #include <boost/graph/graph_utility.hpp> #include <boost/graph/copy.hpp> ///Just for read "work around" ///Two typedefs for modeling both "discrete" & "continues" nets typedef int discret_net_t; typedef double continues_net_t; /// typedef enum {PLACE, TRANSITION} node_type_t; /*! * If you need some more properties, then you should define your property class that derived from * basic_vertex_properties<>; - for nodes, * basic_edge_properties<>; - for edges * Example: struct my_node_prop : basic_vertex_properties<discret_net_t> { typedef double node_delay_t; node_delay_t m_node_delay; }; typedef CPetriNet<adj_list, boost::vecS, boost::listS, boost::bidirectionalS, my_node_prop> petri_net_t * * The types of all property values must be Copy Constructible, Assignable and Default Constructible!! */ template <class T = discret_net_t> struct basic_vertex_properties { typedef std::string node_name_type; typedef int node_index_t; basic_vertex_properties(node_type_t nt = TRANSITION) : m_node_type(nt) { m_token_number = T(0);} T m_token_number; ///Only for place, possible costruct "continues" nets node_name_type m_node_name; node_type_t m_node_type; ///Vertex could be "Place" or "transition" node_index_t m_node_index;///Internal property for convenient vertices lookup }; ///Basic properties for edge template <class T = discret_net_t> struct basic_edge_properties { typedef int edge_index_t; basic_edge_properties(T ew = 0) : m_weight(ew) {} T m_weight; ///possible construct "continues" nets edge_index_t m_edge_index; ///Internal property for convenient vertices lookup; }; using boost::bidirectionalS; using boost::directedS; using boost::no_property; struct my_ver_p : public basic_vertex_properties<discret_net_t> { double m_node_delay; }; struct my_edge_p : public basic_edge_properties<discret_net_t> { double m_edge_delay; }; int _tmain(int argc, _TCHAR* argv[]) { typedef boost::adjacency_list<boost::listS, boost::listS, directedS, my_ver_p> adj_list1_t; adj_list1_t c(10); boost::property_map<adj_list1_t, my_ver_p::node_name_type my_ver_p::* >::type node_name_map1(boost::get(&my_ver_p::m_node_name, c)); boost::print_graph(c, node_name_map1) ; return 0; } 1>------ Build started: Project: TestBoostGraph1, Configuration: Debug Win32 ------ 1>Compiling... 1>TestBoostGraph1.cpp 1>d:\documents and settings\dmitry\my documents\visual studio 2005\projects\testboostgraph1\testboostgraph1\testboostgraph1.cpp(78) : error C2664: 'boost::bundle_property_map<Graph,Descriptor,Bundle,T>::bundle_property_map(const boost::bundle_property_map<Graph,Descriptor,Bundle,T> &)' : cannot convert parameter 1 from 'boost::bundle_property_map<Graph,Descriptor,Bundle,T>' to 'const boost::bundle_property_map<Graph,Descriptor,Bundle,T> &' 1> with 1> [ 1> Graph=adj_list1_t, 1> Descriptor=void *, 1> Bundle=my_ver_p, 1> T=basic_vertex_properties<discret_net_t>::node_name_type 1> ] 1> and 1> [ 1> Graph=boost::adjacency_list<boost::listS,boost::listS,boost::directedS,my_ver_p>, 1> Descriptor=boost::detail::edge_desc_impl<boost::directed_tag,void *>, 1> Bundle=basic_vertex_properties<discret_net_t>, 1> T=basic_vertex_properties<discret_net_t>::node_name_type 1> ] 1> and 1> [ 1> Graph=adj_list1_t, 1> Descriptor=void *, 1> Bundle=my_ver_p, 1> T=basic_vertex_properties<discret_net_t>::node_name_type 1> ] 1> Reason: cannot convert from 'boost::bundle_property_map<Graph,Descriptor,Bundle,T>' to 'const boost::bundle_property_map<Graph,Descriptor,Bundle,T>' 1> with 1> [ 1> Graph=boost::adjacency_list<boost::listS,boost::listS,boost::directedS,my_ver_p>, 1> Descriptor=boost::detail::edge_desc_impl<boost::directed_tag,void *>, 1> Bundle=basic_vertex_properties<discret_net_t>, 1> T=basic_vertex_properties<discret_net_t>::node_name_type 1> ] 1> and 1> [ 1> Graph=adj_list1_t, 1> Descriptor=void *, 1> Bundle=my_ver_p, 1> T=basic_vertex_properties<discret_net_t>::node_name_type 1> ] 1> No user-defined-conversion operator available that can perform this conversion, or the operator cannot be called 1>TestBoostGraph1 - 1 error(s), 0 warning(s) ========== Build: 0 succeeded, 1 failed, 0 up-to-date, 0 skipped ========== if change graph representation to following typedef boost::adjacency_list<boost::listS, boost::listS, directedS, basic_vertex_properties<> > adj_list1_t; then this compiles without any error: adj_list1_t c(10); boost::property_map<adj_list1_t, basic_vertex_properties<>::node_name_type basic_vertex_properties<>::* >::type node_name_map1(boost::get(&basic_vertex_properties<>::m_node_name, c)); but with this I again have some error (just change "type" to "const_type" adj_list1_t c(10); boost::property_map<adj_list1_t, basic_vertex_properties<>::node_name_type basic_vertex_properties<>::* >::const_type node_name_map1(boost::get(&basic_vertex_properties<>::m_node_name, c)); 1>------ Build started: Project: TestBoostGraph1, Configuration: Debug Win32 ------ 1>Compiling... 1>TestBoostGraph1.cpp 1>d:\documents and settings\dmitry\my documents\visual studio 2005\projects\testboostgraph1\testboostgraph1\testboostgraph1.cpp(79) : error C2664: 'boost::bundle_property_map<Graph,Descriptor,Bundle,T>::bundle_property_map(const boost::bundle_property_map<Graph,Descriptor,Bundle,T> &)' : cannot convert parameter 1 from 'boost::bundle_property_map<Graph,Descriptor,Bundle,T>' to 'const boost::bundle_property_map<Graph,Descriptor,Bundle,T> &' 1> with 1> [ 1> Graph=const adj_list1_t, 1> Descriptor=void *, 1> Bundle=basic_vertex_properties<discret_net_t>, 1> T=const basic_vertex_properties<discret_net_t>::node_name_type 1> ] 1> and 1> [ 1> Graph=adj_list1_t, 1> Descriptor=void *, 1> Bundle=basic_vertex_properties<discret_net_t>, 1> T=basic_vertex_properties<discret_net_t>::node_name_type 1> ] 1> and 1> [ 1> Graph=const adj_list1_t, 1> Descriptor=void *, 1> Bundle=basic_vertex_properties<discret_net_t>, 1> T=const basic_vertex_properties<discret_net_t>::node_name_type 1> ] 1> Reason: cannot convert from 'boost::bundle_property_map<Graph,Descriptor,Bundle,T>' to 'const boost::bundle_property_map<Graph,Descriptor,Bundle,T>' 1> with 1> [ 1> Graph=adj_list1_t, 1> Descriptor=void *, 1> Bundle=basic_vertex_properties<discret_net_t>, 1> T=basic_vertex_properties<discret_net_t>::node_name_type 1> ] 1> and 1> [ 1> Graph=const adj_list1_t, 1> Descriptor=void *, 1> Bundle=basic_vertex_properties<discret_net_t>, 1> T=const basic_vertex_properties<discret_net_t>::node_name_type 1> ] 1> No user-defined-conversion operator available that can perform this conversion, or the operator cannot be called 1>TestBoostGraph1 - 1 error(s), 0 warning(s) ========== Build: 0 succeeded, 1 failed, 0 up-to-date, 0 skipped ========== What is wrong here? Any help would be greatly appreciated, Thanks in advance, --dima // TestBoostGraph1.cpp : Defines the entry point for the console application. // #include "stdafx.h" #include <string> #include <boost/graph/adjacency_list.hpp> #include <boost/graph/adjacency_matrix.hpp> #include <boost/graph/graphviz.hpp> #include <boost/graph/iteration_macros.hpp> #include <boost/graph/graph_utility.hpp> #include <boost/graph/copy.hpp> ///Just for read "work around" ///Two typedefs for modeling both "discrete" & "continues" nets typedef int discret_net_t; typedef double continues_net_t; /// typedef enum {PLACE, TRANSITION} node_type_t; /*! * If you need some more properties, then you should define your property class that derived from * basic_vertex_properties<>; - for nodes, * basic_edge_properties<>; - for edges * Example: struct my_node_prop : basic_vertex_properties<discret_net_t> { typedef double node_delay_t; node_delay_t m_node_delay; }; typedef CPetriNet<adj_list, boost::vecS, boost::listS, boost::bidirectionalS, my_node_prop> petri_net_t * * The types of all property values must be Copy Constructible, Assignable and Default Constructible!! */ template <class T = discret_net_t> struct basic_vertex_properties { //typedef node_type_t my_node_type; typedef std::string node_name_type; typedef int node_index_t; basic_vertex_properties(node_type_t nt = TRANSITION) : m_node_type(nt) { m_token_number = T(0);} T m_token_number; ///Only for place, possible costruct "continues" nets node_name_type m_node_name; node_type_t m_node_type; ///Vertex could be "Place" or "transition" node_index_t m_node_index;///Internal property for convenient vertices lookup }; ///Basic properties for edge template <class T = discret_net_t> struct basic_edge_properties { typedef int edge_index_t; basic_edge_properties(T ew = 0) : m_weight(ew) {} //private: T m_weight; ///possible construct "continues" nets edge_index_t m_edge_index; ///Internal property for convenient vertices lookup; }; using boost::bidirectionalS; using boost::directedS; using boost::no_property; struct my_ver_p : public basic_vertex_properties<discret_net_t> { double m_node_delay; }; struct my_edge_p : public basic_edge_properties<discret_net_t> { double m_edge_delay; }; int _tmain(int argc, _TCHAR* argv[]) { //typedef boost::adjacency_list<boost::listS, boost::listS, directedS, my_ver_p> adj_list1_t; typedef boost::adjacency_list<boost::listS, boost::listS, directedS, basic_vertex_properties<> > adj_list1_t; adj_list1_t c(10); boost::property_map<adj_list1_t, basic_vertex_properties<>::node_name_type basic_vertex_properties<>::* >::const_type node_name_map1(boost::get(&basic_vertex_properties<>::m_node_name, c)); boost::print_graph(c, node_name_map1) ; return 0; }

3 2

Resolving TR1/Boost conflicts
by Scott Meyers 06 Mar '06

06 Mar '06

Is there a Boost policy on resolving conflicts between Boost behavior and the TR1 spec? As an example, std::tr1::is_base_of<T, T> returns true, but boost::is_base_of<T, T> returns false. Changing Boost behavior would presumably break existing code, but failing to implement TR1 semantics is likely to be confusing/surprising to many. My understanding is that Boost is committed to bringing its TR1-like libraries into conformance with TR1, but it'd be helpful if people who follow Boost more closely than I could confirm that. Thanks, Scott

2 1

Newbie Build Problem - Debug Assertion Failed
by Eric Hill 06 Mar '06

06 Mar '06

New install of Visual C++ 2005 Express New install of the Platform SDK New download of boost-jam-3.1.12 I get the attached error when the build script tries to launch jam0. Any ideas? Reinstall something maybe? Eric --- Begin Build Log --- C:\boost-jam-3.1.12>build Setting environment for using Microsoft Visual Studio 2005 x86 tools. ### ### Using 'vc8' toolset. ### C:\boost-jam-3.1.12>rd /S /Q bootstrap C:\boost-jam-3.1.12>md bootstrap C:\boost-jam-3.1.12>cl /nologo /RTC1 /Zi /MTd -DNT -DYYDEBUG -wd4996 kernel32.lib advapi32.lib /Febootstrap\jam0 [snipped] command.c compile.c debug.c execnt.c expand.c filent.c glob.c hash.c hdrmacro.c headers.c jam.c jambase.c jamgram.c lists.c make.c make1.c newstr.c option.c parse.c pathunix.c Generating Code... Compiling... regexp.c rules.c scan.c search.c subst.c timestamp.c variable.c modules.c strings.c filesys.c builtins.c pwd.c class.c w32_getreg.c native.c set.c path.c regex.c property-set.c sequence.c Generating Code... Compiling... order.c Generating Code... C:\boost-jam-3.1.12>.\bootstrap\jam0 -f build.jam --toolset=vc8 "--toolset-root=C:\Program Files\Microsoft Visual Studio 8\Common7\Tools\..\..\VC\ " clean

2 2

[multi_array] How to use std algorithms, like for_each?
by Christian Henning 06 Mar '06

06 Mar '06

Hi there, I'm a little confused by the documentation of the multi_array lib. The begin() is supposed to return an iterator, but dereferencing doesn't resolve into the value type. This makes it a little complicated to use multi_arrays with standard algorithms. Please consider the following code snippet which wont compile on VC 7.1. class tVoxel { public: typedef short tValue; tVoxel(): _oValue( 0 ) {} tVoxel(tValue oValue): _oValue( oValue ) {} void set( const tValue& oValue ) { _oValue = oValue; } tValue& get() { return _oValue; } const tValue& get() const { return _oValue; } private: tValue _oValue; }; int _tmain(int argc, _TCHAR* argv[]) { typedef boost::multi_array<tVoxel, 3> tVolume; tVolume oVolume( boost::extents[3][3][3] ); tVolume::const_iterator iVoxel = oVolume.begin(); tVolume::const_iterator iVoxelEnd = oVolume.end(); const tVoxel& oVoxel = iVoxel->get(); return 0; } The error message goes like: error C2039: 'get' : is not a member of 'boost::detail::multi_array::const_sub_array<T,NumDims>' with [ T=tVoxel, NumDims=2 ] Do I miss something important, here? Thanks for your help, Christian

2 1

ptr_map bug in 1.33.1
by 笨笨 06 Mar '06

06 Mar '06

Hi, all, I'm a fresh hand to boost. I encounter some problems with ptr_map, in boost/ptr_container/detail/associative_ptr_container.hpp, line 107 & 111. size_type erase( const key_type& x ) // nothrow { BOOST_ASSERT( !this->empty() ); iterator i = find( x ); // nothrow // line 107 if( i == this->end() ) // nothrow return 0; // nothrow this->remove( i ); // nothrow return this->c_private().erase( i.base() ); // nothrow // line 111 } In fact I doubt the correctness of these two lines. First, find() is defined in ptr_map_adapter class, which is a descendant of associative_ptr_container. No other find() functions could match the case here. As for the erase() in line 111, it's actually std::map::erase(). But this overload should return nothing as specified in C++ standard (in the case of MS implementation, it returns an iterator). In no way can it be converted to size_type. Simple modifications on the code could solve this problem. Another thing for ptr_map_adapter is one of its Insert() overloads std::pair<iterator,bool> insert( key_type& key, value_type x ) I wonder why we don't use const key_type&? Without const modifier, the compiler would not allow passing constants to it. At last, never forget to mention my environment: VC 8.0 No test has been done in other environment. -- Jason

2 1

Thread creation problem
by Olaf van der Spek 05 Mar '06

05 Mar '06

Hi, I'm converting code using pthreads to boost::thread. I've now got this code: Cdns_worker::Cdns_worker(): m_run(true), m_thread(boost::bind(&Cdns_worker::run, this)) { // pthread_cond_init(&m_condition, NULL); // pthread_mutex_init(&m_mutex, NULL); // pthread_create(&m_thread, NULL, Cdns_worker::run, this); } The data the thread is using is in Cdns_worker, but it seems impossible to delay the thread creation until the end of the constructor, like I could with pthreads. What should I do in this case? I also noticed boost::thread has a default constructor but it's not copyable. What is the purpose of this default constructor? And are there any boost::thread examples? I couldn't find them in the documentation.

3 4

Support for reading/writing binary 'streams'
by Olaf van der Spek 05 Mar '06

05 Mar '06

Hi, When reading/writing binary streams, you often need to read/write an (unaligned) integer in big, little or native endian. Is there support for this in Boost? I think iostreams isn't usable as 'zero-copy' is required.

1 0

serializatoin + auto_ptr
by Denis Kuznetsov 05 Mar '06

05 Mar '06

If I build the boost demo_auto_ptr example from http://www.boost.org/libs/serialization/example/demo_auto_ptr.cpp it works fine. But if I change my code (see attach) it doesnt't compile. The main difference in my code from boost's sample is that I don't use save() and load() functions. If I add and call them it works fine. The reason my code doesn't compile is that I get BOOST_STATIC_ASSERT. Compiler (VC 7.1 and VC 8.0) points to the code: template<class Archive, class T> inline void save(Archive & ar, T &t){ // if your program traps here, it indicates taht your doing one of the following: // a) serializing an object of a type marked "track_never" through a pointer. // b) saving an non-const object of a type not markd "track_never) // Either of these conditions may be an indicator of an error usage of the // serialization library and should be double checked. See documentation on // object tracking. BOOST_STATIC_ASSERT(check_tracking<T>::value); // <---------- compile error save(ar, const_cast<const T &>(t)); } Why my code doesn't compile and what should I do to build it?

2 2