bug#15483: POSIXLY_CORRECT documentation vis a vis some simple EREs

2013-09-28 Thread Glenn Golden
-- Regarding EREs having leading repetition operators, e.g. '*xyz': Section 9.5.3 of http://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap09.html supplies the grammar for POSIX-conforming EREs. From the notes at the very bottom: --

bug#15483: POSIXLY_CORRECT documentation vis a vis some simple EREs

2013-09-29 Thread Glenn Golden
-- Eric Blake Sat, 28 Sep 2013 17:17:50 -0600: > > the intent of POSIXLY_CORRECT is only to change behavior where we do > not comply with the requirements by default. > OK, that's a good start at clarifying the intent of POSIXLY_CORRECT, and glad to see it. IMO it would be worthwhile for us to h

bug#15486: Should references to POSIX.2 in grep.1 be changed?

2013-09-29 Thread Glenn Golden
-- (This came up as a side issue when looking into details of bug #15483; it's not directly related, so filing as a separate report.) There's a FAQ put out by opengroup.org http://www.opengroup.org/austin/papers/posix_faq.html which remarks (Q10) that "a POSIX.2 standard no longer exists".

bug#15483: POSIXLY_CORRECT documentation vis a vis some simple EREs

2013-09-30 Thread Glenn Golden
-- Paul Eggert [2013-09-29 16:53:21 -0700]: > Glenn Golden wrote: > > Per the final sentence of 9.5.3, "conforming applications cannot use > > [constructs like '*xyz']" > > This is making the incorrect assumption that 'grep' internally m

bug#15483: POSIXLY_CORRECT documentation vis a vis some simple EREs

2013-10-07 Thread Glenn Golden
ses well-defined within POSIX (single-quotes used). Paul Eggert [2013-09-29 16:53:21 -0700]: > Glenn Golden wrote: > > Per the final sentence of 9.5.3, "conforming applications cannot use > > [constructs like '*xyz']" > > This is making the incorrect assum

bug#15483: POSIXLY_CORRECT documentation vis a vis some simple EREs

2013-10-07 Thread Glenn Golden
-- Eric Blake [2013-10-07 11:05:09 -0600]: > > So what? No one cares whether grep is a 'conforming application', > Disagree strongly that "no one" cares. > > Our counterargument is that we KNOW that grep in not a conforming application, > and WE DON'T CARE. > >From your perspective as develop

bug#15483: POSIXLY_CORRECT documentation vis a vis some simple EREs

2013-10-14 Thread Glenn Golden
-- Yes boys and girls, it's Monday, time again for our next episode of... POSIX Pedantry... We left our intrepid heros poised on the edge of conformance eternity, with Eric suggesting that Glenn raise various questions on the POSIX mailing list... I did so, initially just asking about the interpr

bug#15483: POSIXLY_CORRECT documentation vis a vis some simple EREs

2013-10-14 Thread Glenn Golden
-- Paul Eggert [2013-10-14 10:53:13 -0700]: > > I wouldn't bother with grep.1, as it's not the real documentation. > Instead, I suggest a patch against the grep manual, which is > in Texinfo format. > > I suggest adding something to the paragraph that talks about POSIXLY_CORRECT. > Good idea, I

bug#72246: Possible PCRE bug in grep 3.11

2024-07-22 Thread Glenn Golden
rg/archive/html/grep-devel/2023-03/msg00017.html which references a regression in 3.10. Figured it was worthwhile to report even it may be a duplicate. Version info: Arch64 linux, kernel 6.1.68, commodity x86-64 laptop. - Glenn Golden == BEG

bug#72246: Possible PCRE bug in grep 3.11

2024-07-22 Thread Glenn Golden
Paul Eggert [2024-07-22 12:00:21 -0700]: > On 2024-07-22 11:25, Glenn Golden wrote: > > str=$(printf "begin\xe2\x80\x99end") > > > > # > > # grep 3.11 using PCRE '[\x80-\xFF]' doesn't find any of them, > > # and exits with 1, indicating