On Thu, Nov 29, 2001 at 10:51:52PM -0500, Jeff G wrote:
> > Shouldn't we be placing set_p_i and the like in vtable.ops?
> Of course, I meant vtable.tbl.
No you didn't. vtable.tbl is the methods.
> wondering if it wouldn't be better to let a human create the vtable.ops
> file and leave vtable.tbl
Jeff G wrote:
>
> Shouldn't we be placing set_p_i and the like in vtable.ops?
Of course, I meant vtable.tbl... Based on this confusion I'm now
wondering if it wouldn't be better to let a human create the vtable.ops
file and leave vtable.tbl as an auxiliary file that's used to generate
the approp
Shouldn't we be placing set_p_i and the like in vtable.ops?
-Jeff
Radio Shack: You've got questions, we've got blank stares!
ECTED]
Sent: 9/19/2001 2:11 PM
Subject: another silly question about Parrot::Opcode
I found one more bit that looks odd to me (again in _load), near the end
of the while loop is this code:
my $num_i = () = grep {/i/} @params;
my $num_n = () = grep {/n/} @params;
$opcode{
I found one more bit that looks odd to me (again in _load), near the end
of the while loop is this code:
my $num_i = () = grep {/i/} @params;
my $num_n = () = grep {/n/} @params;
$opcode{$name}{RETURN_OFFSET} = 1 + $num_i + $num_n * 2;
which could be reduced to:
