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

Re: Newbie using regex libraries (John Maddock)
by Mark Helzer 05 Dec '04

05 Dec '04

----------------------------- Message: 3 Date: Fri, 3 Dec 2004 10:57:05 -0000 From: "John Maddock" <john(a)johnmaddock.co.uk> Subject: Re: [Boost-users] Newbie using regex libraries To: <boost-users(a)lists.boost.org> Message-ID: <01c301c4d927$1a2b6520$03800252@fuji> Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original > In developing a very simple test, I ran into an issue with the library. > I linked with libboost_regex-gcc.so and ran into a relocation run time > error -- undefined symbol: __dso_handle. > > I found the symbol in libboost_regex-gcc-mt-d-1_31.so.1.31.0. I linked > with that and my test works. > > So, it seems odd that I would not use one of the more generic library > names (ending in .so). Is this perhaps a configuration issue on my > part? Those two libs should be the same thing, in fact I think one should be a link to the other shouldn't it? No, they are not. Although that is what I would have expected... -rwxr-xr-x 1 eoapi clients 4976367 Apr 22 2004 libboost_regex-gcc-mt-d-1_31.so.1.31.0 -rwxr-xr-x 1 root root 629005 Jun 29 06:16 libboost_regex-gcc.so I shall clean it up and try rebuilding John.

2 1

Problems serializing via pointers
by Jeffrey Holle 04 Dec '04

04 Dec '04

At this point, the last compilation problem in applying the boost.serialization library to my application has to do with pointers. Specifically, its pointers to std::string and char member attributes. I have other pointer member attributes that compile successfully, but this point to objects that have serialize methods. I have attempted use of register_type and am including "serialization/string.hpp" in the modules that have pointer to string attributes. These actions were not affective. As an example of the type of compilation error, when I uncomment the following attribute's archive attempt: char *m_pByPointerPrefix; I get: /home/jholle/boost_1_32_0/boost/serialization/access.hpp: In static member function `static void boost::serialization::access::serialize(Archive&, T&, unsigned int) [with Archive = boost::archive::binary_iarchive, T = char]': /home/jholle/boost_1_32_0/boost/serialization/serialization.hpp:78: instantiated from `void boost::serialization::serialize(Archive&, T&, unsigned int) [with Archive = boost::archive::binary_iarchive, T = char]' /home/jholle/boost_1_32_0/boost/serialization/serialization.hpp:121: instantiated from `void boost::serialization::serialize_adl(Archive&, T&, unsigned int) [with Archive = boost::archive::binary_iarchive, T = char]' /home/jholle/boost_1_32_0/boost/archive/detail/iserializer.hpp:155: instantiated from `void boost::archive::detail::iserializer<Archive, T>::load_object_data(boost::archive::detail::basic_iarchive&, void*, unsigned int) const [with Archive = boost::archive::binary_iarchive, T = char]' VariableName.cpp:102: instantiated from here /home/jholle/boost_1_32_0/boost/serialization/access.hpp:106: error: request for member `serialize' in `t', which is of non-class type `char' What is the solution to this?

3 8

Pool allocating
by jec＠rptec.ch 04 Dec '04

04 Dec '04

Hi, I need the following for our Linux C++ soft: - Create a HeapSpace of FixedSize (say 1Mb) - Allocate FixedSize piece of memory (always alloc 16 bytes from this heap for ex.) - Return NULL if no more space in the HeapSpace - Delete them. - Release the memory when all pieces are deleted Is there a way to do exactly that with Boost? Thanks. -jec

1 0

Boost replace - a trailing 0
by Leon Mergen 03 Dec '04

03 Dec '04

Hello, I'm trying to use boost regex'es replace and add a trailing 0 after the \1 part. However, it seems to want to replace this with \10, which is not what I want. Anyone has any idea how to do this in a proper way ? Thanks in advance! Regards, Leon Mergen

2 2

Newbie using regex libraries
by Mark Helzer 03 Dec '04

03 Dec '04

Hi, In developing a very simple test, I ran into an issue with the library. I linked with libboost_regex-gcc.so and ran into a relocation run time error -- undefined symbol: __dso_handle. I found the symbol in libboost_regex-gcc-mt-d-1_31.so.1.31.0. I linked with that and my test works. So, it seems odd that I would not use one of the more generic library names (ending in .so). Is this perhaps a configuration issue on my part? Mark Helzer ADP Dealer Services 2525 S.W 1st Portland, OR. (503) 402-3481

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

Re: newbie boost sample compile program
by Brian Gaber 02 Dec '04

02 Dec '04

