Subject: Re: [boost] boost::random, header-only, boost::uuids::detail::seed_rng, and UWP development
From: James E. King, III (jking_at_[hidden])
Date: 2017-09-12 14:34:34
Part of any effort here would also include taking the Travis and Appveyor
CI files from boost::uuid and run all the checks in boost::random therefore
any incompatibilities such as the one expressed for MinGW would be
identified. In fact, it would make sense to add some additional unit test
files and/or builds to Appveyor to check different _WIN32_WINNT
compatibility levels to ensure all the build-time code branches are covered
(as well as WINAPI_FAMILY differences). The documentation on rand_s
doesn't lead me to believe it is compatible with all platforms, as it
expressly states it depends on an API that only works on Windows Desktop
applications, however a well formed CI environment would prove it out if
rand_s was to be used.
On Tue, Sep 12, 2017 at 10:13 AM, Andrey Semashev via Boost <
> On Tue, Sep 12, 2017 at 4:27 PM, degski via Boost <boost_at_[hidden]>
> > On 12 September 2017 at 15:40, James E. King, III via Boost <
> > boost_at_[hidden]> wrote:
> >> The older WinCrypt calls are not available in some Windows platforms
> >> forward, so this is
> >> going to become a problem pretty quickly for the community.
> > You worry too much, just call rand_s
> > <https://msdn.microsoft.com/en-us/library/sxtz2fa8.aspx> (the same thing
> > under the hood, but taking care of any WinCrypt BCrypt, whatever issues).
> I assume, this is MSVC-specific, i.e. doesn't work with MinGW?
> Unsubscribe & other changes: http://lists.boost.org/
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk