Closed Bug 11591 Opened 25 years ago Closed 25 years ago

eliminate NS_COMFALSE

Categories

(Core :: XPConnect, defect, P3)

All
Other
defect

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
Component: Javascript Engine → XPConnect
Wrong component, but close.

/be
Blocks: 8929
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → INVALID
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?
Status: RESOLVED → REOPENED
But I want to take it's definition out of the header file, so you'll need to
find something else for this purpose.
Resolution: INVALID → ---
Clearing Invalid resolution due to reopen.
Status: REOPENED → ASSIGNED
OK fine. I have the fixes in hand. Ready when the tree opens.
Status: ASSIGNED → RESOLVED
Closed: 25 years ago25 years ago
Resolution: --- → FIXED
all checked in
You need to log in before you can comment on or make changes to this bug.