Re: Preventing Bash Variable Confusion

From	Roger <rogerx.oss@gmail.com>
Newsgroups	gnu.bash.bug
Subject	Re: Preventing Bash Variable Confusion
Date	2020-01-30 14:41 -0500
Message-ID	<mailman.128.1580413325.2384.bug-bash@gnu.org> (permalink)
References	<20200128210225.GC12574@localhost4.local> <CAJnmqwbr6EVJOZn6SLdByAgZAoFN60ahCp3m2HJyJ6VS=hwEvg@mail.gmail.com> <20200130064018.GA23692@localhost4.local> <CAJnmqwa0y4iOQEzFPZjGGqtJ3eLPPdsZRz2ZAfLneEtQUJo2nA@mail.gmail.com> <20200130194153.GB7255@localhost4.local>

Show all headers | View raw

>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.

Not so much with underscore prefix, however I'll try learning.

--
Roger
http://rogerx.sdf.org/

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

Thread

Re: Preventing Bash Variable Confusion Roger <rogerx.oss@gmail.com> - 2020-01-30 14:41 -0500

csiph-web