Re: RFC 146 (v1) Remove socket functions from core

[Nick Ing-Simmons]

Dan Sugalski <[EMAIL PROTECTED]> writes:
>At 10:08 PM 8/24/00 -0600, Nathan Torkington wrote:
>>Dan Sugalski writes:
>> > One of the current plans is for the parser to have access to a list of
>> > functions that trigger autoloading modules.
>>
>>Isn't dynamic loading really slow?
>
>Not particularly, at least not as far as I know. There's some extra cost in 
>finding the library and loading it that you wouldn't pay 

Unless you really messup the search it will be comparable to the search 
system does (LD_RUN_PATH etc.) to find "linked in" dynamic libraries.

The issue would be if you did two searches - one for Socket.so and then 
_that_ had to go look for libsocket.so 
So if the code is really just a thin wrapper on the system library then 
taking it out will be a (small) performance hit.

But it does mean we can plug in IPv7 in a twinkling, or a stub that re-directs
network traffic via the Furbie's infra-red link to the toaster...

-- 
Nick Ing-Simmons