emo/busybox
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

var_bash4.tests: better wording in comment

Browse Source 
Signed-off-by: Denys Vlasenko <vda.linux@googlemail.com>
This commit is contained in:
Denys Vlasenko 2010-08-06 19:28:04 +02:00
parent f02c82f38c
commit c8d305d89f
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
shell/ash_test/ash-vars/var_bash4.tests
View File

@ -1,12 +1,12 @@
# This testcase demonstrates that backslashes are treated differently
# in 1st and 2nd parts of ${var/search/repl}:
# if quoted: "${var/search/repl}", and repl contains \a (a non-special char),
# the backslash in repl stays; if unquoted, backslash: removed
# if quoted ("${var/search/repl}"), and repl contains \a (a non-special char),
# the backslash in repl stays; if unquoted, backslash is removed.
# But search part does not act like that: \a is always converted to just a,
# even in quotes.
#
# bash4 (and probably bash3 too) result: "Quoted:" results are different -
# they have extra backslash before z.
# bash4 (and probably bash3 too): "Quoted:" results are different from
# unquoted and assignment expansions - they have a backslash before z.
v='a*b\*c'
echo 'Source: ' "$v"