Dan Sugalski <[EMAIL PROTECTED]> wrote:
> At 1:30 PM +0200 6/14/03, Leopold Toetsch wrote:
>>
>> B(inout PMC, in PMC)
>>
>>This is plain wrong. If the LHS PMC doesn't exist yet, you can't
>>call its add vtable method (The implementations is
>>$1->vtable->add(...)).
> You're right. Go ahead and m
At 1:30 PM +0200 6/14/03, Leopold Toetsch wrote:
PMCs are different. Currently many opcodes with PMCs are defined like:
B(inout PMC, in PMC)
This is plain wrong. If the LHS PMC doesn't exist yet, you can't
call its add vtable method (The implementations is
$1->vtable->add(...)).
You're right.
My last attempt WRT this got warnocked, so I'll repeat and summarize
again the issue.
The PARROT_ARGDIR_{IN,OUT,INOUT} defines the directions of information
flow in and out of Parrot opcodes, for some definition of information.
You could also think of these as LHS-usage (OUT) and RHS-usage (IN)
