- Boost-users - lists.preview.boost.org

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

LLVM bitcode for Boost libraries?
by Osman Zakir 06 Dec '18

06 Dec '18

I want to build a project I have, which has to link against Boost.System, to WebAssembly, and it seems like I have to generate LLVM bitcode for it first. Is it possible to use the bootstrapper that comes with the Boost distribution to do this on Windows 10? The project in question is on GitHub here: https://github.com/DragonOsman/currency_converter . I switched out the Asio in the Boost distribution with the official Emscripten port of Asio, found here: https://github.com/emscripten-ports/asio . But I don't know which version of Boost.Asio it's using so I'd like some clarification on that if possible (I opened this issue there: https://github.com/emscripten-ports/asio/issues/2 and have just now updated the question to ask what version of Asio is being used for the port). [https://avatars0.githubusercontent.com/u/18173932?s=400&v=4]<https://github.com/emscripten-ports/asio/issues/2> Update of Asio port? · Issue #2 · emscripten-ports/asio<https://github.com/emscripten-ports/asio/issues/2> Sorry if this is an unwelcome question, but I want to ask if there'll ever be an update to this port of Asio to Emscripten/WebAssembly. I notice it's from 2015. Which version of Boost is it... github.com [https://avatars1.githubusercontent.com/u/8116924?s=400&v=4]<https://github.com/emscripten-ports/asio> GitHub - emscripten-ports/asio<https://github.com/emscripten-ports/asio> Join GitHub today. GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together. github.com [https://avatars0.githubusercontent.com/u/18173932?s=400&v=4]<https://github.com/DragonOsman/currency_converter> GitHub - DragonOsman/currency_converter: Application for Computer Science course<https://github.com/DragonOsman/currency_converter> Google Maps + Currency Converter Web Application. Application for Computer Science course. This is a currency converter web application with the frontend and a backend. github.com

5 14

Boost.Beast vs Boost.Asio
by Cristian Morales Vega 04 Dec '18

04 Dec '18

There are lots of things which I would expect to be in Boost.Asio which are actually in Boost.Beast. Why? Most of it is "helping" code/docs. For example: - Documentation about (and public interfaces to simplify) the creation of composed operations https://www.boost.org/doc/libs/develop/libs/beast/doc/html/beast/using_io/w… - beast::buffers_cat - beast::test::stream (to be fair, it's in experimental) But now we even have code to work around issues in Boost.Asio which ideally would simply be fixed in Boost.Asio. For example: beast::ssl_stream. I'm personally using all of the above, they are extremely useful. I just supposed it is because there is only one person working on Boost.Asio, and Christopher must be quite busy with life and getting Networking TS into the standard. I was hoping all this would go away by 2020 and I was ignoring the issue. But since now it seems Networking TS will have to wait for 2023... well, I am asking myself how to handle an increasing amount of references to Beast that in a future could change to Asio (potentially with slightly different names/semantics). So I am writing this hoping for some light on the situation.

5 10

Re: [Boost-users] [asio] UDP recv error handling
by Bjorn Reese 03 Dec '18

03 Dec '18

On 11/22/18 3:44 PM, Klebsch, Mario via Boost-users wrote: > Are there any recommendations on how to decide, whether the receive > callback function should re-initiate a receive operation after a receive > error or not? Unlike TCP, UDP does not establish a connection. By default you will not receive any network errors on a UDP socket. You have to call connect() on the socket in order to receive (ICMP) error messages, but this has other implications. With UDP it is more common to rely on application layer error messages and/or timeouts.

2 1

Monitor OSX kqueue descriptor for events with ASIO
by Blaine Walls 02 Dec '18

02 Dec '18

Hi all, I'm using boost::asio on OS X. I'd like to watch for changes to a particular regular file - per Apple's documentation, the preferred method for this is with the kevent API. So I do the following: 1) Wrap a kqueue file descriptor (obtained via a call to kqueue()) in a boost::asio::posix::stream_descriptor with boost::asio::posix::stream_descriptor::assign(). 2) Call boost::asio::posix::stream_descriptor::async_wait() to be notified of file events. The problem appears to be that boost::asio::posix::stream_descriptor::async_wait() uses ioctl() w/ FIONBIO to put the file into non-blocking mode, which fails with "Inappropriate ioctl for device". A normal blocking call to wait() works just fine. I realize that my problem is that the kqueue descriptor does not represent a stream of bytes, so it's probably invalid to use stream_descriptor to wrap it. Does anyone have any ideas on how to work around this? I looked for a type concept for a non-stream descriptor that I could implement, but I didn't see anything obvious. Thanks in advance for any advice, -Blaine

1 0