sb-int:bug from broken backquote forms
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
SBCL |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
```((,,@1))
errors with:
debugger invoked on a SB-INT:BUG in thread #<THREAD "initial thread" RUNNING
(A SB-INT:BUG was caught when trying to print *DEBUG-CONDITION* when entering
the debugger. Printing was aborted and the SB-INT:BUG was stored in
SB-DEBUG:
...
0: (SB-INT:BUG #<error printing object>)
1: (SB-IMPL:
2: (SB-IMPL:
3: (SB-IMPL:
4: (SB-PRETTY:
5: (SB-PRETTY:
6: (PRIN1 #<error printing object>)
7: (SB-IMPL::REPL-FUN NIL)
```((,',@1))
errors with the more readable:
debugger invoked on a SB-INT:BUG in thread #<THREAD "initial thread" RUNNING
found illegal dotted backquote form: (QUOTE . 1)
This is probably a bug in SBCL itself. (Alternatively, SBCL might have been
corrupted by bad user code, e.g. by an undefined Lisp operation like
(FMAKUNBOUND 'COMPILE), or by stray pointers from alien code or from unsafe
Lisp code; or there might be a bug in the OS or hardware that SBCL is running
on.) If it seems to be a bug in SBCL itself, the maintainers would like to
know about it. Bug reports are welcome on the SBCL mailing lists, which you
can find at <http://
...
0: (SB-INT:BUG "found illegal dotted backquote form: ~S" (QUOTE . 1))
1: (SB-IMPL:
2: (SB-IMPL:
3: (SB-IMPL:
4: (SB-IMPL:
5: (SB-PRETTY:
6: (SB-PRETTY:
7: (PRIN1 #<error printing object>)
8: (SB-IMPL::REPL-FUN NIL)
expected: PRINTable error message about trying to splice something that isn't a list
tested on 1.0.47.1, x8664 linux
Changed in sbcl: | |
assignee: | nobody → Nikodemus Siivola (nikodemus) |
status: | New → In Progress |
Changed in sbcl: | |
status: | Fix Committed → Fix Released |
Looking further, `(,@1) evaluates to 1 and `(1 ,@2) evaluates to (1 . 2), which don't seem conformant, if i'm looking at the right part of clhs 2.4.6.
`(,@1 2) errors with "The value 1 is not of type LIST." as expected.