December 2010 - Boost - lists.preview.boost.org

NVCC CUDA SUpport
by Joel Falcou 31 Dec '10

31 Dec '10

Here is a few tickets regarding nvcc support: https://svn.boost.org/trac/boost/search?q=nvcc+cuda #4431: Bugs: stdint.h not available in CUDA nvcc + visual studio (new) <https://svn.boost.org/trac/boost/ticket/4431> #4356: Patches: small change to allow mpl code to compile with nvcc (the compiler for ... (new) <https://svn.boost.org/trac/boost/ticket/4356> #4052: Patches: NVCC and boost/type_traits/has_new_operator.hpp (closed: fixed) <https://svn.boost.org/trac/boost/ticket/4052> #4046: Bugs: Boost.System does not compile on Cuda (closed: invalid) <https://svn.boost.org/trac/boost/ticket/4046> as the originator of the nvcc config patch and havign the ressource to test and patch these issues, would the owner of said ticket see any problem if I reassign them to me ?

4 6

Your Boost Needs You!
by John Maddock 31 Dec '10

31 Dec '10

There's been a lot of discussion lately about improving participation in Boost, this is a call to arms for a *small* initial experiment which I hope will grow into something bigger, perhaps after some tweaking to the initial experiment. The aim is to merge the ideas put forward for a Boost Guild, with mine for a roving hit squad to tackle neglected libraries. It goes like this: * Someone, lets call him a manager/mentor/maintainer puts forward a library that has a large number of open tickets against it and which maybe hasn't seen maintenance in some time. * The manager creates a copy of that library in the sandbox for folks to work on. * The volunteers either submit patches or - preferably - commit patches direct to the sandbox copy. Work continues for a month or two until everyone agrees that they have a release ready update (tested locally by the volunteers). * The manager reviews the changes and either: merges the changes to Trunk, or files a clear list of things to do to make the update acceptable. * If the Trunk tests don't pass (and the fix isn't obvious/trivial) the manager throws the problem back to the volunteers, otherwise merges to Release. The aim is to: * Minimize the "manager/maintainer/mentor" bottleneck by having one review of a whole set of changes to one library, rather than having to deal with lots of little patches from all the over the place. * Maximize the chances that the volunteers achieve something meaningful in a defined set of time, by defining clear goals from the outset, and selecting a manageable target from the many folks could choose - currently we suffer from the "too much to choose from or do, so why do anything" dilemma. * The manager undertakes the responsibility for stewarding the update through to the release branch - frankly this is only possible by the mentor dealing with one library at a time, otherwise the "many small patches" problem quickly becomes overwhelming. * Give recognition to volunteers for their efforts, first by providing the "I did that" feeling from working towards a specific target, second by adding acknowledgements or in the case of partial (or complete!) rewrites, co-authorship to the docs. Like I said the aim is to start small with an experiment (low risk, low expectations) to see how it goes... then refine the process... and hope we can grow it into something larger over time. For this I'm prepared to act as the mentor/manager for an update to the pool library (though I'm certainly open to other suggestions, and if someone else would like to take on the manager/mentor role then by all means fell free! :-) ). I chose this library because it's seen essentially no maintenance (and certainly no maintainer) since it was written, and because on the face of it, it looks to be a manageable task for folks to take on. So... let me know if you're interested, and if there's enough people I'll define the goals and get things started, Regards, John.

9 13

Re: [boost] [Boost-commit] svn:boost r67496 - trunk/boost/spirit/home/phoenix/detail
by Steven Watanabe 31 Dec '10

31 Dec '10

AMDG On 12/29/2010 3:38 PM, joel(a)boost-consulting.com wrote: > Author: djowel > Date: 2010-12-29 18:38:19 EST (Wed, 29 Dec 2010) > New Revision: 67496 > URL: http://svn.boost.org/trac/boost/changeset/67496 > > Log: > Added specialization for T const* in reference_type The code says T* const. Which should it be? > Text files modified: > trunk/boost/spirit/home/phoenix/detail/type_deduction.hpp | 6 ++++++ > 1 files changed, 6 insertions(+), 0 deletions(-) > > Modified: trunk/boost/spirit/home/phoenix/detail/type_deduction.hpp > ============================================================================== > --- trunk/boost/spirit/home/phoenix/detail/type_deduction.hpp (original) > +++ trunk/boost/spirit/home/phoenix/detail/type_deduction.hpp 2010-12-29 18:38:19 EST (Wed, 29 Dec 2010) > @@ -254,6 +254,12 @@ > typedef T& type; > }; > > + template<typename T> > + struct reference_type<T* const> > + { > + typedef T const& type; > + }; > + > template<typename C> > struct const_reference_type > { In Christ, Steven Watanabe

2 1

[MPL] web doc suggestion.
by Mostafa 31 Dec '10

31 Dec '10

Hi, From: http://www.boost.org/doc/libs/1_45_0/libs/mpl/doc/refmanual/classes.html, it's not readily apparent that in addition to vector_c, list_c, set_c, there are also vector, list, and set classes. I suggest also mentioning and linking to them in the aforementioned url. Thanks, Mostafa

2 2

[Fusion] begin/end ADL issues with C++0x range-based for
by Michel MORIN 30 Dec '10

30 Dec '10

Hi, In some cases, Fusion Sequence cannot be used in C++0x range-based for (available on GCC 4.6 Pre-Release). For example, this code #include <vector> #include <boost/fusion/include/vector.hpp> int main(int argc, char* argv[]) { typedef boost::fusion::vector<int, int> sequence; for (auto x : std::vector<sequence>()) {} return 0; } does not compile. The C++0x range-based for for (auto x : std::vector<sequence>()) {} is equivalent to { auto&& rng = std::vector<sequence>(); for ( auto it_begin = begin(rng), it_end = end(rng); it_begin != it_end; ++it_begin ) {} } Note that rng has std and boost::fusion as its associated namespaces and the unqualified begin/end function call triggers ADL. The reason for the compiler errors is that the call to begin/end is ambiguous between std::begin/end and boost::fusion::begin/end. (Also boost::fusion::begin/end tries to instanciate result_of::begin/end::<std::vector<sequence> > which leads to a compiler error.) These compiler errors can be avoided by using SFINAE (lazy_enable_if with "is_sequence" metafunction) to boost::fusion::begin/end: // <boost/fusion/sequence/intrinsic/begin.hpp> template <typename Sequence> inline typename lazy_enable_if< traits::is_sequence<Sequence> , typename result_of::begin<Sequence> >::type const begin(Sequence& seq) { return result_of::begin<Sequence>::call(seq); } I attached a patch (against trunk) and a test case. The test case does not compile before applying the patch, but compiles fine after applying the patch. Joel and Christopher, what do you think about this change? Regards, Michel

6 14

[icl] doc filenames
by John Maddock 30 Dec '10

30 Dec '10

Just noticed while doing an update that the documentation filenames for the ICL library are *very* long, and certainly won't pass our inspection script tests (although apparently these have stopped being run :-( ). Assuming that this is quickbook generated docs, the trick is to give each section an ID rather than rely on the auto-generated ones, for example: [section:foo Some long title that generates a really long file name...] Just a quick heads up, John.

4 4

[msm] triggering of a transition on a subclass event does not work on sub state machines in case of favor_compile_time policy is used.
by Richard Szabo 30 Dec '10

30 Dec '10

Hi All I have run it to a problem that feature : Event Hierarchy see doc : http://svn.boost.org/svn/boost/trunk/libs/msm/doc/HTML/ch03s02.html#d0e1108 Does not work in case of sub state machine with favor_compile_time policy. No trans get called on the sub state machine even it has a row with event type to the event base class. This now hit me badly because compiler runs out of heap if favor_compile_time policy is not used but when it is used I can not dispatch based on base type and I have about 150 different event so declare a transition for it is a no go. Is there any workaround for this problem ?. Br. Richie

1 0

[PATCH 1/2] Fixed warning: ignoring return value of 'size_t fread(void*, size_t, size_t, FILE*)'
by Vasyl' 30 Dec '10

30 Dec '10

--- boost/uuid/seed_rng.hpp | 3 ++- 1 files changed, 2 insertions(+), 1 deletions(-)

2 1

QuickBook question
by Marshall Clow 29 Dec '10

29 Dec '10

