petdance/scratch — Issue #1234: Rationalize get/set opcodes
Author: petdance
Created: 2011-11-01 05:39:41+00:00
State: open
Labels: Pri-normal, Sev-medium, todo

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:

1. Creating parallel opcodes with consistent names and signatures.
2. Deprecating the irrational opcodes.
3. Removing the irrational opcodes at the end of a deprecation cycle.

I propose that the rational form be:
a. fully spelled out;
b. with underscores;
c. 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.

Originally http://trac.parrot.org/parrot/ticket/1727