- Boost-users - lists.boost.org

Re: [Boost-users] [multi_index] Problem with find() and Hashed_Index
by Martin Higham 06 Dec '05

06 Dec '05

Thats just what I needed to know. It's all working fine now. Thanks Martin > From: JOAQUIN LOPEZ MU?Z <joaquin(a)tid.es> > To: boost-users(a)lists.boost.org > Date: Sun, 04 Dec 2005 00:31:08 +0100 > Subject: Re: [Boost-users] [multi_index] Problem with find() and > Hashed_Index > Hello Martin, > > ----- Mensaje original ----- > De: Martin Higham <martinh(a)gmail.com> > Fecha: Sábado, Diciembre 3, 2005 11:42 am > Asunto: [Boost-users] [multi_index] Problem with find() and > Hashed_Index > > > I have created a multi_index_container inline with one ordered_unique > > index and one hashed_unique index as demonstrated in the > > documentation > > > (http://www.boost.org/libs/multi_index/doc/advanced_topics.html#hash_lo > okup).I can happily add and retrieve items using find() as indicated. > > > > However, if I use the =* operator as indicated and there is no > > matching record a memory error occurs. > > > > Therefore I need to assign the find result to an iterator and check > > for end(). Can anyone tell me what type this iterator should be? I've > > tried many combinations non of which compile. > > There are several syntaxes to get to the type > of the iterator: > > your_container_type::nth_index<N>::type::iterator > your_container_type::index<Tag>::type::iterator > your_container_type::nth_index_iterator<N>::type > your_container_type::index_iterator<Tag>::type > > Where N is the 0-based ordinal of the index you're > interested in. If the index is tagged, you can also > use the <Tag> variations. > Does this help? Thanks for using Boost.MultiIndex! > > Joaquín M López Muñoz > Telefónica, Investigación y Desarrollo >

1 0

Boost.Filesystem DLL builds on Mingw
by Alo Sarv 06 Dec '05

06 Dec '05

The topic itself is already few months old, namely the fact that Boost.Filesystem library breaks on Mingw in DLL builds. As I see from regression tests, this issue hasn't been fixed yet. The reason I'm bringing this up again is that while originally it was concluded that static builds should be used on Mingw instead of DLL builds, it is becoming an increasing problem for me, since default_name_check doesn't work across DLL boundaries when B.FS is linked statically to one of the DLL's, which results unexpected exceptions being thrown all over my codebase unless I explicitly construct paths using native name-checker, but tracking all those places is a constant headache. Is there any plans on addressing this issue, or are there any additional workarounds to have default_name_check functioanlity working across DLL boundaries when Boost.Filesystem is linked statically? My experience has been that mixing dynamic and static libraries is a really bad idea... Alo Sarv

3 2

[boost][lambda] additional placeholders
by Noel Belcourt 06 Dec '05

06 Dec '05

