master 7362f9f75d5 1/3: Document use of calln in C code in internals.texi

[Stefan Kangas]

branch: master
commit 7362f9f75d5aca1c97f920531dd62763918ba5fe
Author: Stefan Kangas <stefankangas@gmail.com>
Commit: Stefan Kangas <stefankangas@gmail.com>

    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.
---
 doc/lispref/internals.texi | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

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