- Boost-users - lists.boost.org

Boost.Spirit's Greedy Fundamental Type Parsers
by Daniel Hofmann 01 Apr '16

01 Apr '16

Suppose I want to parse a list of ";"-separated floating point pairs with "," being the pair separator as in "1,2;3,4". Following this list comes a string literal representing a file extension, such as ".txt". Therefore what I want to successfully parse input like the following: 1,2;3,4.txt (For the record, the input could also be 1.1,2.2;3.3,4.4.txt) The parser I came up with is the 1:1 translation of above's description into the Spirit DSL and shows Spirit's expressive power: ((double_ % ",") % ";") >> ".txt" Unfortunately, the parser fails on the input with the integral values above. Why? Because the fundamental parser for double_ greedily matches on the "4." in "4.txt". Changing the "4" to "4.0" as in 1,2;3,4.0.txt parses successfully (but is not an option as it requires the user to always add a trailing ".0" in case the last digit is integral. I read about Spirit's DSL mapping to Parsing Expression Grammar (PEG) with the choice operator | being evaluated in order. So the next logical step for me was to try making use of it and adapting the parser: (((int_ | double_) % ",") % ";") >> ".txt" which works on 1,2;3,4.txt but no longer on 1,2;3,4.0.txt Is there a way to adapt the parser to handle both cases? I asked this on IRC and got the answer to try a solution based on ((double_ >> ".") | (int_ >> ".")) >> "txt" but when I use use this to parse "4.txt" into a std::vector<double> via parse(first, last, ((double_ >> ".") | (int_ >> ".")) >> "txt", into); the vector contains: {4, 4} and its size() is 2, which I can make no sense of at all (but this may be a different problem). Cheers, Daniel J H

3 4

Is there any ongoing work to support toolset Clang 3.7 with Microsoft CodeGen (v140_clang_3_7)
by forumer＠smartmobili.com 01 Apr '16

01 Apr '16

Hi, Microsoft has released a new toolset mixing clang for the code analysis part and VS2015 for the code generation. https://blogs.msdn.microsoft.com/vcblog/2015/12/04/clang-with-microsoft-cod… https://blogs.msdn.microsoft.com/vcblog/2016/01/20/clang-with-microsoft-cod… Is there any ongoing work to support this new compiler and properly support it ? Thanks

1 0

Re: [Boost-users] [boost] Boost 1.61.0 Beta 1
by Tom Kent 31 Mar '16

31 Mar '16

On Thu, Mar 31, 2016 at 3:05 AM, Vladimir Prus <vladimir.prus(a)gmail.com> wrote: > > The first beta packages for 1.61.0 beta 1 are now available: > <snip> > > It was discovered that the .zip and .7z archives actually have LF line > endings, > at least in some places. Fixing this is not quite trivial, as Travis uses > ancient version of Ubuntu and Git, and is not deemed critical, as most > Windows > editors handle LF just fine. We might do something for the final release, > or > might not. > I would vote for leaving it, I've always thought it would be preferable if all the releases were the same. I think notepad.exe is the only app that still has issues with line endings, though I'd be interested in hearing some history on why was different for the windows releases. Tom

1 0

Looping through variadic macro arguments
by Florian Lindner 31 Mar '16

31 Mar '16

Hello, I have this macro: #define vmacro(expr, ...) \ cout << "n macro = " << BOOST_PP_VARIADIC_SIZE(__VA_ARGS__) << endl; \ cout << BOOST_PP_VARIADIC_ELEM(0, __VA_ARGS__) << endl; \ cout << BOOST_PP_VARIADIC_ELEM(1, __VA_ARGS__) << endl; \ for (int i = 0; i < BOOST_PP_VARIADIC_SIZE(__VA_ARGS__); i++) { \ cout << i << ": " << BOOST_PP_VARIADIC_ELEM(i, __VA_ARGS__) << endl; \ } The VARIADIC_SIZE is correct and I can access elements using BOOST_PP_VARIADIC_ELEM as long as I use a literal. The loop body produces error messages when compiling. BOOST_PP_VARIADICS is 1. The goal is to concatenate all variadic macro arguments to a string. If there a more clever solution, I'm very eager to hear them. Thanks! Florian ERROR MESSAGES: % clang++ -std=c++11 -g3 -rdynamic -ldl test.cpp test.cpp:154:3: error: expected expression vmacro(4, 5, 6); ^ test.cpp:120:26: note: expanded from macro 'vmacro' cout << i << ": " << BOOST_PP_VARIADIC_ELEM(i, __VA_ARGS__) << endl; \ ^ /usr/include/boost/preprocessor/variadic/elem.hpp:26:101: note: expanded from macro 'BOOST_PP_VARIADIC_ELEM' # define BOOST_PP_VARIADIC_ELEM(n, ...) BOOST_PP_CAT(BOOST_PP_VARIADIC_ELEM_, n)(__VA_ARGS__,) ^ 1 error generated. g++ -std=c++11 -g3 -rdynamic -ldl test.cpp In file included from test.cpp:9:0: test.cpp: In function 'void f(int)': test.cpp:120:26: error: expected primary-expression before ')' token cout << i << ": " << BOOST_PP_VARIADIC_ELEM(i, __VA_ARGS__) << endl; \ ^ test.cpp:154:3: note: in expansion of macro 'vmacro' vmacro(4, 5, 6); ^ test.cpp:120:26: error: 'BOOST_PP_VARIADIC_ELEM_i' was not declared in this scope cout << i << ": " << BOOST_PP_VARIADIC_ELEM(i, __VA_ARGS__) << endl; \ ^ test.cpp:154:3: note: in expansion of macro 'vmacro' vmacro(4, 5, 6); ^

2 16

Boost 1.61.0 Beta 1 Release Candidate 2
by Vladimir Prus 31 Mar '16

31 Mar '16

Second set of release candidates for 1.61.0 beta 1 are now available: http://boost.cowic.de/rc/boost_1_61_0_b1_rc2.zip http://boost.cowic.de/rc/boost_1_61_0_b1_rc2.tar.bz2 http://boost.cowic.de/rc/boost_1_61_0_b1_rc2.tar.gz http://boost.cowic.de/rc/boost_1_61_0_b1_rc2.7z As always, the release managers would appreciate it if you download the candidate of your choice and give building it a try. Please report both success and failure, and anything else that is noteworthy. The changes from RC1 are: * Top-level directory in the archive matches the name * Zip and 7z archives use CRLF line endings The known issues are: * Documentation build has some wrong-location, extra-files and broken-links issues. * There was a report of Boost.Context issue on OSX Release managers believe these issues are not blocking beta 1. The SHA1 checksums are as follows: 4d3c83d3a802d3dd12d4f2d516b3fcf076f6f6ba boost_1_61_0_b1_rc2.7z 8c6ac7326a3cabcabf6c7876052b73e0d41fc36d boost_1_61_0_b1_rc2.tar.bz2 e82b8ff7c3ad5b08c7dbeac1ea85fcf707a1cd4d boost_1_61_0_b1_rc2.tar.gz 7292e8fdac0566fe098a60a197a5722d381842d3 boost_1_61_0_b1_rc2.zip The SHA256 checksums are as follows: bc8341bfb8c6621319ad9eb732179fc7ec4da35c3cefc31b613f83ec3df10361 boost_1_61_0_b1_rc2.7z c0f06c78c195af9079773a2b250674244f1899ec81e84d5455f0761f1d888a16 boost_1_61_0_b1_rc2.tar.bz2 400fa0949aa201d993bf116461365e5d44904a3f8db6412f4f40f2b4ab490405 boost_1_61_0_b1_rc2.tar.gz d75688ecad601303dda2658e9a3d06f406dd4dc8e2c13c36bdadcac0a11dcffa boost_1_61_0_b1_rc2.zip Thanks! -- The release managers

2 2

Encountering an issue trying to compile on OS X 10.11.4
by Brian Krisler 29 Mar '16

29 Mar '16

Hi, I am trying to compile a package that utilizes boost libraries, and the compilation fails. This is on OS X El Capitan, with clang version: 7.3.0.7030029. Is this a known issue, and is there a work around? In file included from /opt/local/include/boost/signals2/slot_base.hpp:18: /opt/local/include/boost/signals2/detail/foreign_ptr.hpp:42:54: error: reference to 'weak_ptr' is ambiguous template<typename T> struct weak_ptr_traits<std::weak_ptr<T> > ~~~~~^ /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../include/c++/v1/memory:5035:29: note: candidate found by name lookup is 'std::__1::weak_ptr' class _LIBCPP_TYPE_VIS_ONLY weak_ptr ^ /opt/local/include/boost/signals2/detail/foreign_ptr.hpp:25:30: note: candidate found by name lookup is 'std::weak_ptr' template<typename T> class weak_ptr; ^ /opt/local/include/boost/signals2/detail/foreign_ptr.hpp:42:33: error: redefinition of 'weak_ptr_traits<weak_ptr<type-parameter-0-0> >' template<typename T> struct weak_ptr_traits<std::weak_ptr<T> > ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ /opt/local/include/boost/signals2/detail/foreign_ptr.hpp:38:33: note: previous definition is here template<typename T> struct weak_ptr_traits<boost::weak_ptr<T> > ^ /opt/local/include/boost/signals2/detail/foreign_ptr.hpp:54:56: error: reference to 'shared_ptr' is ambiguous template<typename T> struct shared_ptr_traits<std::shared_ptr<T> > ~~~~~^ /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../include/c++/v1/memory:3847:29: note: candidate found by name lookup is 'std::__1::shared_ptr' class _LIBCPP_TYPE_VIS_ONLY shared_ptr ^ /opt/local/include/boost/signals2/detail/foreign_ptr.hpp:24:30: note: candidate found by name lookup is 'std::shared_ptr' template<typename T> class shared_ptr; ^ /opt/local/include/boost/signals2/detail/foreign_ptr.hpp:54:33: error: redefinition of 'shared_ptr_traits<shared_ptr<type-parameter-0-0> >' template<typename T> struct shared_ptr_traits<std::shared_ptr<T> > ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ /opt/local/include/boost/signals2/detail/foreign_ptr.hpp:50:33: note: previous definition is here template<typename T> struct shared_ptr_traits<boost::shared_ptr<T> > ^ 4 errors generated. Thanks Brian

1 0

Build console_test_runner.cpp in boost-1.60.0
by Sergiy Tkachuk 29 Mar '16

29 Mar '16

Hello, I downloaded sources boost_1_60_0.zip from boost.org I have built boost libraries. After this I tried to build console_test_runner.cpp located at \libs\test\tools\console_test_runner\src\console_test_runner.cpp of boost_1_60_0.zip. I run following command: ..\..\..\..\b2 toolset=msvc-14.0 address-model=64 variant=release debug-symbols=on I run it from the folder \libs\test\tools\console_test_runner\ I got errors, I tried to investigate them. It appears that console_test_runner.cpp contains following line: #include <boost/test/utils/runtime/cla/named_parameter.hpp> I tried to search boost folder for files "named_parameter*.*". I found html-files only. Then I checked Boost.Test repo at https://github.com/boostorg/test, rev. 36c5fe6a5604d0277f6d6a4cf167f95c38095c3c I also didn't found "named_parameter*.*" How can I obtain console_test_runner.exe from console_test_runner.cpp? I am not an expert in building boost, I just need working binaries. Thank you, -- Best wishes, Sergiy

1 0

LynxOS
by Miller, Caleb R 29 Mar '16

29 Mar '16

Has anyone ever used boost with LynxOS? In particular LynxOS-178 using ppc? Thanks, Caleb Caleb R. Miller 314-232-5633 The Boeing Company

1 0

Re: [Boost-users] Boost.Serialization how to use serialize without nvp
by Bjorn Reese 27 Mar '16

27 Mar '16

On 03/23/2016 12:45 PM, gast128 wrote: > We want archives the same for debug and release. So I tried a couple of things: > * use primitive_type: This doesn't work if the type T is a string. Basically > it doesn't come in the 'load(std::wstring &ws)' anymore, since it now routes > to operator<< and then all kinds of nasty thing happens for xml archives. I do not have a solution for you, but I wanted to voice my support for a new level type to ignore a nesting level (but not its content) during serialization.

2 1

ptree json parser is not bidirectionnal
by Sébastien Gallou 25 Mar '16

25 Mar '16

Hi all, I experience a strange behavior of parsing non-JSON data with JSON parser. Take this example : boost::property_tree::ptree m_tree; > // Non-JSON to ptree using JSON parserstd::istringstream is("1"); // Simple value, non-JSON > boost::property_tree::json_parser::read_json(is, m_tree); // ==> No exception ! > // ptree back to JSONstd::ostringstream buf; > boost::property_tree::json_parser::write_json(buf, m_tree, false); // ==> Exception > > Unserializing non-JSON value using JSON parser doesn't raise exception. If you try to serialize the resulted ptree, you now got an exception. Is this behavior normal ? In this case, is there an easy and light mean to check that input value is JSON formatted (Regex ?) ? Thanks for your help, S. Gallou

1 0