On Mon, Mar 15, 2010 at 11:28 AM, Leo <[email protected]> wrote:
> On 2010-03-14 00:46 +0000, Liam Healy wrote:
>> Fixed in
>> Head: 7c43742f8e - Upcase before interning in #'data-class-name
> [...]
>
> Thanks.
>
>>> 2. #m (1 2 3) fails too
>>> Other reader macros does not err when there's a space follows it, for
>>> example:
>>> - ' (1 2 3)
>>> - # (1 2 3)
I disagree; # does indeed fail on my SBCL
# (1 2 3)
debugger invoked on a SB-INT:SIMPLE-READER-ERROR in thread #<THREAD
"initial thread" RUNNING {10039ADBF1}>:
SB-INT:SIMPLE-READER-ERROR on #<SYNONYM-STREAM :SYMBOL
SB-SYS:*STDIN* {10001DA261}>:
illegal sharp macro character: #\
Type HELP for debugger help, or (SB-EXT:QUIT) to exit from SBCL.
restarts (invokable by number or by possibly-abbreviated name):
0: [ABORT] Exit debugger, returning to top level.
(SB-INT:SIMPLE-READER-ERROR
#<SYNONYM-STREAM :SYMBOL SB-SYS:*STDIN* {10001DA261}>
"illegal sharp macro character: ~S")[:EXTERNAL]
>>>
>>> This is a bit inconvenient because paredit.el automatically inserts a
>>> space behind m.
>
> Should this be fixed in paredit.el? thanks.
I'd say so.
>
> Leo
>
Liam
_______________________________________________
Gsll-devel mailing list
[email protected]
http://common-lisp.net/cgi-bin/mailman/listinfo/gsll-devel
