Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > gnu.bash.bug > #15858 > unrolled thread

Re: Preventing Bash Variable Confusion

Back to article view | Back to gnu.bash.bug

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Re: Preventing Bash Variable Confusion "Chris F.A. Johnson" <chris@cfajohnson.com> - 2020-01-30 21:13 -0500

#15858 — Re: Preventing Bash Variable Confusion

On Thu, 30 Jan 2020, Roger wrote:

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

A text editor, such as emacs in Bash mode, can highlight variables. No
need to use any sort of naming convention.

-- 
    Chris F.A. Johnson                         <http://cfajohnson.com/>
    =========================== Author: ===============================
    Shell Scripting Recipes: A Problem-Solution Approach (2005, Apress)
    Pro Bash Programming: Scripting the GNU/Linux shell (2009, Apress)

[toc] | [standalone]

Back to top | Article view | gnu.bash.bug

csiph-web