HI, I'm trying to extend the number of placeholders in boost lambda 1.33.0. There are three available by default and I need at least one more (_4) . I've followed the pattern establish for _3 to define _4, modifying the following files along the way. // lambda/core.hpp boost::lambda::placeholder3_type free3 = boost::lambda::placeholder3_type(); boost::lambda::placeholder4_type free4 = boost::lambda::placeholder4_type(); boost::lambda::placeholder3_type& _3 = free3; boost::lambda::placeholder4_type& _4 = free4; // lambda/detail/lambda_functors.hpp template<> struct placeholder<FOURTH> { template<class SigArgs> struct sig { typedef typename detail::get_element_or_null_type<3, SigArgs>::type type; }; template<class RET, CALL_TEMPLATE_ARGS> RET call(CALL_FORMAL_ARGS) const { CALL_USE_ARGS; return c; } }; typedef const lambda_functor<placeholder<THIRD> > placeholder3_type; typedef const lambda_functor<placeholder<FOURTH> > placeholder4_type; // lambda/detail/arity_code.hpp enum { NONE = 0x00, // Notice we are using bits as flags here. FIRST = 0x01, SECOND = 0x02, THIRD = 0x04, FOURTH = 0x08, EXCEPTION = 0x10, RETHROW = 0x20}; So now _4 is defined but I get compilation errors from boost/function/function_template.hpp when I attempt to use _4. Is there some change necessary to either lambda placeholders or to boost function to get it to work correctly? Thanks, -- Noel Belcourt // With the changes above, this code fails with the message below. #include <boost/function.hpp> #include <boost/lambda/bind.hpp> using namespace boost; using namespace boost::lambda; typedef function<void (int, int, double, double)> func_t; template <class T1, class T2, class T3, class T4> struct A { template <class R> A(void (R::*required)(T1, T2, T3, T4), R *r) : u(bind(required, r, _1, _2, _3, _4)) {} func_t u; }; struct B { void f(int, int, double, double); }; int main(int, char *[]) { B b; A<int, int, double, double> a(&B::f, &b); return 0; } This is the error message from CW 9.6 on Darwin Error : call of non-function (point of instantiation: 'main(int, char **)') (instantiating: 'A<int, int, double, double>::A<B>(void (B::*)(int, double, double), B *)') (instantiating: 'boost::function4<void, int, int, double, double, std::allocator<void>>::function4 `base constructor'<boost::lambda::lambda_functor<boost::lambda:: lambda_functor_base<boost::lambda::action<6, boost::lambda::function_action<6, boost::lambda::detail::unspecified>>, boost::tuples::tuple<void (B::*const )(int, double, double), B *const , const boost::lambda::lambda_functor<boost::lambda::placeholder<1>>, const boost::lambda::lambda_functor<boost::lambda::placeholder<2>>, const boost::lambda::lambda_functor<boost::lambda::placeholder<4>>, const boost::lambda::lambda_functor<boost::lambda::placeholder<8>>, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type>>>>(boost::lambda::lambda_functor<boost:: lambda::lambda_functor_base<boost::lambda::action<6, boost::lambda::function_action<6, boost::lambda::detail::unspecified>>, boost::tuples::tuple<void (B::*const )(int, double, double), B *const , const boost::lambda::lambda_functor<boost::lambda::placeholder<1>>, const boost::lambda::lambda_functor<boost::lambda::placeholder<2>>, const boost::lambda::lambda_functor<boost::lambda::placeholder<4>>, const boost::lambda::lambda_functor<boost::lambda::placeholder<8>>, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type>>>, int)') (instantiating: 'boost::function4<void, int, int, double, double, std::allocator<void>>::assign_to<boost::lambda::lambda_functor<boost:: lambda::lambda_functor_base<boost::lambda::action<6, boost::lambda::function_action<6, boost::lambda::detail::unspecified>>, boost::tuples::tuple<void (B::*const )(int, double, double), B *const , const boost::lambda::lambda_functor<boost::lambda::placeholder<1>>, const boost::lambda::lambda_functor<boost::lambda::placeholder<2>>, const boost::lambda::lambda_functor<boost::lambda::placeholder<4>>, const boost::lambda::lambda_functor<boost::lambda::placeholder<8>>, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type>>>>(boost::lambda::lambda_functor<boost:: lambda::lambda_functor_base<boost::lambda::action<6, boost::lambda::function_action<6, boost::lambda::detail::unspecified>>, boost::tuples::tuple<void (B::*const )(int, double, double), B *const , const boost::lambda::lambda_functor<boost::lambda::placeholder<1>>, const boost::lambda::lambda_functor<boost::lambda::placeholder<2>>, const boost::lambda::lambda_functor<boost::lambda::placeholder<4>>, const boost::lambda::lambda_functor<boost::lambda::placeholder<8>>, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type>>>)') (instantiating: 'boost::function4<void, int, int, double, double, std::allocator<void>>::assign_to<boost::lambda::lambda_functor<boost:: lambda::lambda_functor_base<boost::lambda::action<6, boost::lambda::function_action<6, boost::lambda::detail::unspecified>>, boost::tuples::tuple<void (B::*const )(int, double, double), B *const , const boost::lambda::lambda_functor<boost::lambda::placeholder<1>>, const boost::lambda::lambda_functor<boost::lambda::placeholder<2>>, const boost::lambda::lambda_functor<boost::lambda::placeholder<4>>, const boost::lambda::lambda_functor<boost::lambda::placeholder<8>>, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type>>>>(boost::lambda::lambda_functor<boost:: lambda::lambda_functor_base<boost::lambda::action<6, boost::lambda::function_action<6, boost::lambda::detail::unspecified>>, boost::tuples::tuple<void (B::*const )(int, double, double), B *const , const boost::lambda::lambda_functor<boost::lambda::placeholder<1>>, const boost::lambda::lambda_functor<boost::lambda::placeholder<2>>, const boost::lambda::lambda_functor<boost::lambda::placeholder<4>>, const boost::lambda::lambda_functor<boost::lambda::placeholder<8>>, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type>>>, boost::detail::function::function_obj_tag)') (instantiating: 'boost::detail::function::void_function_obj_invoker4<boost::lambda:: lambda_functor<boost::lambda::lambda_functor_base<boost::lambda:: action<6, boost::lambda::function_action<6, boost::lambda::detail::unspecified>>, boost::tuples::tuple<void (B::*const )(int, double, double), B *const , const boost::lambda::lambda_functor<boost::lambda::placeholder<1>>, const boost::lambda::lambda_functor<boost::lambda::placeholder<2>>, const boost::lambda::lambda_functor<boost::lambda::placeholder<4>>, const boost::lambda::lambda_functor<boost::lambda::placeholder<8>>, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type>>>, void, int, int, double, double>::invoke(boost::detail::function::any_pointer, int, int, double, double)') function_template.hpp line 136 BOOST_FUNCTION_RETURN((*f)(BOOST_FUNCTION_ARGS)); Error : call of non-function (instantiating: 'boost::detail::function::void_function_obj_invoker4<boost::lambda:: lambda_functor<boost::lambda::lambda_functor_base<boost::lambda:: action<6, boost::lambda::function_action<6, boost::lambda::detail::unspecified>>, boost::tuples::tuple<void (B::*const )(int, double, double), B *const , const boost::lambda::lambda_functor<boost::lambda::placeholder<1>>, const boost::lambda::lambda_functor<boost::lambda::placeholder<2>>, const boost::lambda::lambda_functor<boost::lambda::placeholder<4>>, const boost::lambda::lambda_functor<boost::lambda::placeholder<8>>, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type>>>, void, int, int, double, double>::invoke(boost::detail::function::any_pointer, int, int, double, double)') function_template.hpp line 136 BOOST_FUNCTION_RETURN((*f)(BOOST_FUNCTION_ARGS));

