libera/#commonlisp - IRC Chatlog
Search
2:10:04
paulapatience
In other words, FDEFINITION can accept (SETF NAME)s and SYMBOL-FUNCTION can't?
7:55:35
Gleefre
beach: re conformance of the "" nickname for the KEYWORD package: I think I found a passage in the hyperspec that explicitely prohibits that.
9:12:49
Gleefre
Well, the reader algorithm does seem to say that it is going to be read as a token ":MUMBLE" which would be then parsed as a keyword, the same way as :mumble.
9:15:35
Gleefre
But, to be honest, I'd prefer to have a way to read symbols in the package named "" instead.
9:33:11
Gleefre
Found this old commit: https://github.com/sbcl/sbcl/commit/12478433c6f18424c5d98f3075e3b832ad2c6ee3
10:25:59
Gleefre
It seems that CMUCL has accidentally (back)ported this from SBCL [ this commit, it seems: https://gitlab.common-lisp.net/cmucl/cmucl/-/commit/4958e03bfa7d043768be3397f8ecac31dbe750ff ]
10:28:34
Gleefre
Oh, that's interesting, there is a comment about it in CCL's source code (but no commit history it seems): https://github.com/Clozure/ccl/blob/master/level-1/l1-reader.lisp#L2384-L2389
10:29:17
Gleefre
> MCL's reader has historically treated ||:foo as a reference to the symbol FOO in the package which has the null string as its name. Some other implementations treat it as a keyword.