unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Magne Ingebrigtsen <larsi@gnus.org>
To: "Drew Adams" <drew.adams@oracle.com>
Cc: 8690@debbugs.gnu.org
Subject: bug#8690: 24.0.50; `declare' doc; conflict with cl-macs.el
Date: Fri, 01 Jul 2011 12:29:20 +0200	[thread overview]
Message-ID: <m3liwii9a7.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <98E51A77662843EDB8887B68CC9828DF@us.oracle.com> (Drew Adams's message of "Wed, 18 May 2011 08:58:26 -0700")

"Drew Adams" <drew.adams@oracle.com> writes:

> Something should be done about this.  Perhaps rename the cl form to
> avoid the conflict?  Dunno.  But we shouldn't be getting into this kind
> of conflict/confusion.  Unless the two are truly compatible, in which
> case we should add the same doc string to the macro in cl-macs.el.

The subr.el definition of `declare' is:

(defmacro declare (&rest _specs)
  "Do not evaluate any arguments and return nil.
Treated as a declaration when used at the right place in a
`defmacro' form.  \(See Info anchor `(elisp)Definition of declare'.)"
  nil)

The cl-macs.el definition is:
  
(defmacro declare (&rest specs)
  (if (cl-compiling-file)
      (while specs
	(if (listp cl-declare-stack) (push (car specs) cl-declare-stack))
	(cl-do-proclaim (pop specs) nil)))
  nil)

So the cl-macs.el version extends the macro, but it's just nil, anyway.

So perhaps the fix here is just to copy over the doc string from the
subr.el version to the cl-macs.el version?
  
-- 
(domestic pets only, the antidote for overdose, milk.)
  bloggy blog http://lars.ingebrigtsen.no/





  reply	other threads:[~2011-07-01 10:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-18 15:58 bug#8690: 24.0.50; `declare' doc; conflict with cl-macs.el Drew Adams
2011-07-01 10:29 ` Lars Magne Ingebrigtsen [this message]
2011-07-15 13:47   ` Lars Magne Ingebrigtsen
2011-07-15 14:53     ` Drew Adams
2011-07-15 15:00       ` Lars Magne Ingebrigtsen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=m3liwii9a7.fsf@quimbies.gnus.org \
    --to=larsi@gnus.org \
    --cc=8690@debbugs.gnu.org \
    --cc=drew.adams@oracle.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).