Leopold Toetsch wrote:
>
> I hopefully got the semantics of assign Px,Py right now. The LHS gets
> the value of RHS, eventually morphing itself to the source type.
>
> 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}.
Or else, "set Px, {Iy,Sy,Ny}" ought to create a new pmc, then use
set_<type>_native, with that new pmc as the target, and store that new
pmc into Px.
> But we are missing keyed variants to set the value of some aggregate
> member:
>
> assign(in PMC, in KEY, in PMC)
> assign(in PMC, in INTKEY, in PMC)
>
> with the 2 vtables assign_keyed and assign_keyed_int.
We can alway emulate assign semantics with set followed by assign. That
is:
$Ptmp = $Px[ y ]
assign $Pz, $Ptmp
Bleh.
> Comments welcome
--
$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;}
