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

Re: [Boost-users] [serialization] [wave] [spirit] Can't compile b oost cvs
by James Hughes 12 Jan '06

12 Jan '06

> -----Original Message----- > From: Peter Whaite [mailto:boost@whaite.ca] > Sent: 11 January 2006 17:49 > To: boost-users(a)lists.boost.org > Subject: Re: [Boost-users] [serialization] [wave] [spirit] > Can't compile > boost cvs > > > Joel de Guzman <joel(a)boost-consulting.com> wrote: > > > > Ok, confirmed. I'm the culprit :( Someone submitted a patch > > for the is* functions to work on other POD types. Hartmut is > > reverting it now while I try to find a fix. > > OK thanks it compiles now. > > I'm still surprised this wasn't reported earlier as > serialization seems > to be one of the more popular libs. > With reference to this fix, where can I get it or should I revert to 1.33.0 rather than 1.33.1 which I currently have? Rgds James

2 1

Re: [Boost-users] Cross compiling boost libraries with gcc and using boost jam to crosscompile third-party library (Jambase problem)
by Stering Wolfram 12 Jan '06

12 Jan '06

Vladimir, >recently I was put into task to cross compile boost for ARM platform >with GCC. > >My building platform is i386 Linux with gcc and cross compiling to arm >Linux. > > I had the very same problem for my Coldfire cross-build (target "m68k-elf"), working under Windows XP using Cygwin. I didn't find a "standard way" of doing a cross-build of boost in its build documentation. >Standard way for this kind of compilation is, that name of cross >compiler (running under i386 but producing arm code) and all cross >binary utilities are prefixed by target plarform, so like arm-linux-gcc, >arm-linux-g++, arm-linux-ar, arm-linux-objcopy for arm-linux. > > This applies when using the GNU toolchain. But nowadays, most cross compilers are gcc based. >And this is causing a bit of problem with boost. > >I can force GCC and GXX, but still have a problem with ar and objcopy. > >I've tried to setup GCC_BIN_DIRECTORY but it didn't work. > > I did basically the same thing to tools/build/v1/gcc-tools.jam as you did, at least with respect to ar and objcopy being available as variables that can be set on jam command line. I then used "-sGXX=m68k-elf-g++ -sGCC=m68k-elf-gcc -sAR=m68k-elf-ar" on my build command line. Additionally, I added support for selecting the CPU model (architecture/instruction-set) by adding the following: (I don't know how/why this works, just imitated the respective block for other architectures). Perhaps, boost build system should support (kind of) multilib builds for cross compilation, in a similar way that gcc/g++ does when cross-compiling it for targets where this applies? This enabled me to add "-sBUILD=debug release <runtime-link>static <optimization>size <architecture>m68k <instruction-set>5200" to the build command line for a Coldfire cross-build. It even somehow worked, as gcc got called with the correct -m option... # Coldfire and other m68k (WS, Tue Dec 20 16:46:10 2005). .ARCH = <architecture>m68k <architecture>native ; flags gcc CFLAGS <architecture>m68k/<instruction-set>default : -m5200 ; flags gcc CFLAGS <architecture>m68k/<instruction-set>68000 : -m68000 ; flags gcc CFLAGS <architecture>m68k/<instruction-set>5200 : -m5200 ; flags gcc CFLAGS <architecture>m68k/<instruction-set>5206e : -m5206e ; flags gcc CFLAGS <architecture>m68k/<instruction-set>528x : -m528x ; flags gcc CFLAGS <architecture>m68k/<instruction-set>5307 : -m5307 ; flags gcc CFLAGS <architecture>m68k/<instruction-set>5407 : -m5407 ; flags gcc CFLAGS <architecture>m68k/<instruction-set>cpu32 : -mcpu32 ; flags gcc CFLAGS <architecture>m68k/<instruction-set>68040 : -m68040 ; flags gcc CFLAGS <architecture>m68k/<instruction-set>68060 : -m68060 ; flags gcc CFLAGS <architecture>m68k/<instruction-set>soft-float : -msoft-float ; >So I've done a small patch to tools/build/v1/gcc-tools.jam adding >GCC_PREFIX variable, that if set up, will prefix names of all tools with >that prefix. > >So I can compile boost with > >bjam -sTOOLS=gcc -sGCC_PREFIX=arm-linux- stage > > Ah, your approach with using GCC_PREFIX is even better! Perhaps call it "-sCROSS_TARGET=arm-linux" ? >May be it will be useful to add the same functionality to >gcc-stlport-tools.jam or mingw. > >So please find attached changes. > >It is possible to include them into next boost release? > > I strongly vote for integrating cross-compilation support (at least using GNU toolchain, after all that's what most use!) in the Boost build system. But I don't know or use jam or bjam (other than building (parts of) boost itself), so unfortunately I would be of little help... :-( I replied to the post becuase somone else might find the information helpful as well, I hope. >By the way, the same problem appears when boost jam is used to compile >some third-party libraries. Is this place good to talk about boost jam >and its Jambase file? > > Probably move to the boost-build list? -wolfi -- DI Wolfram Stering (Entwicklung) HALE electronic GmbH., Salzburg, Austria Tel: +43 (662) 439011 550 Fax: +43 (662) 439011 9 Email: wolfram.stering(a)hale.at

2 1

How to create a smart pointer for a non-growable, size determined by run-time array
by yinglcs2＠yahoo.com 12 Jan '06

12 Jan '06

Hi, I have a non-growable, size determined by run-time array. For example convert this from Java to C: int[] func(int size) [ int[] array = new int[size]; return array; } I was told the only way I can do that is using STL vector. But if I need to have a smart pointer for this STL vector, should I use the c++ auto_ptr? or the Boost's shared_ptr with STL vector or Boost's shared_array? Thank you. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

3 3

callback and boost:function
by Lars Schouw 12 Jan '06

12 Jan '06

Guys, First thank you for a wonderful library and all the hours of work that is put into boost to make it what it is today. Is there anyway in C++ to setup a callback to a member function that takes two arguments I am trying to use boost::function but that only works with std::bind1st that does only take one parameter. I want to wrap some existing C code with C++. The function I want to call back is declareed like this: struct X { double foo(double x , void * p); }; Idealy I would like to use lambda to remove the void* and replace it with _1, _2 etc. But I am not sure how that works with callbacks. I had a look at the libsigc++ that seems to be able to handle callbacks with more arguments but the lambda stuff does not work under Visual Studio 2003 at least. Regards Lars Schouw --------------------------------- Yahoo! Photos Ring in the New Year with Photo Calendars. Add photos, events, holidays, whatever.

