- Boost - lists.boost.org

Re: [boost] [Boost-announce] [review][constrained_value] Review of Constrained Value Library begins today
by Daryle Walker 10 Dec '08

10 Dec '08

On Dec 1, 2008, at 7:59 AM, Jeff Garland wrote: > The review of the Robert Kawulak's Constrained Value library begins > today December 1, 2008, and will end on December 10th -- I will be > the review manager. Please post reviews to the developer list. > > Here's the library synopsis: > > The Boost Constrained Value library contains class templates useful > for creating constrained objects. A simple example is an object > representing an hour of a day, for which only integers from the > range [0, 23] are valid values. > > bounded_int<int, 0, 23>::type hour; > hour = 20; // OK > hour = 26; // exception! > > Behavior in case of assignment of an invalid value can be > customized. The library has a policy-based design to allow for > flexibility in defining constraints and behavior in case of > assignment of invalid values. Policies may be configured at compile- > time for maximum efficiency or may be changeable at runtime if such > dynamic functionality is needed. > > The library can be downloaded from the here: > http://rk.go.pl/f/constrained_value.zip > > The documentation is also available online here: > http://rk.go.pl/r/constrained_value > > --------------------------------------------------- > > Please state in your review, whether you think the library should be > accepted as a Boost library. Additionally, please consider the > following aspects in your review of the library: Yes, please accept it. > > - What is your evaluation of the design? It's OK. > - What is your evaluation of the implementation? Fine. I liked the attempts to minimize extra space per object. I didn't like that there were neither tests nor conventional examples. The file where the Quickbook docs took its code examples was the only *.cpp file provided. Fortunately, it's (intentionally) compilable. > - What is your evaluation of the documentation? It's extensive, both the usage (Quickbook) and code (Doxygen) guides. On the usage guide, I don't think the tutorial's "ignore" type does what you think it does. > - What is your evaluation of the potential usefulness of the library? I find restrained types to be useful. > - Did you try to use the library? With what compiler? Did you > have any > problems? Yes, with Mac OS X 10.4 (PowerPC) using XCode. No problems. > - How much effort did you put into your evaluation? A glance? A quick > reading? In-depth study? A day of reading and trying out the examples. > - Are you knowledgeable about the problem domain? Somewhat -- Daryle Walker Mac, Internet, and Video Game Junkie darylew AT hotmail DOT com

2 3

Is there a special reason to use inline before template functions?
by Thomas Klimpel 10 Dec '08

10 Dec '08

