Leopold Toetsch wrote:
> I currently can't imagine any useful RL example for the current
> implementation of set_p_p as $1=$2, _if_ the involved PMC types are
> different.
You need to differentiate between the PMC itself, and a Parrot register
that holds the address of a PMC. In the instructio
Sorry for replying myself,
> my $b is Boolean = 2;
Here obviously a syntax disorder slept in, but the conclusion would be
the same.
leo
Peter Gibbs wrote:
[ set_p_p ]
> ... The future 'assign Px, Py' will call a vtable function
> (set_pmc);
So, trying to set a Boolean to "2", would be a case for the proposed
"assign" function, ok, yes.
> ... however, in the quoted example, the pure register level
> behaviour is all that is
Leopold Toetsch wrote:
> new P14, .PerlUndef
> set P14, 2
> set P10, P14
> An more generally, shouldn't set_p_p call some vtable function?
No. set Px, Py simply sets the Px register to point to the same PMC
as Py already points to; it does not care about the content of the
PMC in any way. The
Hi,
when testing native types with perl6 I encountered the following problem:
..p6:
my $b is Boolean = 2;
..imc:
.local Boolean _SV_b1
$P4 = new PerlUndef
$P4 = 2
_SV_b1 = $P4
..pasm:
new P14, .PerlUndef
set P14, 2
set P10, P14
..pbc
new_p_ic P14,2
s
