[boost] C++11 or C++14?

[Vinnie Falco via Boost]

I'm considering bumping up the C++ language requirement for Boost.URL
from C++11 to C++14. I have concerns about doing this, because it
affects all my downstream libraries (HTTP.Proto, HTTP.IO,
Websocket.Proto, Websocket.IO, and any examples or complete
clients/servers that I write).

My main fear is that there are still a considerable number of
individuals or corporations who, for whatever reason, cannot build
with -std=c++14 or later despite having access to newer compilers. I
don't mind if there is a small percentage of loss but I do mind if 20%
or more of potential users will be locked out.

The questions are:

1. Would you or your company be prevented from using Boost.URL if it
required C++14?

2. Do you know any other organizations who cannot use C++14 or later?

3. Do you know of any regional or global metrics on who _cannot_ use
libraries which require C++14?

See also, this reddit thread on r/cpp:

<https://www.reddit.com/r/cpp/comments/w6zuo5/c11_or_require_c14/>

--
Regards,
Vinnie

Follow me on GitHub: https://github.com/vinniefalco

_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost

[Phil Endecott via Boost]

Vinnie Falco wrote:
> I'm considering bumping up the C++ language requirement for Boost.URL
> from C++11 to C++14.

> 3. Do you know of any regional or global metrics on who _cannot_ use
> libraries which require C++14?

There were questions about what C++ versions people were able
to use in the recent C++ developer survey:

https://isocpp.org/files/papers/CppDevSurvey-2022-summary.pdf

Moving from C++11 to C++14 reduces the percentage of respondents
who can use "pretty much all" of the features of that version from
89.9% to 82.9%.

Personally, my only limitation is what Apple's clang derivative
supports; currently it lacks some C++20 features.


Regards, Phil.