DEFINE-FUNCTION-NAME-SYNTAX for CAS is not strict enough
Bug #1095483 reported by
Douglas Katzman
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
SBCL |
Fix Released
|
Medium
|
Unassigned |
Bug Description
No check is made that the second element of the name is itself a valid name, leading to:
* (fboundp '(sb-ext:cas (foo)))
=> NIL
* (fboundp '(sb-ext:cas "garbage"))
=> NIL
Ideally it would signal the same condition as does this example:
* (fboundp '(setf (foo)))
debugger invoked on a SIMPLE-TYPE-ERROR: invalid function name: (SETF (FOO))
restarts (invokable by number or by possibly-
0: [ABORT] Exit debugger, returning to top level.
(SB-INT:
Changed in sbcl: | |
status: | New → Confirmed |
importance: | Undecided → Medium |
tags: | added: runtime |
Changed in sbcl: | |
status: | Confirmed → Fix Committed |
Changed in sbcl: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.