Closed
Bug 652117
Opened 13 years ago
Closed 6 years ago
hasnext{2} and nextName{Index} need better documentation
Categories
(Tamarin Graveyard :: Documentation, enhancement, P4)
Tamarin Graveyard
Documentation
Tracking
(Not tracked)
RESOLVED
WONTFIX
Q2 12 - Cyril
People
(Reporter: pnkfelix, Assigned: phohense)
References
Details
While working on Bug 640711, I needed to traverse the dynamic own properties of an object.
I was pretty frustrated when I tried to figure out how to do the traversal by reading the documentation for nextNameIndex and nextName. It is not clear in the documentation for the individual opcodes in AVM2 Overview, for example, how one starts off the iteration, because it does not say there that 0 is a valid input index.
(I think the situation may have been described more clearly in some paragraph I found in the introductory sections of the document, but I cannot find that paragraph now, so I'm going to file this bug and look into the situation more carefully later.)
Assignee: nobody → fklockii
Flags: flashplayer-qrb+
Priority: -- → P4
Target Milestone: --- → Q1 12 - Brannan
Reporter | ||
Comment 1•12 years ago
|
||
(this is really somebody else's problem at this point; I'm handing off to Paul because I know he's been looking at the bytecode spec recently.)
The VM team may well resolve as "wontfix".
Assignee: fklockii → phohense
Comment 2•6 years ago
|
||
Tamarin isn't maintained anymore. WONTFIX remaining bugs.
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
•