help-bash
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: non working code .. loop ends after one


From: alex xmb ratchev
Subject: Re: non working code .. loop ends after one
Date: Thu, 2 Mar 2023 01:09:47 +0100

On Thu, Mar 2, 2023, 12:39 AM Lawrence Velázquez <vq@larryv.me> wrote:

> On Wed, Mar 1, 2023, at 6:20 PM, Greg Wooledge wrote:
> > If the option argument is the empty string (-d '' or -d ""), then
> > the NUL byte is used as the line delimiter.
> >
> > This is most likely a side effect of bash's internal code just doing
> > something like 'delimiter = argument[0];' which happens to retrieve
> > a NUL byte when argument is an empty string, due to how C strings are
> > stored internally.
> >
> > Regardless of whether this was an accident originally, Chet has blessed
> > it, and it's officially a supported feature now.
>
> It will also be in the next version of POSIX:
> https://austingroupbugs.net/view.php?id=243#c6110


there is imo ' big undefined ' there
they state , to change to , ' if {} is one char '
what if more than one


> --
> vq
>
>


reply via email to

[Prev in Thread] Current Thread [Next in Thread]