On Fri, Feb 19, 2010 at 9:03 AM, Sjoerd Mullender <sjoerd at acm.org> wrote: > The policy should also be, if someone decides (or rather, implements) a > deprecation of a module, they should do a grep to see where that module > is used and fix the code. It's not rocket science. I'm not sure if you're aware of it, but you're starting to sound a little rude. ISTM that it doesn't make sense to waste effort ensuring that deprecated code is updated to not call other deprecated modules. Of course, all released non-deprecated code should steer clear of deprecated apis. -Mike
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