[1003.1(2016/18)/Issue7+TC2 0001546]: BREs: reserve \? \+ and \|
The following issue has a resolution that has been APPLIED. == https://austingroupbugs.net/view.php?id=1546 == Reported By:calestyo Assigned To: == Project:1003.1(2016/18)/Issue7+TC2 Issue ID: 1546 Category: Base Definitions and Headers Type: Enhancement Request Severity: Editorial Priority: normal Status: Applied Name: Christoph Anton Mitterer Organization: User Reference: Section:9.3 Basic Regular Expressions Page Number:N/A Line Number:N/A Interp Status: --- Final Accepted Text:https://austingroupbugs.net/view.php?id=1546#c5755 Resolution: Accepted As Marked Fixed in Version: == Date Submitted: 2022-01-08 03:48 UTC Last Modified: 2022-05-19 09:15 UTC == Summary:BREs: reserve \? \+ and \| == Relationships ID Summary -- has duplicate 773 Summary: Add \+, \?, and \| to Basic Re... == Issue History Date ModifiedUsername FieldChange == 2022-01-08 03:48 calestyo New Issue 2022-01-08 03:48 calestyo Name => Christoph Anton Mitterer 2022-01-08 03:48 calestyo Section => 9.3 Basic Regular Expressions 2022-01-08 03:48 calestyo Page Number => N/A 2022-01-08 03:48 calestyo Line Number => N/A 2022-01-28 11:21 mirabilos Note Added: 0005636 2022-01-28 23:10 calestyo Note Added: 0005639 2022-03-03 06:56 Don Cragun Note Added: 0005731 2022-03-03 07:03 Don Cragun Note Edited: 0005731 2022-03-10 17:09 geoffclare Note Added: 0005738 2022-03-10 17:09 geoffclare Interp Status => --- 2022-03-10 17:09 geoffclare Final Accepted Text => https://austingroupbugs.net/view.php?id=1546#c5738 2022-03-10 17:09 geoffclare Status New => Resolved 2022-03-10 17:09 geoffclare Resolution Open => Accepted As Marked 2022-03-10 17:10 geoffclare Tag Attached: issue8 2022-03-10 17:44 calestyo Note Added: 0005740 2022-03-12 21:01 Don Cragun Relationship added related to 773 2022-03-12 21:12 calestyo Note Added: 0005744 2022-03-12 21:13 calestyo Note Edited: 0005744 2022-03-14 10:08 geoffclare Note Added: 0005748 2022-03-14 10:08 geoffclare Status Resolved => Under Review 2022-03-14 10:08 geoffclare Resolution Accepted As Marked => Reopened 2022-03-14 13:50 calestyo Note Added: 0005749 2022-03-14 14:31 geoffclare Note Added: 0005750 2022-03-18 09:32 geoffclare Note Added: 0005755 2022-03-24 15:29 geoffclare Final Accepted Text https://austingroupbugs.net/view.php?id=1546#c5738 => https://austingroupbugs.net/view.php?id=1546#c5755 2022-03-24 15:29 geoffclare Status Under Review => Resolved 2022-03-24 15:29 geoffclare Resolution Reopened => Accepted As Marked 2022-03-24 15:34 geoffclare Relationship replacedhas duplicate 773 2022-03-25 22:41 calestyo Note Added: 0005765 2022-03-25 22:57 calestyo Note Added: 0005766 2022-03-31 15:06 geoffclare Note Edited: 0005755 2022-03-31 15:07 geoffclare Note Edited: 0005755 2022-03-31 15:08 geoffclare Note Added: 0005768 2022-04-01 22:22 calestyo Note Added: 0005770 2022-04-02 08:17 kreNote Added: 0005773 2022-04-02 08:19 kreNote Edited: 0005773 2022-04-02 08:22 kre
Re: [1003.1(2016/18)/Issue7+TC2 0001546]: BREs: reserve \? \+ and \|
On Thu, 2022-04-07 at 16:26 -0700, Don Cragun wrote: > Note that the definition of "escape sequence" is being added in > section 9.1 (titled" Regular Expression Definitions") in the Base > Definitions Volume of the standard; not in Section 3 where > definitions go that pertain to the entire standard. Uhm... yes... isn't that what I pointed out again (or at least tried to ^^)? Cause I saw Robert's idea that in the mailing list thread about issue #1550, where, as far as I understood him, he thought about having such definition standard-wide (like in the Definitions chapter)? btw: I'll still need till next week to look into Geoff's replies to my last comments in #1550. Cheers, Chris.
Re: [1003.1(2016/18)/Issue7+TC2 0001546]: BREs: reserve \? \+ and \|
Hey Chris, Note that the definition of "escape sequence" is being added in section 9.1 (titled" Regular Expression Definitions") in the Base Definitions Volume of the standard; not in Section 3 where definitions go that pertain to the entire standard. Cheers, Don > On Apr 7, 2022, at 4:05 PM, Christoph Anton Mitterer via austin-group-l at > The Open Group wrote: > > Hey. > > btw: It should not be forgotten, that this definition of escape > sequence/character, escaped character is in principle only valid for > the RE chapter. Except of course, something explicitly refers to that > or - like with sed - extends the RE language. > > Just wanted to point that out again, to be kept in mind,... when the > same terms are used in other places of the standard. > > > Apart from that,... thanks Goff and Robert for your efforts in this > issue. > > > Cheers, > Chris. > >
Re: [1003.1(2016/18)/Issue7+TC2 0001546]: BREs: reserve \? \+ and \|
Hey. btw: It should not be forgotten, that this definition of escape sequence/character, escaped character is in principle only valid for the RE chapter. Except of course, something explicitly refers to that or - like with sed - extends the RE language. Just wanted to point that out again, to be kept in mind,... when the same terms are used in other places of the standard. Apart from that,... thanks Goff and Robert for your efforts in this issue. Cheers, Chris.
[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: == Project:1003.1(2016/18)/Issue7+TC2 Issue ID: 1546 Category: Base Definitions and Headers Type: Enhancement Request Severity: Editorial Priority: normal Status: Resolved Name: Christoph Anton Mitterer Organization: User Reference: Section:9.3 Basic Regular Expressions Page Number:N/A Line Number:N/A Interp Status: --- Final Accepted Text:https://austingroupbugs.net/view.php?id=1546#c5755 Resolution: Accepted As Marked Fixed in Version: == Date Submitted: 2022-01-08 03:48 UTC Last Modified: 2022-04-07 23:01 UTC == Summary:BREs: reserve \? \+ and \| == Relationships ID Summary -- has duplicate 773 Summary: Add \+, \?, and \| to Basic Re... == -- (0005788) calestyo (reporter) - 2022-04-07 23:01 https://austingroupbugs.net/view.php?id=1546#c5788 -- AFAICS, you just changed the definition of escape sequence... and there it seems you took the proposal from the mailing list with the addition of ", which is thereby ``escaped''." (which fits nicely, IMO), right? >From my side this issue would be fixed now,... let's set a timer for 10 years to re-visit the question whether the literal meaning choice can be skipped O;-) Thanks for your efforts in this matter! :-) Issue History Date ModifiedUsername FieldChange == 2022-01-08 03:48 calestyo New Issue 2022-01-08 03:48 calestyo Name => Christoph Anton Mitterer 2022-01-08 03:48 calestyo Section => 9.3 Basic Regular Expressions 2022-01-08 03:48 calestyo Page Number => N/A 2022-01-08 03:48 calestyo Line Number => N/A 2022-01-28 11:21 mirabilos Note Added: 0005636 2022-01-28 23:10 calestyo Note Added: 0005639 2022-03-03 06:56 Don Cragun Note Added: 0005731 2022-03-03 07:03 Don Cragun Note Edited: 0005731 2022-03-10 17:09 geoffclare Note Added: 0005738 2022-03-10 17:09 geoffclare Interp Status => --- 2022-03-10 17:09 geoffclare Final Accepted Text => https://austingroupbugs.net/view.php?id=1546#c5738 2022-03-10 17:09 geoffclare Status New => Resolved 2022-03-10 17:09 geoffclare Resolution Open => Accepted As Marked 2022-03-10 17:10 geoffclare Tag Attached: issue8 2022-03-10 17:44 calestyo Note Added: 0005740 2022-03-12 21:01 Don Cragun Relationship added related to 773 2022-03-12 21:12 calestyo Note Added: 0005744 2022-03-12 21:13 calestyo Note Edited: 0005744 2022-03-14 10:08 geoffclare Note Added: 0005748 2022-03-14 10:08 geoffclare Status Resolved => Under Review 2022-03-14 10:08 geoffclare Resolution Accepted As Marked => Reopened 2022-03-14 13:50 calestyo Note Added: 0005749 2022-03-14 14:31 geoffclare Note Added: 0005750 2022-03-18 09:32 geoffclare Note Added: 0005755 2022-03-24 15:29 geoffclare Final Accepted Text https://austingroupbugs.net/view.php?id=1546#c5738 => https://austingroupbugs.net/view.php?id=1546#c5755 2022-03-24 15:29 geoffclare Status Under Review => Resolved 2022-03-24 15:29 geoffclare Resolution Reopened => Accepted As Marked 2022-03-24 15:34 geoffclare Relationship replacedhas duplicate 773
[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: == Project:1003.1(2016/18)/Issue7+TC2 Issue ID: 1546 Category: Base Definitions and Headers Type: Enhancement Request Severity: Editorial Priority: normal Status: Resolved Name: Christoph Anton Mitterer Organization: User Reference: Section:9.3 Basic Regular Expressions Page Number:N/A Line Number:N/A Interp Status: --- Final Accepted Text:https://austingroupbugs.net/view.php?id=1546#c5755 Resolution: Accepted As Marked Fixed in Version: == Date Submitted: 2022-01-08 03:48 UTC Last Modified: 2022-04-07 15:09 UTC == Summary:BREs: reserve \? \+ and \| == Relationships ID Summary -- has duplicate 773 Summary: Add \+, \?, and \| to Basic Re... == -- (0005783) geoffclare (manager) - 2022-04-07 15:09 https://austingroupbugs.net/view.php?id=1546#c5783 -- In the April 7th teleconference, the resolution in https://austingroupbugs.net/view.php?id=1546#c5755 was updated to change the "escape sequence" definition (again). Issue History Date ModifiedUsername FieldChange == 2022-01-08 03:48 calestyo New Issue 2022-01-08 03:48 calestyo Name => Christoph Anton Mitterer 2022-01-08 03:48 calestyo Section => 9.3 Basic Regular Expressions 2022-01-08 03:48 calestyo Page Number => N/A 2022-01-08 03:48 calestyo Line Number => N/A 2022-01-28 11:21 mirabilos Note Added: 0005636 2022-01-28 23:10 calestyo Note Added: 0005639 2022-03-03 06:56 Don Cragun Note Added: 0005731 2022-03-03 07:03 Don Cragun Note Edited: 0005731 2022-03-10 17:09 geoffclare Note Added: 0005738 2022-03-10 17:09 geoffclare Interp Status => --- 2022-03-10 17:09 geoffclare Final Accepted Text => https://austingroupbugs.net/view.php?id=1546#c5738 2022-03-10 17:09 geoffclare Status New => Resolved 2022-03-10 17:09 geoffclare Resolution Open => Accepted As Marked 2022-03-10 17:10 geoffclare Tag Attached: issue8 2022-03-10 17:44 calestyo Note Added: 0005740 2022-03-12 21:01 Don Cragun Relationship added related to 773 2022-03-12 21:12 calestyo Note Added: 0005744 2022-03-12 21:13 calestyo Note Edited: 0005744 2022-03-14 10:08 geoffclare Note Added: 0005748 2022-03-14 10:08 geoffclare Status Resolved => Under Review 2022-03-14 10:08 geoffclare Resolution Accepted As Marked => Reopened 2022-03-14 13:50 calestyo Note Added: 0005749 2022-03-14 14:31 geoffclare Note Added: 0005750 2022-03-18 09:32 geoffclare Note Added: 0005755 2022-03-24 15:29 geoffclare Final Accepted Text https://austingroupbugs.net/view.php?id=1546#c5738 => https://austingroupbugs.net/view.php?id=1546#c5755 2022-03-24 15:29 geoffclare Status Under Review => Resolved 2022-03-24 15:29 geoffclare Resolution Reopened => Accepted As Marked 2022-03-24 15:34 geoffclare Relationship replacedhas duplicate 773 2022-03-25 22:41 calestyo Note Added: 0005765 2022-03-25 22:57 calestyo Note Added: 0005766 2022-03-31 15:06 geoffclare Note Edited: 0005755 2022-03-31 15:07
[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:
==
Project:1003.1(2016/18)/Issue7+TC2
Issue ID: 1546
Category: Base Definitions and Headers
Type: Enhancement Request
Severity: Editorial
Priority: normal
Status: Resolved
Name: Christoph Anton Mitterer
Organization:
User Reference:
Section:9.3 Basic Regular Expressions
Page Number:N/A
Line Number:N/A
Interp Status: ---
Final Accepted Text:https://austingroupbugs.net/view.php?id=1546#c5755
Resolution: Accepted As Marked
Fixed in Version:
==
Date Submitted: 2022-01-08 03:48 UTC
Last Modified: 2022-04-05 01:48 UTC
==
Summary:BREs: reserve \? \+ and \|
==
Relationships ID Summary
--
has duplicate 773 Summary: Add \+, \?, and \| to Basic Re...
==
--
(0005781) calestyo (reporter) - 2022-04-05 01:48
https://austingroupbugs.net/view.php?id=1546#c5781
--
@Geoff:
I think the main problem with the wording in (the current) note #5755:
"An escape sequence is defined as the escape character ('\\'),
when neither in a bracket expression nor itself escaped, followed by any
single character."
is that it applies the "neither in a bracket expression" only to the escape
character (the "followed by any single character" comes after that
subclause).
And that simply feels a bit strange, like ruling out that '[\]n' is a
escape sequence.
I mean sure it isn't - but what we really want to rule out is, that '[\n]'
isn't one.
Robert's wording seems to solve that in a nice manner.
Issue History
Date ModifiedUsername FieldChange
==
2022-01-08 03:48 calestyo New Issue
2022-01-08 03:48 calestyo Name => Christoph Anton
Mitterer
2022-01-08 03:48 calestyo Section => 9.3 Basic Regular
Expressions
2022-01-08 03:48 calestyo Page Number => N/A
2022-01-08 03:48 calestyo Line Number => N/A
2022-01-28 11:21 mirabilos Note Added: 0005636
2022-01-28 23:10 calestyo Note Added: 0005639
2022-03-03 06:56 Don Cragun Note Added: 0005731
2022-03-03 07:03 Don Cragun Note Edited: 0005731
2022-03-10 17:09 geoffclare Note Added: 0005738
2022-03-10 17:09 geoffclare Interp Status => ---
2022-03-10 17:09 geoffclare Final Accepted Text =>
https://austingroupbugs.net/view.php?id=1546#c5738
2022-03-10 17:09 geoffclare Status New => Resolved
2022-03-10 17:09 geoffclare Resolution Open => Accepted As
Marked
2022-03-10 17:10 geoffclare Tag Attached: issue8
2022-03-10 17:44 calestyo Note Added: 0005740
2022-03-12 21:01 Don Cragun Relationship added related to 773
2022-03-12 21:12 calestyo Note Added: 0005744
2022-03-12 21:13 calestyo Note Edited: 0005744
2022-03-14 10:08 geoffclare Note Added: 0005748
2022-03-14 10:08 geoffclare Status Resolved => Under
Review
2022-03-14 10:08 geoffclare Resolution Accepted As Marked =>
Reopened
2022-03-14 13:50 calestyo Note Added: 0005749
2022-03-14 14:31 geoffclare Note Added: 0005750
2022-03-18 09:32 geoffclare Note Added: 0005755
2022-03-24 15:29 geoffclare Final Accepted Text
https://austingroupbugs.net/view.php?id=1546#c5738 =>
https://austingroupbugs.net/view.php?id=1546#c5755
2022-03-24 15:29 geoffclare Status
Re: [1003.1(2016/18)/Issue7+TC2 0001546]: BREs: reserve \? \+ and \|
Robert Elz wrote, on 05 Apr 2022:
>
> | > > An escape sequence is defined as the escape character followed
> | > > by any single character. The escape character is a
> | > > that is neither in a bracket expression nor itself escaped.
>
> | Okay, I'll propose that wording in Thursday's teleconference.
>
> Actually, if this (or something to the same intent) doesn't already exist,
> then it might be worth adding a third sentence:
>
> A character is considered "escaped" if it appears as the second
> character in an escape sequence.
>
> I was first going to suggest that you switch from "nor itself escaped"
> to the way I originally worded it ("nor the 2nd char of an escape seq")
> but I realised it would be better to explicitly define "escaped" instead,
> so that can be used elsewhere, and be properly defined (not just rely upon
> being what is obvious).
>
> Whether this new sentence goes 2nd (between the existing two) or 3rd
> (after them) I don't think matters -- but a slight preference for 2nd,
> in which case it could also just be an additional clause on the first
> sentence ", that character is escaped." or something like that, perhaps
> "which is thereby escaped".
I like this last suggestion the best, but with the quotes from your
first suggestion:
An escape sequence is defined as the escape character followed by
any single character, which is thereby "escaped". The escape
character is a that is neither in a bracket expression
nor itself escaped.
--
Geoff Clare
The Open Group, Apex Plaza, Forbury Road, Reading, RG1 1AX, England
Re: [1003.1(2016/18)/Issue7+TC2 0001546]: BREs: reserve \? \+ and \|
Date:Tue, 5 Apr 2022 09:41:26 +0100
From:"Geoff Clare via austin-group-l at The Open Group"
Message-ID: <20220405084126.GA6489@localhost>
| > > ��� An escape sequence is defined as the escape character followed
| > > ��� by any single character.� The escape character is a
| > > ��� that is neither in a bracket expression nor itself escaped.
| Okay, I'll propose that wording in Thursday's teleconference.
Actually, if this (or something to the same intent) doesn't already exist,
then it might be worth adding a third sentence:
A character is considered "escaped" if it appears as the second
character in an escape sequence.
I was first going to suggest that you switch from "nor itself escaped"
to the way I originally worded it ("nor the 2nd char of an escape seq")
but I realised it would be better to explicitly define "escaped" instead,
so that can be used elsewhere, and be properly defined (not just rely upon
being what is obvious).
Whether this new sentence goes 2nd (between the existing two) or 3rd
(after them) I don't think matters -- but a slight preference for 2nd,
in which case it could also just be an additional clause on the first
sentence ", that character is escaped." or something like that, perhaps
"which is thereby escaped".
kre
Re: [1003.1(2016/18)/Issue7+TC2 0001546]: BREs: reserve \? \+ and \|
Christoph Anton Mitterer wrote, on 05 Apr 2022: > > > or it could be split into two sentences along the lines of your > > original > > suggestion: > > > > An escape sequence is defined as the escape character followed > > by any single character. The escape character is a > > that is neither in a bracket expression nor itself escaped. > > I think it should be the 2nd one Okay, I'll propose that wording in Thursday's teleconference. -- Geoff Clare The Open Group, Apex Plaza, Forbury Road, Reading, RG1 1AX, England
Re: [1003.1(2016/18)/Issue7+TC2 0001546]: BREs: reserve \? \+ and \|
On Mon, 2022-04-04 at 15:24 +0100, Geoff Clare via austin-group-l at The Open Group wrote: > An escape sequence is defined as the escape character (a > > that is neither in a bracket expression nor itself escaped), > followed > by any single character. The ordering of that sounds like ruling out '[\]n' to be an escape sequence. > > or it could be split into two sentences along the lines of your > original > suggestion: > > An escape sequence is defined as the escape character followed > by any single character. The escape character is a > that is neither in a bracket expression nor itself escaped. I think it should be the 2nd one, see https://austingroupbugs.net/view.php?id=1546#c5781 Cheers, Chris.
Re: [1003.1(2016/18)/Issue7+TC2 0001546]: BREs: reserve \? \+ and \|
Date:Mon, 4 Apr 2022 15:24:25 +0100 From:"Geoff Clare via austin-group-l at The Open Group" Message-ID: <20220404142425.GA23024@localhost> | I don't see a need for an xref to XBD 6.1, That's fine too, I just suggested that as a replacement, just in case... | A minimal fix to the current proposed text would be something like this: [...] | or it could be split into two sentences along the lines of your original | suggestion: Either would work. I (kind of obviously) slightly prefer the 2nd, I think it is slightly clearer (easier to follow), but the version that's closer to what is currently there would also work. kre
Re: [1003.1(2016/18)/Issue7+TC2 0001546]: BREs: reserve \? \+ and \|
Robert Elz wrote, on 04 Apr 2022: > > | Personally I don't see that there is a problem with the current wording. > > It is almost OK, and if you consider the readers must be able to > interpret the words in a rational, obvious, way, would be. > > The problem is that an escape character cannot be escaped, if it is, > it isn't an escape character (so there is a contradiction). I looked at other uses of "escape character" and found this in XCU 2.2.3: ... the shall retain its special meaning as an escape character (see Section 2.2.1) only when ... which fits with your way of looking at it, so it would make sense to change the proposed text in bug 1546 for consistency with the above. > ps: I'm also not greatly in favour of writing the backslash character as > a C character constant, rather than just as a character (as in a sh quoted > string for example) as '\'. Since there will always people who will object > to either of those, I wouldn't give the character's glyph form at all, but > rather refer to XBD 6.1 where it is presented without the quotes, and so > there's no problem. So " ([xref XBD 6.1])". I can see there are more uses of in the standard without the glyph that with, so I'm happy to drop the glyph. I don't see a need for an xref to XBD 6.1, as the character-name-in-angle-brackets convention is used all over the place without such references. A minimal fix to the current proposed text would be something like this: An escape sequence is defined as the escape character (a that is neither in a bracket expression nor itself escaped), followed by any single character. or it could be split into two sentences along the lines of your original suggestion: An escape sequence is defined as the escape character followed by any single character. The escape character is a that is neither in a bracket expression nor itself escaped. -- Geoff Clare The Open Group, Apex Plaza, Forbury Road, Reading, RG1 1AX, England
Re: [1003.1(2016/18)/Issue7+TC2 0001546]: BREs: reserve \? \+ and \|
Date:Mon, 4 Apr 2022 08:46:56 +
From:Austin Group Bug Tracker
Message-ID:
That is, really from Geoff Clare:
| Personally I don't see that there is a problem with the current wording.
It is almost OK, and if you consider the readers must be able to
interpret the words in a rational, obvious, way, would be.
The problem is that an escape character cannot be escaped, if it is,
it isn't an escape character (so there is a contradiction).
the escape character ('\\'),
when neither [...] nor itself escaped,
There are plenty of ways to rewrite this to make the point that it
is an unescaped backslash (rather than an unescaped escape char) which
becomes the escape char, my suggestion was just one possibility.
The same issue applies to being within a bracket expression, an escape
char cannot be there, so it makes no real sense to exclude it - though
it does to say that a backslash that is in there is not an escape char.
kre
ps: I'm also not greatly in favour of writing the backslash character as
a C character constant, rather than just as a character (as in a sh quoted
string for example) as '\'. Since there will always people who will object
to either of those, I wouldn't give the character's glyph form at all, but
rather refer to XBD 6.1 where it is presented without the quotes, and so
there's no problem. So " ([xref XBD 6.1])".
[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: == Project:1003.1(2016/18)/Issue7+TC2 Issue ID: 1546 Category: Base Definitions and Headers Type: Enhancement Request Severity: Editorial Priority: normal Status: Resolved Name: Christoph Anton Mitterer Organization: User Reference: Section:9.3 Basic Regular Expressions Page Number:N/A Line Number:N/A Interp Status: --- Final Accepted Text:https://austingroupbugs.net/view.php?id=1546#c5755 Resolution: Accepted As Marked Fixed in Version: == Date Submitted: 2022-01-08 03:48 UTC Last Modified: 2022-04-04 08:46 UTC == Summary:BREs: reserve \? \+ and \| == Relationships ID Summary -- has duplicate 773 Summary: Add \+, \?, and \| to Basic Re... == -- (0005779) geoffclare (manager) - 2022-04-04 08:46 https://austingroupbugs.net/view.php?id=1546#c5779 -- Re: https://austingroupbugs.net/view.php?id=1546#c5776 The wording in note 5755 was agreed in a teleconference, so I can't change it without getting agreement in another teleconference. Personally I don't see that there is a problem with the current wording. To me, saying the escape character is backslash just means that the character that is used for escaping is backslash. In situations where backslash loses its special meaning, it doesn't stop being the character that is used for escaping - it just can't perform that function in that situation. When a resolution is very long we prefer to make small changes by editing in place rather than creating another bug note that is otherwise identical. Your point about understanding the history is the reason for adding a separate note (5768) explaining what was changed. Issue History Date ModifiedUsername FieldChange == 2022-01-08 03:48 calestyo New Issue 2022-01-08 03:48 calestyo Name => Christoph Anton Mitterer 2022-01-08 03:48 calestyo Section => 9.3 Basic Regular Expressions 2022-01-08 03:48 calestyo Page Number => N/A 2022-01-08 03:48 calestyo Line Number => N/A 2022-01-28 11:21 mirabilos Note Added: 0005636 2022-01-28 23:10 calestyo Note Added: 0005639 2022-03-03 06:56 Don Cragun Note Added: 0005731 2022-03-03 07:03 Don Cragun Note Edited: 0005731 2022-03-10 17:09 geoffclare Note Added: 0005738 2022-03-10 17:09 geoffclare Interp Status => --- 2022-03-10 17:09 geoffclare Final Accepted Text => https://austingroupbugs.net/view.php?id=1546#c5738 2022-03-10 17:09 geoffclare Status New => Resolved 2022-03-10 17:09 geoffclare Resolution Open => Accepted As Marked 2022-03-10 17:10 geoffclare Tag Attached: issue8 2022-03-10 17:44 calestyo Note Added: 0005740 2022-03-12 21:01 Don Cragun Relationship added related to 773 2022-03-12 21:12 calestyo Note Added: 0005744 2022-03-12 21:13 calestyo Note Edited: 0005744 2022-03-14 10:08 geoffclare Note Added: 0005748 2022-03-14 10:08 geoffclare Status Resolved => Under Review 2022-03-14 10:08 geoffclare Resolution Accepted As Marked => Reopened 2022-03-14 13:50 calestyo Note Added: 0005749 2022-03-14 14:31 geoffclare Note Added: 0005750 2022-03-18 09:32 geoffclare Note Added: 0005755 2022-03-24
[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: == Project:1003.1(2016/18)/Issue7+TC2 Issue ID: 1546 Category: Base Definitions and Headers Type: Enhancement Request Severity: Editorial Priority: normal Status: Resolved Name: Christoph Anton Mitterer Organization: User Reference: Section:9.3 Basic Regular Expressions Page Number:N/A Line Number:N/A Interp Status: --- Final Accepted Text:https://austingroupbugs.net/view.php?id=1546#c5755 Resolution: Accepted As Marked Fixed in Version: == Date Submitted: 2022-01-08 03:48 UTC Last Modified: 2022-04-02 16:06 UTC == Summary:BREs: reserve \? \+ and \| == Relationships ID Summary -- has duplicate 773 Summary: Add \+, \?, and \| to Basic Re... == -- (0005776) calestyo (reporter) - 2022-04-02 16:06 https://austingroupbugs.net/view.php?id=1546#c5776 -- Well, the difference between escape character and backslash is clear to me,... that's why I've asked for the further clarification (in Note 5765) which Geoff made then. But I agree, that both, Geoff’s original proposal and my correction, still do it wrong and use the wording escape sequence/character for a place where it's already clear that it's actually not an escape sequence/character. I like your proposed text in Note 5773. It's "recursive" wording also solves the issue of e.g. " \\\n", where the 3rd \ would be preceded by another backslash (the 2nd),... but since that in turn is preceded by yet another backslash (the 1st, which has a preceding " ")... the 3rd \ is actually a escape character. Geoff, if you agree, then please make a new post with your proposal from 5755 and with Robert's improvement. (Updating the existing post makes it IMO much harder to understand the history and to review). I'd do it myself... but I have no idea how to make the markup. O:-) Issue History Date ModifiedUsername FieldChange == 2022-01-08 03:48 calestyo New Issue 2022-01-08 03:48 calestyo Name => Christoph Anton Mitterer 2022-01-08 03:48 calestyo Section => 9.3 Basic Regular Expressions 2022-01-08 03:48 calestyo Page Number => N/A 2022-01-08 03:48 calestyo Line Number => N/A 2022-01-28 11:21 mirabilos Note Added: 0005636 2022-01-28 23:10 calestyo Note Added: 0005639 2022-03-03 06:56 Don Cragun Note Added: 0005731 2022-03-03 07:03 Don Cragun Note Edited: 0005731 2022-03-10 17:09 geoffclare Note Added: 0005738 2022-03-10 17:09 geoffclare Interp Status => --- 2022-03-10 17:09 geoffclare Final Accepted Text => https://austingroupbugs.net/view.php?id=1546#c5738 2022-03-10 17:09 geoffclare Status New => Resolved 2022-03-10 17:09 geoffclare Resolution Open => Accepted As Marked 2022-03-10 17:10 geoffclare Tag Attached: issue8 2022-03-10 17:44 calestyo Note Added: 0005740 2022-03-12 21:01 Don Cragun Relationship added related to 773 2022-03-12 21:12 calestyo Note Added: 0005744 2022-03-12 21:13 calestyo Note Edited: 0005744 2022-03-14 10:08 geoffclare Note Added: 0005748 2022-03-14 10:08 geoffclare Status Resolved => Under Review 2022-03-14 10:08 geoffclare Resolution Accepted As Marked => Reopened 2022-03-14 13:50 calestyo Note Added: 0005749
[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: == Project:1003.1(2016/18)/Issue7+TC2 Issue ID: 1546 Category: Base Definitions and Headers Type: Enhancement Request Severity: Editorial Priority: normal Status: Resolved Name: Christoph Anton Mitterer Organization: User Reference: Section:9.3 Basic Regular Expressions Page Number:N/A Line Number:N/A Interp Status: --- Final Accepted Text:https://austingroupbugs.net/view.php?id=1546#c5755 Resolution: Accepted As Marked Fixed in Version: == Date Submitted: 2022-01-08 03:48 UTC Last Modified: 2022-04-02 08:17 UTC == Summary:BREs: reserve \? \+ and \| == Relationships ID Summary -- has duplicate 773 Summary: Add \+, \?, and \| to Basic Re... == -- (0005773) kre (reporter) - 2022-04-02 08:17 https://austingroupbugs.net/view.php?id=1546#c5773 -- Re the proposed test in https://austingroupbugs.net/view.php?id=1546#c5770 No, absolutely not, that's worse than what is currently proposed, though I agree that could do with a minor improvement. You seem to be treating and as if they're the same thing (because they are both written as a '\' perhaps). They aren't. Escape chars are escape chars, and backlashes are backslashes, they are not the same thing at all. The common way to define this kind of thing is with a pair of self referential definitions, something like An escape sequence is the escape character, followed by any single character. The escape character is a backslash which is not the second character of an escape sequence, and is not within a bracket expression. Next, it is not that an escape sequence *mustn't* be in a bracket expression, but that it cannot be, which is because no excape character can occur in a bracket expression, and an escape sequence requires a leading escape character. Nothing needs be said about that at all, this can be deduced from the definition. Issue History Date ModifiedUsername FieldChange == 2022-01-08 03:48 calestyo New Issue 2022-01-08 03:48 calestyo Name => Christoph Anton Mitterer 2022-01-08 03:48 calestyo Section => 9.3 Basic Regular Expressions 2022-01-08 03:48 calestyo Page Number => N/A 2022-01-08 03:48 calestyo Line Number => N/A 2022-01-28 11:21 mirabilos Note Added: 0005636 2022-01-28 23:10 calestyo Note Added: 0005639 2022-03-03 06:56 Don Cragun Note Added: 0005731 2022-03-03 07:03 Don Cragun Note Edited: 0005731 2022-03-10 17:09 geoffclare Note Added: 0005738 2022-03-10 17:09 geoffclare Interp Status => --- 2022-03-10 17:09 geoffclare Final Accepted Text => https://austingroupbugs.net/view.php?id=1546#c5738 2022-03-10 17:09 geoffclare Status New => Resolved 2022-03-10 17:09 geoffclare Resolution Open => Accepted As Marked 2022-03-10 17:10 geoffclare Tag Attached: issue8 2022-03-10 17:44 calestyo Note Added: 0005740 2022-03-12 21:01 Don Cragun Relationship added related to 773 2022-03-12 21:12 calestyo Note Added: 0005744 2022-03-12 21:13 calestyo Note Edited: 0005744 2022-03-14 10:08 geoffclare Note Added: 0005748 2022-03-14 10:08 geoffclare Status Resolved => Under Review 2022-03-14 10:08 geoffclare Resolution Accepted As Marked => Reopened
[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:
==
Project:1003.1(2016/18)/Issue7+TC2
Issue ID: 1546
Category: Base Definitions and Headers
Type: Enhancement Request
Severity: Editorial
Priority: normal
Status: Resolved
Name: Christoph Anton Mitterer
Organization:
User Reference:
Section:9.3 Basic Regular Expressions
Page Number:N/A
Line Number:N/A
Interp Status: ---
Final Accepted Text:https://austingroupbugs.net/view.php?id=1546#c5755
Resolution: Accepted As Marked
Fixed in Version:
==
Date Submitted: 2022-01-08 03:48 UTC
Last Modified: 2022-04-01 22:22 UTC
==
Summary:BREs: reserve \? \+ and \|
==
Relationships ID Summary
--
has duplicate 773 Summary: Add \+, \?, and \| to Basic Re...
==
--
(0005770) calestyo (reporter) - 2022-04-01 22:22
https://austingroupbugs.net/view.php?id=1546#c5770
--
"An escape sequence is defined as the escape character ('\\'),
when neither in a bracket expression nor itself escaped, followed by any
single character."
Would do the job, I guess, but reads a bit unusual...?
The escape character mustn't be in a bracket expression nor
itself escaped... but it's rather the whole escape sequence that mustn't be
in a BE?
What about:
"An escape sequence is defined as the escape character ('\\')
followed by any single character, when neither in a bracket expression nor
when the escape character itself is escaped."
Other than that... seems good do me.
I like the future directions note. It gives POSIX the freedom to keep
everything as it is (should that be necessary) or to unify the behaviour
(should that become possible).
Issue History
Date ModifiedUsername FieldChange
==
2022-01-08 03:48 calestyo New Issue
2022-01-08 03:48 calestyo Name => Christoph Anton
Mitterer
2022-01-08 03:48 calestyo Section => 9.3 Basic Regular
Expressions
2022-01-08 03:48 calestyo Page Number => N/A
2022-01-08 03:48 calestyo Line Number => N/A
2022-01-28 11:21 mirabilos Note Added: 0005636
2022-01-28 23:10 calestyo Note Added: 0005639
2022-03-03 06:56 Don Cragun Note Added: 0005731
2022-03-03 07:03 Don Cragun Note Edited: 0005731
2022-03-10 17:09 geoffclare Note Added: 0005738
2022-03-10 17:09 geoffclare Interp Status => ---
2022-03-10 17:09 geoffclare Final Accepted Text =>
https://austingroupbugs.net/view.php?id=1546#c5738
2022-03-10 17:09 geoffclare Status New => Resolved
2022-03-10 17:09 geoffclare Resolution Open => Accepted As
Marked
2022-03-10 17:10 geoffclare Tag Attached: issue8
2022-03-10 17:44 calestyo Note Added: 0005740
2022-03-12 21:01 Don Cragun Relationship added related to 773
2022-03-12 21:12 calestyo Note Added: 0005744
2022-03-12 21:13 calestyo Note Edited: 0005744
2022-03-14 10:08 geoffclare Note Added: 0005748
2022-03-14 10:08 geoffclare Status Resolved => Under
Review
2022-03-14 10:08 geoffclare Resolution Accepted As Marked =>
Reopened
2022-03-14 13:50 calestyo Note Added: 0005749
2022-03-14 14:31 geoffclare Note Added: 0005750
2022-03-18 09:32 geoffclare Note Added: 0005755
2022-03-24 15:29 geoffclare Final Accepted Text
[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: == Project:1003.1(2016/18)/Issue7+TC2 Issue ID: 1546 Category: Base Definitions and Headers Type: Enhancement Request Severity: Editorial Priority: normal Status: Resolved Name: Christoph Anton Mitterer Organization: User Reference: Section:9.3 Basic Regular Expressions Page Number:N/A Line Number:N/A Interp Status: --- Final Accepted Text:https://austingroupbugs.net/view.php?id=1546#c5755 Resolution: Accepted As Marked Fixed in Version: == Date Submitted: 2022-01-08 03:48 UTC Last Modified: 2022-03-31 15:08 UTC == Summary:BREs: reserve \? \+ and \| == Relationships ID Summary -- has duplicate 773 Summary: Add \+, \?, and \| to Basic Re... == -- (0005768) geoffclare (manager) - 2022-03-31 15:08 https://austingroupbugs.net/view.php?id=1546#c5768 -- In the March 31st teleconference, the resolution in https://austingroupbugs.net/view.php?id=1546#c5755 was updated to change the "escape sequence" definition and add the future directions note. Issue History Date ModifiedUsername FieldChange == 2022-01-08 03:48 calestyo New Issue 2022-01-08 03:48 calestyo Name => Christoph Anton Mitterer 2022-01-08 03:48 calestyo Section => 9.3 Basic Regular Expressions 2022-01-08 03:48 calestyo Page Number => N/A 2022-01-08 03:48 calestyo Line Number => N/A 2022-01-28 11:21 mirabilos Note Added: 0005636 2022-01-28 23:10 calestyo Note Added: 0005639 2022-03-03 06:56 Don Cragun Note Added: 0005731 2022-03-03 07:03 Don Cragun Note Edited: 0005731 2022-03-10 17:09 geoffclare Note Added: 0005738 2022-03-10 17:09 geoffclare Interp Status => --- 2022-03-10 17:09 geoffclare Final Accepted Text => https://austingroupbugs.net/view.php?id=1546#c5738 2022-03-10 17:09 geoffclare Status New => Resolved 2022-03-10 17:09 geoffclare Resolution Open => Accepted As Marked 2022-03-10 17:10 geoffclare Tag Attached: issue8 2022-03-10 17:44 calestyo Note Added: 0005740 2022-03-12 21:01 Don Cragun Relationship added related to 773 2022-03-12 21:12 calestyo Note Added: 0005744 2022-03-12 21:13 calestyo Note Edited: 0005744 2022-03-14 10:08 geoffclare Note Added: 0005748 2022-03-14 10:08 geoffclare Status Resolved => Under Review 2022-03-14 10:08 geoffclare Resolution Accepted As Marked => Reopened 2022-03-14 13:50 calestyo Note Added: 0005749 2022-03-14 14:31 geoffclare Note Added: 0005750 2022-03-18 09:32 geoffclare Note Added: 0005755 2022-03-24 15:29 geoffclare Final Accepted Text https://austingroupbugs.net/view.php?id=1546#c5738 => https://austingroupbugs.net/view.php?id=1546#c5755 2022-03-24 15:29 geoffclare Status Under Review => Resolved 2022-03-24 15:29 geoffclare Resolution Reopened => Accepted As Marked 2022-03-24 15:34 geoffclare Relationship replacedhas duplicate 773 2022-03-25 22:41 calestyo Note Added: 0005765 2022-03-25 22:57 calestyo Note Added: 0005766 2022-03-31 15:06 geoffclare Note Edited: 0005755
[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: == Project:1003.1(2016/18)/Issue7+TC2 Issue ID: 1546 Category: Base Definitions and Headers Type: Enhancement Request Severity: Editorial Priority: normal Status: Resolved Name: Christoph Anton Mitterer Organization: User Reference: Section:9.3 Basic Regular Expressions Page Number:N/A Line Number:N/A Interp Status: --- Final Accepted Text:https://austingroupbugs.net/view.php?id=1546#c5755 Resolution: Accepted As Marked Fixed in Version: == Date Submitted: 2022-01-08 03:48 UTC Last Modified: 2022-03-25 22:57 UTC == Summary:BREs: reserve \? \+ and \| == Relationships ID Summary -- has duplicate 773 Summary: Add \+, \?, and \| to Basic Re... == -- (0005766) calestyo (reporter) - 2022-03-25 22:57 https://austingroupbugs.net/view.php?id=1546#c5766 -- May I also add the following: a) Not sure whether https://austingroupbugs.net/view.php?id=773 is really to be considered a duplicate of this. This issue was merely about preventing "\?", "\+", and "\|" to get any completely other meaning than that from ERE. While #773 rather asked for defining them to ONLY have the special meaning (not either special or literal - as the above draft resolves it). b) While the draft in 5755 prevents (a) from happening (e.g. \+ couldn't suddenly mean something completely different) I'm still a bit sceptical on whether that's the best way to go. It merely records the current situation of implementations - but with that also statically codifies the two different interpretations (literal ? + \ vs. special). So we'd get non-portable behaviour even deeper into the standard than it was before, where from the standard's PoV any use of "\?", "\+", and "\|" was simply undefined. I realise that it would be problematic to follow the spirit of #773 and define "\?", "\+", and "\|" to have ONLY the special meaning, when there are implementations (you've mentioned Solaris, HP-UX, AIX) who behave already different. OTOH, if an implementation assigns it's own semantics to undefined parts of a standard, it must always assume that sooner or later it could get compatibility issues. The question arises: Do Solaris/HP-UX/AIX really give "\?", "\+", and "\|" the literal meaning on purpose (or is it perhaps just an undocumented side-effect of the implementation),... is it even used there,... would they be willing to adapt? Depending on the answers, it could make sense to follow a different path. And even if that doesn't seem feasible right now, one could perhaps add something to "future directions", indicating that a future standard might require "\?", "\+", and "\|" to have ONLY the special meaning. This would encourage any new implementations to follow that. And as long as any implementations exist (possibly even forever),... the "future direction" would never need to become true, so no one should be sad. Issue History Date ModifiedUsername FieldChange == 2022-01-08 03:48 calestyo New Issue 2022-01-08 03:48 calestyo Name => Christoph Anton Mitterer 2022-01-08 03:48 calestyo Section => 9.3 Basic Regular Expressions 2022-01-08 03:48 calestyo Page Number => N/A 2022-01-08 03:48 calestyo Line Number => N/A 2022-01-28 11:21 mirabilos Note Added: 0005636 2022-01-28 23:10 calestyo Note Added: 0005639 2022-03-03 06:56 Don Cragun Note Added: 0005731 2022-03-03 07:03 Don Cragun Note Edited: 0005731 2022-03-10 17:09 geoffclare Note Added: 0005738
[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:
==
Project:1003.1(2016/18)/Issue7+TC2
Issue ID: 1546
Category: Base Definitions and Headers
Type: Enhancement Request
Severity: Editorial
Priority: normal
Status: Resolved
Name: Christoph Anton Mitterer
Organization:
User Reference:
Section:9.3 Basic Regular Expressions
Page Number:N/A
Line Number:N/A
Interp Status: ---
Final Accepted Text:https://austingroupbugs.net/view.php?id=1546#c5755
Resolution: Accepted As Marked
Fixed in Version:
==
Date Submitted: 2022-01-08 03:48 UTC
Last Modified: 2022-03-25 22:41 UTC
==
Summary:BREs: reserve \? \+ and \|
==
Relationships ID Summary
--
has duplicate 773 Summary: Add \+, \?, and \| to Basic Re...
==
--
(0005765) calestyo (reporter) - 2022-03-25 22:41
https://austingroupbugs.net/view.php?id=1546#c5765
--
off-topic: Did Austin Group ever consider to handle such changes via git?
It would make following/reviewing changes *so* much easier, than having to
build up the final picture by fiddling around with pages, line numbers and
what's ought to be changed to what.
Regarding https://austingroupbugs.net/view.php?id=1546#c5755
Some comments from my side:
1) I'm still a bit unhappy with the definition of "escape sequence".
It does not directly include the information that the escape character \
itself must not be quoted by another '\'.
Even if you would have 2.2.1 Escape Character (Backslash) in mind:
- this seems more or less defined for chapter 2 - not generally
- and even if one assumes it generally, than 2.2.1 would say "A
that is not quoted" - where quoting however means *any* shell quotation
style (\… '…' "…" and in the future $'…') - however for REs, only
the \… style would apply.
2) Perhaps it would also be better to write instead of:
"An escape sequence, when not in a bracket expression, is defined as the
escape character ('\\') followed by any single character."
something like the following:
"An escape sequence is defined as the escape character ('\\')
followed by any single character, not within a bracket expression."
The problem with "An escape sequence, when not in a bracket expression" is
IMO that this makes no sense, as there are never escape sequences within a
bracket expression - except perhaps for the open question (I've raised in
some other ticket) of whether an an escaped sed delimiter (like in
's.a[\.]b.X.') inside a bracket expression is the undelimitered special
character (special '.' in the example), the undelimitered literal character
(literal '.' in the example) or the literal two characters ('\' and '.' in
the example).
Apart from that,... the draft in 5755 looks good, though I haven't checked
the grammar in detail.
Issue History
Date ModifiedUsername FieldChange
==
2022-01-08 03:48 calestyo New Issue
2022-01-08 03:48 calestyo Name => Christoph Anton
Mitterer
2022-01-08 03:48 calestyo Section => 9.3 Basic Regular
Expressions
2022-01-08 03:48 calestyo Page Number => N/A
2022-01-08 03:48 calestyo Line Number => N/A
2022-01-28 11:21 mirabilos Note Added: 0005636
2022-01-28 23:10 calestyo Note Added: 0005639
2022-03-03 06:56 Don Cragun Note Added: 0005731
2022-03-03 07:03 Don Cragun Note Edited: 0005731
2022-03-10 17:09 geoffclare Note Added: 0005738
2022-03-10 17:09 geoffclare Interp Status => ---
2022-03-10 17:09 geoffclare Final Accepted Text =>
[1003.1(2016/18)/Issue7+TC2 0001546]: BREs: reserve \? \+ and \|
The issue 773 has been set as DUPLICATE OF the following issue. == https://austingroupbugs.net/view.php?id=1546 == Reported By:calestyo Assigned To: == Project:1003.1(2016/18)/Issue7+TC2 Issue ID: 1546 Category: Base Definitions and Headers Type: Enhancement Request Severity: Editorial Priority: normal Status: Resolved Name: Christoph Anton Mitterer Organization: User Reference: Section:9.3 Basic Regular Expressions Page Number:N/A Line Number:N/A Interp Status: --- Final Accepted Text:https://austingroupbugs.net/view.php?id=1546#c5755 Resolution: Accepted As Marked Fixed in Version: == Date Submitted: 2022-01-08 03:48 UTC Last Modified: 2022-03-24 15:29 UTC == Summary:BREs: reserve \? \+ and \| == Relationships ID Summary -- has duplicate 773 Summary: Add \+, \?, and \| to Basic Re... == Issue History Date ModifiedUsername FieldChange == 2022-01-08 03:48 calestyo New Issue 2022-01-08 03:48 calestyo Name => Christoph Anton Mitterer 2022-01-08 03:48 calestyo Section => 9.3 Basic Regular Expressions 2022-01-08 03:48 calestyo Page Number => N/A 2022-01-08 03:48 calestyo Line Number => N/A 2022-01-28 11:21 mirabilos Note Added: 0005636 2022-01-28 23:10 calestyo Note Added: 0005639 2022-03-03 06:56 Don Cragun Note Added: 0005731 2022-03-03 07:03 Don Cragun Note Edited: 0005731 2022-03-10 17:09 geoffclare Note Added: 0005738 2022-03-10 17:09 geoffclare Interp Status => --- 2022-03-10 17:09 geoffclare Final Accepted Text => https://austingroupbugs.net/view.php?id=1546#c5738 2022-03-10 17:09 geoffclare Status New => Resolved 2022-03-10 17:09 geoffclare Resolution Open => Accepted As Marked 2022-03-10 17:10 geoffclare Tag Attached: issue8 2022-03-10 17:44 calestyo Note Added: 0005740 2022-03-12 21:01 Don Cragun Relationship added related to 773 2022-03-12 21:12 calestyo Note Added: 0005744 2022-03-12 21:13 calestyo Note Edited: 0005744 2022-03-14 10:08 geoffclare Note Added: 0005748 2022-03-14 10:08 geoffclare Status Resolved => Under Review 2022-03-14 10:08 geoffclare Resolution Accepted As Marked => Reopened 2022-03-14 13:50 calestyo Note Added: 0005749 2022-03-14 14:31 geoffclare Note Added: 0005750 2022-03-18 09:32 geoffclare Note Added: 0005755 2022-03-24 15:29 geoffclare Final Accepted Text https://austingroupbugs.net/view.php?id=1546#c5738 => https://austingroupbugs.net/view.php?id=1546#c5755 2022-03-24 15:29 geoffclare Status Under Review => Resolved 2022-03-24 15:29 geoffclare Resolution Reopened => Accepted As Marked 2022-03-24 15:34 geoffclare Relationship replacedhas duplicate 773 ==
[1003.1(2016/18)/Issue7+TC2 0001546]: BREs: reserve \? \+ and \|
The following issue has been RESOLVED. == https://austingroupbugs.net/view.php?id=1546 == Reported By:calestyo Assigned To: == Project:1003.1(2016/18)/Issue7+TC2 Issue ID: 1546 Category: Base Definitions and Headers Type: Enhancement Request Severity: Editorial Priority: normal Status: Resolved Name: Christoph Anton Mitterer Organization: User Reference: Section:9.3 Basic Regular Expressions Page Number:N/A Line Number:N/A Interp Status: --- Final Accepted Text:https://austingroupbugs.net/view.php?id=1546#c5755 Resolution: Accepted As Marked Fixed in Version: == Date Submitted: 2022-01-08 03:48 UTC Last Modified: 2022-03-24 15:29 UTC == Summary:BREs: reserve \? \+ and \| == Relationships ID Summary -- related to 773 Summary: Add \+, \?, and \| to Basic Re... == Issue History Date ModifiedUsername FieldChange == 2022-01-08 03:48 calestyo New Issue 2022-01-08 03:48 calestyo Name => Christoph Anton Mitterer 2022-01-08 03:48 calestyo Section => 9.3 Basic Regular Expressions 2022-01-08 03:48 calestyo Page Number => N/A 2022-01-08 03:48 calestyo Line Number => N/A 2022-01-28 11:21 mirabilos Note Added: 0005636 2022-01-28 23:10 calestyo Note Added: 0005639 2022-03-03 06:56 Don Cragun Note Added: 0005731 2022-03-03 07:03 Don Cragun Note Edited: 0005731 2022-03-10 17:09 geoffclare Note Added: 0005738 2022-03-10 17:09 geoffclare Interp Status => --- 2022-03-10 17:09 geoffclare Final Accepted Text => https://austingroupbugs.net/view.php?id=1546#c5738 2022-03-10 17:09 geoffclare Status New => Resolved 2022-03-10 17:09 geoffclare Resolution Open => Accepted As Marked 2022-03-10 17:10 geoffclare Tag Attached: issue8 2022-03-10 17:44 calestyo Note Added: 0005740 2022-03-12 21:01 Don Cragun Relationship added related to 773 2022-03-12 21:12 calestyo Note Added: 0005744 2022-03-12 21:13 calestyo Note Edited: 0005744 2022-03-14 10:08 geoffclare Note Added: 0005748 2022-03-14 10:08 geoffclare Status Resolved => Under Review 2022-03-14 10:08 geoffclare Resolution Accepted As Marked => Reopened 2022-03-14 13:50 calestyo Note Added: 0005749 2022-03-14 14:31 geoffclare Note Added: 0005750 2022-03-18 09:32 geoffclare Note Added: 0005755 2022-03-24 15:29 geoffclare Final Accepted Text https://austingroupbugs.net/view.php?id=1546#c5738 => https://austingroupbugs.net/view.php?id=1546#c5755 2022-03-24 15:29 geoffclare Status Under Review => Resolved 2022-03-24 15:29 geoffclare Resolution Reopened => Accepted As Marked ==
[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:
==
Project:1003.1(2016/18)/Issue7+TC2
Issue ID: 1546
Category: Base Definitions and Headers
Type: Enhancement Request
Severity: Editorial
Priority: normal
Status: Under Review
Name: Christoph Anton Mitterer
Organization:
User Reference:
Section:9.3 Basic Regular Expressions
Page Number:N/A
Line Number:N/A
Interp Status: ---
Final Accepted Text:https://austingroupbugs.net/view.php?id=1546#c5738
==
Date Submitted: 2022-01-08 03:48 UTC
Last Modified: 2022-03-18 09:32 UTC
==
Summary:BREs: reserve \? \+ and \|
==
Relationships ID Summary
--
related to 773 Summary: Add \+, \?, and \| to Basic Re...
==
--
(0005755) geoffclare (manager) - 2022-03-18 09:32
https://austingroupbugs.net/view.php?id=1546#c5755
--
New proposed resolution that adds the grammar changes and changes to the
anchoring description in 9.3.8. I also took the opportunity to improve
consistency between the BRE grammar and ERE grammar.
Page and line numbers are for Issue 8 draft 2.1
After page 165 line 5720 section 9.1, add:
escape sequenceAn escape sequence, when not in a bracket
expression, is defined as the escape character ('\\') followed
by any single character.
After page 167 line 5806 section 9.3.2, add:The '?',
'+', and '|' characters; it is implementation-defined whether "\?", "\+",
and "\|" each match the literal character '?', '+', or '|', respectively,
or behave as described for the ERE special characters '?', '+', and '|',
respectively (see [xref to 9.4.3]).
After page 168 line 5818 section 9.3.3, add a new list
item:Immediately following a "\|" escape sequence (after an
initial '^', if any), if the implementation does not match the escape
sequence "\|" to the literal character '|'.
On page 172 line 6015 section 9.3.8, change:A
('^') shall be an anchor when used as the first character of an entire BRE.
The implementation may treat the as an anchor when used as the
first character of a subexpression.to:A
('^') shall be an anchor when used as the first character of
an entire BRE and, if the implementation does not match the escape sequence
"\|" to the literal character '|', when used immediately following a "\|"
escape sequence that is not inside a subexpression. The implementation may
also treat a as an anchor when used inside a subexpression; in
this case it shall be an anchor only when either of the following is
true:
It is the first character of the subexpression.
It immediately follows a "\|" escape sequence and the implementation
does not match the escape sequence "\|" to the literal character
'|'.
On page 172 line 6023 section 9.3.8, change:A
('$') shall be an anchor when used as the last character of an entire BRE.
The implementation may treat a as an anchor when used as the
last character of a subexpression.to:A
('$') shall be an anchor when used as the last character of
an entire BRE and, if the implementation does not match the escape sequence
"\|" to the literal character '|', when used immediately preceding a "\|"
escape sequence that is not inside a subexpression. The implementation may
also treat a as an anchor when used inside a subexpression;
in this case it shall be an anchor only when either of the following is
true:
It is the last character of the subexpression.
It immediately precedes a "\|" escape sequence and the implementation
does not match the escape sequence "\|" to the literal character
'|'.
On page 176 line 6191 section 9.5.1, change:The character '^'
when it appears as the first character of a basic regular expression and
when not QUOTED_CHAR.to:The character '^'
when it appears either as the first character of a basic regular expression
or, if the implementation does not match the escape sequence "\|" to the
literal character '|', when used immediately following a "\|" escape
sequence that is not inside a subexpression, and when
[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: == Project:1003.1(2016/18)/Issue7+TC2 Issue ID: 1546 Category: Base Definitions and Headers Type: Enhancement Request Severity: Editorial Priority: normal Status: Under Review Name: Christoph Anton Mitterer Organization: User Reference: Section:9.3 Basic Regular Expressions Page Number:N/A Line Number:N/A Interp Status: --- Final Accepted Text:https://austingroupbugs.net/view.php?id=1546#c5738 == Date Submitted: 2022-01-08 03:48 UTC Last Modified: 2022-03-14 14:31 UTC == Summary:BREs: reserve \? \+ and \| == Relationships ID Summary -- related to 773 Summary: Add \+, \?, and \| to Basic Re... == -- (0005750) geoffclare (manager) - 2022-03-14 14:31 https://austingroupbugs.net/view.php?id=1546#c5750 -- The Solaris I tested is the latest (11.4). HP-UX a little on the old side but I believe it is very unlikely to have had any changes to fundamentals like REs since the version I have. Issue History Date ModifiedUsername FieldChange == 2022-01-08 03:48 calestyo New Issue 2022-01-08 03:48 calestyo Name => Christoph Anton Mitterer 2022-01-08 03:48 calestyo Section => 9.3 Basic Regular Expressions 2022-01-08 03:48 calestyo Page Number => N/A 2022-01-08 03:48 calestyo Line Number => N/A 2022-01-28 11:21 mirabilos Note Added: 0005636 2022-01-28 23:10 calestyo Note Added: 0005639 2022-03-03 06:56 Don Cragun Note Added: 0005731 2022-03-03 07:03 Don Cragun Note Edited: 0005731 2022-03-10 17:09 geoffclare Note Added: 0005738 2022-03-10 17:09 geoffclare Interp Status => --- 2022-03-10 17:09 geoffclare Final Accepted Text => https://austingroupbugs.net/view.php?id=1546#c5738 2022-03-10 17:09 geoffclare Status New => Resolved 2022-03-10 17:09 geoffclare Resolution Open => Accepted As Marked 2022-03-10 17:10 geoffclare Tag Attached: issue8 2022-03-10 17:44 calestyo Note Added: 0005740 2022-03-12 21:01 Don Cragun Relationship added related to 773 2022-03-12 21:12 calestyo Note Added: 0005744 2022-03-12 21:13 calestyo Note Edited: 0005744 2022-03-14 10:08 geoffclare Note Added: 0005748 2022-03-14 10:08 geoffclare Status Resolved => Under Review 2022-03-14 10:08 geoffclare Resolution Accepted As Marked => Reopened 2022-03-14 13:50 calestyo Note Added: 0005749 2022-03-14 14:31 geoffclare Note Added: 0005750 ==
[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: == Project:1003.1(2016/18)/Issue7+TC2 Issue ID: 1546 Category: Base Definitions and Headers Type: Enhancement Request Severity: Editorial Priority: normal Status: Under Review Name: Christoph Anton Mitterer Organization: User Reference: Section:9.3 Basic Regular Expressions Page Number:N/A Line Number:N/A Interp Status: --- Final Accepted Text:https://austingroupbugs.net/view.php?id=1546#c5738 == Date Submitted: 2022-01-08 03:48 UTC Last Modified: 2022-03-14 13:50 UTC == Summary:BREs: reserve \? \+ and \| == Relationships ID Summary -- related to 773 Summary: Add \+, \?, and \| to Basic Re... == -- (0005749) calestyo (reporter) - 2022-03-14 13:50 https://austingroupbugs.net/view.php?id=1546#c5749 -- And I assume these refer to reasonably current versions of such implementations? I mean it would probably make not much sense to standardise both ways, if one of them was only used 30 years ago. Issue History Date ModifiedUsername FieldChange == 2022-01-08 03:48 calestyo New Issue 2022-01-08 03:48 calestyo Name => Christoph Anton Mitterer 2022-01-08 03:48 calestyo Section => 9.3 Basic Regular Expressions 2022-01-08 03:48 calestyo Page Number => N/A 2022-01-08 03:48 calestyo Line Number => N/A 2022-01-28 11:21 mirabilos Note Added: 0005636 2022-01-28 23:10 calestyo Note Added: 0005639 2022-03-03 06:56 Don Cragun Note Added: 0005731 2022-03-03 07:03 Don Cragun Note Edited: 0005731 2022-03-10 17:09 geoffclare Note Added: 0005738 2022-03-10 17:09 geoffclare Interp Status => --- 2022-03-10 17:09 geoffclare Final Accepted Text => https://austingroupbugs.net/view.php?id=1546#c5738 2022-03-10 17:09 geoffclare Status New => Resolved 2022-03-10 17:09 geoffclare Resolution Open => Accepted As Marked 2022-03-10 17:10 geoffclare Tag Attached: issue8 2022-03-10 17:44 calestyo Note Added: 0005740 2022-03-12 21:01 Don Cragun Relationship added related to 773 2022-03-12 21:12 calestyo Note Added: 0005744 2022-03-12 21:13 calestyo Note Edited: 0005744 2022-03-14 10:08 geoffclare Note Added: 0005748 2022-03-14 10:08 geoffclare Status Resolved => Under Review 2022-03-14 10:08 geoffclare Resolution Accepted As Marked => Reopened 2022-03-14 13:50 calestyo Note Added: 0005749 ==
[1003.1(2016/18)/Issue7+TC2 0001546]: BREs: reserve \? \+ and \|
The following issue has been REOPENED. == https://austingroupbugs.net/view.php?id=1546 == Reported By:calestyo Assigned To: == Project:1003.1(2016/18)/Issue7+TC2 Issue ID: 1546 Category: Base Definitions and Headers Type: Enhancement Request Severity: Editorial Priority: normal Status: Under Review Name: Christoph Anton Mitterer Organization: User Reference: Section:9.3 Basic Regular Expressions Page Number:N/A Line Number:N/A Interp Status: --- Final Accepted Text:https://austingroupbugs.net/view.php?id=1546#c5738 == Date Submitted: 2022-01-08 03:48 UTC Last Modified: 2022-03-14 10:08 UTC == Summary:BREs: reserve \? \+ and \| == Relationships ID Summary -- related to 773 Summary: Add \+, \?, and \| to Basic Re... == -- (0005748) geoffclare (manager) - 2022-03-14 10:08 https://austingroupbugs.net/view.php?id=1546#c5748 -- Reopening because we forgot that the BRE grammar needs updating (David Wheeler proposed a change to the grammar in bug https://austingroupbugs.net/view.php?id=773). Re https://austingroupbugs.net/view.php?id=1546#c5744 There are implementations where "\+", "\?" and "\|" match a literal '+', '?', or '|' (I tested Solaris and HP-UX; I would expect AIX is the same). The people on the March 10 teleconference were not aware of any implementation which behaves differently than the two behaviours we decided to allow. Issue History Date ModifiedUsername FieldChange == 2022-01-08 03:48 calestyo New Issue 2022-01-08 03:48 calestyo Name => Christoph Anton Mitterer 2022-01-08 03:48 calestyo Section => 9.3 Basic Regular Expressions 2022-01-08 03:48 calestyo Page Number => N/A 2022-01-08 03:48 calestyo Line Number => N/A 2022-01-28 11:21 mirabilos Note Added: 0005636 2022-01-28 23:10 calestyo Note Added: 0005639 2022-03-03 06:56 Don Cragun Note Added: 0005731 2022-03-03 07:03 Don Cragun Note Edited: 0005731 2022-03-10 17:09 geoffclare Note Added: 0005738 2022-03-10 17:09 geoffclare Interp Status => --- 2022-03-10 17:09 geoffclare Final Accepted Text => https://austingroupbugs.net/view.php?id=1546#c5738 2022-03-10 17:09 geoffclare Status New => Resolved 2022-03-10 17:09 geoffclare Resolution Open => Accepted As Marked 2022-03-10 17:10 geoffclare Tag Attached: issue8 2022-03-10 17:44 calestyo Note Added: 0005740 2022-03-12 21:01 Don Cragun Relationship added related to 773 2022-03-12 21:12 calestyo Note Added: 0005744 2022-03-12 21:13 calestyo Note Edited: 0005744 2022-03-14 10:08 geoffclare Note Added: 0005748 2022-03-14 10:08 geoffclare Status Resolved => Under Review 2022-03-14 10:08 geoffclare Resolution Accepted As Marked => Reopened ==
[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: == Project:1003.1(2016/18)/Issue7+TC2 Issue ID: 1546 Category: Base Definitions and Headers Type: Enhancement Request Severity: Editorial Priority: normal Status: Resolved Name: Christoph Anton Mitterer Organization: User Reference: Section:9.3 Basic Regular Expressions Page Number:N/A Line Number:N/A Interp Status: --- Final Accepted Text:https://austingroupbugs.net/view.php?id=1546#c5738 Resolution: Accepted As Marked Fixed in Version: == Date Submitted: 2022-01-08 03:48 UTC Last Modified: 2022-03-12 21:12 UTC == Summary:BREs: reserve \? \+ and \| == Relationships ID Summary -- related to 773 Summary: Add \+, \?, and \| to Basic Re... == -- (0005744) calestyo (reporter) - 2022-03-12 21:12 https://austingroupbugs.net/view.php?id=1546#c5744 -- I've just noted David Wheeler's request #773. Since this one here seems to have been accepted (?) in the sense of Geoff's wording above... it might be worth to at least *consider* whether one should go further, and simply implement 773? - The above change, would already break compatibility if anyone used "\?", "\+", and "\|" for any purpose other than those special meanings or literal value. - Previously, "\?", "\+", and "\|" would have been undefined behavior. Is it known, whether any implementa Issue History Date ModifiedUsername FieldChange == 2022-01-08 03:48 calestyo New Issue 2022-01-08 03:48 calestyo Name => Christoph Anton Mitterer 2022-01-08 03:48 calestyo Section => 9.3 Basic Regular Expressions 2022-01-08 03:48 calestyo Page Number => N/A 2022-01-08 03:48 calestyo Line Number => N/A 2022-01-28 11:21 mirabilos Note Added: 0005636 2022-01-28 23:10 calestyo Note Added: 0005639 2022-03-03 06:56 Don Cragun Note Added: 0005731 2022-03-03 07:03 Don Cragun Note Edited: 0005731 2022-03-10 17:09 geoffclare Note Added: 0005738 2022-03-10 17:09 geoffclare Interp Status => --- 2022-03-10 17:09 geoffclare Final Accepted Text => https://austingroupbugs.net/view.php?id=1546#c5738 2022-03-10 17:09 geoffclare Status New => Resolved 2022-03-10 17:09 geoffclare Resolution Open => Accepted As Marked 2022-03-10 17:10 geoffclare Tag Attached: issue8 2022-03-10 17:44 calestyo Note Added: 0005740 2022-03-12 21:01 Don Cragun Relationship added related to 773 2022-03-12 21:12 calestyo Note Added: 0005744 ==
[1003.1(2016/18)/Issue7+TC2 0001546]: BREs: reserve \? \+ and \|
The following issue has been set as RELATED TO issue 773. == https://austingroupbugs.net/view.php?id=1546 == Reported By:calestyo Assigned To: == Project:1003.1(2016/18)/Issue7+TC2 Issue ID: 1546 Category: Base Definitions and Headers Type: Enhancement Request Severity: Editorial Priority: normal Status: Resolved Name: Christoph Anton Mitterer Organization: User Reference: Section:9.3 Basic Regular Expressions Page Number:N/A Line Number:N/A Interp Status: --- Final Accepted Text:https://austingroupbugs.net/view.php?id=1546#c5738 Resolution: Accepted As Marked Fixed in Version: == Date Submitted: 2022-01-08 03:48 UTC Last Modified: 2022-03-10 17:44 UTC == Summary:BREs: reserve \? \+ and \| == Relationships ID Summary -- related to 773 Summary: Add \+, \?, and \| to Basic Re... == Issue History Date ModifiedUsername FieldChange == 2022-01-08 03:48 calestyo New Issue 2022-01-08 03:48 calestyo Name => Christoph Anton Mitterer 2022-01-08 03:48 calestyo Section => 9.3 Basic Regular Expressions 2022-01-08 03:48 calestyo Page Number => N/A 2022-01-08 03:48 calestyo Line Number => N/A 2022-01-28 11:21 mirabilos Note Added: 0005636 2022-01-28 23:10 calestyo Note Added: 0005639 2022-03-03 06:56 Don Cragun Note Added: 0005731 2022-03-03 07:03 Don Cragun Note Edited: 0005731 2022-03-10 17:09 geoffclare Note Added: 0005738 2022-03-10 17:09 geoffclare Interp Status => --- 2022-03-10 17:09 geoffclare Final Accepted Text => https://austingroupbugs.net/view.php?id=1546#c5738 2022-03-10 17:09 geoffclare Status New => Resolved 2022-03-10 17:09 geoffclare Resolution Open => Accepted As Marked 2022-03-10 17:10 geoffclare Tag Attached: issue8 2022-03-10 17:44 calestyo Note Added: 0005740 2022-03-12 21:01 Don Cragun Relationship added related to 773 ==
[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: == Project:1003.1(2016/18)/Issue7+TC2 Issue ID: 1546 Category: Base Definitions and Headers Type: Enhancement Request Severity: Editorial Priority: normal Status: Resolved Name: Christoph Anton Mitterer Organization: User Reference: Section:9.3 Basic Regular Expressions Page Number:N/A Line Number:N/A Interp Status: --- Final Accepted Text:https://austingroupbugs.net/view.php?id=1546#c5738 Resolution: Accepted As Marked Fixed in Version: == Date Submitted: 2022-01-08 03:48 UTC Last Modified: 2022-03-10 17:44 UTC == Summary:BREs: reserve \? \+ and \| == -- (0005740) calestyo (reporter) - 2022-03-10 17:44 https://austingroupbugs.net/view.php?id=1546#c5740 -- Sounds good to me. Though for the first part (escape sequence) I would more clearly mention that "escape character " means that it's a backslash that is not escaped itself. While this may already be perfectly clear to anyone who is very deep into the language of the standard, it may not be that obvious to others... Issue History Date ModifiedUsername FieldChange == 2022-01-08 03:48 calestyo New Issue 2022-01-08 03:48 calestyo Name => Christoph Anton Mitterer 2022-01-08 03:48 calestyo Section => 9.3 Basic Regular Expressions 2022-01-08 03:48 calestyo Page Number => N/A 2022-01-08 03:48 calestyo Line Number => N/A 2022-01-28 11:21 mirabilos Note Added: 0005636 2022-01-28 23:10 calestyo Note Added: 0005639 2022-03-03 06:56 Don Cragun Note Added: 0005731 2022-03-03 07:03 Don Cragun Note Edited: 0005731 2022-03-10 17:09 geoffclare Note Added: 0005738 2022-03-10 17:09 geoffclare Interp Status => --- 2022-03-10 17:09 geoffclare Final Accepted Text => https://austingroupbugs.net/view.php?id=1546#c5738 2022-03-10 17:09 geoffclare Status New => Resolved 2022-03-10 17:09 geoffclare Resolution Open => Accepted As Marked 2022-03-10 17:10 geoffclare Tag Attached: issue8 2022-03-10 17:44 calestyo Note Added: 0005740 ==
[1003.1(2016/18)/Issue7+TC2 0001546]: BREs: reserve \? \+ and \|
The following issue has been RESOLVED. == https://austingroupbugs.net/view.php?id=1546 == Reported By:calestyo Assigned To: == Project:1003.1(2016/18)/Issue7+TC2 Issue ID: 1546 Category: Base Definitions and Headers Type: Enhancement Request Severity: Editorial Priority: normal Status: Resolved Name: Christoph Anton Mitterer Organization: User Reference: Section:9.3 Basic Regular Expressions Page Number:N/A Line Number:N/A Interp Status: --- Final Accepted Text:https://austingroupbugs.net/view.php?id=1546#c5738 Resolution: Accepted As Marked Fixed in Version: == Date Submitted: 2022-01-08 03:48 UTC Last Modified: 2022-03-10 17:09 UTC == Summary:BREs: reserve \? \+ and \| == Issue History Date ModifiedUsername FieldChange == 2022-01-08 03:48 calestyo New Issue 2022-01-08 03:48 calestyo Name => Christoph Anton Mitterer 2022-01-08 03:48 calestyo Section => 9.3 Basic Regular Expressions 2022-01-08 03:48 calestyo Page Number => N/A 2022-01-08 03:48 calestyo Line Number => N/A 2022-01-28 11:21 mirabilos Note Added: 0005636 2022-01-28 23:10 calestyo Note Added: 0005639 2022-03-03 06:56 Don Cragun Note Added: 0005731 2022-03-03 07:03 Don Cragun Note Edited: 0005731 2022-03-10 17:09 geoffclare Note Added: 0005738 2022-03-10 17:09 geoffclare Interp Status => --- 2022-03-10 17:09 geoffclare Final Accepted Text => https://austingroupbugs.net/view.php?id=1546#c5738 2022-03-10 17:09 geoffclare Status New => Resolved 2022-03-10 17:09 geoffclare Resolution Open => Accepted As Marked ==
[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:
==
Project:1003.1(2016/18)/Issue7+TC2
Issue ID: 1546
Category: Base Definitions and Headers
Type: Enhancement Request
Severity: Editorial
Priority: normal
Status: New
Name: Christoph Anton Mitterer
Organization:
User Reference:
Section:9.3 Basic Regular Expressions
Page Number:N/A
Line Number:N/A
Interp Status: ---
Final Accepted Text:
==
Date Submitted: 2022-01-08 03:48 UTC
Last Modified: 2022-03-10 17:09 UTC
==
Summary:BREs: reserve \? \+ and \|
==
--
(0005738) geoffclare (manager) - 2022-03-10 17:09
https://austingroupbugs.net/view.php?id=1546#c5738
--
Page and line numbers are for Issue 8 draft 2.1
After P165 line 5720, add:
escape sequenceAn escape sequence, when not in a bracket
expression, is defined as the escape character ('\\') followed
by any single character.
After P167 line 5806, add:The '?', '+', and '|'
characters; it is implemention-defined whether "\?", "\+", and "\|" each
match the literal character '?', '+', or '|', respectively, or behave as
described for the ERE special characters '?', '+', and '|', respectively
(see [xref to 9.4.3]).
Issue History
Date ModifiedUsername FieldChange
==
2022-01-08 03:48 calestyo New Issue
2022-01-08 03:48 calestyo Name => Christoph Anton
Mitterer
2022-01-08 03:48 calestyo Section => 9.3 Basic Regular
Expressions
2022-01-08 03:48 calestyo Page Number => N/A
2022-01-08 03:48 calestyo Line Number => N/A
2022-01-28 11:21 mirabilos Note Added: 0005636
2022-01-28 23:10 calestyo Note Added: 0005639
2022-03-03 06:56 Don Cragun Note Added: 0005731
2022-03-03 07:03 Don Cragun Note Edited: 0005731
2022-03-10 17:09 geoffclare Note Added: 0005738
==
[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:
==
Project:1003.1(2016/18)/Issue7+TC2
Issue ID: 1546
Category: Base Definitions and Headers
Type: Enhancement Request
Severity: Editorial
Priority: normal
Status: New
Name: Christoph Anton Mitterer
Organization:
User Reference:
Section:9.3 Basic Regular Expressions
Page Number:N/A
Line Number:N/A
Interp Status: ---
Final Accepted Text:
==
Date Submitted: 2022-01-08 03:48 UTC
Last Modified: 2022-03-03 06:56 UTC
==
Summary:BREs: reserve \? \+ and \|
==
--
(0005731) Don Cragun (manager) - 2022-03-03 06:56
https://austingroupbugs.net/view.php?id=1546#c5731
--
Re https://austingroupbugs.net/view.php?id=1546#c5636:
I don't unde3rstand what you mean when you say that BSD's use of [[:<:]]
and [[:>:]] fit into the framework.
In POSIX "[[:class:]]" is an RE that matches a single character in the
character class named "class". And the only valid character class names
are 1 to {CHARCLASS_NAME_MAX} bytes from the portable filename character
set where the 1st byte is not a digit. Neither '<' nor '>' is in the
portable filenamne character set.
Issue History
Date ModifiedUsername FieldChange
==
2022-01-08 03:48 calestyo New Issue
2022-01-08 03:48 calestyo Name => Christoph Anton
Mitterer
2022-01-08 03:48 calestyo Section => 9.3 Basic Regular
Expressions
2022-01-08 03:48 calestyo Page Number => N/A
2022-01-08 03:48 calestyo Line Number => N/A
2022-01-28 11:21 mirabilos Note Added: 0005636
2022-01-28 23:10 calestyo Note Added: 0005639
2022-03-03 06:56 Don Cragun Note Added: 0005731
==
[1003.1(2016/18)/Issue7+TC2 0001546]: BREs: reserve \? \+ and \|
A NOTE has been added to this issue. == https://www.austingroupbugs.net/view.php?id=1546 == Reported By:calestyo Assigned To: == Project:1003.1(2016/18)/Issue7+TC2 Issue ID: 1546 Category: Base Definitions and Headers Type: Enhancement Request Severity: Editorial Priority: normal Status: New Name: Christoph Anton Mitterer Organization: User Reference: Section:9.3 Basic Regular Expressions Page Number:N/A Line Number:N/A Interp Status: --- Final Accepted Text: == Date Submitted: 2022-01-08 03:48 UTC Last Modified: 2022-01-28 23:10 UTC == Summary:BREs: reserve \? \+ and \| == -- (0005639) calestyo (reporter) - 2022-01-28 23:10 https://www.austingroupbugs.net/view.php?id=1546#c5639 -- As I've said above: "But it would prevent that any conforming implementation uses these as special characters for other purposes." I don't see why unspecified should mean "reserved", neither reserved in the sense "something may not be used at all" nor in the sense "something may be used unless or a certain purpose". "they’re (hopefully) looking at existing implementations." One should hope that, but there's absolutely no guarantee that this is done. Issue History Date ModifiedUsername FieldChange == 2022-01-08 03:48 calestyo New Issue 2022-01-08 03:48 calestyo Name => Christoph Anton Mitterer 2022-01-08 03:48 calestyo Section => 9.3 Basic Regular Expressions 2022-01-08 03:48 calestyo Page Number => N/A 2022-01-08 03:48 calestyo Line Number => N/A 2022-01-28 11:21 mirabilos Note Added: 0005636 2022-01-28 23:10 calestyo Note Added: 0005639 ==
[1003.1(2016/18)/Issue7+TC2 0001546]: BREs: reserve \? \+ and \|
A NOTE has been added to this issue. == https://www.austingroupbugs.net/view.php?id=1546 == Reported By:calestyo Assigned To: == Project:1003.1(2016/18)/Issue7+TC2 Issue ID: 1546 Category: Base Definitions and Headers Type: Enhancement Request Severity: Editorial Priority: normal Status: New Name: Christoph Anton Mitterer Organization: User Reference: Section:9.3 Basic Regular Expressions Page Number:N/A Line Number:N/A Interp Status: --- Final Accepted Text: == Date Submitted: 2022-01-08 03:48 UTC Last Modified: 2022-01-28 11:21 UTC == Summary:BREs: reserve \? \+ and \| == -- (0005636) mirabilos (reporter) - 2022-01-28 11:21 https://www.austingroupbugs.net/view.php?id=1546#c5636 -- What’s the use? If POSIX says they are unspecified, they are already reserved. If POSIX is going to use them, they’re (hopefully) looking at existing implementations. By the way, the BSDs use [[:<:]] and [[:>:]] for GNU’s \< and \> which fit nicer into the framework. (mksh now supports them on nōn-BSDs as well.) Issue History Date ModifiedUsername FieldChange == 2022-01-08 03:48 calestyo New Issue 2022-01-08 03:48 calestyo Name => Christoph Anton Mitterer 2022-01-08 03:48 calestyo Section => 9.3 Basic Regular Expressions 2022-01-08 03:48 calestyo Page Number => N/A 2022-01-08 03:48 calestyo Line Number => N/A 2022-01-28 11:21 mirabilos Note Added: 0005636 ==
[1003.1(2016/18)/Issue7+TC2 0001546]: BREs: reserve \? \+ and \|
The following issue has been SUBMITTED.
==
https://www.austingroupbugs.net/view.php?id=1546
==
Reported By:calestyo
Assigned To:
==
Project:1003.1(2016/18)/Issue7+TC2
Issue ID: 1546
Category: Base Definitions and Headers
Type: Enhancement Request
Severity: Editorial
Priority: normal
Status: New
Name: Christoph Anton Mitterer
Organization:
User Reference:
Section:9.3 Basic Regular Expressions
Page Number:N/A
Line Number:N/A
Interp Status: ---
Final Accepted Text:
==
Date Submitted: 2022-01-08 03:48 UTC
Last Modified: 2022-01-08 03:48 UTC
==
Summary:BREs: reserve \? \+ and \|
Description:
At least two implementations use \? \+ and \| as special characters, namely
GNU's sed and grep as well as busybox' sed and grep.
Thereby being used by countless of systems.
There \? \+ and \| act for BREs as their unquoted (? + and |) counterparts
of EREs, bringing the same functionality to BREs.
POSXI, as of now
(https://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap09.html)
says:
The interpretation of an ordinary character preceded by an unescaped
( '\\' ) is undefined, except for:
- The characters ')', '(', '{', and '}'
- The digits 1 to 9 inclusive (see BREs Matching Multiple Characters)
- A character inside a bracket expression
so a conforming implementation either didn't support \? \+ and \| at all,
or already defined it's own semantics, as e.g. GNU did.
Desired Action:
I would propose, that POSIX doesn't standardise \? \+ and \| ... but
reserve these for that purpose.
I.e. not add the functionality as used by GNU as required for conforming
implementations, but mandating that *if* an implementation chooses to use
\? \+ and \| in some way - it has to be the counterparts of ERE's ? + and |
.
The actual effect of this to the world would be small. Implementation that
don’t already support it, wouldn’t need to add support for it.
But it would prevent that any conforming implementation uses these as
special characters for other purposes.
GNU (and I guess others) support further such uses beyond POSIX, e.g.:
\b \B \< \> \w \W \s \S (GNU's sed and grep)
and:
\` \' (GNU's sed)
I personally would rather tend not to reserve those in POSIX.
POSIX isn't GNU, and the main reason why I propose the reservation of \? \+
and \| is that these are already special in EREs.
But the others from above aren't.
==
Issue History
Date ModifiedUsername FieldChange
==
2022-01-08 03:48 calestyo New Issue
2022-01-08 03:48 calestyo Name => Christoph Anton
Mitterer
2022-01-08 03:48 calestyo Section => 9.3 Basic Regular
Expressions
2022-01-08 03:48 calestyo Page Number => N/A
2022-01-08 03:48 calestyo Line Number => N/A
==
