Closed
Bug 484509
Opened 16 years ago
Closed 14 years ago
abcasm: need support for a[i] style setproperty
Categories
(Tamarin Graveyard :: Tools, defect)
Tamarin Graveyard
Tools
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: tharwood, Assigned: lhansen)
References
Details
Attachments
(1 file, 1 obsolete file)
19.78 KB,
patch
|
edwsmith
:
review+
tharwood
:
feedback+
|
Details | Diff | Splinter Review |
i.e., setproperty null
Assignee | ||
Updated•15 years ago
|
Target Milestone: --- → Future
Assignee | ||
Updated•14 years ago
|
Assignee: tharwood → lhansen
Target Milestone: Future → ---
Assignee | ||
Comment 1•14 years ago
|
||
A simple change that adds general support for multinames using a straightforward syntax (see comment in the grammar, included in this patch).
The patch does not incorporate the regenerated jar file; ping me if you want it.
Attachment #554017 -
Flags: review?(edwsmith)
Attachment #554017 -
Flags: feedback?(tharwood)
Assignee | ||
Updated•14 years ago
|
Attachment #554017 -
Flags: feedback?(tharwood)
Reporter | ||
Comment 2•14 years ago
|
||
In general I like the way this is going. A couple of comments:
- The use of the @ character does not conform to its use in AS3, where it specifies an attribute variant of a name.
- The proto-AET backing abcasm is starting to co-evolve with the actual AET. I don't think that's a reason to avoid necessary maintenance to abcasm, but at some point these subsystems need to be made congruent. That could be done by making abcasm a driver and grammar that drives the AET, as long as we don't introduce incompatible semantics at the AET level.
Assignee | ||
Comment 3•14 years ago
|
||
Adds support for CONSTANT_TypeName and QNames in multiname instructions. Updated comment block.
Note, I ran tabify on these files because they predominantly use tabs despite the modeline that says not to use tabs, so there are a few strange changes in this diff. That appears to be a win over the otherwise mixed indentation that otherwise resulted.
Attachment #554017 -
Attachment is obsolete: true
Attachment #554040 -
Flags: review?(edwsmith)
Attachment #554040 -
Flags: feedback?(tharwood)
Attachment #554017 -
Flags: review?(edwsmith)
Attachment #554017 -
Flags: feedback?(tharwood)
Reporter | ||
Comment 4•14 years ago
|
||
Comment on attachment 554040 [details] [diff] [review]
General multiname support, v2
Review of attachment 554040 [details] [diff] [review]:
-----------------------------------------------------------------
Looks OK, but why use # on typenames? ANTLR should be able to handle <typename> style constructs, which would look a lot more like AS3 and might some day get us closer to a generalized typename.
Attachment #554040 -
Flags: feedback?(tharwood) → feedback+
Assignee | ||
Comment 5•14 years ago
|
||
Agreed, the # was a bit hacky, more for expedience than anything. I'll consider testing ".<" ... ">" to see how that works.
Comment 6•14 years ago
|
||
Comment on attachment 554040 [details] [diff] [review]
General multiname support, v2
seems fine to me if it works and you guys are happy with it. limiting scope creep probably trumps any of my notes.
nits, as you see fit:
- maybe fix the modelines to agree with the tabified files?
- xml attribute names are naturally written as @foobar... as long as IDENTIFIER sucks in the @ character, no conflict, right?
fyi, in verbose dumps I've habitually printed [] in places where an index or namespace gets substituted into a multiname. not sure how well that would parse.
Attachment #554040 -
Flags: review?(edwsmith) → review+
Assignee | ||
Comment 7•14 years ago
|
||
I've adopted both the V.<C> and [] syntaxen without any problems and I'll just land the patches with those changes without re-review.
Assignee | ||
Updated•14 years ago
|
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Comment 8•14 years ago
|
||
changeset: 6530:6b300f7377e5
user: Lars T Hansen <lhansen@adobe.com>
summary: Fix 484509: - abcasm: need support for a[i] style setproperty (r=edwsmith, f=tharwood)
http://hg.mozilla.org/tamarin-redux/rev/6b300f7377e5
You need to log in
before you can comment on or make changes to this bug.
Description
•