Re: master 48ac40e60e: ; Fix last change.

[Stefan Monnier]

Eli Zaretskii [2022-08-14 13:51:34] wrote:
> diff --git a/doc/lispref/functions.texi b/doc/lispref/functions.texi
> index 8c6328b440..e140998d65 100644
> --- a/doc/lispref/functions.texi
> +++ b/doc/lispref/functions.texi
> @@ -219,8 +219,10 @@ function.  For example:
>  
>  @defun compiled-function-p object
>  This function returns @code{t} if @var{object} is a function object
> -that was either byte-compiled (@pxref{Byte Compilation}) or
> -natively-compiled (@pxref{Native Compilation}).
> +that was either built-in (a.k.a.@: ``primitive'', @pxref{What is a
> +Function}), or byte-compiled (@pxref{Byte Compilation}), or
> +natively-compiled (@pxref{Native Compilation}), or a function loaded
> +from a dynamic module (@pxref{Dynamic Modules}).
>  @end defun
>  
>  @defun subr-arity subr
> diff --git a/etc/NEWS b/etc/NEWS
> index 0788b94da2..c982684d3a 100644
> --- a/etc/NEWS
> +++ b/etc/NEWS
> @@ -2573,8 +2573,9 @@ patcomp.el, pc-mode.el, pc-select.el, s-region.el, and 
> sregex.el.
>  
>  +++
>  ** New function 'compiled-function-p'.
> -This returns non-nil if its argument is either a byte-compiled or a
> -natively-compiled function object.
> +This returns non-nil if its argument is either a built-in, or a
> +byte-compiled, or a natively-compiled function object, or a function
> +loaded from a dynamic module.

Funny: I find this rather hard to understand compared to my
original wording.  E.g. a reader might wonder what other cases there
could be and why they don't return non-nil.

IOW, I prefer an "intentional" description over the "extensional" one
you installed.  E.g. it's more useful when faced with a new
function type.


        Stefan