From 850ba56f1da3f2f8033e6f9ac4082cc1a1a2aaef Mon Sep 17 00:00:00 2001 From: "H. Peter Anvin" Date: Wed, 15 Oct 2008 16:14:39 -0700 Subject: [PATCH] doc: minor editorial change Use the terms "defined" and "expanded" for single-line macros more consistently. Signed-off-by: H. Peter Anvin --- doc/nasmdoc.src | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/doc/nasmdoc.src b/doc/nasmdoc.src index 8d03cf3..1f4d8e5 100644 --- a/doc/nasmdoc.src +++ b/doc/nasmdoc.src @@ -1983,10 +1983,10 @@ the NASM command line: see \k{opt-d}. \S{xdefine} Resolving \c{%define}: \I\c{%ixdefine}\i\c{%xdefine} To have a reference to an embedded single-line macro resolved at the -time that it is embedded, as opposed to when the calling macro is -expanded, you need a different mechanism to the one offered by -\c{%define}. The solution is to use \c{%xdefine}, or it's -\I{case sensitive}case-insensitive counterpart \c{%ixdefine}. +time that the embedding macro is \e{defined}, as opposed to when the +embedding macro is \e{expanded}, you need a different mechanism to the +one offered by \c{%define}. The solution is to use \c{%xdefine}, or +it's \I{case sensitive}case-insensitive counterpart \c{%ixdefine}. Suppose you have the following code: -- 2.7.4