Re: Preventing Bash Variable Confusion

From	Greg Wooledge <wooledg@eeg.ccf.org>
Newsgroups	gnu.bash.bug
Subject	Re: Preventing Bash Variable Confusion
Date	2020-01-30 08:35 -0500
Message-ID	<mailman.102.1580391358.2384.bug-bash@gnu.org> (permalink)
References	<20200128210225.GC12574@localhost4.local> <CAJnmqwbr6EVJOZn6SLdByAgZAoFN60ahCp3m2HJyJ6VS=hwEvg@mail.gmail.com> <20200130133526.GQ1350@eeg.ccf.org>

Show all headers | View raw

On Thu, Jan 30, 2020 at 11:37:26AM +0800, konsolebox wrote:
> You can still use all caps on global variables just mind the internal
> variables.

Easier said than done.  How many times have you had to diagnose
someone's failing script, and it turned out the reason it was failing
was because they used a variable like HOME or PATH or USER and "forgot"
that it would conflict with a special/environment variable?

For me, that answer is "too many".

Back to gnu.bash.bug | Previous | Next | Find similar | Unroll thread

Thread

Re: Preventing Bash Variable Confusion Greg Wooledge <wooledg@eeg.ccf.org> - 2020-01-30 08:35 -0500

csiph-web