- Boost - lists.boost.org

List posting delays
by Beman Dawes 24 Jun '08

24 Jun '08

Several people have reported up to 12 hours of delay before their messages are posted. DongInn Kim, the IU system admin, thinks that these delays may be caused by a new spam filter. He has turned off the filter for now to see if that in fact clears the delays. --Beman

1 0

Re: [boost] Google Summer Of Code 2008
by Kasra (Math & ComSci) 24 Jun '08

24 Jun '08

Thanks guys, I wonder why am I late for all these events :(( Next year then :D

1 0

[serialization] 1.34.1 / 1.35 incompatibiliy
by Johan Råde 24 Jun '08

24 Jun '08

There is an incompatibility between text archives saved with 1.34.1 and 1.35. The format for vectors (and other containers?) is different. How will this be handled in 1.36? Will 1.36 revert to the 1.34.1 format? This is the solution I would prefer. Otherwise I will not be able to read my old serialization archives. --Johan

2 1

[shifted_ptr] __normal_iterator ..?
by Phil Bouchard 24 Jun '08

24 Jun '08

Hi, Upon trying to create the new shifted_allocator class that is instead to be passed as a template parameter on STL containers, I got stuck in a circle or errors. I came to realize there was not way to replace internal pointers used by containers with smart pointers... which is very unfortunate. There are different solution I could take but hopefully I won't need them. By trying compiling shifted_ptr_test2.cpp in the Sandbox we'll get the following errors. I believe shifted_allocator (in shifted_allocator.hpp) should be represented the way it is but I may likely got something wrong because I haven't followed the verdict on this in previous posts: ...stl_vector.h: In member function `__gnu_cxx::__normal_iterator<typename _Alloc::const_pointer, std::vector<_Tp, _Alloc> > std::vector<_Tp, _Alloc>::begin() const [with _Tp = boost::detail::sh::shifted_ptr<vector>, _Alloc = boost::shifted_allocator<boost::detail::sh::shifted_ptr<vector> >]': ...stl_vector.h:221: instantiated from `std::vector<_Tp, _Alloc>::vector(const std::vector<_Tp, _Alloc>&) [with _Tp = boost::detail::sh::shifted_ptr<vector>, _Alloc = boost::shifted_allocator<boost::detail::sh::shifted_ptr<vector> >]' shifted_ptr_test2.cpp:66: instantiated from here ...stl_vector.h:322: error: no matching function for call to `__gnu_cxx::__normal_iterator<const boost::detail::sh::shifted<boost::detail::sh::shifted_ptr<vector> >*, std::vector<boost::detail::sh::shifted_ptr<vector>, boost::shifted_allocator<boost::detail::sh::shifted_ptr<vector> > > >::__normal_iterator(boost::detail::sh::shifted_ptr<vector>* const&)' ...stl_iterator.h:587: note: candidates are: __gnu_cxx::__normal_iterator<const boost::detail::sh::shifted<boost::detail::sh::shifted_ptr<vector> >*, std::vector<boost::detail::sh::shifted_ptr<vector>, boost::shifted_allocator<boost::detail::sh::shifted_ptr<vector> > > >::__normal_iterator(const __gnu_cxx::__normal_iterator<const boost::detail::sh::shifted<boost::detail::sh::shifted_ptr<vector> >*, std::vector<boost::detail::sh::shifted_ptr<vector>, boost::shifted_allocator<boost::detail::sh::shifted_ptr<vector> > > >&) ...stl_iterator.h:603: note: __gnu_cxx::__normal_iterator<_Iterator, _Container>::__normal_iterator(const _Iterator&) [with _Iterator = const boost::detail::sh::shifted<boost::detail::sh::shifted_ptr<vector> >*, _Container = std::vector<boost::detail::sh::shifted_ptr<vector>, boost::shifted_allocator<boost::detail::sh::shifted_ptr<vector> > >] ...stl_iterator.h:600: note: __gnu_cxx::__normal_iterator<_Iterator, _Container>::__normal_iterator() [with _Iterator = const boost::detail::sh::shifted<boost::detail::sh::shifted_ptr<vector> >*, _Container = std::vector<boost::detail::sh::shifted_ptr<vector>, boost::shifted_allocator<boost::detail::sh::shifted_ptr<vector> > >] The Vault version presents the same code except the comment of line 67 & 68 in shifted_ptr_test2.cpp will need to be swapped: http://www.boostpro.com/vault/index.php?action=downloadfile&filename=shifte… -Phil

2 6

[website] discoverability of Trac (from boost-users)
by David Abrahams 24 Jun '08

24 Jun '08

I don't entirely understand the user's complaint, but it sounds like it must be valid... :) -- Dave Abrahams BoostPro Computing http://www.boostpro.com

2 1

boost::lambda::ret does not define result_type?
by Mathias Gaunard 23 Jun '08

23 Jun '08

I'm working on some project where I need to generate functors that expose result_type. I thought boost::lambda::ret was supposed to do just that, however it seems it doesn't. It would just require adding one line in boost/lambda/detail/lambda_functor_base.hpp, for the explicit_return type_action case.

1 0

Re: [boost] [hash] Is there any interest in cryptographic hash functions?
by Kasra (Math & ComSci) 23 Jun '08

23 Jun '08

Kevin, Some clarifications :D -> "I contest that statement, it is in fact quite modular, you are merely adding abstract base classes to impose an interface for the different models which is not necessary when using templates to compose objects." I forgot to mention I don't want to say that we will have base classes with virtual stuff, because that is expensive, however, what I wanted to point is that there must be an interface "template" so when one wants to add more block_cipher, ciphers and etc, one should know which functions should be available as public. The base class code is merely for documentation purposes only! "Okay, wipe algorithms are interesting but I don't see added value in clearing memory to zeros vs clearing the memory with some other pattern or random data. For current RAM technologies the original data is destroyed with a simple memset to zero." Check this one out: http://citp.princeton.edu/memory/ But when we have wipe algorithms we could hook them to fstreams and there is it! We will wipe a file which as you know is quiet important when you want to get rid of the data! "How is that better than template<class Cipher, class Mode, class Padding> struct block_cipher; ?" I told you about the idea of "cipher". So a block_cipher only encrypt/decrypts blocks and that is as far as it stretches (including key schedules etc). However, a cipher would encrypt any arbitary length of message. The modes of operation would have some thing like: template < class block_cipher, class padding > class mode_of_operation { . . . }; which turns a block_cipher concept into a "cipher"; that could encrypt any arbitary message length. So that is why I thought we could changed it. "I am interested in that optimization, I have deliberately chosen the 'slower' variant as it follows the original paper more closely and made it a little easier for me to implement. I would like to see benchmarks of this variant." I am NOT going to write this variant since "Paulo Barreto"; which is THE EXPERT, he has written the optimized version (http://www.iaik.tugraz.at/Research/krypto/AES/old/~rijmen/rijndael/rijndael…) So I would only create a wrapper for the functions :D. Since I have been active in the field I know of most of the optimized implementations, so we only need to write wrappers for them. However I am rather busy for two weeks, so this is probably the last e-mail which I will sent in two weeks time :( Thanks for the comments Kasra

3 2

g++ "extra semicolon" in ptr_vector.hpp
by Steve Huston 23 Jun '08

23 Jun '08

I'm building a project that uses boost, and it insists on building with g++ -pedantic on Linux. This is causing an issue in ptr_container/ptr_vector.hpp (in boost 1.35 it's on line 47) public: BOOST_PTR_CONTAINER_DEFINE_SEQEUENCE_MEMBERS( ptr_vector, base_class, this_type ); After BOOST_PTR_CONTAINER_DEFINE_SEQEUENCE_MEMBERS gets done being expanded in detail/reversible_ptr_container.hpp, the semicolon is extraneous. g++ 3.4.6 (at least) complains about this: /usr/local/include/boost/ptr_container/ptr_vector.hpp:45: error: extra semicolon Could that be removed?

