On 01/07/2014 01:38 AM, Joshua Cranmer 🐧 wrote:
On 1/6/2014 4:27 PM, Robert O'Callahan wrote:
That's just not true, sorry. If some module owner decides to keep using NULL or
PRUnichar, or invent their own string class, they will be corrected.
Maybe. But we also have a very large number of deprecated or
effectively-deprecated constructs whose deprecation module owners may not be
aware of
because their use is somewhat prevalent in code. For example, the NS_ENSURE_*
macros are apparently now considered officially deprecated.
Since when? NS_ENSURE_ macros are very useful for debugging. (When something is
going wrong, the warnings in the terminal tend to give strong
hints what/where that something is. Reduces debugging time significantly.)
Our track
record of removing these quickly is poor (nsISupportsArray and nsVoidArray,
anyone?), and many of the deprecated constructs are macros or things
defined in external project headers (like, say, prtypes.h), which makes using
__declspec(deprecated) or __attribute__((deprecated)) unfeasible.
Is there any support for setting up a wiki page that lists these deprecated,
obsolete constructs and provides tracking bugs for actually eliminating
them?
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
