Zsh Mailing List Archive Messages sorted by: Reverse Date, Date, Thread, Author

Re: [bug] busyloop upon $=var with NULs when $IFS contains both NUL and a byte > 0x7f

X-seq: zsh-workers 51189
From: Stephane Chazelas <stephane@xxxxxxxxxxxx>
To: "Jun. T" <takimoto-j@xxxxxxxxxxxxxxxxx>
Cc: zsh-workers@xxxxxxx
Subject: Re: [bug] busyloop upon $=var with NULs when $IFS contains both NUL and a byte > 0x7f
Date: Sun, 11 Dec 2022 19:12:57 +0000
Archived-at: <https://zsh.org/workers/51189>
In-reply-to: <AD3B3716-F348-4C93-981F-8B8DD624C37D@kba.biglobe.ne.jp>
List-id: <zsh-workers.zsh.org>
Mail-followup-to: "Jun. T" <takimoto-j@xxxxxxxxxxxxxxxxx>, zsh-workers@xxxxxxx
References: <20221118142717.t4elzrigjeizjm6w@chazelas.org> <AD3B3716-F348-4C93-981F-8B8DD624C37D@kba.biglobe.ne.jp>

2022-11-29 23:27:10 +0900, Jun. T:
[...]
> This not simple to solve. The basic question is:
>    What should we do if IFS contains invalid characters?
[...]

As also mentioned in the read -d $'\200' thread, in some other
parts of the code, bytes that can't be decoded into characters
in the locale's charmap are decoded as a 0xdc00 + byte_value.
(see See workers/36411 workers/36415)

So here, in a UTF-8 locale, IFS=$'\200' could be decoded as a
0xdc80 wchar_t and split on 0xdc80 wchar_t's only in the input
(0x80 byte values not found to be part of a character).

-- 
Stephane

References:
- [bug] busyloop upon $=var with NULs when $IFS contains both NUL and a byte > 0x7f
  - From: Stephane Chazelas
- Re: [bug] busyloop upon $=var with NULs when $IFS contains both NUL and a byte > 0x7f
  - From: Jun. T

Messages sorted by: Reverse Date, Date, Thread, Author