December 2018 - Boost-users

Formatting Boost.Uuid as string
by Michael Powell 11 Dec '18

11 Dec '18

Hello, I see that you can do "basic" formatting of boost::uuids::uuid via boost::format. This is good for basic formatting, but are there other format specifiers one can furnish? I'm thinking along the lines of formats such as with or without hyphens, etc. Or an ability to extend such a feature for that matter. See my C# WPF GuidGen for some examples: http://github.com/mwpowellhtx/guidgenwpf/tree/master/src/GuidGen.Wpf/Formats This is based on the Microsoft GuidGen, but using WPF technology, and with some additional formats. Thanks! Best regards, Michael Powell

1 0

[release] 1.69.0 closed for release
by Marshall Clow 11 Dec '18

11 Dec '18

The master branch is now closed for all changes except by permission. The commit-bot isn't running on master, so the super project will need to be manually updated for any changes. If all goes well, the release candidate should be out later today. Thanks, -- The Boost Release Team

3 4

travis runners version
by Alain Miniussi 10 Dec '18

10 Dec '18

Hi, I see that travis runners uses open MPI 1.6.5 mpirun.openmpi --version mpirun.openmpi (OpenRTE) 1.6.5 which is considered "retired" on the OpenMPI download page (https://www.open-mpi.org/) current version is 4.0.0 and most linux ditrib I see uses 2.x.x or hirgher. What is the travis runners distrib/version ? Thanks -- ----- Alain Miniussi DSI, Pôles Calcul et Genie Log. Tél. : +33492003009 (Mont-Gros) Tél. : +33483618544 (Sophia Antipolis)

1 0

Boost.Filesystem perms on Windows
by Lars 10 Dec '18

10 Dec '18

Hello, The documentation<https://www.boost.org/doc/libs/1_68_0/libs/filesystem/doc/reference.html#En…> (boost version 1.68) for boost::filesystem::perms enumerator says; "Windows: All permissions except write are currently ignored. There is only a single write permission; setting write permission for owner, group, or others sets write permission for all, and removing write permission for owner, group, or others removes write permission for all." Does "All permissions except write are currently ignored" restriction apply to both getting permission from a file and setting permission to a file? In other words, does it apply to both boost::filesystem::status(..) and boost::filesystem::permissions(..) methods? Why does the fileysystem have this restriction? Is this some limitation in the design or a bug or missing feature? Kind regards, Lars

2 3

Mocking with boost.test
by Sean Farrow 09 Dec '18

09 Dec '18

Hi all, I was just wondering whether boost.test provides any mocking facilities? If it doesn't is there a recommended mocking framework? Any help appreciated. Kind regards Sean.

4 3

GIL: New file io, almost there, but can't compile 'write_view'
by Dan Bloomquist 08 Dec '18

08 Dec '18

So, I had to deal with a lib I worked on last a couple of years ago. Great news, the file IO has been greatly simplified in 1.68. I was able to retire several dozens of cryptic,(for me), lines. The old code won't compile as the Adobe extensions are gone. I'm almost there, I can read files, but I don't understand why I can't get the writer to compile. I get to my code, in case it matters: bg::rgb8_image_t destImg( res, x ); resize_view( view( sourceImg ), view( destImg ), bg::bilinear_sampler( ) ); and rgb8_image_t should be a good one from what I read: <https://www.boost.org/doc/libs/1_68_0/libs/gil/doc/html/io.html> With either: bg::write_view( path_to, destImg, bg::jpeg_tag() ); or: bg::image_write_info<bg::jpeg_tag> write_setttings; bg::write_view( path_to, destImg, write_setttings ); ms140 complains: 1>C:\cpp\boost_1_68_0\boost/gil/extension/toolbox/metafunctions/get_pixel_type.hpp(33): error C2039: 'reference': is not a member of 'boost::gil::image<boost::gil::rgb8_pixel_t,false,std::allocator<unsigned char>>' 1> c:\cpp\boost_1_68_0\boost\gil\typedefs.hpp(176): note: see declaration of 'boost::gil::image<boost::gil::rgb8_pixel_t,false,std::allocator<unsigned char>>' 1> console_test.cpp(248): note: see reference to class template instantiation 'boost::gil::get_pixel_type<boost::gil::rgb8_image_t>' being compiled 1>C:\cpp\boost_1_68_0\boost/gil/extension/toolbox/metafunctions/get_pixel_type.hpp(34): error C2146: syntax error: missing '>' before identifier 'reference' What am I missing? Do I need to supply more information? I'll put the whole thing in a url if needed. Thanks, Dan.

2 3

[release] Boost 1.69.0 Release Candidate 1
by Marshall Clow 07 Dec '18

07 Dec '18

The release candidates for the 1.68.0 release are now available at: <https://dl.bintray.com/boostorg/release/1.69.0/source/> The SHA256 checksums are as follows: af05616f71006f97833e130aad886c96136457511ace4b5496d6566e69cbe0ca boost_1_69_0_rc1.7z 8f32d4617390d1c2d16f26a27ab60d97807b35440d45891fa340fc2648b04406 boost_1_69_0_rc1.tar.bz2 9a2c2819310839ea373f42d69e733c339b4e9a19deab6bfec448281554aa4dbb boost_1_69_0_rc1.tar.gz d074bcbcc0501c4917b965fc890e303ee70d8b01ff5712bae4a6c54f2b6b4e52 boost_1_69_0_rc1.zip 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 Boost Release Managers

2 2

error_code using c++11 and boost
by Lars 07 Dec '18

07 Dec '18

Hello, A project that uses Boost 1.6X (filesystem, uuid, asio) and C++14 on multiplatform. Does it make sense to use std::error_code in this project ? The concern is compatibility between boost and std. The filesystem_error exception will return a boost ::system::error_code which is not compatible with std::error_code as far as I can tell. Exception is not an option. Would it be possible for boost to implement some sort of convertion method from boost::system::error_code to std::errror_code? Thanks kind regards, Lars

3 2

Re: [Boost-users] error_code using c++11 and boost
by Bjorn Reese 06 Dec '18

06 Dec '18

On 11/16/18 4:06 PM, Lars via Boost-users wrote: > Would it be possible for boost to implement some sort of convertion > method from boost::system::error_code to std::errror_code? The upcoming 1.69 release of Boost.System has built-in support for std::error_code. If you need to use earlier versions, then you can create a bridge between the two: http://breese.github.io/2016/06/18/unifying-error-codes.html

3 2

[Spirit] How to prohibit reserved names from matching
by Michael Powell 06 Dec '18

06 Dec '18

Hello, Let's say I have some Qi rules: qi::rule<It, char()> mych; qi::rule<It, std::string()> myname; struct reserved_names_t : qi::symbols<path_t, path_t> { reserved_names_t() { this->add("CON", "CON") ("PRN", "PRN") ("AUX", "AUX") ("NUL", "NUL") ("COM1", "COM1") ("COM2", "COM2") ("COM3", "COM3") ("COM4", "COM4") ("COM5", "COM5") ("COM6", "COM6") ("COM7", "COM7") ("COM8", "COM8") ("COM9", "COM9") ("LPT1", "LPT1") ("LPT2", "LPT2") ("LPT3", "LPT3") ("LPT4", "LPT4") ("LPT5", "LPT5") ("LPT6", "LPT6") ("LPT7", "LPT7") ("LPT8", "LPT8") ("LPT9", "LPT9") ; } } reserved_names; Assuming I've defined mych accordingly, the simple approach would be: myname %= +myname; This gets me the name in the character set. Now, I want to prohibit the reserved names from matching. myname %= ~qi::no_case[reserved_names] | +myname; However, this does not seem to work. I suppose it is one thing ruling out invalid characters, but what about prohibiting whole strings? Thanks in advance for any insights... Michael Powell

1 0