2 2

Automatically including libaries
by Chris Morley 06 Dec '05

06 Dec '05

Hi, this is a how-is-it-done question rather than a problem. Ive learnt a lot about c++ from using boost, but this one I just cant work out. I installed boost and it dumped all the libraries in c\boost\lib.Now I am slightly confused how I'm able to simply reference a header file in c:\boost\include\blahblah yet I don't have to include the specific libraries... somehow its done for me?! This is using visual studio, and whenever I have built lib files I have to include the header file as usual, but also have to explicitly drag the lib file into the project (or under the required libraries in the linker tab). Any idea how this is done? Would love to be able to do this with my libs! Cheers, Chris

5 4

[Announce] Boost 1.33.1 released
by Douglas Gregor 06 Dec '05

06 Dec '05

Boost 1.33.1, the latest version of peer-reviewed, portable C++ libraries, has been released. This is a bug fix release addressing many small problems with the 1.33.0 release. It is a recommended upgrade for all users of Boost 1.33.0. Boost is available at http://www.boost.org Updated Libraries include: * Any Library: Cast to reference types introduced in 1.33.0 is now documented on any_cast documentation page. * Config Library: Don't undef BOOST_LIB_TOOLSET after use. * Boost.Python: o The build now assumes Python 2.4 by default, rather than 2.2 o Support Python that's built without Unicode support o Support for wrapping classes with overloaded address-of (&) operators * Smart Pointer Library: Fixed problems under Metrowerks CodeWarrior on PowerPC (Mac OS X) with inlining on, GNU GCC on PowerPC 64. * Regex Library: Fixed the supplied makefiles, and other small compiler specific changes. Refer to the regex history page for more information on these and other small changes. * Iostreams Library: Improved the interface for accessing a chain's components, added is_open members to the file and file descriptor devices, fixed memory-mapped files on Windows, and made minor changes to the documentation. * Functional/Hash Library: Fixed the points example. * Multi-index Containers Library: Fixed a problem with multithreaded code, and other minor changes. Refer to the library release notes for further details. * Graph Library: o Fixed a problem with the relaxed heap on x86 Linux (fixes bug in dijkstra_shortest_paths). o Fixed problems with cuthill_mckee_ordering and king_ordering producing no results. o Added color_map parameter to dijkstra_shortest_paths. * Signals Library: Fixed problems with the use of Signals across shared library boundaries. * Thread library: read_write_mutex has been removed due to problems with deadlocks. * Wave library (V1.2.1) Fixed a couple of problems, refer to the change log for further details. Supported Compilers Boost is tested on a wide range of compilers and platforms. Since Boost libraries rely on modern C++ features not available in all compilers, not all Boost libraries will work with every compiler. The following compilers and platforms have been extensively tested with Boost, although many other compilers and platforms will work as well. For more information, see the regression test results. New for this release: Support for building with the newest STLport-5.0 was added. The support includes building with MinGW Runtime 3.8 plus STLport-5.0 improved to support wide character operations. Apple GCC 4.0, HP Tru64 C++, and Microsoft Visual C++ 8.0 are supported platforms. We have added an experimental autoconf-like configure script for Unix-like systems: run configure --help for more information. * Apple GCC 3.3, 4.0 on Mac OS X. * Borland C++ 5.6.4 on Windows. * GNU C++ 2.95.3 (with and without STLport), 3.2.x., 3.3.x, 3.4.x, 4.0.x on Windows, Linux and Solaris. * HP C++ for Tru64 UNIX 7.1. * Intel C++ 8.1, 9.0 on Windows, Linux. * Metrowerks CodeWarrior 8.3, 9.4, 9.5 on Mac OS X and Windows. * Microsoft Visual C++ 6.0 (sp5, with and without STLport), 7.0, 7.1, 8.0. Note: Boost does not support the non-standard "Safe" C++ Library shipping with Visual C++ 8.0, which may result in many spurious warnings from Boost headers and other standards- conforming C++ code. To suppress these warnings, define the macro _SCL_SECURE_NO_DEPRECATE. Acknowledgements Douglas Gregor managed this release. A great number of people contributed their time and expertise to make this release possible. Special thanks go to Aleksey Gurtovoy and Misha Bergal, who managed to keep the regression testing system working throughout the release process; David Abrahams, Beman Dawes, Aleksey Gurtovoy, Bronek Kozicki, Rene Rivera and Jonathan Turkanis for greatly improving the quality of this release; Rene Rivera for the new Boost web page design; and Zoltan "cad" Juhasz for the new Boost logo.

1 0

[wave] bug report for wave
by Andreas Sæbjørnsen 05 Dec '05

05 Dec '05

When preprocessing the code #define $jack int test; $jack using any preprocessor using the wave library, in this case the samples/lexed_tokens/lexed_tokens preprocessor , gives the following error: PP_DEFINE (#369) at test.C ( 1/ 1): >#define< SPACE (#393) at test.C ( 1/ 8): > < lexed_tokens: /home/saebjornsen1/projects/boost/boost/wave/token_ids.hpp:497: boost::wave::util::flex_string<char, std::char_traits<char>, std::allocator<char>, boost::wave::util::CowString<boost::wave::util::AllocatorStringStorage<char, std::allocator<char> >, char*> > boost::wave::get_token_name(boost::wave::token_id): Assertion `id < T_LAST_TOKEN-T_FIRST_TOKEN' failed. Aborted using the preprocesor cpp (from the gcc team) I get (as cpp test.C): # 1 "test.C" # 1 "<built-in>" # 1 "<command line>" # 1 "test.C" int test; I believe the problem lies in that the lexer does not recognize the '$' as a valid character within the name of macro definition. Thanks Andreas Saebjoernsen

6 14

[Serialization] Pure binary archive available?
by Chris . 05 Dec '05

05 Dec '05

Hi, the serialization library is almost what im after. My only problem is that in the archive output additional data is added to the start of the archive (for example "22 serialization::archive" for text files). Is there any way of disabling this? In my case, I require a pure binary archive. Ideally i would like to write one if one doesnt exist but i'm not sure if i have time, depending on how hard it would be. How hard would it be do make my own archive type, where by i could set the endian field to convert bigendian to littleendian depending on what the user defines the 'archive endianess' to be on archive construction? I have done this with my own serialization library, however i dont want to extend that because it only handles c++ primitives and dealing with pointers things start getting horrible very very quickly! Thanks in advance. Chris _________________________________________________________________ MSN Messenger 7.5 is now out. Download it for FREE here. http://messenger.msn.co.uk

4 4

libboost_unit_test_framework-vc71-mt-s-1_33.lib?
by Mingjun Huang 05 Dec '05

05 Dec '05

I have built boost using: bjam "-sBUILD=release <runtime-link>dynamic <threading>multi" "-sTOOLS=vc-7_1" but I can not find the library file: libboost_unit_test_framework-vc71-mt-s-1_33.lib can anyone give me a hand? Thanks so much! On 12/3/05, gast128 <gast128(a)hotmail.com> wrote: > > Mingjun Huang <mingjun.huang <at> gmail.com> writes: > > > > > > > Hello, I am a newbie for Boost. Could anyone give me some directions on > how > to build boost on my PC with Visual Studio .NET 2003 installed? Thanks a > lot! > > > > Best, > > -Mingjun > > > > > > _______________________________________________ > > Boost-users mailing list > > Boost-users <at> lists.boost.org > > http://lists.boost.org/mailman/listinfo.cgi/boost-users > > > or http://www.codeproject.com/tips/Building_boost_libraries.asp > > > _______________________________________________ > Boost-users mailing list > Boost-users(a)lists.boost.org > http://lists.boost.org/mailman/listinfo.cgi/boost-users

3 2

[Serialization] Compile error in heap_allocator.invoke in MSVC8 debug mode
by Tim Murray 05 Dec '05

05 Dec '05

Hi, I have successfully compiled the boost libs for the serialization library using bjam and I am now trying to make use of it in my project. I am building my project in MSVC8. It has successfully compiled and run in Release mode, but I am getting a compiler error in Debug mode on the same code and am at a loss as to what the problem is. The compiler error I am getting is: iserializer.hpp(252) : error C2065: '()' : undeclared identifier Here's a bit from the template stack trace: ...iserializer.hpp(252) : error C2544: expected ')' for operator '()' ...iserializer.hpp(251) : while compiling class template member function 'World::CWorld *boost::archive::detail::heap_allocator<T>::invoke(void)' 1> with 1> [ 1> T=World::CWorld 1> ] The following is the class this is complaining about: namespace World { class CWorld { friend class boost::serialization::access; template<class Archive> void save(Archive & ar, const unsigned int version) const; template<class Archive> void load(Archive & ar, const unsigned int version); BOOST_SERIALIZATION_SPLIT_MEMBER() public: ~CWorld(); static CWorld* getWorld(){ return m_world; } static bool loadWorld(std::string filename); static bool saveWorld(std::string filename); static bool unloadWorld(); protected: CWorld(); static CWorld *m_world; }; } And the source of the error traces back to the following member function: bool CWorld::loadWorld(std::string filename) { if(m_world) return false; m_world = new CWorld(); // create and open an archive for input std::ifstream ifs(filename.c_str(), std::ios::binary); boost::archive::text_iarchive ia(ifs); // read class state from archive ia & *m_world; //!!!this is the line that the error traces to return true; } Like I said - this code compiles fine under Release mode, but this error keeps showing up on Debug mode. Any ideas on what might be wrong? And if you need more information, just ask. Thanks, Tim Murray

2 3

[Serialization] Resolved problems with vs 7.1 -- kind of
by David Parks 04 Dec '05

04 Dec '05

First off, I apologize for not replying directly to my last message but I'm not even sure it's been posted yet -- as I don't have permission to post yet (the 'first message is moderated' deal). Anyway, I wasn't able to make the example in my last post work with any sane process but I did get it to work by doing the following: 1) splitting the stuff into 3 files -- the main driver, the class header, and the class .cpp. I put both classes in the class files. 2) Including the */archive/* files in the class cpp immediately followed by export.hpp... then the class header. 3) Including the same archive headers in the class header followed by serialization.hpp (I'm sure this could be done lighter but...) 4) Including only the class header in main. 5) BOOST_CLASS_EXPORT(derived) in the class cpp. 6) This is where it starts to diverge from any information in the tutorials and documentation. First, I had to switch from text to xml. I'm not positive but, if I couldn't get it to work after 12 straight hours, I'd guess the text interface is broken. 7) You will get a pretty incorrect error (in the header comments) if you don't call the base class in the derived class serialization (ar & BOOST_SERIALIZATION_BASE_OBJECT_NVP(base);). This is not ideal because in many instances, like mine, you might not care about the bases serialization if you have a derived class... the derived class is 'smarter'. But this I can deal with. What I needed to do was serialize a vector of objects of some base class -- you know, like the useless circles and squares of shapes example in every intro C++ book. The documentation could use this as an example -- it has to be one of the most common uses for a serializer. Oh, one goofy note that thankfully only took a couple of minutes to catch: namespaces aren't all the rage but if you make big use of them (like me), beware of BOOST_CLASS_EXPORT... it takes a flash of inspiration to realize that it's going to try to put colons in your XML tags. Even more tricky is the situation where you are calling, say, the base-class with BOOST_SERIALIZATION_BASE_OBJECT_NVP. It stringizes this without telling you -- it has to. But if you do this ar & BOOST_SERIALIZATION_BASE_OBJECT_NVP(A::B) you will get an error but this (thankfully) using namespace A; ar & BOOST_SERIALIZATION_BASE_OBJECT_NVP(B); works. I have no idea how to make this friendly. Best, - David

2 1