Hi, in boost, many template functions (but not all) use inline. (Example from boost/accumulators/framework/accumulator_set.hpp that uses inline: template<typename Args> inline accumulator_visitor<Args> const make_accumulator_visitor(Args const &args) { return accumulator_visitor<Args>(args); } Example from boost/algorithm/minmax.hpp hat doesn't use inline: template <typename T> tuple< T const&, T const& > minmax(T const& a, T const& b) { return (b<a) ? make_tuple(cref(b),cref(a)) : make_tuple(cref(a),cref(b)); } ) Is there a special reason why inline is used for template functions? I would expect that current compilers know better when inlining a function provides a benefit than the programmer. So I guess there is a better reason for using the inline keyword before template function than just speculative performance optimization, but I can't figure it out. Can anybody help me? Most libs only prepend inline before template functions, but ublas prepends nearly every member function with the macro "BOOST_UBLAS_INLINE", which expands to "inline". Is there a reason why ublas uses this macro? Regards, Thomas

7 12

[constrained_value] example
by Neal Becker 10 Dec '08

10 Dec '08

Not a review - I would like to offer my fixed_pt code as an example, and placed it here: http://www.bitbucket.org/nbecker/fixed_pt/src/ Notes: 1) This is a fixed_pt class for run-time parameterization of bit widths. I'm using it to interface with python (so a compile-time parameterization would not be useful) 2) Some others have suggested different semantics for fixed_pt numbers. In particular, there is question about whether arithmetic operations on numbers of some bit-widths should give results of different bit-widths. I've elected to have operands and results have the same widths.

1 0

[config/interprocess] visual C++ express og /Za option
by Thorsten Ottosen 09 Dec '08

09 Dec '08

I got this error when I switch on the /Za option: d:\boost\trunk\boost\interprocess\detail\workaround.hpp(20) : fatal error C1083: Cannot open include file: 'unistd.h': No such file or directory The only thing I did was to add /Za to my Jamroot. The compiler switch is supposed to turn of microsoft extensions. Does anyone have any clues to what is going on? Thanks -Thorsten

3 2

Coroutine
by Stephane Belmon 09 Dec '08

09 Dec '08

What is the status of Giovanni's Coroutine lib? -- Stephane Belmon <sbelmon(a)gmail.com>

1 0

[LibrariesUnderConstruction] new LibrariesUnderConstruction wiki page
by vicente.botet 09 Dec '08

09 Dec '08

Hi, I have created a new wiki page containing some of the libraries under construction for Boost. You can access this page from the Boost Trac wiki https://svn.boost.org/trac/boost/wiki > Projects > Libraries Under Construction or directly https://svn.boost.org/trac/boost/wiki/LibrariesUnderConstruction The contents of this page is by nature incomplete and outdated. Please help to maintain this page updated by modifying it directly (if you have the rights) or posting on the Boost mailing lists boost-AT-lists.boost.org or boost-users-AT-lists.boost.org with the prefix [LibrariesUnderConstruction]. If you're the author of one of these libraries and desire that all or part of the information related to your library be removed or modified, please send a mail or you can do it directly if you prefer. If you're a library author and plan on submitting a library but don't know when it will be ready for review, and you want to include your library in this list, please add it directly (if you have the rights) or send a mail. If you're a library author and plan on submitting a library for review in the next 3-6 months, email Ron Garcia or John Phillips ("garcia at osl dot iu dot edu" and "phillips at mps dot ohio-state dot edu" respectively) a short description of your library and they will add it to the Review Wizard Report Libraries Under Construction section. HTH, Vicente

2 3

[Signals] Call of an unary object function from a binary signal does not fail to compile
by Samuel Debionne 09 Dec '08

09 Dec '08

Hello, Almost everything is in the title. To go into details, I have a small test case (see attached file) where I accidentally manage to call a unary object function from a binary signal. The object function is the result of a Boost.Bind call. I would have expect a compile time error here. What happend to the second parameter ? Is there any risks of stack corruption ? Thanks, Samuel

2 1

[review][constrained_value] Constrained Value Review Ends Tomorrow - December 10th
by Jeff Garland 09 Dec '08

09 Dec '08

Thanks to all who have submitted a review and the healthy issue discussion. The review is scheduled to wrap up tomorrow. We can certainly continue to discuss after the deadline since I don't believe another review is scheduled, but if you're thinking of reviewing sooner would be better than later. Thanks, Jeff ******************************************************************* The review of the Robert Kawulak's Constrained Value library begins today December 1, 2008, and will end on December 10th -- I will be the review manager. Please post reviews to the developer list. Here's the library synopsis: The Boost Constrained Value library contains class templates useful for creating constrained objects. A simple example is an object representing an hour of a day, for which only integers from the range [0, 23] are valid values. bounded_int<int, 0, 23>::type hour; hour = 20; // OK hour = 26; // exception! Behavior in case of assignment of an invalid value can be customized. The library has a policy-based design to allow for flexibility in defining constraints and behavior in case of assignment of invalid values. Policies may be configured at compile-time for maximum efficiency or may be changeable at runtime if such dynamic functionality is needed. The library can be downloaded from the here: http://rk.go.pl/f/constrained_value.zip The documentation is also available online here: http://rk.go.pl/r/constrained_value --------------------------------------------------- Please state in your review, whether you think the library should be accepted as a Boost library. Additionally, please consider the following aspects in your review of the library: - What is your evaluation of the design? - What is your evaluation of the implementation? - What is your evaluation of the documentation? - What is your evaluation of the potential usefulness of the library? - Did you try to use the library? With what compiler? Did you have any problems? - How much effort did you put into your evaluation? A glance? A quick reading? In-depth study? - Are you knowledgeable about the problem domain? Thanks, Jeff

1 0

[Review] UUID library (mini-)review starts today, November 23rd
by Hartmut Kaiser 09 Dec '08

09 Dec '08

Hi all, The mini-review of Andy Tompkins UUID library starts today, November 23rd 2008, and will end on November 30th. I really hope to see your vote and your participation in the discussions on the Boost mailing lists! The library can be downloaded from the vault here (it's the file uuid_v13.zip in the topmost directory): http://tinyurl.com/6xx28b The initial review of the UUID library ended with a provisional acceptance (read here: http://article.gmane.org/gmane.comp.lib.boost.user/27774/) This mini review is meant to allow for a final decision after looking at the changed parts of the library. Here is a list of things fixed and changed: - fixed the licensing issues revealed by the initial review - fixed the security vulnerability revealed by the initial review - renamed to uuid, moved all classes, functions, etc. to namespace boost::uuids - implemented sha1 hash function (thus no license problem) - new class basic_uuid_generator to create random-based uuids. The random number generator is no longer hard coded. It can use any random number generator, default is boost::mt19937 - implemented a good seed function for random number generators - all functions are now reentrant, all classes are as thread safe as an int and the library is no longer dependent on Boost.Thread --------------------------------------------------- Please always state in your review, whether you think the library should be accepted as a Boost library! Additionally please consider giving feedback on the following general topics: - What is your evaluation of the design? - What is your evaluation of the implementation? - What is your evaluation of the documentation? - What is your evaluation of the potential usefulness of the library? - Did you try to use the library? With what compiler? Did you have any problems? - How much effort did you put into your evaluation? A glance? A quick reading? In-depth study? - Are you knowledgeable about the problem domain? Regards Hartmut Review Manager

11 25

[Serialization] assertion failure on exit
by Kenny Riddile 09 Dec '08

09 Dec '08

I'm getting the following assertion failure on exit when instantiating certain serializable classes: Assertion failed: NULL != l, file libs\serialization\src\extended_type_info.cpp, line 47 I was finally able to determine a difference between the classes that caused the assertion failure and those that didn't. Here's some code: ////////////////////////////////////////////////////////////////// // Serializable.hpp: class Serializable { public: virtual ~Serializable() = 0; template< typename Archive > void serialize( Archive& /*ar*/, const unsigned int /*version*/ ) { } private: }; inline Serializable::~Serializable() { } BOOST_CLASS_EXPORT( Serializable ) ////////////////////////////////////////////////////////////////// ////////////////////////////////////////////////////////////////// // Foo.hpp: struct Foo : Serializable { template< typename Archive > void serialize( Archive& ar, const unsigned int /*version*/ ) { ar & BOOST_SERIALIZATION_BASE_OBJECT_NVP( Serializable ); } }; BOOST_CLASS_EXPORT( Foo ) ////////////////////////////////////////////////////////////////// The above code does not assert on exit after instantiating a Foo object. However, if I make Foo not header-only like so: ////////////////////////////////////////////////////////////////// // Foo.hpp: struct Foo : Serializable { Foo(); template< typename Archive > void serialize( Archive& ar, const unsigned int /*version*/ ) { ar & BOOST_SERIALIZATION_BASE_OBJECT_NVP( Serializable ); } }; BOOST_CLASS_EXPORT( Foo ) ////////////////////////////////////////////////////////////////// ////////////////////////////////////////////////////////////////// // Foo.cpp: Foo::Foo() { } ////////////////////////////////////////////////////////////////// then I get the assertion failure on program exit if I so much as instantiate a Foo object.

1 2