This article is also available over Gopher with selector 2017-12-30 for the menu.
The Gopher URL is the following: gopher://verisimilitudes.net/12017-12-30
This is great, I’ve wanted something like this for almost a decade!
Hey verisimilitude, I know that ACUTE-TERMINAL-CONTROL didn’t make it into quicklisp, but, how about this one? :)
I don’t believe so, no. I don’t understand the ‘’:)’’.
The smile is from https://lobste.rs/s/fbaek3/acute_terminal_control_common_lisp#c_80jf8g
So, this is mockery, then? I don’t appreciate that.
No, no. I am sorry, there has been a misunderstanding, verisimilitude. I am on your side. I do find quicklisp to be very useful. This highlights the fact that Zach should not be the sole gatekeeper of quicklisp. Thanks for your work!
On first glance, as a Common Lisp outsider, I could not tell if this library was a joke. It seems not! It’s always interesting to hear about blind spots in the X3J13 spec.
Specs are always hilarious in their blind spots. POSIX’s rationale document states that an implementation of the db(3) routines would still be conforming even if it only was able to store one data item (because the hash function is implementation-defined and they can’t guarantee that it wouldn’t hash every key to the same value). ANSI REXX’s rationale states that an implementation that does nothing but report “SYSTEM RESOURCES EXHAUSTED” for every input would still be conforming (but they do state that it would somewhat violate the “spirit” of the specification).
The implementation of choice when X3J13 was written was Symbolics Lisp machine. You can’t really quit from Lisp to the system there, because Lisp is the system.