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

[Dan Sugalski]

At 07:45 PM 8/25/00 +0000, Nick Ing-Simmons wrote:
>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.

This is actually one of the spots I'm hoping to pick up a win from--if the 
only code that links against the system socket library is in the code 
that's not loaded by default, then that means one fewer system library to load.

Granted, odds are the library's in memory already, but we don't have to map 
it, and we don't need to do symbol resolution, and we generally just don't 
need to mess with it.

Big win? No. Small one. But for code that just rips through a disk file or 
something piped in on stdin, it might mean a few milliseconds shaved off 
startup.

                                        Dan

--------------------------------------"it's like this"-------------------
Dan Sugalski                          even samurai
[EMAIL PROTECTED]                         have teddy bears and even
                                      teddy bears get drunk