Closed
Bug 303500
Opened 19 years ago
Closed 7 years ago
make NS_NOTYETIMPLEMENTED a warning and not assertion
Categories
(Core :: XPCOM, defect, P5)
Core
XPCOM
Tracking
()
RESOLVED
WONTFIX
People
(Reporter: bc, Unassigned)
References
()
Details
Currently NS_NOTYETIMPLEMENTED calls nsDebug::Assertion. When assertions become fatal, this will need to be changed to a warning. Unfortunately nsDebug::Warning does not take an additional string such as "NotYetImplemented" which is currently passed to nsDebug::Assertion. It would be nice to have a nsDebug::Warning that took an additional parameter so that it could be used when switching macros like NS_NOTYETIMPLEMENTED from assertion to warning.
Comment 1•19 years ago
|
||
Perhaps we need two separate things here... there are places where NS_NOTYETIMPLEMENTED should absolutely assert.
Comment 2•17 years ago
|
||
bz, that would be nice, so I could file bugs when I hit the ones that "should assert" :)
Updated•12 years ago
|
Priority: -- → P5
Updated•7 years ago
|
Has Regression Range: --- → irrelevant
Comment 4•7 years ago
|
||
I am proposing to replace NS_NOTYETIMPLEMENTED with MOZ_ASSERT_UNREACHABLE, a fatal debug assertion, in bug 1416164. This is safe because NS_NOTYETIMPLEMENTED isn't hit during a debug Try run or when browsing some popular top sites.
You need to log in
before you can comment on or make changes to this bug.
Description
•