Martin Lemieux <lemieux<at>cae.com> writes: 1) You describe to much path information in the #include directive in simple_ls.cpp . Like the Boost's .hpp, just start with "boost/(...).hpp". I fixed the path information in the #include directive to be "boost/filesystem/... 2) Then make sure your compiler command line at least mention "-I /user/local/include" or "-I $(INC)" where INC ~includes~ "/user/local/include". I get further, here is the new AIX compiler error: xlc++ -o simple_ls simple_ls.cpp -I /usr/local/include ld: 0711-317 ERROR: Undefined symbol: .boost::filesystem::initial_path() ld: 0711-317 ERROR: Undefined symbol: boost::filesystem::native(const std::basic_string<char,std::char_traits<char>,std::allocator<char> >&) ld: 0711-317 ERROR: Undefined symbol: .boost::filesystem::path::path(const char*,bool(*)(const std::basic_string<char,std::char_traits<char>,std::allocator<char> >&)) ld: 0711-317 ERROR: Undefined symbol: .boost::filesystem::system_complete(const boost::filesystem::path&) ld: 0711-317 ERROR: Undefined symbol: .boost::filesystem::exists(const boost::filesystem::path&) ld: 0711-317 ERROR: Undefined symbol: .boost::filesystem::path::native_file_string() const ld: 0711-317 ERROR: Undefined symbol: .boost::filesystem::is_directory(const boost::filesystem::path&) ld: 0711-317 ERROR: Undefined symbol: .boost::filesystem::path::native_directory_string() const ld: 0711-317 ERROR: Undefined symbol: .boost::filesystem::path::leaf() const ld: 0711-317 ERROR: Undefined symbol: .boost::filesystem::detail::dir_itr_init(boost::shared_ptr<boost::filesystem::detail::dir_itr_imp>&,const boost::filesystem::path&) ld: 0711-317 ERROR: Undefined symbol: .boost::filesystem::detail::dir_itr_dereference(const boost::shared_ptr<boost::filesystem::detail::dir_itr_imp>&) ld: 0711-317 ERROR: Undefined symbol: .boost::filesystem::detail::dir_itr_increment(boost::shared_ptr<boost::filesystem::detail::dir_itr_imp>&) ld: 0711-345 Use the -bloadmap or -bnoquiet option to obtain more information. 2a) On AIX, look inside your makefile. What am I looking for? > [...] 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 2b) On MSDEV6, add "c:\boost\include\boost-1_32" in your project settings. More specifically in the "C++" tab, under "Preprocessor" category (drop-down list), and at "Additional include directories:". I did this and I can now build, but I get a linker error: LINK : fatal error LNK1104: cannot open file "libboost_filesystem-vc6-sgd-1_32.lib" Thanks.

2 1

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

GCC and precompiling headers containing anonymous namspaces (i.e. bind/placeholders.hpp)
by Matthew Gruenke 02 Dec '04

02 Dec '04

Like a number of other compilers, GCC (version 3.4.3) appears to have problems related to precompiled headers that contain anonymous namespaces - such as the one in bind/placeholders.hpp. There appears to be some consensus that GCC currently does have issues in this area (see http://gcc.gnu.org/bugzilla/show_bug.cgi?id=10591) I noticed the workarounds in bind/placeholders.hpp (Boost version 1.32.0) for other compilers, and tried them with the above version of GCC. I discovered that only the work-around using static inline wrapper functions (i.e. the one for Borland compilers) seems to work. Can anyone confirm this? Should I file a bug to have that workaround apply for GCC, as well? Are anonymous/unnamed namespaces used in any other BOOST headers (which should presumably also have the workaround)? Matt Gruenke Software Engineer IntelliVid Corporation

1 0

boost::lambda without 'use namespace'
by Agoston Bejo 01 Dec '04

01 Dec '04

Hi all, is there a way to use the boost::lambda library without having to use boost::lambda; ? I would like to use lambda expressions in a header file, therefore without 'use'-ing the namespace. Thx, Agoston

2 1

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

FStream compile problem in VC6
by Adam 01 Dec '04

01 Dec '04

Hi, I'm trying to compile the following in Visual C++6.0 #include "boost/config.hpp" #include "boost/filesystem/operations.hpp" // includes boost/filesystem/path.hpp #include "boost/filesystem/fstream.hpp" // ditto #include <iostream> // for std::cout using namespace boost::filesystem; int main(int argc, char* argv[]) { remove_all( "foobar" ); create_directory( "foobar" ); boost::filesystem::ofstream file( "foobar/cheeze" ); file << "tastes good!\n"; file.close(); if ( !exists( "foobar/cheeze" ) ) std::cout << "Something is rotten in foobar\n"; return 0; } and I keep getting an error saying that c:\program files\microsoft visual studio\vc98\include\boost\filesystem\fstream.hpp(95) : error C2504: 'basic_ofstream<char,struct std::char_traits<char> >' : base class undefined C:\Program Files\Microsoft Visual Studio\MyProjects\boost_filesystem\boost_filesystem.cpp(17) : see reference to class template instantiation 'boost::filesystem::basic_ofstream<char,struct std::char_traits<char> >' being compiled which I think means that it can't find the implementation for std::basic_ofstream<charT,traits> . I'm not sure how to get around this because I can define a std::basic_ofstream, without problem. Thanks for help, Adam

1 0

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

Q: VC7 boost1.32 date_time\time_system_counted.hpp(57) : warning C4244: 'initializing'
by Dan Dimerman 01 Dec '04

01 Dec '04

Hello, >From the department of unexplained warnings... I found this one which I hope someone out there could help me kill. The warning reads: C:\Boost\include\boost-1_32\boost\date_time\time_system_counted.hpp(57) : warning C4244: 'initializing' : conversion from 'boost::date_time::counted_time_rep<config>::int_type' to 'boost::date_time::gregorian_calendar_base<ymd_type_,date_int_type_>::date_int_type', possible loss of data What can I do to get rid of this one? many thanks Dan --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com) Version: 6.0.803 / Virus Database: 546 - Release Date: 30-Nov-04

2 1

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