- Boost - lists.boost.org

[DateTime] warnings patch
by Juergen Hunold 20 Feb '11

20 Feb '11

Hi, please find a patch removing a clang warning from gregorian _calendar.ipp. The warning is warning: equality comparison with extraneous parentheses [-Wparentheses] note: use '=' to turn this equality comparison into an assignment note: remove extraneous parentheses around the comparison to silence this warning The right fix is to remove the extra parentheses. See the patch for further details. Okay to commit? Yours, Jürgen -- * Dipl.-Math. Jürgen Hunold ! Ingenieurgesellschaft für * voice: ++49 511 262926 57 ! Verkehrs- und Eisenbahnwesen mbH * fax : ++49 511 262926 99 ! Lister Straße 15 * juergen.hunold(a)ivembh.de ! www.ivembh.de * * Geschäftsführer: ! Sitz des Unternehmens: Hannover * Prof. Dr.-Ing. Thomas Siefer ! Amtsgericht Hannover, HRB 56965 * PD Dr.-Ing. Alfons Radtke !

1 0

[optionał] warnigs patch
by Juergen Hunold 20 Feb '11

20 Feb '11

Hi, please find a small patch removing some gcc "unused variable" warnings attachted. Okay to commit? Yours, Jürgen -- * Dipl.-Math. Jürgen Hunold ! Ingenieurgesellschaft für * voice: ++49 511 262926 57 ! Verkehrs- und Eisenbahnwesen mbH * fax : ++49 511 262926 99 ! Lister Straße 15 * juergen.hunold(a)ivembh.de ! www.ivembh.de * * Geschäftsführer: ! Sitz des Unternehmens: Hannover * Prof. Dr.-Ing. Thomas Siefer ! Amtsgericht Hannover, HRB 56965 * PD Dr.-Ing. Alfons Radtke !

1 0

[trunk] access denied
by Joachim Faulhaber 20 Feb '11

20 Feb '11

Hi, I am unable to commit changes to trunk. Attempts (using tortoise-SVN on windows) result in: Error: access to '/svn/boost/!svn/act/91b0fcb8-4a55-a041-8d53-63a889463250' forbidden can someone help? Regards, Joachim -- Interval Container Library [Boost.Icl] http://www.joachim-faulhaber.de

1 1

[quickbook] issues writing the documentation for has_operator_xxx
by Frédéric Bron 19 Feb '11

19 Feb '11

I am trying to write the documentation of the operator traits using quickbook. You can have a look at it here: http://www.boostpro.com/vault/index.php?action=downloadfile&filename=type_t… untar and open type_traits/libs/type_traits/doc/html/boost_typetraits/category/value_traits/operators.html I have encountered some issues: * syntax highlighting is not working (c++ code is not in color, just in courrier font) * tables have no lines around cells, header has no special formatting as in the documentation of quickbook * table columns are two large because they adjust to their content. I would like to have some new lines inside some cells (in particular header cells) but the only way I found was to have a new paragraph which creates huge vertical space between lines. In fact, the best would be to set the column width but I did not find how to do that. * I was not able to put macros in table captions. * `code` is not recognized in table caption Maybe somebody could help me, Apart from that, quickbook is easy to use and the documentation is easy to follow. Regards, Frédéric

3 5

Requesting review manager for the variadic_macro_data library
by Edward Diener 19 Feb '11

19 Feb '11

I am looking for a review manager for my variadic_macro_data library in the Boost sandbox. It has been added to the review queue by Ron Rivera and I have been asked to try to find someone to serve as review manager for the library. The variadic_macro_data library adds support and functionality for variadic macros to Boost as well as integrating variadic macros with the Boost PP library without changing the latter library in any way. The library comes with full documentation in both HTML and PDF format, as well as a series of tests. The documentation can also be regenerated from the jamfile and the tests can be run from the jamfile. The library has been tested extensively with gcc ( MingW) and VC++ on Windows and should work with any C++ compiler which supports variadic macros and does not define BOOST_NO_VARIADIC_MACROS in its compiler configuration in Boost.

