November 2004 - Boost-users - lists.preview.boost.org

boost::shared_ptr and stl algorithms
by Bill Eidson 15 Apr '05

15 Apr '05

std::vector< boost::shared_ptr<T> > TVec; I want to write a function object to run std::for_each. to do somework against members of T and accumulate results in functor. My attempts have failed in VC7 with memory errors in my operator() method. struct fo { bool operator()( boost::shared_ptr<T>& t ) { return true; } }; Thanks in advance bille

5 9

Will libraries built on WinNT run on Win98? (MinGW)
by Reed Hedges 31 Mar '05

31 Mar '05

I know that Win98 is not really supported, but is there any chance that libraries (specifically thread and regex) that were build on WinNT using MinGW work on Win98 (in MinGW)? My guess is no, but has anyone tried it? thanks reed

2 1

Bug in lexical_cast<> with doubles
by Leon Raj 29 Jan '05

29 Jan '05

I think I've found a bug in the boost::lexical_cast<> library (v1.31.0) on WinXP SP1, MSVC 6.0 (sp5) and MSVC.NET 2003. --- Start code snippet --- #include <boost/lexical_cast.hpp> #include <iostream> int main( int argc, char* argv[] ) { double dMax = = std::numeric_limits< double >::max(); // On a Win32 x86 system, dMax is now 1.7976931348623157e+308 // This is successful and strMax is "1.797693134862316e+308" std::string strMax = boost::lexical_cast< std::string >( dMax ); try { double newDMax = boost::lexical_cast< double >( strMax ); std::cout << "Successfuly" << std::endl; } catch ( boost::bad_lexical_cast& ) { std::cout << "Failed to cast" << std::endl; } // On a Win32 x86 system, this always fails, // because (I think) strMax overflows a double, // because 1.7976931348623157e+308 is *rounded UP* // to 1.797693134862316e+308, which cannot be // represented by a double } --- End code snippet --- ----------------------------------------------------- Leon Raj Senior Engineer Invetech Pty. Ltd. Phone: +61 3 9211 7000 (Switchboard) +61 3 9211 7938 (DDI) leon.raj(a)invetech.com.au IMPORTANT - This e-mail and any attachments may be confidential. Any retransmissions, dissemination or other use of these materials by persons or entities other than the intended recipient is prohibited. If received in error, please contact us and delete all copies. Before opening or using attachments, check them for viruses and defects. Our liability is limited to resupplying any affected attachments. [Any representations or opinions expressed in this e-mail are those of the individual sender, and not necessarily those of Vision Systems Limited].

2 1

boost::regex partial matches
by L.P. Mergen 31 Dec '04

31 Dec '04

Hello, I apologise in advance if this question is not direct to the right mailinglist, but this was the best I could find. The IRC channel also seems very quite... :) I am currently experimenting with the boost::regex library, and so far it seems to do just the thing I need. However, when I have a regex "[0-9]+[a-zA-Z]+" And want to match this against the string "42foo 42bar" It returns false. This is (as far as I can see) due to the library not taking partial matches too, even when I set the boost::match_partial and boost::match_any flags (which, according to my interpretation, should be doing the trick). Here is my statement: bool success = boost::regex_match(subject->c_str(), returns, expression, boost::match_partial | boost::match_any); I hope anyone has an idea what might be the problem here. Thanks in advance! :) Grt, Leon Mergen

5 5

graphviz compile problem
by Jean Utke 15 Dec '04

15 Dec '04

I am running into a problem compiling code that uses write_graphviz which used to work e.g. for gcc 3.3 and boost versions prior to 1.31. As I am trying to move forward I am testing different gcc and boost versions. Here is the example code: ---------------------------------------------------------------- #include "boost/graph/adjacency_list.hpp" #include "boost/graph/graphviz.hpp" class BoostVertexContentType { public: enum { num=100 }; typedef boost::vertex_property_tag kind; }; class BoostEdgeContentType { public: enum { num=101 }; typedef boost::edge_property_tag kind; }; int main(void) { boost::adjacency_list< boost::listS, boost::listS, boost::bidirectionalS, boost::property<BoostVertexContentType, int>, boost::property<BoostEdgeContentType, int> > b; std::ofstream anOutFileStream; anOutFileStream.open("test.dot",std::ios::out); boost::write_graphviz(anOutFileStream, b); anOutFileStream.close(); } ----------------------------------------------------------------- This compiles ok with gcc 3.3 and boost 1.30.0 / 1.30.2 It does not compile with gcc 3.3/3.4.3 and boost 1.31/1.32 basically complaining about: boost_1_32_0/boost/graph/graphviz.hpp:269: error: no match for `std::basic_ostream<char, std::char_traits<char> >& << const boost::detail::error_property_not_found&' operator My target right now is to use gcc 3.4.3 with boost 1.32. Before I spend time searching for a workaround I hope that somebody has seen this and that there is an easy solution. Thanks, Jean

4 7

Boost format library Segmentation fault with Intel 8.1
by Filipe Sousa 08 Dec '04

08 Dec '04

Hi! I get a segmentation fault with Intel compiler 8.1 using the fallowing code #include <boost/format.hpp> #include <iostream> int main() { std::cout << boost::format("writing %1%, x=%2% : %3%-th try") % "toto" % 40.23 % 50 << std::endl; return 0; } (idb) bt #0 0x0804aba8 in ctype<char>::is (this=0x41016b50, __m=2048, __c=49 '1') at ctype_inline.h:40 #1 0x08051d55 in std::isdigit (__c=49 '1', __loc=& { ... }) at locale_facets.h:4528 #2 0x0805517f in boost::io::detail::wrap_isdigit (c=49 '1', os=& { ... }) at parsing.hpp:36 #3 0x0805509b in boost::io::detail::wrap_scan_notdigit (beg= { ... }, end= { ... }, os=& { ... }) at parsing.hpp:46 #4 0x08054f7b in boost::io::detail::upper_bound_from_fstring (buf=& { ... }, arg_mark=37 '%', os=& { ... }, exceptions=-1 '\377') at parsing.hpp:351 #5 0x0804d33a in basic_format<char,std::char_traits<char> >::parse (this=0xbffff480, buf=& { ... }) at parsing.hpp:377 #6 0x0804ceab in basic_format<char,std::char_traits<char> >::basic_format (this=0xbffff480, str=0x80572a8 "writing %1%, x=%2% : %3%-th try") at format_implementation.hpp:37 #7 0x0804d02c in basic_format<char,std::char_traits<char> >::basic_format (this=0xbffff480, =<no value>) at format_implementation.hpp:38 #8 0x0804a41c in main () at test.cc:5 #9 0x4102e7f8 The same code works perfectly with gcc-3.4.2 under linux. Is this a bug in boost format library or a Intel compiler problem? My system: Debian, boost-1.31.0, gcc-3.4.2, Intel compiler 8.1 -- Filipe Sousa

