diff options
author | David Kastrup <dak@gnu.org> | 2007-09-23 22:42:08 +0200 |
---|---|---|
committer | Junio C Hamano <gitster@pobox.com> | 2007-09-23 16:12:00 -0700 |
commit | 822f7c7349d61f6075961ce42c1bd1a85cf999e5 (patch) | |
tree | ae3b0243021d42bf07da00b2d47aa4082a68e720 /git-submodule.sh | |
parent | b9fc6ea9efdc988d851666d45d80076839d9c225 (diff) | |
download | git-822f7c7349d61f6075961ce42c1bd1a85cf999e5.tar.gz git-822f7c7349d61f6075961ce42c1bd1a85cf999e5.tar.xz |
Supplant the "while case ... break ;; esac" idiom
A lot of shell scripts contained stuff starting with
while case "$#" in 0) break ;; esac
and similar. I consider breaking out of the condition instead of the
body od the loop ugly, and the implied "true" value of the
non-matching case is not really obvious to humans at first glance. It
happens not to be obvious to some BSD shells, either, but that's
because they are not POSIX-compliant. In most cases, this has been
replaced by a straight condition using "test". "case" has the
advantage of being faster than "test" on vintage shells where "test"
is not a builtin. Since none of them is likely to run the git
scripts, anyway, the added readability should be worth the change.
A few loops have had their termination condition expressed
differently.
Signed-off-by: David Kastrup <dak@gnu.org>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'git-submodule.sh')
-rwxr-xr-x | git-submodule.sh | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/git-submodule.sh b/git-submodule.sh index 3320998c7..673aa27a4 100755 --- a/git-submodule.sh +++ b/git-submodule.sh @@ -251,7 +251,7 @@ modules_list() done } -while case "$#" in 0) break ;; esac +while test $# != 0 do case "$1" in add) |