Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > gnu.bash.bug > #15850
| From | Roger <rogerx.oss@gmail.com> |
|---|---|
| Newsgroups | gnu.bash.bug |
| Subject | Re: Preventing Bash Variable Confusion |
| Date | 2020-01-29 15:26 -0500 |
| Message-ID | <mailman.65.1580329599.2384.bug-bash@gnu.org> (permalink) |
| References | (2 earlier) <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> |
> 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
Re: Preventing Bash Variable Confusion Roger <rogerx.oss@gmail.com> - 2020-01-29 15:26 -0500
csiph-web