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: Preventing Bash Variable Confusion
Date: Tue, 28 Jan 2020 16:02:25 -0500
Lines: 76
Approved: bug-bash@gnu.org
Message-ID: <mailman.263.1580245350.2185.bug-bash@gnu.org>
References: <20200128210225.GC12574@localhost4.local>
NNTP-Posting-Host: lists.gnu.org
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="v9Ux+11Zm5mwPlX6"
To: bug-bash@gnu.org
Envelope-to: bug-bash@gnu.org
Content-Disposition: inline
User-Agent: Mutt/1.10.1 (2018-07-13)
Precedence: list
Xref: csiph.com gnu.bash.bug:15829


--v9Ux+11Zm5mwPlX6
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

I've used Bash for quite some time now and have heard lots about how variab=
les=20
should be named or styled.

1) Bash internal reserved words cannot be used a variables.  (OK. All of us=
 who=20
have programmed code get this and of course abide whole heartedly, else we =
fail=20
quickly!)

2) Operating System (Bash or other) reserved variables are all defined as=
=20
capitol letters, and all capitol letter variables should be avoided within =
Bash=20
scripts.  (I've heard of this, however, I enjoy defining my variables in al=
l=20
capitol letters due to the increased readability of the script ... or in=20
essence, all capitol letters readily distinguishes variables from other Bas=
h=20
words and operators.)

Some say variables should be prefixed (or suffixed) to further distinguish =
Bash=20
variables from possible collisions with operating system Bash or other rela=
ted=20
variables.

I've thought about using "_VARIABLE" and have seen similar, but also requir=
es=20
an extra odd stressed finger combination prior to typing all capitol letter=
s. =20
Typing all capitol letters can be stressful, but the task improves readabil=
ity=20
in my point of view that the time and effort are well worth the effort, unt=
il I=20
get to the additional underscore.

When and if I program in C, I tend to use all lower case style, my_variable.

Anybody have any further insight concerning variable naming styles aside fr=
om=20
what's already written within the documentation?

I could do something like MY_VARIABLE, but then prefixing with "MY_" eats u=
p=20
three more chars I could have used for describing my variable better. =20
Shrugs...

--=20
Roger
http://rogerx.sdf.org/

--v9Ux+11Zm5mwPlX6
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature

-----BEGIN PGP SIGNATURE-----

iQEzBAEBCAAdFiEE9RWsHyMf/E7wvN52Bs6g7OKIfHUFAl4woWEACgkQBs6g7OKI
fHXiawf+NBWNkknWvprUrce5C3ulBiC4ycVumbeyEhjA0t36/YJYg/8XLQ6w4VZM
33/fDZsRPGvB0eoSvJeqXBhwKX/K4wf5dHpzfrZ+H5jrljwQqA8xmYloT5o1Hwq1
wk/5WgQOY6QO5elDbSCYXC+MacOM7Kh+LQaiRBjh2AJX2VSIk6UT0bZINHIQ6huF
l1KG+8VWN8qh0DL4DFl8ji7iaBOzsOBP2JLU/QhJWvdmeTmWzm5pu7itJ8tSTgJC
Yu1GIOXGthnfcAIqt5rtZ72dRPKs9oRQ3vWChw/CNwPC0tWfvs1zdVOx61JC9Vuj
Hii6HkL2JqA+tQxsXNXhh2H/Aaqc3g==
=lre7
-----END PGP SIGNATURE-----

--v9Ux+11Zm5mwPlX6--