DEFINE-FUNCTION-NAME-SYNTAX for CAS is not strict enough

Bug #1095483 reported by Douglas Katzman
6
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-abbreviated name):
  0: [ABORT] Exit debugger, returning to top level.

(SB-INT:LEGAL-FUN-NAME-OR-TYPE-ERROR (SETF (FOO)))

Tags: runtime
Paul Khuong (pvk)
Changed in sbcl:
status: New → Confirmed
importance: Undecided → Medium
tags: added: runtime
Douglas Katzman (dougk)
Changed in sbcl:
status: Confirmed → Fix Committed
Changed in sbcl:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.