Subject: Re: [boost] Libraries and C++ compliance
From: Paul A. Bristow (pbristow_at_[hidden])
Date: 2017-04-10 08:39:34
> -----Original Message-----
> From: Boost [mailto:boost-bounces_at_[hidden]] On Behalf Of Niall Douglas via Boost
> Sent: 10 April 2017 08:05
> To: boost_at_[hidden]
> Cc: Niall Douglas
> Subject: Re: [boost] Libraries and C++ compliance
> On 10/04/2017 03:24, Edward Diener via Boost wrote:
> > Please, please library authors this is important. No end-user or tester
> > of your library wants to spend extended time trying to figure out why
> > some compile fails when the answer turns out simply to be one of
> > inadequate C++ conformance level for a particular compiler
> > implementation being used with a particular level of conformance.
+1 - this IS really important to users.
(and even info on what happens with older versions that the author cannot test, including any clues. "Some parts will probably work
with C++ 2003 but no tested." are also useful).
Using BOOST_STATIC_ASSERT_MSG at the right places is really helpful too.
> Outcome is up for review here end of May.
> Are you happy with its compiler support at
> https://ned14.github.io/boost.outcome/prerequisites.html? To save people
> clicking on the link:
> "Outcome is a header only C++ 14 library known to work on these
> compilers or better:
> clang 3.5 (LLVM)
> clang 3.7 (with Microsoft Codegen)
> GCC 5.4
> VS2015 Update 2
> Xcode 7.3
Yes - just right.
--- Paul A. Bristow Prizet Farmhouse Kendal UK LA8 8AB +44 (0) 1539 561830