February 2016 - Boost-users - lists.preview.boost.org

[interprocess] Determine size of managed_shared_memory
by Kai Benndorf 12 Oct '19

12 Oct '19

Hi all, I want to create a managed_shared_memory in exactly the size I needed. Therefore I do something like this: size = sizeof( common_managed_shared_memory ); size += sizeof( MyClassInSharedMem ); managed_shared_memory segment(create_only, "name", size ); MyClassInSharedMem allocates itself some memory by segment->allocate(). I added this also to the size, but get a boost::interprocess::bad_alloc exception on allocating this additional memory. Are there some magic bytes I forgot to add? Many thanks in advance Kai

3 2

Weird compilation error when using boost::geometry
by 邓尧 16 Nov '17

16 Nov '17

Hi, I have implemented my own "point" as specified by the point concept http://www.boost.org/doc/libs/1_59_0/libs/geometry/doc/html/geometry/refere… When I use it along with boost::geometry::model::polygon/multi_polygon, GCC refuses to compile, tested on GCC 4.9/5.2. What's even more weird is that CLANG 3.6 would happy accept my code. BTW, the Point implementation is part of a large project, it difficult to replace it with boost::geometry::model::point. Here is my code: Point.hpp > #ifndef RAPTOR_POINT_HPP_INCLUDED_ > > #define RAPTOR_POINT_HPP_INCLUDED_ > > >> #include <boost/mpl/int.hpp> > > #include <boost/geometry/core/access.hpp> > > #include <boost/geometry/core/cs.hpp> > > #include <boost/geometry/core/coordinate_type.hpp> > > #include <boost/geometry/core/coordinate_system.hpp> > > #include <boost/geometry/core/coordinate_dimension.hpp> > > #include <boost/geometry/geometries/polygon.hpp> > > #include <boost/geometry/multi/geometries/multi_polygon.hpp> > > >> namespace raptor { > > >> template<typename T, int tDimension = 2> > > class Point { > > public: > > Point() = default; > > >> Point(T a, T b) { > > data[0] = a; > > data[1] = b; > > } > > >> Point(T a, T b, T c) { > > data[0] = a; > > data[1] = b; > > data[2] = c; > > } > > >> T& operator [] (long index) { > > return data[index]; > > } > > >> const T& operator [] (long index) const { > > return data[index]; > > } > > >> private: > > T data[tDimension]; > > }; > > >> using CubicPoint = Point<long, 3>; > > using PlanarPoint = Point<long>; > > using SphericalPoint = Point<double>; > > >> template<typename T> > > using Polygon = boost::geometry::model::polygon<T>; > > >> template<typename T> > > using PolySet = boost::geometry::model::multi_polygon<Polygon<T>>; > > >> } // namespace raptor > > >> namespace boost { namespace geometry { namespace traits { > > >> template<typename Type, std::size_t tDimension> > > struct tag<::raptor::Point<Type, tDimension>> { > > typedef point_tag type; > > }; > > >> template<typename Type, std::size_t tDimension> > > struct coordinate_type<::raptor::Point<Type, tDimension>> { > > typedef Type type; > > }; > > >> template<typename Type, std::size_t tDimension> > > struct coordinate_system<::raptor::Point<Type, tDimension>> { > > typedef boost::geometry::cs::cartesian type; > > }; > > >> template<typename Type, std::size_t tDimension> > > struct dimension<::raptor::Point<Type, tDimension>> > > : public boost::mpl::int_<tDimension> { > > // EMPTY > > }; > > >> template<typename Type, std::size_t tDimension, std::size_t tIndex> > > struct access<::raptor::Point<Type, tDimension>, tIndex> { > > static Type get(const ::raptor::Point<Type, tDimension>& p) { > > return p[tIndex]; > > } > > >> static void set(::raptor::Point<Type, tDimension>& p, > > const Type& value) { > > p[tIndex] = value; > > } > > }; > > >> }}} // namespace boost::geometry::traits > > >> #endif // RAPTOR_POINT_HPP_INCLUDED_ > > A real simple main.cpp: > #include "Point.hpp" > > >> int main() { > > raptor::Polygon<raptor::SphericalPoint> pl; > > raptor::PolySet<raptor::SphericalPoint> set; > > return sizeof(pl) + sizeof(set); > > } > > > GCC compilation error: g++ main.cpp -std=c++14 > In file included from /usr/include/boost/geometry/core/access.hpp:20:0, from Point.hpp:5, from main.cpp:1: /usr/include/boost/geometry/core/point_type.hpp: In instantiation of > 'struct boost::geometry::traits::point_type<raptor::Point<double> >': /usr/include/boost/geometry/core/point_type.hpp:66:17: required from > 'struct boost::geometry::core_dispatch::point_type<void, > raptor::Point<double> >' /usr/include/boost/geometry/core/coordinate_type.hpp:58:62: required from > 'struct boost::geometry::core_dispatch::coordinate_type<void, > raptor::Point<double> >' /usr/include/boost/geometry/core/coordinate_type.hpp:92:25: required from > 'struct boost::geometry::coordinate_type<raptor::Point<double> >' /usr/include/boost/geometry/geometries/concepts/point_concept.hpp:90:54: > required from 'class boost::geometry::concept::Point<raptor::Point<double> > >' /usr/include/boost/concept/detail/has_constraints.hpp:32:62: required by > substitution of 'template<class Model> boost::concepts::detail::yes > boost::concepts::detail::has_constraints_(Model*, > boost::concepts::detail::wrap_constraints<Model, (& Model:: constraints)>*) > [with Model = boost::geometry::concept::Point<raptor::Point<double> >]' /usr/include/boost/concept/detail/has_constraints.hpp:42:5: required from > 'const bool > boost::concepts::not_satisfied<boost::geometry::concept::Point<raptor::Point<double> > > >::value' /usr/include/boost/concept/detail/has_constraints.hpp:45:31: required > from 'struct > boost::concepts::not_satisfied<boost::geometry::concept::Point<raptor::Point<double> > > >' /usr/include/boost/mpl/if.hpp:67:11: required from 'struct > boost::mpl::if_<boost::concepts::not_satisfied<boost::geometry::concept::Point<raptor::Point<double> > > >, > boost::concepts::constraint<boost::geometry::concept::Point<raptor::Point<double> > > >, boost::concepts::requirement<boost::concepts::failed************ > boost::geometry::concept::Point<raptor::Point<double> >::************> >' /usr/include/boost/concept/detail/general.hpp:50:8: required from 'struct > boost::concepts::requirement_<void > (*)(boost::geometry::concept::Point<raptor::Point<double> >)>' /usr/include/boost/geometry/geometries/ring.hpp:60:5: required from > 'class boost::geometry::model::polygon<raptor::Point<double>, true, true, > std::vector, std::vector, std::allocator, std::allocator>' main.cpp:4:42: required from here /usr/include/boost/geometry/core/point_type.hpp:45:5: error: no matching > function for call to 'assertion_failed(mpl_::failed************ > (boost::geometry::traits::point_type<raptor::Point<double> > >::NOT_IMPLEMENTED_FOR_THIS_POINT_TYPE::************)(mpl_::assert_::types<raptor::Point<double>, > mpl_::na, mpl_::na, mpl_::na>))' BOOST_MPL_ASSERT_MSG ^ /usr/include/boost/mpl/assert.hpp:82:5: note: candidate: template<bool C> > int mpl_::assertion_failed(typename mpl_::assert<C>::type) int assertion_failed( typename assert<C>::type ); ^ /usr/include/boost/mpl/assert.hpp:82:5: note: template argument > deduction/substitution failed: /usr/include/boost/geometry/core/point_type.hpp:45:5: note: cannot > convert > 'boost::geometry::traits::point_type<Geometry>::NOT_IMPLEMENTED_FOR_THIS_POINT_TYPE48::assert_arg<raptor::Point<double> > >()' (type 'mpl_::failed************ > (boost::geometry::traits::point_type<raptor::Point<double> > >::NOT_IMPLEMENTED_FOR_THIS_POINT_TYPE::************)(mpl_::assert_::types<raptor::Point<double>, > mpl_::na, mpl_::na, mpl_::na>)') to type 'mpl_::assert<false>::type {aka > mpl_::assert<false>}' BOOST_MPL_ASSERT_MSG ^ In file included from > /usr/include/boost/geometry/core/coordinate_type.hpp:21:0, from /usr/include/boost/geometry/core/access.hpp:24, from Point.hpp:5, from main.cpp:1: /usr/include/boost/geometry/core/point_type.hpp: In instantiation of > 'struct boost::geometry::core_dispatch::point_type<void, > raptor::Point<double> >': /usr/include/boost/geometry/core/coordinate_type.hpp:58:62: required from > 'struct boost::geometry::core_dispatch::coordinate_type<void, > raptor::Point<double> >' /usr/include/boost/geometry/core/coordinate_type.hpp:92:25: required from > 'struct boost::geometry::coordinate_type<raptor::Point<double> >' /usr/include/boost/geometry/geometries/concepts/point_concept.hpp:90:54: > required from 'class boost::geometry::concept::Point<raptor::Point<double> > >' /usr/include/boost/concept/detail/has_constraints.hpp:32:62: required by > substitution of 'template<class Model> boost::concepts::detail::yes > boost::concepts::detail::has_constraints_(Model*, > boost::concepts::detail::wrap_constraints<Model, (& Model:: constraints)>*) > [with Model = boost::geometry::concept::Point<raptor::Point<double> >]' /usr/include/boost/concept/detail/has_constraints.hpp:42:5: required from > 'const bool > boost::concepts::not_satisfied<boost::geometry::concept::Point<raptor::Point<double> > > >::value' /usr/include/boost/concept/detail/has_constraints.hpp:45:31: required > from 'struct > boost::concepts::not_satisfied<boost::geometry::concept::Point<raptor::Point<double> > > >' /usr/include/boost/mpl/if.hpp:67:11: required from 'struct > boost::mpl::if_<boost::concepts::not_satisfied<boost::geometry::concept::Point<raptor::Point<double> > > >, > boost::concepts::constraint<boost::geometry::concept::Point<raptor::Point<double> > > >, boost::concepts::requirement<boost::concepts::failed************ > boost::geometry::concept::Point<raptor::Point<double> >::************> >' /usr/include/boost/concept/detail/general.hpp:50:8: required from 'struct > boost::concepts::requirement_<void > (*)(boost::geometry::concept::Point<raptor::Point<double> >)>' /usr/include/boost/geometry/geometries/ring.hpp:60:5: required from > 'class boost::geometry::model::polygon<raptor::Point<double>, true, true, > std::vector, std::vector, std::allocator, std::allocator>' main.cpp:4:42: required from here /usr/include/boost/geometry/core/point_type.hpp:66:17: error: no type named > 'type' in 'struct boost::geometry::traits::point_type<raptor::Point<double> > >' >::type type; ^ In file included from > /usr/include/boost/geometry/geometries/polygon.hpp:26:0, from Point.hpp:10, from main.cpp:1: /usr/include/boost/geometry/geometries/concepts/point_concept.hpp: In > instantiation of 'class > boost::geometry::concept::Point<raptor::Point<double> >': /usr/include/boost/concept/detail/has_constraints.hpp:32:62: required by > substitution of 'template<class Model> boost::concepts::detail::yes > boost::concepts::detail::has_constraints_(Model*, > boost::concepts::detail::wrap_constraints<Model, (& Model:: constraints)>*) > [with Model = boost::geometry::concept::Point<raptor::Point<double> >]' /usr/include/boost/concept/detail/has_constraints.hpp:42:5: required from > 'const bool > boost::concepts::not_satisfied<boost::geometry::concept::Point<raptor::Point<double> > > >::value' /usr/include/boost/concept/detail/has_constraints.hpp:45:31: required > from 'struct > boost::concepts::not_satisfied<boost::geometry::concept::Point<raptor::Point<double> > > >' /usr/include/boost/mpl/if.hpp:67:11: required from 'struct > boost::mpl::if_<boost::concepts::not_satisfied<boost::geometry::concept::Point<raptor::Point<double> > > >, > boost::concepts::constraint<boost::geometry::concept::Point<raptor::Point<double> > > >, boost::concepts::requirement<boost::concepts::failed************ > boost::geometry::concept::Point<raptor::Point<double> >::************> >' /usr/include/boost/concept/detail/general.hpp:50:8: required from 'struct > boost::concepts::requirement_<void > (*)(boost::geometry::concept::Point<raptor::Point<double> >)>' /usr/include/boost/geometry/geometries/ring.hpp:60:5: required from > 'class boost::geometry::model::polygon<raptor::Point<double>, true, true, > std::vector, std::vector, std::allocator, std::allocator>' main.cpp:4:42: required from here /usr/include/boost/geometry/geometries/concepts/point_concept.hpp:93:10: > error: 'value' is not a member of > 'boost::geometry::dimension<raptor::Point<double> >' enum { ccount = dimension<Geometry>::value }; ^ Where is the problem ? or it's a GCC bug ? Thanks

