Closed Bug 303500 Opened 19 years ago Closed 7 years ago

make NS_NOTYETIMPLEMENTED a warning and not assertion

Categories

(Core :: XPCOM, defect, P5)

defect

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.
Perhaps we need two separate things here... there are places where NS_NOTYETIMPLEMENTED should absolutely assert.
bz, that would be nice, so I could file bugs when I hit the ones that "should assert" :)
mass reassigning to nobody.
Assignee: dougt → nobody
Priority: -- → P5
Has Regression Range: --- → irrelevant
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.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WONTFIX
See Also: → 1416164
You need to log in before you can comment on or make changes to this bug.