Status

()

Core
XPCOM
P5
enhancement
RESOLVED WONTFIX
18 years ago
8 years ago

People

(Reporter: Gagan, Assigned: David Bradley)

Tracking

Trunk
Future
x86
All
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

Comment hidden (empty)

Comment 1

18 years ago
... so what does it do?

Comment 2

18 years ago
Gagan just told me a little more about his idea, and it sounds interesting...

I'd originally thought that he was taking about sample javascript that used the
interface, an xpidl idea we'd had from before we had JavaScript components.

His thought was to generate something analogous to the sample .c++
implementations that are now generated into the .h file; the generated .js file
would contain a sample implementation of the interface, as a JavaScript
component.

Comment 3

18 years ago
[SPAM] Marking milestone 'future' as part of nsbeta3 triage.
Status: NEW → ASSIGNED
Target Milestone: --- → Future

Comment 4

17 years ago
Mass-reassigning mccabe's non-JS, non-Rhino bugs to jband (34 total). 

Would like to cc mccabe; but the mass-reassign page does not allow this. 
I'll leave it up to mccabe to decide if he wants to be cc'ed on these - 
Assignee: mike+mozilla → jband
Status: ASSIGNED → NEW

Comment 5

17 years ago
mass reassign of xpidl bugs to dbradley@netscape.com
Assignee: jband → dbradley
(Assignee)

Updated

17 years ago
Status: NEW → ASSIGNED
Priority: P3 → P5

Updated

10 years ago
Component: xpidl → XPCOM
QA Contact: mike+mozilla → xpcom

Updated

9 years ago
Status: ASSIGNED → RESOLVED
Last Resolved: 9 years ago
Resolution: --- → WONTFIX
I know this bug is over ten years old.  I'm thinking about reviving it with for xpidl.py, with a Python script like header.py.  Would anyone be interested?

Comment 7

8 years ago
Do it, but don't spam this bug about it ;-)
You need to log in before you can comment on or make changes to this bug.