Dan Sugalski wrote:
> This:
>
>new P0, .PerlScalar
>new P1, .PerlArray
>assign P0, P1
>
> isn't code that a compiler should be emitting.
(snip alternative compiler output)
> Though I freely admit that's a big punt on the real problem, which we
> still need to address.
>
> I'm
At 9:55 AM +0200 8/9/02, Peter Gibbs wrote:
>Peter Gibbs wrote:
>> vtable method get_scalar(pmc)
>> vtable method get_value(pmc, context)
>
>Having broken the rule of posting before drinking coffee in the morning,
>this is obviously nonsense - neither of these will work, because we don
Peter Gibbs wrote:
> vtable method get_scalar(pmc)
> vtable method get_value(pmc, context)
Having broken the rule of posting before drinking coffee in the morning,
this is obviously nonsense - neither of these will work, because we don't
know the return type of these functions. So, back
How should the PerlScalar PMC behave in the following situation?
new P0, .PerlScalar
new P1, .PerlArray
assign P0, P1
The assign opcode will call PerlScalar's set_pmc function, which needs
to get a value from P1, so it calls PerlArray's X function??
The two obvious options seem to be:
