February 2015 - Boost - lists.preview.boost.org

Re: [boost] A proposal
by Ganesh Prasad 08 Feb '15

08 Feb '15

LU is already implemented in UBLAS. As of QR, SVD and Cholesky you might want to spend more time in debugging and testing for any one or two of the algorithms. https://github.com/GnsP/viennacl-dev/tree/master/viennacl/linalg you can find some useful sources here. Best wishes Ganesh

1 0

[c++11] MSVC does not define __cplusplus?
by Oliver Kowalke 07 Feb '15

07 Feb '15

Hi, I encountered that '__cplusplus < 201103L' evaluates on MSVC (14.0 ...) to true?! At least on GCC + CLANG this test works - what about MSVC? best regards, Oliver

4 4

[new libraries] [sort] New Library Check list updated
by Beman Dawes 07 Feb '15

07 Feb '15

As we started through the process of adding the sort library as a module, it became obvious the docs for how to do this were quite out-of-date. The best document for adding new libraries is https://svn.boost.org/trac/boost/wiki/ReleasePractices/ManagerCheckList#New…, and that section has now been updated. Although this document is written from the perspective of release managers, the New Library Checklist section serves as a roadmap for what is expected as a new library goes through the stages of being added to a Boost distribution. Comments and corrections welcome, --Beman

5 6

Serialisation: Is is_trivial<T> a sufficient precondition to bypass serialisation?
by Niall Douglas 06 Feb '15

06 Feb '15

A library user has raised an interesting question at: https://github.com/BoostGSoC13/boost.afio/commit/ac32ebfceb9a08b133e8c d47000d3b4807bc3e42#commitcomment-9574522 Basically, AFIO v1.3 has new pre-serialisation metaprogramming in response to Robert's comments on his Incubator about it being too hard to serialise and deserialise data with AFIO. AFIO will now consume any STL container and will implicitly auto expand to ASIO scatter gather buffers any: 1. Trivial type T 2. C array of trivial type T 3. STL container of trivial type T, including initializer_list. A free function, to_asio_buffers(T), can be specialised by external code to extend this with custom ASIO scatter gather buffers generation. Note that AFIO explicitly and intentionally expects that anyone interested in async file i/o will be doing their serialisation and endian conversion far away from AFIO code, so to_asio_buffers(T) is really for marking extra types to be treated as implicit auto expand. The user asks the question: Is is_trivial<T> a sufficient precondition for this auto expansion to be safe, or should is_standard_layout<T> also be required? The user notes that is_trivial<T> && is_standard_layout<T> == is_pod<T> which seems a little overkill to me. There is also the possibility that is_trivial<T> is too conservative. Some may argue that is_trivially_copyable<T> would be sufficient. Thoughts? Niall -- ned Productions Limited Consulting http://www.nedproductions.biz/ http://ie.linkedin.com/in/nialldouglas/

5 7

[release-mgt] missing library
by Oliver Kowalke 05 Feb '15

05 Feb '15

Hello, some weeks ago we discussed/decided that the C++11-only version of boost.coroutine should be a new lib -> boost.coroutine2. Daniel has already created a git-submodul inf the boostorg-repo and I've added the sources to branches master and develop. Unfortunately I'm missing coroutine2 (link) in <boost>/lib/coroutine2, entries in <boost>/libraries.htm and <boost>/lib/maintainers.txt. File <boost>/website/blob/master/feed/history/boost_1_58_0.qbk already contains announcement of boost.coroutine2. Could you execute the missing steps to add coroutine2 to release 1.58 please? best regards, Oliver

3 3

boost interval arithmetic
by Павел Кудан 05 Feb '15

05 Feb '15

The difference in behaviour of comparison operators and basic arithmetic operators looks as probable misconception. Default and changeable behaviour of comparison operators consists in throwing exception in intermediate situation (intersecting intervals, ! (a>b) == (a <= b) is not applicable). Great decision for correct migration from float numeric code. The only and unchangeable behaviour of arithmetic operators consists in silent returning only one of possible intervals in intermediate situation (possible return is not single, multiple interval result). The source of mistakes and undesired behaviour at migration from float numeric. At least, throwing exception by arithmetic operators at intermediate situation would provide behaviour unity of comparison and arithmetic operators and functions. Best regards, Pavel Coodan

7 51

[release-mgt] Name of release manager's repository?
by Beman Dawes 05 Feb '15

05 Feb '15

We used to have a directory <boost-root>tools/release that contained scripts used by release managers. As part of the modularization effort, it was separated into its own GitHub repository, boostorg/release. It is not a submodule of the boost super-module as it is primarily of interest only to release managers. That seems to me to be a "good thing". But I'm wondering if the "release" name might be confusing, since it doesn't contain releases or release tags themselves. Would renaming it "release-mgt" or similar be clearer? --Beman

2 2

BOOST_HAS_PRAGMA_ONCE
by Stephen Kelly 05 Feb '15

05 Feb '15

Hello, As of commit 5b20f4910d8b6b48b0b6ad2df693d36edf54cf21 in the interprocess repo, the affected files seem to expect prior include of config by the the includer. Apparently this is not obvious to everyone, so it seems worth pointing out. Thanks, Steve.

4 10

Regression tests stopped on Saturday?
by Neil Groves 05 Feb '15

05 Feb '15

Hi, I know there has been a lot go good work going on updating regression testing, and I might have missed an email. I'm currently waiting for some tests to cycle, but there appear to have been no updates since Saturday. Is this expected? Thanks, Neil Groves

6 10

Boost regression testing on Android
by Dmitry Moskalchuk 04 Feb '15

04 Feb '15

Hi all, We've just published CrystaX NDK 10.1 (https://www.crystax.net/android/ndk) which is a drop-in replacement for the Google's Android NDK, and we've included prebuilt Boost 1.57.0 libraries there, to make life easier for those developers who want to use Boost on Android. The reason I write here is that in CrystaX NDK we were able to build Boost for Android without any changes in Boost sources, just because CrystaX NDK makes Android much more POSIX-conformant than original Android is, and Boost just works on top of it. If you're interested how we did it, please read description of CrystaX NDK release on https://www.crystax.net/android/ndk. Another important point is that we were able to run Boost regression tests on Android devices - again, without any changes in Boost sources, just providing own 'adbrunner' script as tests launcher. The only thing needed is to plug one or more Android devices to USB ports and/or run one or more Android emulators and then run script for Boost testing provided by CrystaX NDK. As long as those devices/emulators are available by ADB, Boost regressions tests will run on all of them. As far as I know, Boost is not yet officially supported on Android platform, mainly because of lack of regular regression testing procedure. I wonder if someone would be interested in our results and, if yes, would he/she like to participate in further Boost-on-Android improvements? -- Dmitry Moskalchuk

3 6