[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[groff] 11/13: doc/groff.texi (Requests and Macros): Generalize.
From: |
G. Branden Robinson |
Subject: |
[groff] 11/13: doc/groff.texi (Requests and Macros): Generalize. |
Date: |
Sat, 5 Dec 2020 02:20:39 -0500 (EST) |
gbranden pushed a commit to branch master
in repository groff.
commit a130c718d19047bc2ac3b27234466516273e44a1
Author: G. Branden Robinson <g.branden.robinson@gmail.com>
AuthorDate: Fri Dec 4 14:31:40 2020 +1100
doc/groff.texi (Requests and Macros): Generalize.
Remove "mutually" qualifier; a macro can also be self-recursive. It
should be okay to permit the imaginative reader to infer support for
mutually recursive macros.
---
doc/groff.texi | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/doc/groff.texi b/doc/groff.texi
index 80a4716..5fc967b 100644
--- a/doc/groff.texi
+++ b/doc/groff.texi
@@ -4846,10 +4846,10 @@ the body of a macro definition is not (completely)
interpreted, but
stored instead (@pxref{Copy Mode}). While a macro is being defined,
requests are not interpreted and macros not interpolated, whereas some
commonly used escape sequences @emph{are} interpolated. @code{roff}
-systems also support mutually recursive macros---as long as you have a
-way to break the recursion (@pxref{Conditionals and Loops}). For
-maintainable @code{roff} documents, arrange your macro definitions so
-that they are most easily understood when read from beginning to end.
+systems also support recursive macros---as long as you have a way to
+break the recursion (@pxref{Conditionals and Loops}). For maintainable
+@code{roff} documents, arrange your macro definitions so that they are
+most easily understood when read from beginning to end.
@c ---------------------------------------------------------------------
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [groff] 11/13: doc/groff.texi (Requests and Macros): Generalize.,
G. Branden Robinson <=