At 11:46 AM -0700 8/9/02, Sean O'Rourke wrote:
>On Fri, 9 Aug 2002, Dan Sugalski wrote:
>> 1) Bind the ops to the PMC implementation and just peek under the hood
>> 2) Make method calls and have the PMCs do what they need to.
>>
>> #1 requires a way to load up PMC classes along with supporting opcode
>> libs and parrot bytecode libs, which is infrastructure we've not got
>> defined yet.
>>
>> #2 is slow. Yech.
>
>Since find_method results can be cached, the only slowdown would be from
>fiddling with parameter passing (and maybe one extra level of function
>call for invoke), and from looking up the method the first time.
True, and odds are that time would be swamped by the time to actually
perform the operations. Still, it's as good an excuse as any to get
me motivated to get the stuff this needs defined... :)
--
Dan
--------------------------------------"it's like this"-------------------
Dan Sugalski even samurai
[EMAIL PROTECTED] have teddy bears and even
teddy bears get drunk
