This is good question.
I have the C++11 update at the roadmap for CppCMS 2.0.
One if the issues I can't do it for CppCMS 1.4 or something like that
is because removing of auto_ptr will break backward compatibility.
CppCMS is C++11 friendly. The only current incompatibility is
auto_ptr. Currently you can always hide deprecated warnings.
Also I think that moving to c++11 may be higher priority that it is now.
Artyom
On Fri, Dec 28, 2018 at 10:44 PM Andrew Marlow <mar...@gm...> wrote:
>
> Hello,
>
> I see this on the roadmap and wonder what progress has been made. I am thinking about possibly using cppcms in a linux env with the gcc 8.2.1 compiler. I plan to use the option -std=gnu++17. Use of auto_ptr with that compiler gives deprecation warnings. Using C++17 ought to give errors since auto_ptr has been removed from C++17 but gcc still just gives the warning. I expect that to be fixed soon. When it is that means game over for cppcms, which is why I am keen to find out what the plans are please.
>
> --
> Regards,
>
> Andrew Marlow
> http://www.andrewpetermarlow.co.uk
>
> _______________________________________________
> Cppcms-users mailing list
> Cpp...@li...
> https://lists.sourceforge.net/lists/listinfo/cppcms-users
|
