1 @c PSPP - a program for statistical analysis.
2 @c Copyright (C) 2017, 2020 Free Software Foundation, Inc.
3 @c Permission is granted to copy, distribute and/or modify this document
4 @c under the terms of the GNU Free Documentation License, Version 1.3
5 @c or any later version published by the Free Software Foundation;
6 @c with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts.
7 @c A copy of the license is included in the section entitled "GNU
8 @c Free Documentation License".
11 @node Conditionals and Looping
12 @chapter Conditional and Looping Constructs
15 @cindex flow of control
18 This chapter documents @pspp{} commands used for conditional execution,
19 looping, and flow of control.
22 * BREAK:: Exit a loop.
23 * DEFINE:: Define a macro.
24 * DO IF:: Conditionally execute a block of code.
25 * DO REPEAT:: Textually repeat a code block.
26 * LOOP:: Repeat a block of code.
37 @cmd{BREAK} terminates execution of the innermost currently executing
40 @cmd{BREAK} is allowed only inside @cmd{LOOP}@dots{}@cmd{END LOOP}.
41 @xref{LOOP}, for more details.
52 @t{DEFINE} @i{macro_name}@t{(}@r{[}@i{argument}@r{[}@t{/}@i{argument}@r{]@dots{}]}@t{)}
53 @dots{}@i{body}@dots{}
58 Each @i{argument} takes the following form:
60 @r{@{}@i{!arg_name}@t{=} @math{|} @t{!POSITIONAL}@r{@}}
61 @r{[}@t{!DEFAULT(}@i{default}@t{)}@r{]}
62 @r{[}@t{!NOEXPAND}@r{]}
63 @r{@{}@t{!TOKENS(}@i{count}@t{)} @math{|} @t{!CHAREND('}@i{token}@t{')} @math{|} @t{!ENCLOSE('}@i{start}@t{' @math{|} '}@i{end}@t{')} @math{|} @t{!CMDEND}@}
67 The following directives may be used within @i{body}:
74 The following functions may be used within the body:
76 @t{!BLANKS(}@i{count}@t{)}
77 @t{!CONCAT(}@i{arg}@dots{}@t{)}
78 @t{!EVAL(}@i{arg}@t{)}
79 @t{!HEAD(}@i{arg}@t{)}
80 @t{!INDEX(}@i{haystack}@t{,} @i{needle}@t{)}
81 @t{!LENGTH(}@i{arg}@t{)}
83 @t{!QUOTE(}@i{arg}@t{)}
84 @t{!SUBSTR(}@i{arg}@t{,} @i{start}[@t{,} @i{count}]@t{)}
85 @t{!TAIL(}@i{arg}@t{)}
86 @t{!UNQUOTE(}@i{arg}@t{)}
87 @t{!UPCASE(}@i{arg}@t{)}
91 The body may also include the following constructs:
93 @t{!IF (}@i{condition}@t{) !THEN} @i{true-expansion} @t{!ENDIF}
94 @t{!IF (}@i{condition}@t{) !THEN} @i{true-expansion} @t{!ELSE} @i{false-expansion} @t{!ENDIF}
96 @t{!DO} @i{!var} @t{=} @i{start} @t{!TO} @i{end} [@t{!BY} @i{step}]
99 @t{!DO} @i{!var} @t{!IN} @t{(}@i{expression}@t{)}
103 @t{!LET} @i{!var} @t{=} @i{expression}
106 @node Macro Introduction
107 @subsection Introduction
109 The DEFINE command creates a @dfn{macro}, which is a name for a
110 fragment of PSPP syntax called the macro's @dfn{body}. Following the
111 DEFINE command, syntax may @dfn{call} the macro by name any number of
112 times. Each call substitutes, or @dfn{expands}, the macro's body in
113 place of the call, as if the body had been written in its place.
115 The following syntax defines a macro named @code{!vars} that expands
116 to the variable names @code{v1 v2 v3}. The macro's name begins with
117 @samp{!}, which is optional for macro names. The @code{()} following
118 the macro name are required:
126 Here are two ways that @code{!vars} might be called given the
127 preceding definition:
131 FREQUENCIES /VARIABLES=!vars.
134 With macro expansion, the above calls are equivalent to the following:
137 DESCRIPTIVES v1 v2 v3.
138 FREQUENCIES /VARIABLES=v1 v2 v3.
141 The @code{!vars} macro expands to a fixed body. Macros may have more
142 sophisticated contents:
146 Macro @dfn{arguments} that are substituted into the body whenever they
147 are named. The values of a macro's arguments are specified each time
148 it is called. @xref{Macro Arguments}.
151 Macro @dfn{functions}, expanded when the macro is called. @xref{Macro
155 @code{!IF} constructs, for conditional expansion. @xref{Macro
156 Conditional Expansion}.
159 Two forms of @code{!DO} construct, for looping over a numerical range
160 or a collection of tokens. @xref{Macro Loops}.
163 @code{!LET} constructs, for assigning to macro variables. @xref{Macro
164 Variable Assignment}.
167 Many identifiers associated with macros begin with @samp{!}, a
168 character not normally allowed in identifiers. These identifiers are
169 reserved only for use with macros, which helps keep them from being
170 confused with other kinds of identifiers.
172 The following sections provide more details on macro syntax and
176 @subsection Macro Bodies
178 As previously shown, a macro body may contain a fragment of a PSPP
179 command (such as a variable name). A macro body may also contain full
180 PSPP commands. In the latter case, the macro body should also contain
181 the command terminators.
183 Most PSPP commands may occur within a macro. The @code{DEFINE}
184 command itself is one exception, because the inner @code{!ENDDEFINE}
185 ends the outer macro definition. For compatibility, @code{BEGIN
186 DATA}@dots{}@code{END DATA.} should not be used within a macro.
188 The body of a macro may call another macro. The following shows one
194 FREQUENCIES /VARIABLES=!vars.
197 DEFINE !vars() v1 v2 v3 !ENDDEFINE.
200 * We can redefine the variables macro to analyze different variables:
201 DEFINE !vars() v4 v5 !ENDDEFINE.
205 The @code{!commands} macro would be easier to use if it took the
206 variables to analyze as an argument rather than through another macro.
207 The following section shows how to do that.
209 @node Macro Arguments
210 @subsection Macro Arguments
212 This section explains how to use macro arguments. As an initial
213 example, the following syntax defines a macro named @code{!analyze}
214 that takes all the syntax up to the first command terminator as an
218 DEFINE !analyze(!POSITIONAL !CMDEND)
220 FREQUENCIES /VARIABLES=!1.
224 @noindent When @code{!analyze} is called, it expands to a pair of analysis
225 commands with each @code{!1} in the body replaced by the argument.
226 That is, these calls:
233 @noindent act like the following:
236 DESCRIPTIVES v1 v2 v3.
237 FREQUENCIES /VARIABLES=v1 v2 v3.
239 FREQUENCIES /VARIABLES=v4 v5.
242 Macros may take any number of arguments, described within the
243 parentheses in the DEFINE command. Arguments come in two varieties
244 based on how their values are specified when the macro is called:
248 A @dfn{positional} argument has a required value that follows the
249 macro's name. Use the @code{!POSITIONAL} keyword to declare a
252 When a macro is called, the positional argument values appear in the
253 same order as their definitions, before any keyword argument values.
255 References to a positional argument in a macro body are numbered:
256 @code{!1} is the first positional argument, @code{!2} the second, and
257 so on. In addition, @code{!*} expands to all of the positional
258 arguments' values, separated by spaces.
260 The following example uses a positional argument:
263 DEFINE !analyze(!POSITIONAL !CMDEND)
265 FREQUENCIES /VARIABLES=!1.
273 A @dfn{keyword} argument has a name. In the macro call, its value is
274 specified with the syntax @code{@i{name}=@i{value}}. The names allow
275 keyword argument values to take any order in the call.
277 In declaration and calls, a keyword argument's name may not begin with
278 @samp{!}, but references to it in the macro body do start with a
281 The following example uses a keyword argument that defaults to ALL if
282 the argument is not assigned a value:
285 DEFINE !analyze_kw(vars=!DEFAULT(ALL) !CMDEND)
287 FREQUENCIES /VARIABLES=!vars.
290 !analyze_kw vars=v1 v2 v3. /* Analyze specified variables.
291 !analyze_kw. /* Analyze all variables.
295 If a macro has both positional and keyword arguments, then the
296 positional arguments must come first in the DEFINE command, and their
297 values also come first in macro calls. A keyword argument may be
298 omitted by leaving its keyword out of the call, and a positional
299 argument may be omitted by putting a command terminator where it would
300 appear. (The latter case also omits any following positional
301 arguments and all keyword arguments, if there are any.) When an
302 argument is omitted, a default value is used: either the value
303 specified in @code{!DEFAULT(@i{value})}, or an empty value otherwise.
305 Each argument declaration specifies the form of its value:
308 @item !TOKENS(@i{count})
309 Exactly @var{count} tokens, e.g.@: @code{!TOKENS(1)} for a single
310 token. Each identifier, number, quoted string, operator, or
311 punctuator is a token. @xref{Tokens}, for a complete definition.
313 The following variant of @code{!analyze_kw} accepts only a single
314 variable name (or @code{ALL}) as its argument:
317 DEFINE !analyze_one_var(!POSITIONAL !TOKENS(1))
319 FREQUENCIES /VARIABLES=!1.
325 @item !CHAREND('@var{token}')
326 Any number of tokens up to @var{token}, which should be an operator or
327 punctuator token such as @samp{/} or @samp{+}. The @var{token} does
328 not become part of the value.
330 With the following variant of @code{!analyze_kw}, the variables must
331 be following by @samp{/}:
334 DEFINE !analyze_parens(vars=!CHARNED('/'))
336 FREQUENCIES /VARIABLES=!vars.
339 !analyze_parens vars=v1 v2 v3/.
342 @item !ENCLOSE('@var{start}','@var{end}')
343 Any number of tokens enclosed between @var{start} and @var{end}, which
344 should each be operator or punctuator tokens. For example, use
345 @code{!ENCLOSE('(',')')} for a value enclosed within parentheses.
346 (Such a value could never have right parentheses inside it, even
347 paired with left parentheses.) The start and end tokens are not part
350 With the following variant of @code{!analyze_kw}, the variables must
351 be specified within parentheses:
354 DEFINE !analyze_parens(vars=!ENCLOSE('(',')'))
356 FREQUENCIES /VARIABLES=!vars.
359 !analyze_parens vars=(v1 v2 v3).
363 Any number of tokens up to the end of the command. This should be
364 used only for the last positional parameter, since it consumes all of
365 the tokens in the command calling the macro.
367 The following variant of @code{!analyze_kw} takes all the variable
368 names up to the end of the command as its argument:
371 DEFINE !analyze_kw(vars=!CMDEND)
373 FREQUENCIES /VARIABLES=!vars.
376 !analyze_kw vars=v1 v2 v3.
380 By default, when an argument's value contains a macro call, the call
381 is expanded each time the argument appears in the macro's body. The
382 @code{!NOEXPAND} keyword in an argument declaration suppresses this
383 expansion. @xref{Controlling Macro Expansion}.
385 @node Controlling Macro Expansion
386 @subsection Controlling Macro Expansion
388 Multiple factors control whether macro calls are expanded in different
389 situations. At the highest level, @code{SET MEXPAND} controls whether
390 macro calls are expanded. By default, it is enabled. @xref{SET
391 MEXPAND}, for details.
393 A macro body may contain macro calls. By default, these are expanded.
394 If a macro body contains @code{!OFFEXPAND} or @code{!ONEXPAND}
395 directives, then @code{!OFFEXPAND} disables expansion of macro calls
396 until the following @code{!ONEXPAND}.
398 A macro argument's value may contain a macro call. These macro calls
399 are expanded, unless the argument was declared with the
400 @code{!NOEXPAND} keyword.
402 The argument to a macro function is a special context that does not
403 expand macro calls. For example, if @code{!vars} is the name of a
404 macro, then @code{!LENGTH(!vars)} expands to 5, as does
405 @code{!LENGTH(!1)} if positional argument 1 has value @code{!vars}.
406 To expand macros in these cases, use the @code{!EVAL} macro function,
407 e.g.@: @code{!LENGTH(!EVAL(!vars))} or @code{!LENGTH(!EVAL(!1))}.
408 @xref{Macro Functions}, for details.
410 These rules apply to macro calls, not to uses within a macro body of
411 macro functions, macro arguments, and macro variables created by
412 @code{!DO} or @code{!LET}, which are always expanded.
414 @code{SET MEXPAND} may appear within the body of a macro, but it will
415 not affect expansion of the macro that it appears in. Use
416 @code{!OFFEXPAND} and @code{!ONEXPAND} instead.
418 @node Macro Functions
419 @subsection Macro Functions
421 Macro bodies may manipulate syntax using macro functions. Macro
422 functions accept tokens as arguments and expand to sequences of
425 The arguments to macro functions have a restricted form. They may
426 only be a single token (such as an identifier or a string), a macro
427 argument, or a call to a macro function. Thus, the following are
428 valid macro arguments:
430 x 5.0 x !1 "5 + 6" !CONCAT(x,y)
432 @noindent and the following are not:
437 Macro functions expand to sequences of characters. When these
438 character strings are processed further as character strings, e.g.@:
439 with @code{!LENGTH}, any character string is valid. When they are
440 interpreted as PSPP syntax, e.g.@: when the expansion becomes part of
441 a command, they need to be valid for that purpose. For example,
442 @code{!UNQUOTE("It's")} will yield an error if the expansion
443 @code{It's} becomes part of a PSPP command, because it contains
444 unbalanced single quotes, but @code{!LENGTH(!UNQUOTE("It's"))} expands
447 The following macro functions are available. Each function's
448 documentation includes examples in the form @code{@var{call}
449 @expansion{} @var{expansion}}.
451 @deffn {Macro Function} !BLANKS (count)
452 Expands to @var{count} unquoted spaces, where @var{count} is a
453 nonnegative integer. Outside quotes, any positive number of spaces
454 are equivalent; for a quoted string of spaces, use
455 @code{!QUOTE(!BLANKS(@var{count}))}.
457 In the examples below, @samp{_} stands in for a space to make the
460 @c Keep these examples in sync with the test for !BLANKS in
461 @c tests/language/control/define.at:
463 !BLANKS(0) @expansion{} @r{empty}
464 !BLANKS(1) @expansion{} _
465 !BLANKS(2) @expansion{} __
466 !QUOTE(!BLANKS(5)) @expansion{} '_____'
470 @deffn {Macro Function} !CONCAT (arg@dots{})
471 Expands to the concatenation of all of the arguments. Before
472 concatenation, each quoted string argument is unquoted, as if
473 @code{!UNQUOTE} were applied. This allows for ``token pasting'',
474 combining two (or more) tokens into a single one:
476 @c Keep these examples in sync with the test for !CONCAT in
477 @c tests/language/control/define.at:
479 !CONCAT(x, y) @expansion{} xy
480 !CONCAT('x', 'y') @expansion{} xy
481 !CONCAT(12, 34) @expansion{} 1234
482 !CONCAT(!NULL, 123) @expansion{} 123
485 @code{!CONCAT} is often used for constructing a series of similar
486 variable names from a prefix followed by a number and perhaps a
489 @c Keep these examples in sync with the test for !CONCAT in
490 @c tests/language/control/define.at:
492 !CONCAT(x, 0) @expansion{} x0
493 !CONCAT(x, 0, y) @expansion{} x0y
496 An identifier token must begin with a letter (or @samp{#} or
497 @samp{@@}), which means that attempting to use a number as the first
498 part of an identifier will produce a pair of distinct tokens rather
499 than a single one. For example:
501 @c Keep these examples in sync with the test for !CONCAT in
502 @c tests/language/control/define.at:
504 !CONCAT(0, x) @expansion{} 0 x
505 !CONCAT(0, x, y) @expansion{} 0 xy
509 @deffn {Macro Function} !EVAL (arg)
510 Expands macro calls in @var{arg}. This is especially useful if
511 @var{arg} is the name of a macro or a macro argument that expands to
512 one, because arguments to macro functions are not expanded by default
513 (@pxref{Controlling Macro Expansion}).
515 The following examples assume that @code{!vars} is a macro that
516 expands to @code{a b c}:
519 !vars @expansion{} a b c
520 !QUOTE(!vars) @expansion{} '!vars'
521 !EVAL(!vars) @expansion{} a b c
522 !QUOTE(!EVAL(!vars)) @expansion{} 'a b c'
525 These examples additionally assume that argument @code{!1} has value
529 !1 @expansion{} a b c
530 !QUOTE(!1) @expansion{} '!vars'
531 !EVAL(!1) @expansion{} a b c
532 !QUOTE(!EVAL(!1)) @expansion{} 'a b c'
536 @deffn {Macro Function} !HEAD (arg)
537 @deffnx {Macro Function} !TAIL (arg)
538 @code{!HEAD} expands to just the first token in an unquoted version of
539 @var{arg}, and @code{!TAIL} to all the tokens after the first.
542 !HEAD('a b c') @expansion{} a
543 !HEAD('a') @expansion{} a
544 !HEAD(!NULL) @expansion{} @r{empty}
545 !HEAD('') @expansion{} @r{empty}
547 !TAIL('a b c') @expansion{} b c
548 !TAIL('a') @expansion{} @r{empty}
549 !TAIL(!NULL) @expansion{} @r{empty}
550 !TAIL('') @expansion{} @r{empty}
554 @deffn {Macro Function} !INDEX (haystack, needle)
555 Looks for @var{needle} in @var{haystack}. If it is present, expands
556 to the 1-based index of its first occurrence; if not, expands to 0.
559 !INDEX(banana, an) @expansion{} 2
560 !INDEX(banana, nan) @expansion{} 3
561 !INDEX(banana, apple) @expansion{} 0
562 !INDEX("banana", nan) @expansion{} 4
563 !INDEX("banana", "nan") @expansion{} 0
564 !INDEX(!UNQUOTE("banana"), !UNQUOTE("nan")) @expansion{} 3
568 @deffn {Macro Function} !LENGTH (arg)
569 Expands to a number token representing the number of characters in
573 !LENGTH(123) @expansion{} 3
574 !LENGTH(123.00) @expansion{} 6
575 !LENGTH( 123 ) @expansion{} 3
576 !LENGTH("123") @expansion{} 5
577 !LENGTH(xyzzy) @expansion{} 5
578 !LENGTH("xyzzy") @expansion{} 7
579 !LENGTH("xy""zzy") @expansion{} 9
580 !LENGTH(!UNQUOTE("xyzzy")) @expansion{} 5
581 !LENGTH(!UNQUOTE("xy""zzy")) @expansion{} 6
582 !LENGTH(!1) @expansion{} 5 @r{if @t{!1} is @t{a b c}}
583 !LENGTH(!1) @expansion{} 0 @r{if @t{!1} is empty}
584 !LENGTH(!NULL) @expansion{} 0
588 @deffn {Macro Function} !NULL
589 Expands to an empty character sequence.
591 @c Keep these examples in sync with the test for !NULL in
592 @c tests/language/control/define.at:
594 !NULL @expansion{} @r{empty}
595 !QUOTE(!NULL) @expansion{} ''
599 @deffn {Macro Function} !QUOTE (arg)
600 @deffnx {Macro Function} !UNQUOTE (arg)
601 The @code{!QUOTE} function expands to its argument surrounded by
602 apostrophes, doubling any apostrophes inside the argument to make sure
603 that it is valid PSPP syntax for a string. If the argument was
604 already a quoted string, @code{!QUOTE} expands to it unchanged.
606 Given a quoted string argument, the @code{!UNQUOTED} function expands
607 to the string's contents, with the quotes removed and any doubled
608 quote marks reduced to singletons. If the argument was not a quoted
609 string, @code{!UNQUOTE} expands to the argument unchanged.
611 @c Keep these examples in sync with the test for !QUOTE and !UNQUOTE in
612 @c tests/language/control/define.at:
614 !QUOTE(123.0) @expansion{} '123.0'
615 !QUOTE( 123 ) @expansion{} '123'
616 !QUOTE('a b c') @expansion{} 'a b c'
617 !QUOTE("a b c") @expansion{} "a b c"
618 !QUOTE(!1) @expansion{} 'a ''b'' c' @r{if @t{!1} is @t{a 'b' c}}
620 !UNQUOTE(123.0) @expansion{} 123.0
621 !UNQUOTE( 123 ) @expansion{} 123
622 !UNQUOTE('a b c') @expansion{} a b c
623 !UNQUOTE("a b c") @expansion{} a b c
624 !UNQUOTE(!1) @expansion{} a 'b' c @r{if @t{!1} is @t{a 'b' c}}
626 !QUOTE(!UNQUOTE(123.0)) @expansion{} '123.0'
627 !QUOTE(!UNQUOTE( 123 )) @expansion{} '123'
628 !QUOTE(!UNQUOTE('a b c')) @expansion{} 'a b c'
629 !QUOTE(!UNQUOTE("a b c")) @expansion{} 'a b c'
630 !QUOTE(!UNQUOTE(!1)) @expansion{} 'a ''b'' c' @r{if @t{!1} is @t{a 'b' c}}
634 @deffn {Macro Function} !SUBSTR (arg, start[, count])
635 Expands to a substring of @var{arg} starting from 1-based position
636 @var{start}. If @var{count} is given, it limits the number of
637 characters in the expansion; if it is omitted, then the expansion
638 extends to the end of @var{arg}.
641 !SUBSTR(banana, 3) @expansion{} nana
642 !SUBSTR(banana, 3, 3) @expansion{} nan
643 !SUBSTR("banana", 1, 3) @expansion{} @r{error (@code{"ba} is not a valid token)}
644 !SUBSTR(!UNQUOTE("banana"), 3) @expansion{} nana
645 !SUBSTR("banana", 3, 3) @expansion{} ana
647 !SUBSTR(banana, 3, 0) @expansion{} @r{empty}
648 !SUBSTR(banana, 3, 10) @expansion{} nana
649 !SUBSTR(banana, 10, 3) @expansion{} @r{empty}
653 @deffn {Macro Function} !UPCASE (arg)
654 Expands to an unquoted version of @var{arg} with all letters converted
658 !UPCASE(freckle) @expansion{} FRECKLE
659 !UPCASE('freckle') @expansion{} FRECKLE
660 !UPCASE('a b c') @expansion{} A B C
661 !UPCASE('A B C') @expansion{} A B C
665 @node Macro Expressions
666 @subsection Macro Expressions
668 Macro expressions are used in conditional expansion and loops, which
669 are described in the following sections. A macro expression may use
670 the following operators, listed in descending order of operator
675 Parentheses override the default operator precedence.
677 @item !EQ !NE !GT !LT !GE !LE = ~= <> > < >= <=
678 Relational operators compare their operands and yield a Boolean
679 result, either @samp{0} for false or @samp{1} for true.
681 These operators always compare their operands as strings. This can be
682 surprising when the strings are numbers because, e.g.,@: @code{1 <
683 1.0} and @code{10 < 2} both evaluate to @samp{1} (true).
685 Comparisons are case sensitive, so that @code{a = A} evaluates to
691 Logical operators interpret their operands as Boolean values, where
692 quoted or unquoted @samp{0} is false and anything else is true, and
693 yield a Boolean result, either @samp{0} for false or @samp{1} for
697 Macro expressions do not include any arithmetic operators.
699 An operand in an expression may be a single token (including a macro
700 argument name) or a macro function invocation. Either way, the
701 expression evaluator unquotes the operand, so that @code{1 = '1'} is
704 @node Macro Conditional Expansion
705 @subsection Macro Conditional Expansion
707 The @code{!IF} construct may be used inside a macro body to allow for
708 conditional expansion. It takes the following forms:
711 !IF (@var{expression}) !THEN @var{true-expansion} !IFEND
712 !IF (@var{expression}) !THEN @var{true-expansion} !ELSE @var{false-expansion} !IFEND
715 When @var{expression} evaluates to true, the macro processor expands
716 @var{true-expansion}; otherwise, it expands @var{false-expansion}, if
717 it is present. The macro processor considers quoted or unquoted
718 @samp{0} to be false, and anything else to be true.
721 @subsection Macro Loops
723 The body of a macro may include two forms of loops: loops over
724 numerical ranges and loops over tokens. Both forms expand a @dfn{loop
725 body} multiple times, each time setting a named @dfn{loop variable} to
726 a different value. The loop body typically expands the loop variable
729 The MITERATE setting (@pxref{SET MITERATE}) limits the number of
730 iterations in a loop. This is a safety measure to ensure that macro
731 expansion terminates. PSPP issues a warning when the MITERATE limit
734 @subsubheading Loops Over Ranges
737 !DO @var{!var} = @var{start} !TO @var{end} [!BY @var{step}]
742 A loop over a numerical range has the form shown above. @var{start},
743 @var{end}, and @var{step} (if included) must be expressions with
744 numeric values. The macro processor accepts both integers and real
745 numbers. The macro processor expands @var{body} for each numeric
746 value from @var{start} to @var{end}, inclusive.
748 The default value for @var{step} is 1. If @var{step} is positive and
749 @math{@var{first} > @var{last}}, or if @var{step} is negative and
750 @math{@var{first} < @var{last}}, then the macro processor doesn't
751 expand the body at all. @var{step} may not be zero.
753 @subsubheading Loops Over Tokens
756 !DO @var{!var} !IN (@var{expression})
761 A loop over tokens takes the form shown above. The macro processor
762 evaluates @var{expression} and expands @var{body} once per token in
763 the result, substituting the token for @var{!var} each time it
766 @node Macro Variable Assignment
767 @subsection Macro Variable Assignment
769 The @code{!LET} construct evaluates an expression and assigns the
770 result to a macro variable. It may create a new macro variable or
771 change the value of one created by a previous @code{!LET} or
772 @code{!DO}, but it may not change the value of a macro argument.
773 @code{!LET} has the following form:
776 !LET @var{!var} = @var{expression}
779 If @var{expression} is more than one token, it must be enclosed in
783 @subsection Macro Settings
785 Some macro behavior is controlled through the SET command
786 (@pxref{SET}). This section describes these settings.
788 Any SET command that changes these settings within a macro body only
789 takes effect following the macro. This is because PSPP expands a
790 macro's entire body at once, so that the SET command inside the body
791 only executes afterwards.
793 The MEXPAND setting (@pxref{SET MEXPAND}) controls whether macros will
794 be expanded at all. By default, macro expansion is on. To avoid
795 expansion of macros called within a macro body, use @code{!OFFEXPAND}
796 and @code{!ONEXPAND} (@pxref{Controlling Macro Expansion}).
798 When MPRINT (@pxref{SET MPRINT}) is turned on, PSPP outputs an
799 expansion of each macro called. This feature can be useful for
800 debugging macro definitions. For reading the expanded version, note
801 that macro expansion removes comments and standardizes white space.
803 MNEST (@pxref{SET MNEST}) limits the depth of expansion of macro
804 calls, that is, the nesting level of macro expansion. The default is
805 50. This is mainly useful to avoid infinite expansion in the case of
806 a macro that calls itself.
808 MITERATE (@pxref{SET MITERATE}) limits the number of iterations in a
809 @code{!DO} construct. The default is 1000.
812 @subsection Additional Notes
814 @subsubsection Calling Macros from Macros
816 If the body of macro A includes a call to macro B, the call can use
817 macro arguments (including @code{!*}) and macro variables as part of
818 arguments to B. For @code{!TOKENS} arguments, the argument or
819 variable name counts as one token regardless of the number that it
820 expands into; for @code{!CHAREND} and @code{!ENCLOSE} arguments, the
821 delimiters come only from the call, not the expansions; and
822 @code{!CMDEND} ends at the calling command, not any end of command
823 within an argument or variable.
825 Macro functions are not supported as part of the arguments in a macro
826 call. To get the same effect, use @code{!LET} to define a macro
827 variable, then pass the macro variable to the macro.
829 When macro A calls macro B, the order of their @code{DEFINE} commands
830 doesn't matter, as long as macro B has been defined when A is called.
832 @subsubsection Command Terminators
834 Macros and command terminators require care. Macros honor the syntax
835 differences between interactive and batch syntax (@pxref{Syntax
836 Variants}), which means that the interpretation of a macro can vary
837 depending on the syntax mode in use. We assume here that interactive
838 mode is in use, in which @samp{.}@: at the end of a line is the
839 primary way to end a command.
841 The @code{DEFINE} command needs to end with @samp{.}@: following the
842 @code{!ENDDEFINE}. The macro body may contain @samp{.}@: if it is
843 intended to expand to whole commands, but using @samp{.}@: within a
844 macro body that expands to just syntax fragments (such as a list of
845 variables) will cause syntax errors.
847 Macro directives such as @code{!IF} and @code{!DO} do not end with
850 @subsubsection Expansion Contexts
852 Macros do not expand within comments, whether introduced within a line
853 by @code{/*} or as a separate COMMENT or @samp{*} commands
854 (@pxref{COMMENT}). (SPSS does expand macros in COMMENT and @samp{*}.)
856 Macros do not expand within quoted strings.
858 Macros are expanded in the @code{TITLE} and @code{SUBTITLE} commands
859 as long as their arguments are not quoted strings.
861 @subsubsection PRESERVE and RESTORE
863 Some macro bodies might use the SET command to change certain
864 settings. When this is the case, consider using the PRESERVE and
865 RESTORE commands to save and then restore these settings.
866 @xref{PRESERVE and RESTORE}.
883 @cmd{DO IF} allows one of several sets of transformations to be
884 executed, depending on user-specified conditions.
886 If the specified boolean expression evaluates as true, then the block
887 of code following @cmd{DO IF} is executed. If it evaluates as
889 none of the code blocks is executed. If it is false, then
890 the boolean expression on the first @cmd{ELSE IF}, if present, is tested in
891 turn, with the same rules applied. If all expressions evaluate to
892 false, then the @cmd{ELSE} code block is executed, if it is present.
894 When @cmd{DO IF} or @cmd{ELSE IF} is specified following @cmd{TEMPORARY}
895 (@pxref{TEMPORARY}), the @cmd{LAG} function may not be used
903 DO REPEAT dummy_name=expansion@dots{}.
907 expansion takes one of the following forms:
913 num_or_range takes one of the following forms:
918 @cmd{DO REPEAT} repeats a block of code, textually substituting
919 different variables, numbers, or strings into the block with each
922 Specify a dummy variable name followed by an equals sign (@samp{=})
923 and the list of replacements. Replacements can be a list of existing
924 or new variables, numbers, strings, or @code{ALL} to specify all
925 existing variables. When numbers are specified, runs of increasing
926 integers may be indicated as @code{@var{num1} TO @var{num2}}, so that
927 @samp{1 TO 5} is short for @samp{1 2 3 4 5}.
929 Multiple dummy variables can be specified. Each
930 variable must have the same number of replacements.
932 The code within @cmd{DO REPEAT} is repeated as many times as there are
933 replacements for each variable. The first time, the first value for
934 each dummy variable is substituted; the second time, the second value
935 for each dummy variable is substituted; and so on.
937 Dummy variable substitutions work like macros. They take place
938 anywhere in a line that the dummy variable name occurs. This includes
939 command and subcommand names, so command and subcommand names that
940 appear in the code block should not be used as dummy variable
941 identifiers. Dummy variable substitutions do not occur inside quoted
942 strings, comments, unquoted strings (such as the text on the
943 @cmd{TITLE} or @cmd{DOCUMENT} command), or inside @cmd{BEGIN
944 DATA}@dots{}@cmd{END DATA}.
946 Substitution occurs only on whole words, so that, for example, a dummy
947 variable PRINT would not be substituted into the word PRINTOUT.
949 New variable names used as replacements are not automatically created
950 as variables, but only if used in the code block in a context that
951 would create them, @i{e.g.}@: on a @cmd{NUMERIC} or @cmd{STRING} command
952 or on the left side of a @cmd{COMPUTE} assignment.
954 Any command may appear within @subcmd{DO REPEAT}, including nested @subcmd{DO REPEAT}
955 commands. If @cmd{INCLUDE} or @cmd{INSERT} appears within @subcmd{DO REPEAT},
956 the substitutions do not apply to the included file.
958 If @subcmd{PRINT} is specified on @cmd{END REPEAT}, the commands after
959 substitutions are made should be printed to the listing file, prefixed
960 by a plus sign (@samp{+}). This feature is not yet implemented.
967 LOOP [@var{index_var}=@var{start} TO @var{end} [BY @var{incr}]] [IF @var{condition}].
969 END LOOP [IF @var{condition}].
972 @cmd{LOOP} iterates a group of commands. A number of
973 termination options are offered.
975 Specify index_var to make that variable count from one value to
976 another by a particular increment. @var{index_var} must be a pre-existing
977 numeric variable. @var{start}, @var{end}, and @var{incr} are numeric expressions
978 (@pxref{Expressions}.)
980 During the first iteration, @var{index_var} is set to the value of @var{start}.
981 During each successive iteration, @var{index_var} is increased by the value of
982 @var{incr}. If @var{end} > @var{start}, then the loop terminates
983 when @var{index_var} > @var{end};
984 otherwise it terminates when @var{index_var} < @var{end}. If @var{incr} is not specified
985 then it defaults to +1 or -1 as appropriate.
987 If @var{end} > @var{start} and @var{incr} < 0, or if @var{end} < @var{start} and
988 @var{incr} > 0, then the
989 loop is never executed. @var{index_var} is nevertheless set to the value of
992 Modifying @var{index_var} within the loop is allowed, but it has no effect on
993 the value of @var{index_var} in the next iteration.
995 Specify a boolean expression for the condition on @cmd{LOOP} to
996 cause the loop to be executed only if the condition is true. If the
997 condition is false or missing before the loop contents are executed the
998 first time, the loop contents are not executed at all.
1000 If index and condition clauses are both present on @cmd{LOOP}, the
1001 index variable is always set before the condition is evaluated. Thus,
1002 a condition that makes use of the index variable will always see the
1003 index value to be used in the next execution of the body.
1005 Specify a boolean expression for the condition on @cmd{END LOOP} to cause
1006 the loop to terminate if the condition is true after the enclosed
1007 code block is executed. The condition is evaluated at the end of the
1008 loop, not at the beginning, so that the body of a loop with only a
1009 condition on @cmd{END LOOP} will always execute at least once.
1011 If the index clause is not present, then the global @code{MXLOOPS}
1012 setting, which defaults to 40, limits the number of iterations
1013 (@pxref{SET MXLOOPS}).
1015 @cmd{BREAK} also terminates @cmd{LOOP} execution (@pxref{BREAK}).
1017 Loop index variables are by default reset to system-missing from one
1018 case to another, not left, unless a scratch variable is used as index.
1019 When loops are nested, this is usually undesired behavior, which can
1020 be corrected with @cmd{LEAVE} (@pxref{LEAVE}) or by using a scratch
1021 variable as the loop index.
1023 When @cmd{LOOP} or @cmd{END LOOP} is specified following @cmd{TEMPORARY}
1024 (@pxref{TEMPORARY}), the @cmd{LAG} function may not be used