#2114: getprop op is strange
-------------------------+--------------------------------------------------
Reporter: whiteknight | Owner:
Type: RFC | Status: new
Priority: trivial | Milestone:
Component: core | Version: master
Severity: low | Keywords:
Lang: | Patch:
Platform: all |
-------------------------+--------------------------------------------------
The getprop op is strange because it has a signature getprop_p_s_p. By
analogy, the getattr opcode has signature getattr_p_p_s. setprop_p_s_p and
setattr_p_s_p are similar and are not a problem.
getprop_p_s_p should be changed to getprop_p_p_s for symmetry with other
ops.
Also, we should take some time to reconsider the whole properties
mechanism, since I don't think it is used often. It *is* used, but not
often and I'm not sure that it's the best mechanism for doing what we want
to do with it.
--
Ticket URL: <https://trac.parrot.org/parrot/ticket/2114>
Parrot <https://trac.parrot.org/parrot/>
Parrot Development
_______________________________________________
parrot-tickets mailing list
[email protected]
http://lists.parrot.org/mailman/listinfo/parrot-tickets
