summaryrefslogtreecommitdiff
path: root/Lisp/conditions.lisp
diff options
context:
space:
mode:
authorMatthias Benkard <code@mail.matthias.benkard.de>2007-10-10 14:02:36 +0200
committerMatthias Benkard <code@mail.matthias.benkard.de>2007-10-10 14:02:36 +0200
commit5b0be258009220af661ba877b17c3ebf33972409 (patch)
treef4c0d6c3744473d009d258927d5484edb1a99328 /Lisp/conditions.lisp
parentf71611e1995b2645a183a52e221fccfcca64d2e0 (diff)
FIND-SELECTOR: Make ERRORP default to T.
darcs-hash:629ac814cc7f7427b1b1cbe71448a670c37c0171
Diffstat (limited to 'Lisp/conditions.lisp')
-rw-r--r--Lisp/conditions.lisp9
1 files changed, 2 insertions, 7 deletions
diff --git a/Lisp/conditions.lisp b/Lisp/conditions.lisp
index de65b2b..5080ea3 100644
--- a/Lisp/conditions.lisp
+++ b/Lisp/conditions.lisp
@@ -45,11 +45,7 @@
A **condition** of **type** __no-such-selector__ is **signal**led when
an attempt is made to retrieve a method selector by name, and that
selector cannot be found. This is most often the case when a typo is
-made in the message name part of a method invocation.
-
-Note that this error will, at present, never be signalled on Mac OS X,
-because __find-selector__ automatically interns selectors on that
-system. This behaviour is subject to change."))
+made in the message name part of a method invocation."))
(define-condition message-not-understood (error)
@@ -74,5 +70,4 @@ method. This is most often the case when an object is used at a place
that expects an object of a different Objective-C type (that is, it can
be regarded as a kind of type error), although it can also happen when a
typo is made in the message name part of a method invocation and a
-__no-such-selector__ error is not **signal**led (on Mac OS X, for
-example)."))
+__no-such-selector__ error is not **signal**led."))