Re: No word splitting for assignment-like expressions in compound assignment

Path	csiph.com!xmission!news.snarked.org!news.linkpendium.com!news.linkpendium.com!panix!usenet.stanford.edu!not-for-mail
From	Lawrence Velázquez <vq@larryv.me>
Newsgroups	gnu.bash.bug
Subject	Re: No word splitting for assignment-like expressions in compound assignment
Date	Mon, 27 Jul 2020 18:19:09 -0400
Lines	19
Approved	bug-bash@gnu.org
Message-ID	<mailman.168.1595888356.2739.bug-bash@gnu.org> (permalink)
References	<87o8o1zfpn.fsf@hobgoblin.ariadne.com> <F420E583-E5D4-48BB-98E3-044C700BA07A@larryv.me> <87pn8hs7wd.fsf@igel.home> <EC80FDF6-835B-41BE-89F7-51B3F25C3D38@larryv.me>
NNTP-Posting-Host	lists.gnu.org
Mime-Version	1.0 (Mac OS X Mail 12.4 \(3445.104.14\))
Content-Type	text/plain; charset=utf-8
Content-Transfer-Encoding	quoted-printable
X-Trace	usenet.stanford.edu 1595888356 10776 209.51.188.17 (27 Jul 2020 22:19:16 GMT)
X-Complaints-To	action@cs.stanford.edu
Cc	"Dale R. Worley" <worley@alum.mit.edu>, Alexey Izbyshev <izbyshev@ispras.ru>, bug-bash@gnu.org
To	Andreas Schwab <schwab@linux-m68k.org>
Envelope-to	bug-bash@gnu.org
DKIM-Signature	v=1; a=rsa-sha256; c=relaxed/relaxed; d=larryv.me; h= content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; s=fm1; bh=/ 65cUNc2vMagaW2Yb46O5C5APC/07R5j/puImCQvYrQ=; b=Pc4uPX/QlHx62lDwI Lw/MGxLlg/en7okoMIWi26ZJUyTr1bnZi2f3rwIQR6M4mMH4M3vpQS7uh9MJSMJd chJi4fyIXT7kVNOCXWi5eQvMd+e1GwAIG+tc8s4z0yiyAmXdixdqE0H1NNyPvam7 Jim2yM5eabrYqszhXxEAXnCyV1MG9cSCakebtNsb+UwOQuETBoVLiZaAoGQDMnEh Kx0VrGYWQlmKHYtJoGraSqx9YtYOtsWrzxglfyMBFVfIVvKWij3ofvEN3p245NQe f1B0WxDKPx9AamR4hOb1aZQPim174z0RyERrs0FKmLZpV2zicPTVjL02zFgpkK+s 80Bdg==
DKIM-Signature	v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm3; bh=/65cUNc2vMagaW2Yb46O5C5APC/07R5j/puImCQvY rQ=; b=an5Zg8Wq9VH1dRyFRAS/oeSh1Nr1t6LWKc549murmgSGKe5FvkgpowVwi 7UmcMzfHyObftqQhbMJeeNOctTNthUuWcaGxGrzQ6U5yjP3HKKs7db5Ywf60Fktt TD+mcUQi6ojTrs1E+oIl7j3suhszwrOV3+Ze5akEnob5Afrh1zixrK1OCK5GkFj8 jcx3nMuwimLf3yfkykl6egUtyYy/3Byv827iEuD5e77wA81+XU8TcyJl66fx4fqt Hc1N12jIGBAw1Nl9dABBl6AulwNRIFCXMK2n0LMRC6Z9ovFNABiSi29Ru5vrvEbX uoAnIbaL+SWZEvdNRUT5Hi60Mu69w==
X-ME-Sender	<xms:3lIfXy5IUatsKjJV5uyb_Wtc6gPMv6KXH-AkQ3AekuaN3y-bYU8now>
X-ME-Proxy-Cause	gggruggvucftvghtrhhoucdtuddrgeduiedriedugddtjecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpegtggfuhfgjfffgkfhfvffosehtqhhmtdhhtdejnecuhfhrohhmpefnrgifrhgv nhgtvggpgggvlhojiihquhgviicuoehvqheslhgrrhhrhihvrdhmvgeqnecuggftrfgrth htvghrnhepudekjedtleehvdduhfevleegteffteekhedvheejteelffdvgedtjedvueeu geeinecukfhppedutddtrdduvddrudejkedrvdefnecuvehluhhsthgvrhfuihiivgeptd enucfrrghrrghmpehmrghilhhfrhhomhepvhhqsehlrghrrhihvhdrmhgv
X-ME-Proxy	<xmx:3lIfX74r064PCWer9bqXOPNuyz0zUyNJNaCUPI0zuDDh16r8btKpHg> <xmx:3lIfXxesvjfhn53x23C1Ha4rRVPH1ULSlvGFFSiWtuQGxPGbUmV95A> <xmx:3lIfX_Jb4-aAagkCxJ5mbcl57XByG2eWQmxiTL-WKt5Qy_VRmULXAg> <xmx:4FIfXwyVFu3BZxws-zpKIMtA14cPXeT0pwt40esvVfwcBx2zHxJNqQ>
In-Reply-To	<87pn8hs7wd.fsf@igel.home>
X-Mailer	Apple Mail (2.3445.104.14)
Received-SPF	pass client-ip=66.111.4.29; envelope-from=vq@larryv.me; helo=out5-smtp.messagingengine.com
X-detected-operating-system	by eggs.gnu.org: First seen = 2020/07/27 18:19:12
X-ACL-Warn	Detected OS = Linux 2.2.x-3.x [generic] [fuzzy]
X-Spam_score_int	-27
X-Spam_score	-2.8
X-Spam_bar	--
X-Spam_report	(-2.8 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001 autolearn=ham autolearn_force=no
X-Spam_action	no action
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	<EC80FDF6-835B-41BE-89F7-51B3F25C3D38@larryv.me>
X-Mailman-Original-References	<87o8o1zfpn.fsf@hobgoblin.ariadne.com> <F420E583-E5D4-48BB-98E3-044C700BA07A@larryv.me> <87pn8hs7wd.fsf@igel.home>
Xref	csiph.com gnu.bash.bug:16630

Show key headers only | View raw

> On Jul 27, 2020, at 4:02 AM, Andreas Schwab <schwab@linux-m68k.org> wrote:
> 
> On Jul 27 2020, Lawrence Velázquez wrote:
> 
>> If word splitting were not performed in compound assignments, this...
>> 
>>    foo=(a b c)
>> 
>> ...would not work.
> 
> This is not true.  Field splitting is only relevant for words generated
> by other expansions, not for literal tokens.

My fault, I got it mixed up with tokenization. Carry on!

vq

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

Thread

Re: No word splitting for assignment-like expressions in compound assignment Lawrence Velázquez <vq@larryv.me> - 2020-07-27 18:19 -0400

csiph-web