Togos wrote:
>
> > Anyway:
> >
> > assign Px, {Iy,Sy,Ny}
> >
> > are not needed IMHO, these end up as
> > set_<type>_native and are identical
> > to set Px, {Iy,Sy,Ny}.
>
> Yes, but as we were discussing in the
> Set vs. Assign thread, it makes more sense
> to call them 'assign', as it morphs the
> existing value (as 'assign Px, Py' does),
> instead of simply copying a pointer
> (as 'set Px, Py' does). Yay for consistancy.
> If you want to get rid of opcode aliases,
> perhaps it would be better to get rid of
> the extra 'set's.
Out of curiosity, how does the word "assign" imply that it morphs an
existing value, and how does the word "set" imply that it copies a
pointer?
Obviously, in parrot as it is now, this is how it is, but what precisely
led to the choice of those two names?
--
$a=24;split//,240513;s/\B/ => /for@@=qw(ac ab bc ba cb ca
);{push(@b,$a),($a-=6)^=1 for 2..$a/6x--$|;print "[EMAIL PROTECTED]
]\n";((6<=($a-=6))?$a+=$_[$a%6]-$a%6:($a=pop @b))&&redo;}
