Re: Preventing Bash Variable Confusion

From	"Chris F.A. Johnson" <chris@cfajohnson.com>
Newsgroups	gnu.bash.bug
Subject	Re: Preventing Bash Variable Confusion
Date	2020-01-30 21:13 -0500
Message-ID	<mailman.1.1580436833.2412.bug-bash@gnu.org> (permalink)
References	(1 earlier) <CAJnmqwbr6EVJOZn6SLdByAgZAoFN60ahCp3m2HJyJ6VS=hwEvg@mail.gmail.com> <20200130064018.GA23692@localhost4.local> <CAJnmqwa0y4iOQEzFPZjGGqtJ3eLPPdsZRz2ZAfLneEtQUJo2nA@mail.gmail.com> <20200130194153.GB7255@localhost4.local> <alpine.DEB.2.21.2001302111240.27533@chris>

Show all headers | View raw

On Thu, 30 Jan 2020, Roger wrote:

>> They still allow you to define constants in all-caps.  The impact it
>> makes is not so different with defining globals as such.  Try Ruby.
>
> The reason I used to prefer using all uppercase/capital letters, the variable
> definitations would stand out similar to C style definition macros.  Variables
> become extremely identifiable and comprehensible.

A text editor, such as emacs in Bash mode, can highlight variables. No
need to use any sort of naming convention.

-- 
    Chris F.A. Johnson                         <http://cfajohnson.com/>
    =========================== Author: ===============================
    Shell Scripting Recipes: A Problem-Solution Approach (2005, Apress)
    Pro Bash Programming: Scripting the GNU/Linux shell (2009, Apress)

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

Thread

Re: Preventing Bash Variable Confusion "Chris F.A. Johnson" <chris@cfajohnson.com> - 2020-01-30 21:13 -0500

csiph-web