libera/#lisp - IRC Chatlog
Search
19:03:09
edgar-rft
I think it's -> https://www.cliki.net/html-encode - but the github link on that page is 404 :-(
19:16:06
White_Flame
it was on quicklisp before, given that it's in quickref, so look in prior ql dists?
19:44:01
earl-ducaine
Style 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:57
jcowan
Returning 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:01
grawlinson
managed to grab a tarball of html-encode, but it's not ideal relying on quicklisp :(
19:54:57
earl-ducaine
jcowan: 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:07
jcowan
The 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