GNU bug report logs -
#7319
`defsetf' methods of `extent-*' in emacs-lisp/cl-macs.el
Previous Next
Reported by: MON KEY <monkey <at> sandpframing.com>
Date: Tue, 2 Nov 2010 20:34:01 UTC
Severity: minor
Done: Stefan Monnier <monnier <at> iro.umontreal.ca>
Bug is archived. No further changes may be made.
Full log
View this message in rfc822 format
[Message part 1 (text/plain, inline)]
Your message dated Mon, 08 Nov 2010 14:09:45 -0500
with message-id <jwv1v6vskw4.fsf-monnier+emacs <at> gnu.org>
and subject line Re: bug#7319: `defsetf' methods of `extent-*' in emacs-lisp/cl-macs.el
has caused the GNU bug report #7319,
regarding `defsetf' methods of `extent-*' in emacs-lisp/cl-macs.el
to be marked as done.
(If you believe you have received this mail in error, please contact
help-debbugs <at> gnu.org.)
--
7319: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=7319
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems
[Message part 2 (message/rfc822, inline)]
Current through bzr-102222
emacs-lisp/cl-macs.el has `defsetf' methods for:
`extent-data', `extent-face', `extent-priority',
`extent-end-position', `extent-start-position'
AFAICT GNU Emacs deosn't define the corresponding operators:
`set-extent-data', `set-extent-face',
`set-extent-priority', `set-extent-endpoints'
GNU Emacs doesn't even support the majority of cl*.el functions at
runtime (let alone setf methods for many core procedures) so why does
it make an attempt tos upport CL related functions for an alien
application's incompatible lisp featureset?
emacs -Q
(defun bubba (x)
(eval-when-compile (require 'cl))
x)
M-x compile-defun
(symbol-plist 'extent-data)
(symbol-plist 'extent-face)
(symbol-plist 'extent-priority)
(symbol-plist 'extent-end-position)
(symbol-plist 'extent-start-position)
Is this another example of CL polluting the "global names"?
:P
--
/s_P\
[Message part 3 (message/rfc822, inline)]
> emacs-lisp/cl-macs.el has `defsetf' methods for:
> `extent-data', `extent-face', `extent-priority',
> `extent-end-position', `extent-start-position'
Funny, eh?
It's most likely the result of CL supporting both Emacs and XEmacs.
Of course, nowadays the Emacs and XEmacs versions aren't kept in sync
any more, so we could get rid of it, although they don't cause any
harm, AFAICT.
Stefan
This bug report was last modified 14 years and 198 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.