1 0

[BGL] Typo in transitive_reduction.hpp
by Shaun Jackman 19 Feb '11

19 Feb '11

There appears to be a typo in transitive_reduction.hpp where a semicolon should be a comma. Cheers, Shaun --- graph/transitive_reduction.hpp (revision 68995) +++ graph/transitive_reduction.hpp (working copy) @@ -99,7 +99,7 @@ transitive_reduction(const Graph& g, Gra { //and run through all vertices in topological order typename std::vector<Vertex>::reverse_iterator - rit = topo_order.rbegin(); + rit = topo_order.rbegin(), rend = topo_order.rend(); for(; rit != rend; ++rit ) { //looking if they are successors of *it

2 1

program_options negative numbers
by Andrzej Zielinski 18 Feb '11

18 Feb '11

I am using boost::program_options and found a problem with passing a series of positive/negative numbers. i.e myProgram.out --system 0 -2 2 -3 Similar problem like in: http://stackoverflow.com/questions/4107087/accepting-negative-doubles-with-… I do not want to disable short options. I want to make quotes working. So when I call myProgram.out --system '0 -2' error: in option 'system': invalid option value myProgram.out --system 0 -2 error: unknown option -2 What quotation do you mean ? I am using bash, on CYGWIN and in linux Let me know your answer. Regards Andrzej.

2 2

[interfaces] Boost Interface Library (2004?)
by Daniel Larimer 18 Feb '11

18 Feb '11

I recently ran across the unofficial Boost Interface Library (http://www.coderage.com/interfaces) but it appears that it is was never adopted nor much discussed since I joined this mailing list. Boost.Interfaces provides a macro-based Interface Definition Language (IDL) which can be used to define C++ class types called interfaces. An interface is a lightweight value type associated with a set of named function signatures. An interface instance can be bound at runtime to any object which implements the interface, i.e., to any object of a type with accessible non-static member functions having the same name and signature as the set of functions associated with the interface. The functions of the bound object can then be invoked through the interface instance using the �dot� operator. Binding is completely non-intrusive: the object's type need not declare any virtual functions or derive from any particluar base class. Interfaces were described in a September 2004 C/C++ Users Journal article by Christopher Diggins. After looking through the library I concluded that I did not like how it was implemented. Too many macros, unnatural syntax. I guess few people liked it enough for it to be kept up to date (6+ years old now). I have also looked at the Boost Mirror library which provides reflection of just about everything at the expense of some nasty macros and no clear path toward defining dynamic interfaces based upon the reflected type information. I think the goal of the interface library should be a more flexible/powerful version of "boost::any" that allows you to define the interface of the object stored in the 'any'. In this way it takes type erasure to a new level. That said, I have a need for developing an interface library that abstracts the differences between direct pointer access, RPC, and asynchronous inter-thread communication. So I have developed and tested a new 'api' for defining interfaces with the hope that it would be considered worthwhile for boost. Goals / Non-Goals 1) Define Interfaces in Natural C++ Syntax 2) Provide the ability to define 'dynamic' implementations of an interface for calling RPC, scripting language interface, etc. 3) Objects that implement 'interfaces' should be long-lasting 'actors' where overhead of creating/copying/destroying the interface along with any memory usage is of secondary importance to the ease of defining dynamic interfaces and achieving 'type erasure'. 4) Ideally each member of an interface is a function object that can be bound to anything. I am interested in feedback on what the API/features should be of a generic interface library to improve upon BIL. Should the interface definition classes be in a namespace such as idl_definition or should the BOOST_IDL_INTERFACE macro place the interface type in an 'idl' namespace? Example: namespace idl_definition { struct SomeBase { // these methods need not be implemented anywhere as they are never called. std::string name()const; }; struct Shape : public SomeBase { double area(int); std::string type(); std::string my_mem; }; } BOOST_IDL_INTERFACE( SomeBase, BOOST_PP_NIL, (name) ) BOOST_IDL_INTERFACE( Shape, (SomeBase,BOOST_PP_NIL), (area) (type) (my_mem) ) class print_api_visitor : public boost::idl::visitor<print_api_visitor> { public: template<typename InterfaceName, typename M> bool accept( M& m, const char* name ) { std::cerr << boost::idl::get_typestring<InterfaceName>::str() << "::" << name << " " << boost::idl::get_typestring<typename M::signature>::str() << (M::is_const ? "const" : "") << std::endl; return true; } }; class Circle { public: std::string name()const{ return "CircleName"; } double area(int v) { return v*3.1415; } std::string type() { return "circle"; } std::string my_mem; }; int main( int argc, char** argv ) { boost::shared_ptr<Circle> c(new Circle()); Shape s = c;//Circle(); //new Circle(); s.my_mem = std::string("HelloWOrld"); std::string tmp = s.my_mem; std::cerr<<"type: "<<s.type() << std::endl; std::cerr<<"area: "<<s.area(3) << std::endl; std::cerr<<"area: "<<*s.my_mem << std::endl; std::cerr<< "9*pi = "<<boost::idl::make_delegate( c.get(), Shape::__idl__area::get_member_on_type<Circle>() )(9) << std::endl; std::cerr<< "my_mem = "<< c.get()->*Shape::__idl__my_mem::get_member_on_type<Circle>() << std::endl; std::cerr<< "my_mem = "<< c.get()->*s.my_mem.get_member_on_type<Circle>() << std::endl; std::cerr<<"print api!\n"; print_api_visitor papi; papi.start(s); Circle* c2 = new Circle; c2->my_mem = "Circle2!!!"; boost::idl::set_delegate_visitor<Circle> sd(c2); sd.start(s); std::cerr<<"c->area: "<< *s.my_mem << std::endl; return 0; } Here is an example of the visitor used to setup the delegate: template<typename T> class set_delegate_visitor : public boost::idl::visitor<set_delegate_visitor<T> > { public: set_delegate_visitor( T* self = 0) :m_self(self){} template<typename InterfaceName, typename M> bool accept( M& m, const char* name ) { m.set_delegate( m_self, M::template get_member_on_type<T>() ); return true; } private: T* m_self; }; Output ==================== type: circle area: 9.4245 area: HelloWOrld c->area: HelloWOrld sizeof(s): 120 9*pi = 28.2735 my_mem = HelloWOrld my_mem = HelloWOrld print api! SomeBase::name std::string()const Shape::area double(int32_t) Shape::type std::string() Shape::my_mem std::string c->area: Circle2!!!

6 14

[ICL] cardinality of float interval
by John Reid 18 Feb '11

18 Feb '11

cardinality( interval< float >( 1, 5 ) ) == 18446744073709551615 Can this be true? Is this by design?

3 3

shared_from_this() fails from boost.serialization load()
by Allan Johns 18 Feb '11

18 Feb '11

Hi, Consider class A, which contains an instance of class B, which in turn contains a weak reference to its parent A instance (note: pseudocode): class A; class B { weak_ptr<A> m_parent; } class A { shared_ptr<B> m_child; } I have a case where I am boost-serializing class A, and its load() method looks like so: template<class Archive> void A::load(Archive& ar, const unsigned int) { ar & m_child; m_child->m_parent = shared_from_this(); } Note that B does *not* serialize its m_parent member (this is by design). The problem I have is that the shared_from_this() call in A::load() fails, even though I am guaranteeing that A is serialized via a shared_ptr. Presumably boost.serialize is not placing the default-constructed instance of A into its containing shared_ptr<A>, before calling A::load(). My question is, is there any reason why boost.serialize couldn't deal with this special case, which would allow me to call shared_from_this() from load()? I don't have a workaround for this in my code, other than to resort to a raw ptr for B::m_parent. ps - I suppose you could argue that since you can't do this in A's constructor, you shouldn't be able to do it in its load() function either. However I do have a legitimate case where I need to do this... I can extrapolate on the whole situation if necessary, but I've left it out here in the interests of simplicity). Thanks boosters, Allan

1 1