From 462782af86a723cad40c505fe81a26046959f3a8 Mon Sep 17 00:00:00 2001
From: Andy Wingo <wingo@pobox.com>
Date: Thu, 19 Sep 2019 15:24:14 +0200
Subject: [PATCH] Add documentation for else, =>, _, ... aux syntax

* doc/ref/api-macros.texi (Syntax Rules): Document aux syntax.
---
 doc/ref/api-macros.texi | 20 ++++++++++++++++++++
 1 file changed, 20 insertions(+)

diff --git a/doc/ref/api-macros.texi b/doc/ref/api-macros.texi
index 2e0036932..83345a2f5 100644
--- a/doc/ref/api-macros.texi
+++ b/doc/ref/api-macros.texi
@@ -248,6 +248,26 @@ lawyers probably see the need here for use of @code{literal-identifier=?} rather
 than @code{free-identifier=?}, and would probably be correct. Patches
 accepted.}.
 
+@cindex auxiliary syntax
+@cindex syntax, auxiliary
+Although literals can be unbound, usually they are bound to allow them
+to be imported, exported, and renamed.  @xref{Modules}, for more
+information on imports and exports.  In Guile there are a few standard
+auxiliary syntax definitions, as specified by R6RS and R7RS:
+
+@deffn {Scheme Syntax} else
+@deffnx {Scheme Syntax} =>
+@deffnx {Scheme Syntax} _
+@deffnx {Scheme Syntax} ...
+Auxiliary syntax definitions.
+
+These are defined as if with a macro that never matches, e.g.:
+
+@example
+(define-syntax else (syntax-rules ()))
+@end example
+@end deffn
+
 If a pattern is not a list, vector, or an identifier, it matches as a literal,
 with @code{equal?}.