- Boost-users - lists.boost.org

generalize boost macros
by Gero Peterhoff 06 Feb '19

06 Feb '19

Hello, I have some ideas for config/predef, multiprecision and others. config/predef: What bothers me is the inconsistent nomenclature of several macros. For example, integer: BOOST_HAS_INT128 BOOST_NO_INT64_T float: BOOST_FLOATx_C decimal: ? I think you should definitely generalize that: BOOST_HW_TYPE_AVAILABLE: only if TYPE is supported by the hardware (based on BOOST_HW_SIMD*), but not necessarily by the compiler or selected architecture BOOST_LIB_TYPE_AVAILABLE: TYPE is available from the c++library/compiler For example, float80_t: has HW support on x86 (BOOST_HW_FLOAT80_AVAILABLE is defined), but not on MSVC (BOOST_LIB_FLOAT80_AVAILABLE is not defined then) BOOST_SW_TYPE_AVAILABLE: there is an external emulation of TYPE For example, multiprecision A's complement fixed precision integer (TODO) or "half" by sourceforge Of course, this must be set manually. At least for int/float/decimal 8..512 this should be available. BOOST_HW_MACHINE_SIZE: the real word size of HW BOOST_ARCH_MACHINE_SIZE: the word size of the architecture For example, DOS on AMD Ryzen BOOST_HW_MACHINE_SIZE = 64 and BOOST_ARCH_MACHINE_SIZE = 16 multiprecision/float128_t: there are still many features missing most values in numeric_limits<float128_t> are not constexpr math::constants: i miss log2(2/e/pi/10) etc and i miss BOOST_COMP_VECTOR_EXTENSIONS_AVAILABLE if the compiler supports __attribute__(__vector_size__(...)) and BOOST_COMP_VECTOR_EXTENDED_EXTENSIONS_AVAILABLE if the compiler supports extendet vector extensions (currently only clang/llvm?) and BOOST_ARTIFICIAL __attribute__((artificial)) if supported thx

3 9

Boost serialization calling abort
by tim＠raisedbar.net 05 Feb '19

05 Feb '19

Hi, I'm experiencing the issue described at: https://svn.boost.org/trac10/ticket/13354 I' building using VS2017 and Boost 1.69.0 (I note that the article refers to 1.66.0). Does anybody know a fix for this, or am I best to revert back to 1.65.0? Best wishes. Tim Burgess Raised Bar Ltd. E: <mailto:tim@raisedbar.net> tim(a)raisedbar.net M: +44 (0)7989 486976

2 2

Latest Boost.Test version broke runtime_config::get
by David Sommer 05 Feb '19

05 Feb '19

Hi everyone, version 1.69 of boost.test broke the line *runtime_config::get<log_level>(runtime_config::btrt_log_level)* It works with static linking, however it breaks on dynamic linking. Error message is *boost::runtime::arg_type_mismatch: Access with invalid type for argument corresponding to parameter log_level* In particular the following program fails: * #define BOOST_TEST_MODULE example #define BOOST_TEST_DYN_LINK #include <iostream> #include <boost/test/unit_test.hpp> #include <boost/test/unit_test_parameters.hpp> BOOST_AUTO_TEST_CASE(failDyn) { using namespace boost::unit_test; std::cout << runtime_config::get<log_level>( runtime_config::btrt_log_level ) << std::endl; }* if boost.test is linked dynamically. Best regards, David Sommer

1 0

Boost, MacOSx, and 64 bit
by S. L. Garwood 04 Feb '19

04 Feb '19

I have built boost 1.68 and 1.69 on MacOSX. When I try to use the binary components in a link, I get an error about not being able to find a version for x86_64. Does anyone have any tips? Is there a 64 but specific define for the build? Boost 1.66 from MacPorts seems to be fine but they don’t have 1.68 or 1.69 available (yet). I have a lot of software build using MacPorts so a migration to Homebrew is not really doable at this time.

2 2

Windows 64 bit Libraries.
by A Z 02 Feb '19

02 Feb '19

The boost library contains links to 64 bit Windows libraries on the bintray website, at https://dl.bintray.com/boostorg/release/1.66.0/binaries/. However, these libraries are only for versions of the Microsoft Visual C++ compiler, which do not have compatible bit profiles towards GNU G++, but more particularly with 64 bit Windows TDM. Is it possible for someone at BOOST to build and post libraries for Windows 64 bit TDM C++ for public and professional downloading and usage?