2 1

Re: [Boost-users] Question Regarding Boost 1.33.1 on MSVC.NET 2003
by Wu Yinghui, Freddie 12 Jan '06

12 Jan '06

Peter Dimov wrote: > The problem is that > > boost::bind(&OperatorMap::value_type::second, _1) > > returns an Operator by value (in 1.33.1) or by const reference (in the > current CVS). Since boost::bind needs to decide on a result type at bind > time, and since it doesn't know whether the argument coming in from the _1 > is const, it needs to conservatively assume const (Lambda doesn't have this > limitation because it deduces the return type at call time). > > Use > > boost::bind<Operator&>(&OperatorMap::value_type::second, _1) > > to tell boost::bind to return a non-const reference. Thanks for your quick reply! I noticed this problem at about the same time, and tried it out already. This modification indeed worked. Cheers, Freddie -- Wu Yinghui, Freddie Research & Development Software Engineer Volume Interactions Pte Ltd 1 Kim Seng Promenade, #12-01 Great World City East Tower Singapore 237994 Tel: +65 62226962 (Ext 216) Fax: +65 62226215 Email: yhwu(a)volumeinteractions.com URL: http://www.volumeinteractions.com Important: This message is intended for the recipient(s) addressed above. It contains privileged and confidential information. If you are not the intended recipient, please notify the sender immediately by replying to this message and then delete it from your system. You must not read, copy, use, or disseminate this communication in any form. Thank you.

1 0

[bjam] Inconsistency in header/library linkages
by Peter Whaite 11 Jan '06

11 Jan '06

One thing that catches me out every now and then is that I compile with the wrong boost header files. What I'd like to be able to do is omit the version number from the Makefile and include/ld the most recent `bjam install`. By default bjam hard links the libraries, e.g. libboost_serialization_gcc.a->libboost-serialization-gcc-1_33.a but there is no such linkage for the headers, e.g. /usr/local/include/boost->/usr/local/include/boost-1_33. I can maintain it by hand, but inevitably I end up forgetting. Is there something I can do to get bjam to update the header link automatically?

1 0

[lambda] Operators
by David Greene 11 Jan '06

11 Jan '06