2 1

iterator_adaptor: disguise iterator as const_iterator?
by Martin Wartens 03 Dec '04

03 Dec '04

Hi all, I am trying to disguise a std container non-const iterator as a const_iterator. My guess is that iterator_adaptor could be useful for this, but I can't figure it out myself. I am trying to solve an old problem with the standard library, which is that you can't convert a const_iterator into an iterator. [There are two "solutions" to that problem, one uses distance and is expensive, the other one does a brutal conversion on bitlevel which breaks for several std implementations.] My use case: I have written a wrapper class mymap for std::map. I only want to give map::const_iterators to the users of this class. If the user wants to erase an element from the map, he must pass a const_iterator back to the wrapper class and call "mymap::erase(const_iterator)". The problem is that mymap has no way to convert the const_iterator into an iterator to call "map::erase(iterator)" in turn [there is no "map::erase(const_iterator)"]. So my idea was to write a iterator_adaptor for iterator that lets it behave like a const_iterator. Unfortunately I didn't get very far. I have to say that the documentation was not of much help to me. There are lots of complicated implementation details but only small examples. So any help is appreciated. How can I solve my problem? Side note: In the following code sample, iterator_adaptor accidentally turns a const_iterator into a non-const iterator. (Seemingly, some bit-level casting is done somewhere). Is this a bug? #include <boost/iterator/iterator_adaptor.hpp> #include <map> template <class Value> class node_iter :public boost::iterator_adaptor<node_iter<Value>, Value> { public: node_iter() : node_iter::iterator_adaptor_(0) {} node_iter(Value p) : node_iter::iterator_adaptor_(p) {} }; int main() { typedef std::map<int, int> mymap_type; mymap_type testmap; node_iter<mymap_type::const_iterator> ni(testmap.begin()); ni->second = 42; //this works, not a const_iterator anymore } ___________________________________________________________________________ Die einen haben es, die anderen werden es! http://my-mail.ch/?redirect=9905 So macht schenken richtig Freude! Schenken und Helfen mit World Vision! http://www.my-mail.ch/?redirect=1958

5 13

Q: W4003 with vc7 boost=1.32 in date_time lib
by Dan Dimerman 02 Dec '04

02 Dec '04

Hello, I just wanted to see if there are others getting this warning in VC7 with Boost 1.32, or it's just me doing something wrong with the #include order or forgetting a #define. The warning reads: C:\Boost\include\boost-1_32\boost\date_time\gregorian\greg_facet.hpp(293) : warning C4003: not enough actual parameters for macro 'max' thanks for any help... Dan --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com) Version: 6.0.802 / Virus Database: 545 - Release Date: 26-Nov-04

7 14

newbie boost sample compile program
by Brian Gaber 01 Dec '04

01 Dec '04

I have installed boost on both Windows and AIX and get the same problem when I try to compile the simple_ls.cpp program that boost provides. In AIX the boost hpp files get installed in /usr/local/include/boost-1_32/boost/... I created /usr/local/include/boost/... with this command: ln -s /usr/local/include/boost-1_32/boost /usr/local/include/boost In Windows the boost hpp files get installed C:\boost-1_32\boost\... In AIX when I try to compile simple_ls.cpp I get the following: "/usr/local/include/boost/filesystem/operations.hpp", line 18.10: 1540-0836 (S) The #include file <boost/filesystem/path.hpp> is not found. "/usr/local/include/boost/filesystem/operations.hpp", line 19.10: 1540-0836 (S) The #include file <boost/shared_ptr.hpp> is not found. "/usr/local/include/boost/filesystem/operations.hpp", line 21.10: 1540-0836 (S) The #include file <boost/iterator.hpp> is not found. "/usr/local/include/boost/filesystem/operations.hpp", line 22.10: 1540-0836 (S) The #include file <boost/cstdint.hpp> is not found. "/usr/local/include/boost/filesystem/operations.hpp", line 27.10: 1540-0836 (S) The #include file <boost/config/abi_prefix.hpp> is not found. "/usr/local/include/boost/filesystem/operations.hpp", line 149.10: 1540-0836 (S) The #include file <boost/config/abi_suffix.hpp> is not found. my simple_ls.cpp currently has the following include statements: #include "/usr/local/include/boost/filesystem/operations.hpp" #include "/usr/local/include/boost/filesystem/path.hpp" #include <iostream> simple_ls.cpp came with the following include statements which generate similar errors to those above: #include "boost/filesystem/operations.hpp" #include "boost/filesystem/path.hpp" #include <iostream> MS Visual C++ 6 generates the following similar error when attempting to compile simple_ls.cpp c:\boost\include\boost-1_32\boost\filesystem\operations.hpp(18) : fatal error C1083: Cannot open include file: 'boost/filesystem/path.hpp': No such file or directory Thanks for any tips.

2 1

Format Library - Asterisk Support
by Barak Simon 01 Dec '04

01 Dec '04

Hi, I have noticed that the format library does not support at present the printf asterisk for providing dynamic width as an extra parameter. Unfortunately my users need to use this widely and I would really hate to revert back to a non-typesafe solution. a. Are there any plans to support it in near future? b. If not, is there an easy way to add that to parsing.hpp, parse_printf_directive method, parse_width & parse_precision sections? currently the asterisk is ignored, and the library throws an exception thinking it has an extra parameter. c. Is there any workaround I miss which may give me the same expected result of providing say "%*s, width, charPtr" ? (I have 'width' and a non-null-terminated char pointer and need to construct the correct string from them without doing unnecessary copying...) Many thanks, Barak ________________________ Barak Simon GED IT Core Platform Deutsche Bank 190 George St. Sydney, 2000 Phone +61 2 925 85070 Fax +61 2 925 95050 -- This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden.

