Ticket #2114 (new RFC)
getprop op is strange
Reported by: | whiteknight | Owned by: | |
---|---|---|---|
Priority: | trivial | Milestone: | |
Component: | core | Version: | master |
Severity: | low | Keywords: | |
Cc: | Language: | ||
Patch status: | Platform: | all |
Description
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.
Change History
Note: See
TracTickets for help on using
tickets.