3 ms·
Common Lisp lacks a standard modern way to network I/O http://common-lisp.net/project/usocket/ http://common-lisp.net/project/usocket/
by mahmud 17y ago
Common Lisp lacks a standard modern way to network I/O
http://common-lisp.net/project/usocket/ http://common-lisp.net/project/usocket/
- jgg 17y agoCommon Lisp has no standard way of doing Network I/O. usocket is one of several available socket libraries which don't exist in the ANSI spec.
- mahmud 17y agoIt is a de facto standard. Everyone uses it; just like the Metaobject protocol.
- jgg 17y agoIf the usocket library suddenly disappeared, along with all the current Lisp implementations, there would be no guarantee that someone making a new CL implementation had to implement the library in a way similar to usocket, or even implement a socket library at all. It's the same as saying "everyone uses Emacs to edit Common Lisp, so it's the standard Common Lisp editor".
- mahmud 17y agoWhat is the standard way for network I/O in C, C++, Python, PHP and Ruby? I am not in the business of conjuring up hypothetical situations about the demise of Lisp implementations and libraries; that doomsday scenario of having to recreate civilization from specs is simply not in my contingency plan :-) Never underestimate the power of convention, de facto is the rule, rather than the exception.