19:26:19White_Flamenote that it's pretty disruptive to your ql installation
19:27:22White_Flamenot sure how to search history for a package, htough
19:44:01earl-ducaineStyle question: CLHS occasionally uses (VALUES) rather than NIL. e.g. (READ S NIL (VALUES) T) Does this ever make a difference? If not, is it still used as a convention to distinguish various types of NIL?
19:49:57jcowanReturning NIL is returning one value, namely NIL. Returning (VALUES) is literally returning zero values. In contexts where a value is demanded, zero values will be silently coerced to a single value, namely NIL, but in the REPL, zero values is normally shown by printing nothing, whereas a single value NIL is shown by printing NIL or ().
19:53:01grawlinsonmanaged to grab a tarball of html-encode, but it's not ideal relying on quicklisp :(
19:54:57earl-ducainejcowan: awesome explanation. Just noticed the side-effect in the REPL. Makes perfect sense to use that notation in the context of READ. Thansk!
19:55:07jcowanThe argument to a function is a context demanding exactly one value (not always true of macros), so I have no idea why anyone would write (VALUE) instead of NIL for the eof-values argument to READ