From c7e89264b37328ba475129dc71ca851988a27988 Mon Sep 17 00:00:00 2001 From: Vidar Holen Date: Sun, 25 Feb 2018 13:56:48 -0800 Subject: [PATCH] Updated SC2229 (markdown) --- SC2229.md | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/SC2229.md b/SC2229.md index 7df1da7..bd0adfd 100644 --- a/SC2229.md +++ b/SC2229.md @@ -36,4 +36,8 @@ read "${foo}" # ShellCheck warns read "${foo?}" # No warning ``` -`${foo?}` fails when `foo` is unset, which is fine since `read` would have failed too. The main side effect is an improved runtime error message in that case. \ No newline at end of file +`${foo?}` fails when `foo` is unset, which is fine since `read` would have failed too. The main side effect is an improved runtime error message in that case. + +### Related resources: + +* [Bash Pitfalls #12](https://mywiki.wooledge.org/BashPitfalls#pf12): `read $foo` \ No newline at end of file