3 4

[Range, Phoenix] What am I missing...
by Robert Jones 25 Apr '17

25 Apr '17

Hi Folks Can anyone explain the output of this program... #include <iostream> #include <boost/range/algorithm/copy.hpp> #include <boost/range/counting_range.hpp> #include <boost/range/adaptor/reversed.hpp> #include <boost/range/adaptor/transformed.hpp> #include <boost/phoenix/bind/bind_function.hpp> #include <boost/phoenix/core/argument.hpp> int f( int i ) { return i * 2; } int main( ) { using boost::adaptors::reversed; using boost::adaptors::transformed; using boost::counting_range; using boost::copy; using boost::phoenix::arg_names::_1; copy( counting_range( 1, 5 ) | reversed | transformed( f ), std::ostream_iterator<int>( std::cout, " " ) ); std::cout << std::endl; copy( counting_range( 1, 5 ) | reversed | transformed( bind( f, _1 ) ), std::ostream_iterator<int>( std::cout, " " ) ); std::cout << std::endl; } Which is... 8 6 4 2 1768406272 1768406272 1768406272 1768406272 I'm using Gcc 4.6.2 & Boost 1.53 Thx All.

3 4

[statechart] Passing parameters from event to State Local Storage
by Christophe Bourez 16 Nov '16

16 Nov '16

