- Boost - lists.boost.org

boost::bind result type
by David Sankel 23 Jul '10

23 Jul '10

I'm wondering if there's a way I can generically get the result type of boost bind. I'd like to write something along these lines: template< typename StreamT, typename Sink > typename boost::result_of< boost::Bind( StreamT, boost::arg<1>, Sink ) >::type apSink( StreamT t, Sink sk ) { return boost::bind( t , _1 , sk ); } I'm not interested in a boost::function solution because I require that uses apSink's result can be inlined. Any ideas? Perhaps one of these other bind-like libraries has an answer to this. Thanks, David -- David Sankel Sankel Software www.sankelsoftware.com 585 617 4748 (Office)

5 15

Problem in proto library
by Jorge Lodos Vigil 23 Jul '10

23 Jul '10

Hi The addition of macro BOOST_PROTO_EXTENDS_USING_ASSIGN in literal.hpp broke compilation with /clr option in MSVC. The problem is that the macro is used as BOOST_PROTO_EXTENDS_USING_ASSIGN(literal) and literal is a variable modifier for managed C++. Adding a private typedef: typedef literal<T, Domain> literal_t; and replacing the macro parameter with: BOOST_PROTO_EXTENDS_USING_ASSIGN(literal_t) solves the problem for us. Tested with VS2008. Please note that this problem prevents compilation of xpressive and any other library that uses proto with /clr. Thank you for boost and particularly for proto and xpressive :-) Best regards Jorge

2 1

[GIL] bits64
by fabien.castan＠free.fr 22 Jul '10

22 Jul '10

Hi, 64 bits pixels are interesting for accumulation buffers or internal computations. I think it could be a good thing to add these typedefs in gil. Is there any reason not to do it? Best regards, Fabien Castan

3 2

Re: [boost] [GIL] scoped_channel_value type
by fabien.castan＠free.fr 22 Jul '10

22 Jul '10

>> So if you want to extract this, you will have to special-case >> scoped_channel_value anyway. So in this case you don't need a typedef >> inside. >> You can just define a specialization like this: >> >> Template <typename ChannelValue> >> Struct base_channel_value { >> typedef ChannelValue type; >> }; >> >> Template <typename ChannelValue, typename MinV, typename MaxV> >> Struct base_channel_value<scoped_channel_value<ChannelValue, MinV, MaxV> > >> { >> typedef ChannelValue type; >> }; >> > >I really have to write that one down. I keep on forgetting this trick. Thanks ! Maybe this utility structure can be added (like channel_type, etc.) ?

1 0

[GIL] scoped_channel_value type
by fabien.castan＠free.fr 22 Jul '10

22 Jul '10

Hi, I would like to get the value type of the channels depending on an image view. So I can get the scoped channel type, from MyView type, like this: typedef typename boost::gil::channel_type<MyView>::type MyScopedChannel; But I can't get the primitive type used by the scoped channel. For example, if the type is scoped_channel_value<float,float_zero,float_one>, I can't get the float type. /// \ingroup ScopedChannelValue /// \brief A channel adaptor that modifies the range of the source channel. Models: ChannelValueConcept template <typename BaseChannelValue, // base channel (models ChannelValueConcept) typename MinVal, typename MaxVal> // classes with a static apply() function returning the minimum/maximum channel values struct scoped_channel_value { typedef BaseChannelValue base_channel_t; //< missing typedef //... } So this will allows to use: typedef typename boost::gil::channel_type<MyView>::type::base_channel_t ChannelBaseType; Are you agree to add this typedef ? Best regards, Fabien Castan

3 3

fixed size vector in boost::numeric::ublas?
by Markus Grabner 22 Jul '10

22 Jul '10

Hi all! In boost::numeric::ublas, there exist different vector variants (unbounded and bounded). All of them can be resized dynamically (up to a maximum size defined at compile time in the case of the bounded vector). Therefore the vector class (or the underlying storage array) have a size member which indicates the current size of the vector. However, it would be extremely useful to have a vector of fixed size, i.e., one which can't be resized dynamically, but has its size statically defined at compile time. Such a vector does not require a size member and only consumes N*sizeof(T) bytes of storage, where N is the (static) vector size and T the value type. Many libraries dealing with geometric data (OpenGL and OpenInventor being prominent examples) store their data in compact arrays in their native data types, e.g., the values (x0,y0,z0,x1,y1,z1,x2,y2,z2) stored in consecutive memory locations define three points in 3D space. By means of a fixed size vector, the entire boost::numeric::ublas functionality could be applied to such arrays by a simple reinterpret_cast on each element. This is not possible with the bounded or unbounded vectors since the vector must be constructed before with its size member properly initialized, and the actual vector data must therefore be copied explicitly before use. I tried to create a fixed_array class to implement this proposal (see attachment), it can be used, e.g., to create the equivalent of the OpenInventor "SbVec3f" data type as follows: typedef boost::numeric::ublas::vector<float,fixed_array<float,3> > vec3d_t; It is probably not the cleanest solution, and I skipped the serialization stuff altogether, but it demonstrates an approach how this can be done. What do you think about adding such an extension to improve boost's interoperability with other libraries? Thanks & kind regards, Markus -- Markus Grabner Institute for Computer Graphics and Vision Graz University of Technology, Inffeldgasse 16a/II, 8010 Graz, Austria WWW: http://www.icg.tugraz.at/Members/grabner

2 1

[ref] incompatibility with c++0x
by Andy Venikov 21 Jul '10

21 Jul '10

The latest c++0x FCD defines the single argument constructor for reference_wrapper(T &) as non-explicit. The boost version is explicit. Was it done on purpose? Should it be changed to non-explicit? BTW, I think original standard drafts did have it as explicit since gcc 4.3.3 still defines it as explicit. But in the final draft (as in gcc 4.5) it's non-explicit. I know that boost::reference_wrapper is not the same as std::reference_wrapper, but still it would be nice to have some uniformity. Thanks, Andy.

2 2

info about boost process
by Conoscenza Silente 21 Jul '10

21 Jul '10

Hi All Do you know whether "boost.process" will become part of the boost library at some point? I need some C++ way to start-stop processes and getting the console output produced by them and it seems that this library is doing right that. I see it in the BOOST VAULT that the development is stopped since 2008. Do you know what are the plans for it and if there is some alternative I can use in current/future boost library? Thanks AFG

2 1

[Graph] Problems customizing edge storage for adjacency_list
by Alex Betts 21 Jul '10

21 Jul '10

Hello! I can't seem to use a custom container for storing edge data when using adjacency_list (this is with gcc 4.1.0 on Linux, but it won't work for gcc 4.3.0 either). I understand that I need to create push() and erase() functions for the custom container, but the compiler never seems to see my implementations of these two functions, as it always gives an error like: boost/pending/container_traits.hpp:414: error: no matching function for call to ‘container_category(...)’ ...from the default implementation of push() defined in container_traits.hpp. I've tried moving push() and erase() in and out of the boost::graph_detail namespace, but that doesn't seem to help. I've attached the source for the program in question, & appreciate any help! thanks, -- Alex

2 2

boost graph.
by Giorgio Zoppi 21 Jul '10

21 Jul '10

Hi, I've a problem with multiple links on the same vertexes. For example we've vertex A and vertex B and we want identify two different edges that they connects to these edges, i.e. A-->B with cost 6 A-->B with cost 8 Is there any way to tag or label these links and using the dijkstra algorithm on the graph? Cheers, Giorgio. -- Quiero ser el rayo de sol que cada día te despierta para hacerte respirar y vivir en me. "Favola -Moda".

2 1