Path: csiph.com!xmission!news.snarked.org!news.linkpendium.com!news.linkpendium.com!panix!usenet.stanford.edu!not-for-mail
From: Uriel <url.15.104@gmail.com>
Newsgroups: gnu.bash.bug
Subject: Conditions with logical operators and nested groups execute "if" and "else"
Date: Mon, 21 May 2018 16:17:18 -0500
Lines: 86
Approved: bug-bash@gnu.org
Message-ID: <mailman.206.1526969874.1292.bug-bash@gnu.org>
NNTP-Posting-Host: lists.gnu.org
Mime-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
To: bug-bash@gnu.org, bash@packages.debian.org
Envelope-to: bug-bash@gnu.org
Precedence: list
Xref: csiph.com gnu.bash.bug:14125

Configuration Information:
Machine: x86_64
OS: linux-gnu
Compiler: gcc
Compilation CFLAGS:  -DPROGRAM=3D'bash' -DCONF_HOSTTYPE=3D'x86_64'
-DCONF_OSTYPE=3D'linux-gnu' -DCONF_MACHTYPE=3D'x86_64-pc-linux-gnu'
-DCONF_VENDOR=3D'pc' -DLOCALEDIR=3D'/usr/share/locale' -DPACKAGE=3D'bash' -=
DSHELL
-DHAVE_CONFIG_H   -I.  -I../. -I.././include -I.././lib  -Wdate-time
-D_FORTIFY_SOURCE=3D2 -g -O2
-fdebug-prefix-map=3D/build/bash-DWMIDv/bash-4.4.18=3D.
-fstack-protector-strong -Wformat -Werror=3Dformat-security -Wall
-Wno-parentheses -Wno-format-security
uname output: Linux HPgS 4.9.0-6-amd64 #1 SMP Debian 4.9.88-1+deb9u1
(2018-05-07) x86_64 GNU/Linux
Machine Type: x86_64-pc-linux-gnu

Bash Version: 4.4
Patch Level: 19
Release Status: release

Description:
As you know, a conditional is of the type:
if [[ EXPRESSION ]]; then TRUE CONDITION; else ALTERNATIVE RESULT; fi

Or with logical operators and groups:

[[ EXPRESSION ]]; && { TRUE CONDITION; } || { ALTERNATIVE RESULT; }

Within each of the conditionals there may be more nested, written the first
or
second way they should give the same result, however, using the logical
operators form to obfuscate the code a little, I find that my conditional
(which has another one in it) is executed in the first condition and also
in the
second one. Analyzing for a long time if it was a mistake in rewriting I sa=
w
that it worked the same way, the problem seems to be one of the operator
=C2=AB!=C2=BB in
a =C2=AB=3D~=C2=BB conditional because when testing this same notation with=
 other
conditions
it does not seem to have an error.

Repeat-By:
#!/bin/bash
# In the second example passing through =C2=AB[[ ! "$OPT" =3D~ ^- ]] && {
OPT=3D"-$OPT"; }=C2=BB should end, however, it continues with the following

OPT=3D"-e-e-e--debug"; OPT_PERFECT=3D"-e"

echo "INICIAL $OPT"

if [[ "$OPT" =3D~ ^- ]]; then
    OPT=3D"${OPT#$OPT_PERFECT}"
    echo "REDUCCION TIPO 1 $OPT"
    if [[ ! "$OPT" =3D~ ^- ]]; then
        OPT=3D"-$OPT"
        echo "CONDICIONAL $OPT"
    fi
else
   OPT=3D"${OPT#$OPT_PERFECT}"
   echo "REDUCCION TIPO 2 $OPT"
fi

echo "----------------------------------------------"

OPT=3D"-e-e-e--debug"; OPT_PERFECT=3D"-e"

echo "INICIAL $OPT"

[[ "$OPT" =3D~ ^- ]] && {
    OPT=3D"${OPT#$OPT_PERFECT}"
    echo "REDUCCION TIPO 1 $OPT"
    [[ ! "$OPT" =3D~ ^- ]] && {
        OPT=3D"-$OPT"
    }
} || {
   OPT=3D"${OPT#$OPT_PERFECT}"
   echo "REDUCCION TIPO 2 $OPT"
}

Fix:
No big deal, you can use operator alternatives instead of
=C2=AB[[ ! "$OPT" =3D~ ^- ]] && { OPT=3D"-$OPT"; }=C2=BB you can use
=C2=AB[[ "$OPT" =3D~ ^- ]] || { OPT=3D"-$OPT"; }=C2=BB.