[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
master 6e628ff99c: * doc/lispref/functions.texi (What Is a Function): Im
From: |
Stefan Monnier |
Subject: |
master 6e628ff99c: * doc/lispref/functions.texi (What Is a Function): Improve further |
Date: |
Mon, 15 Aug 2022 18:46:02 -0400 (EDT) |
branch: master
commit 6e628ff99c3b55a74f3f34aed232ce8a1746aa27
Author: Stefan Monnier <monnier@iro.umontreal.ca>
Commit: Stefan Monnier <monnier@iro.umontreal.ca>
* doc/lispref/functions.texi (What Is a Function): Improve further
---
doc/lispref/functions.texi | 10 ++++++----
1 file changed, 6 insertions(+), 4 deletions(-)
diff --git a/doc/lispref/functions.texi b/doc/lispref/functions.texi
index ddf7cff6c2..983dfe2ec5 100644
--- a/doc/lispref/functions.texi
+++ b/doc/lispref/functions.texi
@@ -219,10 +219,12 @@ function. For example:
@defun compiled-function-p object
This function returns @code{t} if @var{object} is a function object
-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}).
+that is not in the form of ELisp source code but something like
+machine code or byte code instead. More specifically it returns
+@code{t} if the function is 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
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- master 6e628ff99c: * doc/lispref/functions.texi (What Is a Function): Improve further,
Stefan Monnier <=