4 5

abort when constructing filesystem::path object
by Richard Wolf 01 Dec '04

01 Dec '04

Hi I'm trying to use the filesystem library, and I get an abort when trying to initialise a path object with a string containing a space. #include <boost/filesystem/path.hpp> #include <iostream> int main() { boost::filesystem::path p1("hello"); std::cout << p1.string(); boost::filesystem::path p2("hello world"); std::cout << p2.string(); } when run, this prints: helloAborted I couldn't find anything saying that the string path constructor can't contain a space. Am I doing something wrong, or is this a bug? Using gcc 3.3.4 on Debian. thanks, Richard

2 2

[Q] Which compiler tool for MSVC 2005 (Beta)
by Michael Peterson 01 Dec '04

01 Dec '04

I have MSVC 2005 (Beta) installed and was wondering with what compiler toolset, if any, should I use to build boost 1_32_0? Also, any advice as to whether I should use Microsoft's stl or the open source version (I have 4.6.2)? Thanks, Michael

4 3

Help: Building Boost with Different Compiler Options
by Paul Dubuc 30 Nov '04

30 Nov '04

I'm trying to build Boost 1.32 on Solaris 8 (SPARC) with GCC 3.3.4. I want to build a 64-bit version of the libraries and this requires pasing the -m64 option to the compiler. How do I tell bjam to do this? I've tried: export TOOLSET_OPT="-sGCC_ROOT_DIRECTORY=${GCCDIR} -exec-prefix=${PWD}/${GCCVERSION}/64 \"\"-sGXX=g++ -m64\"\" \"\"-sGCC=gcc -m64\"\"" ... bjam ${TOOLSET_OPT} \ -sTOOLS=${TOOLSET} \ --prefix=${PWD}/.. \ --with-python-root=/projects/gnu/sparc-sun-solaris8 \ install It dosn't seem to work. I still get 32-bit libraries. Help would be appreciated, Thanks. -- Paul M. Dubuc

4 6

Re: [Boost-users] Errors when playing with lambda (1.32.0, VC7.1)
by John.Wismar＠autozone.com 30 Nov '04

30 Nov '04

"Peter Dimov" <pdimov(a)mmltd.net> wrote: > You are trying to invoke the non-const member > function Foo::print on a const Foo. and > You didn't call the function: (&_1->*&Foo::print)(). Thanks for the reply! Both seem obvious once the errors have been pointed out, but I was not making any headway by reading the error messages (in the first case) or stepping through the code execution (in the second).... I'll keep working with it. Thanks again!! -------------------------------- John Wismar john.wismar(a)autozone.com

1 0

Errors when playing with lambda (1.32.0, VC7.1)
by John.Wismar＠autozone.com 30 Nov '04

30 Nov '04