2 2

Google Summer Of Code 2008
by Kasra (Math & ComSci) 23 Jun '08

23 Jun '08

Dear all, As you migh already know I have propsed some changed to the current implementation of boost::crypto namespace. Some of these changes are enough to be propsed as a new project idea for Google Summer Of Code 2008 (of course I am a student). I am wondering: 1) how should I propse this new project idea? 2) how could I apply for SOM? Regards

3 2

[Accumulators] Problem building the combined boost documentation.
by Daniel James 23 Jun '08

23 Jun '08

Hi, I'm getting errors building the combined documentation on Ubuntu Hardy. The problem seems to be caused by the accumulator library (or maybe the boost build tools that it uses) using absolute directories for its build destination, while most other libraries use relative ones. Looking through the build output the first error is: common.copy ../libs/accumulators/doc/tagfile.xml MkDir1 /home/daniel/boost/branches/release/bin.v2 mkdir: cannot create directory `/home/daniel/boost/branches/release/bin.v2': File exists mkdir "/home/daniel/boost/branches/release/bin.v2" ...failed MkDir1 /home/daniel/boost/branches/release/bin.v2... ...skipped /home/daniel/boost/branches/release/bin.v2/libs for lack of /home/daniel/boost/branches/release/bin.v2... ...skipped /home/daniel/boost/branches/release/bin.v2/libs/accumulators for lack of /home/daniel/boost/branches/release/bin.v2/libs... ...skipped /home/daniel/boost/branches/release/bin.v2/libs/accumulators/doc for lack of /home/daniel/boost/branches/release/bin.v2/libs/accumulators... ...skipped /home/daniel/boost/branches/release/bin.v2/libs/accumulators/doc/html for lack of /home/daniel/boost/branches/release/bin.v2/libs/accumulators/doc... doxygen-action ../bin.v2/libs/accumulators/doc/gcc-4.3/debug/statsdoc.html-dir Notice: Output directory `/home/daniel/boost/branches/release/bin.v2/libs/accumulators/doc/html' does not exist. I have created it for you. '../bin.v2' has been previously created as a relative directory, and here is an absolute directory '/home/daniel/boost/branches/release/bin.v2', which I think causes boost build to try to create the same directory twice. You can see from the output that the required directory gets created soon after, but boost build seems to remember the error, because later in the output: ...skipped <p/home/daniel/boost/branches/release/bin.v2/libs/accumulators/doc/html>statsdoc.html for lack of /home/daniel/boost/branches/release/bin.v2/libs/accumulators/doc/html... ...skipped <p../bin.v2/libs/accumulators/doc/gcc-4.3/debug>statsdoclatex.tag for lack of <p/home/daniel/boost/branches/release/bin.v2/libs/accumulators/doc/html>statsdoc.html... ...skipped <p../bin.v2/libs/accumulators/doc/gcc-4.3/debug>statsdoc-xml.doxyfile for lack of <p../bin.v2/libs/accumulators/doc/gcc-4.3/debug>statsdoclatex.tag... ...skipped <p../bin.v2/libs/accumulators/doc/gcc-4.3/debug>statsdoc-xml.xml-dir for lack of <p../bin.v2/libs/accumulators/doc/gcc-4.3/debug>statsdoc-xml.doxyfile... ...skipped <p../bin.v2/libs/accumulators/doc/gcc-4.3/debug>statsdoc-xml.doxygen for lack of <p../bin.v2/libs/accumulators/doc/gcc-4.3/debug>statsdoc-xml.xml-dir... ...skipped <p../bin.v2/libs/accumulators/doc/gcc-4.3/debug>statsdoc-xml.boostbook for lack of <p../bin.v2/libs/accumulators/doc/gcc-4.3/debug>statsdoc-xml.doxygen... ...skipped <p../libs/accumulators/doc>statsdoc.xml for lack of <p../bin.v2/libs/accumulators/doc/gcc-4.3/debug>statsdoc-xml.boostbook... Which then causes more targets to be skipped later on, preventing the documentation from being built. It seems that if bjam is then run again the problem doesn't occur, probably because the problem directories are already created. I'm running it at the moment and it looks like it'll probably succeed (it takes a while). I can send the complete build output if it'll help. thanks, Daniel

2 3