Re: Regular Expression matching operation =~

From	Allodoxaphobia <trepidation@example.net>
Newsgroups	gnu.bash.bug
Subject	Re: Regular Expression matching operation =~
Date	2019-09-23 17:14 +0000
Message-ID	<mailman.911.1569258898.2190.bug-bash@gnu.org> (permalink)
References	<slrnqofqq2.43b.trepidation@vps.jonz.net> <932d9cd1-fcfc-c085-a909-291c4013a9ed@case.edu> <mailman.870.1569244925.2190.bug-bash@gnu.org> <slrnqohvca.gm7.trepidation@vps.jonz.net>

Show all headers | View raw

On Mon, 23 Sep 2019 09:21:44 -0400, Chet Ramey wrote:
> On 9/22/19 5:44 PM, Allodoxaphobia wrote:
>
>> In moving a bash ver. 4.3.48 (Ubuntu) program to a bash ver. 5.0.11
>> (FreeBSD) environment I encountered either a bug, a quirk, or
>> an undocumented feature.
>
> It's not exactly undocumented, more undefined. You can't count on 
> the NUL character or the empty string doing anything in particular.

Thanks.  The "undocumented" action made it so much easier
for some coding logic in my linux/Ubuntu environement. :-)

Thanks, also, to Grisha Levit for more details about the "why".

Regards,
Jonesy
--
  Marvin L Jones    | Marvin      | W3DHJ.net  | linux
   38.238N 104.547W |  @ jonz.net | Jonesy     |  FreeBSD
    * Killfiling google & XXXXbanter.com: jonz.net/ng.htm

Back to gnu.bash.bug | Previous | Next — Previous in thread | Find similar | Unroll thread

Thread

Re: Regular Expression matching operation =~ Chet Ramey <chet.ramey@case.edu> - 2019-09-23 09:21 -0400
  Re: Regular Expression matching operation =~ Allodoxaphobia <trepidation@example.net> - 2019-09-23 17:14 +0000

csiph-web