I need to maintain a parameter into the state local storage. This parameter is initially contained in the event that causes the transition to the target state. I give hereafter a small illustrative example. typename sc = boost::statechart; class EvTest : public sc::event<EvTest> { public: EvTest(std::size_t val) : value(val) {} std::size_t getValue() const { return this->value; } private: std::size_t value; }; class MyStateMachine; class StSource; class StTarget; class StSource : public sc::simple_state<StSource, MyStateMachine> { public: typedef sc::custom_reaction<EvTest> reactions; sc::result react(const EvTest &event) { // How to pass event.getValue() to the target state ? transit<StTarget>(); } }; class StTarget : public sc::simple_state<StTarget, MyStateMachine> { public: StTarget(std::size_t val) : val(value) {} private: std::size_t value; }; Thanks, Christophe

5 6

[Fit] upcoming formal review for Boost.Fit
by Vicente J. Botet Escriba 05 Mar '16

05 Mar '16

Dear Boost community, The formal review of Paul Fultz II's Fit library starts on Wednesday, 2nd March and ends on 13th March. Fit is a header-only C++11/C++14 library that provides utilities for functions and function objects. Fit is: - Modern: Fit takes advantages of modern C++11/C++14 features. It support both `constexpr` initialization and `constexpr` evaluation of functions. It takes advantage of type deduction, variadic templates, and perfect forwarding to provide a simple and modern interface. - Relevant: Fit provides utilities for functions and does not try to implement a functional language in C++. As such, Fit solves many problems relevant to C++ programmers, including initialization of function objects and lambdas, overloading with ordering, improved return type deduction, and much more. - Lightweight: Fit builds simple lightweight abstraction on top of function objects. It does not require subscribing to an entire framework. Just use the parts you need. Fit is divided into three components: * Function Adaptors and Decorators: These enhance functions with additional capability. * Functions: These return functions that achieve a specific purpose. * Utilities: These are general utilities that are useful when defining or using functions Fit has been tested on gcc 4.6-4.9, clang 3.4-3.7, and Visual Studio 2015. For more information see: Github:https://github.com/pfultz2/Fit/tree/boost Documentation:http://pfultz2.github.io/Fit/doc/html/ Note that, as Fit is a functional library, the semantic of the functions is given in the form of `equations` instead of the classic effects, returns schema. This is because most of the functions have no side effects. E.g. the semantic of the function flip is defined as |assert(flip(f)(x, y, xs...) == f(y, x, xs...));| and the semantic of compose as |assert(compose(f, g)(xs...) == f(g(xs...)));| We await your feedback! Best regards, Vicente J. Botet Escriba P.S. Paul, now it is time to freeze the version that will be reviewed. I suggest you to create a branch on which you could fix the review issues.

6 11

boost::asio::read_until Segmentation Fault & Third Party Signal Handler
by Craig, Tom 01 Mar '16

01 Mar '16

My Linux application sis using bool::asio::read_until() to read data from a socket. The application also uses commercial, 3rd party hardware. Occasionally my program crashes due to a SIGSEGV violation. The core dump stack trace is shown below. It indicates that the 3rd party signal handler is invoked while my thread is waiting for socket I/O, and that the crash is occurring during signal handler execution. While I recognize that this is an issue with the 3rd party vendor (and I am currently engaged in discussions with them), I'm wondering if my usage of boost is incorrect, or if there is something that I should be doing differently in performing socket I/O? I am using boost v1.43. [cid:image001.png@01D17303.98B2DD10] E. Thomas Craig Principal Software Engineer SWIFT Division KLA-Tencor Corporation 408-875-7909 (work) 650-799-4787 (cell)

3 3

Re: [Boost-users] [boost] [Fit] upcoming formal review for Boost.Fit
by Paul Fultz II 29 Feb '16

29 Feb '16

On Sunday, February 28, 2016 at 5:28:39 PM UTC-6, Edward Diener wrote: > > On 2/28/2016 4:23 PM, paul Fultz wrote: > > > > > > > > > > On Sunday, February 28, 2016 12:23 PM, Edward Diener < > eldi...(a)tropicsoft.com <javascript:>> wrote: > > > > > >> > >> > >> On 2/27/2016 11:16 AM, Vicente J. Botet Escriba wrote: > >>> Dear Boost community, > >>> > >>> The formal review of Paul Fultz II's Fit library starts on Wednesday, > 2nd March and ends on 13th March. > >> > >> How do I generate the docs or run the tests for my local copy of Fit ? > > > >> > > > > You can build and run the tests by building the check target. For those > > unfamiliar with cmake, first configure the build directory with cmake: > > > > mkdir build > > cd build > > cmake .. > > cd .. > > > > Next build the check target using the native build system(such as make > or > > msbuild). CMake can call the native build system to build the target > 'check', > > like so: > > > > cmake --build build --config Release --target check > > > > Also, the library can be installed by invoking the 'install' target. > > Why is the CMakeLists.txt not in the 'test' subdirectory, since it > appears from your explanation that the file is used for the tests ? > Its used to install the library as well. > > > > > The documentation needs to be built using mkdocs. You can install mkdocs > and > > the boost theme with pip like this: > > > > pip install mkdocs mkdocs-boost > > > > Then to build the documentation, first `setup.py` must be run to extract > the > > documentation and examples from the source code, then `mkdocs` can be > invoked, > > like this: > > > > python setup.py > > mkdocs build -t boost > > > > And the documentation will be in the 'doc/html' directory. > > Please add these explanations to Fit as you are not using Boost build to > build the doc or run the tests. > I will add them. Also, I tried to add an initial Jamfile to build and run the tests as well. I just modified the Jamfile from other boost libraries. However, I haven't figured out how to run the tests yet using bjam to test my Jamfile. I get "error: Did not find Jamfile.jam or Jamroot.jam in any parent directory". I am not sure how I am supposed to run the tests. > > > _______________________________________________ > Unsubscribe & other changes: > http://lists.boost.org/mailman/listinfo.cgi/boost >

2 4

[gsoc16] Boost rejected as GSoC 2016 org
by Niall Douglas 29 Feb '16

29 Feb '16

Dear Boost, It is with a heavy heart I write to say that Boost was rejected as an org for Google Summer of Code 2016 by Google. We had our application submitted in time, it was reviewed by three members of the Boost leadership, our ideas list had six solid ideas with an especially solid seventh on the way, we were in very good standing with Google and there was no reason to expect rejection. We have asked for clarification as to why we were rejected, and we shall try to improve our application next year to improve our chances. We recognise that many students and mentors will be extremely disappointed by this news. We share in that disappointment, and all we can say is please try again next year. For those students and mentors who are continuing a previous GSoC on an existing Boost library, there may be a possibility that Boost may be able to fund those continuations this year. Each case will be approached by the steering committee on a case by case basis, and be aware that the standard required for funding by Boost is considerably above that of Google's with an accompanying high and detailed standard of funding application to the steering committee. Contact us privately if you want to know more. On other news we had been expecting to announce today that Bryce Adelstein Lelbach has generously agreed to take over as secondary GSoC admin from Boris Schäling who has served Boost GSoC for something like four years now, so he has definitely earned himself a rest! Our thanks to Boris for his service, and welcome Bryce to the team! Finally, I'd like to thank Jon Kalb who moved heaven and earth as he always does to get the GSoC application submitted in time. Yours, Niall Douglas -- ned Productions Limited Consulting http://www.nedproductions.biz/ http://ie.linkedin.com/in/nialldouglas/

1 0

C++Now Student/Volunteers Call for Applications
by Jon Kalb 29 Feb '16

29 Feb '16

The Call for Applications for Student/Volunteers for C++Now 2016 (AKA BoostCon X) has been released: http://cppnow.org/2016-conference/announcements/2016/02/23/student-volunteer -program-accepting-applications.html The application submission deadline is March 16th. We are looking for students with a strong interest in C++. The opportunity is open to student of any level or any field of study. Jon Kalb Chair, C++Now 2016

1 0

Re: [Boost-users] Boost.Context stack growing inwards
by Thomas Ziegenhagen 29 Feb '16

29 Feb '16

Hi again, just noticed that the make_fcontext() documentation says that it expects the stack pointer to be at the end or at the beginning, depending on the architecture. So please re-read my last mail as a feature request: If Boost.Context is a platform-independent context switching library, please make its stack pointer parameter also platform-independent. Rationale: Booost.Context knows best on which platform it runs. If the API is supposed to work the same on all supported systems, its parameter should do so, too. Other than that: Sorry for wasting your time. Bye, Thomas

3 2

Boost.Context stack growing inwards
by Thomas Ziegenhagen 29 Feb '16

29 Feb '16

Hi there, I get regular crashes when using Boost.Context after just a few calls to make_fcontext(). I built a minimal example as follows: ---- #include <iostream> #include <vector> #include <boost/context/all.hpp> struct Context { boost::context::fcontext_t c_outside, c_inside; }; Context gContext = { nullptr, nullptr }; void DoIt( intptr_t /*pt*/) { uint8_t test[64]; memset( test, 0xaf, sizeof( test)); std::cout << "DoIt(), Point 1" << std::endl; boost::context::jump_fcontext( &gContext.c_inside, gContext.c_outside, 0, true); std::cout << "DoIt(), Point 2" << std::endl; boost::context::jump_fcontext( &gContext.c_inside, gContext.c_outside, 0, true); std::cout << "DoIt(), Point 3" << std::endl; boost::context::jump_fcontext( &gContext.c_inside, gContext.c_outside, 0, true); } int main() { const size_t StackSize = 16384; std::vector<uint8_t> stack( StackSize, 0xf1); gContext.c_inside = boost::context::make_fcontext( stack.data() + 256, stack.size() - 512, DoIt); std::cout << "main(), Point 1" << std::endl; boost::context::jump_fcontext( &gContext.c_outside, gContext.c_inside, 0, true); std::cout << "main(), Point 2" << std::endl; boost::context::jump_fcontext( &gContext.c_outside, gContext.c_inside, 0, true); std::cout << "main(), Point 3" << std::endl; boost::context::jump_fcontext( &gContext.c_outside, gContext.c_inside, 0, true); std::cout << "main(), Point 4" << std::endl; return 0; } ------ This notable thing is that I provide a stack with additional 256 bytes of safety borders. And it turns out: the provided memory is overwritten way beyond the beginning. The actual designated area is not touched at all, but instead the area before the beginning is overwritten. The only thing I found in the documentation is this: "sp Member: Pointer to the beginning of the stack (depending of the architecture the stack grows downwards or upwards)." which hints that on some system the stack might grow to negative addresses. But up to now I thought that boost.context knows which direction is correct, and adjusts the given pointer accordingly. But apparently it doesn't. Or the environment underwent a drastic change. Here it is Windows 10 64bit, Visual Studio 2015. For readers remembering my last mails: I have verified this also with an "classic" boost build using this command line: b2.exe -a --reconfigure variant=debug,release link=static runtime-link=static --with-context So I'm pretty sure it's not a build issue. Question: is this a bug? Probably not, I'm surely not the first to use Boost.Context, so I wonder what the correct way is to handle this issue. So what do I do about this? Thanks in advance Bye, Thomas

1 0

Boost.Spirit Karma: how to store generator?
by Matwey V. Kornilov 28 Feb '16

28 Feb '16

Hello, After reading Karma tutorial, I still don't understand whether there a way to store generator except auto my_generator = ... I would like to generate text representation for many similar objects and I think that it is worth to use single generate object and pass it to generate_delimited() by const reference. Are there such things like qi::rule<> and qi::grammar for Karma?

2 1

[ sorting_view ] -do not sort arrays, sort iterators instead
by Boris Kats 27 Feb '16

27 Feb '16

The sorting procedure is one of the most usable routine in programming.And all sorting template functions have the same signature:template< class RandomIt, class Compare >void sort( RandomIt first, RandomIt last, Compare comp );with conditions: the type of dereferenced RandomIt must meet the requirements of MoveAssignable and MoveConstructible.It is clear that in the sorting process a lot of records are moving in the memory andwhen these records have a big size, these movements, together with calling constructors, can be very expensive.Solution.The proposed template function sorting_view is free of that problem - the sorting procedureis working (and moving) on tiny objects - iterators. As result of that procedure,the initial array of records is remaining intact; however provided std::vector<int> viewallows indirect access to the sorted array. On many occasions user does not need the sortedarray at all and he/she has a luxury to iterate through sorted and unsorted arrays simultaneously.In case of real needs of sorted array, it can be obtained via other template function apply_view with exactly 2*N movements of the records, where N is the size of initial array.For getting sorted view of arrays of user's defined records the appropriate Compare template function should be supplied.Happy sorting, Boris Kats.

1 0

Help: Errors compiling SESHAT project
by C. Ichongiri 26 Feb '16

26 Feb '16

Hey there, I've been at this for days now and can't seem to find anything to help with this: I got the project at https://github.com/falvaro/seshat and followed the instructions exactly as-is: - Got the *Boost* headers - Have got *g++ *compiler ( versions 5.2, 4.9, 4.7, 4.5, 4.3) and my default *clang++* *- Makefile *is present *P.S.* I'm on *OS X Mavericks*; Used *MacPorts* to install all above gcc versions *except *5.2, which was manually done following this tutorial: https://solarianprogrammer.com/2015/05/01/compiling-gcc-5-mac-os-x/#comment… However, when I attempt to compile it, I get the following errors (attached in the Textfile below). A screenshot image also attached shows the filesystem and path I am working with, from where the error file was created. Honestly, I'm at my wits end now, especially with my being new to C++. ANY helpful insight into this would be MOST APPRECIATED. Much thanks in advance, chiich.

1 0

Build Boost.Context with Visual Studio
by Thomas Ziegenhagen 26 Feb '16

26 Feb '16

Hi there, I'm building the required portions of Boost myself, along with all my other projects. It turned out that even the smallest compiler setting changes lead to strange crashes, some of which only occured on 5% of the client's systems, so I will not use externally built boost libraries anymore. So now I'm building the parts of boost which I require, which works fine so far. The trouble starts when I tried to use Boost.Context. It also contains ASM code, which I now need to build in Visual Studio 2015. VS2015 does not have builtin Asm support, for x64 it never had. So I'm invoking the Microsoft assembler as a custom build step. Command line is as follows: ml64 /Fo path/to/obj/file.obj /c path/to/source/jump_x86_64_ms_pe_masm.asm Documentation is as scarce as usual, but I figured from the filename that jump_x86_64_ms_pe_masm.asm is the correct file for Microsoft Visual Studio, x64. But assembling failed, and to add insult to injury, the error messages are lost somewhere in the output piping process. The complete output reads like this: ------ 1>------ Erstellen gestartet: Projekt: boost, Konfiguration: Debug x64 ------ 1> Microsoft (R) Macro Assembler (x64) Version 14.00.23506.0 1> Copyright (C) Microsoft Corporation. All rights reserved. 1> 1> Assembling: C:\Projekte\DeadPlanet\SourceExt\boost\context\asm\jump_x86_64_ms_pe_masm.asm 1> C:\Projekte\DeadPlanet\SourceExt\boost\context\asm\jump_x86_64_ms_pe_masm.asm(80)ied size 1>: error A2008 : syntax error : FRAME 1> C:\Projekte\DeadPlanet\SourceExt\boost\context\asm\jump_x86_64_ms_pe_masm.asm(81)ied size 1>CUSTOMBUILD : warning A4020: directive ignored outside a procedure 1> C:\Projekte\DeadPlanet\SourceExt\boost\context\asm\jump_x86_64_ms_pe_masm.asm(215 1>CUSTOMBUILD : fatal error A1010: unmatched block nesting : jump_fcontext ------ Please note that the actual error messages are overwritten by the filename - I can only guess at what buffer magic happens there, but I'm pretty sure it's not intended. But that's just a funny anecdote. My actual question is: how do I build Boost.Context in Visual Studio? Is there maybe some way to see the effective command line when building using Boost.Jam? Is this even the right ASM file for x86_64, Visual Studio? Thanks in advance! Bye, Thomas

4 5

Spherical Bessel function (nu, x as real) implementation
by campagne 26 Feb '16

26 Feb '16

Dear developpers, 1) Does you use this reference to compute Spherical Bessel Functions for real argument? Accurate recursive generation of spherical Bessel and Neumann functions for a large range of indices E. Gillman <http://scitation.aip.org/content/contributor/AU0510272>^1 and H. R. Fiebig <http://scitation.aip.org/search?value1=H.+R.+Fiebig&option1=author&option91…>Comput. Phys. 2, 62(1988); http://dx.doi.org/10.1063/1.168296 2) is there a way to speed up the computation of j_nu(x) if one wants 10 digits accuracy for instance? Best regards J.E

2 1

[ASIO] Resolver question
by Davies, John 25 Feb '16

25 Feb '16

I have some pretty simple UPD code. (It has to be simple, I'm new at ASIO) boost::asio::ip::udp::resolver::query query(boost::asio::ip::udp::v4(), addr, port); m_receiverEndpoint = *m_resolver.resolve(query); If my address is 192.168.1.112 everything works If my address is 192.168.001.112 it doesn't work and throws an exception about not finding the host. It's not a big deal, but it sure took me a long time to track down. Is there some sort of Boost magic I can do to convert the bad address into a good address? Thanks, John ________________________________ The information contained in this message may be confidential and legally protected under applicable law. The message is intended solely for the addressee(s). If you are not the intended recipient, you are hereby notified that any use, forwarding, dissemination, or reproduction of this message is strictly prohibited and may be unlawful. If you are not the intended recipient, please contact the sender by return e-mail and destroy all copies of the original message.

6 11

Boost Thread Compile Issue
by Len Za 25 Feb '16

25 Feb '16

When simply including into C++ project and attempting to compile causes the following compile error: Environment: - Visual Studio 2010 Pro (Project Configuration: DLL project) - boost v1.60.0 C:\src\SDK\Boost\boost_1_60_0\boost_1_60_0\boost/date_time/microsec_time_clock.hpp(99): error C2146: syntax error : missing ';' before identifier 'curr' C:\src\SDK\Boost\boost_1_60_0\boost_1_60_0\boost/date_time/microsec_time_clock.hpp(81) : while compiling class template member function 'boost::posix_time::ptime boost::date_time::microsec_clock<time_type>::create_time(boost::date_time::microsec_clock<time_type>::time_converter)' with [ time_type=boost::posix_time::ptime ] C:\src\SDK\Boost\boost_1_60_0\boost_1_60_0\boost/thread/thread_time.hpp(22) : see reference to class template instantiation 'boost::date_time::microsec_clock<time_type>' being compiled with [ time_type=boost::posix_time::ptime ] C:\src\SDK\Boost\boost_1_60_0\boost_1_60_0\boost/date_time/microsec_time_clock.hpp(99): error C2065: 'curr' : undeclared identifier C:\src\SDK\Boost\boost_1_60_0\boost_1_60_0\boost/date_time/microsec_time_clock.hpp(100): error C2065: 'curr_ptr' : undeclared identifier C:\src\SDK\Boost\boost_1_60_0\boost_1_60_0\boost/date_time/microsec_time_clock.hpp(100): error C2065: 'curr' : undeclared identifier C:\src\SDK\Boost\boost_1_60_0\boost_1_60_0\boost/date_time/microsec_time_clock.hpp(101): error C2065: 'curr_ptr' : undeclared identifier C:\src\SDK\Boost\boost_1_60_0\boost_1_60_0\boost/date_time/microsec_time_clock.hpp(101): error C2227: left of '->tm_year' must point to class/struct/union/generic type type is ''unknown-type'' C:\src\SDK\Boost\boost_1_60_0\boost_1_60_0\boost/date_time/microsec_time_clock.hpp(102): error C2065: 'curr_ptr' : undeclared identifier C:\src\SDK\Boost\boost_1_60_0\boost_1_60_0\boost/date_time/microsec_time_clock.hpp(102): error C2227: left of '->tm_mon' must point to class/struct/union/generic type type is ''unknown-type'' C:\src\SDK\Boost\boost_1_60_0\boost_1_60_0\boost/date_time/microsec_time_clock.hpp(103): error C2065: 'curr_ptr' : undeclared identifier C:\src\SDK\Boost\boost_1_60_0\boost_1_60_0\boost/date_time/microsec_time_clock.hpp(103): error C2227: left of '->tm_mday' must point to class/struct/union/generic type type is ''unknown-type'' C:\src\SDK\Boost\boost_1_60_0\boost_1_60_0\boost/date_time/microsec_time_clock.hpp(111): error C2065: 'curr_ptr' : undeclared identifier C:\src\SDK\Boost\boost_1_60_0\boost_1_60_0\boost/date_time/microsec_time_clock.hpp(111): error C2227: left of '->tm_hour' must point to class/struct/union/generic type type is ''unknown-type'' C:\src\SDK\Boost\boost_1_60_0\boost_1_60_0\boost/date_time/microsec_time_clock.hpp(112): error C2065: 'curr_ptr' : undeclared identifier C:\src\SDK\Boost\boost_1_60_0\boost_1_60_0\boost/date_time/microsec_time_clock.hpp(112): error C2227: left of '->tm_min' must point to class/struct/union/generic type type is ''unknown-type'' C:\src\SDK\Boost\boost_1_60_0\boost_1_60_0\boost/date_time/microsec_time_clock.hpp(113): error C2065: 'curr_ptr' : undeclared identifier C:\src\SDK\Boost\boost_1_60_0\boost_1_60_0\boost/date_time/microsec_time_clock.hpp(113): error C2227: left of '->tm_sec' must point to class/struct/union/generic type type is ''unknown-type''

1 0

(no subject)
by Виктория Доможакова 24 Feb '16

24 Feb '16

Hello. I have template class. I want to serialize it. But I don't know how. template <class T> class AverDayVisTask : public DrawTask, public AverDayVisMathTask <T> { public: // some functions private: friend class boost::serialization::access; //! boost::serialize template <class Archive> void serialize(Archive& ar, const unsigned int /*version*/) { ar & BOOST_SERIALIZATION_BASE_OBJECT_NVP(DrawTask); ar & BOOST_SERIALIZATION_BASE_OBJECT_NVP(AverDayVisMathTask<T>); //<----- error } }; // class AverDayVisTask BOOST_CLASS_VERSION(AverDayVisTask<SphericalModel>, 1); BOOST_CLASS_VERSION(AverDayVisTask<SphericalNutModel>, 1); BOOST_CLASS_VERSION(AverDayVisTask<WGS84Model>, 1); BOOST_CLASS_IMPLEMENTATION(AverDayVisTask<SphericalModel>, boost::serialization::object_class_info); BOOST_CLASS_IMPLEMENTATION(AverDayVisTask<SphericalNutModel>, boost::serialization::object_class_info); BOOST_CLASS_IMPLEMENTATION(AverDayVisTask<WGS84Model>, boost::serialization::object_class_info); How fix my problem? -- Виктория Доможакова

2 1

[graph] abort algorithm execution from a visitor
by Frank Tetzel 23 Feb '16

23 Feb '16

Hi all, i played around with the bfs example calculating distances to all vertices. Now i just want to calculate the distance between two vertices, so i want to stop when the target vertex is visited. If i understood the visitor concept correctly it's not really possible to change the behaviour of the algorithm from a visitor. Does anybody know of any workaround to do early exit? Do i have to implement a new algorithm for this? In a different thread on this list Paolo Bolzoni wrote that he aborts in a custom visitor by throwing an exception. Is this the only way? I'm using bfs here and not dijkstra because i have uniform edge weights. Btw, if someone could fix the documentation that would be really nice: http://www.boost.org/doc/libs/1_60_0/libs/graph/doc/bfs_visitor.html The code snippet there did not work for me. I had to wrap make_bfs_visitor() in visitor() like it is done in examples/bfs.cpp too. Regards, Frank

2 2

Boost 1.60 Raspberry Pi lockfree::queue compilation error
by Alexander Simpson 23 Feb '16

23 Feb '16

Hello, I’m trying to compile a project that makes use of boost::lockfree::queue on a Raspberry Pi 2 running Jessie. I built version 1.60 of Boost myself (apt-get was out of date) with sudo ./bjam install. I’m not cross-compiling. When I attempt to compile a project that uses the boost library I get the error listed below (where boostreader.cpp is the file written by me). I found a patch suggested two years ago here (https://svn.boost.org/trac/boost/ticket/9041 <https://svn.boost.org/trac/boost/ticket/9041>) but the changes in that patch seem to have already applied in 1.60, so I’m at a loss as to what to do. Assistance would be greatly appreciated. Alexander Simpson Error message: In function `boost::lockfree::detail::freelist_stack<boost::lockfree::queue<int, boost::parameter::void_, boost::parameter::void_, boost::parameter::void_>::node, std::allocator<boost::lockfree::queue<int, boost::parameter::void_, boost::parameter::void_, boost::parameter::void_>::node> >::~freelist_stack()': main.cpp:(.text._ZN5boost8lockfree6detail14freelist_stackINS0_5queueIiNS_9parameter5void_ES5_S5_E4nodeESaIS7_EED2Ev[_ZN5boost8lockfree6detail14freelist_stackINS0_5queueIiNS_9parameter5void_ES5_S5_E4nodeESaIS7_EED5Ev]+0x18): undefined reference to `boost::atomics::detail::lockpool::scoped_lock::scoped_lock(void const volatile*)' main.cpp:(.text._ZN5boost8lockfree6detail14freelist_stackINS0_5queueIiNS_9parameter5void_ES5_S5_E4nodeESaIS7_EED2Ev[_ZN5boost8lockfree6detail14freelist_stackINS0_5queueIiNS_9parameter5void_ES5_S5_E4nodeESaIS7_EED5Ev]+0x24): undefined reference to `boost::atomics::detail::lockpool::scoped_lock::~scoped_lock()' main.o: In function `boost::lockfree::queue<int, boost::parameter::void_, boost::parameter::void_, boost::parameter::void_>::queue(unsigned int)': main.cpp:(.text._ZN5boost8lockfree5queueIiNS_9parameter5void_ES3_S3_EC2Ej[_ZN5boost8lockfree5queueIiNS_9parameter5void_ES3_S3_EC5Ej]+0x6c): undefined reference to `boost::atomics::detail::lockpool::scoped_lock::scoped_lock(void const volatile*)' main.cpp:(.text._ZN5boost8lockfree5queueIiNS_9parameter5void_ES3_S3_EC2Ej[_ZN5boost8lockfree5queueIiNS_9parameter5void_ES3_S3_EC5Ej]+0x78): undefined reference to `boost::atomics::detail::lockpool::scoped_lock::~scoped_lock()' main.cpp:(.text._ZN5boost8lockfree5queueIiNS_9parameter5void_ES3_S3_EC2Ej[_ZN5boost8lockfree5queueIiNS_9parameter5void_ES3_S3_EC5Ej]+0xb0): undefined reference to `boost::atomics::detail::lockpool::scoped_lock::scoped_lock(void const volatile*)' main.cpp:(.text._ZN5boost8lockfree5queueIiNS_9parameter5void_ES3_S3_EC2Ej[_ZN5boost8lockfree5queueIiNS_9parameter5void_ES3_S3_EC5Ej]+0xbc): undefined reference to `boost::atomics::detail::lockpool::scoped_lock::~scoped_lock()' main.cpp:(.text._ZN5boost8lockfree5queueIiNS_9parameter5void_ES3_S3_EC2Ej[_ZN5boost8lockfree5queueIiNS_9parameter5void_ES3_S3_EC5Ej]+0xd8): undefined reference to `boost::atomics::detail::lockpool::scoped_lock::scoped_lock(void const volatile*)' main.cpp:(.text._ZN5boost8lockfree5queueIiNS_9parameter5void_ES3_S3_EC2Ej[_ZN5boost8lockfree5queueIiNS_9parameter5void_ES3_S3_EC5Ej]+0xe4): undefined reference to `boost::atomics::detail::lockpool::scoped_lock::~scoped_lock()' main.cpp:(.text._ZN5boost8lockfree5queueIiNS_9parameter5void_ES3_S3_EC2Ej[_ZN5boost8lockfree5queueIiNS_9parameter5void_ES3_S3_EC5Ej]+0x148): undefined reference to `boost::atomics::detail::lockpool::scoped_lock::scoped_lock(void const volatile*)' main.cpp:(.text._ZN5boost8lockfree5queueIiNS_9parameter5void_ES3_S3_EC2Ej[_ZN5boost8lockfree5queueIiNS_9parameter5void_ES3_S3_EC5Ej]+0x170): undefined reference to `boost::atomics::detail::lockpool::scoped_lock::~scoped_lock()' main.cpp:(.text._ZN5boost8lockfree5queueIiNS_9parameter5void_ES3_S3_EC2Ej[_ZN5boost8lockfree5queueIiNS_9parameter5void_ES3_S3_EC5Ej]+0x1ec): undefined reference to `boost::atomics::detail::lockpool::scoped_lock::scoped_lock(void const volatile*)' main.cpp:(.text._ZN5boost8lockfree5queueIiNS_9parameter5void_ES3_S3_EC2Ej[_ZN5boost8lockfree5queueIiNS_9parameter5void_ES3_S3_EC5Ej]+0x1f8): undefined reference to `boost::atomics::detail::lockpool::scoped_lock::~scoped_lock()' main.cpp:(.text._ZN5boost8lockfree5queueIiNS_9parameter5void_ES3_S3_EC2Ej[_ZN5boost8lockfree5queueIiNS_9parameter5void_ES3_S3_EC5Ej]+0x224): undefined reference to `boost::atomics::detail::lockpool::scoped_lock::scoped_lock(void const volatile*)' main.cpp:(.text._ZN5boost8lockfree5queueIiNS_9parameter5void_ES3_S3_EC2Ej[_ZN5boost8lockfree5queueIiNS_9parameter5void_ES3_S3_EC5Ej]+0x230): undefined reference to `boost::atomics::detail::lockpool::scoped_lock::~scoped_lock()' main.o: In function `boost::lockfree::queue<int, boost::parameter::void_, boost::parameter::void_, boost::parameter::void_>::~queue()': main.cpp:(.text._ZN5boost8lockfree5queueIiNS_9parameter5void_ES3_S3_ED2Ev[_ZN5boost8lockfree5queueIiNS_9parameter5void_ES3_S3_ED5Ev]+0x58): undefined reference to `boost::atomics::detail::lockpool::scoped_lock::scoped_lock(void const volatile*)' main.cpp:(.text._ZN5boost8lockfree5queueIiNS_9parameter5void_ES3_S3_ED2Ev[_ZN5boost8lockfree5queueIiNS_9parameter5void_ES3_S3_ED5Ev]+0x64): undefined reference to `boost::atomics::detail::lockpool::scoped_lock::~scoped_lock()' main.cpp:(.text._ZN5boost8lockfree5queueIiNS_9parameter5void_ES3_S3_ED2Ev[_ZN5boost8lockfree5queueIiNS_9parameter5void_ES3_S3_ED5Ev]+0x90): undefined reference to `boost::atomics::detail::lockpool::scoped_lock::scoped_lock(void const volatile*)' main.cpp:(.text._ZN5boost8lockfree5queueIiNS_9parameter5void_ES3_S3_ED2Ev[_ZN5boost8lockfree5queueIiNS_9parameter5void_ES3_S3_ED5Ev]+0x9c): undefined reference to `boost::atomics::detail::lockpool::scoped_lock::~scoped_lock()' main.cpp:(.text._ZN5boost8lockfree5queueIiNS_9parameter5void_ES3_S3_ED2Ev[_ZN5boost8lockfree5queueIiNS_9parameter5void_ES3_S3_ED5Ev]+0xc8): undefined reference to `boost::atomics::detail::lockpool::scoped_lock::scoped_lock(void const volatile*)' main.cpp:(.text._ZN5boost8lockfree5queueIiNS_9parameter5void_ES3_S3_ED2Ev[_ZN5boost8lockfree5queueIiNS_9parameter5void_ES3_S3_ED5Ev]+0xd4): undefined reference to `boost::atomics::detail::lockpool::scoped_lock::~scoped_lock()' main.cpp:(.text._ZN5boost8lockfree5queueIiNS_9parameter5void_ES3_S3_ED2Ev[_ZN5boost8lockfree5queueIiNS_9parameter5void_ES3_S3_ED5Ev]+0x128): undefined reference to `boost::atomics::detail::lockpool::scoped_lock::scoped_lock(void const volatile*)' main.cpp:(.text._ZN5boost8lockfree5queueIiNS_9parameter5void_ES3_S3_ED2Ev[_ZN5boost8lockfree5queueIiNS_9parameter5void_ES3_S3_ED5Ev]+0x134): undefined reference to `boost::atomics::detail::lockpool::scoped_lock::~scoped_lock()' main.cpp:(.text._ZN5boost8lockfree5queueIiNS_9parameter5void_ES3_S3_ED2Ev[_ZN5boost8lockfree5queueIiNS_9parameter5void_ES3_S3_ED5Ev]+0x164): undefined reference to `boost::atomics::detail::lockpool::scoped_lock::scoped_lock(void const volatile*)' main.cpp:(.text._ZN5boost8lockfree5queueIiNS_9parameter5void_ES3_S3_ED2Ev[_ZN5boost8lockfree5queueIiNS_9parameter5void_ES3_S3_ED5Ev]+0x170): undefined reference to `boost::atomics::detail::lockpool::scoped_lock::~scoped_lock()' main.cpp:(.text._ZN5boost8lockfree5queueIiNS_9parameter5void_ES3_S3_ED2Ev[_ZN5boost8lockfree5queueIiNS_9parameter5void_ES3_S3_ED5Ev]+0x180): undefined reference to `boost::atomics::detail::lockpool::scoped_lock::scoped_lock(void const volatile*)' main.cpp:(.text._ZN5boost8lockfree5queueIiNS_9parameter5void_ES3_S3_ED2Ev[_ZN5boost8lockfree5queueIiNS_9parameter5void_ES3_S3_ED5Ev]+0x18c): undefined reference to `boost::atomics::detail::lockpool::scoped_lock::~scoped_lock()' main.cpp:(.text._ZN5boost8lockfree5queueIiNS_9parameter5void_ES3_S3_ED2Ev[_ZN5boost8lockfree5queueIiNS_9parameter5void_ES3_S3_ED5Ev]+0x1c8): undefined reference to `boost::atomics::detail::lockpool::scoped_lock::scoped_lock(void const volatile*)' main.cpp:(.text._ZN5boost8lockfree5queueIiNS_9parameter5void_ES3_S3_ED2Ev[_ZN5boost8lockfree5queueIiNS_9parameter5void_ES3_S3_ED5Ev]+0x1d4): undefined reference to `boost::atomics::detail::lockpool::scoped_lock::~scoped_lock()' main.cpp:(.text._ZN5boost8lockfree5queueIiNS_9parameter5void_ES3_S3_ED2Ev[_ZN5boost8lockfree5queueIiNS_9parameter5void_ES3_S3_ED5Ev]+0x1e8): undefined reference to `boost::atomics::detail::lockpool::scoped_lock::scoped_lock(void const volatile*)' main.cpp:(.text._ZN5boost8lockfree5queueIiNS_9parameter5void_ES3_S3_ED2Ev[_ZN5boost8lockfree5queueIiNS_9parameter5void_ES3_S3_ED5Ev]+0x1f4): undefined reference to `boost::atomics::detail::lockpool::scoped_lock::~scoped_lock()' main.cpp:(.text._ZN5boost8lockfree5queueIiNS_9parameter5void_ES3_S3_ED2Ev[_ZN5boost8lockfree5queueIiNS_9parameter5void_ES3_S3_ED5Ev]+0x218): undefined reference to `boost::atomics::detail::lockpool::scoped_lock::scoped_lock(void const volatile*)' main.cpp:(.text._ZN5boost8lockfree5queueIiNS_9parameter5void_ES3_S3_ED2Ev[_ZN5boost8lockfree5queueIiNS_9parameter5void_ES3_S3_ED5Ev]+0x224): undefined reference to `boost::atomics::detail::lockpool::scoped_lock::~scoped_lock()' main.cpp:(.text._ZN5boost8lockfree5queueIiNS_9parameter5void_ES3_S3_ED2Ev[_ZN5boost8lockfree5queueIiNS_9parameter5void_ES3_S3_ED5Ev]+0x260): undefined reference to `boost::atomics::detail::lockpool::scoped_lock::scoped_lock(void const volatile*)' main.cpp:(.text._ZN5boost8lockfree5queueIiNS_9parameter5void_ES3_S3_ED2Ev[_ZN5boost8lockfree5queueIiNS_9parameter5void_ES3_S3_ED5Ev]+0x26c): undefined reference to `boost::atomics::detail::lockpool::scoped_lock::~scoped_lock()' main.cpp:(.text._ZN5boost8lockfree5queueIiNS_9parameter5void_ES3_S3_ED2Ev[_ZN5boost8lockfree5queueIiNS_9parameter5void_ES3_S3_ED5Ev]+0x278): undefined reference to `boost::atomics::detail::lockpool::scoped_lock::scoped_lock(void const volatile*)' main.cpp:(.text._ZN5boost8lockfree5queueIiNS_9parameter5void_ES3_S3_ED2Ev[_ZN5boost8lockfree5queueIiNS_9parameter5void_ES3_S3_ED5Ev]+0x284): undefined reference to `boost::atomics::detail::lockpool::scoped_lock::~scoped_lock()' boostreader.o: In function `BoostReader::run()': boostreader.cpp:(.text+0x84): undefined reference to `boost::atomics::detail::lockpool::scoped_lock::scoped_lock(void const volatile*)' boostreader.cpp:(.text+0x90): undefined reference to `boost::atomics::detail::lockpool::scoped_lock::~scoped_lock()' boostreader.cpp:(.text+0xb8): undefined reference to `boost::atomics::detail::lockpool::scoped_lock::scoped_lock(void const volatile*)' boostreader.cpp:(.text+0xc4): undefined reference to `boost::atomics::detail::lockpool::scoped_lock::~scoped_lock()' boostreader.cpp:(.text+0xf0): undefined reference to `boost::atomics::detail::lockpool::scoped_lock::scoped_lock(void const volatile*)' boostreader.cpp:(.text+0xfc): undefined reference to `boost::atomics::detail::lockpool::scoped_lock::~scoped_lock()' boostreader.cpp:(.text+0x11c): undefined reference to `boost::atomics::detail::lockpool::scoped_lock::scoped_lock(void const volatile*)' boostreader.cpp:(.text+0x128): undefined reference to `boost::atomics::detail::lockpool::scoped_lock::~scoped_lock()' boostreader.cpp:(.text+0x1ac): undefined reference to `boost::atomics::detail::lockpool::scoped_lock::scoped_lock(void const volatile*)' boostreader.cpp:(.text+0x1dc): undefined reference to `boost::atomics::detail::lockpool::scoped_lock::~scoped_lock()' boostreader.cpp:(.text+0x204): undefined reference to `boost::atomics::detail::lockpool::scoped_lock::scoped_lock(void const volatile*)' boostreader.cpp:(.text+0x210): undefined reference to `boost::atomics::detail::lockpool::scoped_lock::~scoped_lock()' boostreader.cpp:(.text+0x264): undefined reference to `boost::atomics::detail::lockpool::scoped_lock::scoped_lock(void const volatile*)' boostreader.cpp:(.text+0x288): undefined reference to `boost::atomics::detail::lockpool::scoped_lock::~scoped_lock()' boostreader.cpp:(.text+0x438): undefined reference to `boost::atomics::detail::lockpool::scoped_lock::scoped_lock(void const volatile*)' boostreader.cpp:(.text+0x454): undefined reference to `boost::atomics::detail::lockpool::scoped_lock::~scoped_lock()'

2 1

boost 1.54: problem with building documentation.
by Paul K 22 Feb '16

22 Feb '16

Hallo people. I need to have documentation in man pages format on my ubuntu 14.04. Unfortunatelly, I fail with this task. The following are the steps I've performed. In step 11 I do "../b2" instead "../b2 man" just to highlight that the problem is not related to building the man pages. Of course "../b2 man" fails as well Could You please help me with it? 1. install following packages for man pages build. lubuntu.14.04$ sudo apt-get install xsltproc lubuntu.14.04$ sudo apt-get install doxygen 2. lubuntu.14.04$ dpkg --list | grep libboost-all ii libboost-all-dev 1.54.0.1ubuntu1 i386 Boost C++ Libraries development files (ALL) (default version) 3. download boost_1_54_0.tar.bz2, unpack to ~/ 4. cd ~/boost_1_54_0 5. ./bootstrap prepares build configuration and puts it to project-config.jam. 6. ./b2 builds whole the boost libraries, but does not install them into the system. 7. lubuntu.14.04$ export BOOST_ROOT=/home/userp/boost_1_54_0 8. lubuntu.14.04$ cd ~/boost.doc/ 9. lubuntu.14.04$ ~/boost_1_54_0/tools/boostbook/setup_boostbook.sh Downloading DocBook XSLT Stylesheets version 1.75.2... Expanding DocBook XSLT Stylesheets into /home/userp/boost.doc/docbook-xsl-1.75.2...done. Downloading DocBook XML DTD version 4.2... Expanding DocBook XML DTD into /home/userp/boost.doc/docbook-dtd-4.2... done. Searching for xsltproc... /usr/bin/xsltproc. Searching for Doxygen... /usr/bin/doxygen. Searching for Java... /usr/bin/java. Downloading FOP distribution version 0.94... Expanding FOP distribution into /home/userp/boost.doc/fop-0.94... done. Updating Boost.Jam configuration in /home/userp/user-config.jam... done. Done! Execute "bjam --v2" in a documentation directory to generate documentation with BoostBook. If you have not already, you will need to compile Boost.Jam. 10. lubuntu.14.04$ cd ~/boost_1_54_0/doc 11. lubuntu.14.04$ ../b2 Performing configuration checks - has_icu builds : yes (cached) /home/userp/boost_1_54_0/tools/build/v2/build/virtual-target.jam:1099: in virtual-target.register-actual-name from module virtual-target error: Duplicate name of actual target: <p../bin.v2/libs/filesystem/build/gcc-4.9.3/release/link-static>libboost_filesystem.a error: previous virtual target { gcc%gcc.archive-libboost_filesystem.a.STATIC_LIB { gcc%gcc.compile.c++-codecvt_error_category.o.OBJ { codecvt_error_category.cpp.CPP } } { gcc%gcc.compile.c++-operations.o.OBJ { operations.cpp.CPP } } { gcc%gcc.compile.c++-path.o.OBJ { path.cpp.CPP } } { gcc%gcc.compile.c++-path_traits.o.OBJ { path_traits.cpp.CPP } } { gcc%gcc.compile.c++-portability.o.OBJ { portability.cpp.CPP } } { gcc%gcc.compile.c++-unique_path.o.OBJ { unique_path.cpp.CPP } } { gcc%gcc.compile.c++-utf8_codecvt_facet.o.OBJ { utf8_codecvt_facet.cpp.CPP } } { gcc%gcc.compile.c++-windows_file_codecvt.o.OBJ { windows_file_codecvt.cpp.CPP } } } error: created from ../libs/filesystem/build/boost_filesystem error: another virtual target { gcc%gcc.archive-libboost_filesystem.a.STATIC_LIB { gcc%gcc.compile.c++-codecvt_error_category.o.OBJ { codecvt_error_category.cpp.CPP } } { gcc%gcc.compile.c++-operations.o.OBJ { operations.cpp.CPP } } { gcc%gcc.compile.c++-path.o.OBJ { path.cpp.CPP } } { gcc%gcc.compile.c++-path_traits.o.OBJ { path_traits.cpp.CPP } } { gcc%gcc.compile.c++-portability.o.OBJ { portability.cpp.CPP } } { gcc%gcc.compile.c++-unique_path.o.OBJ { unique_path.cpp.CPP } } { gcc%gcc.compile.c++-utf8_codecvt_facet.o.OBJ { utf8_codecvt_facet.cpp.CPP } } { gcc%gcc.compile.c++-windows_file_codecvt.o.OBJ { windows_file_codecvt.cpp.CPP } } } error: created from ../libs/filesystem/build/boost_filesystem error: added properties: <auto-index-internal>off <auto-index-no-duplicates>off <auto-index-section-names>on <auto-index-verbose>off <auto-index>off <format>docbook error: removed properties: <format>html /home/userp/boost_1_54_0/tools/build/v2/build/virtual-target.jam:484: in actualize-no-scanner from module object(file-target)@3468 /home/userp/boost_1_54_0/tools/build/v2/build/virtual-target.jam:134: in class(a)virtual-target.actualize from module object(file-target)@3468 /home/userp/boost_1_54_0/tools/build/v2/build/virtual-target.jam:815: in actualize-source-type from module object(action)@3786 /home/userp/boost_1_54_0/tools/build/v2/build/virtual-target.jam:836: in actualize-sources from module object(action)@3786 /home/userp/boost_1_54_0/tools/build/v2/build/virtual-target.jam:776: in class(a)action.actualize from module object(action)@3786 /home/userp/boost_1_54_0/tools/build/v2/build/virtual-target.jam:311: in actualize-action from module object(file-target)@3787 /home/userp/boost_1_54_0/tools/build/v2/build/virtual-target.jam:493: in actualize-no-scanner from module object(file-target)@3787 /home/userp/boost_1_54_0/tools/build/v2/build/virtual-target.jam:134: in class(a)virtual-target.actualize from module object(file-target)@3787 /home/userp/boost_1_54_0/tools/build/v2/build/virtual-target.jam:815: in actualize-source-type from module object(action)@3793 /home/userp/boost_1_54_0/tools/build/v2/build/virtual-target.jam:834: in actualize-sources from module object(action)@3793 /home/userp/boost_1_54_0/tools/build/v2/build/virtual-target.jam:776: in class(a)action.actualize from module object(action)@3793 /home/userp/boost_1_54_0/tools/build/v2/build/virtual-target.jam:311: in actualize-action from module object(file-target)@3794 /home/userp/boost_1_54_0/tools/build/v2/build/virtual-target.jam:493: in actualize-no-scanner from module object(file-target)@3794 /home/userp/boost_1_54_0/tools/build/v2/build/virtual-target.jam:134: in class(a)virtual-target.actualize from module object(file-target)@3794 /home/userp/boost_1_54_0/tools/build/v2/build/virtual-target.jam:815: in actualize-source-type from module object(action)@7122 /home/userp/boost_1_54_0/tools/build/v2/build/virtual-target.jam:834: in actualize-sources from module object(action)@7122 /home/userp/boost_1_54_0/tools/build/v2/build/virtual-target.jam:776: in class(a)action.actualize from module object(action)@7122 /home/userp/boost_1_54_0/tools/build/v2/build/virtual-target.jam:311: in actualize-action from module object(file-target)@7123 /home/userp/boost_1_54_0/tools/build/v2/build/virtual-target.jam:493: in actualize-no-scanner from module object(file-target)@7123 /home/userp/boost_1_54_0/tools/build/v2/build/virtual-target.jam:134: in class(a)virtual-target.actualize from module object(file-target)@7123 /home/userp/boost_1_54_0/tools/build/v2/build-system.jam:720: in load from module build-system /home/userp/boost_1_54_0/tools/build/v2/kernel/modules.jam:289: in import from module modules /home/userp/boost_1_54_0/tools/build/v2/kernel/bootstrap.jam:139: in boost-build from module /home/userp/boost_1_54_0/boost-build.jam:17: in module scope from module regards

1 0

boost::any constructors
by David 22 Feb '16

22 Feb '16

Hi, boost::any has a perfect forward constructor declared as: template<typename ValueType> any(ValueType&& value , typename boost::disable_if<boost::is_same<any&, ValueType> >::type* = 0 // disable if value has type `any&` , typename boost::disable_if<boost::is_const<ValueType> >::type* = 0) // disable if value has type `const ValueType&&` : content(new holder< typename decay<ValueType>::type >(static_cast<ValueType&&>(value))) {} The is_const SFINAE exclusion forces const types to the regular copy constructor: template<typename ValueType> any(const ValueType & value) : content(new holder< BOOST_DEDUCED_TYPENAME remove_cv<BOOST_DEDUCED_TYPENAME decay<const ValueType>::type>::type >(value)) {} What is different about how the regular copy constructor treats a constant value than what the perfect forward construct would do if the is_const exclusion were removed? Thanks, David

2 1

Nested BOOST_FOREACH crash
by peyman＠ausdia.com 22 Feb '16

22 Feb '16

Good Day Boosters! I am experiencing sporadic crashes that look like memory problem when I have nested (2 level) BOOST_FOREACH loops. Reason I say it looks like memory problem is because slightest change will make it crash or not crash. For example, adding a simple cout would change it! I cannot provide a testcase. So I am just wondering if anybody has experienced the same, or know what could be going on. I am using Boost 1.57. Cheers, Peyman

2 1

Need help when adapting boost 1.59.0 to WinRT
by Nguyễn Trung Duy 22 Feb '16

22 Feb '16

Dear Boost team, I need your help with adapting boost 1.59 to WinRT. I am working on boost and reSIProcate. I built boost and integrated it with reSIProcate project. However, when build reflow project, I got stuck with bellow bugs. I wonder with your great experiences, could you please give me some advice. The error happens at line 96 : #if defined(BOOST_ASIO_WINDOWS_RUNTIME) const int max_addr_v4_str_len = 256; const int max_addr_v6_str_len = 256; typedef unsigned __int32 u_long_type; typedef unsigned __int16 u_short_type; struct in4_addr_type { u_long_type s_addr; }; // error at here And the logs: *\boost-msvc-14.0-store\boost/asio/detail/socket_types.hpp(96): error C3927: '->': trailing return type is not allowed after a non-function declarator (compiling source file MediaStream.cxx)\boost-msvc-14.0-store\boost/asio/detail/socket_types.hpp(96): error C3484: syntax error: expected '->' before the return type (compiling source file MediaStream.cxx)\boost-msvc-14.0-store\boost/asio/detail/socket_types.hpp(96): error C3613: missing return type after '->' ('int' assumed) (compiling source file MediaStream.cxx)\boost-msvc-14.0-store\boost/asio/detail/socket_types.hpp(96): error C3646: 'S_addr': unknown override specifier (compiling source file MediaStream.cxx)\boost-msvc-14.0-store\boost/asio/detail/socket_types.hpp(98): error C3927: '->': trailing return type is not allowed after a non-function declarator (compiling source file MediaStream.cxx)\boost-msvc-14.0-store\boost/asio/detail/socket_types.hpp(98): error C3484: syntax error: expected '->' before the return type (compiling source file MediaStream.cxx)\boost-msvc-14.0-store\boost/asio/detail/socket_types.hpp(98): error C3613: missing return type after '->' ('int' assumed) (compiling source file MediaStream.cxx)\boost-msvc-14.0-store\boost/asio/detail/socket_types.hpp(98): error C3646: 'Byte': unknown override specifier (compiling source file MediaStream.cxx)\boost-msvc-14.0-store\boost/asio/detail/socket_types.hpp(98): error C2143: syntax error: missing ',' before '[' (compiling source file MediaStream.cxx)\boost-msvc-14.0-store\boost/asio/detail/socket_types.hpp(98): error C4430: missing type specifier - int assumed. Note: C++ does not support default-int (compiling source file MediaStream.cxx)\boost-msvc-14.0-store\boost/asio/detail/socket_types.hpp(98): error C2143: syntax error: missing ')' before ';' (compiling source file MediaStream.cxx)\boost-msvc-14.0-store\boost/asio/detail/socket_types.hpp(98): error C2143: syntax error: missing ';' before ')' (compiling source file MediaStream.cxx)\boost-msvc-14.0-store\boost/asio/detail/socket_types.hpp(98): error C2059: syntax error: ')' (compiling source file MediaStream.cxx)\boost-msvc-14.0-store\boost/asio/ip/address_v4.hpp(61): error C2039: 'S_addr': is not a member of 'default::uint32' (compiling source file MediaStream.cxx)\boost-msvc-14.0-store\boost/asio/ip/address_v4.hpp(147): error C2039: 'S_addr': is not a member of 'default::uint32' (compiling source file MediaStream.cxx)\boost-msvc-14.0-store\boost/asio/ip/address_v4.hpp(153): error C2039: 'S_addr': is not a member of 'default::uint32' (compiling source file MediaStream.cxx)* Thanks you so much!!!! *--* *Best Regards,* *NGUYEN TRUNG DUY* *Android Developer* *Mobile*: (+84)977 46 12 23 *Skype :* trungduy150388 *Website*: http://nguyentrungduy.com/ *Blog*: http://dbox.nguyentrungduy.com/ *Github*: https://github.com/nguyentrungduy

2 2

Newbie
by Shan Wijesinghe 22 Feb '16

22 Feb '16

Hi all, I'm a new member to C++ boost and I have a fairly good knowledge in programming in C++. I'm very much excited to join this group and I need directions from the senior members on how to start myself. Please help me here. Thanks in advance. regards, DilSHAN.

6 11

Query on Boost.DLL
by Leo Carreon 21 Feb '16

21 Feb '16

Hi, I have been reading the Boost.DLL documentation. Can a single plugin support multiple API’s? If yes, when the multiple API’s are used at the same time; will there be only one instance of the plugin loaded or will there be multiple instances loaded? Regards, Leo

2 1

Boost.DLL
by Leo Carreon 21 Feb '16

21 Feb '16

Hi, Can anyone please let me know what the status of the Boost.DLL library is? Regards, Leo

2 1

[coroutine] - only std exceptions are caught from coroutines
by Tamas.Ruszkai＠leica-geosystems.com 21 Feb '16

21 Feb '16

3 4

[Interprocess] Communication between x86 and x64 issue
by Toni Neubert 19 Feb '16

19 Feb '16

I want to communicate between different platforms using boost interprocess. I am using vc12 and boost 1.58 on windows 7. My code below is a very simple example, that should work. But it doesn't for communications between different platforms... If I create it in x64 and open in win32, the process stuck at a lock at function try_based_lock in boost/int/sync/detail/common_algorithms.hpp In the other way around: win32 create, x64 open: the process crashes at name_length in segment_manager_helper.hpp while trying to find the name in index (priv_generic_find in segment_manager). #include <iostream> #include <boost/interprocess/managed_shared_memory.hpp> int main() { namespace bip = boost::interprocess; // open in WIN32, create in x64 #ifdef _WIN32 bip::managed_shared_memory msm(bip::open_only, "TestIPC"); #elsif X64 bip::shared_memory_object::remove("TestIPC"); bip::managed_shared_memory msm(bip::create_only, "TestIPC", 4096); msm.construct<uint32_t>("Data")[1](10); #endif // Get Data and print it auto data = msm.find<uint32_t>("Data"); if (data.second == 1) { std::cout << *data.first << std::endl; } std::cin.ignore(); return 0; } Does anybody have experience in this? Thank you in advance!

3 2

Re: [Boost-users] [Serialization] This compiles; but does it work?
by Bjorn Reese 19 Feb '16

19 Feb '16

On 02/19/2016 04:20 AM, Merrill Cornish wrote: > Can anyone tell me if this will work, or do I need to implement the > serialize() function? When you are doing different things for the input and output archives then it is better to split serialization into load and save: #include <boost/filesystem/path.hpp> #include <boost/serialization/split_free.hpp> namespace boost { namespace serialization { template <typename Archive> void serialize(Archive& ar, filesystem::path& p, const unsigned int version) { split_free(ar, p, version); } template<class Archive> void save(Archive & ar, const filesystem::path& p, unsigned int version) { ar << p.string(); } template<class Archive> void load(Archive & ar, filesystem::path& p, unsigned int version) { std::string data; ar >> data; p = data; } }}

2 1

[graph] Search algorithm using quality metric rather than distance
by rleigh＠codelibre.net 19 Feb '16

19 Feb '16

I have an adjacency_list graph (shown in attached dot file). Each edge has an attached "quality metric" as a bundled property. Similar to the dijkstra_shortest_paths algorithm, I'd like to determine the optimal path. However, this algorithm sums the distance along each edge, and finds the shortest path. What I'd like to do is *multiply* the quality metric for each edge in the path, and find the largest one. A perfect path will have a quality metric of 1.0, while suboptimal paths will have values tending towards zero, and the more "bad" edges the smaller the number. I'll likely then look at the number of edges and then select the shortest of the candidates. It seems like a simple algorithm that might already be included, but I just haven't found it yet not knowing its formal name. If anyone has any suggestions, I'd be very grateful. Many thanks, Roger

5 4

[Serialization] This compiles; but does it work?
by Merrill Cornish 19 Feb '16

19 Feb '16

mGraphFile is a data member of type boost:filesystem::path, which isn't (as I understand) handled natively by Boost Serialization. I could define template<class Archive> void serialize(Archive& ar, boost::filesystem::path& p, const unsigned int version); but it is needed in only one place. Below is an excerpt from an inline serialization function that I'm already using. While it has a redundant step not needed for loading and a different redundant step not needed for storing, it would seem to do what I need. (The minor inefficiency of the redundant statements is of no concern here.) ... std::string str = mGraphFile.string(); // redundant if loading ar & BOOST_SERIALIZATION_NVP(str); mGraphFile = str; // redundant if saving ... Can anyone tell me if this will work, or do I need to implement the serialize() function? Merrill Cornish

1 0

boost::msm usage: how to set properties of target states
by spiritwalker 18 Feb '16

18 Feb '16

States in my fsm has different properties. I define a event which will invoke a transition to a target state. I want to set properties of target by event data. My choices are: 1. set properties in the action or guard: but it is still in the source state. I fill not good if i set the target state properties at the time 2. set properties in the target entry: but the value of properties have been calculated in guard on receiving the event so i should recalculated again :( Any one can give me more ideas. Thanks ! -- View this message in context: http://boost.2283326.n4.nabble.com/boost-msm-usage-how-to-set-properties-of… Sent from the Boost - Users mailing list archive at Nabble.com.

2 1

SERIALIZE: Registering derived templete classes serialized via base ptr
by Unger, Jörg 17 Feb '16

17 Feb '16

I'm trying to serialize a derived class via a base ptr using boost serialize. The example to illustrate the problem (without templates) is as follows //****************** Main.cpp ********************** #include <fstream> #include <boost/archive/text_iarchive.hpp> #include <boost/archive/text_oarchive.hpp> #include "Derived.h" int main(int argc, char* argv[]) { std::string fileName = "Out.txt"; Derived myDerived; Base* myBasePtr = &myDerived; //myDerived.foo(); // serialize it as txt std::ofstream ofs(fileName.c_str(), std::ios_base::binary ); boost::archive::text_oarchive ota ( ofs, std::ios::binary ); //ota & boost::serialization::make_nvp(std::string("directly derived").c_str(), myDerived);; ota & boost::serialization::make_nvp(std::string("via base ptr").c_str(), myBasePtr);; return 0; } //*********************************************** //*************** Base.h ************************* #pragma once #include <boost/serialization/access.hpp> #include <boost/serialization/export.hpp> class Base { friend class boost::serialization::access; public: Base(){}; virtual ~Base(){}; template<class Archive> void serialize(Archive & ar, const unsigned int version) {}; }; BOOST_CLASS_EXPORT_KEY(Base) //*********************************************** //**************** Derived.h ********************** #pragma once #include <boost/serialization/access.hpp> #include <boost/serialization/export.hpp> #include "Base.h" class Derived : public Base { friend class boost::serialization::access; public: Derived(){}; void foo(); template<class Archive> void serialize(Archive & ar, const unsigned int version); }; BOOST_CLASS_EXPORT_KEY(Derived) //*********************************************** //**************** Derived.cpp ******************** #include <boost/archive/text_oarchive.hpp> #include <boost/archive/text_iarchive.hpp> #include "Derived.h" //Derived::Derived() //{} void Derived::foo() { } // serializes the class template void Derived::serialize(boost::archive::text_oarchive & ar, const unsigned int version); template void Derived::serialize(boost::archive::text_iarchive & ar, const unsigned int version); template<class Archive> void Derived::serialize(Archive & ar, const unsigned int version) { ar & BOOST_SERIALIZATION_BASE_OBJECT_NVP(Base); } BOOST_CLASS_EXPORT_IMPLEMENT(Derived) //*********************************************** When compiling the above code and linking the object files, everything works fine. When I combine everything in a library (in this example it is essentially only Derived.o) and link the main file with the library, I get an error what(): unregistered class - derived class not registered or exported The problem seems to be that the registration in the linked library is not activated. The problem is simplified here, because in our implementation, the derived class is essentially a template class that does not have any cpp-files. We have just added another otherwise empty cpp file with the registration of all possible instantiations of the class. There are several possibilities to solve the problem · The macro BOOST_CLASS_EXPORT_IMPLEMENT(Derived) could be moved to the main.cpp. This workaround is not my preferred options, since the registration has to be done in every main file we want to use the library for. · The macro BOOST_CLASS_EXPORT_IMPLEMENT(Derived) could be moved to the Base.cpp (the constructor for the base class has to be implemented in this file as well). This is another option, but this requires the header files of the derived classes to be included in Base.cpp, which is not convenient either. · Serialize one object of the derived class before serialization through the pointer, but that's only a workaround. (see the commented line in Main.cpp) · Call the foo method in Main.cpp. Surprisingly, this does not depend on whether the foo function is implemented in Derived.cpp, but also if it is called in Main.cpp. Surprisingly, if "myDerived.foo();" in Main.cpp is uncommented the program works fine, which is something I do not understand. It seems that the registration is only performed, if one of the functions in this cpp file is actually called, or am I wrong? · Implement the constructor of Derived in Derived.cpp. This approach works fine for the current example (somehow similar to the previous solution). However, in our case, Derived is a template and thus the constructor can't be implemented in the cpp file. · Another option is to always link the main file with the library and the object file Derived.o, but this is also not a convenient option. · Finally, a manual registration with register_type is possible. This could be moved to a separate subroutine that is always called in different main files. What is the recommended way of registering derived template classes that are serialized through a base ptr within a library. Best regards, Jörg F. Unger

2 1

[Timer] unresolved external symbol boost::chrono::time_point
by Aman Wardak 17 Feb '16

17 Feb '16

Env: Win7 32-bit running in VirtualBox on Macbook Pro Compiler: MS Visual Studio 14 It's my first time working with Boost. I've followed the instructions here: http://www.boost.org/doc/libs/1_60_0/more/getting_started/windows.html I've compiled Boost successfully: ============================ The Boost C++ Libraries were successfully built! The following directory should be added to compiler include paths: C:\Users\IEUser\Documents\boost_1_60_0 The following directory should be added to linker library paths: C:\Users\IEUser\Documents\boost_1_60_0\stage\lib ============================================== I've added the above paths in Visual Studio and was able to run the test in step 6 of the instructions linked above to verify my environment is set up correctly. MY PROBLEM: I'm trying to compile the very first sample code at this link: http://www.boost.org/doc/libs/1_60_0/libs/timer/doc/cpu_timers.html I get the following error: ------ Build started: Project: BoostExample, Configuration: Debug Win32 ------ Source.cpp libboost_timer-vc140-mt-gd-1_60.lib(cpu_timer.obj) : error LNK2019: unresolved external symbol "public: static class boost::chrono::time_point<class boost::chrono::steady_clock,class boost::chrono::duration<__int64,class boost::ratio<1,1000000000> > > __cdecl boost::chrono::steady_clock::now(void)" (?now@steady_clock @chrono@boost@@SA?AV?$time_point@Vsteady_clock@chrono@boost@@V?$duration@ _JV?$ratio@$00$0DLJKMKAA@@boost@@@23@@23@XZ) referenced in function __catch$??1auto_cpu_timer@timer@boost@@QAE@XZ$0 C:\Users\IEUser\Documents\Visual Studio 2015\Projects\CS2370\Debug\BoostExample.exe : fatal error LNK1120: 1 unresolved externals ========== Build: 0 succeeded, 1 failed, 0 up-to-date, 0 skipped ========== Thanks, Aman

1 0

[Test] BOOST_CHECK_EXCEPTION error message still vague
by Merrill Cornish 17 Feb '16

17 Feb '16

In BOOST_1_59_0, I complained that the error message from BOOST_CHECK_EXCEPTION was indecipherable. In BOOST_1_60_0, things improved a lot. But it still leave you hanging. I use the function fail_msg() as the predicate argument to BOOST_CHECK_EXCEPTION. If it finds a specified substring in the exception message, it returns true. Otherwise, it returns false. Below is an error message from BOOST_CHECK_EXCEPTION when the predicate returned false: exception "std::runtime_error" raised as expected: validation on the raised exception through predicate "fail_msg" The first clause says my code raised the expected exception class. That part of the message is clear and unambiguous. The second clause, however, is a non-sequitur. It seems to only acknowledge that there was a predicate named "fail_msg" without saying whether it returned true or false. Overall, the whole message doesn't say whether BOOST_CHECK_EXCEPTION passed or failed. Since a message was output, the user can assume things did not go well, but it seems like the message could be more explicit. Merrill Cornish

2 2

multiprecision max and et_on
by Daniel Brake 16 Feb '16

16 Feb '16

Hi Boost, I would like to be able to use the Eigen linear algebra library with Boost.Multiprecision with et_on. However, as noted here: https://svn.boost.org/trac/boost/ticket/11149 for max, et_on isn't compatible out of the box. Aside from writing my own little overload for max for the particular form being produced in my line of code from within Eigen, does anyone have a fix for enabling max with expression templates on? MWE: { using mpfr = boost::multiprecision::mpfr_float; // et_on by default, which is what i want using std::max; mpfr a(1), b(2), c(4); auto q = b*b+c; mpfr r = max(a,q); } Thanks a lot, Daniel

1 0

[GIL] Why doesn't pixel assignment color-convert?
by Stonewall Ballard 16 Feb '16

16 Feb '16

I've just started using boost.gil, though I've been looking at it for a while. It seems odd to me that assignment doesn't do an implicit color_convert() when the pixels are of different types. Instead, it just copies matching channels. That's the wrong thing to do when assigning an rgba pixel to an rgb pixel, since the former is straight and the latter is premultiplied. It also seems wrong that you can assign an rgba pixel to an rgb pixel, but not vice-versa. It looks like this is caused by pixels_are_compatible in gil_concept.hpp, where it fails to check that both pixels have the same number of channels. Instead, it matches channels of the output pixel against the input pixel, ignoring any extra input pixel channels. It also ignores scoped_channel_value usage. This seems like an error waiting to happen. Comments? - Stoney

1 0

ASIO: add work and remove immed., will ignore further handler_requests???
by aj neu 16 Feb '16

16 Feb '16

Hi, below is some code where boost::asio::io_service::work is added, and then immediately removed. After that, I call async_wait on a steady_timer, but it does not work: io.run() RETURNS IMMEDIATELY, and IGNORES the async_wait. Is this intended? (I was rather surprised, because I thought that the async_wait would schedule new work, but it does not work). If I cange the code-line #define WEIRD_BEHAVIOUR to #undef WEIRD_BEHAVIOUR then I have my expected behaviour. Thanks, ajneu #include <iostream> #include <chrono> #include <experimental/optional> #include <boost/asio.hpp> #include <boost/asio/steady_timer.hpp> #define WEIRD_BEHAVIOUR int main() { boost::asio::io_service io; std::experimental::optional<boost::asio::io_service::work> work; #ifdef WEIRD_BEHAVIOUR work.emplace(io); work = std::experimental::nullopt; #endif boost::asio::steady_timer timer(io, std::chrono::milliseconds{1000}); timer.async_wait([](const boost::system::error_code &ec) { std::cout << ((!ec) ? "done" : "err") << std::endl; }); io.run(); }

1 0

Writing a stratum client using boost:asio
by Jan Willem Penterman 11 Feb '16

11 Feb '16

Hi, I'm trying to write a stratum client for a cryptocurrency mining application. The mining application connects to a stratum server to receive new work to mine on and submit solutions. The stratum protocol is a simple TCP based line protocol with JSON payload. Documentation here: https://mining.bitcoin.cz/help/#!/manual/stratum-protocol I've chosen to use boost::asio, as boost is already heavily used in the fork of the project I'm building the miner for. But I'm having difficulties to understand why my current implementation doesn't work. The basic flow is as follows: 1. connect to the server. this works 2. send subscribe method. this also works 3. authorize worker(s). doesn't work. 4. stratum server should start pushing new work periodically. doesn't work. 5. submit solution when found. not implemented yet. Without authorization, the server should still start pushing work. So I've skipped step 3 for now. The source code as I have it now is available here: https://github.com/Genoil/cpp-ethereum/blob/stratum/libstratum/ The output I get from this is as follows: i 12:19:14|<unknown> Connected to stratum server coinotron.com : 3344 i 12:19:15|<unknown> {"error": null, "id": 1, "result": [["mining.notify", "91d0025c5ea54509977e3475d065169e"], "080016D0", 4]} i 12:19:15|<unknown> Subscribed i 12:19:15|<unknown> { "id": null, "method": "mining.set_difficulty", "params": [32768]} i 12:19:15|<unknown> mining.set_difficulty i 12:19:15|<unknown> {"params": ["31065", "0xc09361c52e9dddd141040cc79c52eaed382e92c1dd350324c040482a4c4ac0fa","0x5a46dd85298b0beff65ccf3006c4b5d2f7fa6ca8a5885a7f2132714fe7a48602","0x0000000200000000000000000000000000000000000000000000000000000000", true], "id": null, "method": "mining.notify"} i 12:19:15|<unknown> mining.notify >From this I can conclude that the subscription call works. Then at the end of handleResponse, I simply queue up a new async_read_until to wait for the next line of JSON to come in from the server. This also kind of works, but the idea is that after a few seconds, new work should come in as a "mining.notify". This never happens. Can anybody explain what I'm doing wrong? Regarding the mining.authorize call on line 113. I've understood from the documentation that I can send that whenever I want, so I tried to do this immediately after the subscribe method returned. But if I do this, it a) doesn't return and b) all lines after "Subscribed" don't come in any longer. This is the second problem I'm trying to figure out. I'm using this as reference, but my Python is even worse than my C++ https://github.com/slush0/stratum-mining-proxy But when I run the binaries connecting to the same host (coinotron.com:3344), I do get new work coming in... Thanks for having a look at this.

1 0

[ASIO] Newbie question - Bidirectional communication example
by Davies, John 11 Feb '16

11 Feb '16

For a simple explanation I have two processes that run on the same computer. Process 1 sends messages to Process 2 by putting the messages into an Interprocess message queue that Process 2 created. Process 2 sends messages to Process 1 by putting the messages into an Interprocess message queue that Process 1 created. The messages can be sent at any time and are not in response to each other. Very symmetrical. Now I want to put Process 1 and Process 2 on separate computers. My intent is to transfer the messages over TCP to the opposite computer without changing Process 1 or 2. So I thought I'd create two connector programs. Connector 1 creates a message queue that pretends to be the Process 2 message queue. When it gets a message, it send it over TCP the Connector 2. Connector 2 gets the message and puts it into the real Process 2 message queue. And the reverse if Process 2 has an outgoing message. I just can't find a good example to steal from. Everything I can find are more like Process 1 makes a request and Process 2 responds. So I think I have a fundamental misunderstanding of how ASIO works. ________________________________ The information contained in this message may be confidential and legally protected under applicable law. The message is intended solely for the addressee(s). If you are not the intended recipient, you are hereby notified that any use, forwarding, dissemination, or reproduction of this message is strictly prohibited and may be unlawful. If you are not the intended recipient, please contact the sender by return e-mail and destroy all copies of the original message.

2 1

[Test] Funny Business with vector::at() out-of-range
by Merrill Cornish 11 Feb '16

11 Feb '16

I posted a question a couple of days ago: "Throws 'Escaping' both BOOST_CHECK_THROW and try{}". I found that BOOST_CHECK_EXCEPTION which is working for me elsewhere fails the same way. So, an out-of-range std::vector::at() seems to be the common element. In the definition of at(), the out-of-range response is handled by __throw_out_of_range_fmt(). When I looked up that one, I found void __throw_out_of_range_fmt(const char*, ...) __attribute__((__noreturn__)) __attribute__((__format__(__gnu_printf__, 1, 2))); in functexcept.h. To my admittedly less-than-expert eye, there doesn't seem to be an actual throw() here. On the other hand, the entire file are entries like this for various exceptions. There are a lot of Google hits for __throw_out_of_range_fmt, but they are for unresolved references in links, apparently caused by mixed version of libraries and object. Everything I've got is compiled linked for MinGW 64-bit, GCC 5.3.0, 64-bit --std=C++14, BOOST 1_60_1 64-bit so I get none of those errors. The problem I'm seeing with my test code is that wrapping a try{} around BOOST_CHECK_THROW shows that [1] the body of the try doesn't complete; but at the same time [2] not even a catch(...) can catch the presumed throw--as if a throw isn't actually being done. So, where did the throw go? Merrill Cornish

2 1

[TEST] Throws "Escaping" both BOOST_CHECK_THROW and try{}
by Merrill Cornish 11 Feb '16

11 Feb '16

I'm running Windows 10, 64-bit; MinGW 64-bit; GCC 5.3 64-bit; and BOOST 1_60_1 Here is the relevant test code: [319] BOOST_CHECK_THROW(throw std::out_of_range("BOOST_CK_THROW test"), std::out_of_range); [320] try { [321] std::cerr << "arcsSize()" << std::endl; [322] empty1.arcsSize(Operand::DEFAULT_ARC_SET+1); [323] std::cerr << "arcsSize() did not throw" << std::endl; [324] }//try [325] catch (const std::out_of_range& ex) [326] { std::cerr << "out_of_range caught=|" << ex.what() << "|" << std::endl; } [327] catch (...) { std::cerr << "something else caught" << std::endl; } [328] [329] BOOST_CHECK_THROW(empty1.arcsSize(Operand::DEFAULT_ARC_SET+1), std::out_of_range); The original code was just the last line, line [329]. [319]-[327] was added in an attempt to characterize the problem. The error [329] got by itself was: terminate called after throwing an instance of 'std::out_of_range' what(): vector::_M_range_check: __n (which is 1) >= this->size() (which is 1) This application has requested the Runtime to terminate it in an unusual way. Please contact the application's support team for more information. SIGABRT intercepted; converted to exit(EXIT_FAILURE). arcSize() is implemented with std::vector::at() and the index is out-of-range, so it's supposed to throw std::out_of_range. That's what was detected, so why did it terminate the program? (The last line comes from my SIGABRT handler. Without it, the test executable ends up locked and can't be deleted.) Adding in all of the test lines shown above gives; [319] Operand_Test.cpp(319): info: check 'exception "std::out_of_range" raised as expected' has passed [321] arcsSize() terminate called after throwing an instance of 'std::out_of_range' what(): vector::_M_range_check: __n (which is 1) >= this->size() (which is 1) This application has requested the Runtime to terminate it in an unusual way. Please contact the application's support team for more information. SIGABRT intercepted; converted to exit(EXIT_FAILURE). Notice the explicit throw in line [319] is detected and handled properly. However, the arcSize() call from inside the try block throws, but is not caught by even catch(...) {}. Can anyone help me see what's going on here? Merrill Cornish

2 6

[Container] Regarding Trac #11957, static_vector::max_size() is higher than the capacity
by Gagan Kumar 10 Feb '16

10 Feb '16

I tried a simple fix for https://svn.boost.org/trac/boost/ticket/11957 here https://github.com/boostorg/container/pull/37/files . Can someone please review it. Regards,Gagan Kumar

1 0

Boost Variant Type Interfaces
by Ali Nakipoglu 09 Feb '16

09 Feb '16

Hi, In our project we are using boost, boost.variant very extensively. We was using methods provided by the library to interface with Variant types. Mainly : get<T>( variant ) for accessing stored values and variant.which() == Index for checking currently stored type. Overtime we realized we can improve this as : variant.getT() for accessing stored values much more nicer to write and variant.isT() or variant.which() == WHICH_T for checking currently stored type which does not depend on order of template paramters in the Variant definition. Also in some cases we wanted to be able to add type specific methods for example in our case we are using subscript operator to access recursively stored Variants variant[ "a" ].isT() or variant[ 0 ].asT() We generalized this solution for our project and published at https://github.com/FictionIO/WrappedVariant I would like to hear your comments. Do you think its a correct approach or useful? Any suggestions are welcome! Kind Regards, Ali

1 0

[Multiprecision] Runtime assertion failure with clang++3.6.0 but not g++4.9.2
by mbw_bst＠mailbox.org 09 Feb '16

09 Feb '16

Dear all, this is my first post on this mailing list, so hopefully this will all be by the book. Executing the following minimal working example, which is supposed to calculate "3! == 6" via (1) a template function (2) a class template and save the result in a boost::multiprecision::mpz_int, results in unexpected behavior for clang++3.6.0, with the version of my boost library being 1.59.0. The program displays the correct result using g++4.9.2 however: #include <iostream> #include <boost/multiprecision/gmp.hpp> namespace bm = boost::multiprecision; template <std::size_t N> bm::mpz_int factorial() { return N * factorial<N-1>(); } template<> bm::mpz_int factorial<0>() { return 1; } template <std::size_t N> struct factorial2 { static const bm::mpz_int value; }; template<std::size_t N> const bm::mpz_int factorial2<N>::value = N * factorial2<N-1>::value; template<> struct factorial2<0> { static const bm::mpz_int value; }; const bm::mpz_int factorial2<0>::value = 1; int main () { std::cout << factorial<3>() << '\n'; std::cout << factorial2<3>::value << '\n'; return 0; } The output for clang, having been compiled via clang++ -std=c++14 -stdlib=libc++ -DNDEBUG -o main main.cpp -lgmp will result in: 6 0 However, omitting the NDEBUG flag will trigger an assertion failure: main: /usr/include/boost/multiprecision/gmp.hpp:1296: const mpz_t &boost::multiprecision::backends::gmp_int::data() const: Assertion `m_data[0]._mp_d' failed. Aborted (core dumped) Compiling the same program with g++4.9.2 (with or without "-DNDEBUG") yields the expected result: 6 6 What did I miss? Can this behavior indeed be traced down to Boost.Multiprecision, or does it have to do with the initialization order of static const class members? Or something else? Additionally, both variants work correctly with clang when using a built-in type like 'int'. Any help in understanding the problem on hand would be greatly appreciated! Best Regards, mbw

3 5

Re: [Boost-users] [Multiprecision] Runtime assertion failure with clang++3.6.0 but not g++4.9.2
by mbw_bst＠mailbox.org 09 Feb '16

09 Feb '16

Hello again and thanks for your replies! Taking the following two statements into account: > For type int, the values are computed recursively at compile time, for a > user-defined-type the values are computed at runtime and you hit > initialization-order issues. > Seems to be that Multiprecision relies on static data that haven't > (necessarily) been initialized before your own static members. Works > fine > if the members are made non-static: Does that mean that, since a) boost::multiprecision::number<gmp_int> is not constexpr enabled, and b) static initialization can't happen at compile-time for user-defined types, that there is no way for me to initialize a variable of this type at compile-time? Does b) follow logically from a) ? I (believe to have) confirmed runtime-initialization by running valgrind, which showed the presence of dynamic memory allocations (and also jumps depending on uninitialized variables, which probably corresponds to the assertion failure). I am mentioning this because initially my little test program looked somewhat like this: #include <iostream> #include <vector> #include <boost/multiprecision/gmp.hpp> namespace bm = boost::multiprecision; template<std::size_t N> struct factorial { static const bm::mpz_int value; static void add_values(std::vector<bm::mpz_int>& vec) { factorial<N-1>::add_values(vec); vec.push_back(value); } }; template<std::size_t N> const bm::mpz_int factorial<N>::value = N * factorial<N-1>::value; template<> struct factorial<std::size_t{0}> { static const bm::mpz_int value; static void add_values(std::vector<bm::mpz_int>& vec) { vec.push_back(value); } }; const bm::mpz_int factorial<0>::value = 1; int main () { std::vector<bm::mpz_int> fac_table{}; factorial<10'000>::add_values(fac_table); std::cout << "Enter a number between 0 and 10'000 to calculate factorial:"; std::size_t number; std::cin >> number; std::cout << '\n' << number << "! == " << fac_table[number] << '\n'; return 0; } This still includes the "unsafe" static initialization of a user-defined type. However it compiles and runs via g++ -ansi -std=c++14 -O3 -Wall -Wextra -pedantic -static -save-temps -ftemplate-depth-50000 -DNDEBUG -o main main.cpp -lgmp -pthread This was what made me believe in the compile-time computation of the factorials in the first place, since using this version, valgrind does not show any dynamic memory allocation at all. On the other hand, I don't understand what's going on here really, especially since std::vector<> is supposed to allocate memory at run-time. Now I'm not sure whether the last example has anything to do with Boost.Multiprecision anymore, so while it would really make my day if you could help me better understand this, I will understand if this is not the right place to ask these questions. Thanks again for your replies so far, they have been of great help! Cheers, Max

2 1

[gsoc16] ATTN: Project ideas deadline 19th Feb
by Niall Douglas 07 Feb '16

07 Feb '16

Tomorrow 8th February the application period for Google Summer of Code 2016 begins, and yet we have just *one* idea on the ideas page: https://svn.boost.org/trac/boost/wiki/SoC2016 We need *plenty* more if we are to be approved again this year as a Google Summer of Code org, the deadline for which is the 19th February. So if you have some project ideas and think you could mentor a student this summer, *please* consider adding a project idea to the ideas list or stepping forward with a list of Boost libraries or topics you'd be willing to mentor. Our thanks in advance. --- Boost C++ Libraries Google Summer of Code 2016 admin https://svn.boost.org/trac/boost/wiki/SoC2016

1 0

download from sourceforge?
by Dan Bloomquist 07 Feb '16

07 Feb '16

I followed the link form boost.org and then through sourceforge. But sourceforge directed me to: <http://downloadbud.com/?adprovider=sourceforge_fwint&source=fw36_300x250-do…> The link is an executable! I've never heard of 'downloadbud'. Not a big deal for now, I'm running with 1.58. But I'd like to get the latest of spirit x3 before I ask questions on the spirit list that may not need asking. Is there another source for boost? Or, is this executable actually a safe extractor? Sourceforge handing over an exe when it should be be a package seems just wrong... Thanks, Dan.

2 5