4 ms·
No, for C/C++ you don't have to do anything unless the compiler writers add yet another new warning to -Wall -W, which you have to disable because it is spuriou
by naclet 3y ago
No, for C/C++ you don't have to do anything unless the compiler writers add yet another new warning to -Wall -W, which you have to disable because it is spurious.
Java is more backwards compatible, so is Common Lisp.
Someone here said that the thread on the Python "discussion" forum was shut down. That does not sound like everyone except for the proponents is supposed to be heard (or is even aware of the discussion).
- usrbinbash 3y ago> No, for C/C++ you don't have to do anything Even for such stable languages, a library maintainer has to, at the very least, patch security problems as they are discovered. > That does not sound like everyone except for the proponents is supposed to be heard (or is even aware of the discussion). There is an official poll among the Python core devs, linked in the article, which shows overwhelming support for the change. Since they are the ones who have to work this out, that's the only discussion about this that is relevant.