Path: csiph.com!xmission!news.snarked.org!news.linkpendium.com!news.linkpendium.com!panix!usenet.stanford.edu!not-for-mail
From: konsolebox <konsolebox@gmail.com>
Newsgroups: gnu.bash.bug
Subject: Re: Preventing Bash Variable Confusion
Date: Thu, 30 Jan 2020 16:19:01 +0800
Lines: 26
Approved: bug-bash@gnu.org
Message-ID: <mailman.93.1580372436.2384.bug-bash@gnu.org>
References: <20200128210225.GC12574@localhost4.local> <CAJnmqwbr6EVJOZn6SLdByAgZAoFN60ahCp3m2HJyJ6VS=hwEvg@mail.gmail.com> <20200130064018.GA23692@localhost4.local> <CAJnmqwa0y4iOQEzFPZjGGqtJ3eLPPdsZRz2ZAfLneEtQUJo2nA@mail.gmail.com>
NNTP-Posting-Host: lists.gnu.org
Mime-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Cc: bug-bash <bug-bash@gnu.org>
To: Roger <rogerx.oss@gmail.com>
Envelope-to: bug-bash@gnu.org
In-Reply-To: <20200130064018.GA23692@localhost4.local>
Precedence: list
Xref: csiph.com gnu.bash.bug:15853

On Thu, Jan 30, 2020 at 2:40 PM Roger <rogerx.oss@gmail.com> wrote:
> 1) Using an underslash on all capitol variable names just looks ugly in my
> opinion.

If you mean adding an underscore prefix I agree.

> 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.)

Really just useful if you're writing in multiple scripts.

> 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.

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.

-- 
konsolebox