~ chicken-core (chicken-5) afa0977c3aa00910af8bf8d2627151181cecde1c

commit afa0977c3aa00910af8bf8d2627151181cecde1c
Author:     felix <felix@call-with-current-continuation.org>
AuthorDate: Wed Jul 13 17:01:24 2011 +0200
Commit:     felix <felix@call-with-current-continuation.org>
CommitDate: Wed Jul 13 17:01:24 2011 +0200

    undocumented use of raw lambdas in places where transformer procedures are used

diff --git a/manual/Macros b/manual/Macros
index d4ee169c..321e5d3d 100644
--- a/manual/Macros
+++ b/manual/Macros
@@ -76,13 +76,13 @@ where symbols have all context-information removed.
 
 The low-level macro facility that CHICKEN provides is called "explicit
 renaming" and allows writing hygienic or non-hygienic macros
-procedurally.  When given a lambda-expression or the return value of
-the procedure {{er-macro-transformer}} (to be preferred for
-portability reasons) instead of a {{syntax-rules}} form,
-{{define-syntax}} evaluates the procedure in a distinct expansion
-environment (initially having access to the exported identifiers of
-the {{scheme}} module). The procedure takes an expression and two
-other arguments and returns a transformed expression.
+procedurally.  When given a the return value of the one of the
+procedures {{er-macro-transformer}} or {{ir-macro-transformer}}
+instead of a {{syntax-rules}} form, {{define-syntax}} evaluates the
+procedure in a distinct expansion environment (initially having access
+to the exported identifiers of the {{scheme}} module). The procedure
+takes an expression and two other arguments and returns a transformed
+expression.
 
 For example, the transformation procedure for a {{call}} macro such
 that {{(call proc arg ...)}} expands into {{(proc arg ...)}} can be