From: Paul Eggert <eggert@cs.ucla.edu>
To: Chong Yidong <cyd@stupidchicken.com>
Cc: Emacs-Devel devel <emacs-devel@gnu.org>
Subject: Re: DEFU* macro name for a extern DEFUN: DEFUE? DEFUNEX?
Date: Mon, 11 Apr 2011 18:35:44 -0700 [thread overview]
Message-ID: <4DA3AC70.6070609@cs.ucla.edu> (raw)
In-Reply-To: <87hba4tnx8.fsf@stupidchicken.com>
On 04/11/2011 03:37 PM, Chong Yidong wrote:
> there isn't sufficient justification to replace DEFUNS throughout the tree
Hmm, well, now that I've gotten used to it, I would like for it
to continue to be easy to tell, when I'm reading the code, which
DEFUNs are called by other C modules.
How about this idea instead? It would not replace any DEFUNs.
We put the line "static" in front of functions that are not exported.
For example:
static
DEFUN ("subrp", Fsubrp, Ssubrp, 1, 1, 0,
doc: /* Return t if OBJECT is a built-in function. */)
(Lisp_Object object)
{
if (SUBRP (object))
return Qt;
return Qnil;
}
This works too. Would it be OK? Other solutions are possible,
but this is the simplest I can think of, and it would be easy
for me to do.
next prev parent reply other threads:[~2011-04-12 1:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-11 5:47 DEFU* macro name for a extern DEFUN: DEFUE? DEFUNEX? Paul Eggert
2011-04-11 6:27 ` Dan Nicolaescu
2011-04-11 6:37 ` Paul Eggert
2011-04-11 10:39 ` Juanma Barranquero
2011-04-11 16:49 ` Paul Eggert
2011-04-11 14:34 ` Jason Rumney
2011-04-11 22:37 ` Chong Yidong
2011-04-12 1:35 ` Paul Eggert [this message]
2011-04-14 23:52 ` checking static vs extern symbols Paul Eggert
2011-04-15 8:23 ` Eli Zaretskii
2011-04-15 1:15 ` DEFU* macro name for a extern DEFUN: DEFUE? DEFUNEX? Stefan Monnier
2011-04-12 3:34 ` Stefan Monnier
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4DA3AC70.6070609@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=cyd@stupidchicken.com \
--cc=emacs-devel@gnu.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.