Skip to content

Commit

Permalink
Minor rewording to reduce multiple uses of "execution" in macro discu…
Browse files Browse the repository at this point in the history
…ssion.
  • Loading branch information
Tim Burks committed Dec 29, 2008
1 parent 008fda4 commit bceca31
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions pages/operators/body.txt
Original file line number Diff line number Diff line change
Expand Up @@ -344,12 +344,12 @@ It expects three arguments: the macro name, the argument list, and the
body of the macro.

A macro is executed in two phases. The first phase is *macro-expansion*.
During macro-expansion, the body of the macro is executed using the values
During macro-expansion, the body of the macro is evaluated using the values
passed into the macro via its argument list. Any symbols in the calling
context that have the same name as the macro arguments are temporarily
masked until the expansion is complete.

Once the macro-expansion phase is complete, the execution phase takes place,
Once the macro-expansion phase is complete, the *execution* phase takes place,
where the macro-expanded code is executed in the caller's context.

Here's a simple example of a macro that increments a variable in-place:
Expand Down

0 comments on commit bceca31

Please sign in to comment.