# HG changeset patch
# User lost@l-w.ca
# Date 1301984237 21600
# Node ID fd1ecc5d6e699d181d57c4a3768b418e8ad36998
# Parent  f55650f5e9b8f1cab9bad2c1eca2ecc951c26d43
Added mention of NOEXPAND macro argument in manual

diff -r f55650f5e9b8 -r fd1ecc5d6e69 docs/manual.docbook.sgml
--- a/docs/manual.docbook.sgml	Tue Apr 05 00:12:58 2011 -0600
+++ b/docs/manual.docbook.sgml	Tue Apr 05 00:17:17 2011 -0600
@@ -1093,7 +1093,7 @@
 
 <variablelist>
 <varlistentry>
-<term><parameter>macroname</parameter> MACRO</term>
+<term><parameter>macroname</parameter> MACRO [NOEXPAND]</term>
 <listitem>
 <para>This directive is used to being the definition of a macro called
 <parameter>macroname</parameter>. If <parameter>macroname</parameter> already
@@ -1101,6 +1101,17 @@
 macro is undefined. It may work and it may not so the behaviour should not
 be relied upon.
 </para>
+
+<para>If NOEXPAND is specified, the macro will not be expanded in a program
+listing. Instead, all bytes emitted by all instructions within the macro
+will appear to be emitted on the line where the macro is invoked, starting
+at the address of the line of the invokation. If the macro uses ORG or other
+directives that define symbols or change the assembly address, these things
+will also be hidden (except in the symbol table) and the output bytes will
+appear with incorrect address attribution. Thus, NOEXPAND should only be
+used for macros that do not mess with the assembly address or otherwise
+define symbols that should be visible.</para>
+
 </listitem>
 </varlistentry>