- Boost - lists.preview.boost.org

toml parser for boost::property_tree
by Auer, Jens 26 Feb '16

26 Feb '16

Hi, is somebody working (or has been) on a property_tree parser for toml (https://github.com/toml-lang/toml)? if not I would give it a try. It looks like a project with reasonable for a single person, but complex enough to involve some interesting components, e.g. boost::spirit. Cheers, Jens -- Jens Auer | CGI | Software-Engineer CGI (Germany) GmbH & Co. KG Rheinstraße 95 | 64295 Darmstadt | Germany T: +49 6151 36860 154 jens.auer(a)cgi.com<mailto:jens.auer@cgi.com> Unsere Pflichtangaben gemäß § 35a GmbHG / §§ 161, 125a HGB finden Sie unter de.cgi.com/pflichtangaben<http://de.cgi.com/pflichtangaben>. CONFIDENTIALITY NOTICE: Proprietary/Confidential information belonging to CGI Group Inc. and its affiliates may be contained in this message. If you are not a recipient indicated or intended in this message (or responsible for delivery of this message to such person), or you think for any reason that this message may have been addressed to you in error, you may not use or copy or deliver this message to anyone else. In such case, you should destroy this message and are asked to notify the sender by reply e-mail.

1 0

[interval] rounded_arith_opp doesn't work in Release configuration under msvc 14
by Peter Azmanov 25 Feb '16

25 Feb '16

Hello, Interval calculations with rounded_arith_opp in Release configuration under msvc 14 result in zero-size intervals. For example consider following: #include <iostream> #include <boost/numeric/interval.hpp> int main(int argc, char * argv[]) { unsigned int ctrl = _control87(0, 0); _control87(_EM_INEXACT | _RC_UP, _MCW_EM | _MCW_RC); using namespace boost::numeric::interval_lib; typedef typename unprotect< boost::numeric::interval<double> >::type interval_t; interval_t test = interval_t(1.) / interval_t(3.); std::cout << "test.lower() != test.upper(): " << std::boolalpha << (test.lower() != test.upper()) << std::endl; return 0; } This test unexpectedly prints: test.lower() != test.upper(): false Tested on x64 platform with /fp:strict and /fp:precise under MS Visual Studio Community 2015 Version 14.0.24720.00 Update 1, Boost 1.60. I've already reported this to https://svn.boost.org/trac/boost/ticket/12018 There you can find some details of what I think is going wrong and proposed workaround patch. I didn't create pull request because I'm not sure if my patch is a correct workaround. Maybe someone will propose more appropriate solution. Best regards, Peter Azmanov.

1 0

Re: [boost] Removal of boost::basic_string_ref (in favor of basic_string_view)
by Bjorn Reese 25 Feb '16

25 Feb '16

On 02/17/2016 08:52 PM, Marshall Clow wrote: > I have just removed boost::basic_string_ref from the develop branch, and > updated the specializations to use basic_string_view. I am against this decision. I am using basic_string_ref<> quite heavily in several projects that have work with Boost 1.55 and newer.

4 4

[spirit] develop test problems
by Robert Ramey 24 Feb '16

24 Feb '16

For some time now, the serialization library fails to compile on the develop branch. The test matrix for some platforms indicates syntax error in some spirit file. On other platforms, the library build is reported to "succeed" but the it still seems that library build fails. This error also shows up in the spirit library tests. see http://www.boost.org/development/tests/develop/developer/output/teeks99-09e… Is there any time frame for addressing this? It's currently creating test failures on library which depend directly or indirectly on spirit/classic. Robert Ramey

3 3

[geometry][pool][ptr_container][typeof][auto_index][quickbook] Merge to master planned for release?
by Rene Rivera 24 Feb '16

24 Feb '16

There are some changes I did to the cited libraries and tools to deal with some release build infrastructure. I need to know if the maintainers of them are going to merge their respective develop branches to master? I need to know so that I can move forward as quickly as possible to generating CI release packages for the upcoming 1.61 release. Note: If I don't hear soon I might need to do some merging myself on your libraries/tools and end up messing something up ;-) So I would prefer if the maintainers do it. -- -- Rene Rivera -- Grafik - Don't Assume Anything -- Robot Dreams - http://robot-dreams.net -- rrivera/acm.org (msn) - grafikrobot/aim,yahoo,skype,efnet,gmail

4 9

Regression impacting chrono
by Raffi Enficiaud 23 Feb '16

23 Feb '16

Dear all, There is a regression between 180bee and 372c53 on VS, and apparently boost.chrono (and indirectly boost.test...) is impacted: See http://www.boost.org/development/tests/develop/developer/output/teeks99-08e… trace below: ================= cl /Zm800 -nologo @"D:\t08\run\results\boost\bin.v2\libs\chrono\build\msvc-12.0\dbg\adrs-mdl-64\lnk-sttc\thrd-mlt\process_cpu_clocks.obj.rsp" process_cpu_clocks.cpp D:\t08\run\boost_root\boost/system/error_code.hpp(431) : error C2872: 'detail' : ambiguous symbol could be 'boost::detail' or 'boost::operators_impl::detail' ================= Between those 2 revisions, there were updates on - context - dll - system - utility - winapi Thanks, Raffi

2 2

[utility] Re: Massive test failures due to ambiguous namespace
by Rene Rivera 23 Feb '16

23 Feb '16

On Tue, Feb 23, 2016 at 1:31 PM, Markus Trippelsdorf <markus(a)trippelsdorf.de > wrote: > http://www.boost.org/development/tests/develop/developer/summary.html > show many "fails" due to: > > In file included from ../libs/chrono/src/process_cpu_clocks.cpp:17: > In file included from > ../boost/chrono/detail/inlined/process_cpu_clocks.hpp:19: > In file included from ../boost/chrono/process_cpu_clocks.hpp:22: > In file included from ../boost/chrono/detail/system.hpp:12: > ../boost/system/error_code.hpp:431:15: error: 'detail' is not a class, > namespace, or scoped enumeration > { return *detail::throws(); } > ^ > ../boost/system/error_code.hpp:431:15: error: reference to 'detail' is > ambiguous > { return *detail::throws(); } > ^ > ../boost/system/error_code.hpp:421:13: note: candidate found by name > lookup is 'boost::detail' > namespace detail { inline system::error_code * throws() { return 0; } } > ^ > ../boost/operators.hpp:658:11: note: candidate found by name lookup is > 'boost::operators_impl::detail' > namespace detail > ^ > 2 errors generated. > Also.. This is affecting general building of release packages. First time it showed up was with this superproject update < https://travis-ci.org/boostorg/boost/jobs/111041426>. Please fix ASAP! -- -- Rene Rivera -- Grafik - Don't Assume Anything -- Robot Dreams - http://robot-dreams.net -- rrivera/acm.org (msn) - grafikrobot/aim,yahoo,skype,efnet,gmail

2 2

Massive test failures due to ambiguous namespace
by Markus Trippelsdorf 23 Feb '16

23 Feb '16

http://www.boost.org/development/tests/develop/developer/summary.html show many "fails" due to: In file included from ../libs/chrono/src/process_cpu_clocks.cpp:17: In file included from ../boost/chrono/detail/inlined/process_cpu_clocks.hpp:19: In file included from ../boost/chrono/process_cpu_clocks.hpp:22: In file included from ../boost/chrono/detail/system.hpp:12: ../boost/system/error_code.hpp:431:15: error: 'detail' is not a class, namespace, or scoped enumeration { return *detail::throws(); } ^ ../boost/system/error_code.hpp:431:15: error: reference to 'detail' is ambiguous { return *detail::throws(); } ^ ../boost/system/error_code.hpp:421:13: note: candidate found by name lookup is 'boost::detail' namespace detail { inline system::error_code * throws() { return 0; } } ^ ../boost/operators.hpp:658:11: note: candidate found by name lookup is 'boost::operators_impl::detail' namespace detail ^ 2 errors generated. -- Markus

1 0

boost::container::set insert range bug
by Han Wang 23 Feb '16

23 Feb '16

Hi, Let's say we have some simple code here. boost::container::set<int> s; boost::container::set<int> const sp; s.insert(boost::begin(sp), boost::end(sp)); This insert call will cause "ambiguous call to overloaded function". Best regards, Han

2 1

GSoC Project Proposal - Boost Document Library Extensions
by Anurag Ghosh 23 Feb '16

23 Feb '16

Hello everyone! I wished to propose continue working on the Boost Document Library as a part of the Google Summer of Code 2016, and would like to work on the following things this summer on the library which was started last summer - 1. Integrating Basic Chart Support. 2. Writing comparators for the cells. (Cells are heterogeneous in nature, similar to Boost.Variant) 3. Making cell class have the behavior of a reference to the document's cell. 4. Basic formatting options for cell contents. Kindly make appropriate suggestions to my proposal. The aim of the proposal is to make it a Boost-Ready library. I would remind everyone that the library in its current state has basic spreadsheet functionality like opening, closing and exporting documents, sheet operations and cell,row,column (iterators) operations for Linux and Windows through wrappers over LibreOffice and Microsoft Office API's. ( https://github.com/BoostGSoC15/boost-document) I have been inactive for sometime, but I hope to improve test coverage before March and fix some other issues. Thanks Anurag Ghosh researchweb.iiit.ac.in/~anurag.ghosh

1 0