Hi again, As can can probably guess, I'm just learning how to use the BLL. Here's another testcase I'm having trouble with: #include <boost/lambda/lambda.hpp> #include <boost/lambda/bind.hpp> #include <boost/iterator/counting_iterator.hpp> #include <vector> #include <algorithm> #include <cassert> class Test { private: int value; public: Test(int v) : value(v) {}; int get(void) const { return(value); }; }; std::vector<Test> seq; std::vector<Test>::iterator find_value(const Test &value) { using boost::lambda::bind; using boost::lambda::_1; return(std::find(seq.begin(), seq.end(), bind(&Test::get, _1) == value.get())); } int main(void) { std::copy(boost::counting_iterator<int>(0), boost::counting_iterator<int>(10), std::back_inserter(seq)); std::vector<Test>::iterator i = find_value(0); assert(i == seq.begin()); i = find_value(5); assert(i != seq.end()); i = find_value(11); assert(i == seq.end()); return(0); } [compile log below] Another question: when using bind to delay application of the member function to the object, is the object passed by reference or value on invocation? If by value, is there a way to pass it by reference? It's not relevant to this test but will be in the code I'm working on. I'm thinking of cases where I might want to run transform algorithms on Test objects. Thanks for your help. Some of this is just learning to pattern-match gcc's cryptic template error messages. -Dave ------------------- /usr/include/c++/3.3.3/bits/stl_algo.h: In function `_RandomAccessIter std::find(_RandomAccessIter, _RandomAccessIter, const _Tp&, std::random_access_iterator_tag) [with _RandomAccessIter = __gnu_cxx::__normal_iterator<Test*, std::vector<Test, std::allocator<Test> > >, _Tp = boost::lambda::lambda_functor<boost::lambda::lambda_functor_base<boost::lambda::relational_action<boost::lambda::equal_action>, boost::tuples::tuple<const int, boost::lambda::lambda_functor<boost::lambda::lambda_functor_base<boost::lambda::action<2, boost::lambda::function_action<2, boost::lambda::detail::unspecified> >, boost::tuples::tuple<int (Test::*const)() const, const boost::lambda::lambda_functor<boost::lambda::placeholder<1> >, 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, 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> > >]': /usr/include/c++/3.3.3/bits/stl_algo.h:298: instantiated from `_InputIter std::find(_InputIter, _InputIter, const _Tp&) [with _InputIter = __gnu_cxx::__normal_iterator<Test*, std::vector<Test, std::allocator<Test> > >, _Tp = boost::lambda::lambda_functor<boost::lambda::lambda_functor_base<boost::lambda::relational_action<boost::lambda::equal_action>, boost::tuples::tuple<const int, boost::lambda::lambda_functor<boost::lambda::lambda_functor_base<boost::lambda::action<2, boost::lambda::function_action<2, boost::lambda::detail::unspecified> >, boost::tuples::tuple<int (Test::*const)() const, const boost::lambda::lambda_functor<boost::lambda::placeholder<1> >, 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, 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> > >]' lambda2.cc:28: instantiated from here /usr/include/c++/3.3.3/bits/stl_algo.h:208: error: could not convert ` boost::lambda::operator==(const A&, const boost::lambda::lambda_functor<Arg>&) [with A = Test, Arg = boost::lambda::lambda_functor_base<boost::lambda::relational_action<boost::lambda::equal_action>, boost::tuples::tuple<const int, boost::lambda::lambda_functor<boost::lambda::lambda_functor_base<boost::lambda::action<2, boost::lambda::function_action<2, boost::lambda::detail::unspecified> >, boost::tuples::tuple<int (Test::*const)() const, const boost::lambda::lambda_functor<boost::lambda::placeholder<1> >, 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, 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> >]((+__val))' to `bool' /usr/include/c++/3.3.3/bits/stl_algo.h:298: instantiated from `_InputIter std::find(_InputIter, _InputIter, const _Tp&) [with _InputIter = __gnu_cxx::__normal_iterator<Test*, std::vector<Test, std::allocator<Test> > >, _Tp = boost::lambda::lambda_functor<boost::lambda::lambda_functor_base<boost::lambda::relational_action<boost::lambda::equal_action>, boost::tuples::tuple<const int, boost::lambda::lambda_functor<boost::lambda::lambda_functor_base<boost::lambda::action<2, boost::lambda::function_action<2, boost::lambda::detail::unspecified> >, boost::tuples::tuple<int (Test::*const)() const, const boost::lambda::lambda_functor<boost::lambda::placeholder<1> >, 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, 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> > >]' lambda2.cc:28: instantiated from here /usr/include/c++/3.3.3/bits/stl_algo.h:211: error: could not convert ` boost::lambda::operator==(const A&, const boost::lambda::lambda_functor<Arg>&) [with A = Test, Arg = boost::lambda::lambda_functor_base<boost::lambda::relational_action<boost::lambda::equal_action>, boost::tuples::tuple<const int, boost::lambda::lambda_functor<boost::lambda::lambda_functor_base<boost::lambda::action<2, boost::lambda::function_action<2, boost::lambda::detail::unspecified> >, boost::tuples::tuple<int (Test::*const)() const, const boost::lambda::lambda_functor<boost::lambda::placeholder<1> >, 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, 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> >]((+__val))' to `bool' /usr/include/c++/3.3.3/bits/stl_algo.h:214: error: could not convert ` boost::lambda::operator==(const A&, const boost::lambda::lambda_functor<Arg>&) [with A = Test, Arg = boost::lambda::lambda_functor_base<boost::lambda::relational_action<boost::lambda::equal_action>, boost::tuples::tuple<const int, boost::lambda::lambda_functor<boost::lambda::lambda_functor_base<boost::lambda::action<2, boost::lambda::function_action<2, boost::lambda::detail::unspecified> >, boost::tuples::tuple<int (Test::*const)() const, const boost::lambda::lambda_functor<boost::lambda::placeholder<1> >, 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, 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> >]((+__val))' to `bool' /usr/include/c++/3.3.3/bits/stl_algo.h:217: error: could not convert ` boost::lambda::operator==(const A&, const boost::lambda::lambda_functor<Arg>&) [with A = Test, Arg = boost::lambda::lambda_functor_base<boost::lambda::relational_action<boost::lambda::equal_action>, boost::tuples::tuple<const int, boost::lambda::lambda_functor<boost::lambda::lambda_functor_base<boost::lambda::action<2, boost::lambda::function_action<2, boost::lambda::detail::unspecified> >, boost::tuples::tuple<int (Test::*const)() const, const boost::lambda::lambda_functor<boost::lambda::placeholder<1> >, 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, 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> >]((+__val))' to `bool' /usr/include/c++/3.3.3/bits/stl_algo.h:223: error: could not convert ` boost::lambda::operator==(const A&, const boost::lambda::lambda_functor<Arg>&) [with A = Test, Arg = boost::lambda::lambda_functor_base<boost::lambda::relational_action<boost::lambda::equal_action>, boost::tuples::tuple<const int, boost::lambda::lambda_functor<boost::lambda::lambda_functor_base<boost::lambda::action<2, boost::lambda::function_action<2, boost::lambda::detail::unspecified> >, boost::tuples::tuple<int (Test::*const)() const, const boost::lambda::lambda_functor<boost::lambda::placeholder<1> >, 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, 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> >]((+__val))' to `bool' /usr/include/c++/3.3.3/bits/stl_algo.h:226: error: could not convert ` boost::lambda::operator==(const A&, const boost::lambda::lambda_functor<Arg>&) [with A = Test, Arg = boost::lambda::lambda_functor_base<boost::lambda::relational_action<boost::lambda::equal_action>, boost::tuples::tuple<const int, boost::lambda::lambda_functor<boost::lambda::lambda_functor_base<boost::lambda::action<2, boost::lambda::function_action<2, boost::lambda::detail::unspecified> >, boost::tuples::tuple<int (Test::*const)() const, const boost::lambda::lambda_functor<boost::lambda::placeholder<1> >, 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, 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> >]((+__val))' to `bool' /usr/include/c++/3.3.3/bits/stl_algo.h:229: error: could not convert ` boost::lambda::operator==(const A&, const boost::lambda::lambda_functor<Arg>&) [with A = Test, Arg = boost::lambda::lambda_functor_base<boost::lambda::relational_action<boost::lambda::equal_action>, boost::tuples::tuple<const int, boost::lambda::lambda_functor<boost::lambda::lambda_functor_base<boost::lambda::action<2, boost::lambda::function_action<2, boost::lambda::detail::unspecified> >, boost::tuples::tuple<int (Test::*const)() const, const boost::lambda::lambda_functor<boost::lambda::placeholder<1> >, 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, 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> >]((+__val))' to `bool' make: *** [lambda2.o] Error 1 Compilation exited abnormally with code 2 at Wed Jan 11 12:21:07

4 4

Boost and Sun Studio 11
by Dipak Bapatla 11 Jan '06

11 Jan '06

Hi, Has anyone built Boost using Sun Studio 11 on Solaris 8? I tried to build with the boost source 1.33.1 and it was complaining about assertions ../link.cc or something like that. Then I saw a post which talked about BOOST_NO_INCLASS_MEMBER_INITIALIZATION. So I changed the file boost/config/compiler/sunpro_cc.hpp as follows //# if (__SUNPRO_CC < 0x570) # define BOOST_NO_TEMPLATE_TEMPLATES // see http://lists.boost.org/MailArchives/boost/msg47184.php // and http://lists.boost.org/MailArchives/boost/msg47220.php # define BOOST_NO_INCLASS_MEMBER_INITIALIZATION # define BOOST_NO_SFINAE # define BOOST_NO_ARRAY_TYPE_SPECIALIZATIONS # define BOOST_NO_IS_ABSTRACT //# endif I commented out the code where it was checking for compiler version less than 5.7. I was able to compile the code (atleast the ones I needed - date_time and serialization). Now when I try to use the built libraries with my test code, I get the following errors related to has_facet and use_facet. "/opt/idev3/dbapatla/NativeSTL/boostlibs/include/boost-1_33_1/boost/date_time/gregorian/gregorian_io.hpp", line 45: Error: Could not find a match for std::has_facet<std::Facet>(std::locale) needed in boost::gregorian::operator<<<char, std::char_traits<char>>(std::ostream &, const boost::gregorian::date&). "/opt/idev3/dbapatla/NativeSTL/boostlibs/include/boost-1_33_1/boost/date_time/gregorian/gregorian_io.hpp", line 46: Error: Could not find a match for std::use_facet<std::Facet>(std::locale) needed in boost::gregorian::operator<<<char, std::char_traits<char>>(std::ostream &, const boost::gregorian::date&). "/opt/idev3/dbapatla/NativeSTL/boostlibs/include/boost-1_33_1/boost/date_time/gregorian/gregorian_io.hpp", line 46: Error: Could not find a match for std::use_facet<std::Facet>(std::locale) needed in boost::gregorian::operator<<<char, std::char_traits<char>>(std::ostream &, const boost::gregorian::date&). "/opt/idev3/dbapatla/NativeSTL/boostlibs/include/boost-1_33_1/boost/date_time/gregorian/gregorian_io.hpp", line 45: Error: Could not find a match for std::has_facet<std::Facet>(std::locale) needed in boost::gregorian::operator<<<char, std::char_traits<char>>(std::ostream &, const boost::gregorian::date&). "/opt/idev3/dbapatla/NativeSTL/boostlibs/include/boost-1_33_1/boost/date_time/gregorian/gregorian_io.hpp", line 46: Error: Could not find a match for std::use_facet<std::Facet>(std::locale) needed in boost::gregorian::operator<<<char, std::char_traits<char>>(std::ostream &, const boost::gregorian::date&). "/opt/idev3/dbapatla/NativeSTL/boostlibs/include/boost-1_33_1/boost/date_time/gregorian/gregorian_io.hpp", line 46: Error: Could not find a match for std::use_facet<std::Facet>(std::locale) needed in boost::gregorian::operator<<<char, std::char_traits<char>>(std::ostream &, const boost::gregorian::date&). Has anyone come across these errors? thanks, Deepak

1 0

How to run the boost.python example
by Olga Gerchikov 11 Jan '06

11 Jan '06

Hi, how can I run the boost.python example? >From the README, I did this: ~/src/boost_1_33_1/libs/python/example bjam -sTOOLS=gcc test But please tell me what is the next step?

1 0

[lambda] Understanding ->*
by David Greene 11 Jan '06

11 Jan '06

I'm debugging some even nastier lambda compiler error messages (not sure if I can reduce to a testcase but I'll try). In the course of figuring this out, I relized that I need to understand the similarities and/or differences between bind operations and ->* in a lambda context. What is the difference between these two: class Class { public: int member_func(void); }; bind(&Class::member_func, _1) == 1 (_1 ->* &Class::member_func) == 1 used in the context of std::find_if(seq.being(), seq.end(), <lambda-func>); Does the second construct make sense in this case? I don't think it does because member_func takes no arguments. Because the ->* expression must be followed immediately by an argument list, there is no way to delay the substitution of the object on which to call member_func. This, I believe, it what bind is for. That is, ->* only delays application of n-1 arguments, where n is the total arity of the function (including the hidden "this" parameter). Bind is able to delay application of all n arguments. Is this analysis correct? -Dave

2 1

Re: [Boost-users] Pyste/Pyplusplus/Boost documentation problems
by Nat Goodspeed 11 Jan '06

11 Jan '06

> -----Original Message----- > From: boost-users-bounces(a)lists.boost.org [mailto:boost-users- > bounces(a)lists.boost.org] On Behalf Of Drumheller, Michael > Sent: Wednesday, January 11, 2006 1:18 PM > To: c++-sig(a)python.org; boost-users(a)lists.boost.org > Subject: [Boost-users] Pyste/Pyplusplus/Boost documentation problems > > As a side question, does anyone use Boost.Python *without* an automatic > code generator such as Pyste or Pyplusplus? [Nat] We do. > It does not seem like a > practical thing to do--but maybe I'm missing something...? [Nat] Heh, maybe we should have paid more attention to Pyste when we got started, but we just kept growing the hand-coded prototype module.

1 0

Re: [Boost-users] Boost Serialization: extended_type_info_no_rtti not working...
by RIVASSEAU Jean Noel 11 Jan '06

11 Jan '06

Hello I get the exception for the derived class - not the base class. Yes, I have done everything correctly for both the base and derived class. After reading your mail, I have several questions: You recommend to include the archives headers once in the executable. This seems strange; I need to include them in many .cpp files (everytime I want to *call* serialization code). This is why I've included serialization code in the .cpp files and not the headers, in order to avoid multiple definitions. Of course, if you include the archive files only once in your executable, I understand that you can put all serialization code in the headers. But being able to include archive headers only once will require me to do quite a bit of code reorganization I think (every function that needs to call serialization has to be put in the same file... even if they are member functions belonging to different classes etc... I do not understand how you can achieve this without a big mess). If, like I did, you include serialization code only in the .cpp files, you avoid multiple definitions problems, since the code is only instantiated for each class during the compile of the .cpp. Of course, the disadvantage is that you must include the archive headers in each class that you want to serialize, before the export.hpp. And the second problem is that at run time it does not work (the problem I am reporting). This is strange. I found yesterday a way to avoid my problem. If I put all the serialization code in the *same* .cpp file, and compile that file, everything works fine. This means that the derived class is properly registered only if during the compilation of the same unit, the code corresponding to the base class is also instantiated. If you instantiate "separately" the serialization code for the base class and the derived class, it does not work. This is probably a bug, but only you can tell since you know the implementation (and with your way of organizing your code, you probably never ran into this problem). In fact, I think I will maybe keep this workaround (one special .cpp file with all the serialization code for all my classes) since it has several advantages (one is that I am independent of any archive implementation, as I only need to change the headers in that only .cpp file ). Thank you, I am waiting for your reply on these remarks. Jean-Noël For which class do you get this exception? But I have done the following: in all my classes, in the implementation unit (.cpp) I have included explicitely the headers needed for the archives I use: #include <boost/archive/text_oarchive.hpp> #include <boost/archive/text_iarchive.hpp> Then I have something like that in each class: #include <boost/serialization/base_object.hpp> #include <boost/serialization/type_info_implementation.hpp> #include <boost/serialization/extended_type_info_no_rtti.hpp> #include <boost/serialization/export.hpp> namespace boost { namespace serialization { template<class Archive> void serialize(Archive & ar, PrimitiveMemberVariableSpecification & m, const unsigned int version) { ar & boost::serialization::base_object<MemberVariableSpecification>(m); ar & m.unused_primitive_type; } } // namespace serialization } // namespace boost BOOST_CLASS_TYPE_INFO( PrimitiveMemberVariableSpecification, extended_type_info_no_rtti<PrimitiveMemberVariableSpecification> ) BOOST_CLASS_EXPORT(PrimitiveMemberVariableSpecification) (Here the name of the class is PrimitiveMemberVariableSpecification. Is the above being done for the base class as well? I also want to report a bug in the documentation: the doc says that you should write: <skip> correct - good call. Normally the BOOST_CLASS_EXPORT should *register* all my classes. Why doesn't it work? I have of course also written a correct get_key() virtual function for all my classes. If I just change extended_type_info_no_rtti to extended_type_info_typeid, everything works fine, but I do want extended_type_info_no_rtti. This suggests that all derived classes are being exported. Also, keeping everything in the headers files seems to be a nightmare, although that is what Robert Ramsey recommends. I get tons of multiple definitions errors at link time if I do that (something like: multiple definition of `boost::archive::detail::guid_initializer<MemberVariableSpecification>::instance' with gcc - MinGW 3.4.2) This would surprise me. It suggests that boost/archive/...archive.hpp files are being included in several places. In order to avoid the bothersome warnings above and speed build time. I try to organize my code so that non-inline code is instantiated in only one place. This is not strictly a requirement but generally I've found that things work better this way. And I'm not just referring to serialization code but C++ template code in general. In theory, it shouldn't matter, but in practice things work better this way. So what works well for me is: Include serialization code in the headers corresponding to each type. That way all if the types are imported into different executables they are all all consistent with each other. include boost/archive/... headers only once in each executable. This will eliminate multiple definition errors. This might take a little bit of code re-organization and should not be strictly necessary - but it has worked well for me. Generally I also recommend that any boost/archive/...hpp headers be included before any boost/serialization/...hpp headers. This is not strictly necessary - though it was at one time - but I'm in the habit of doing it. If I find I can't do it, I'm wondering if I "accidently" included a boost/archive/....hpp in another header - which can lead to multiple definition warnngs. Also if I do this an import the module into another executable, I might be instantiating code that isn't called. By sticking to the "rules of thumb" above, I generally avoid some problems and or surprises. Note that there are couple of cases where header order does make a difference. a) boost/serialization/export.hpp has to follow all the boost/archive/...hpp files for each combination of type/archive export to be instantiated. b) boost/serialization/base_object.hpp has to follow all the boost/archive/*.hpp files. This is an oversight which will be corrected in the next version. I have looked at the documentation for two days, read absolutely everything and still do not understand. Maybe I should look at the code ??? LOL - if you like the documentation - you'll love the code ! But, trapping the exception will tell you which class isn't being "registered" which will be helpful information. Robert Ramey

2 1

Re: [Boost-users] [serialization] [wave] [spirit] Can't compile boost cvs
by Peter Whaite 11 Jan '06

11 Jan '06

Joel de Guzman <joel(a)boost-consulting.com> wrote: > > Ok, confirmed. I'm the culprit :( Someone submitted a patch > for the is* functions to work on other POD types. Hartmut is > reverting it now while I try to find a fix. OK thanks it compiles now. I'm still surprised this wasn't reported earlier as serialization seems to be one of the more popular libs.

1 0

BOOST_STATIC_ASSERT is not compiled
by OSA 11 Jan '06

11 Jan '06

Look at example code: class CBase { public: virtual ~CBase(){} virtual void foo()const = 0; }; template <class T> class CTest { private: BOOST_STATIC_ASSERT((boost::is_base_of<CBase,T>::value_type)); public: CTest(){} void what()const { } }; class CDerived : public CBase { CTest<CDerived> m_a; public: CDerived(){} virtual void foo()const{m_a.what();} }; int main(int argc, _TCHAR* argv[]) { CDerived d; d.foo(); return 0; } I am using the BOOST_STATIC_ASSERT to make sure the template parameter of the CTest class is inherited from some specific class (in particular CBase in this example). But this code is not compiled. I am using Visual C++ 7 compiler. What is my error?

2 1

[lambda] Binding template functions
by David Greene 11 Jan '06

11 Jan '06

Is it possible to bind template functions? If so, what's the syntax? I'm having trouble with this test: #include <boost/lambda/bind.hpp> #include <boost/numeric/interval.hpp> #include <vector> #include <cassert> typedef boost::numeric::interval<int> range; std::vector<range> ranges; int main(void) { using boost::lambda::bind; using boost::lambda::_1; int range_base = 0; int range_limit = 9; for(int i = 0; i < 10; ++i) { ranges.push_back(range(range_base, range_limit)); range_base += 10; range_limit += 10; } std::vector<range>::iterator i = std::find_if(ranges.begin(), ranges.end(), bind(&boost::numeric::template in<range>, 5, _1)); // bind(&boost::numeric::in<range>, 5, _1)); // bind(&boost::numeric::in, 5, _1)); assert(i == ranges.begin()); return(0); } None of the commented options works, either. I wouldn't expect the last one to work. They all fail with the same error trace: lambda.cc: In function `int main()': lambda.cc:27: error: no matching function for call to `bind(<unknown type>, int, const boost::lambda::lambda_functor<boost::lambda::placeholder<1> >&)' Any ideas? -Dave

3 3

Smart pointer library in boost
by Olga Gerchikov 11 Jan '06

11 Jan '06

Suppose I have this function in c++: int* f(int size) { int * array = new int[size]; return array; } Is there a safe idiom to prevent memory leak? Should i use auto_ptr in C++? Or should I use the smart pointer library in boost? Which is the simplest solution? Thank you.

3 2

[Boost.Build][program_options] Problem with path length
by Ames Andreas 11 Jan '06

11 Jan '06

Hi all, I have a problem with building program_options on VC 7.1. It is only related to program_options in that this is one of the boost libs with the longest names. The problem is the path length of files generated during build. As an example, there is a file generated with the name bin/boost/libs/program_options/build/libboost_program_options.lib/vc-7_1/debug/native-wchar_t-off/threading-multi/libboost_program_options-vc71-mt-gd-1_33.CMD which amounts to 158 characters in length. As the path to the leading bin directory is already 100 characters long, I cannot build (max. 254 characters on NTFS). Besides shortening the preceding path, is there any other solution (like customizing the generated path)? TIA, aa -- Andreas Ames | Programmer | Comergo GmbH | Voice: +49 69 7505 3213 | andreas . ames AT comergo . com

2 1

Re: [Boost-users] Cross compiling boost libraries with gcc and us ing boost jam to crosscompile third-party library (Jambase problem)
by James Hughes 11 Jan '06

11 Jan '06

> -----Original Message----- > From: Vladimir Michl [mailto:vladimir.michl@seznam.cz] > Sent: 11 January 2006 13:09 > To: boost-users(a)lists.boost.org > Subject: Re: [Boost-users] Cross compiling boost libraries > with gcc and > us ing boost jam to crosscompile third-party library (Jambase problem) > > > On Wed, 2006-01-11 at 11:25 +0100, James Hughes wrote: > > I had the same problem in the same circumstance. Just > hacked mine to call > > the correct objcopy. > > > > Did you get the whole boost system to build cleanly - I am > still seeing > > problems (although a very recent post may have explained why) > > I was compiling boost 1.32, may be this is reason why it worked. > > Vlad My build is 1.33, which may be the cause of the fault as indicated by another post today. Thanks for the info - I don't have -D_REENTRANT, so will try that anyway. James

1 0

Re: [Boost-users] Cross compiling boost libraries with gcc and us ing boost jam to crosscompile third-party library (Jambase problem)
by James Hughes 11 Jan '06

11 Jan '06

I had the same problem in the same circumstance. Just hacked mine to call the correct objcopy. Did you get the whole boost system to build cleanly - I am still seeing problems (although a very recent post may have explained why) James -----Original Message----- From: Vladimir Michl [mailto:vladimir.michl@seznam.cz] Sent: 10 January 2006 17:03 To: boost-users Subject: [Boost-users] Cross compiling boost libraries with gcc and using boost jam to crosscompile third-party library (Jambase problem) Hi all in this list, recently I was put into task to cross compile boost for ARM platform with GCC. My building platform is i386 Linux with gcc and cross compiling to arm Linux. Standard way for this kind of compilation is, that name of cross compiler (running under i386 but producing arm code) and all cross binary utilities are prefixed by target plarform, so like arm-linux-gcc, arm-linux-g++, arm-linux-ar, arm-linux-objcopy for arm-linux. And this is causing a bit of problem with boost. I can force GCC and GXX, but still have a problem with ar and objcopy. I've tried to setup GCC_BIN_DIRECTORY but it didn't work. So I've done a small patch to tools/build/v1/gcc-tools.jam adding GCC_PREFIX variable, that if set up, will prefix names of all tools with that prefix. So I can compile boost with bjam -sTOOLS=gcc -sGCC_PREFIX=arm-linux- stage May be it will be useful to add the same functionality to gcc-stlport-tools.jam or mingw. So please find attached changes. It is possible to include them into next boost release? By the way, the same problem appears when boost jam is used to compile some third-party libraries. Is this place good to talk about boost jam and its Jambase file? Vlad -- Vladimir Michl <vladimir.michl(a)seznam.cz>, ICQ# 312939054 Tel: +447793527010 +447906361574 +420608413590

2 2

Need help in installing Boost on Fedora 4
by yinglcs2＠yahoo.com 11 Jan '06

11 Jan '06

Hi, i am trying to install Boost on Fedora 4 I am able to configure, make and make install, But I don't know how to do step 5 in here: http://www.boost.org/more/getting_started.html#Build_Install When I type 'bjam', I got a 'bjam: command not found' Thanks for any help. [localhost boost_1_33_1]$ bjam bash: bjam: command not found __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

3 3

Question Regarding Boost 1.33.1 on MSVC.NET 2003
by Wu Yinghui, Freddie 11 Jan '06

11 Jan '06

Hi all, I'm having a problem using Boost.Bind on the above platform. The simple test file I'm using looks like this: === snip === #include <iostream> #include <algorithm> #include <map> #include <boost/bind.hpp> struct Argument { int value_; }; struct Operator { Operator &compute(Argument const &arg) { std::cout << arg.value_ << std::endl; return *this; } // Warning is gone if I declare the above function as: //Operator const &compute(Argument const &arg) const {...} }; int main() { typedef std::map<int, Operator> OperatorMap; OperatorMap ops; ops.insert(std::make_pair(0, Operator())); Argument arg0 = { 1 }; std::for_each( ops.begin(), ops.end(), boost::bind(&Operator::compute, boost::bind(&OperatorMap::value_type::second, _1), boost::cref(arg0))); } === snip === The idea is that I want to put a parameter through a collection of Operators objects stored in an std::map. However, I always get the following warning from the compiler: === snip === test.cpp ..\..\..\boost-1.x\include\boost-1_33_1\boost\bind.hpp(276) : warning C4239: nonstandard extension used : 'argument' : conversion from 'boost::_bi::result_traits<R,F>::type' to 'Operator &' with [ R=Operator, F=boost::_mfi::dm<Operator,stlp_std::pair<const int,Operator>> ] A reference that is not to 'const' cannot be bound to a non-lvalue ..\..\..\boost-1.x\include\boost-1_33_1\boost\bind\bind_template.hpp(32) : see reference to function template instantiation 'R boost::_bi::list2<A1,A2>::operator ()<boost::_bi::bind_t<R,F,L>::result_type,F,boost::_bi::list1<stlp_std::pair<_T1,_T2> &>>(boost::_bi::type<T>,F &,A &,long)' being compiled with [ R=boost::_bi::bind_t<Operator &,boost::_mfi::mf1<Operator &,Operator,const Argument &>,boost::_bi::list2<boost::_bi::list_av_2<boost::_bi::bind_t<Operator,boost::_mfi::dm<Operator,stlp_std::pair<const int,Operator>>,boost::_bi::list1<boost::_bi::list_av_1<boost::arg<1>>::B1>>,Argument>::B1,boost::_bi::list_av_2<boost::_bi::bind_t<Operator,boost::_mfi::dm<Operator,stlp_std::pair<const int,Operator>>,boost::_bi::list1<boost::_bi::list_av_1<boost::arg<1>>::B1>>,Argument>::B2>>::result_type, A1=boost::_bi::list_av_2<boost::_bi::bind_t<Operator,boost::_mfi::dm<Operator,stlp_std::pair<const int,Operator>>,boost::_bi::list1<boost::_bi::list_av_1<boost::arg<1>>::B1>>,Argument>::B1, A2=boost::_bi::list_av_2<boost::_bi::bind_t<Operator,boost::_mfi::dm<Operator,stlp_std::pair<const int,Operator>>,boost::_bi::list1<boost::_bi::list_av_1<boost::arg<1>>::B1>>,Argument>::B2, F=boost::_mfi::mf1<Operator &,Operator,const Argument &>, L=boost::_bi::list2<boost::_bi::list_av_2<boost::_bi::bind_t<Operator,boost::_mfi::dm<Operator,stlp_std::pair<const int,Operator>>,boost::_bi::list1<boost::_bi::list_av_1<boost::arg<1>>::B1>>,Argument>::B1,boost::_bi::list_av_2<boost::_bi::bind_t<Operator,boost::_mfi::dm<Operator,stlp_std::pair<const int,Operator>>,boost::_bi::list1<boost::_bi::list_av_1<boost::arg<1>>::B1>>,Argument>::B2>, _T1=const int, _T2=Operator, T=boost::_bi::bind_t<Operator &,boost::_mfi::mf1<Operator &,Operator,const Argument &>,boost::_bi::list2<boost::_bi::list_av_2<boost::_bi::bind_t<Operator,boost::_mfi::dm<Operator,stlp_std:: pair<const int,Operator>>,boost::_bi::list1<boost::_bi::list_av_1<boost::arg<1>>::B1>>,Argument>::B1,boost::_bi::list_av_2<boost::_bi::bind_t<Operator,boost::_mfi::dm<Operator,stlp_std::pair<const int,Operator>>,boost::_bi::list1<boost::_bi::list_av_1<boost::arg<1>>::B1>>,Argument>::B2>>::result_type, A=boost::_bi::list1<stlp_std::map<int,Operator>::value_type &> ] ..\..\..\STLport-5.0\stlport\stl\_algo.h(61) : see reference to function template instantiation 'boost::_bi::bind_t<R,F,L>::result_type boost::_bi::bind_t<R,F,L>::operator ()<_Tp>(A1 &)' being compiled with [ R=Operator &, F=boost::_mfi::mf1<Operator &,Operator,const Argument &>, L=boost::_bi::list2<boost::_bi::list_av_2<boost::_bi::bind_t<Operator,boost::_mfi::dm<Operator,stlp_std::pair<const int,Operator>>,boost::_bi::list1<boost::_bi::list_av_1<boost::arg<1>>::B1>>,Argument>::B1,boost::_bi::list_av_2<boost::_bi::bind_t<Operator,boost::_mfi::dm<Operator,stlp_std::pair<const int,Operator>>,boost::_bi::list1<boost::_bi::list_av_1<boost::arg<1>>::B1>>,Argument>::B2>, _Tp=stlp_std::map<int,Operator>::value_type, A1=stlp_std::map<int,Operator>::value_type ] \workspace\devel\RD3.0-vc71\Libraries\MkToolkit-3.0\src\core\test.cpp(35) : see reference to function template instantiation '_Function stlp_std::for_each<stlp_std::map<_Key,_Tp>::iterator,boost::_bi::bind_t<R,F,L>>(_InputIter,_InputIter,_Function)' being compiled with [ _Function=boost::_bi::bind_t<Operator &,boost::_mfi::mf1<Operator &,Operator,const Argument &>,boost::_bi::list2<boost::_bi::list_av_2<boost::_bi::bind_t<Operator,boost::_mfi::dm<Operator,stlp_std::pair<const int,Operator>>,boost::_bi::list1<boost::_bi::list_av_1<boost::arg<1>>::B1>>,Argument>::B1,boost::_bi::list_av_2<boost::_bi::bind_t<Operator,boost::_mfi::dm<Operator,stlp_std::pair<const int,Operator>>,boost::_bi::list1<boost::_bi::list_av_1<boost::arg<1>>::B1>>,Argument>::B2>>, _Key=int, _Tp=Operator, R=Operator &, F=boost::_mfi::mf1<Operator &,Operator,const Argument &>, L=boost::_bi::list2<boost::_bi::list_av_2<boost::_bi::bind_t<Operator,boost::_mfi::dm<Operator,stlp_std::pair<const int,Operator>>,boost::_bi::list1<boost::_bi::list_av_1<boost::arg<1>>::B1>>,Argument>::B1,boost::_bi::list_av_2<boost::_bi::bind_t<Operator,boost::_mfi::dm<Operator,stlp_std::pair<const int,Operator>>,boost::_bi::list1<boost::_bi::list_av_1<boost::arg<1>>::B1>>,Argument>::B2>, _InputIter=stlp_std::map<int,Operator>::iterator ] === snip === It seems that it is complaining about the const-ness of Operator::compute() member function. May I know if there is anything I can do to fix this problem? Or, is there any problem with my understanding of Boost.Bind through the way I used it? Cheers, Freddie -- Wu Yinghui, Freddie Research & Development Software Engineer Volume Interactions Pte Ltd 1 Kim Seng Promenade, #12-01 Great World City East Tower Singapore 237994 Tel: +65 62226962 (Ext 216) Fax: +65 62226215 Email: yhwu(a)volumeinteractions.com URL: http://www.volumeinteractions.com Important: This message is intended for the recipient(s) addressed above. It contains privileged and confidential information. If you are not the intended recipient, please notify the sender immediately by replying to this message and then delete it from your system. You must not read, copy, use, or disseminate this communication in any form. Thank you.

2 1

Re: [Boost-users] [serialization] [wave] [spirit] Can't compile b oost cvs
by James Hughes 11 Jan '06

11 Jan '06

I think this is the same or similar fault I am seeing when cross compiling to ARM architecture. Lots of faults in the serialisation and grammar area, seemingly caused by a single fault somewhere. Fingers crossed your fix fixes this also. FYI, here is a snapshot of one of the faults... /home/jhughes/boost_1_33_1/boost/spirit/core/primitives/numerics.hpp:120: error: declaration of `template<class ScannerT> struct boost::spirit::sign_parser::result' /home/jhughes/boost_1_33_1/boost/spirit/core/parser.hpp:123: error: conflicts with previous declaration `template<class ScannerT> struct boost::spirit::parser<boost::spirit::sign_parser>::result' In file included from /home/jhughes/boost_1_33_1/libs/serialization/build/../src/basic_xml_grammar .ipp:22, from /home/jhughes/boost_1_33_1/libs/serialization/build/../src/xml_wgrammar.cpp: 243: If that isn't the case, the anyone any ideas? James -----Original Message----- From: Joel de Guzman [mailto:joel@boost-consulting.com] Sent: 10 January 2006 23:33 To: boost-users(a)lists.boost.org Subject: Re: [Boost-users] [serialization] [wave] [spirit] Can't compile boost cvs Peter Whaite wrote: > Since before Christmas I haven't been able to compile the cvs > serialization xml files. It looks like something in spirit. Wave also > fails to compile with the same errors. > > I'm a bit surprised I haven't seen this mentioned on the boost lists, > though I see there are many failures in the boost regression > notifications. Ok, confirmed. I'm the culprit :( Someone submitted a patch for the is* functions to work on other POD types. Hartmut is reverting it now while I try to find a fix. Regards, -- Joel de Guzman http://www.boost-consulting.com http://spirit.sf.net _______________________________________________ Boost-users mailing list Boost-users(a)lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users

1 0

Memory leak with STL containers and pool_allocator?
by Georgios Diamantopoulos 11 Jan '06

11 Jan '06

Hello everyone, I am experiencing a memory leak while using pool_allocator with std::vector. I am detecting this with _CrtDumpMemoryLeaks() on MSVC8. The full program listing is at the end of the program. The leaks reported are: Detected memory leaks! Dumping objects -> {122} normal block at 0x00356518, 520 bytes long. Data: < e5 e5 $e5 (e5 > 1C 65 35 00 20 65 35 00 24 65 35 00 28 65 35 00 {121} normal block at 0x003563D0, 264 bytes long. Data: < c5 c5 c5 c5 > D4 63 35 00 D8 63 35 00 DC 63 35 00 E0 63 35 00 {120} normal block at 0x00356308, 136 bytes long. Data: < c5 c5 c5 c5 > 0C 63 35 00 10 63 35 00 14 63 35 00 18 63 35 00 Object dump complete. This could be due to a static object being destroyed after main() returns but I couldn't know that without knowing the implementation of pool_allocator. I have tried getting mem checkpoints at the beginning and end of main and detecting the leaks that way which I *think* would get around static objects but without any difference. Thanks, Georgios #define CRTDBG_MAP_ALLOC #include <cstdlib> #include <crtdbg.h> #include <stdexcept> #if defined(_DEBUG) inline void* __cdecl operator new(size_t nSize) { void* pResult = _malloc_dbg(nSize, _NORMAL_BLOCK, NULL, 0); if (pResult != NULL) return pResult; else throw std::bad_alloc(); return pResult; } inline void __cdecl operator delete(void* p) { _free_dbg(p, _NORMAL_BLOCK); } inline void* __cdecl operator new[](size_t nSize) { return ::operator new(nSize); } inline void __cdecl operator delete[](void* p) { ::operator delete(p); } inline void* __cdecl operator new(size_t nSize, int nType, const char * lpszFileName, int nLine) { void* pResult = _malloc_dbg(nSize, nType, lpszFileName, nLine); if (pResult != NULL) return pResult; else throw std::bad_alloc(); return pResult; } inline void* __cdecl operator new[](size_t nSize, int nType, const char * lpszFileName, int nLine) { return ::operator new(nSize, nType, lpszFileName, nLine); } inline void* __cdecl operator new(size_t nSize, const char * lpszFileName, int nLine) { return ::operator new(nSize, _NORMAL_BLOCK, lpszFileName, nLine); } inline void* __cdecl operator new[](size_t nSize, const char * lpszFileName, int nLine) { return ::operator new[](nSize, _NORMAL_BLOCK, lpszFileName, nLine); } inline void __cdecl operator delete(void* pData, const char * /* lpszFileName */, int /* nLine */) { ::operator delete(pData); } inline void __cdecl operator delete[](void* pData, const char * /* lpszFileName */, int /* nLine */) { ::operator delete(pData); } #define DEBUG_NEW new(THIS_FILE, __LINE__) #endif // _DEBUG #include <vector> #include <boost/pool/pool_alloc.hpp> #ifdef _DEBUG #define new DEBUG_NEW #undef THIS_FILE static char THIS_FILE[] = __FILE__; #endif int main(void) { std::vector<int, boost::pool_allocator<int> > data_points; for(int i = 0; i < 100; ++i) { data_points.push_back(i); } data_points.~vector(); boost::singleton_pool<boost::pool_allocator_tag, sizeof(int)>::release_memory(); _CrtDumpMemoryLeaks(); return 0; }

