summary refs log tree commit diff
path: root/bin/cash/tests/expansion/plus-minus3.0
blob: 0e5510608d127c35b9a4eed9ae8e1ff76a6a1003 (plain) (blame)
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
# $FreeBSD: releng/12.0/bin/sh/tests/expansion/plus-minus3.0 206817 2010-04-18 22:13:45Z jilles $

e= q='?' a='*' t=texttext s='ast*que?non' p='/et[c]/' w='a b c' b='{{(#)}}'
h='##'
failures=''
ok=''

testcase() {
	code="$1"
	expected="$2"
	oIFS="$IFS"
	eval "$code"
	IFS='|'
	result="$#|$*"
	IFS="$oIFS"
	if [ "x$result" = "x$expected" ]; then
		ok=x$ok
	else
		failures=x$failures
		echo "For $code, expected $expected actual $result"
	fi
}

# We follow original ash behaviour for quoted ${var+-=?} expansions:
# a double-quote in one switches back to unquoted state.
# This allows expanding a variable as a single word if it is set
# and substituting multiple words otherwise.
# It is also close to the Bourne and Korn shells.
# POSIX leaves this undefined, and various other shells treat
# such double-quotes as introducing a second level of quoting
# which does not do much except quoting close braces.

testcase 'set -- "${p+"/et[c]/"}"'		'1|/etc/'
testcase 'set -- "${p-"/et[c]/"}"'		'1|/et[c]/'
testcase 'set -- "${p+"$p"}"'			'1|/etc/'
testcase 'set -- "${p-"$p"}"'			'1|/et[c]/'
testcase 'set -- "${p+"""/et[c]/"}"'		'1|/etc/'
testcase 'set -- "${p-"""/et[c]/"}"'		'1|/et[c]/'
testcase 'set -- "${p+"""$p"}"'			'1|/etc/'
testcase 'set -- "${p-"""$p"}"'			'1|/et[c]/'
testcase 'set -- "${p+"\@"}"'			'1|@'
testcase 'set -- "${p+"'\''/et[c]/'\''"}"'	'1|/et[c]/'

test "x$failures" = x