On Tue, Feb 24, 2009 at 11:13:55AM -0000, Robin Barker wrote: > > > Shall we use 'deprecated' as the name for this warning? It is already in > > use and it is off by default. If we change that, users may get loads of > > warnings they don't get yet. > > We could separate deprecated into deprecated_code and deprecated_module > and have deplacated_code DEFAULT_OFF and deprecated_module DEFAULT_ON So, for things that when change are (hopefully) fixed reasonable quickly (by installing a module), we warn by default, but things that require more work (and hence time) to fix we keep silent? AbigailThread Previous | Thread Next