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: Wed, 29 Jan 2020 13:05:11 -0500
Lines: 71
Approved: bug-bash@gnu.org
Message-ID: <mailman.50.1580321118.2384.bug-bash@gnu.org>
References: <20200128210225.GC12574@localhost4.local> <20806.1580277461@jinx.noi.kre.to> <20200129142305.GX1350@eeg.ccf.org> <20200129180511.GA5533@localhost4.local>
NNTP-Posting-Host: lists.gnu.org
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="uAKRQypu60I7Lcqm"
To: bug-bash@gnu.org
Envelope-to: bug-bash@gnu.org
Content-Disposition: inline
In-Reply-To: <20200129142305.GX1350@eeg.ccf.org>
User-Agent: Mutt/1.10.1 (2018-07-13)
Precedence: list
Xref: csiph.com gnu.bash.bug:15842


--uAKRQypu60I7Lcqm
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Awesome.

So $mVARIABLE is an alternative.  However, per Google style and my preferen=
ce,=20
mixed seems messy.  I thought camel/mixed case increased readability years =
ago,=20
but over time I typed my_variable or my_function_name (C code) much easier =
as=20
well as read easier.  The missing space char between words seems to condone=
=20
confusion when attempting to read script/code naturally.  All capitol case=
=20
variable names were extremely visible when reading code, but seems now to b=
e=20
explicitly reserved for OS intercommunication use.

I think I prefer the style; $_variable, $my_variable and f_functionname. =
=20
Google style documentation cited the "$_" prefix satisfied uniqueness from =
OS=20
related variable names as well as supposedly increasing readability or=20
distinguishing variables from the rest of the scripting language.

Also the use of local defined variables within functions is probably desira=
ble. =20
I'll start incorporating these techniques within my scripts as well as like=
ly=20
incorporating a trap protection within loops calling non-builtin commands.


For reference:

Google
Shell Style Guide
https://google.github.io/styleguide/shell.xml


Ky-Anh Huynh icy (Popular Hit)
https://github.com/icy/bash-coding-style
Seems to be a duplicate of Google's style guide.



--=20
Roger
http://rogerx.sdf.org/

--uAKRQypu60I7Lcqm
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature

-----BEGIN PGP SIGNATURE-----

iQEzBAEBCAAdFiEE9RWsHyMf/E7wvN52Bs6g7OKIfHUFAl4xyVMACgkQBs6g7OKI
fHUXOggAgtb4mEfH6bJdY92P3Kq/9V5acCvbo9/qoMxmCnonU2EephhYiLPYy3JK
ZWDieuT368/he+YQh0oJXuj4oiE/mQ4T3ePJLp7yKrdxWAQWAK7eMj3mJU3wkhka
xmmdgwrjKeDfaa+TTx//wx7rHtiRBRuzanEHhJcSaWxGZwmUj9URfc8NvRH/cv9l
SN+sUnGxg+cM1k/B4BFLsNrHJw0zdUevwcePsM8InKXkoqoTdDOZe33i9nQfOlBI
Bu9Ae+HIhUBcjzN6hPd4VUSsniET3794zezAjYNCR5y705T5PaiCV7Tf7zlu89pv
k1+wwhCHdsHTNb9qdS6dMtwFkRlzVA==
=JnjE
-----END PGP SIGNATURE-----

--uAKRQypu60I7Lcqm--