1 0

issue with property_tree/json_parser
by Harikrishna 29 Jan '19

29 Jan '19

Hi All, I am trying to use boost json_parser. I have included json_parser.hpp in my cpp file, I have not included any other code. But I am getting many compilation errors like error: 'boost::spirit::classic' has not been declared and In function void boost::property_tree::json_parser::read_json_internal(std::basic_istream<typename Ptree::key_type::value_type, std::char_traits<typename Ptree::key_type::value_type> >&, Ptree&, const std::string&): [exec] /usr/include/boost/property_tree/detail/json_parser_read.hpp:288: error: \u2018classic\u2019 is not a namespace-name Can you help me resolve this issue? -- Thanks Harikrishna

3 2

[Spirit] Looking for a little Qi guidance for Unicode parsing
by Michael Powell 28 Jan '19

28 Jan '19

Hello, I am turning a corner in my JSON parser. I support ASCII through and through, but now I want to support Unicode, apparently UTF-8, part of the JSON standard. From what I can tell, this is not the entire grammar, but just for Strings. Looking for a little guidance on how to approach that issue, the elements involved, etc. Such as, are we talking about C++ std::wstring? I have also seen std::u32string referenced in some forums. To begin with, it is a somewhat naive impression, would the characters not translate to unsigned char or char, but rather to std::wstring::value_type or std::u32string::value_type? Things like that come to mind approaching the issue. Additionally, how to otherwise handle symbol tables such as escape characters, i.e. from: struct escapes_t : qi::symbols<char, char> { escapes_t() { this->add("\\b", '\b') ("\\f", '\f') ("\\n", '\n') ("\\r", '\r') ("\\t", '\t') ("\\v", '\v') ("\\\\", '\\') ("\\/", '/') ("\\'", '\'') ("\\\"", '"') ; } } char_esc; And on from there. Thanks! Best regards, Michael W Powell

2 1

ASIO: Writing Composed Operations
by Cristian Morales Vega 26 Jan '19

26 Jan '19

Hi, I was looking at https://www.boost.org/doc/libs/develop/libs/beast/doc/html/beast/using_io/w… and came up with a question I can't answer: In https://github.com/boostorg/beast/blob/develop/example/echo-op/echo_op.cpp#… why does it use the AsyncStream associated executor without even looking at the potentially different (right?) Handler associated executor? Regards.

3 13

Fwd: Help needed with include path
by David Aldrich 25 Jan '19

25 Jan '19

Hi I am using Boost on Ubuntu 18.04 LTS, which has boost 1.65.1 installed. I want to use boost 1.69, which I have installed on another server. I specify that remote boost path in my makefile and make compiles my source file with: g++ -c -Wall -m64 -I/net/simdata/OpenSourceLibs/Boost/rel-1.69.0/ -fpic -O3 SINRCalculation.cpp -o _gnuRelease/SINRCalculation.o Now that source file uses boost/multi_array.hpp. The above compiler command gives error: In file included from /usr/include/boost/multi_array.hpp:30:0, from SINRCalculation.cpp:25: /net/simdata/Hudson_OpenSourceLibs/Boost/rel-1.69.0/boost/type_traits.hpp:118:10: fatal error: boost/type_traits/is_nothrow_swappable.hpp: No such file or directory #include <boost/type_traits/is_nothrow_swappable.hpp> ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ compilation terminated. Now my copy of boost 1.69 does contain is_nothrow_swappable.hpp so, at first sight, that error is surprising. I think what is happening is the is_nothrow_swappable.hpp is being searched for on the system library path (boost 1.65 does not have that file), not the one I specified using -I. Am I correct? If so, how can I force the compiler to use the boost 1.69 path consistently for all paths?

3 2

Memory mapped files
by Simon Giddings 24 Jan '19

24 Jan '19

Good morning, We are developing a system which heavily uses memory mapped files. These files are initially created under a unix system, but will then be used in portable systems such as Android and iOS. We are having some problems loading memory mapped files created under Unix into Android. Is this scenario even possible ? Are the memory mapped files compatible between systems ? Hope you will be able to shed some light on this. Best regards Simon

5 10