From: martin rudalics <rudalics@gmx.at>
To: David Kastrup <dak@gnu.org>
Cc: "Mark A. Hershberger" <mah@everybody.org>,
Dan Nicolaescu <dann@ics.uci.edu>,
emacs-devel@gnu.org
Subject: Re: What happened to (defun x)?
Date: Sat, 24 Nov 2007 23:48:01 +0100 [thread overview]
Message-ID: <4748AA21.9090807@gmx.at> (raw)
In-Reply-To: <85bq9juwuf.fsf_-_@lola.goethe.zz>
> I might have missed the discussion: pre-22 we had considered having
> (defun nxml-define-char-name-set)
> be a byte-compiler silencer in the same manner as
> (defvar preview-version)
> is a byte-compiler silencer. The obvious advantage over
> "declare-function" is that one does not need to remember another idiom
> and name.
>
> Is there a particular advantage for a separate declare-function that I
> just am not able to see?
It's a question of strong vs weak type-checking. The advantage of
strong type-checking is to catch errors sooner - in the special case
because a particular file fails to define a declared function. Its
disadvantage is that you can no more move a defun to another file
without finding and changing all files that have a declaration for it.
next prev parent reply other threads:[~2007-11-24 22:48 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-23 7:06 initial nxml merge Mark A. Hershberger
2007-11-23 12:56 ` Vinicius Jose Latorre
2007-11-23 16:32 ` Mark A. Hershberger
2007-11-23 18:27 ` Romain Francoise
2007-11-23 18:59 ` Stefan Monnier
2007-11-23 19:40 ` Mark A. Hershberger
2007-11-23 19:59 ` David Kastrup
2007-11-23 20:00 ` Glenn Morris
2007-11-24 3:13 ` Richard Stallman
2007-11-24 15:25 ` David Kastrup
2007-11-25 3:42 ` Richard Stallman
2007-11-24 21:44 ` Dan Nicolaescu
2007-11-24 22:01 ` What happened to (defun x)? (was: initial nxml merge) David Kastrup
2007-11-24 22:48 ` martin rudalics [this message]
2007-11-24 22:51 ` What happened to (defun x)? David Kastrup
2007-11-24 23:11 ` martin rudalics
2007-11-24 23:06 ` Dan Nicolaescu
2007-11-24 23:44 ` Jay Belanger
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=4748AA21.9090807@gmx.at \
--to=rudalics@gmx.at \
--cc=dak@gnu.org \
--cc=dann@ics.uci.edu \
--cc=emacs-devel@gnu.org \
--cc=mah@everybody.org \
/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).