OpenGrok
Home
Sort by:
relevance
|
last modified time
|
path
Full Search
in project(s):
src
Definition
Symbol
File Path
History
|
|
Help
Searched
refs:parentheses
(Results
1 - 25
of
29
) sorted by relevancy
1
2
/src/usr.bin/make/unit-tests/
cond-op-parentheses.exp
1
make: cond-op-
parentheses
.mk:22: Comparison with ">" requires both operands "3" and "(2" to be numeric
2
make: cond-op-
parentheses
.mk:25: Malformed conditional "(3) > 2"
3
make: cond-op-
parentheses
.mk:44: Malformed conditional "("
4
make: cond-op-
parentheses
.mk:58: Malformed conditional ")"
gnode-submake.mk
16
all:
parentheses
-dot
parentheses
-no-dot
38
parentheses
-dot:
41
parentheses
-no-dot:
cond-op-parentheses.mk
1
# $NetBSD: cond-op-
parentheses
.mk,v 1.9 2025/06/28 22:39:28 rillig Exp $
3
# Tests for
parentheses
in .if conditions, which group expressions to override
4
# the precedence of the operators '!', '&&' and '||'.
Parentheses
cannot be
8
# does not have to be enclosed in
parentheses
.
15
#
Parentheses
cannot enclose numbers as there is no need for it. Make does
19
# XXX: It's inconsistent that the right operand has unbalanced
parentheses
.
34
#
Parentheses
can be nested at least to depth 112. There is nothing special
cond-func.mk
13
${:UVAR(value)}= variable name with
parentheses
61
# Even
parentheses
may appear in variable names.
78
# There may be spaces around the operators and
parentheses
, and even
79
# inside the
parentheses
. The spaces inside the
parentheses
are not
var-op-assign.mk
62
# But if the whitespace appears inside
parentheses
or braces, everything is
66
# neither contain
parentheses
nor braces. This is only a side-effect from
68
# name. It only counts
parentheses
and braces instead of properly parsing
71
VAR(spaces in
parentheses
)= ()
78
VARNAME_PAREN= VAR(spaces in
parentheses
)
var-op-sunsh.mk
97
# Since the parser just counts braces and
parentheses
instead of properly
100
# be enclosed in braces or
parentheses
.
104
VAR :sh(Put a comment here)= comment in
parentheses
105
.if ${VAR} != "comment in
parentheses
"
110
#
parentheses
. Braces and
parentheses
are interchangeable, that is, a '(' can
111
# be closed by either ')' or '}'. These braces and
parentheses
are only
varmod-edge.mk
13
INP= (
parentheses
) {braces} (opening closing) ()
15
EXP= (
parentheses
) ()
50
#
parentheses
and braces are counted. This leads to a parse error since
56
INP= (
parentheses
)
58
EXP= (
parentheses
)}
65
# In contrast to
parentheses
and braces, the brackets are not counted
varname.mk
8
# must be balanced.
Parentheses
and braces may be mixed.
15
# braces and
parentheses
equally, therefore the first closing brace already
18
${VARNAME}= 3 open
parentheses
19
.if "${VAR(((}}}}" != "3 open
parentheses
}}}"
26
# This is not a variable assignment since the
parentheses
and braces are not
33
# as an escape character, therefore the
parentheses
still count to the nesting
directive-include-guard.exp
31
Parse_PushInput: variable-name-
parentheses
.tmp:1
32
Parse_PushInput: variable-name-
parentheses
.tmp:1
cond-op.mk
9
# cond-op-
parentheses
.mk
28
# does not need
parentheses
.
moderrs.mk
57
# In ParseModifierPart, braces and
parentheses
don't have to be balanced.
58
# This is contrary to the :M, :N modifiers, where both
parentheses
and
61
# used delimiter (either braces or
parentheses
) must be balanced.
cond-func-empty.mk
6
# Note that the argument in the
parentheses
is a variable name, not an
153
# There may be spaces outside the
parentheses
.
154
# Spaces inside the
parentheses
are interpreted as part of the variable name.
directive-include-guard.mk
124
# If the guard variable condition is enclosed in
parentheses
, it does not have
153
# If the guard variable condition is enclosed in
parentheses
, it does not have
189
# A variable name can contain balanced
parentheses
, at least in conditions and
191
# where
parentheses
or braces are handled inconsistently to make this naming
194
CASES+= variable-name-
parentheses
195
LINES.variable-name-
parentheses
= \
196
'.ifndef VARIABLE_NAME(&)
PARENTHESES
' \
197
'VARIABLE_NAME(&)
PARENTHESES
=' \
199
# expect: Parse_PushInput: variable-name-
parentheses
.tmp:1
200
# expect: Parse_PushInput: variable-name-
parentheses
.tmp:
[
all
...]
cond-token-string.mk
89
# if it contains expressions. The
parentheses
are not necessary for
varmod-defined.mk
59
# to the :M modifier,
parentheses
and braces do not need to be nested.
parse-var.mk
10
# long form with
parentheses
endc == ')'
cond-token-var.mk
56
#
parentheses
.
varmod-assign.mk
138
# enclosed in
parentheses
. In such a case, parsing stops at the first ')',
varmod.mk
259
# When an expression has the unusual form $(...) with
parentheses
,
directive-for-escape.mk
132
# expressions, braces and
parentheses
. (Compare ':M', ':S', and
/src/regress/lib/libc/divrem/
Makefile
6
COPTS+= -Wall -Wno-format -Wno-
parentheses
-Wno-uninitialized
/src/usr.sbin/zdump/
Makefile
17
CWARNFLAGS.clang+= -Wno-error=bitwise-conditional-
parentheses
/src/sys/modules/dtrace/dtrace/
Makefile
58
-Wno-
parentheses
\
/src/tests/usr.bin/indent/
t_errors.sh
362
error: code.c:3: Unbalanced
parentheses
382
error: code.c:4: Unbalanced
parentheses
/src/sys/external/gpl2/dts/dist/arch/arm/boot/dts/
pxa3xx.dtsi
87
* used in
parentheses
for don't-care values. Except for the float output,
Completed in 19 milliseconds
1
2
Indexes created Wed Oct 15 07:09:58 GMT 2025