Re: [boost] Best Practices for Surviving the Boost Test Gauntlet?

On 8/9/2017 7:07 PM, Vinnie Falco via Boost wrote:

On Wed, Aug 9, 2017 at 4:04 PM, Gavin Lambert via Boost wrote:

...

Are you using the BOOST_NOEXCEPT* macros? They resolve to nothing (or in some cases to throw()) on older compilers.

No, because Beast requires C++11.

...

In general for most compatibility issues there is a macro somewhere, either in Boost.Config or elsewhere.

I know, and its amazing the amount of work and dedication that some authors go through to keep their libraries working with old compilers. Unfortunately that level of support is not something I have resources to maintain in Beast.

This is almost exclusively for libraries which have been around for a long time. Boost fully accepts the fact that your library may need a particular level of c++ compliance. The important thing is to document the level of c++ compliance needed by your library. Once you have done that then it is the end-user's problem if they are using a compiler that does not meet the level of c++ that your library needs if they wish to use your library.

I can only support Beast on Visual Studio 2015 with Update 3 or later.

Thanks