From: Stefan Kangas <stefankangas@gmail.com>
Date: Sun, 19 Jan 2025 11:44:05 +0000 (+0100)
Subject: Document use of calln in C code in internals.texi
X-Git-Url: http://git.eshelyaron.com/gitweb/?a=commitdiff_plain;h=0b1ad96b1a79bb80970db621e7c7a13da3ddf5c1;p=emacs.git

Document use of calln in C code in internals.texi

* doc/lispref/internals.texi
(Writing Emacs Primitives): Don't recommend `call0`, `call1`, etc.
Instead recommend `calln`, which covers all of those use cases.

(cherry picked from commit 7362f9f75d5aca1c97f920531dd62763918ba5fe)
---

diff --git a/doc/lispref/internals.texi b/doc/lispref/internals.texi
index 3703c6087f7..ff09e0aca1c 100644
--- a/doc/lispref/internals.texi
+++ b/doc/lispref/internals.texi
@@ -1154,9 +1154,9 @@ one-dimensional array containing their values.  The first Lisp-level
 argument is the Lisp function to call, and the rest are the arguments to
 pass to it.
 
-  The C functions @code{call0}, @code{call1}, @code{call2}, and so on,
-provide handy ways to call a Lisp function conveniently with a fixed
-number of arguments.  They work by calling @code{Ffuncall}.
+  The C macro @code{calln} is a convenient way to call a Lisp function
+without having to specify the number of arguments.  It works by calling
+@code{Ffuncall}.
 
   @file{eval.c} is a very good file to look through for examples;
 @file{lisp.h} contains the definitions for some important macros and