From: Daniel J. <dan...@gm...> - 2016-05-31 07:26:53
|
Sam wrote: > This module _IS_ that "socket library". That was exactly what I needed to know :) Reading the rest of the discussion, as well as what Don wrote: > TCP/IP uses sockets but not raw sockets. I think the name of the module is really unfortunate. "rawsock" could plausibly mean all of the following: * "raw access" to (the general concept of) sockets (which it actually is) * access to OS specific sockets * access to "raw sockets", i.e. SOCK_RAW A better name would probably be something like BSD sockets, or even POSIX sockets. I wonder though, why is this not part of CLISP (i.e. not a module)? The socket interface of CLISP could be perfectly well build on top of "rawsock", or - if speed is an issue - on the underlying C functions. Is the "overhead" of providing access to the functions (i.e. the LISP<->C conversions, the additional subrs) really that crucial? |