I thought cluser:foobar would cause an error when being read into Scheme
No, colon is a perfectly cromulent symbol character in Scheme with no special meaning. When Scheme forked from Maclisp, there were no packages yet, so colon wasn't special.
Yes, only in code.
Serializing CL code is what I was saying was too big an effort, and we shouldn't go there. It would have to handle conditional exclusions (#+ and #-) and comments and all kinds of nasty ugly things. Anything used only in code (in practice) doesn't belong here.
>> Ah, ok. I'll wait for your #name syntax before evaluating the #u8"".
>
> I talked about this above and you LGTMed it. The format is # followed by
> name or hexcode, followed by list, string, or bytevector.
I missed that, unless you somehow mean the bytevector syntax.
Examples: #ratio(11 10), #date"2019-11-11", #bits[07-EE80] = CL #*111011101, where the 07 means that the last 7 bits of the last byte are not part of the bitvector. I really don't want #bits#u8"07EE00" just to avoid square brackets; it's a human readability fail.
John Cowan
http://vrici.lojban.org/~cowan xxxxxx@ccil.orgAnd it was said that ever after, if any man looked in that Stone,
unless he had a great strength of will to turn it to other purpose,
he saw only two aged hands withering in flame. --"The Pyre of Denethor"