At 9:12 AM +0100 11/21/02, Leopold Toetsch wrote:
Oh, I hate those too. It's an evil, crufty, embarrassing piece of code. It is, however, well encapsulated, so it can be ripped out, shot, and replaced with something elegant and fast at some point in the future.Brent Dax wrote:Dan Sugalski:
# ... Later the # ancillary routine may be nonexistant if we build up the function # headers on the fly and embed the destination function into them.
Oh JITters... ;^)
jit/i386 has already code to call (specific) functions e.g. vtable funcs or pmc_new_noinit. The main differemce is, that the function signature (for vtables) comes from jit_info i.e. the definitions in core.ops.
The nci an is abstraction of this. *But*, what I really don't like in nci.c are the string functions. Can't we define, the signature is plain ascii?
Nope. If something needs that, it ought to go through the standard parrot extension loading mechanism and install real extension sub PMCs for the routines.Second: don't we need a signature for passing a Parrot_Interp* too?
--
Dan
--------------------------------------"it's like this"-------------------
Dan Sugalski even samurai
[EMAIL PROTECTED] have teddy bears and even
teddy bears get drunk
