Closed
Bug 664258
Opened 13 years ago
Closed 6 years ago
Multiname.isAnyName/isAnyNamespace needs documentation
Categories
(Tamarin Graveyard :: Documentation, defect)
Tamarin Graveyard
Documentation
Tracking
(Not tracked)
RESOLVED
WONTFIX
Future
People
(Reporter: stejohns, Unassigned)
References
Details
The concept of "AnyName/AnyNamespace" in Multiname is (apparently) a construct that is really useful only to E4X code (to support wildcards), but this isn't well-documented anywhere in our code or specs. We should (at a minimum) add documentation to the Multiname class about when and where these variants are acceptable.
For extra credit, we could examine whether it's feasible to move the "Any" functionality to some Multiname subclass, so that it's only possible to express this functionality to the E4X code that's expecting it (thus changing a runtime/assertion failure into a compiletime failure).
Updated•13 years ago
|
Component: Virtual Machine → Documentation
QA Contact: vm → documentation
Comment 1•13 years ago
|
||
All the bells and whistles of Multinames needs to be fleshed out in "The structure of the ActionScript Virtual Machine" in avmspec, perhaps even its own toplevel section.
Blocks: avmspec
Updated•6 years ago
|
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•