From: Mattias Engdegård <mattiase@acm.org>
Date: Tue, 17 Jun 2025 08:37:14 +0000 (+0200)
Subject: * doc/lispref/functions.texi (Closures): Rewrite outdated text.
X-Git-Url: http://git.eshelyaron.com/gitweb/?a=commitdiff_plain;h=e94ca804e60e89ef7de16e257f56fc0ed4d418f4;p=emacs.git

* doc/lispref/functions.texi (Closures): Rewrite outdated text.

(cherry picked from commit eca2cc00b6688c5fde11c1ae23b0123966008938)
---

diff --git a/doc/lispref/functions.texi b/doc/lispref/functions.texi
index b4764a6de15..90ca1724054 100644
--- a/doc/lispref/functions.texi
+++ b/doc/lispref/functions.texi
@@ -1621,22 +1621,15 @@ same way as ordinary functions.
 
   @xref{Lexical Binding}, for an example of using a closure.
 
-  Currently, an Emacs Lisp closure object is represented by a list
-with the symbol @code{closure} as the first element, a list
-representing the lexical environment as the second element, and the
-argument list and body forms as the remaining elements:
-
 @example
 ;; @r{lexical binding is enabled.}
 (lambda (x) (* x x))
      @result{} #f(lambda (x) [t] (* x x))
 @end example
 
-@noindent
-However, the fact that the internal structure of a closure is
-exposed to the rest of the Lisp world is considered an internal
-implementation detail.  For this reason, we recommend against directly
-examining or altering the structure of closure objects.
+  The internal structure of a closure is an implementation matter and we
+recommend against examining or altering it directly.  For the curious,
+@pxref{Closure Objects}.
 
 @node OClosures
 @section Open Closures