Closed
Bug 11591
Opened 25 years ago
Closed 25 years ago
eliminate NS_COMFALSE
Categories
(Core :: XPConnect, defect, P3)
Tracking
()
RESOLVED
FIXED
People
(Reporter: warrensomebody, Assigned: jband_mozilla)
References
Details
We should eliminate the NS_COMFALSE madness once and for all. Here's a list of offending uses in your module -- please pass the bug along if there's someone else who should deal with it. js/src/xpconnect/tests/TestXPC.cpp: View change log or Blame annotations line 447 js/src/xpconnect/tests/components/xpctest_echo.cpp: View change log or Blame annotations line 266
Updated•25 years ago
|
Component: Javascript Engine → XPConnect
Comment 1•25 years ago
|
||
Wrong component, but close. /be
Assignee | ||
Updated•25 years ago
|
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → INVALID
Assignee | ||
Comment 2•25 years ago
|
||
Heck, this may be the only place in the code where we *should* use NS_ERROR_COMFALSE. This is code that is used to test proper handling of nsresults in xpconnect. I want to make sure to handle success codes as well as error codes. Make sense?
Reporter | ||
Updated•25 years ago
|
Status: RESOLVED → REOPENED
Reporter | ||
Comment 3•25 years ago
|
||
But I want to take it's definition out of the header file, so you'll need to find something else for this purpose.
Assignee | ||
Updated•25 years ago
|
Status: REOPENED → ASSIGNED
Assignee | ||
Comment 5•25 years ago
|
||
OK fine. I have the fixes in hand. Ready when the tree opens.
Assignee | ||
Updated•25 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 25 years ago → 25 years ago
Resolution: --- → FIXED
Assignee | ||
Comment 6•25 years ago
|
||
all checked in
You need to log in
before you can comment on or make changes to this bug.
Description
•