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


Groups > gnu.bash.bug > #14853

Re: null array[*] expansion not treated as null

Path csiph.com!goblin1!goblin.stu.neva.ru!usenet.stanford.edu!not-for-mail
From L A Walsh <bash@tlinx.org>
Newsgroups gnu.bash.bug
Subject Re: null array[*] expansion not treated as null
Date Sun, 25 Nov 2018 12:02:41 -0800
Lines 68
Approved bug-bash@gnu.org
Message-ID <mailman.4610.1543176177.1284.bug-bash@gnu.org> (permalink)
References <CAMu=BrrfCCe9VevjQ9_=UcKQUWTVZ_beqzhqZk617h=wSOj58w@mail.gmail.com>
NNTP-Posting-Host lists.gnu.org
Mime-Version 1.0
Content-Type text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding quoted-printable
X-Trace usenet.stanford.edu 1543176178 1047 208.118.235.17 (25 Nov 2018 20:02:58 GMT)
X-Complaints-To action@cs.stanford.edu
Cc bug-bash <bug-bash@gnu.org>
To Grisha Levit <grishalevit@gmail.com>
Envelope-to bug-bash@gnu.org
User-Agent Thunderbird
In-Reply-To <CAMu=BrrfCCe9VevjQ9_=UcKQUWTVZ_beqzhqZk617h=wSOj58w@mail.gmail.com>
X-MIME-Autoconverted from 8bit to quoted-printable by Ishtar.sc.tlinx.org id wAPK2fHn019513
X-detected-operating-system by eggs.gnu.org: GNU/Linux 2.2.x-3.x (no timestamps) [generic] [fuzzy]
X-Received-From 173.164.175.65
X-BeenThere bug-bash@gnu.org
X-Mailman-Version 2.1.21
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 <http://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>
Xref csiph.com gnu.bash.bug:14853

Show key headers only | View raw


On 11/12/2018 1:32 PM, Grisha Levit wrote:
> When an array A has non-zero elements but the expansion of "${A[*]}" is
> still
> a null string, it is not treated as such for purposes of ${var:-X} expansion
> (though $* is treated as null in the same circumstance).
>
>     $ A=(''); set -- ''
>     $ echo "<${A[*]:-X}>" "<${*:-X}>"
>     <> <X>
>   
----
    Ah, a null string != empty.  Example:
>  A=()
>  declare -p A
declare -a A=()
>  A=('')                #null string
>  declare -p A
declare -a A=([0]="")    #a string is still a string, even if empty

Related:

FWIW, below, "IFS=" sets IFS to an empty string, like
IFS=''
>     $ IFS=
>     $ A=('' ''); set -- '' '';
>   
Typing in lines to echo the size of A and shell params:

>  echo "=$#"   ; echo number of parameters set by "set - '' ''"
=2
>  echo "size of A=${#A[@]}"
size of A=2

>     $ echo "<${A[*]:-X}>" "<${*:-X}>"
>     <> <X>
>   
---
    Going to use "«»" instead of "<>" cuz <> are shell chars that
need quoting (  otherwise: bash: syntax error near unexpected token `<'  ).

First, your echo:

>  echo "«${A[*]:-X}»" "«${*:-X}»"   
«» «X»            (#same)

and w/o the quotes:
>  echo «${A[*]:-X}» «${*:-X}»
« » « »

---
Notice adding quotes around your vars can change what is
echo'ed.  Looks like the output-separator ' ' (space) is
embedded in the '*'s of both expressions, but [*] undergoes
expansion, while the 2nd one doesn't.

So 1 hint to remember a variable is an internally quoted entity, such
if it is assigned to another var, it will be assigned "as-is", but
if you put double-quotes around a variable, it will replace sequences
of white space with 1 white space.

Does that address your examples' behaviors?

of some sort where '*'«»

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


Thread

Re: null array[*] expansion not treated as null L A Walsh <bash@tlinx.org> - 2018-11-25 12:02 -0800

csiph-web