Re:The Time Needed to Write “Effective Modern C++”
by amatheus on Thursday April 23, 2015 @11:12AM
(#9427244)
Couldn't these things just be deprecated? As in, never removed because of compatibility, but when compiling you would get warnings about using features no longer 'best practices', and maybe there could be a switch for 'modern c++' that would turn use of these features in errors?
[ Parent
| on HN ]
Re:The Time Needed to Write “Effective Modern C++”
by stinos on Thursday April 23, 2015 @11:30AM
(#9427376)
Yes that would be ideal - in practice it is also not extremely hard as most of these things aren't baked in to the compiler/linker but can be solved with (a lot) of #ifdefs. The harder part is likely getting such thing into the standard: decide what will be deprecated and what not.