June 2008 - Boost - lists.boost.org

[python] frame corruption in python -> c++ -> python scenario
by Gennadiy Rozental 11 Jun '08

11 Jun '08

Hi, I am experiencing strange issue I can't find solution for. Sorry I'll need a bit lengthy explanation to describe it. I am using boost python for both automation and embedding the same time. I wrote trivial unit test module (can't use standard one). It has function check like this: def check( val ): check_impl( val ) def check_impl( val ): ... print "Error at line " + str(sys._getframe(2).f_lineno+1) ... ... This supposedly should produce error line location. And it does. Sometimes. test1.py: ... 8> check( False ) produces: Error in line 8: ... I've noticed though that in some cases line numbers are incorrect. I was able to narrow it down to the single function mymodule.foo() Before this function call line numbers are correct. After it incorrect. foo is a function implemented in c++ and exported using boost.python. I was able further to identify that the line at fault inside function foo implementation is the one invoking python function: void foo() { ... boost::python::object obj = ... obj(); ... } So. Finally the question: Is there way to fix/circumvent this somehow? Thanks, Gennadiy

1 0

boost::decimal ?
by Mårten Rånge 11 Jun '08

11 Jun '08

Is there some work been done on implementing a boost::decimal class? If there isn't my guess is that this would be very useful to C++ programmers out there if boost could provide this (we sure would dance with joy!). I would like to help but frankly I lack the competence on how to implement a decimal class efficiently and with the robustness it needs. A decimal class would be very useful for ERP and Financial systems as in many cases of the typical customers work with the decimal system instead of the binary system. It's hard to motivate for the customers why: 1 -0.2 -0.2 -0.2 -0.2 -0.2 doesn't add up to _exactly_ 0 when using double (windows calc.exe had this problem many years ago and it attracted lot of gleeful comments, so gleeful calc.exe uses infinite precision these days to represent rational numbers). In addition many sums are intended to become 0 at the end (the debit and credit should be balanced) so cancellation errors like above actually are quite common. The key issue is that common numbers such as 0.1, 0.2, and so on can't be exactly represented in a double. http://www2.hursley.ibm.com/decimal/ -- Mårten

4 3

[serialization] Base64 padding in basic_text_oprimitive
by Vyacheslav E. Andrejev 10 Jun '08

10 Jun '08

Hello, Code that pads base64 output with '=' looks in basic_text_oprimitive.ipp like following: std::size_t padding = 2 - count % 3; if(padding > 1) *oi = '='; if(padding > 2) *oi = '='; It will give the following transformations of a few simple strings: "012" -> "MDEy=" "0123" -> "MDEyMw" "01234" -> "MDEyMzQ" "012345" -> "MDEyMzQ1=" Which violates the principle of the base 64 that the encoded output length is multiple of 4 bytes. Right output for the samples above should be: "012" -> "MDEy" "0123" -> "MDEyMw==" "01234" -> "MDEyMzQ=" "012345" -> "MDEyMzQ1" The problem with the code above is that the condition (padding > 2) is never satisfied. I think that the proper code should look like std::size_t padding = 2 - count % 3; if (padding < 2) { *oi = '='; if (padding > 0) *oi = '='; } -- -- Vyacheslav Andrejev -- System Architect, Optech International, Inc.

2 3

[serialization] implementing class_name_optional_type
by Esteve Fernandez 10 Jun '08

10 Jun '08

Hi all, I'm working on the "YAML archives for Boost.Serialization" GSoC project and I've already implemented a working output archive. However, since YAML requires the class name to be always serialized, I had to implement the serialization of a new type called class_name_optional_type in basic_oarchive.cpp, which lets the archive decide if class names should always be written. It was discussed in the past [1], but never implemented, AFAIK. Cheers. PS: should I send the patch to this list or is it better to create a new ticket? 1 - http://lists.boost.org/boost-users/2006/06/20319.php

2 9

Request: RDTSC
by dherring＠ll.mit.edu 10 Jun '08

10 Jun '08

The CPU timestamp counter is a high-resolution clock source useful for profiling code or controlling tight timing loops. AMD/Intel CPUs support this via the RDTSC opcode, and other CPUs often provide similar functionality. Apparently MS compilers support an __rdtsc() intrinsic, but I couldn't find one for gcc. The code at http://www-unix.mcs.anl.gov/~kazutomo/rdtsc.html seems to do a good job for gcc; it avoids a couple bugs in code found at other sites. Any possibility of a raw boost::rdtsc() or boost::readTSC()? Something that doesn't compile on unsupported architectures would be good. Other code can worry about whether this is an accurate time source[1]; I just want a portable way to access the raw counter itself. Thanks, Daniel [1] Search "rdtsc site:boost.org"

4 3

[shifted_ptr] "new shifted<T>"
by Phil Bouchard 10 Jun '08

10 Jun '08

Hi, Firstly after defining my own sh::pool allocator new doors opened on their own and now I am able to replace the "new_sh<>()" function call with a much more neat C++ approach with "new shifted<>()". For example instead of: shifted_ptr<char[9]> u = new_sh<char[9]>(); Now we can write: shifted_ptr<char[9]> u = new shifted<char[9]>(); This will allows us defining STL container allocators more easily because of the distinct steps the constructor and allocator are called; new_sh<>() was mixing them altogether. Secondly I was able to drastically clean up "class shifted<>" (was: owned<>) by unifying the construction of the member object with the construction of the class itself. This was necessary to use "new shifted<>()" adequately. Last but not least the library now takes advantage of the fast_pool_allocator for objects such as "struct set" and "numeric::interval<int>". FYI I am using "numeric::interval<int>" instead of "numeric::interval<void *>" because of a compilation failure with the latter. I am casting the pointers to an "int" meanwhile because there is no lost of information by doing so according to the standards. The files are both on Vault and the Sandbox and is nearly the official release. Documentation will follow soon for those who got no clue what I'm talking about: http://www.boost-consulting.com/vault/index.php?action=downloadfile&filenam… Thanks, -Phil

3 14

[regex] cygwin compile errors
by Emil Dotchevski 10 Jun '08

10 Jun '08

Please see the relevant part from my build log below. gcc.compile.c++ ../../../../../bin/lib/re_0_02_0/impl/test/header-reno_config~pimpl~h.test/gcc-3.4.4/debug/link-static/header-reno_config~pimpl~h.o In file included from /cygdrive/c/code/lib/boost-trunk/boost/regex/v4/regex_traits.hpp:35, from /cygdrive/c/code/lib/boost-trunk/boost/regex/regex_traits.hpp:27, from /cygdrive/c/code/lib/boost-trunk/boost/regex/v4/regex.hpp:39, from /cygdrive/c/code/lib/boost-trunk/boost/regex.hpp:31, from /cygdrive/c/code/lib/re_0_02_0/re/reno_config.pimpl.h:10, from header-test.cpp:4: /cygdrive/c/code/lib/boost-trunk/boost/regex/v4/regex_traits_defaults.hpp: In function `ptrdiff_t boost::re_detail::global_length(const charT*) [with charT = wchar_t]': /cygdrive/c/code/lib/boost-trunk/boost/regex/v4/regex_traits_defaults.hpp:234: error: `wcslen' is not a member of `std' In file included from /cygdrive/c/code/lib/boost-trunk/boost/regex/v4/regex_traits.hpp:44, from /cygdrive/c/code/lib/boost-trunk/boost/regex/regex_traits.hpp:27, from /cygdrive/c/code/lib/boost-trunk/boost/regex/v4/regex.hpp:39, from /cygdrive/c/code/lib/boost-trunk/boost/regex.hpp:31, from /cygdrive/c/code/lib/re_0_02_0/re/reno_config.pimpl.h:10, from header-test.cpp:4: /cygdrive/c/code/lib/boost-trunk/boost/regex/v4/c_regex_traits.hpp: At global scope: /cygdrive/c/code/lib/boost-trunk/boost/regex/v4/c_regex_traits.hpp:104: error: ISO C++ forbids declaration of `wstring' with no type /cygdrive/c/code/lib/boost-trunk/boost/regex/v4/c_regex_traits.hpp:104: error: expected `;' before "string_type" /cygdrive/c/code/lib/boost-trunk/boost/regex/v4/c_regex_traits.hpp:122: error: `string_type' does not name a type /cygdrive/c/code/lib/boost-trunk/boost/regex/v4/c_regex_traits.hpp:123: error: `string_type' does not name a type /cygdrive/c/code/lib/boost-trunk/boost/regex/v4/c_regex_traits.hpp:126: error: `string_type' does not name a type /cygdrive/c/code/lib/boost-trunk/boost/regex/v4/c_regex_traits.hpp: In static member function `static size_t boost::c_regex_traits<wchar_t>::length(const wchar_t*)': /cygdrive/c/code/lib/boost-trunk/boost/regex/v4/c_regex_traits.hpp:110: error: `wcslen' is not a member of `std' /cygdrive/c/code/lib/boost-trunk/boost/regex/v4/c_regex_traits.hpp: In member function `wchar_t boost::c_regex_traits<wchar_t>::translate_nocase(wchar_t) const': /cygdrive/c/code/lib/boost-trunk/boost/regex/v4/c_regex_traits.hpp:119: error: `towlower' is not a member of `std' In file included from /cygdrive/c/code/lib/boost-trunk/boost/regex/v4/regex.hpp:76, from /cygdrive/c/code/lib/boost-trunk/boost/regex.hpp:31, from /cygdrive/c/code/lib/re_0_02_0/re/reno_config.pimpl.h:10, from header-test.cpp:4: /cygdrive/c/code/lib/boost-trunk/boost/regex/v4/sub_match.hpp: At global scope: /cygdrive/c/code/lib/boost-trunk/boost/regex/v4/sub_match.hpp:186: error: `std::wstring' has not been declared /cygdrive/c/code/lib/boost-trunk/boost/regex/v4/sub_match.hpp:186: error: `const_iterator' was not declared in this scope /cygdrive/c/code/lib/boost-trunk/boost/regex/v4/sub_match.hpp:186: error: template argument 1 is invalid /cygdrive/c/code/lib/boost-trunk/boost/regex/v4/sub_match.hpp:186: error: ISO C++ forbids declaration of `wssub_match' with no type In file included from /cygdrive/c/code/lib/boost-trunk/boost/regex.hpp:31, from /cygdrive/c/code/lib/re_0_02_0/re/reno_config.pimpl.h:10, from header-test.cpp:4: /cygdrive/c/code/lib/boost-trunk/boost/regex/v4/regex.hpp:140: error: `std::wstring' has not been declared /cygdrive/c/code/lib/boost-trunk/boost/regex/v4/regex.hpp:140: error: `const_iterator' was not declared in this scope /cygdrive/c/code/lib/boost-trunk/boost/regex/v4/regex.hpp:140: error: template argument 1 is invalid /cygdrive/c/code/lib/boost-trunk/boost/regex/v4/regex.hpp:140: error: template argument 2 is invalid /cygdrive/c/code/lib/boost-trunk/boost/regex/v4/regex.hpp:140: error: ISO C++ forbids declaration of `wsmatch' with no type In file included from /cygdrive/c/code/lib/boost-trunk/boost/regex/v4/regex.hpp:151, from /cygdrive/c/code/lib/boost-trunk/boost/regex.hpp:31, from /cygdrive/c/code/lib/re_0_02_0/re/reno_config.pimpl.h:10, from header-test.cpp:4: /cygdrive/c/code/lib/boost-trunk/boost/regex/v4/regex_iterator.hpp:172: error: `std::wstring' has not been declared /cygdrive/c/code/lib/boost-trunk/boost/regex/v4/regex_iterator.hpp:172: error: `const_iterator' was not declared in this scope /cygdrive/c/code/lib/boost-trunk/boost/regex/v4/regex_iterator.hpp:172: error: template argument 1 is invalid /cygdrive/c/code/lib/boost-trunk/boost/regex/v4/regex_iterator.hpp:172: error: template argument 2 is invalid /cygdrive/c/code/lib/boost-trunk/boost/regex/v4/regex_iterator.hpp:172: error: template argument 3 is invalid /cygdrive/c/code/lib/boost-trunk/boost/regex/v4/regex_iterator.hpp:172: error: ISO C++ forbids declaration of `wsregex_iterator' with no type In file included from /cygdrive/c/code/lib/boost-trunk/boost/regex/v4/regex.hpp:154, from /cygdrive/c/code/lib/boost-trunk/boost/regex.hpp:31, from /cygdrive/c/code/lib/re_0_02_0/re/reno_config.pimpl.h:10, from header-test.cpp:4: /cygdrive/c/code/lib/boost-trunk/boost/regex/v4/regex_token_iterator.hpp:286: error: `std::wstring' has not been declared /cygdrive/c/code/lib/boost-trunk/boost/regex/v4/regex_token_iterator.hpp:286: error: `const_iterator' was not declared in this scope /cygdrive/c/code/lib/boost-trunk/boost/regex/v4/regex_token_iterator.hpp:286: error: template argument 1 is invalid /cygdrive/c/code/lib/boost-trunk/boost/regex/v4/regex_token_iterator.hpp:286: error: template argument 2 is invalid /cygdrive/c/code/lib/boost-trunk/boost/regex/v4/regex_token_iterator.hpp:286: error: template argument 3 is invalid /cygdrive/c/code/lib/boost-trunk/boost/regex/v4/regex_token_iterator.hpp:286: error: ISO C++ forbids declaration of `wsregex_token_iterator' with no type Emil Dotchevski Reverge Studios, Inc. http://www.revergestudios.com/reblog/index.php?n=ReCode

1 1

[ptr_container] Fix for Tru64/CXX
by Markus Schöpflin 09 Jun '08

09 Jun '08

Hello, attached patch contains a fix for Tru64/CXX, which somehow seems to have troubles with the following code in the class associative_ptr_container: using base_type::begin; using base_type::end; using base_type::cbegin; using base_type::cend; It looks like the compiler doesn't consider these using declarations when performing overload resolution for one of these methods. The fix is easy, it simply adds inline definitions for these methods. Can this patch please be applied? Regards, Markus Index: detail/associative_ptr_container.hpp =================================================================== --- detail/associative_ptr_container.hpp (revision 46270) +++ detail/associative_ptr_container.hpp (working copy) @@ -18,6 +18,7 @@ #endif #include <boost/ptr_container/detail/reversible_ptr_container.hpp> +#include <boost/detail/workaround.hpp> namespace boost { @@ -347,10 +348,42 @@ } public: +#if BOOST_WORKAROUND(__DECCXX_VER, BOOST_TESTED_AT(70190006)) + iterator begin() + { + return base_type::begin(); + } + + const_iterator begin() const + { + return base_type::begin(); + } + + iterator end() + { + return base_type::end(); + } + + const_iterator end() const + { + return base_type::end(); + } + + const_iterator cbegin() const + { + return base_type::cbegin(); + } + + const_iterator cend() const + { + return base_type::cend(); + } +#else using base_type::begin; using base_type::end; using base_type::cbegin; using base_type::cend; +#endif protected: local_iterator begin( size_type n )

2 1

[iterators][range] size compile failure in 1.35
by Jeff Flinn 09 Jun '08

09 Jun '08

I'm moving from 1.34.1 to 1.35.0 The following compiles in 1.34.1 and fails in 1.35.0 on MSVC 8. Any thoughts on how to correct this? #include <vector> #include <boost/bind.hpp> #include <boost/iterator/filter_iterator.hpp> #include <boost/range/iterator_range.hpp> template<class Predicate, class Range> boost::iterator_range<boost::filter_iterator<Predicate, typename Range::iterator> > filteredRange(Range& range, Predicate p) { return boost::make_iterator_range( boost::make_filter_iterator<Predicate>(p, range.begin(), range.end()), boost::make_filter_iterator<Predicate>(p, range. end(), range.end())); } bool filt(int ) { return true; } int main() { std::vector<int> c; filteredRange(c, boost::bind(&filt, _1)).size(); return 0; } And the errors are: 1>IteratorAndRangeSizeTest.cpp 1>f:\gene_codes\external_libraries\boost_1_35_0\boost\iterator\iterator_adaptor.hpp(225) : error C2027: use of undefined type 'boost::STATIC_ASSERTION_FAILURE<x>' 1> with 1> [ 1> x=false 1> ] 1> f:\gene_codes\external_libraries\boost_1_35_0\boost\iterator\iterator_adaptor.hpp(348) : see reference to function template instantiation 'void boost::detail::iterator_adaptor_assert_traversal<boost::bidirectional_traversal_tag,boost::random_access_traversal_tag>(void)' being compiled 1> f:\gene_codes\external_libraries\boost_1_35_0\boost\iterator\iterator_facade.hpp(554) : see reference to function template instantiation '__w64 int boost::iterator_adaptor<Derived,Base,Value,Traversal>::distance_to<boost::filter_iterator<Predicate,Iterator>,Iterator,boost::use_default,boost::bidirectional_traversal_tag,boost::use_default,boost::use_default>(const boost::iterator_adaptor<Derived,Base,Value,Traversal> &) const' being compiled 1> with 1> [ 1> Derived=boost::filter_iterator<boost::_bi::bind_t<bool,bool (__cdecl *)(int),boost::_bi::list1<boost::arg<1>>>,std::_Vector_iterator<int,std::allocator<int>>>, 1> Base=std::_Vector_iterator<int,std::allocator<int>>, 1> Value=boost::use_default, 1> Traversal=boost::bidirectional_traversal_tag, 1> Predicate=boost::_bi::bind_t<bool,bool (__cdecl *)(int),boost::_bi::list1<boost::arg<1>>>, 1> Iterator=std::_Vector_iterator<int,std::allocator<int>> 1> ] 1> f:\gene_codes\external_libraries\boost_1_35_0\boost\iterator\iterator_facade.hpp(852) : see reference to function template instantiation '__w64 int boost::iterator_core_access::distance_from<Derived1,Derived2>(const Facade1 &,const Facade2 &,boost::mpl::true_)' being compiled 1> with 1> [ 1> Derived1=boost::filter_iterator<boost::_bi::bind_t<bool,bool (__cdecl *)(int),boost::_bi::list1<boost::arg<1>>>,std::_Vector_iterator<int,std::allocator<int>>>, 1> Derived2=boost::filter_iterator<boost::_bi::bind_t<bool,bool (__cdecl *)(int),boost::_bi::list1<boost::arg<1>>>,std::_Vector_iterator<int,std::allocator<int>>>, 1> Facade1=boost::filter_iterator<boost::_bi::bind_t<bool,bool (__cdecl *)(int),boost::_bi::list1<boost::arg<1>>>,std::_Vector_iterator<int,std::allocator<int>>>, 1> Facade2=boost::filter_iterator<boost::_bi::bind_t<bool,bool (__cdecl *)(int),boost::_bi::list1<boost::arg<1>>>,std::_Vector_iterator<int,std::allocator<int>>> 1> ] 1> f:\gene_codes\external_libraries\boost_1_35_0\boost\range\iterator_range.hpp(278) : see reference to function template instantiation '__w64 int boost::operator -<Derived,int,boost::bidirectional_traversal_tag,int&,__w64 int,Derived,int,boost::bidirectional_traversal_tag,int&,__w64 int>(const boost::iterator_facade<Derived,Value,CategoryOrTraversal,Reference,Difference> &,const boost::iterator_facade<Derived,Value,CategoryOrTraversal,Reference,Difference> &)' being compiled 1> with 1> [ 1> Derived=boost::filter_iterator<boost::_bi::bind_t<bool,bool (__cdecl *)(int),boost::_bi::list1<boost::arg<1>>>,std::_Vector_iterator<int,std::allocator<int>>>, 1> Value=int, 1> CategoryOrTraversal=boost::bidirectional_traversal_tag, 1> Reference=int &, 1> Difference=__w64 int 1> ] 1> f:\gene_codes\external_libraries\boost_1_35_0\boost\range\iterator_range.hpp(276) : while compiling class template member function '__w64 int boost::iterator_range<IteratorT>::size(void) const' 1> with 1> [ 1> IteratorT=boost::filter_iterator<boost::_bi::bind_t<bool,bool (__cdecl *)(int),boost::_bi::list1<boost::arg<1>>>,std::_Vector_iterator<int,std::allocator<int>>> 1> ] 1> f:\dev\iteratorandrangesizetest\iteratorandrangesizetest.cpp(24) : see reference to class template instantiation 'boost::iterator_range<IteratorT>' being compiled 1> with 1> [ 1> IteratorT=boost::filter_iterator<boost::_bi::bind_t<bool,bool (__cdecl *)(int),boost::_bi::list1<boost::arg<1>>>,std::_Vector_iterator<int,std::allocator<int>>> 1> ] Thanks, Jeff

4 4

SF 2008 Community awards
by joaquin＠tid.es 09 Jun '08

09 Jun '08

Hello, I just received an invitation to nominate a project for SF 2008 Community awards and naturally decided to go for Boost in the category of Best Tool or Utility for Developers. Once in the nomination page I clicked "Search", typed Boost, and now comes the problem: SF locates two different Boost projects: Name: Boost, URL: http://boost.org Name: Boost C++ Libraries, URL: http://sourceforge.net/projects/boost/ Of course both projects are actually the one and only Boost, but I wonder whether we should agree on which one to formally nominate so that our voting force does not get split. Joaquín M López Muñoz Telefónica, Investigación y Desarrollo

6 8