Re: DEFU* macro name for a extern DEFUN: DEFUE? DEFUNEX?

[Paul Eggert]

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.