Tim Peters <tim.one@comcast.net> writes: > > I'd be in favour of renaming them, thus actively breaking extension > > modules that use them at compile time. > > That would break every extension type written for 1.5.2; the relevant ones > from Neil's random sampling are: There are different levels of breakage, though: low: generates a warning when invoked middle: fails to compile high: compiles, but corrupts memory at run-time If even the middle level is too much breakage, I'd be in favour of deprecating things in the low level: map them to a function that produces a warning when invoked. Regards, Martin
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4