Ticket #1727 (new todo)
Opened 11 years ago
Rationalize get/set opcodes
Reported by: | Austin | Owned by: | |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | none | Version: | 2.6.0 |
Severity: | medium | Keywords: | |
Cc: | Language: | ||
Patch status: | Platform: |
Description
There are opcodes called:
get_class getattribute getprop
with (some) corresponding setters.
The signatures are:
getattribute $PMC, 'name' getprop 'name', $PMC
I propose these be made rational by:
- Creating parallel opcodes with consistent names and signatures.
- Deprecating the irrational opcodes.
- Removing the irrational opcodes at the end of a deprecation cycle.
I propose that the rational form be:
- fully spelled out;
- with underscores;
- pmc, then name.
Thus:
$P0 = get_class $PMC $P1 = get_attribute $PMC, 'attr' $P2 = get_property $PMC, 'prop'
and likewise for the setters, and any others I may have missed.
Note: See
TracTickets for help on using
tickets.