Re: [Issue 8 drafts 0001550]: clarifications/ambiguities in the description of context addresses and their delimiters for sed

On Sat, Apr 2, 2022, at 11:34 PM, Christoph Anton Mitterer via austin-group-l at The Open Group wrote: > Apparently some sed implementations use \+ (and friends) in BREs like + > EREs, while some use it as the literal + . The behavior of things like \+ are explicitly undefined by the BRE

Re: [Issue 8 drafts 0001550]: clarifications/ambiguities in the description of context addresses and their delimiters for sed

On Sun, 2022-04-03 at 05:51 +0300, Oğuz wrote: > 3 Nisan 2022 Pazar tarihinde Christoph Anton Mitterer via austin- > group-l at The Open Group yazdı: > > But many of those extensions made by implementations in areas where > > POSIX doesn't define things, cause IMO quite some trouble in > >

Re: [Issue 8 drafts 0001550]: clarifications/ambiguities in the description of context addresses and their delimiters for sed

3 Nisan 2022 Pazar tarihinde Christoph Anton Mitterer via austin-group-l at The Open Group yazdı: > > But many of those extensions made by implementations in areas where > POSIX doesn't define things, cause IMO quite some trouble in practise. > Such as? -- Oğuz

Re: [Issue 8 drafts 0001550]: clarifications/ambiguities in the description of context addresses and their delimiters for sed

On Sun, 2022-04-03 at 08:41 +0700, Robert Elz via austin-group-l at The Open Group wrote: > Actually there's no reason to forbid them, they simply do > not work.   Applications cannot expect them to work. > That's all that needs to be said. Well than let's not call it forbid, but - as already the

[Issue 8 drafts 0001556]: clarify meaning of \n used in a bracket expression in a sed context address or s-command

A NOTE has been added to this issue. == https://austingroupbugs.net/view.php?id=1556 == Reported By:calestyo Assigned To:

Re: [Issue 8 drafts 0001550]: clarifications/ambiguities in the description of context addresses and their delimiters for sed

Date:Sat, 2 Apr 2022 19:47:44 + From:Austin Group Bug Tracker Message-ID: | That indented paragraph of yours (in Note 0005775) should (if at all) | only go to the Rationale, IMO. That's fine. | Cause for the purpose of the standard itself it's not really

[Issue 8 drafts 0001550]: clarifications/ambiguities in the description of context addresses and their delimiters for sed

A NOTE has been added to this issue. == https://austingroupbugs.net/view.php?id=1550 == Reported By:calestyo Assigned To:

[1003.1(2016/18)/Issue7+TC2 0001546]: BREs: reserve \? \+ and \|

A NOTE has been added to this issue. == https://austingroupbugs.net/view.php?id=1546 == Reported By:calestyo Assigned To:

[Issue 8 drafts 0001550]: clarifications/ambiguities in the description of context addresses and their delimiters for sed

A NOTE has been added to this issue. == https://austingroupbugs.net/view.php?id=1550 == Reported By:calestyo Assigned To:

[Issue 8 drafts 0001551]: sed: ambiguities in the how BREs/EREs are parsed/interpreted between delimiters (especially when these are special characters)

A NOTE has been added to this issue. == https://austingroupbugs.net/view.php?id=1551 == Reported By:calestyo Assigned To:

[1003.1(2016/18)/Issue7+TC2 0001546]: BREs: reserve \? \+ and \|

A NOTE has been added to this issue. == https://austingroupbugs.net/view.php?id=1546 == Reported By:calestyo Assigned To: