From: Peter Stephenson <p.w.stephenson@ntlworld.com>
To: zsh-workers@zsh.org
Subject: Re: [bug] busyloop upon $=var with NULs when $IFS contains both NUL and a byte > 0x7f
Date: Tue, 13 Dec 2022 11:55:55 +0000 (GMT) [thread overview]
Message-ID: <946835209.7082170.1670932555405@mail.virginmedia.com> (raw)
In-Reply-To: <7910F067-9694-432B-9890-2BA25692C2C9@kba.biglobe.ne.jp>
> On 13/12/2022 11:40 Jun T <takimoto-j@kba.biglobe.ne.jp> wrote:
>
>
> > 2022/12/13 19:13, Peter Stephenson <p.w.stephenson@ntlworld.com> wrote:
> >
> >> On 13/12/2022 09:49 Jun T <takimoto-j@kba.biglobe.ne.jp> wrote:
> >>
> >> How can we 'give up'? Is it OK to call exit()?
> >
> > By giving up, I meant we stop splitting at that point and leave the
> > rest of the string intact. If splitting fails, stop splitting...
>
> If we modify wordcount() in this way, then we also need to modify
> at least sepsplit() and spacesplit()?
Right, this would have to be a general policy.
I'm not necessarily hooked on this way of doing it; it seems to
me it's a little bit less surprising than resetting IFS but I
suppose errors are always surprising.
pws
next prev parent reply other threads:[~2022-12-13 11:56 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-18 14:27 Stephane Chazelas
2022-11-29 14:27 ` Jun. T
2022-11-29 14:38 ` Peter Stephenson
2022-11-30 4:20 ` Bart Schaefer
2022-11-30 9:21 ` Peter Stephenson
2022-12-13 9:50 ` Jun T
2022-12-13 9:49 ` Jun T
2022-12-13 10:13 ` Peter Stephenson
2022-12-13 11:40 ` Jun T
2022-12-13 11:55 ` Peter Stephenson [this message]
2023-06-21 4:49 ` Jun T
2022-12-11 19:12 ` Stephane Chazelas
2022-12-13 9:51 ` Jun T
2022-11-30 14:56 ` Jun. T
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=946835209.7082170.1670932555405@mail.virginmedia.com \
--to=p.w.stephenson@ntlworld.com \
--cc=zsh-workers@zsh.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).