At 09:49 PM 2/1/2001 +0100, Johan Vromans wrote: >Dan Sugalski <[EMAIL PROTECTED]> writes: > > > The module loaded can define the routines as either regular perl > > subs or opcode functions (the difference is in calling convention > > mainly) [...] > >Difference in calling convention at the user level or just internal? Internal mainly. There'll be prototype and attribute changes at the perl level, but they're pretty trivial. (What they'll be is up in the air, but there'll have to be some) Perl subs get passed in a list of variable size, while opcode functions will get passed in a known number of parameters, likely in registers. Or on the stack, depending on the platform. Dan --------------------------------------"it's like this"------------------- Dan Sugalski even samurai [EMAIL PROTECTED] have teddy bears and even teddy bears get drunk
- Re: Really auto autoloaded modules Simon Cozens
- Re: Really auto autoloaded modules Dan Sugalski
- Re: Really auto autoloaded modules Nathan Wiger
- Re: Really auto autoloaded modules Dave Rolsky
- Re: Really auto autoloaded modules Dan Sugalski
- Re: Really auto autoloaded modules Ken Fox
- Re: Really auto autoloaded modules Ted Ashton
- Re: Really auto autoloaded modules Nathan Wiger
- Re: Really auto autoloaded modules Johan Vromans
- Re: Really auto autoloaded modules Dan Sugalski
- Re: Really auto autoloaded modules Michael G Schwern
- Re: Really auto autoloaded modules Dan Sugalski
- Re: Really auto autoloaded modules Michael G Schwern
- Re: Really auto autoloaded modules Dan Sugalski
- Re: Really auto autoloaded modules John Porter
- Re: Really auto autoloaded modules Dan Sugalski
- Re: Really auto autoloaded modules John Porter
- Re: Really auto autoloaded modules John Porter
- Re: Really auto autoloaded modules Tim Bunce
- RE: Really auto autoloaded modules Garrett Goebel