Path: csiph.com!xmission!news.snarked.org!news.linkpendium.com!news.linkpendium.com!panix!usenet.stanford.edu!not-for-mail
From: Roger <rogerx.oss@gmail.com>
Newsgroups: gnu.bash.bug
Subject: Re: Preventing Bash Variable Confusion
Date: Thu, 30 Jan 2020 01:40:18 -0500
Lines: 40
Approved: bug-bash@gnu.org
Message-ID: <mailman.92.1580366438.2384.bug-bash@gnu.org>
References: <20200128210225.GC12574@localhost4.local> <CAJnmqwbr6EVJOZn6SLdByAgZAoFN60ahCp3m2HJyJ6VS=hwEvg@mail.gmail.com> <20200130064018.GA23692@localhost4.local>
NNTP-Posting-Host: lists.gnu.org
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
To: konsolebox <konsolebox@gmail.com>, bug-bash@gnu.org
Envelope-to: bug-bash@gnu.org
Content-Disposition: inline
In-Reply-To: <CAJnmqwbr6EVJOZn6SLdByAgZAoFN60ahCp3m2HJyJ6VS=hwEvg@mail.gmail.com>
User-Agent: Mutt/1.10.1 (2018-07-13)
Precedence: list
Xref: csiph.com gnu.bash.bug:15852

> On Thu, Jan 30, 2020 at 11:37:26AM +0800, konsolebox wrote:
>
>   Here's my take.
>   You can still use all caps on global variables just mind the internal
>   variables. You can have it prefixed by an underscore if you worry about
>   conflicts.** You can also have it prefixed with the script's name in all
>   caps.** It's best to have the variables initialized at the beginning if
>   the script so it's explicit that you intend to use the variables as global
>   variables of the script.
>   And then you use lowercase on local.** Use an underscore or
>   two-underscores prefix on indirect variables and never reference an
>   indirect variable with another.** This includes passing the indirect
>   variable for reference to another function.
>   --
>   konsolebox

I've thought about this, yes I can use that style.  However...

1) Using an underslash on all capitol variable names just looks ugly in my 
opinion.  Or more to the point, the style seems to stray away from main stream 
styles.

2) Prefixing variable names with the name of the script (or other lengthy 
prefix) requires more characters I could be using for describing my variable or 
function.  (If I were writing unreadable code, I probably would not mind.)


I've decided to comply with Google's Style guidelines, even though they do not 
pay me a paycheck, but they do give me lots of free stuff.  Shrugs, besides, 
the more my Bash scripting looks like C, the easier it is to read.

The can push me away from defining my variables in all capitol letters.  They 
can even push me to code in C and Assembly, but just don't push me to script in 
Python.


-- 
Roger
http://rogerx.sdf.org/