November 2017 - 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

boost::filtered_graph filtering on vertex color... if I only had a colormap
by Brian Davis 19 Jul '19

19 Jul '19

Lets say I have a graph g (of type graph_t) and a color map (boy I wish I had a colormap): typedef boost::property_map<graph_t, boost::vertex_color_t>::type color_map_t; or is it? auto indexmap = boost::get(boost::vertex_index, g); auto colors = boost::make_vector_property_map<boost::default_color_type>(indexmap); or maybe? auto indexmap = boost::get(boost::vertex_index, g); auto colors = boost::make_vector_property_map<boost::vertex_color_t>(indexmap); or possibly some goop found on the internet? boost::make_iterator_property_map(color_map.begin(), boost::get(boost::vertex_index, data_->g), color_map[0]) or other internet goop? typedef boost::property_map<GraphType, boost::vertex_color_t>::type color_map_t; color_map_t colorMap; boost::color_map(colorMap)) or other internet goop?? std::vector<int> colorMap(num_vertices(g), boost::white_color); so confused... (certainly not surprised why bgl is not a part of stl) Can someone help explain the various types and ways of specifying colormaps and the logic for each way and means? and a function (if I could get that far without VS syntax highlighter going bonkers and gobs of compiler errors.. you know the type): make_pretty(g, colormap ) which colors the graph colormap and a filter struct for boost::filtered_graph<Graph, EdgePredicate, VertexPredicate> (where I wonder why if I only want to filter vertices I have to set boost::keep_all for EdgePredicate... sigh... I know the answer... and also know how long it found me to find/figure out boost::keep_all - and if you are looking for boost::keep_all and found it here... your welcome ;-) ) and modifying (probably incorrectly) boost::filtered_graph example to: template <typename ColorMap> struct vertex_color_filter_eq { vertex_color_filter_eq() { } vertex_color_filter_eq(ColorMap colormap/*, boost::default_color_type c*/) : m_colormap(colormap)/*, m_c(c)*/ { } template <typename Vertex> bool operator()(const Vertex& v) const { return 0 < get(m_colormap, v); //return c < get(m_colormap, v); } ColorMap m_colormap; //boost::default_color_type m_c; }; auto indexmap = boost::get(boost::vertex_index, g); auto colors = boost::make_vector_property_map<boost::default_color_type>(indexmap); // some where here I would call make_pretty(g, colors) typedef property_map<graph_t, boost::vertex_color_t>::type ColorMap_t; vertex_color_filter<ColorMap_t> filter(colors); // boost::filtered_graph<graph_t, boost::keep_all, VertexPredicate> boost::filtered_graph<graph_t, boost::keep_all, vertex_color_filter> fg(g, filter); // Later say if I could get it compile and better if it compiled and worked I could move on and auto color = boost::red_color; typedef property_map<graph_t, boost::vertex_color_t>::type ColorMap_t; vertex_color_filter<ColorMap_t> filter(colors, color); boost::filtered_graph<graph_t, boost::keep_all, vertex_color_filter> fg(g, filter); Maybe if I color them yellow, I can then reach the wizard pull back the curtain and ask how to create a color map... If I only had a color map.

4 6

Boost Unit Test: How to run only the enabled tests of a test suite?
by Maarten Anonymous 28 Dec '17

28 Dec '17

Hey, I'm looking for a way to only run the enabled unit tests of a tests suite. I have the following test suite: #define BOOST_TEST_MODULE decorator_predicate#include <boost/test/included/unit_test.hpp>namespace utf = boost::unit_test; BOOST_AUTO_TEST_SUITE(test_suite_1) BOOST_AUTO_TEST_CASE(bare_test){ BOOST_TEST(true);} BOOST_AUTO_TEST_CASE(enabled_test, * utf::enabled()){ BOOST_TEST(true);} BOOST_AUTO_TEST_CASE(disabled_test, * utf::disabled()){ BOOST_TEST(false);} BOOST_AUTO_TEST_SUITE_END() BOOST_AUTO_TEST_SUITE(test_suite_2) BOOST_AUTO_TEST_CASE(bare_test){ BOOST_TEST(true);} BOOST_AUTO_TEST_CASE(enabled_test, * utf::enabled()){ BOOST_TEST(true);} BOOST_AUTO_TEST_CASE(disabled_test, * utf::disabled()){ BOOST_TEST(false);} BOOST_AUTO_TEST_SUITE_END() Compilation and running: # Compile the test g++ predicate.cpp -o predicate # List all tests./predicate --list_content test_suite_1* bare_test* enabled_test* disabled_test test_suite_2* bare_test* enabled_test* disabled_test # Run the tests that are enabled by default./predicateRunning 4 test cases... *** No errors detected # Here, I would like to only run the enabled tests of test_suite_1.# Instead, all tests are run. Including the disabled../predicate -t test_suite_1Running 3 test cases... predicate.cpp(21): error: in "test_suite_1/disabled_test": check false has failed *** 1 failure is detected in the test module "decorator_predicate" How can I only run the enabled tests of tst_suite1? Only bare_test and enabled_test should be run. Thanks!

2 1

[test] Set fixture for all tests
by Florian Lindner 28 Dec '17

28 Dec '17

Hello, can I set a fixture for the entire test tree, so that it is called before and after each test case? BOOST_FIXTURE_TEST_CASE does that for a test suite, but how can I apply it to all tests e.g. the master test suite? Thanks, Florian

2 1

[iostreams] file_descriptor doesn't retry on EINTR
by David Roberts 30 Nov '17

30 Nov '17

Hi, I have found that the file_descriptor class in Boost.Iostreams does not retry on EINTR. The relevant code is in libs/iostreams/src/file_descriptor.cpp. A bug was raised for this 7 years ago: https://svn.boost.org/trac10/ticket/4913 <https://svn.boost.org/trac10/ticket/4913> There is a patch attached to that bug that makes the file_descriptor_impl::read method retry on EINTR. If something like this were implemented then something similar should also be done to retry in the file_descriptor_impl::write method. I could have a go at submitting a PR to make both the read and write methods retry if interrupted. But before I do this, is there any other history I should be aware of, like a good reason why EINTR is not currently handled? Many thanks, David

2 1

boost::asio::buffer bug with string literal
by Martijn Otto 29 Nov '17

29 Nov '17

When using boost::asio::buffer with a string literal the terminating null character is included in the buffer size, leading to bugs like accidentally sending out a null character. We could fix this by adding something like this to buffer.hpp: /// Create a new non-modifiable buffer that represents the given character array. /** * @returns A const_buffer value equivalent to: * @code const_buffer( * static_cast<const void*>(data), * (N - 1) * sizeof(char)); @endcode */ template <std::size_t N> inline BOOST_ASIO_CONST_BUFFER buffer( const char (&data)[N]) BOOST_ASIO_NOEXCEPT { return BOOST_ASIO_CONST_BUFFER(data, (N - 1) * sizeof(char)); } But this might cause trouble when using a const char array that is not null-terminated, since we then basically drop the last character. Would this be the best approach?

3 6

[Spirit.Qi] failing to parse IP address octets
by Michael Powell 27 Nov '17

27 Nov '17

Hello, I've got the following parsers which are failing to find the correct attributes. I tried to parse in terms of uint_parser<uint8_t, 10, 1, 3>() at first, but this was not working properly. So I tried the following: _octet_rule = lexeme[ char_('0') | (char_('1') >> -(digit >> -digit)) | (char_('2') >> -((char_('0', '4') >> -(digit)) | (char_('5') >> -(char_('0', '5'))) | char_('6', '9') ) ) | (char_('3', '9') >> -digit) ]; Which is presently failing to find all three digits in the "20\d"-"24\d" use case. Octet itself parses correctly when I use this rule: _octet_rule >> !(char_); My octet test cases verify the entire range of 0-255 successfully, as well as the following invalid cases: VerifyOctet(-1, invalid_); VerifyOctet(1990, invalid_); VerifyOctet(2550, invalid_); VerifyOctet("255.", invalid_); VerifyOctet(256, invalid_); VerifyOctet(999, invalid_); VerifyOctet("abc", invalid_); VerifyOctet(123.456, invalid_); Converted to corresponding string, i.e. "1990" or "123.456". But when I combine that into the IP address rule, the test results occur: _octet_rule >> repeat(3)[char_('.') >> _octet_rule]; And the test results: CHECK_THAT( y, Equals(x) ) with expansion: "145.23.183.47" equals: "145.231.183.47" with message: Verifying address >>> 145.231.183.47 <<< FAILED: CHECK_THAT( y, Equals(x) ) with expansion: "189.21.29.11" equals: "189.211.29.11" with message: Verifying address >>> 189.211.29.11 <<< FAILED: CHECK_THAT( y, Equals(x) ) with expansion: "90.60.32.24" equals: "90.60.32.246" with message: Verifying address >>> 90.60.32.246 <<< FAILED: CHECK_THAT( y, Equals(x) ) with expansion: "22.59.144.140" equals: "223.59.144.140" with message: Verifying address >>> 223.59.144.140 <<< IP address test data is randomly generated, or combinatorially if I wanted to wait for all 4.3B or so test cases. However, I figure that as long as the Octet rule is working, it is reasonable to expect the Address rule may also work. Not sure why those last digits are being dropped, however. Or how the 1's can succeed where the 2's are failing. Any suggestions, Spirit folks? Thanks! Cheers, Michael Powell

1 3

[serialization] property_tree::ptree bpta back-end, json, forward (upward) compatibility
by Sergey Spiridonov 27 Nov '17

27 Nov '17

Hi Current binary, text and xml archive back-ends allow to implement backward compatibility. This means that it is possible to read old serialization files with the new version of the serialization code, with the help of the version of the class which is stored in archive itself. Unfortunately forward compatibility is not possible to implement with the existing archive backends. Suppose we have class A with one field. struct A { template<class Archive> inline void serialize(Archive & ar, const unsigned int version ) { ar & BOOST_SERIALIZATION_NVP(field); } int field; }; Later we want to add a new field2. To be able to load the previously created file we need can use versioning. struct A { template<class Archive> inline void serialize(Archive & ar, const unsigned int version ) { ar & BOOST_SERIALIZATION_NVP(field); if(version > 0) { ar & BOOST_SERIALIZATION_NVP(field2); } } int field; int field2; }; BOOST_CLASS_VERSION(A, 1) But if we want the opposite, to load the old class from the file which was created from the new class (for example, if we use serialization to communicate between new and old version of application on the network), existing backends will fail. Why? The reason is that they expect certain field in certain order and do not allow unexpected unknown fields. Although with text and binary backend it is difficult to do, because field names are not stored, but xml backend has names for every field, so it can simply skip unknown fields. Unfortunately this is not implemented. I created [1] simple experimental archive which allows forward(upward) compatibility. It stores data in boost::property_tree::ptree (instead of std::stream), which, in turn, can be saved to json, if necessary. If the file which is loaded, has additional unknown fields (from future version), they will be ignored. [1] https://github.com/sena73/ptree_archive Intermediate storage of data in ptree has its advantages and disadvantages. Of course, this slows down things and requires more memory. On other hand, it allows to get upward compatibility automatically easily and even to process data before (or without) loading it into the target class. Also we get json and info storage for free. With little modification xml backend from property_tree can be used. Sure, it must be possible to create a version of boost::archive::xml which will be also capable to keep upward compatibility without necessity to load things into the property_tree first. Binary and text archives must be extended with field names to allow field skipping. -- Best regards, Sergey Spiridonov

1 1

[release] Boost 1.66.0 Beta 1
by Daniel James 24 Nov '17

24 Nov '17

Boost release 1.66.0 beta 1 is now available at: <https://dl.bintray.com/boostorg/beta/1.66.0.beta.1/source/> The SHA256 checksums are as follows: e7b23e638e8c3a9da1512439385b04850829cea7bd56d8398677c096857d830b boost_1_66_0_b1.7z 5d0405eb73bd609ebcd54bbc96d4f1e2d97c51b96c4703706695ddd94f942d6b boost_1_66_0_b1.tar.bz2 f0f455e39bc47b2b670a17cb221687506e9a22dc478956d3d8aabb9cb835a7dc boost_1_66_0_b1.tar.gz 694c8b9e902b7981670bce166f675f3875c19326936db51aabd98d2ddfea9b45 boost_1_66_0_b1.zip For details of what's in the release, see <http://www.boost.org/users/history/version_1_66_0.html>. Please download the beta, give it a try, and report any problems you encounter. Thanks, -- The Boost Release Team

3 4

how to build boost binary libraries for GCC in windows 10
by Renfan Luo 23 Nov '17

23 Nov '17

Hi All As VS supports OpenMP2.0 only, I have to use GCC instead for my project with parallelisation in coding. I have downloaded Cygwin and installed the GCC 6.4.0 then updated it to the latest version 5.5.0 on my windows 10. All those binary libraries I built up in VS 2017, I guess, cannot be usable for GCC, so it may be necessary to rebuild them for boost 1.65.1 for GCC. Could you guys show me how to build them? Cheers Renfan

2 4

function template argument deduction with std::tuple
by Ireneusz Szcześniak 23 Nov '17

23 Nov '17

Hi, I have a problem related to function template argument deduction with std::tuple (with boost::tuple too). I attach a file with the complete source you can compile. Below I describe the code. I have a template function declaration: > template <typename T> > auto > get_cost(const T &); Then I define my template types: > template <typename Graph> > using Vertex = typename Graph::vertex_descriptor; > > template <typename Graph> > using Label = std::tuple<Vertex<Graph>>; I define the specialization of the get_cost function for the Label type: > template <typename Graph> > auto > get_cost(const Label<Graph> &l) > { > return std::get<0>(l); > } I can define alright a variable of type Label: > struct graph > { > using vertex_descriptor = unsigned; > }; > > Label<graph> l; But I cannot use the templated function: > get_cost(l); I get this error: > error: use of 'auto get_cost(const T&) [with T = > std::tuple<unsigned int>]' before deduction of 'auto' I got this error with GCC HEAD 8.0.0 20171113 and Clang HEAD 6.0.0 (I used wandbox.org). Some other type definitions and their specializations of the get_cost function compile. For a struct derived from the std::tuple: > template <typename Graph> > struct Label1: std::tuple<Vertex<Graph>> > { > }; > > template <typename Graph> > auto > get_cost(const Label1<Graph> &l) > { > return std::get<0>(l); > } For a member of type std::tuple: > template <typename Graph> > struct Label2 > { > std::tuple<Vertex<Graph>> t; > }; > > template <typename Graph> > auto > get_cost(const Label2<Graph> &l) > { > return std::get<0>(l.t); > } For a member of type Vertex<Graph>: > template <typename Graph> > struct Label3 > { > Vertex<Graph> m_v; > }; > > template <typename Graph> > auto > get_cost(const Label3<Graph> &l) > { > return l.m_v; > } I would like to use the Label type, i.e., because it has the constructor and operators already defined, which I need. I would appreciate it if someone could explain what is going wrong here. Best, Irek

2 6

Building b2 --prefix include directory not quite
by Michael Powell 22 Nov '17

22 Nov '17

Hello, So the B2 help indicates that the include directory should be whatever "<prefix>/include" is. So, I'm setting my prefix accordingly, something like, "/path/to/installed/boost-1.65.1", however, the include directory ends up being something a little more like this: "/path/to/installed/boost-1.65.1/include/boost-1_65_1". This looks like a bug to me. Can I set the --includedir myself and correct this during my build? Thank you... Cheers, Michael Powell

1 0

[Interprocess] Waiting thread termination causes deadlock
by Markus Bonk 22 Nov '17

22 Nov '17

Hi, I am having issues with boost::interprocess::ipcdetail::spin_condition::do_wait_timed deadlocking. The issue occurs when a thread that is waiting due to a call to interprocess_condition_any::wait() terminates unexpectedly and interprocess_condition_any::notify_all() is called (from any process). The cause of the deadlock is not that the terminating thread held a lock – it doesn’t because it is waiting, but that spin_condition::m_num_waiters is never decremented to zero because one of the threads is no longer waiting and so the enter mutex is not freed. I have tried BOOST_INTERPROCESS_ENABLE_TIMEOUT_WHEN_LOCKING, however as far as I can see this only tells me that the deadlock is there. Are there any suggestions how I can recover from spin_condition not freeing the enter mutex? Or perhaps some way of avoiding the issue? Markus ________________________________ Markus Bonk Senior Software Engineer [cid:image19ab5c.GIF@24a568cc.448b8dc0] 3Dconnexion GmbH Clarita-Bernhard-Str. 18 81249 München Germany Tel: +49 (89) 897 45 42 - 70 Fax: +49 (89) 897 45 42 - 50 markus_bonk(a)3dconnexion.com<mailto:markus_bonk@3dconnexion.com> www.3dconnexion.com<http://www.3dconnexion.com> Geschäftsführer: Antonio Pascucci Sitz der Gesellschaft: München Registergericht: München HRB 99232

1 0

Adding Lzma support to b2 invocation
by Michael Powell 22 Nov '17

22 Nov '17

Hello, So I've got LZMA downloading, have the include in hand, as well as what I presume are either object files and/or a DLL. Just need to know how to integrate that with my B2 invocation. Something like: -sLZMA_INCLUDE="/path/to/lzma/include" ? And then, how to include the object file with the linkage, or the DLL(s). And necessarily in which architecture/address-model. Otherwise, I am getting close to building. Around the corner from that is Locale support from ICU (?), which I've got downloading as well ATM. Cheers, Michael Powell

1 0

Re: [Boost-users] Building boost b2 lzma options
by Michael Powell 21 Nov '17

21 Nov '17

Next errors seem to be lzma related. Is this along the same lines as with Zlib and bzip2? To avoid confusion, this is 1.65.1, as well; not the announced 1.66. Thanks! On Mon, Nov 20, 2017 at 1:41 PM, Nelson, Erik - 2 via Boost-users <boost-users(a)lists.boost.org> wrote: > Michael Powell Sent: Monday, November 20, 2017 1:24 PM >> >> I am building Boost and making progress. Thus far wondering what >> >> options to provide my B2. I added the zlib include path to the >> >> include="...;/path/to/zlib;...", and now seems to be wanting the LIB >> >> path? > > I use > > "-sBZIP2_SOURCE=/path/to/bzip2/src" "-sZLIB_SOURCE=/path/to/zlib/src" > > And it adds the source to the build. > > ---------------------------------------------------------------------- > This message, and any attachments, is for the intended recipient(s) only, may contain information that is privileged, confidential and/or proprietary and subject to important terms and conditions available at http://www.bankofamerica.com/emaildisclaimer. If you are not the intended recipient, please delete this message. > _______________________________________________ > Boost-users mailing list > Boost-users(a)lists.boost.org > https://lists.boost.org/mailman/listinfo.cgi/boost-users

3 5

Building boost b2 zlib options
by Michael Powell 20 Nov '17

20 Nov '17

Hello, I am building Boost and making progress. Thus far wondering what options to provide my B2. I added the zlib include path to the include="...;/path/to/zlib;...", and now seems to be wanting the LIB path? LINK : fatal error LNK1181: cannot open input file 'z.lib' LINK : fatal error LNK1181: cannot open input file 'zlib.lib' LINK : fatal error LNK1181: cannot open input file 'zll.lib' LINK : fatal error LNK1181: cannot open input file 'zdll.lib' Which option is that for B2? After that, it is on to finding bzip? fatal error C1083: Cannot open include file: 'bzlib.h': No such file or directory Is there a source download similar to that of zlib? I think I'm pretty close but for a handful of obscurish third party dependencies. Thanks! Cheers, Michael Powell

4 9

Could guys help on OpenMP odeint 'for' statement error
by Renfan Luo 20 Nov '17

20 Nov '17

Hi All I have just started an OpenMP application example in VS2017 platform (/* Boost libs/numeric/odeint/examples/openmp/lorenz_ensemble_simple.cpp). When switch on Properties->C/C++->Language->Open MP Support-> Yes (/openmp), it has a build error Severity Code Description Project File Line Suppression State Error C3016 'i': index variable in OpenMP 'for' statement must have signed integral type OpenMP-test1 c:\users\renfanluo\source\repos\openmp-test1\openmp-test1\openmptest1.cpp 35 If When switch off Properties->C/C++->Language->Open MP Support-> Yes (/openmp) to No (/openmp), then the error goes off. However, "No" means OpenMP is switched off, which is not what I want. It is understood that in the for statement, the variables can be assigned with data type before, the errors associated with these user defined for statement will go off but the similar error shown below remain the same for boost header files. Severity Code Description Project File Line Suppression State Error C3016 'i': index variable in OpenMP 'for' statement must have signed integral type Test-OpenMP2 C:\boost_1_65_1\boost\numeric\odeint\external\openmp\openmp_range_algebra.hpp 72 Could you guys have any ideas of how to fix this problem? Best regards Renfan

1 0

[python::numpy] Access Violation when initializing numpy
by Christian Henning 18 Nov '17

18 Nov '17

Hi all, On Windows 10 with Visual Studio 2017 I', trying to run the following code in x64 debug configuration: #include <iostream> #include <boost/python.hpp> #include <boost/python/numpy.hpp> namespace p = boost::python; namespace np = boost::python::numpy; int main() { Py_Initialize(); np::initialize(); p::tuple shape = p::make_tuple(3, 3); np::dtype dtype = np::dtype::get_builtin<float>(); np::ndarray a = np::zeros(shape, dtype); return 0; } In the line np::initialize(); I'm getting a Exception thrown at 0x0000000066E43B15 (python36.dll) in test.exe: 0xC0000005: Access violation reading location 0x0000000000000025. occurred Inside boost::python::numpy::intialize() the exception is thrown when trying to execute the line: PyObject *numpy = PyImport_ImportModule("numpy.core.multiarray"); Does anyone know why that would happen or how to debug the issue further? I have installed all packages via pip and executed the python code as described in https://www.scipy.org/getting-started.html. Thanks ahead! Christian

1 1

[python] Linker error when initializing numpy
by Christian Henning 18 Nov '17

18 Nov '17

Hi all, I have the latest boost from the master branch and built everything including python. I can see that two python related libs were built: libboost_python3-vc141-mt-gd-x64-1_66.lib libboost_numpy3-vc141-mt-gd-x64-1_66.lib For compiling python I use vcpkg and it's generating python3_d.lib for debug and python3.lib for release. The cpp code I like to compile is: #include <iostream> #include <boost/python.hpp> #include <boost/python/numpy.hpp> namespace p = boost::python; namespace np = boost::python::numpy; int main() { Py_Initialize(); np::initialize(); return 0; } A few issues: 1) linker is looking for "boost_python3-vc141-mt-gd-x64-1_66.lib" but I got "libboost_python3-vc141-mt-gd-x64-1_66.lib" Please tell me how to fix that. For now I just copied the libboost* files and renamed them. 2) Linker error: "__declspec(dllimport) void __cdecl boost::python::numpy::initialize(bool)" How can I resolve that? Thanks, Christian

4 6

Conan-center package.
by Philippe Groarke 17 Nov '17

17 Nov '17

Are there any plans to release an official Boost package on Conan-Center? If not, any specific reason? It would really help Windows builds and facilitate enterprise adoption. Thank you & good day.

1 0

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

Could guys help me on a boost MPI link error
by Renfan Luo 16 Nov '17

16 Nov '17

Hi All I have built boost binary library on my PC workstation in windows 10 using VS 2017 for boost 1.65.1 successfully for application of MPI in my project. I had a simple test for MPI which worked perfectly. So I moved to a further test using boost example "odeint-v2/examples/mpi/phase_chain.cpp", which is applied to solve ODE with MPI capacity. When I tried to build the project, it gives me an error Severity Code Description Project File Line Suppression State Error LNK1112 module machine type 'x86' conflicts with target machine type 'x64' MPI-test2 C:\Users\renfanluo\source\repos\MPI-test2\MPI-test2\libboost_mpi-vc141-mt-1_65_1.lib(environment.obj) 1 I googled, then I went to properties->Linker->Advanced->Target Machine, changed to "MachineX86 (/MACHINE:X86)", then rebuild the project, now the error changes to Severity Code Description Project File Line Suppression State Error LNK1112 module machine type 'x64' conflicts with target machine type 'x86' MPI-test2 C:\Users\renfanluo\source\repos\MPI-test2\MPI-test2\x64\Release\MPItest2.obj 1 So this shows that simply changing the target machine setting in VS will not work. Could you guys give me some indications of how to fix this problem. Best regards Renfan

2 1

Boost.Chrono custom I/O
by Leo Cacciari 15 Nov '17

15 Nov '17

Hi, I'm using boost.chrono in a project and I need some non-standard input-output. First of all, I need to print days as days. Consider the following code namespace testing { typedef boost::chrono::duration<long double,boost::ratio<86400>> day; } int main(int argc,char *argv[]) { using namespace testing; day d(10.5); std::cout << "Value: " << d << std::endl; } This prints Value: 10.5 [86400/1]seconds Which is obviously right; but I'd rather have: Value 10.5 days Obviously, a solution is to define operator<<(ostream&,const & day), however I'd rather use the facet approach, which looks like easier to extend to parsing and more flexible (e.g. allowing to print the above value as "10.5 days" somewhere and as "10.5 d" elsewhere.) If I understand the documentation, I must define a subclass of boost::chrono::duration_units and then imbue the facet into the stream. Is this right? Where can I found some guidelines on how to do that? Thanks for the help lc -- Leo Cacciari Aliae nationes servitutem pati possunt. Populi Romani est propria libertas.

1 0

[Beast] Problems in getting started with Beast
by Sharklaser Lasershark 14 Nov '17

14 Nov '17

Hello! I'm migrating a project from libcurl to Beast. I'm trying to compile http_client_async.cpp <https://github.com/boostorg/beast/blob/develop/example/http/client/async/ht…>, but 110 errors come from "file_win32.ipp" and "file_win32.hpp", mostly missing declarations and members. I'm using Visual Studio 2017 (warning level 4). Here is what I have done: 1. Downloaded and set up boost 1.65.1 according to the "getting started" tutorial <http://www.boost.org/doc/libs/1_65_1/more/getting_started/windows.html> - Built all binaries - Verified header only example and binary-dependent example 2. Downloaded beast/include/boost <https://github.com/boostorg/beast/tree/develop/include/boost> from GitHub and moved the folder and .hpp to - C:\Program Files\boost\boost_1_65_1\boost 3. Started an empty project and pasted in the http_client_async.cpp <https://github.com/boostorg/beast/blob/develop/example/http/client/async/ht…> example. I have spent too many days trying to get this up and running. Any help would be greatly appreciated! Kind regards

2 1

help on how to build mpi library
by Renfan Luo 14 Nov '17

14 Nov '17

I am a new user of boost and have downloaded 1.65.1 and unzipped it to my C:\local\boost_1_65_1. Then chose the "MPI nearest neighbour coupled phase chain." Example, file "phase_chain.cpp" as my first test in VS2015, I have got a link error message "Error LNK1104 cannot open file 'libboost_mpi-vc141-mt-1_65_1.lib" . I have checked the boost root directory and sub-directories and did not this library file. Hope guys can suggest how I build mpi library and install it to windows.

3 3