Front page | perl.perl6.internals |
Postings from August 2002
set_p_p
Thread Next
From:
Aldo Calpini
Date:
August 23, 2002 07:59
Subject:
set_p_p
Message ID:
120296847125.20020823165654@alos.it
while sniffing core.ops I see this:
inline op set(out PMC, in PMC) {
$1 = $2;
goto NEXT();
}
shouldn't it be instead:
inline op set(out PMC, in PMC) {
$1->vtable->set_pmc(interpreter, $1, $2);
goto NEXT();
}
if not, then the set_pmc vtable entry is totaly useless :-)
changing this seems to cause a lot of failures in the test
suite, so I guess it's a big change that I'm asking for.
I stumbled upon this because I'm trying to implement an
Iterator PMC (almost done), and the most obvious way I've
found to bind the iterator to what it should iterate is this
one:
new P0, .PerlHash
new P1, .Iterator
set P1, P0 # tells P1 that he's going to iterate P0
this code obviously don't work with the current set_p_p
semanthic. what do you think, should I change my PASM
(and if so, how?) or do we patch core.ops instead?
cheers,
Aldo
__END__
$_=q,just perl,,s, , another ,,s,$, hacker,,print;
Thread Next