Search
11:07:04
stassats
can we have some other mechanism for readable strings? instead of read-eval
11:07:23
stassats
although i fully expect "hey, why did you usurp my reader macro?!" anyway
11:10:22
stassats
~ is not used in Common Lisp, and reserved to implementors.
11:25:24
Xof
This is only an issue in a sb-unicode build, right?
11:26:02
stassats
as always, somebody is probably already using it
11:27:17
Xof
I think it would be hilarious to use ~ and see what breaks
11:37:43
Xof
or „“ - surely no-one uses that?
11:44:16
Shinmera
While we're exploring Unicode, there's also 「」
11:44:48
jackdaniel
or ® (for implementer-reserved)
11:46:17
flip214
λ might already be used... how about ¨ or ΅ ?
13:31:26
jdz
Xof: „” are "proper" Latvian quotation marks («» are the alternative "official" ones).
13:32:09
jdz
Pretty sure MS Office does not use them for the "smart quotes" feature, so no problem.
16:20:50
dougk_
stassats: Xof: joking aside, perhaps #"string" would do ?
16:21:48
stassats
we should research what other implementations do to minimize the number of usurped macro characters
16:21:49
dougk_
is it not? I don't know if the rest of the # dispatch macro space is reserved
16:22:55
stassats
there's no explicit wording like with ~
16:23:52
Bike
2.4.8 has a list of # sub-macros and lists some of them as reserved for users, and #" isn't reserved for users
16:24:16
stassats
users are sneaky and don't care about that stuff
16:25:46
stassats
#S(base-setring "Abc")
16:31:28
stassats
ecl: (write (make-array 10 :element-type 'fixnum) :readably t) => #A(EXT:INTEGER64 (10) (0 1 39 39 94558646378856 8391102643395586095 3418359013798015841 7810197433147747689 7507329520638452271 27988498760887397))
16:32:27
stassats
that might be a good idea, actually
16:33:08
stassats
i think the best so far
16:44:38
Xof
extending #A seems like a reasonable plan