1 0

How to use Boost.Array library
by yinglcs2＠yahoo.com 11 Jan '06

11 Jan '06

In Java, I can create an array based on the value of an input parameter of a function: int[] func (int size) { int[] rtn = new int[size]; // do something return rtn; } Can you please tell me if I can do the same with the Boost.Array library? >From the example I see, I can only declare the size of the array during declaration (not dynamically, the rhs in my example). If I can't do that with Boost.Array, is there any other solution? Thank you. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

2 1

Getting Started documentation: minor update request
by Lonnie Princehouse 11 Jan '06

11 Jan '06

Hello, I'm trying to get boost-build up and running on Linux so that I can build the Python bindings for Boost.Graph, and after a few hours of fiddling around I'm thoroughly confused and frustrated. Please, could someone who understands boost-build could tell me what I'm doing wrong? (Note: I added the boost-build.jam file, which points to the installation directory of boost-build, and the project-root.jam which is just two newlines, copied from the "hello" example.) -------------------------------------------------------------------------------------------------- bash$ ls Jamfile LICENSE_1_0.txt boost build project-root.jam src Jamrules README boost-build.jam example python test bash$ bjam /usr/local/share/boost-build/build/project-roots.jam:368: in project-root warning: rulename $(project-root).$(method) expands to empty string Jamfile:13: in modules.load /usr/local/share/boost-build/build/project.jam:255: in load-jamfile /usr/local/share/boost-build/build/project.jam:67: in project.load /usr/local/share/boost-build/build-system.jam:75: in load /usr/local/share/boost-build/kernel/modules.jam:259: in import /usr/local/share/boost-build/kernel/bootstrap.jam:120: in boost-build /home/princelj/boost_graph/bgl-python-0.9/boost-build.jam:1: in module scope Jamfile:19: in modules.load rule subinclude unknown in module Jamfile</home/princelj/boost_graph/bgl-python-0.9>. /usr/local/share/boost-build/build/project.jam:255: in load-jamfile /usr/local/share/boost-build/build/project.jam:67: in project.load /usr/local/share/boost-build/build-system.jam:75: in load /usr/local/share/boost-build/kernel/modules.jam:259: in import /usr/local/share/boost-build/kernel/bootstrap.jam:120: in boost-build /home/princelj/boost_graph/bgl-python-0.9/boost-build.jam:1: in module scope ---------------------------------------------------------------------------------- The Jamfile that came with bgl-python looks like this: # Copyright 2005 The Trustees of Indiana University. # Use, modification and distribution is subject to the Boost Software # License, Version 1.0. (See accompanying file LICENSE_1_0.txt or copy at # http://www.boost.org/LICENSE_1_0.txt) # Authors: Douglas Gregor # Andrew Lumsdaine # This file builds the Python bindings for the Boost Graph Library and # the Parallel BGL. project-root ; # Only build release-mode binaries, unless the user explicitly # requests otherwise BUILD ?= release ; subinclude build ; subinclude build/distributed ; ------------------------------------------------------------------------------ Boost, bjam, and boost-build (V2) are the latest (non-CVS) releases from boost.org, installed as per the "Getting Started" instructions on boost.org. I have no idea what's going wrong. I read on the list archive that "subinclude" only exists in perforce-jam, not bjam, so I emerged perforce jam and tried it with no more success: $ jam warning: unknown rule project-root warning: unknown rule subinclude warning: unknown rule subinclude ...found 7 target(s)... Please help! (This is using Gentoo Linux, although boost/bjam/boost-build were installed from scratch and not using the ebuilds)

2 2