I'm taking a look at the Lambda library, and writing some toy programs, and I keep coming up with errors, and I can't figure out what the problems are.... Example 1: This works as expected: using namespace boost::lambda; class Foo { public: void print() { std::cout << "Foo::print()\n"; } }; template <class Container, class Function> Function for_all(Container cont, Function f) { return std::for_each(cont.begin(), cont.end(), f); } int main(int argc, char* argv[]) { std::vector<Foo> vec; //Fill vec for_all(vec, (bind(&Foo::print, _1))); return 0; } If I change the declaration of for_all to take the container by const reference, I get errors [See Error 1 pasted in below]: using namespace boost::lambda; class Foo { public: void print() { std::cout << "Foo::print()\n"; } }; template <class Container, class Function> Function for_all(Container const &cont, Function f) { return std::for_each(cont.begin(), cont.end(), f); } int main(int argc, char* argv[]) { std::vector<Foo> vec; //Fill vec for_all(vec, (bind(&Foo::print, _1))); return 0; } Example 2: It looks from the docs like I should be able to rewrite the bind expression above using operator ->*, like so: for_all(vec, (&_1 ->* &Foo::print)); And, in fact this compiles cleanly (regardless of whether the container is passed by value or by const reference). Foo::print() never gets called, though. What am I doing wrong or not understanding here? Thanks in advance!!! -------------------------------- John Wismar john.wismar(a)autozone.com ------------------------------------------------------------------------------------------------------------- [Error 1] c:\dev\alldata\Dev\3rd Party\boost\boost\lambda\detail\actions.hpp(87) : error C2665: 'boost::lambda::function_adaptor<Func>::apply' : none of the 2 overloads can convert parameter 2 from type 'const std::allocator<_Ty>::value_type' with [ Func=boost::lambda::return_type_N<boost::lambda::function_action<2>,boost::lambda::lambda_functor_base<boost::lambda::action<2,boost::lambda::function_action<2>>,boost::tuples::tuple<const boost::lambda::detail::bind_traits<void (__thiscall Foo::* const )(void)>::type,const boost::lambda::detail::bind_traits<const boost::lambda::placeholder1_type>::type,boost::lambda::detail::bind_traits<boost::tuples::null_type>::type,boost::lambda::detail::bind_traits<boost::tuples::null_type>::type,boost::lambda::detail::bind_traits<boost::tuples::null_type>::type,boost::lambda::detail::bind_traits<boost::tuples::null_type>::type,boost::lambda::detail::bind_traits<boost::tuples::null_type>::type,boost::lambda::detail::bind_traits<boost::tuples::null_type>::type,boost::lambda::detail::bind_traits<boost::tuples::null_type>::type,boost::lambda::detail::bind_traits<boost::tuples::null_type>::type>>::sig<boost::tuples::tuple<const std::allocator<Foo>::value_type &,boost::tuples::null_type,boost::tuples::null_type,boost::tuples::null_type,boost::tuples::null_type,boost::tuples::null_type,boost::tuples::null_type,boost::tuples::null_type,boost::tuples::null_type,boost::tuples::null_type>>::rets_t>::plain_Func ] and [ _Ty=Foo ] c:\dev\alldata\Dev\3rd Party\boost\boost\lambda\detail\function_adaptors.hpp(193): could be 'Result boost::lambda::function_adaptor<Func>::apply<RET>(Result (__thiscall Foo::* )(void),Object *)' with [ Result=void, Func=boost::lambda::return_type_N<boost::lambda::function_action<2>,boost::lambda::lambda_functor_base<boost::lambda::action<2,boost::lambda::function_action<2>>,boost::tuples::tuple<const boost::lambda::detail::bind_traits<void (__thiscall Foo::* const )(void)>::type,const boost::lambda::detail::bind_traits<const boost::lambda::placeholder1_type>::type,boost::lambda::detail::bind_traits<boost::tuples::null_type>::type,boost::lambda::detail::bind_traits<boost::tuples::null_type>::type,boost::lambda::detail::bind_traits<boost::tuples::null_type>::type,boost::lambda::detail::bind_traits<boost::tuples::null_type>::type,boost::lambda::detail::bind_traits<boost::tuples::null_type>::type,boost::lambda::detail::bind_traits<boost::tuples::null_type>::type,boost::lambda::detail::bind_traits<boost::tuples::null_type>::type,boost::lambda::detail::bind_traits<boost::tuples::null_type>::type>>::sig<boost::tuples::tuple<const std::allocator<Foo>::value_type &,boost::tuples::null_type,boost::tuples::null_type,boost::tuples::null_type,boost::tuples::null_type,boost::tuples::null_type,boost::tuples::null_type,boost::tuples::null_type,boost::tuples::null_type,boost::tuples::null_type>>::rets_t>::plain_Func , RET=boost::lambda::lambda_functor_base<boost::lambda::action<2,boost::lambda::function_action<2>>,boost::tuples::tuple<const boost::lambda::detail::bind_traits<void (__thiscall Foo::* const )(void)>::type,const boost::lambda::detail::bind_traits<const boost::lambda::placeholder1_type>::type,boost::lambda::detail::bind_traits<boost::tuples::null_type>::type,boost::lambda::detail::bind_traits<boost::tuples::null_type>::type,boost::lambda::detail::bind_traits<boost::tuples::null_type>::type,boost::lambda::detail::bind_traits<boost::tuples::null_type>::type,boo st::lambda::detail::bind_traits<boost::tuples::null_type>::type,boost::lambda::detail::bind_traits<boost::tuples::null_type>::type,boost::lambda::detail::bind_traits<boost::tuples::null_type>::type,boost::lambda::detail::bind_traits<boost::tuples::null_type>::type>>::sig<boost::tuples::tuple<const std::allocator<Foo>::value_type &,boost::tuples::null_type,boost::tuples::null_type,boost::tuples::null_type,boost::tuples::null_type,boost::tuples::null_type,boost::tuples::null_type,boost::tuples::null_type,boost::tuples::null_type,boost::tuples::null_type>>::type, Object=Foo ] c:\dev\alldata\Dev\3rd Party\boost\boost\lambda\detail\function_adaptors.hpp(197): or 'Result boost::lambda::function_adaptor<Func>::apply<RET>(Result (__thiscall Foo::* )(void),Object &)' with [ Result=void, Func=boost::lambda::return_type_N<boost::lambda::function_action<2>,boost::lambda::lambda_functor_base<boost::lambda::action<2,boost::lambda::function_action<2>>,boost::tuples::tuple<const boost::lambda::detail::bind_traits<void (__thiscall Foo::* const )(void)>::type,const boost::lambda::detail::bind_traits<const boost::lambda::placeholder1_type>::type,boost::lambda::detail::bind_traits<boost::tuples::null_type>::type,boost::lambda::detail::bind_traits<boost::tuples::null_type>::type,boost::lambda::detail::bind_traits<boost::tuples::null_type>::type,boost::lambda::detail::bind_traits<boost::tuples::null_type>::type,boost::lambda::detail::bind_traits<boost::tuples::null_type>::type,boost::lambda::detail::bind_traits<boost::tuples::null_type>::type,boost::lambda::detail::bind_traits<boost::tuples::null_type>::type,boost::lambda::detail::bind_traits<boost::tuples::null_type>::type>>::sig<boost::tuples::tuple<const std::allocator<Foo>::value_type &,boost::tuples::null_type,boost::tuples::null_type,boost::tuples::null_type,boost::tuples::null_type,boost::tuples::null_type,boost::tuples::null_type,boost::tuples::null_type,boost::tuples::null_type,boost::tuples::null_type>>::rets_t>::plain_Func , RET=boost::lambda::lambda_functor_base<boost::lambda::action<2,boost::lambda::function_action<2>>,boost::tuples::tuple<const boost::lambda::detail::bind_traits<void (__thiscall Foo::* const )(void)>::type,const boost::lambda::detail::bind_traits<const boost::lambda::placeholder1_type>::type,boost::lambda::detail::bind_traits<boost::tuples::null_type>::type,boost::lambda::detail::bind_traits<boost::tuples::null_type>::type,boost::lambda::detail::bind_traits<boost::tuples::null_type>::type,boost::lambda::detail::bind_traits<boost::tuples::null_type>::type,boo st::lambda::detail::bind_traits<boost::tuples::null_type>::type,boost::lambda::detail::bind_traits<boost::tuples::null_type>::type,boost::lambda::detail::bind_traits<boost::tuples::null_type>::type,boost::lambda::detail::bind_traits<boost::tuples::null_type>::type>>::sig<boost::tuples::tuple<const std::allocator<Foo>::value_type &,boost::tuples::null_type,boost::tuples::null_type,boost::tuples::null_type,boost::tuples::null_type,boost::tuples::null_type,boost::tuples::null_type,boost::tuples::null_type,boost::tuples::null_type,boost::tuples::null_type>>::type, Object=Foo ] while trying to match the argument list '(const rt0 , const std::allocator<_Ty>::value_type)' with [ _Ty=Foo ] c:\dev\alldata\Dev\3rd Party\boost\boost\lambda\detail\lambda_functor_base.hpp(408) : see reference to function template instantiation 'RET boost::lambda::function_action<I>::apply<RET,U,const Foo>(A1 & ,A2 &)' being compiled with [ RET=boost::lambda::lambda_functor_base<boost::lambda::action<2,boost::lambda::function_action<2>>,boost::tuples::tuple<const boost::lambda::detail::bind_traits<void (__thiscall Foo::* const )(void)>::type,const boost::lambda::detail::bind_traits<const boost::lambda::placeholder1_type>::type,boost::lambda::detail::bind_traits<boost::tuples::null_type>::type,boost::lambda::detail::bind_traits<boost::tuples::null_type>::type,boost::lambda::detail::bind_traits<boost::tuples::null_type>::type,boost::lambda::detail::bind_traits<boost::tuples::null_type>::type,boost::lambda::detail::bind_traits<boost::tuples::null_type>::type,boost::lambda::detail::bind_traits<boost::tuples::null_type>::type,boost::lambda::detail::bind_traits<boost::tuples::null_type>::type,boost::lambda::detail::bind_traits<boost::tuples::null_type>::type>>::sig<boost::tuples::tuple<const std::allocator<Foo>::value_type &,boost::tuples::null_type,boost::tuples::null_type,boost::tuples::null_type,boost::tuples::null_type,boost::tuples::null_type,boost::tuples::null_type,boost::tuples::null_type,boost::tuples::null_type,boost::tuples::null_type>>::type, I=2, U=const rt0, A1=const rt0, A2=const std::allocator<Foo>::value_type ] c:\dev\alldata\Dev\3rd Party\boost\boost\lambda\detail\lambda_functors.hpp(148) : see reference to function template instantiation 'RET boost::lambda::lambda_functor_base<Act,Args>::call<boost::lambda::lambda_functor_base<Act,Args>::sig<SigArgs>::type,A,const boost::tuples::null_type,const boost::tuples::null_type,const boost::tuples::null_type>(A &,B &,C &,Env &) const' being compiled with [ RET=boost::lambda::lambda_functor_base<boost::lambda::action<2,boost::lambda::function_action<2>>,boost::tuples::tuple<const boost::lambda::detail::bind_traits<void (__thiscall Foo::* const )(void)>::type,const boost::lambda::detail::bind_traits<const boost::lambda::placeholder1_type>::type,boost::lambda::detail::bind_traits<boost::tuples::null_type>::type,boost::lambda::detail::bind_traits<boost::tuples::null_type>::type,boost::lambda::detail::bind_traits<boost::tuples::null_type>::type,boost::lambda::detail::bind_traits<boost::tuples::null_type>::type,boost::lambda::detail::bind_traits<boost::tuples::null_type>::type,boost::lambda::detail::bind_traits<boost::tuples::null_type>::type,boost::lambda::detail::bind_traits<boost::tuples::null_type>::type,boost::lambda::detail::bind_traits<boost::tuples::null_type>::type>>::sig<boost::tuples::tuple<const std::allocator<Foo>::value_type &,boost::tuples::null_type,boost::tuples::null_type,boost::tuples::null_type,boost::tuples::null_type,boost::tuples::null_type,boost::tuples::null_type,boost::tuples::null_type,boost::tuples::null_type,boost::tuples::null_type>>::type, Act=boost::lambda::action<2,boost::lambda::function_action<2>>, Args=boost::tuples::tuple<const boost::lambda::detail::bind_traits<void (__thiscall Foo::* const )(void)>::type,const boost::lambda::detail::bind_traits<const boost::lambda::placeholder1_type>::type,boost::lambda::detail::bind_traits<boost::tuples::null_type>::type,boost::lambda::detail::bind_traits<boost::tuples::null_type>::type,boost::lambda::detail::bind_traits<boost::tuples::null_type>::typ e,boost::lambda::detail::bind_traits<boost::tuples::null_type>::type,boost::lambda::detail::bind_traits<boost::tuples::null_type>::type,boost::lambda::detail::bind_traits<boost::tuples::null_type>::type,boost::lambda::detail::bind_traits<boost::tuples::null_type>::type,boost::lambda::detail::bind_traits<boost::tuples::null_type>::type>, SigArgs=boost::tuples::tuple<const std::allocator<Foo>::value_type &,boost::tuples::null_type,boost::tuples::null_type,boost::tuples::null_type,boost::tuples::null_type,boost::tuples::null_type,boost::tuples::null_type,boost::tuples::null_type,boost::tuples::null_type,boost::tuples::null_type>, A=const std::allocator<Foo>::value_type, B=const boost::tuples::null_type, C=const boost::tuples::null_type, Env=const boost::tuples::null_type ] c:\DevTools\VS.NET2003\Vc7\include\algorithm(21) : see reference to function template instantiation 'boost::lambda::lambda_functor_base<Act,Args>::sig<SigArgs>::type boost::lambda::lambda_functor<T>::operator ()<const std::allocator<_Ty>::value_type>(A &) const' being compiled with [ Act=boost::lambda::action<2,boost::lambda::function_action<2>>, Args=boost::tuples::tuple<const boost::lambda::detail::bind_traits<void (__thiscall Foo::* const )(void)>::type,const boost::lambda::detail::bind_traits<const boost::lambda::placeholder1_type>::type,boost::lambda::detail::bind_traits<boost::tuples::null_type>::type,boost::lambda::detail::bind_traits<boost::tuples::null_type>::type,boost::lambda::detail::bind_traits<boost::tuples::null_type>::type,boost::lambda::detail::bind_traits<boost::tuples::null_type>::type,boost::lambda::detail::bind_traits<boost::tuples::null_type>::type,boost::lambda::detail::bind_traits<boost::tuples::null_type>::type,boost::lambda::detail::bind_traits<boost::tuples::null_type>::type,boost::lambda::detail::bind_traits<boost::tuples::null_type>::type>, SigArgs=boost::tuples::tuple<const std::allocator<Foo>::value_type &,boost::tuples::null_type,boost::tuples::null_type,boost::tuples::null_type,boost::tuples::null_type,boost::tuples::null_type,boost::tuples::null_type,boost::tuples::null_type,boost::tuples::null_type,boost::tuples::null_type>, T=boost::lambda::lambda_functor_base<boost::lambda::action<2,boost::lambda::function_action<2>>,boost::tuples::tuple<const boost::lambda::detail::bind_traits<void (__thiscall Foo::* const )(void)>::type,const boost::lambda::detail::bind_traits<const boost::lambda::placeholder1_type>::type,boost::lambda::detail::bind_traits<boost::tuples::null_type>::type,boost::lambda::detail::bind_traits<boost::tuples::null_type>::type,boost::lambda::detail::bind_traits<boost::tuples::null_type>::type,boost::lambda::detail::bind_traits<boost::tuples::null_type>::type,boost::lambda::detail::bind_traits<b oost::tuples::null_type>::type,boost::lambda::detail::bind_traits<boost::tuples::null_type>::type,boost::lambda::detail::bind_traits<boost::tuples::null_type>::type,boost::lambda::detail::bind_traits<boost::tuples::null_type>::type>>, _Ty=Foo, A=const std::allocator<Foo>::value_type ] c:\Temp\LambdaTest\LambdaTest.cpp(29) : see reference to function template instantiation '_Fn1 std::for_each<std::vector<_Ty>::const_iterator,Function>(_InIt,_InIt,_Fn1)' being compiled with [ _Fn1=boost::lambda::lambda_functor<boost::lambda::lambda_functor_base<boost::lambda::action<2,boost::lambda::function_action<2>>,boost::tuples::tuple<const boost::lambda::detail::bind_traits<void (__thiscall Foo::* const )(void)>::type,const boost::lambda::detail::bind_traits<const boost::lambda::placeholder1_type>::type,boost::lambda::detail::bind_traits<boost::tuples::null_type>::type,boost::lambda::detail::bind_traits<boost::tuples::null_type>::type,boost::lambda::detail::bind_traits<boost::tuples::null_type>::type,boost::lambda::detail::bind_traits<boost::tuples::null_type>::type,boost::lambda::detail::bind_traits<boost::tuples::null_type>::type,boost::lambda::detail::bind_traits<boost::tuples::null_type>::type,boost::lambda::detail::bind_traits<boost::tuples::null_type>::type,boost::lambda::detail::bind_traits<boost::tuples::null_type>::type>>>, _Ty=Foo, Function=boost::lambda::lambda_functor<boost::lambda::lambda_functor_base<boost::lambda::action<2,boost::lambda::function_action<2>>,boost::tuples::tuple<const boost::lambda::detail::bind_traits<void (__thiscall Foo::* const )(void)>::type,const boost::lambda::detail::bind_traits<const boost::lambda::placeholder1_type>::type,boost::lambda::detail::bind_traits<boost::tuples::null_type>::type,boost::lambda::detail::bind_traits<boost::tuples::null_type>::type,boost::lambda::detail::bind_traits<boost::tuples::null_type>::type,boost::lambda::detail::bind_traits<boost::tuples::null_type>::type,boost::lambda::detail::bind_traits<boost::tuples::null_type>::type,boost::lambda::detail::bind_traits<boost::tuples::null_type>::type,boost::lambda::detail::bind_traits<boost::tuples::null_type>::type,boost::lambda::detail::bind_traits<boost::tuples::null_type>::type>>>, _InIt=std::vector<Foo>::const_iterator ] c:\Temp\LambdaTest\LambdaTest.cpp(35) : see reference to function template instantiation 'Function for_all<std::vector<_Ty>,boost::lambda::lambda_functor<T>>(const Container &,Function)' being compiled with [ Function=boost::lambda::lambda_functor<boost::lambda::lambda_functor_base<boost::lambda::action<2,boost::lambda::function_action<2>>,boost::tuples::tuple<const boost::lambda::detail::bind_traits<void (__thiscall Foo::* const )(void)>::type,const boost::lambda::detail::bind_traits<const boost::lambda::placeholder1_type>::type,boost::lambda::detail::bind_traits<boost::tuples::null_type>::type,boost::lambda::detail::bind_traits<boost::tuples::null_type>::type,boost::lambda::detail::bind_traits<boost::tuples::null_type>::type,boost::lambda::detail::bind_traits<boost::tuples::null_type>::type,boost::lambda::detail::bind_traits<boost::tuples::null_type>::type,boost::lambda::detail::bind_traits<boost::tuples::null_type>::type,boost::lambda::detail::bind_traits<boost::tuples::null_type>::type,boost::lambda::detail::bind_traits<boost::tuples::null_type>::type>>>, _Ty=Foo, T=boost::lambda::lambda_functor_base<boost::lambda::action<2,boost::lambda::function_action<2>>,boost::tuples::tuple<const boost::lambda::detail::bind_traits<void (__thiscall Foo::* const )(void)>::type,const boost::lambda::detail::bind_traits<const boost::lambda::placeholder1_type>::type,boost::lambda::detail::bind_traits<boost::tuples::null_type>::type,boost::lambda::detail::bind_traits<boost::tuples::null_type>::type,boost::lambda::detail::bind_traits<boost::tuples::null_type>::type,boost::lambda::detail::bind_traits<boost::tuples::null_type>::type,boost::lambda::detail::bind_traits<boost::tuples::null_type>::type,boost::lambda::detail::bind_traits<boost::tuples::null_type>::type,boost::lambda::detail::bind_traits<boost::tuples::null_type>::type,boost::lambda::detail::bind_traits<boost::tuples::null_type>::type>>, Container=std::vector<Foo> ]

3 2

Help with serializating an abstract object
by Jeffrey Holle 30 Nov '04

30 Nov '04

I'm running into trouble handling an abstract object in my attempt to apply boost.serialization to my application. Since it doesn't have state, initially I didn't add serialize methods to this class, and got compilization errors for want of these methods. Next, I added noop methods, and got errors because the serialization package attempted to construct an abstract class. I see there is an is_abstract template, but don't know how to employ it. Can somebody give me some pointers? Note that I've choosen to implement non-templated serialize methods, using a forwared reference of the desired archive classes. Should this template be in the definition file, or implementation file (inside or outside the serialize method(s))?

2 1

Problem with including boost/serialization/shared_ptr.hpp
by Jeffrey Holle 29 Nov '04

29 Nov '04

I'm attempting to apply the boost::serialization library to my application. Because it is fairly large, I've choosing to implement the serialize methods as non-templates. Such a tactic is used in some of the examples, for instance demo_polymorphic_A.hpp. This means that I don't include any boost.serialization or boost.archive headers in my definition files. A forward reference to the specific archive object is made instead. I've run into trouble with an object wrapped in a shared_pointer. To solve this, I've attempted to defined the BOOST_SHARED_POINTER_EXPORT() macro in this object's definition file. This necessitates including boost/serialization/shared_ptr.hpp. The problem is no matter what position I place this include file in this *.h file, I get the following error. boost/serialization/shared_ptr.hpp:26:2: #error "include <boost/serialization/shared_ptr> first This is a self reference, what is it trying to say? In other words, what do I have to include before boost/serialization/shared_ptr.hpp to make it happy?

4 3

howto store vertex-iterators as internal graph property?
by Sebastian Weber 29 Nov '04

29 Nov '04

Hi folks! I got a cyclic type-dependency problem. I am trying to let every vertex store a iterator to a list which stores vertex-iterators. This sounds weired, but I need to keep track of very few vertices within my graph which have a particle located at it. Thus I created a list of vertex-iterators who carry my particle positions in the graph. In order to be able to tell quickly if a vertice is taken by a particle I want each vertice to include a pointer to a null element representing the absence of a particle or a pointer into that list. My non-working code looks like: Definition of my graph: struct Spot { // acutally I need the vertex_iterator to be defined already // in order to define particle, but this is not yet defined // so I am using the knowledge that it is going to be represented // by a vector<std::size_t>::iterator (at least I hope so) // this assumption is WRONG!! typedef std::list< std::vector<std::size_t>::iterator >::iterator \\ particle_t; particle_t particle; }; typedef boost::adjacency_list<boost::vecS, boost::vecS, \\ boost::undirectedS, Spot > graph_t; Here I initialise my particles to be distributed in the graph object bg. m_posA is of type: std::list<RandomGraph::gtraits::vertex_iterator> // first initialise every position to the null-flag for(; vi != vend; ++vi) bg[*vi].particle = Spot::particle_t(); // now place particles at random positions boost::tie(vi, vend) = boost::vertices(bg); for(std::size_t i = 0; i < initialA; i++) { std::size_t pos; //aList_t::iterator iter; // find a random empty vertice do { pos = rand_gen(); } while(bg[pos].particle != m_posA_end); // place particle A there RandomGraph::gtraits::vertex_iterator vref = vi + pos; // put returns an iterator to the list-element where // vref has been stored bg[pos].particle = m_posA.put(vref); } Any help would be great. Thanks in adavance. Greetings, Sebastian Weber

6 6

[OSX] Multiply defined symbols between Function and Signals libs ?
by Alo Sarv 29 Nov '04

29 Nov '04

Hi I'v been compiling boost libraries objects straight into my application binaries on linux and OSX platforms (e.g. not using bjam/stat/dynlibs), and thus far it has worked. However, recently I started getting multiply defined symbols on OSX, namely _1, _2, _3 etc. Most likely they come between Boost.Function and Boost.Signals libraries (latter of which I started using recently). My question is is it inherently bad idea to compile boost objects like this straight into application binary (e.g. should I always use bjam?), or there any other workarounds to avoid those multiple symbols on OSX ? Alo Sarv.

2 2

Re: Re: Graph library - bundled properties for edge
by TC MA 29 Nov '04

29 Nov '04

Thank you for your answer. I don't know '*first' will give an edge_description already. > TC MA wrote: > > > G[source(*first, G)].y << " joins " << > > G[target(*first, G)].x << "," << G[target(*first, > > G)].y << " weight " << G[edge(*first)].weight << endl; > > ++first; > > What's the 'edge' function and why do you call it? What about just '*first', > which gives you an edge_description already? > > - Volodya ===== TingChong Ma ______________________________________________________________________ Post your free ad now! http://personals.yahoo.ca

1 0

Re: Re: Re: Leak when using boost threads under VC .NET using usi ng statically linked CRT
by alansa＠ati-uk.com 29 Nov '04

29 Nov '04

-----Original Message----- From: Alan Saunders Sent: 22 November 2004 17:24 To: 'boost-users(a)lists.boost.org' Subject: >> Hmmm no linker errors or warnings. I've set my main exe to statically >> link. if i use the version of threads that statically links to >> msvcrt71 or dynamically to msvcrt71.dll it doesn't seem to make any >> difference. Our boost libraries where compiled here for msvcrt71 and i >> can confirm this. >> >> As i say if my main exe uses msvcrt71.dll then theres no leak. >Are you using tls code? >TLS currently (as to my knowledge) contains a "intentional" leak which >however is harmless. >Could you post the messages? >Did you track down the leak? Hi Roland In order to clear random influences from other areas of the software i'm working on, I have created a simple program with the code that i listed before. nothing else, no tls code. The intentinal leak would be harmless if it did not keep increasing. If I let the program run for long enough i will run out of memory. Sorry which messages would you like me to post? Haven't tracked down the leak yet. My problem is solved for the time being by using msvcrt71.dll as i said before. However it would be nice to be able to using the static lib. I replace the code in the loop which constantly starts and stop threads with my own code that did the same thing. This code was pretty much the same as the code for boost::thread using the windows api functions. This did not leak. However the big difference between my code and boost::thread is that my code didn't use boost::function. Therefore I suspect the leak could be in there! Looking at function it certainly isn't as trivial as thread. One thing i have noticed is that there is an option to get function to use "new" instead of std::allocator with the macro BOOST_NO_STD_ALLOCATOR. (function_template.hpp). I haven't got round to trying this yet though. Alan

4 4

accessing internal graph properties via vertex-iterators directly?
by Sebastian Weber 29 Nov '04

29 Nov '04

Hello there! First of all thanks a lot for the rapid response of my last question. I got another question concerning the access of internal graph properties: To access a bundeled vertice internal properties of a graph one has to use the following syntax: struct VertStruct { int stuff; }; typedef adjacency_list<vecS, vecS, undirectedS, VertStruct> graph_t; graph_t bg; ... setup graph ... graph_traits<graph_t>::vertex_iterator vi, vend; tie(vi, vend) = vertices(bg); bg[*vi].stuff = 4; This makes it clear, that even though we already have an iterator (vi) pointing to our vertice of interest, the BGL has to spend again some time locating the data ascociated with it. A far more direct and much clearer notion would be: (*vi).stuff = 4; With this, one would save a lookup in the data-structures and the vertice-iterator concept would be far more logic to me, concernig internal property handling. I don't know the BGL internals and how this behaviour is optimally programmed with the BGL. I thought of providing a custom container for the vertex-container which is composed of a vector of a customary struct, which glues vertice properties together with every element of the vertice list and makes the property really internal, allowing a (*vi).myrealinternalstuff = 4 expression. I hope my point is clear. Thanks a lot for any help. Greetings, Sebastian Weber

2 2

Graph library - bundled properties for edge
by TC MA 29 Nov '04

29 Nov '04

I try to add Vertex and Edge data with bundled properties. I am modifying the sample program interior_property_map.cpp to learn how to access the bundled properties, but I don't know how to fix my compile error. What is the right way to access the bundled properties for edge? Source code is: #include <boost/config.hpp> #include <iostream> #include <algorithm> #include <boost/graph/adjacency_list.hpp> #include <boost/property_map.hpp> using namespace std; using namespace boost; struct VertexData { int x; int y; }; struct EdgeData { int weight; }; template <class EdgeIter, class Graph> void who_owes_who(EdgeIter first, EdgeIter last, const Graph& G) { // Access the propety acessor type for this graph while (first != last) { // fail to compile here!!! cout << G[source(*first, G)].x << "," << G[source(*first, G)].y << " joins " << G[target(*first, G)].x << "," << G[target(*first, G)].y << " weight " << G[edge(*first)].weight << endl; ++first; } } int main() { // Create the graph, and specify that we will use store the data. typedef adjacency_list<vecS, vecS, directedS, VertexData, EdgeData> MyGraphType; typedef pair<int, int> Pair; // from <utility> Pair edge_array[11] = { Pair(0,1), Pair(0,2), Pair(0,3), Pair(0,4), Pair(2,0), Pair(3,0), Pair(2,4), Pair(3,1), Pair(3,4), Pair(4,0), Pair(4,1) }; MyGraphType G(5); for (int i=0; i<11; ++i) add_edge(edge_array[i].first, edge_array[i].second, G); G[0].x = 0; G[0].y = 0; G[1].x = 1; G[1].y = 1; G[2].x = 2; G[2].y = 2; G[3].x = 3; G[3].y = 3; G[4].x = 4; G[4].y = 4; // store weights in edges graph_traits <MyGraphType>::edge_iterator ei, eend; int i = 0; for (tie(ei, eend) = edges(G); ei != eend; ++ei) { G[*ei].weight = i++; cout << "G[e] weight " << G[*ei].weight << endl; } who_owes_who(edges(G).first, edges(G).second, G); cout << endl; return 0; } Compile error is: gcc-C++-action /home/tcma/cpp/boosttcma/libs/graph/interior_property_map.test/gcc/debug/inlining-on/interior_property_map.o /home/tcma/cpp/boosttcma/libs/graph/interior_property_map.cpp: In function `void who_owes_who(EdgeIter, EdgeIter, const Graph&) [with EdgeIter = boost::detail::adj_list_edge_iterator<boost::counting_iterator<size_t, boost::use_default, boost::use_default>, boost::detail::out_edge_iter<__gnu_cxx::__normal_iterator<boost::detail::sep_<size_t, boost::property<boost::edge_bundle_t, EdgeData, boost::no_property> >*, std::vector<boost::detail::sep_<size_t, boost::property<boost::edge_bundle_t, EdgeData, boost::no_property> >, std::allocator<boost::detail::sep_<size_t, boost::property<boost::edge_bundle_t, EdgeData, boost::no_property> > > > >, size_t, boost::detail::edge_desc_impl<boost::directed_tag, size_t>, ptrdiff_t>, boost::adjacency_list<boost::vecS, boost::vecS, boost::directedS, VertexData, EdgeData, boost::no_property, boost::listS> >, Graph = main()::MyGraphType]': /home/tcma/cpp/boosttcma/libs/graph/interior_property_map.cpp:113: instantiated from here /home/tcma/cpp/boosttcma/libs/graph/interior_property_map.cpp:64: error: no matching function for call to `edge(boost::detail::edge_desc_impl<boost::directed_tag, size_t>)' set -e "g++" -c -Wall -ftemplate-depth-255 -g -O0 -Wno-inline -I"../../../bin/boost/libs/graph/example" -I "/home/tcma/cpp/boost_1_32_0" -o "/home/tcma/cpp/boosttcma/libs/graph/interior_property_map.test/gcc/debug/inlining-on/interior_property_map.o" "/home/tcma/cpp/boosttcma/libs/graph/interior_property_map.cpp" "/usr/bin/objcopy" --set-section-flags .debug_str=contents,debug "/home/tcma/cpp/boosttcma/libs/graph/interior_property_map.test/gcc/debug/inlining-on/interior_property_map.o" ... ===== TingChong Ma ______________________________________________________________________ Post your free ad now! http://personals.yahoo.ca

2 1

RE: Problem with graph:johnson_all_pairs_shortest_paths
by keith.briggs＠bt.com 29 Nov '04

29 Nov '04

>So, you get a code like: const int V = n; int D[V][V]; In this case, 'V' is not a compile time constant and the second line >is not valid -- array bounds must be compile time constant. I have no idea why you get the error you get, instead of >error right at the point where array is declared. Most likely, this is diagnostic problem in the rather ancient (;-)) version of >gcc that you're using. Ok, so what's the right say to do this kind of dynamically-sized problem? Keith

2 1

Problem with graph:johnson_all_pairs_shortest_paths
by keith.briggs＠bt.com 29 Nov '04

29 Nov '04

I am using g++ 3.2 on a redhat linux system. I took the johnson_all_pairs_shortest_paths example, (http://www.boost.org/libs/graph/example/johnson-eg.cpp) which works fine, but then changed const int V = 5; to const int V = n; where n has been computed at runtime. This should not change the type of V or D, but I now get the error below. Can anyone explain how to fix this? Thanks, Keith > /usr/bin/g++ -I ~/boost_1_32_0/ graph_stats.cc graph_stats.cc: In function `int main()': graph_stats.cc:46: no matching function for call to ` johnson_all_pairs_shortest_paths(main()::Graph&, int[V][V], boost::bgl_named_params<int*, boost::vertex_distance_t, boost::no_property> )'

2 1