- Boost - lists.preview.boost.org

[GitHub] Checks not listed for Travis CI
by Mateusz Loskot 18 Sep '19

18 Sep '19

Hi, GitHub offers the Checks tab [1] which displays CI checks based on Travis CI, Azure Pipelines, etc. I can't find out why the Travis CI ones are not displayed for any of repositories under github.com/boostorg/ I checked Histogram, Beast, and a few others and ffor GIL only Azure Pipelines is displayed (I integrated AzP there from the marketplace fairly recently). I suspect, that is due to the fact Travis CI integration was installed long time ago, using an old way, so it does not 'recognise' new features. For example, using the old webhooks/services method now deprecated which then was automatically ported to new marketplace-based integrations. Does anyone know how to add the Checks feature to boostorg/ repos? One of interesting feature of it is that it can display "a specific line in a commit causes a check to fail" [1] [1] https://help.github.com/en/articles/about-status-checks#checks Here is example of the Checks in full: https://github.com/OSGeo/gdal/pull/1776/checks I can confirm enabling the Checks has nothing to do with the branch protection feature and enabling required statuses of PRs. Best regards, -- Mateusz Loskot, http://mateusz.loskot.net

2 2

Details of environment building release docs and website
by Mateusz Loskot 18 Sep '19

18 Sep '19

Hi, Where can I find details about the environment used to build the website and the documentation for the releases? For example, - What is the OS? (i.e. system packages can be identified then) - What is toolset and compiler version used? GCC 4.8? - What is the version of Python, Doxygen, AsciiDoc, Sphinx? I looked at these places, but it's still unclear to me https://www.boost.org/development/website_updating.html https://github.com/boostorg/website/blob/master/.travis.yml Or was I supposed to derive the answer from the Travis CI's image php:'5.3'? Best regards, -- Mateusz Loskot, http://mateusz.loskot.net

1 0

[Quickbook] VSCode Extension for syntax colouring & simple preview
by Jan Bouwer 18 Sep '19

18 Sep '19

I've built a Visual Studio Code <https://code.visualstudio.com/> extension to provide simple syntax colouring & preview generation for Boost.Quickbook source files. It is available from within the VSCode extension marketplace or at https://marketplace.visualstudio.com/items?itemName=JBouwer.boost-quickbook… - from where the GitHub repos/issue tracker can be accessed too. Perhaps somebody else may find this useful too - like I have. Regards Jan Bouwer

2 1

[program_options] Proposal: self-contained, header-only port of Boost Program Options library
by Vicram Rajagopalan 17 Sep '19

17 Sep '19

I am interested in creating a header-only implementation of the Boost Program Options library that only depends on the C++ standard library. Program Options uses several other Boost libraries, so I would have to re-implement some of it using standard library constructs. I have 2 questions for the community: 1. Would you use something like this if it were available? 2. Do you know of any implementation details of Program Options which might make some part of this difficult or impossible? To be clear, I do not intend for this to be merged into Boost in any form. Rationale: There is no portable command-line argument-parsing capability in the C++ standard library. There's getopt, but that's in unistd.h which is only available on Unix-based systems. The only widely-used C++ command-line parsing library I am aware of is Program Options, but that requires adding a dependency on Boost to your project, which seems like overkill to me. I would like to be able to simply add a project as a submodule in my Git repo and #include it without even having to add anything to my build files. The goal is to ensure that the library is as portable and easy to include as possible, because it shouldn't be difficult to parse command-line options. I appreciate any thoughts, comments, or criticisms! -Vicram Rajagopalan

9 14

[Boost.numeric.ublas] Compiler warnings when building with O2 optimizations and NDEBUG defined
by Albert Perlman 17 Sep '19

17 Sep '19

I am using boost v1.69, compiling with g++-7 for an x86 target. If I build with -O2 optimization flags when NDEBUG is defined, I get the following compiler warning: ./../boost/numeric/ublas/matrix_expression.hpp:59:20: error: ‘*((void*)&<anonymous> +8)’ is used uninitialized in this function [-Werror=uninitialized] return e_.size2 (); If I add -fno-partial-inling to the compiler flags, this makes the warning go away. This warning does not appear if NDEBUG is not defined, regardless of optimization flags. This behavior is the same with boost v1.71. I would like to build with the -fpartial-inling optimization when NDEBUG is defined. Is there a workaround to fix this warning? -- Albert -- IMPORTANT: The information contained in this transmission may be privileged, proprietary and confidential and protected from disclosure. It is intended only for the intended recipient. If you are not the intended recipient or a person responsible for delivering this transmission to the intended recipient, you may not disclose, copy or distribute this transmission or take any action in reliance on it. If you received this transmission in error, please notify us immediately by replying to this message and please dispose of and delete this transmission. Thank you. Yaskawa America, Inc.

1 0

Write data to NAND flash file system
by JH 13 Sep '19

13 Sep '19

Hi, I am using boost::filesystem to write / remove files to NAND flash file system where it writes by pages, the system can cache and pack data upon write back to avoid segmentation if fsync(), fdatasync(), O_SYNC or a sync mounted filesystem are not used to force write. Will the boost::filesystem::ofstream and operator<< involve any of sync call? Which IO library is not using sync call? Thank you. Kind regards, - jupiter

1 0

math
by Gero Peterhoff 12 Sep '19

12 Sep '19

Hello Developers, Hello John, thanks for making the float128_t features I missed available in boost 1.71. But: - I miss in boost::math::constants log2_e (M_LOG2E); You have written in the documentation that all constants are now available; are there any other constants missing? - in boost/multiprecision/float128.hpp, the value in numeric_limits<float128_t>::is_bounded must be true Thanks and Greetings Gero

2 1

Secure-by-default networking
by Alex Christensen 11 Sep '19

11 Sep '19

At https://github.com/boostorg/asio/pull/283 <https://github.com/boostorg/asio/pull/283> I’ve attached a proof-of-concept which explores making ASIO secure by default. The C++ committee is discussing what secure-by-default networking would look like in the soon to be published papers P1860 and P1861. Since the C++ Networking TS is based on ASIO, this seems like a good place to try things out. The implementation uses BoringSSL for its crypto and Security.framework to evaluate certificates against the root certificates trusted by the system. I've implemented enough to see what the API shape would need to be, and it works with basic client and server programs. I’d love to get your feedback on this initial work, including any implementation concerns you have and suggestions on portability. I don’t think the patch is ready to commit as-is.

3 2

Re: [boost] Secure-by-default networking
by Bjorn Reese 11 Sep '19

11 Sep '19

On 9/11/19 1:35 AM, Alex Christensen via Boost wrote: > At https://github.com/boostorg/asio/pull/283 <https://github.com/boostorg/asio/pull/283> I’ve attached a proof-of-concept which explores making ASIO secure by default. The C++ committee is discussing what secure-by-default networking would look like in the soon to be published papers P1860 and P1861. Since the C++ Networking TS is based on ASIO, this seems like a good place to try things out. Please don't. There are plenty of networking applications that do not use SSL. Use ssl::stream if you want secure-by-default.

1 0

Re: [boost] Requesting opinions on CECS (C/C++ Error Control) library for possible boost implementation.
by Bjorn Reese 11 Sep '19

11 Sep '19

On 9/8/19 3:17 PM, Terablade via Boost wrote: > I have also released the library on github:https://github.com/terablade2001/CECS This library is described as handling "textual informative error control" using severity levels, so the first question that comes to mind is how this differs from Boost.Log? PS: The standard as reserved all symbol names starting with an underscore followed by a capital letter.

2 1