freenode/#lisp - IRC Chatlog
Search
0:53:42
Bike
{} and [] are reserved in the sense that the implementation can't use them. there's no restrictions on programmer users, library writers or not. named readtables is probably still a good idea tho.
1:24:33
aeth
You'd probably want #[...] and #{...} instead of just [...] and {...} to make it really clear that it's a reader macro
5:45:33
fiddlerwoaroof
Bike, I'm confusing two things, it's interesting that #{} and #[] aredescribed this way: "The combinations marked by an asterisk (*) are explicitly reserved to the user"
5:46:32
fiddlerwoaroof
While [] and {} are defined this way: "The characters marked with an asterisk (*) are initially constituents, but they are not used in any standard Common Lisp notations. These characters are explicitly reserved to the programmer."
5:47:47
fiddlerwoaroof
It seems to me that there's an attempt here to distinguish characters that end-users might define reader macros on from characters that non-end-user programmers might define reader macros on
5:48:19
fiddlerwoaroof
Of course, in retrospect, it seems to me that NAMED-READTABLES is the right solution to this sort of problems