1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
|
# $NetBSD: directive-for.mk,v 1.10 2020/12/27 09:58:35 rillig Exp $
#
# Tests for the .for directive.
#
# TODO: Describe naming conventions for the loop variables.
# .for f in values
# .for file in values
# .for _FILE_ in values
# .for .FILE. in values
# .for _f_ in values
# Using the .for loop, lists of values can be produced.
# In simple cases, the :@var@${var}@ variable modifier can be used to
# reach the same effects.
#
.undef NUMBERS
.for num in 1 2 3
NUMBERS+= ${num}
.endfor
.if ${NUMBERS} != "1 2 3"
. error
.endif
# The .for loop also works for multiple iteration variables.
# This is something that the variable modifier :@ cannot do.
.for name value in VARNAME value NAME2 value2
${name}= ${value}
.endfor
.if ${VARNAME} != "value" || ${NAME2} != "value2"
. error
.endif
# The .for loop splits the items at whitespace, taking quotes into account,
# just like the :M or :S variable modifiers.
#
# Until 2012-06-03, it had split the items exactly at whitespace, without
# taking the quotes into account. This had resulted in 10 words.
#
.undef WORDS
.for var in one t\ w\ o "three three" 'four four' `five six`
WORDS+= counted
.endfor
.if ${WORDS:[#]} != 6
. error
.endif
# In the body of the .for loop, the iteration variables can be accessed
# like normal variables, even though they are not really variables.
#
# Instead, the expression ${var} is transformed into ${:U1}, ${:U2} and so
# on, before the loop body is evaluated.
#
# A notable effect of this implementation technique is that the .for
# iteration variables and the normal global variables live in separate
# namespaces and do not influence each other.
#
var= value before
var2= value before
.for var var2 in 1 2 3 4
.endfor
.if ${var} != "value before"
. warning After the .for loop, var must still have its original value.
.endif
.if ${var2} != "value before"
. warning After the .for loop, var2 must still have its original value.
.endif
# Everything from the paragraph above also applies if the loop body is
# empty, even if there is no actual iteration since the loop items are
# also empty.
#
var= value before
var2= value before
.for var var2 in ${:U}
.endfor
.if ${var} != "value before"
. warning After the .for loop, var must still have its original value.
.endif
.if ${var2} != "value before"
. warning After the .for loop, var2 must still have its original value.
.endif
# Until 2008-12-21, the values of the iteration variables were simply
# inserted as plain text and then parsed as usual, which made it possible
# to achieve all kinds of strange effects.
#
# Before that date, the .for loop expanded to:
# EXPANSION+= value
# Since that date, the .for loop expands to:
# EXPANSION${:U+}= value
#
EXPANSION= before
EXPANSION+ = before
.for plus in +
EXPANSION${plus}= value
.endfor
.if ${EXPANSION} != "before"
. error This must be a make from before 2009.
.endif
.if ${EXPANSION+} != "value"
. error This must be a make from before 2009.
.endif
# When the outer .for loop is expanded, it sees the expression ${i} and
# expands it. The inner loop then has nothing more to expand.
.for i in outer
. for i in inner
. info ${i}
. endfor
.endfor
# From https://gnats.netbsd.org/29985.
#
# Until 2008-12-21, the .for loop was expanded by replacing the variable
# value literally in the body. This could lead to situations where the
# characters from the variable value were interpreted as markup rather than
# plain text.
#
# Until 2012-06-03, the .for loop had split the words at whitespace, without
# taking quotes into account. This made it possible to have variable values
# like "a:\ a:\file.txt" that ended in a single backslash. Since then, the
# variable values have been replaced with expressions of the form ${:U...},
# which are not interpreted as code anymore.
#
# As of 2020-09-22, a comment in for.c says that it may be possible to
# produce an "unwanted substitution", but there is no demonstration code yet.
#
# The above changes prevent a backslash at the end of a word from being
# interpreted as part of the code. Because of this, the trailingBackslash
# hack in Var_Subst is no longer needed and as of 2020-09-22, has been
# removed.
.for path in a:\ a:\file.txt d:\\ d:\\file.txt
. info ${path}
.endfor
# Ensure that braces and parentheses are properly escaped by the .for loop.
# Each line must print the same word 3 times.
# See GetEscapes.
.for v in ( [ { ) ] } (()) [[]] {{}} )( ][ }{
. info $v ${v} $(v)
.endfor
# As of 2020-10-25, the variable names may contain arbitrary characters,
# except for whitespace. This allows for creative side effects. Hopefully
# nobody is misusing this "feature".
var= outer
.for var:Q in value "quoted"
. info ${var} ${var:Q} ${var:Q:Q}
.endfor
# XXX: A parse error or evaluation error in the items of the .for loop
# should skip the whole loop. As of 2020-12-27, the loop is expanded twice.
.for var in word1 ${:Uword2:Z} word3
. info XXX: Not reached ${var}
.endfor
all:
@:;
|
