[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: declare a="$b" if $a previously set as array

From: konsolebox
Subject: Re: declare a="$b" if $a previously set as array
Date: Wed, 10 Dec 2014 06:51:17 +0800

On Tue, Dec 9, 2014 at 7:29 AM, Linda Walsh <address@hidden> wrote:

>         Instead of dumbing down bash, why not lobby for bash to record
> which variables contain tainted input -- and throw an error they are eval'ed
> (based on an option setting, of course)?

For compatibility's sake I think it's a good idea to have an option
(through shopt [and set / a command-line argument]) to make a strict
behavior of declare in which assignment of variables are strictly the
same as the way they are normally assigned without it.

And I don't see it as dumbing down, but more of correcting.  To me it's
actually a wrong implementation more than a feature (i.e. having a
builtin-like behavior like test / unset over a reserved word like
behavior like [[ ]].

If there would have been a tool for that, it can never be declare as its
function to me would give conflict.  Better have another builtin tool
for it that behaves similar to what I suggested before.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]