- Boost-users - lists.boost.org

Re: [Boost-users] [BULK] Re: [Test] Running a specific Test Suite
by Sohail Somani 10 Jan '06

10 Jan '06

> -----Original Message----- > From: boost-users-bounces(a)lists.boost.org > [mailto:boost-users-bounces@lists.boost.org] On Behalf Of > Gennadiy Rozental > Sent: Tuesday, January 10, 2006 11:03 AM > To: boost-users(a)lists.boost.org > Subject: [BULK] Re: [Boost-users] [Test] Running a specific Test Suite > Importance: Low > > > > Is there a flag I can pass to the test program or any other > way to run > > only a specific Test Suite, ignoring the other ones? > > Hopefully by the end of this release cycle I will add an > ability to run tests by name, which should satisfy this request. I am not yet a user of boost unit test, but is there a way of listing all the tests/targets as well? That could be very useful. I still wish this was a feature in scons!

2 1

iterators 2
by jens-theisen＠gmx.de 10 Jan '06

10 Jan '06

Hello, Thanks for the references, I briefly looked at them (Views and any_iterator) and wasn't aware of them beforehand. I'm not really looking for a solution to a particular problem I might have, but rather wondering if there is not something very basic missing from C++. In many other programming languages there is a good notion for talking about a collection of things conveniently. Python and the .NET languages have this with their iterator concepts. C++ only has it's iterators currently, which is not always a very good solution for reasons alread said. Especially, for the starting problem of my original posting, there is no natural solution. True, there is any_iterator: We can define the virtual function in my original problem as typedef boost::iterator_range< adobe::any_iterator< ... > > ret_range; class X : ... { virtual ret_range give_stuff() const; ... It's still a monstrosity, however, given that any_iterator has 4 template parameters, is derived from iterator_facade, and the iterator_range doubles this even. Presumably, a library author would quickly write his own little nonstandard iterator interface himself and have the virtual function return this instead. It would be nice to have something lightweight enough to promote its use a bit like boost::shared_ptr has become "the obvious way" of dealing with dynamic objects in C++. What I like to have is something more lightweight, along the following requirements: - the "notion" of a collection of things as a concrete type rather than a concept - fast to compile, simple error messages, fun to use, it should be the obvious choice for a library programmer to give collections of things (rather than awkward input iterators derived from iterator_facade) - a toolbox of free functions to combine them in all the ways I can do with linked lists in functional languages - performance and memory usage don't have to be optimal if we're just talking about the cost of a virtualisation A while ago, I made a first attempt on this, making the following design decisions: - There is no concept, but just one templated type: class list< typename reference >; which has various implementations and is, despite the name, conceptually a forward traversal iterator which is aware of the end of its range. - lists are constructed by using a number of free functions only, notably - the make_list overload set, implementing construction from stuff like iterators, containers, etc. and - map, filter, concat, etc. for combining lists in useful ways. - lists have conversion operators along the line of the conversion of their underlying reference type, which especially enables list< T const& > to be used where list< T > is expected. - lists are not iterators, but they can export that behaviour. If this feature isn't used, iterator_facade don't have to be present. (If viewed as iterators, their end is a default constructed list, as usual.) The most important thing that's lacking, however, is that lists are conceptually forward traversal only. Actually, I'm not entirely convinced that it would really be necessary to have more than that (or less). My impression is that virtualisation for more than forward traversal is less dearly needed. I can only think of somewhat contrived examples. What do you think? If other forms of traversal are important, this would complexify all of this quite a bit. Presumably there would be a class hierarchy reflecting the traversal concepts, and possibly each such hiearchy for the implementations as well. But what should free function like map return then? There would have to be overloads for each of the traversal types, and there are already other reasons for overloads. How do people think on this matter? What direction to go? Is this worth spending time on? Cheers, Jens

2 2

[Test] Running a specific Test Suite
by Edson Tadeu 10 Jan '06

10 Jan '06

Is there a flag I can pass to the test program or any other way to run only a specific Test Suite, ignoring the other ones? Thanks in advance

2 1

Boost Serialization: extended_type_info_no_rtti not working...
by RIVASSEAU Jean Noel 10 Jan '06

10 Jan '06

Hello, I am trying to learn the Boost Serialization Library. Although I like the fundamental principles of the library, using the library so far has proven a nightmare for my project. To be more precise: I need to serialize objects via pointers to base class. And I need to do it without RTTI. While using extended_type_info_no_rtti for my classes I always get an "unregistered_class" exception at run time. 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. I also want to report a bug in the documentation: the doc says that you should write: BOOST_CLASS_TYPE_INFO( ClassName, extended_type_info_no_rtti<BaseClassName> ) Although the example test_no_rtti.cpp uses the following syntax: BOOST_CLASS_TYPE_INFO( ClassName, extended_type_info_no_rtti<ClassName> ) I think that the example is right, not the documentation. ) 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. 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) I have looked at the documentation for two days, read absolutely everything and still do not understand. Maybe I should look at the code ??? Thank you Jean-Noël

2 1

Cross compiling boost libraries with gcc and using boost jam to crosscompile third-party library (Jambase problem)
by Vladimir Michl 10 Jan '06

10 Jan '06

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

1 0

[bind] Problem with 1.33.1, g++ 3.3.3
by David Greene 10 Jan '06

10 Jan '06

I'm trying to compile this little program: #include <boost/bind.hpp> #include <iostream> namespace tester { class Test { public: void do_test(void) { std::cout << "Done!" << std::endl; }; }; }; int main(void) { tester::Test x; bind(&tester::Test::do_test, &x, _1)(); return(0); } But I end up with this error (full error trace below): /tools/i686-pc-linux-gnu/include/boost-1_33_1/boost/bind.hpp:63: error: ` void (tester::Test::*)()' is not a class, struct, or union type It looks like somewhere along the way the wrong template specialization is chosen for result type deduction. Am I doing something wrong or is this a known problem? I tried lambda's bind but that also gives an error. It's a different error but I believe it amounts to the same problem. Thanks! -Dave ------------------------ bind.cc:16: instantiated from here /tools/i686-pc-linux-gnu/include/boost-1_33_1/boost/bind.hpp:63: error: ` void (tester::Test::*)()' is not a class, struct, or union type /tools/i686-pc-linux-gnu/include/boost-1_33_1/boost/bind/bind_template.hpp: In instantiation of `boost::_bi::bind_t<boost::_bi::unspecified, void (tester::Test::*)(), boost::_bi::list2<boost::_bi::value<tester::Test*>, boost::arg<1> > >': /tools/i686-pc-linux-gnu/include/boost-1_33_1/boost/bind.hpp:1409: instantiated from `boost::_bi::bind_t<boost::_bi::unspecified, F, typename boost::_bi::list_av_2<A1, A2>::type> boost::bind(F, A1, A2) [with F = void (tester::Test::*)(), A1 = tester::Test*, A2 = boost::arg<1>]' bind.cc:16: instantiated from here /tools/i686-pc-linux-gnu/include/boost-1_33_1/boost/bind/bind_template.hpp:15: error: no type named `type' in `struct boost::_bi::result_traits<boost::_bi::unspecified, void (tester::Test::*)()> ' /tools/i686-pc-linux-gnu/include/boost-1_33_1/boost/bind/bind_template.hpp:18: error: no type named `type' in `struct boost::_bi::result_traits<boost::_bi::unspecified, void (tester::Test::*)()> ' /tools/i686-pc-linux-gnu/include/boost-1_33_1/boost/bind/bind_template.hpp:24: error: no type named `type' in `struct boost::_bi::result_traits<boost::_bi::unspecified, void (tester::Test::*)()> ' /tools/i686-pc-linux-gnu/include/boost-1_33_1/boost/bind/bind_template.hpp:30: error: no type named `type' in `struct boost::_bi::result_traits<boost::_bi::unspecified, void (tester::Test::*)()> ' /tools/i686-pc-linux-gnu/include/boost-1_33_1/boost/bind/bind_template.hpp:30: confused by earlier errors, bailing out make: *** [bind.o] Error 1 Compilation exited abnormally with code 2 at Mon Jan 9 17:08:20

3 3

accessing boost::format's parsing results?
by nospam＠technolumiere.com 10 Jan '06

10 Jan '06

Does anyone know if it is possible to have boost::format parse a printf style format string, and have the results accessible? i.e. given a string like "filename_v%02d.%s", I'd like to be able to parse it and see that there are two arguments, and then retrieve their type. It seems that all the parsing in boost::format is hidden away internally. It would be a shame to have to write my own printf format string parser when I know there is a good one already in there somewhere. AC.

2 1

Profiling Boost Graph Library with gprof
by Dave 10 Jan '06

10 Jan '06

Hello All, I have been trying to profile a few graph algorithms written using Boost Graph Library. I am using gprof for profiling. My graph has 100 vertices. It takes more than 10 minutes to compile, I suspect it is because of the size of the graph. The profile does not show any details though. It only shows the amount of time spent by the profiler. What am I doing wrong? Any help is greatly appreciated! Thanks. __________________________________________ Yahoo! DSL Something to write home about. Just $16.99/mo. or less. dsl.yahoo.com

3 2

Understanding Boost.Mpl Fold Algorithm
by Eduardo Bezerra 10 Jan '06

10 Jan '06

Hi, I'm having a hard time trying to understand what the placeholders _1 and _2 mean in the context of the mpl::fold algorithm. >From the Boost.Mpl Reference manual: typedef vector<long,float,short,double,float,long,long double> types; typedef fold< types , int_<0> , if_< is_float<_2>,next<_1>,_1 > >::type number_of_floats; BOOST_MPL_ASSERT_RELATION( number_of_floats::value, ==, 4 ); Could someone give me some help on this ? Best regards, Eduardo

4 6

Is there a StringBuffer equivalent in Boost library?
by ying lcs 10 Jan '06

10 Jan '06

Is there a StringBuffer equivalent in Boost library? If not, what is the most efficient way to append string? Thank you. __________________________________________ Yahoo! DSL Something to write home about. Just $16.99/mo. or less. dsl.yahoo.com

2 1