At 11:38 AM 8/24/00 -0600, Tom Christiansen wrote:
> >At 10:26 AM 8/24/00 -0600, Tom Christiansen wrote:
> >> >Remove socket functions from core
> >>
> >>Why? What is the justification? I can think of some, but you
> >>haven't given them.
>
> >There are a number of good reasons to do this from an internals standpoint,
> >enough that I'd like to do it.
>
>Is one allowed to know that number, and those reasons? :-)
Nope, it's a secret! :-P
Seriously, they are:
*) Fewer opcodes to deal with. Fewer opcodes means fewer cases to deal
with, and a potentially smaller (and more cache-coherent) dispatch table
*) Easy upgradability. To fix any issues with these functions as they
currently exist means replacing perl. If they're a module of sorts, there
can be a simple plug-in upgrade.
*) It makes optionalizing (now there's a good word... :) the functions
easier for platforms that just don't have 'em. Like, say, the Palm, or
embedded gadgets. (Most teddy bears aren't likely to come with a network
stack...)
*) Easy extension. Which is an extension of easy upgradeability, I suppose,
but if you wanted to open, say, NetWare connections, or IPv6 connections,
with the current interface it'd be nice to be able to do this without
rebuilding perl.
Dan
--------------------------------------"it's like this"-------------------
Dan Sugalski even samurai
[EMAIL PROTECTED] have teddy bears and even
teddy bears get drunk
