Closed
Bug 13813
Opened 26 years ago
Closed 25 years ago
xpconnect assumes that [retval] can only be the last param
Categories
(Core :: XPCOM, defect, P3)
Core
XPCOM
Tracking
()
RESOLVED
FIXED
Future
People
(Reporter: jband_mozilla, Assigned: mike+mozilla)
Details
Attachments
(1 file)
|
1.58 KB,
patch
|
Details | Diff | Splinter Review |
xpconnect assumes that if one of the params has been marked as [retval] then it
must be the last param in the param list.
We should either enforce this in the compiler or change xpconnect. This is
a(nother) case where I'd hate to be trimming a param out of the middle of the
param list as called from JS. I'd be much happier if we enforced this in the
compiler so that xpconnect can be assured that if the param is trimmed it comes
off the end
Thoughts?
|
Assignee | |
Comment 1•26 years ago
|
||
Mass accept as ASSIGNED of xpidl bugs
|
|
Assignee | |
Comment 2•25 years ago
|
||
[SPAM] Marking milestone 'future' as part of nsbeta3 triage.
Target Milestone: --- → Future
|
|
Assignee | |
Comment 3•25 years ago
|
||
Does this bug still apply?
If so, attached patch asserts it. Patch also includes fixes to 52520.
|
|
Assignee | |
Comment 4•25 years ago
|
||
|
|
Assignee | |
Comment 5•25 years ago
|
||
Fix checked in. I jumped the gun, but I wanted to batch it with other xpidl
changes.
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
|
|
||
Comment 6•25 years ago
|
||
Patch looks good, FWIW.
You need to log in
before you can comment on or make changes to this bug.
Description
•