Closed Bug 38678 Opened 25 years ago Closed 15 years ago

RFE: xpidl -m js

Categories

(Core :: XPCOM, enhancement, P5)

Product:
Core
Component:
XPCOM
Platform:
x86
All
Type:
enhancement

Tracking

()

Status:
RESOLVED WONTFIX
Milestone:
Future

People

(Reporter: gagan, Assigned: dbradley)

Details

No description provided.
... so what does it do?
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.
[SPAM] Marking milestone 'future' as part of nsbeta3 triage.
Status: NEW → ASSIGNED
Target Milestone: --- → Future
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
mass reassign of xpidl bugs to dbradley@netscape.com
Assignee: jband → dbradley
Status: NEW → ASSIGNED
Priority: P3 → P5
Component: xpidl → XPCOM
QA Contact: mike+mozilla → xpcom
Status: ASSIGNED → RESOLVED
Closed: 15 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?
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.