I am working one some quickbook docs and they start out like this: > [library The Boost Algorithm Library > [quickbook 1.5] > [id algorithm] > [dirname algorithm] > [purpose Library of useful algorithms] > [category algorithms] > [authors [Clow, Marshall]] > [copyright 2010 Marshall Clow] > [source-mode c++] > [license > Distributed under the Boost Software License, Version 1.0. > (See accompanying file LICENSE_1_0.txt or copy at > [@http://www.boost.org/LICENSE_1_0.txt]) > ] > ] > Later (in the same file), I want to drop a link. So, I write: > [link algorithm.all.none_of_if none_of_if1] (where all is a section, and none_of_if is a heading in that section) but this doesn't work! Some investigation shows that > [link the_boost_algorithm_library.all.none_of_if none_of_if2] does work - even though the documentation says that the first element in the link is the document id, not the document title. Am I misunderstanding something? -- Marshall

2 2

Inspection script not running?
by John Maddock 29 Dec '10

29 Dec '10

Title says it all really, Cheers, John.

2 1

no access to http://svn.boost.org/trac/boost/browser
by Frédéric Bron 29 Dec '10

29 Dec '10

Is http://svn.boost.org/trac/boost/browser down? I get: Error: Not Found No handler matched request to /browser Frédéric

5 5

Boost::Regex get URLs
by Tim Hsu 29 Dec '10

29 Dec '10

Hello guys, How do i using Boost::Regex or standard C++ to get all the URLs from a given string.... For example... i want to write a function that is.... But this code doesnt work.... I am not sure how to use Boost::Regex to solve it.... size_t GetUrlsFromString(std::string const& str, std::vector<std::string>& urls) { boost::regex re("<a\\s+href=\"([\\-:\\w\\d\\.\\/]+)\">"); boost::sregex_token_iterator p(str.begin(), str.end(), re, 1); boost::sregex_token_iterator end; while (p != end) { std::string surl(p->first, p->second); urls.push_back(surl); ++p; } return urls.size(); } Thank you!!!! Tim

2 1

[filesystem] what happened to default_name_check()?
by John Maddock 29 Dec '10

29 Dec '10

I'm in the process of porting bcp to Filesystem V3, as the change of default to V3 has broken bcp in Trunk. One thing that has come up is default_name_check() which has been removed. bcp set that to a "do nothing" check since it deals only with files that already exist, so it really does not want to be told that a file name isn't portable! :-) The tests seem to pass OK without this, but should I be worried about this? I couldn't find a rationale for the change in the docs... Cheers, John.

2 1

range adaptors
by barend 29 Dec '10

29 Dec '10

hi, First of all I like the new range adaptors, thanks for creating them. As much of Boost.Geometry is range-based, we like to support them. So I recently created a small integration, enabling things as: int n = boost::geometry::num_points(my_line | filtered(not_two())); where it filters out the points having a coordinate with 2 (just for testing). It works great, and most the adaptors, like strided, sliced, uniqued, reversed, seem very useful to me in this context. To enable this use I needed to specialize one of our structures to match boost range adaptors, like this: template<typename Filter, typename Geometry> struct tag<boost::range_detail::filter_range<Filter, Geometry> > { typedef typename geometry::tag<Geometry>::type type; }; This was all that was necessary to enable range adaptors. I now discover that their names are recently changed, from filter_range to filtered_range, etc (to match the adaptors, understandable). Of course library developers may do these things in a namespace called range_detail, but I've some questions: - do you encourage or support or discourage using filtered_range etc. in library code? Namespace range_detail is normally not used by library users, but there is no other way for us to adapt them: the filtered function returns a range_detail::filtered_range struct, and we have to specialize on that specific struct... - if this is a generic need, would it not be better to move them out of namespace *detail? - I noticed that sliced and copied are not in namespace range_detail but in adaptors, for me that sounds OK, but it is expected that for consistancy it might move namespace in any future - are there more changes on the way? Regards, Barend

3 2

[MSM] constructor arguments for sub state/machines
by Richard Szabo 28 Dec '10

28 Dec '10

Hi all I have tried out the new feature of msm : using constructor arguments for substate/machines : namely : player p( back::states_ << Playing(back::states_ << Song1(some_Song1_data)) , boost::ref(data),3); see doc : http://svn.boost.org/svn/boost/trunk/libs/msm/doc/HTML/ch03s05.html#d0e2320 I have some problem with it :(. this case state Playing and Song1 will be constructed first with default constructor in back end constructor than the internally constructed Playing and Song1 will be assigned to the newly construed Playing / Song1 copy which got copied by value. The only reason to use this feature is to able to use reference members in the substates but for that reference members must be initialised in the member initialisation list of the constructor of the substates in order to provide the references constructor arguments must be used. Since subsates must provide default constructors it is not possible to always initialise reference members from outside. Furthermore substate must be copyable and must implement assignment which brings more harm than good :(. Is there a way to resolve these problems ? PS: Looking to the test: http://svn.boost.org/svn/boost/trunk/libs/msm/test/Constructor.cpp I think there is a bug : at with line : fsm.context_ = 20; according my understanding the compiler will create a SomeExternalContext object on the stack of the context of on_entry(Event const&,FSM& fsm) function and will replace the fsm.context_ reference to the reference of the newly constructed object one the stack so when the on_entry function exits the SomeExternalContext object will be removed from the stack so the fsm.context_ reference becomes invalid so code p.context_.bla == 20 actually should crash because it uses invalid reference. I think it is just working by chance ? p.start(); // after this p.context_ will be invalid BOOST_CHECK_MESSAGE(p.context_.bla == 20,"error with fsm entry behavior"); // accessing invalid reference Br. Richie

1 0

Re: [boost] Packaging in cross-compiling environment
by Vladimir Prus 28 Dec '10

28 Dec '10

On Tuesday, December 28, 2010 00:18:11 Ben Gamari wrote: > On Mon, 27 Dec 2010 23:13:29 +0300, Vladimir Prus <vladimir(a)codesourcery.com> wrote: > > The includes are supposed to be added by this code in libs/python/build/Jamfile.v2: > > [ cond [ python.configured ] : > > <library>/python//python_for_extensions ] > > > > where 'cond' is basically C's ?: operator. From your log, I suspect that > > python.configured is not set, because python.jam is unable to run python > > to check it's version. > > > > Could you try the below patch? > > That did the trick. I get into the python build at this point (although > things still fail with "LONG_BIT definition appears wrong for platform > (bad gcc/glibc config?)." errors, but that another matter). Good to know. > > Perhaps this would be a cleaner patch? Yes, it's cleaner. However, I have to figure what the code is trying to do in the first place. I'll take a look at this between Jan 1 and Jan 11. Thanks, Volodya

1 0

Packaging in cross-compiling environment
by Ben Gamari 27 Dec '10

27 Dec '10

Hey all, A few days ago I got around to updating an embedded Linux image (cross-compiled with openembedded[1]). Unfortunately, I soon hit a some realized that the latest Boost version in OpenEmbedded is 1.41. I initially thought it was quite strange that such a well-used library could be so out-of-date and thought I might try my hand at getting 1.45 running. I quickly found that the reason OE's package is so old is because they are using the Boost CMake fork, which hasn't been updated for some time. At first I found it strange that the packagers would use an alternative build system like this, but this is before I met bJam. Unfortunately, bJam has made what should have been a straightforward version bump one of the most unpleasant packaging experiences I have ever had. After much pain, I finally have a user-config.jam[2] capable of starting the build, but it quickly fails with a variety of compile errors. The first is related to icu, the test program for which fails during linking, gcc.link bin.v2/libs/regex/build/gcc-target/debug/has_icu bin.v2/libs/regex/build/gcc-target/debug/has_icu_test.o: In function `main': /home/bgamari/OE/angstrom-dev/work/armv7a-angstrom-linux-gnueabi/boost-1.45.0-r9.1/boost_1_45_0/libs/regex/bu ild/has_icu_test.cpp:24: undefined reference to `u_charFromName_4_2' collect2: ld returned 1 exit status "arm-angstrom-linux-gnueabi-g++" "-march=armv7-a" "-mtune=cortex-a8" "-mfpu=neon" "-mfloat-abi=softfp" "- L/home/bgamari/OE/angstrom-dev/sysroots/armv7a-angstrom-linux-gnueabi/usr/lib" "-Wl,-rpath-link,/home/bgamari/O E/angstrom-dev/sysroots/armv7a-angstrom-linux-gnueabi/usr/lib" "-Wl,-O1" "-Wl,--hash-style=gnu" "-mthumb-interw ork" "-mno-thumb" -L"/usr/lib" -Wl,-R -Wl,"/usr/bin" -Wl,-R -Wl,"/usr/lib" -Wl,-rpath-link -Wl,"/usr/lib" -o "b in.v2/libs/regex/build/gcc-target/debug/has_icu" -Wl,--start-group "bin.v2/libs/regex/build/gcc-target/debug/ha s_icu_test.o" -Wl,-Bstatic -Wl,-Bdynamic -licuuc -licui18n -licudata -Wl,--end-group -g -L/home/bgamari/OE/an gstrom-dev/sysroots/armv7a-angstrom-linux-gnueabi/usr/lib This appears to due to the build having used the icu 4.2 headers from /usr which is given as --includedir (which should be the install directory, according to the documentation) yet for is for some reason added to the include path list, "arm-angstrom-linux-gnueabi-g++" "-march=armv7-a" "-mtune=cortex-a8" "-mfpu=neon" "-mfloat-abi=softfp" "-L/home/bgamari/OE/angstrom-dev/sysroots/armv7a-a ngstrom-linux-gnueabi/usr/lib" "-Wl,-rpath-link,/home/bgamari/OE/angstrom-dev/sysroots/armv7a-angstrom-linux-gnueabi/usr/lib" "-Wl,-O1" "-Wl,--hash-style=gnu" "-mthumb-interwork" "-mno-thumb" -ftemplate-depth-128 -isystem/home/bgamari/OE/angstrom-dev/sysroots/armv7a-angstrom-linux-gnueabi/usr/include -O0 -fno-inline -Wall -pedantic -g -fPIC -DBOOST_ALL_NO_LIB=1 -DBOOST_HAS_ICU=1 -I"." -I"/usr/include" -c -o "bin.v2/libs/regex/build/gcc-target/debug/has_icu_test.o" "libs /regex/build/has_icu_test.cpp" This causes the system's icu headers to override the cross-compile environment's, wrecking havoc when it comes to link time. Does anyone know why bJam is doing this? The second pertains to Python. I have specified a python configuration listing the correct include and library paths in my user-config.jam yet it appears that bjam ignores it "arm-angstrom-linux-gnueabi-g++" "-march=armv7-a" "-mtune=cortex-a8" "-mfpu=neon" "-mfloat-abi=softfp" "- L/home/bgamari/OE/angstrom-dev/sysroots/armv7a-angstrom-linux-gnueabi/usr/lib" "-Wl,-rpath-link,/home/bgamari/O E/angstrom-dev/sysroots/armv7a-angstrom-linux-gnueabi/usr/lib" "-Wl,-O1" "-Wl,--hash-style=gnu" "-mthumb-interw ork" "-mno-thumb" -ftemplate-depth-128 -isystem/home/bgamari/OE/angstrom-dev/sysroots/armv7a-angstrom-linux-gn ueabi/usr/include -O3 -finline-functions -Wno-inline -Wall -pthread -fPIC -DBOOST_ALL_NO_LIB=1 -DBOOST_PYTHON_ SOURCE -DNDEBUG -I"." -c -o "bin.v2/libs/python/build/gcc-target/release/threading-multi/numeric.o" "libs/pyth on/src/numeric.cpp" ...failed gcc.compile.c++ bin.v2/libs/python/build/gcc-target/release/threading-multi/numeric.o... gcc.compile.c++ bin.v2/libs/math/build/gcc-target/release/threading-multi/sph_neumannf.o gcc.compile.c++ bin.v2/libs/python/build/gcc-target/release/threading-multi/list.o In file included from ./boost/python/detail/prefix.hpp:13:0, from ./boost/python/list.hpp:8, from libs/python/src/list.cpp:5: ./boost/python/detail/wrap_python.hpp:50:23: fatal error: pyconfig.h: No such file or directory compilation terminated. As indicated in the documentation, I have tried passing target-os=linux/python=2.6 to bjam but this does not appear to change bjam's behavior at all. When the build process begins, bjam produces this cryptic hint, error: No best alternative for /python_for_extensions next alternative: required properties: <python>2.6 <target-os>linux matched next alternative: required properties: <python>2.6 <target-os>linux matched error: No best alternative for /python_for_extensions next alternative: required properties: <python>2.6 <target-os>linux matched next alternative: required properties: <python>2.6 <target-os>linux matched Does anyone know what might be going on here? I seriously hope that the Boost project will consider dropping this seriously deficient, clunky, and user-unfriendly build system. When it works people will largely overlook its flaws, but most everyone I've heard who have actually worked with it seem to agree: stay away at all costs. I now completely understand why OpenEmbedded used the CMake fork. Cheers, - Ben [1] http://www.openembedded.org/ [2] user-config.jam using gcc : host : : <cxxflags> <linkflags> ; using gcc : target : arm-angstrom-linux-gnueabi-g++ -march=armv7-a -mtune=cortex-a8 -mfpu=neon -mfloat-abi=soft fp -L/home/bgamari/OE/angstrom-dev/sysroots/armv7a-angstrom-linux-gnueabi/usr/lib -Wl,-rpath-link,/home/bgamar i/OE/angstrom-dev/sysroots/armv7a-angstrom-linux-gnueabi/usr/lib -Wl,-O1 -Wl,--hash-style=gnu -mthumb-interwork -mno-thumb : <cxxflags>-isystem/home/bgamari/OE/angstrom-dev/sysroots/armv7a-angstrom-linux-gnueabi/usr/includ e -fexpensive-optimizations -frename-registers -fomit-frame-pointer -O2 -ggdb2 -isystem/home/bgamari/OE/angstro m-dev/sysroots/armv7a-angstrom-linux-gnueabi/usr/include -fexpensive-optimizations -frename-registers -fomit-fr ame-pointer -O2 -ggdb2 -fpermissive -fvisibility-inlines-hidden <linkflags>-L/home/bgamari/OE/angstrom-dev/sysr oots/armv7a-angstrom-linux-gnueabi/usr/lib -Wl,-rpath-link,/home/bgamari/OE/angstrom-dev/sysroots/armv7a-angstr om-linux-gnueabi/usr/lib -Wl,-O1 -Wl,--hash-style=gnu ; using python : 2.6 : python2.6 : /home/bgamari/OE/angstrom-dev/sysroots/armv7a-angstrom-linux-gnueabi/usr/include/python2.6 : /home/bgamari/OE/angstrom-dev/sysroots/armv7a-angstrom-linux-gnueabi/usr/lib ;

3 9

Phoenix3 Status update.
by Thomas Heller 27 Dec '10

27 Dec '10

Hi, some of you might have noticed that the version of phoenix3 located at https://svn.boost.org/trac/boost/browser/sandbox/SOC/2010/phoenix3 didn't compile from time time to. I just wanted to inform you that this is over now! Phoenix3 is in a stable state once again! All tests from boost.bind are passing! Placeholder unification is in place! Now ... up to documentation writing and checking for BLL compatibility ... The compilers i tested are: clang 2.8 gcc 4.5.1 gcc 4.2 (this only works with a patch for proto attached to this mail) I appreciate any feedback! I guess we can schedule the review now. Hartmut, does your offer still stand? Regards, Thomas

6 16

[dynamic_bitset] Append byte to the less significant end
by Romain CHANU 27 Dec '10

27 Dec '10

Hi, Here is my problem: i am using boost::dynamic_bitset and I would like to append a byte to the bitset. The idea is the following: 1) read a byte (represented as an unsigned char) 2) append the byte to the bitset 3) repeat these steps until there is no more data to read The current "append" in the API appends a byte to the most significant end. I would like to actually append the byte to the less significant end. The only solution that I have found so far is to concatenate two bitsets: http://pastebin.com/cguqaMgS I am not sure this is a very efficient way. Do you have any other suggestions? Thank you for your help and Merry Christmas. Romain

2 2

[range][stride] broken?
by Maxim Yanchenko 27 Dec '10

27 Dec '10

Consider the following test: std::vector<int> v; boost::push_back( v, boost::irange(0, 30) ); boost::copy( v, std::ostream_iterator<int>(std::cout, " ")); std::cout << std::endl << std::endl; for ( int i = 1; i <= 30; i++ ) { std::cout << std::setw(2) << i << ": "; boost::copy( v | boost::adaptors::strided(i), std::ostream_iterator<int>(std::cout, " ")); std::cout << std::endl; //std::cout << std::setw(2) << "" << ": "; //BOOST_FOREACH( int x, v | boost::adaptors::strided(i) ) // std::cout << x << ' '; //std::cout << std::endl; } Here is the output: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 1: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 2: 0 2 4 6 8 10 12 14 16 18 20 22 24 26 28 3: 0 3 6 9 12 15 18 21 24 27 4: 0 4 8 12 16 20 24 ///< where is 28? 5: 0 5 10 15 20 25 6: 0 6 12 18 24 7: 0 7 14 21 ///< where is 28? 8: 0 8 16 ///< where is 24? 9: 0 9 18 ///< where is 27? 10: 0 10 20 11: 0 11 ///< where is 22? ... 16: 0 ///< where is 16? etc If you uncomment the BOOST_FOREACH code, it crashes at stride=4 (prints 28 and then crashes): 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 1: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 : 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 2: 0 2 4 6 8 10 12 14 16 18 20 22 24 26 28 : 0 2 4 6 8 10 12 14 16 18 20 22 24 26 28 3: 0 3 6 9 12 15 18 21 24 27 : 0 3 6 9 12 15 18 21 24 27 4: 0 4 8 12 16 20 24 /usr/include/stlport-5.2.1/stlport/stl/debug/_iterator.h(170): STL assertion failure : _Incrementable(*this, __n, _Iterator_category()) : 0 4 8 12 16 20 24 28 unknown location:0: fatal error in "test": signal: SIGABRT (application abort requested) Nothing changes if I replace "v | boost::adaptors::strided(i)" with "boost::adaptors::stride(v,i)". It's Boost 1.45.0 on STLPort 5.2.1, gcc 4.4. IF I switch from std::vector to boost::array, BOOST_FOREACH just doesn't stop and keeps printing memory until crash, so I don't think it's an STLPort problem. Am I doing anything wrong, or range::stride is broken? Thanks, Maxim

3 10

$100 reward to get Boost libraries to run in Windows 7 with Visual Studio 2008 Express Edition
by Paul Bergen 25 Dec '10

25 Dec '10

I'm a veteran c++ coder and don't normally resort to such tactics, but I'm desperate. I've got a looming deadline to finish a big task and need to wrap up a minor utility that's less than 1% of the project but is consuming all my time because it uses boost for socket i/o, but I can't get the boost itself to work on windows 7 with vs2008ee, and it's blocking me from getting my core projects complete. The same code works fine on someone else's windows vista PC with vs2010, and under Linux. Given how popular boost is I can't believe it's simply that boost doesn't run on Windows 7. So, before I go out and buy another PC with Vista, I figured I'd offer a bit of cash for a Boost guru to VNC into my PC and look at it. The problem is that every time I do anything with the boost libraries they crash deep within the boost code. Since I'm a boost/bjam newbie, I'm just struggling trying every combination of bjam option and project option, but nothing seems to generate libraries that actually work, and, after fighting with it for about 15 hours, I'm totally out of time to mess with it anymore or I won't get the rest of my code done. If a seasoned Boost dev agrees to do it, I'll send you money by paypal first, then give you VNC access to my dev box so you can login and see for yourself what's happening. My email is bergen.p0(a)gmail.com. Basically, I use bjam like this: bjam toolset=msvc-9.0 variant=release threading=multi link=shared --with-system --with-thread --with-date_time --with-regex --with-serialization stage then every time I do anything socket related, it crashes in xmemory, deallocate with the following backtrace: ntdll.dll!77eefadc() [Frames below may be incorrect and/or missing, no symbols loaded for ntdll.dll] ntdll.dll!77eb272c() ntdll.dll!77e7e1ef() KernelBase.dll!76b9468e() DeviceManager.exe!_CrtIsValidHeapPointer(const void * pUserData=0x00d554d0) Line 2103 C++ DeviceManager.exe!_free_dbg_nolock(void * pUserData=0x00d554d0, int nBlockUse=1) Line 1317 + 0x9 bytes C++ DeviceManager.exe!_free_dbg(void * pUserData=0x00d554d0, int nBlockUse=1) Line 1258 + 0xd bytes C++ DeviceManager.exe!operator delete(void * pUserData=0x00d554d0) Line 54 + 0x10 bytes C++ > DeviceManager.exe!std::allocator<char>::deallocate(char * _Ptr=0x00d554d0, unsigned int __formal=64) Line 140 + 0x9 bytes C++ DeviceManager.exe!std::basic_string<char,std::char_traits<char>,std::allocator<char> >::_Tidy(bool _Built=true, unsigned int _Newsize=0) Line 2158 C++ DeviceManager.exe!std::basic_string<char,std::char_traits<char>,std::allocator<char> >::~basic_string<char,std::char_traits<char>,std::allocator<char> >() Line 907 C++ DeviceManager.exe!http::server3::connection::handle_read(const boost::system::error_code & e={...}, unsigned int bytes_transferred=0) Line 190 C++ DeviceManager.exe!boost::_mfi::mf2<void,http::server3::connection,boost::system::error_code const &,unsigned int>::call<boost::shared_ptr<http::server3::connection>,boost::system::error_code const ,unsigned int>(boost::shared_ptr<http::server3::connection> & u={...}, const void * __formal=0x00000000, const boost::system::error_code & b1={...}, unsigned int & b2=0) Line 271 + 0x27 bytes C++ DeviceManager.exe!boost::_mfi::mf2<void,http::server3::connection,boost::system::error_code const &,unsigned int>::operator()<boost::shared_ptr<http::server3::connection> >(boost::shared_ptr<http::server3::connection> & u={...}, const boost::system::error_code & a1={...}, unsigned int a2=0) Line 287 C++ DeviceManager.exe!boost::_bi::list3<boost::_bi::value<boost::shared_ptr<http::server3::connection> >,boost::arg<1>,boost::arg<2> >::operator()<boost::_mfi::mf2<void,http::server3::connection,boost::system::error_code const &,unsigned int>,boost::_bi::list2<boost::system::error_code const &,unsigned int const &> >(boost::_bi::type<void> __formal={...}, boost::_mfi::mf2<void,http::server3::connection,boost::system::error_code const &,unsigned int> & f={...}, boost::_bi::list2<boost::system::error_code const &,unsigned int const &> & a={...}, boost::_bi::type<void> __formal={...}) Line 393 C++ DeviceManager.exe!boost::_bi::bind_t<void,boost::_mfi::mf2<void,http::server3::connection,boost::system::error_code const &,unsigned int>,boost::_bi::list3<boost::_bi::value<boost::shared_ptr<http::server3::connection> >,boost::arg<1>,boost::arg<2> > >::operator()<boost::system::error_code,unsigned int>(const boost::system::error_code & a1={...}, const unsigned int & a2=0) Line 103 C++ DeviceManager.exe!boost::asio::detail::binder2<boost::_bi::bind_t<void,boost::_mfi::mf2<void,http::server3::connection,boost::system::error_code const &,unsigned int>,boost::_bi::list3<boost::_bi::value<boost::shared_ptr<http::server3::connection> >,boost::arg<1>,boost::arg<2> > >,boost::system::error_code,unsigned int>::operator()() Line 99 C++ DeviceManager.exe!boost::asio::asio_handler_invoke<boost::asio::detail::binder2<boost::_bi::bind_t<void,boost::_mfi::mf2<void,http::server3::connection,boost::system::error_code const &,unsigned int>,boost::_bi::list3<boost::_bi::value<boost::shared_ptr<http::server3::connection> >,boost::arg<1>,boost::arg<2> > >,boost::system::error_code,unsigned int> >(boost::asio::detail::binder2<boost::_bi::bind_t<void,boost::_mfi::mf2<void,http::server3::connection,boost::system::error_code const &,unsigned int>,boost::_bi::list3<boost::_bi::value<boost::shared_ptr<http::server3::connection> >,boost::arg<1>,boost::arg<2> > >,boost::system::error_code,unsigned int> function={...}, ...) Line 65 C++ DeviceManager.exe!boost_asio_handler_invoke_helpers::invoke<boost::asio::detail::binder2<boost::_bi::bind_t<void,boost::_mfi::mf2<void,http::server3::connection,boost::system::error_code const &,unsigned int>,boost::_bi::list3<boost::_bi::value<boost::shared_ptr<http::server3::connection> >,boost::arg<1>,boost::arg<2> > >,boost::system::error_code,unsigned int>,boost::_bi::bind_t<void,boost::_mfi::mf2<void,http::server3::connection,boost::system::error_code const &,unsigned int>,boost::_bi::list3<boost::_bi::value<boost::shared_ptr<http::server3::connection> >,boost::arg<1>,boost::arg<2> > > >(const boost::asio::detail::binder2<boost::_bi::bind_t<void,boost::_mfi::mf2<void,http::server3::connection,boost::system::error_code const &,unsigned int>,boost::_bi::list3<boost::_bi::value<boost::shared_ptr<http::server3::connection> >,boost::arg<1>,boost::arg<2> > >,boost::system::error_code,unsigned int> & function={...}, boost::_bi::bind_t<void,boost::_mfi::mf2<void,http::server3::connection,boost::system::error_code const &,unsigned int>,boost::_bi::list3<boost::_bi::value<boost::shared_ptr<http::server3::connection> >,boost::arg<1>,boost::arg<2> > > & context={...}) Line 39 + 0x2c bytes C++ DeviceManager.exe!boost::asio::detail::asio_handler_invoke<boost::asio::detail::binder2<boost::_bi::bind_t<void,boost::_mfi::mf2<void,http::server3::connection,boost::system::error_code const &,unsigned int>,boost::_bi::list3<boost::_bi::value<boost::shared_ptr<http::server3::connection> >,boost::arg<1>,boost::arg<2> > >,boost::system::error_code,unsigned int>,boost::_bi::bind_t<void,boost::_mfi::mf2<void,http::server3::connection,boost::system::error_code const &,unsigned int>,boost::_bi::list3<boost::_bi::value<boost::shared_ptr<http::server3::connection> >,boost::arg<1>,boost::arg<2> > >,boost::system::error_code,unsigned int>(const boost::asio::detail::binder2<boost::_bi::bind_t<void,boost::_mfi::mf2<void,http::server3::connection,boost::system::error_code const &,unsigned int>,boost::_bi::list3<boost::_bi::value<boost::shared_ptr<http::server3::connection> >,boost::arg<1>,boost::arg<2> > >,boost::system::error_code,unsigned int> & function={...}, boost::asio::detail::binder2<boost::_bi::bind_t<void,boost::_mfi::mf2<void,http::server3::connection,boost::system::error_code const &,unsigned int>,boost::_bi::list3<boost::_bi::value<boost::shared_ptr<http::server3::connection> >,boost::arg<1>,boost::arg<2> > >,boost::system::error_code,unsigned int> * this_handler=0x030ce8a4) Line 133 + 0xd bytes C++ DeviceManager.exe!boost_asio_handler_invoke_helpers::invoke<boost::asio::detail::binder2<boost::_bi::bind_t<void,boost::_mfi::mf2<void,http::server3::connection,boost::system::error_code const &,unsigned int>,boost::_bi::list3<boost::_bi::value<boost::shared_ptr<http::server3::connection> >,boost::arg<1>,boost::arg<2> > >,boost::system::error_code,unsigned int>,boost::asio::detail::binder2<boost::_bi::bind_t<void,boost::_mfi::mf2<void,http::server3::connection,boost::system::error_code const &,unsigned int>,boost::_bi::list3<boost::_bi::value<boost::shared_ptr<http::server3::connection> >,boost::arg<1>,boost::arg<2> > >,boost::system::error_code,unsigned int> >(const boost::asio::detail::binder2<boost::_bi::bind_t<void,boost::_mfi::mf2<void,http::server3::connection,boost::system::error_code const &,unsigned int>,boost::_bi::list3<boost::_bi::value<boost::shared_ptr<http::server3::connection> >,boost::arg<1>,boost::arg<2> > >,boost::system::error_code,unsigned int> & function={...}, boost::asio::detail::binder2<boost::_bi::bind_t<void,boost::_mfi::mf2<void,http::server3::connection,boost::system::error_code const &,unsigned int>,boost::_bi::list3<boost::_bi::value<boost::shared_ptr<http::server3::connection> >,boost::arg<1>,boost::arg<2> > >,boost::system::error_code,unsigned int> & context={...}) Line 39 + 0x16 bytes C++ DeviceManager.exe!boost::asio::detail::strand_service::dispatch<boost::asio::detail::binder2<boost::_bi::bind_t<void,boost::_mfi::mf2<void,http::server3::connection,boost::system::error_code const &,unsigned int>,boost::_bi::list3<boost::_bi::value<boost::shared_ptr<http::server3::connection> >,boost::arg<1>,boost::arg<2> > >,boost::system::error_code,unsigned int> >(boost::asio::detail::strand_service::strand_impl * & impl=0x022dbc78, boost::asio::detail::binder2<boost::_bi::bind_t<void,boost::_mfi::mf2<void,http::server3::connection,boost::system::error_code const &,unsigned int>,boost::_bi::list3<boost::_bi::value<boost::shared_ptr<http::server3::connection> >,boost::arg<1>,boost::arg<2> > >,boost::system::error_code,unsigned int> handler={...}) Line 65 + 0xd bytes C++ DeviceManager.exe!boost::asio::io_service::strand::dispatch<boost::asio::detail::binder2<boost::_bi::bind_t<void,boost::_mfi::mf2<void,http::server3::connection,boost::system::error_code const &,unsigned int>,boost::_bi::list3<boost::_bi::value<boost::shared_ptr<http::server3::connection> >,boost::arg<1>,boost::arg<2> > >,boost::system::error_code,unsigned int> >(boost::asio::detail::binder2<boost::_bi::bind_t<void,boost::_mfi::mf2<void,http::server3::connection,boost::system::error_code const &,unsigned int>,boost::_bi::list3<boost::_bi::value<boost::shared_ptr<http::server3::connection> >,boost::arg<1>,boost::arg<2> > >,boost::system::error_code,unsigned int> handler={...}) Line 160 C++ DeviceManager.exe!boost::asio::detail::wrapped_handler<boost::asio::io_service::strand,boost::_bi::bind_t<void,boost::_mfi::mf2<void,http::server3::connection,boost::system::error_code const &,unsigned int>,boost::_bi::list3<boost::_bi::value<boost::shared_ptr<http::server3::connection> >,boost::arg<1>,boost::arg<2> > > >::operator()<boost::system::error_code,unsigned int>(const boost::system::error_code & arg1={...}, const unsigned int & arg2=0) Line 66 C++ DeviceManager.exe!boost::asio::detail::binder2<boost::asio::detail::wrapped_handler<boost::asio::io_service::strand,boost::_bi::bind_t<void,boost::_mfi::mf2<void,http::server3::connection,boost::system::error_code const &,unsigned int>,boost::_bi::list3<boost::_bi::value<boost::shared_ptr<http::server3::connection> >,boost::arg<1>,boost::arg<2> > > >,boost::system::error_code,unsigned int>::operator()() Line 99 C++ DeviceManager.exe!boost::asio::detail::rewrapped_handler<boost::asio::detail::binder2<boost::asio::detail::wrapped_handler<boost::asio::io_service::strand,boost::_bi::bind_t<void,boost::_mfi::mf2<void,http::server3::connection,boost::system::error_code const &,unsigned int>,boost::_bi::list3<boost::_bi::value<boost::shared_ptr<http::server3::connection> >,boost::arg<1>,boost::arg<2> > > >,boost::system::error_code,unsigned int>,boost::_bi::bind_t<void,boost::_mfi::mf2<void,http::server3::connection,boost::system::error_code const &,unsigned int>,boost::_bi::list3<boost::_bi::value<boost::shared_ptr<http::server3::connection> >,boost::arg<1>,boost::arg<2> > > >::operator()() Line 138 C++ DeviceManager.exe!boost::asio::asio_handler_invoke<boost::asio::detail::rewrapped_handler<boost::asio::detail::binder2<boost::asio::detail::wrapped_handler<boost::asio::io_service::strand,boost::_bi::bind_t<void,boost::_mfi::mf2<void,http::server3::connection,boost::system::error_code const &,unsigned int>,boost::_bi::list3<boost::_bi::value<boost::shared_ptr<http::server3::connection> >,boost::arg<1>,boost::arg<2> > > >,boost::system::error_code,unsigned int>,boost::_bi::bind_t<void,boost::_mfi::mf2<void,http::server3::connection,boost::system::error_code const &,unsigned int>,boost::_bi::list3<boost::_bi::value<boost::shared_ptr<http::server3::connection> >,boost::arg<1>,boost::arg<2> > > > >(boost::asio::detail::rewrapped_handler<boost::asio::detail::binder2<boost::asio::detail::wrapped_handler<boost::asio::io_service::strand,boost::_bi::bind_t<void,boost::_mfi::mf2<void,http::server3::connection,boost::system::error_code const &,unsigned int>,boost::_bi::list3<boost::_bi::value<boost::shared_ptr<http::server3::connection> >,boost::arg<1>,boost::arg<2> > > >,boost::system::error_code,unsigned int>,boost::_bi::bind_t<void,boost::_mfi::mf2<void,http::server3::connection,boost::system::error_code const &,unsigned int>,boost::_bi::list3<boost::_bi::value<boost::shared_ptr<http::server3::connection> >,boost::arg<1>,boost::arg<2> > > > function={...}, ...) Line 65 C++ DeviceManager.exe!boost_asio_handler_invoke_helpers::invoke<boost::asio::detail::rewrapped_handler<boost::asio::detail::binder2<boost::asio::detail::wrapped_handler<boost::asio::io_service::strand,boost::_bi::bind_t<void,boost::_mfi::mf2<void,http::server3::connection,boost::system::error_code const &,unsigned int>,boost::_bi::list3<boost::_bi::value<boost::shared_ptr<http::server3::connection> >,boost::arg<1>,boost::arg<2> > > >,boost::system::error_code,unsigned int>,boost::_bi::bind_t<void,boost::_mfi::mf2<void,http::server3::connection,boost::system::error_code const &,unsigned int>,boost::_bi::list3<boost::_bi::value<boost::shared_ptr<http::server3::connection> >,boost::arg<1>,boost::arg<2> > > >,boost::_bi::bind_t<void,boost::_mfi::mf2<void,http::server3::connection,boost::system::error_code const &,unsigned int>,boost::_bi::list3<boost::_bi::value<boost::shared_ptr<http::server3::connection> >,boost::arg<1>,boost::arg<2> > > >(const boost::asio::detail::rewrapped_handler<boost::asio::detail::binder2<boost::asio::detail::wrapped_handler<boost::asio::io_service::strand,boost::_bi::bind_t<void,boost::_mfi::mf2<void,http::server3::connection,boost::system::error_code const &,unsigned int>,boost::_bi::list3<boost::_bi::value<boost::shared_ptr<http::server3::connection> >,boost::arg<1>,boost::arg<2> > > >,boost::system::error_code,unsigned int>,boost::_bi::bind_t<void,boost::_mfi::mf2<void,http::server3::connection,boost::system::error_code const &,unsigned int>,boost::_bi::list3<boost::_bi::value<boost::shared_ptr<http::server3::connection> >,boost::arg<1>,boost::arg<2> > > > & function={...}, boost::_bi::bind_t<void,boost::_mfi::mf2<void,http::server3::connection,boost::system::error_code const &,unsigned int>,boost::_bi::list3<boost::_bi::value<boost::shared_ptr<http::server3::connection> >,boost::arg<1>,boost::arg<2> > > & context={...}) Line 39 + 0x2c bytes C++ DeviceManager.exe!boost::asio::detail::asio_handler_invoke<boost::asio::detail::rewrapped_handler<boost::asio::detail::binder2<boost::asio::detail::wrapped_handler<boost::asio::io_service::strand,boost::_bi::bind_t<void,boost::_mfi::mf2<void,http::server3::connection,boost::system::error_code const &,unsigned int>,boost::_bi::list3<boost::_bi::value<boost::shared_ptr<http::server3::connection> >,boost::arg<1>,boost::arg<2> > > >,boost::system::error_code,unsigned int>,boost::_bi::bind_t<void,boost::_mfi::mf2<void,http::server3::connection,boost::system::error_code const &,unsigned int>,boost::_bi::list3<boost::_bi::value<boost::shared_ptr<http::server3::connection> >,boost::arg<1>,boost::arg<2> > > >,boost::asio::detail::binder2<boost::asio::detail::wrapped_handler<boost::asio::io_service::strand,boost::_bi::bind_t<void,boost::_mfi::mf2<void,http::server3::connection,boost::system::error_code const &,unsigned int>,boost::_bi::list3<boost::_bi::value<boost::shared_ptr<http::server3::connection> >,boost::arg<1>,boost::arg<2> > > >,boost::system::error_code,unsigned int>,boost::_bi::bind_t<void,boost::_mfi::mf2<void,http::server3::connection,boost::system::error_code const &,unsigned int>,boost::_bi::list3<boost::_bi::value<boost::shared_ptr<http::server3::connection> >,boost::arg<1>,boost::arg<2> > > >(const boost::asio::detail::rewrapped_handler<boost::asio::detail::binder2<boost::asio::detail::wrapped_handler<boost::asio::io_service::strand,boost::_bi::bind_t<void,boost::_mfi::mf2<void,http::server3::connection,boost::system::error_code const &,unsigned int>,boost::_bi::list3<boost::_bi::value<boost::shared_ptr<http::server3::connection> >,boost::arg<1>,boost::arg<2> > > >,boost::system::error_code,unsigned int>,boost::_bi::bind_t<void,boost::_mfi::mf2<void,http::server3::connection,boost::system::error_code const &,unsigned int>,boost::_bi::list3<boost::_bi::value<boost::shared_ptr<http::server3::connection> >,boost::arg<1>,boost::arg<2> > > > & function={...}, boost::asio::detail::rewrapped_handler<boost::asio::detail::binder2<boost::asio::detail::wrapped_handler<boost::asio::io_service::strand,boost::_bi::bind_t<void,boost::_mfi::mf2<void,http::server3::connection,boost::system::error_code const &,unsigned int>,boost::_bi::list3<boost::_bi::value<boost::shared_ptr<http::server3::connection> >,boost::arg<1>,boost::arg<2> > > >,boost::system::error_code,unsigned int>,boost::_bi::bind_t<void,boost::_mfi::mf2<void,http::server3::connection,boost::system::error_code const &,unsigned int>,boost::_bi::list3<boost::_bi::value<boost::shared_ptr<http::server3::connection> >,boost::arg<1>,boost::arg<2> > > > * this_handler=0x030cf1e8) Line 196 + 0x10 bytes C++ DeviceManager.exe!boost_asio_handler_invoke_helpers::invoke<boost::asio::detail::rewrapped_handler<boost::asio::detail::binder2<boost::asio::detail::wrapped_handler<boost::asio::io_service::strand,boost::_bi::bind_t<void,boost::_mfi::mf2<void,http::server3::connection,boost::system::error_code const &,unsigned int>,boost::_bi::list3<boost::_bi::value<boost::shared_ptr<http::server3::connection> >,boost::arg<1>,boost::arg<2> > > >,boost::system::error_code,unsigned int>,boost::_bi::bind_t<void,boost::_mfi::mf2<void,http::server3::connection,boost::system::error_code const &,unsigned int>,boost::_bi::list3<boost::_bi::value<boost::shared_ptr<http::server3::connection> >,boost::arg<1>,boost::arg<2> > > >,boost::asio::detail::rewrapped_handler<boost::asio::detail::binder2<boost::asio::detail::wrapped_handler<boost::asio::io_service::strand,boost::_bi::bind_t<void,boost::_mfi::mf2<void,http::server3::connection,boost::system::error_code const &,unsigned int>,boost::_bi::list3<boost::_bi::value<boost::shared_ptr<http::server3::connection> >,boost::arg<1>,boost::arg<2> > > >,boost::system::error_code,unsigned int>,boost::_bi::bind_t<void,boost::_mfi::mf2<void,http::server3::connection,boost::system::error_code const &,unsigned int>,boost::_bi::list3<boost::_bi::value<boost::shared_ptr<http::server3::connection> >,boost::arg<1>,boost::arg<2> > > > >(const boost::asio::detail::rewrapped_handler<boost::asio::detail::binder2<boost::asio::detail::wrapped_handler<boost::asio::io_service::strand,boost::_bi::bind_t<void,boost::_mfi::mf2<void,http::server3::connection,boost::system::error_code const &,unsigned int>,boost::_bi::list3<boost::_bi::value<boost::shared_ptr<http::server3::connection> >,boost::arg<1>,boost::arg<2> > > >,boost::system::error_code,unsigned int>,boost::_bi::bind_t<void,boost::_mfi::mf2<void,http::server3::connection,boost::system::error_code const &,unsigned int>,boost::_bi::list3<boost::_bi::value<boost::shared_ptr<http::server3::connection> >,boost::arg<1>,boost::arg<2> > > > & function={...}, boost::asio::detail::rewrapped_handler<boost::asio::detail::binder2<boost::asio::detail::wrapped_handler<boost::asio::io_service::strand,boost::_bi::bind_t<void,boost::_mfi::mf2<void,http::server3::connection,boost::system::error_code const &,unsigned int>,boost::_bi::list3<boost::_bi::value<boost::shared_ptr<http::server3::connection> >,boost::arg<1>,boost::arg<2> > > >,boost::system::error_code,unsigned int>,boost::_bi::bind_t<void,boost::_mfi::mf2<void,http::server3::connection,boost::system::error_code const &,unsigned int>,boost::_bi::list3<boost::_bi::value<boost::shared_ptr<http::server3::connection> >,boost::arg<1>,boost::arg<2> > > > & context={...}) Line 39 + 0x16 bytes C++ DeviceManager.exe!boost::asio::detail::strand_service::dispatch<boost::asio::detail::rewrapped_handler<boost::asio::detail::binder2<boost::asio::detail::wrapped_handler<boost::asio::io_service::strand,boost::_bi::bind_t<void,boost::_mfi::mf2<void,http::server3::connection,boost::system::error_code const &,unsigned int>,boost::_bi::list3<boost::_bi::value<boost::shared_ptr<http::server3::connection> >,boost::arg<1>,boost::arg<2> > > >,boost::system::error_code,unsigned int>,boost::_bi::bind_t<void,boost::_mfi::mf2<void,http::server3::connection,boost::system::error_code const &,unsigned int>,boost::_bi::list3<boost::_bi::value<boost::shared_ptr<http::server3::connection> >,boost::arg<1>,boost::arg<2> > > > >(boost::asio::detail::strand_service::strand_impl * & impl=0x022dbc78, boost::asio::detail::rewrapped_handler<boost::asio::detail::binder2<boost::asio::detail::wrapped_handler<boost::asio::io_service::strand,boost::_bi::bind_t<void,boost::_mfi::mf2<void,http::server3::connection,boost::system::error_code const &,unsigned int>,boost::_bi::list3<boost::_bi::value<boost::shared_ptr<http::server3::connection> >,boost::arg<1>,boost::arg<2> > > >,boost::system::error_code,unsigned int>,boost::_bi::bind_t<void,boost::_mfi::mf2<void,http::server3::connection,boost::system::error_code const &,unsigned int>,boost::_bi::list3<boost::_bi::value<boost::shared_ptr<http::server3::connection> >,boost::arg<1>,boost::arg<2> > > > handler={...}) Line 97 + 0xd bytes C++ DeviceManager.exe!boost::asio::io_service::strand::dispatch<boost::asio::detail::rewrapped_handler<boost::asio::detail::binder2<boost::asio::detail::wrapped_handler<boost::asio::io_service::strand,boost::_bi::bind_t<void,boost::_mfi::mf2<void,http::server3::connection,boost::system::error_code const &,unsigned int>,boost::_bi::list3<boost::_bi::value<boost::shared_ptr<http::server3::connection> >,boost::arg<1>,boost::arg<2> > > >,boost::system::error_code,unsigned int>,boost::_bi::bind_t<void,boost::_mfi::mf2<void,http::server3::connection,boost::system::error_code const &,unsigned int>,boost::_bi::list3<boost::_bi::value<boost::shared_ptr<http::server3::connection> >,boost::arg<1>,boost::arg<2> > > > >(boost::asio::detail::rewrapped_handler<boost::asio::detail::binder2<boost::asio::detail::wrapped_handler<boost::asio::io_service::strand,boost::_bi::bind_t<void,boost::_mfi::mf2<void,http::server3::connection,boost::system::error_code const &,unsigned int>,boost::_bi::list3<boost::_bi::value<boost::shared_ptr<http::server3::connection> >,boost::arg<1>,boost::arg<2> > > >,boost::system::error_code,unsigned int>,boost::_bi::bind_t<void,boost::_mfi::mf2<void,http::server3::connection,boost::system::error_code const &,unsigned int>,boost::_bi::list3<boost::_bi::value<boost::shared_ptr<http::server3::connection> >,boost::arg<1>,boost::arg<2> > > > handler={...}) Line 160 C++ DeviceManager.exe!boost::asio::detail::asio_handler_invoke<boost::asio::detail::binder2<boost::asio::detail::wrapped_handler<boost::asio::io_service::strand,boost::_bi::bind_t<void,boost::_mfi::mf2<void,http::server3::connection,boost::system::error_code const &,unsigned int>,boost::_bi::list3<boost::_bi::value<boost::shared_ptr<http::server3::connection> >,boost::arg<1>,boost::arg<2> > > >,boost::system::error_code,unsigned int>,boost::asio::io_service::strand,boost::_bi::bind_t<void,boost::_mfi::mf2<void,http::server3::connection,boost::system::error_code const &,unsigned int>,boost::_bi::list3<boost::_bi::value<boost::shared_ptr<http::server3::connection> >,boost::arg<1>,boost::arg<2> > > >(const boost::asio::detail::binder2<boost::asio::detail::wrapped_handler<boost::asio::io_service::strand,boost::_bi::bind_t<void,boost::_mfi::mf2<void,http::server3::connection,boost::system::error_code const &,unsigned int>,boost::_bi::list3<boost::_bi::value<boost::shared_ptr<http::server3::connection> >,boost::arg<1>,boost::arg<2> > > >,boost::system::error_code,unsigned int> & function={...}, boost::asio::detail::wrapped_handler<boost::asio::io_service::strand,boost::_bi::bind_t<void,boost::_mfi::mf2<void,http::server3::connection,boost::system::error_code const &,unsigned int>,boost::_bi::list3<boost::_bi::value<boost::shared_ptr<http::server3::connection> >,boost::arg<1>,boost::arg<2> > > > * this_handler=0x030cf600) Line 173 C++ DeviceManager.exe!boost_asio_handler_invoke_helpers::invoke<boost::asio::detail::binder2<boost::asio::detail::wrapped_handler<boost::asio::io_service::strand,boost::_bi::bind_t<void,boost::_mfi::mf2<void,http::server3::connection,boost::system::error_code const &,unsigned int>,boost::_bi::list3<boost::_bi::value<boost::shared_ptr<http::server3::connection> >,boost::arg<1>,boost::arg<2> > > >,boost::system::error_code,unsigned int>,boost::asio::detail::wrapped_handler<boost::asio::io_service::strand,boost::_bi::bind_t<void,boost::_mfi::mf2<void,http::server3::connection,boost::system::error_code const &,unsigned int>,boost::_bi::list3<boost::_bi::value<boost::shared_ptr<http::server3::connection> >,boost::arg<1>,boost::arg<2> > > > >(const boost::asio::detail::binder2<boost::asio::detail::wrapped_handler<boost::asio::io_service::strand,boost::_bi::bind_t<void,boost::_mfi::mf2<void,http::server3::connection,boost::system::error_code const &,unsigned int>,boost::_bi::list3<boost::_bi::value<boost::shared_ptr<http::server3::connection> >,boost::arg<1>,boost::arg<2> > > >,boost::system::error_code,unsigned int> & function={...}, boost::asio::detail::wrapped_handler<boost::asio::io_service::strand,boost::_bi::bind_t<void,boost::_mfi::mf2<void,http::server3::connection,boost::system::error_code const &,unsigned int>,boost::_bi::list3<boost::_bi::value<boost::shared_ptr<http::server3::connection> >,boost::arg<1>,boost::arg<2> > > > & context={...}) Line 39 + 0x16 bytes C++ DeviceManager.exe!boost::asio::detail::win_iocp_socket_recv_op<boost::asio::mutable_buffers_1,boost::asio::detail::wrapped_handler<boost::asio::io_service::strand,boost::_bi::bind_t<void,boost::_mfi::mf2<void,http::server3::connection,boost::system::error_code const &,unsigned int>,boost::_bi::list3<boost::_bi::value<boost::shared_ptr<http::server3::connection> >,boost::arg<1>,boost::arg<2> > > > >::do_complete(boost::asio::detail::win_iocp_io_service * owner=0x022d19f8, boost::asio::detail::win_iocp_operation * base=0x022df948, boost::system::error_code ec={...}, unsigned int bytes_transferred=0) Line 91 + 0xd bytes C++ DeviceManager.exe!boost::asio::detail::win_iocp_operation::complete(boost::asio::detail::win_iocp_io_service & owner={...}, const boost::system::error_code & ec={...}, unsigned int bytes_transferred=0) Line 42 + 0x20 bytes C++ DeviceManager.exe!boost::asio::detail::win_iocp_io_service::do_one(bool block=true, boost::system::error_code & ec={...}) Line 387 C++ DeviceManager.exe!boost::asio::detail::win_iocp_io_service::run(boost::system::error_code & ec={...}) Line 160 + 0xe bytes C++ DeviceManager.exe!boost::asio::io_service::run() Line 57 + 0xf bytes C++ DeviceManager.exe!boost::_mfi::mf0<unsigned int,boost::asio::io_service>::operator()(boost::asio::io_service * p=0x0018fb30) Line 49 + 0xc bytes C++ DeviceManager.exe!boost::_bi::list1<boost::_bi::value<boost::asio::io_service *> >::operator()<unsigned int,boost::_mfi::mf0<unsigned int,boost::asio::io_service>,boost::_bi::list0>(boost::_bi::type<unsigned int> __formal={...}, boost::_mfi::mf0<unsigned int,boost::asio::io_service> & f={...}, boost::_bi::list0 & a={...}, boost::_bi::type<unsigned int> __formal={...}) Line 244 C++ DeviceManager.exe!boost::_bi::bind_t<unsigned int,boost::_mfi::mf0<unsigned int,boost::asio::io_service>,boost::_bi::list1<boost::_bi::value<boost::asio::io_service *> > >::operator()() Line 21 C++ DeviceManager.exe!boost::detail::thread_data<boost::_bi::bind_t<unsigned int,boost::_mfi::mf0<unsigned int,boost::asio::io_service>,boost::_bi::list1<boost::_bi::value<boost::asio::io_service *> > > >::run() Line 62 C++ boost_thread-vc90-mt-gd-1_44.dll!boost::`anonymous namespace'::thread_start_function(void * param=0x00748fc0) Line 169 C++ msvcr90d.dll!61e5dfd3() msvcr90d.dll!61e5df69() kernel32.dll!77143677() ntdll.dll!77e59d72() ntdll.dll!77e59d45()

7 7

[OT] CPH (Copenhagen) STL
by Hal Finkel 24 Dec '10

24 Dec '10

Hello, I have no connection to the CPH STL project, but I have spent several hours looking over their technical reports, and a number of them are quite interesting. They detail research into different implementation choices for the STL containers and some of the algorithms, and have benchmarks, practical implementation notes, etc. Many of the reports even include full source code in the appendices. http://www.cphstl.dk/WWW/reports.html For example, I recommend looking at: 2004-2 - Mads D. Kristensen: Vector implementation for the CPH STL Even though these are academic in nature, unlike most papers about data structures which I've read, they deal explicitly with the issues associated with actually creating STL-compatible containers (with the associated iterators). This seems to be an active project, with work ongoing through this year. There is also some source code posted, although I was not able to find any licensing details. I hope everyone has an enjoyable holiday season! -Hal

2 1

Re: [boost] Interest in a list comprehension library?
by Brent Spillner 24 Dec '10

24 Dec '10

On 21/12/2010 09:09, Mathias Gaunard wrote: >Can you explain the difference with the Boost.Range adaptors? I think these are the most important ones: * Lazy evaluation of every comprehension. In contrast, boost::filter_iterator applies the filter predicate to the entire wrapped range at construction time (via satisfy_predicate().) * As a consequence, there are several ways to limit the amount of computation based on the amount of output required rather than the length of the input ranges. * Predictable backtracking behavior that allows filter criteria to depend on each other. This enables a number of computations (e.g. looping over the elements within a range of ranges) that are otherwise difficult or impossible to express, and even in straightforward cases permits some efficiency improvements. For instance, your example Pythagorean triple comprehension using Boost.Range evaluates a number of combinations of the three indices equal to the n'th cubic number, while the 'i <<= range(1,n), j <<= range(i,n), k <<=range(j,n)' version evaluates the n'th tetrahedral number's worth of combinations. The ratio of these quantities approaches 6 as n increases, and is in fact greater that 5 by n=16. A factor of 5 speedup is surely worth something. * Somewhat more concise and I believe more readable syntax. My goal was to require fewer characters than a Python comprehension and ideally not many more than Haskell, and I think I'm there in the simple cases. (Neglecting the variable declarations, naturally.) >It is true Boost.Range is quite lacking in terms of range generators, and maybe your solution is what we need. Don't get me wrong; I think Boost.Range is great, and the iterator adapters are a fantastic way to improve the iterator-based algorithms that tend to be somewhat clumsily expressed in a lot of traditional C++ code. I just don't think they're a fully satisfying substitute for the comprehension syntax (and backtracking, etc.) provided or easily defined in most functional languages. >It would be nice however, if it didn't reinvent the wheel and can be based on Phoenix for the functional part. I definitely don't want to reinvent the wheel, and I was a little hesitant to publish this in case it largely duplicated work that someone else had done in Range or Phoenix or somewhere else. I've never used Phoenix; it seems fascinating but I'm a little wary of making it a dependency just to get something simple like a comprehension syntax. I also took a look at using Boost.Proto to provide the expression trees, but it seemed that the syntax was a little more verbose than it needs to be for things that will be evaluated only in the context of a comprehension expression. Either one of those libraries could likely replace most of the boilerplate in my expressions.hpp and operators.hpp; on the other hand, being boilerplate, it wasn't that hard to write or to get it to work exactly as I needed. At this point I'm leaning more toward providing adaptors to permit Proto or Phoenix expressions within a comprehension, rather than absolutely requiring the use of either.

3 3

Re: [boost] [Boost-users] [units] Automatic Physical Units in Mathematica and Boost.Units
by Matthias Schabel 24 Dec '10

24 Dec '10

Alfredo, As one-half of the Boost.Units developer's community (actually I should also give due credit to Torsten Mähne for contributing the lambda component), I'll try to answer your questions : > Does any body have experience with using boost.units quantity with a > underlying type that are not double, e.g. multiple precision, or > vector (geometric) objects? Does it work well? For "well-behaved" types, Boost.Units should work transparently. See the examples for complex and measurement types. I believe there are some users who have applied Boost.Units to vectors in varying coordinate systems as well. > Are there future planned developments for Boost.Units, in terms of > external features (e.g. automatic conversion, better interaction with > boost.phoenix) or internal implementation? Automatic conversion is a much-requested and highly contentious issue that we intentionally did not support in the library, making the decision after much careful consideration. It is difficult to do it correctly - in the situation where you have, e.g., mixed meters and feet : 1.5*meters + 3.7*feet either there must be a specified default set of units to which everything is converted or an arbitrary decision must be made by the compiler. While it probably doesn't matter too much in this case, and for MP numeric types it shouldn't matter at all (excepting execution time), there are possible unit combinations where truncation/ round-off could become a problem. There is no obvious way to determine this at compile-time. Why not just explicitly specify your default units of choice in your code - this is self-documenting and should be consistent and correct. Do you have a use case where the requirement of explicit unit specification is excessively problematic? As far as Boost.Phoenix, what are the concerns? While I can't speak for Steven, I personally do not have a tremendous amount of time or resources to devote to Boost.Units on an ongoing basis; my bread-and-butter work is in medical imaging and, therefore, Boost.Units is a somewhat tangential project. That being said, one of the beauties of the open source model is that other interested parties (you, perhaps) are welcome to extend the work. Going from code that works for your particular application to code that is Boost-ready is non-trivial, but there are quite a number of people who can help provide advice. Boost.Units.Phoenix would be, I'm sure, a great addition to the library. As far as internal implementation, what are the concerns? Best, Matthias

1 0

[move] Review result pending since May !!!
by Vicente Botet 23 Dec '10

23 Dec '10

Hi, The Boost.Move library is a important library that will allow to adapt a lot of libraries to a common Move semantics. The review result is pending since May 2010. I want to request the review manager Overmind1 to give the result of the review as soon as possible. If you think that you can not do it in a short time, I think that we will need a volunteer to make the result report (of course if there is one) Best, Vicente -- View this message in context: http://boost.2283326.n4.nabble.com/move-Review-result-pending-since-May-tp3… Sent from the Boost - Dev mailing list archive at Nabble.com.

2 1