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

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