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


Groups > gnu.bash.bug > #15850

Re: Preventing Bash Variable Confusion

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 15:26:34 -0500
Lines 19
Approved bug-bash@gnu.org
Message-ID <mailman.65.1580329599.2384.bug-bash@gnu.org> (permalink)
References <20200129142305.GX1350@eeg.ccf.org> <20200128210225.GC12574@localhost4.local> <20806.1580277461@jinx.noi.kre.to> <19032.1580321011@jinx.noi.kre.to> <20200129190553.GC5533@localhost4.local> <b9e672cf-9d32-b066-409d-882032cd79ae@case.edu> <20200129202634.GB17112@localhost4.local>
NNTP-Posting-Host lists.gnu.org
Mime-Version 1.0
Content-Type text/plain; charset=us-ascii
X-Trace usenet.stanford.edu 1580329600 21521 209.51.188.17 (29 Jan 2020 20:26:40 GMT)
X-Complaints-To action@cs.stanford.edu
To Chet Ramey <chet.ramey@case.edu>, bug-bash@gnu.org
Envelope-to bug-bash@gnu.org
DKIM-Signature v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=uJD4OGUbJoP/5OTtcBdHL1UbfYMK9UN/cWcvYD1SLCg=; b=RCU33RevUCwf6wKONp3wC7Zc1CosAHurSIaGGei7AwmojeKVHbnX56KJN1CmUJT+2J pWyNYC0OmA7hfYkuwIbNTWd+irqoN1TgI9HstX70CFU/BRJ7LseJXzEfKylmFd5ohWwF AKLbzMResNyWeUcLQhVxIGLvPh210HlHqeMtY8GtnB81qW8QEhzssRpbxBrnQsEHinxE erNnVlgsPMNbq8426DaxhgMfoQ/lQV3Oy7jvsyQ13fHYW7N8MWwCRv91MivOwqry5pwn vJ9qjXmug6HX0SsBvYmxtuY3rvDv1DaZZTW9mmi8kZDL3OKlB6yZb/IqM+HEeejRIdQD 9LKg==
X-Google-DKIM-Signature v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=uJD4OGUbJoP/5OTtcBdHL1UbfYMK9UN/cWcvYD1SLCg=; b=aj2m0dfB2arkFHINE2FdfEGiwU78nW0kD0XvibZgO9K0D5tX+HQgkUZLOtlwc41Bgl XBqw2VGE53ysrBgdw+Ixj2OIZccxaqch8+WUou5vPu83ZObWdJARKMg/irOPF5HM/yXL jbUVfrf+v0E7F7wbtPV7ahOIc0lOMFPreRxQ8He7tsY8TdYWdnOnVRPghRXHwpWiqedv MS+bpVjo7yfl76AP8uTZ9kxg13F0WiuTStF6huXXZAL5ijiHjdzAHXt/k6uAwmGie2s6 vCud/gzJiMUkbwQfpkmalHRORjRbmbSa0swENbnU/N8Cy54NRrOlgm9/8mO3Y7yit7Ao k8Tw==
X-Gm-Message-State APjAAAX+Cnpqb40ZUQTWrJhMgfZ/TNUpYC3xEmAPpu/xwasO9JJL++Hu 8viTBk15w3gSNuPRQpRSL2U=
X-Google-Smtp-Source APXvYqy7GlxVndm68XgvvGdbCs+kd08XMQnK/e2rUVR7e17MEPCYJ5etbNLQ1XsZ8z9CLb/Cd89FBA==
X-Received by 2002:a05:6214:287:: with SMTP id l7mr941371qvv.142.1580329595233; Wed, 29 Jan 2020 12:26:35 -0800 (PST)
Content-Disposition inline
In-Reply-To <b9e672cf-9d32-b066-409d-882032cd79ae@case.edu>
X-PGP-Key http://rogerx.sdf.org/about/armor-F515AC1F231FFC4EF0BCDE7606CEA0ECE2887C75-20170104.asc
User-Agent Mutt/1.10.1 (2018-07-13)
X-detected-operating-system by eggs.gnu.org: Genre and OS details not recognized.
X-Received-From 2607:f8b0:4864:20::f30
X-BeenThere bug-bash@gnu.org
X-Mailman-Version 2.1.23
Precedence list
List-Id Bug reports for the GNU Bourne Again SHell <bug-bash.gnu.org>
List-Unsubscribe <https://lists.gnu.org/mailman/options/bug-bash>, <mailto:bug-bash-request@gnu.org?subject=unsubscribe>
List-Archive <https://lists.gnu.org/archive/html/bug-bash>
List-Post <mailto:bug-bash@gnu.org>
List-Help <mailto:bug-bash-request@gnu.org?subject=help>
List-Subscribe <https://lists.gnu.org/mailman/listinfo/bug-bash>, <mailto:bug-bash-request@gnu.org?subject=subscribe>
X-Mailman-Original-Message-ID <20200129202634.GB17112@localhost4.local>
X-Mailman-Original-References <20200129142305.GX1350@eeg.ccf.org> <20200128210225.GC12574@localhost4.local> <20806.1580277461@jinx.noi.kre.to> <19032.1580321011@jinx.noi.kre.to> <20200129190553.GC5533@localhost4.local> <b9e672cf-9d32-b066-409d-882032cd79ae@case.edu>
Xref csiph.com gnu.bash.bug:15850

Show key headers only | View raw


> On Wed, Jan 29, 2020 at 02:24:11PM -0500, Chet Ramey wrote:
>On 1/29/20 2:05 PM, Roger wrote:
>
>> "Linux Shell Scripting with Bash." (Burtch) suggested using declare instead of 
>> local, due to local lacking the other switches declare provides. p262 (eg.  
>> declare can specify type of variable, such as integar only.)
>
> `local' accepts the same option set as `declare'.

Got it.

$ man bash -> builtin local: "The (local) option can be any of the options 
accepted by declare."


-- 
Roger
http://rogerx.sdf.org/

Back to gnu.bash.bug | Previous | Next | Find similar | Unroll thread


Thread

Re: Preventing Bash Variable Confusion Roger <rogerx.oss@gmail.com> - 2020-01-29 15:26 -0500

csiph-web