A NOTE has been added to this issue. 
====================================================================== 
https://www.austingroupbugs.net/view.php?id=1911 
====================================================================== 
Reported By:                dannyniu
Assigned To:                
====================================================================== 
Project:                    1003.1(2024)/Issue8
Issue ID:                   1911
Category:                   Base Definitions and Headers
Type:                       Omission
Severity:                   Editorial
Priority:                   normal
Status:                     New
Name:                       DannyNiu/NJF 
Organization:               Individual 
User Reference:              
Section:                    XBD Section 9, Regular Expressions 
Page Number:                Page 187 
Line Number:                Line 6675 Onwards 
Interp Status:              --- 
Final Accepted Text:         
====================================================================== 
Date Submitted:             2025-02-28 02:37 UTC
Last Modified:              2025-03-06 17:49 UTC
====================================================================== 
Summary:                    Clearify & consistently define "subexpression" for
ERE.
====================================================================== 

---------------------------------------------------------------------- 
 (0007096) geoffclare (manager) - 2025-03-06 17:49
 https://www.austingroupbugs.net/view.php?id=1911#c7096 
---------------------------------------------------------------------- 
Suggested changes ...

On page 187 line 6684-6686 section 9.4.1, delete:<blockquote>An ERE matching a
single character enclosed in parentheses shall match the same as the ERE without
parentheses would have matched.</blockquote>
On page 189 line 6729 section 9.4.6, change:<blockquote>1. A concatenation of
EREs shall match the concatenation of the character sequences matched by each
component of the ERE. A concatenation of EREs enclosed in parentheses shall
match whatever the concatenation without the parentheses matches. For example,
both the ERE "cd" and the ERE "(cd)" are matched by the third and fourth
character of the string "abcdefabcdef".</blockquote>to:<blockquote>1. A
concatenation of EREs shall match the concatenation of the strings matched by
each component of the ERE.

2. A subexpression can be defined within an ERE by enclosing it in parentheses.
Such a subexpression shall match whatever it would have matched without the
parentheses. For example, both the ERE "cd" and the ERE "(cd)" are matched by
the third and fourth character of the string "abcdefabcdef". Subexpressions can
be arbitrarily nested.</blockquote>
and renumber the remaining items.

On page 189 line 6734 section 9.4.6, and
page 189 line 6739 section 9.4.6, and
page 189 line 6745 section 9.4.6, and
page 189 line 6749 section 9.4.6, change:<blockquote>When an ERE matching a
single character or an ERE enclosed in parentheses is followed by
...</blockquote>to:<blockquote>When an ERE matching a single character or an ERE
subexpression is followed by ...</blockquote>
On page 189 line 6772 section 9.4.6, change:<blockquote>An ERE matching a single
character repeated by an '*', '?', or an interval expression shall not match a
null expression unless ...</blockquote>to:<blockquote>An ERE matching a single
character, or an ERE subexpression, repeated by an '*', '?', or an interval
expression shall not match a null expression unless ...</blockquote>
On page 190 line 6787 section 9.4.8,
change:<blockquote>Grouping</blockquote>to:<blockquote>Subexpressions</blockquote>


Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2025-02-28 02:37 dannyniu       New Issue                                    
2025-03-06 17:49 geoffclare     Note Added: 0007096                          
======================================================================


  • [1003.1(20... Austin Group Issue Tracker via austin-group-l at The Open Group
    • [1003... Austin Group Issue Tracker via austin-group-l at The Open Group
    • [1003... Austin Group Issue Tracker via austin-group-l at The Open Group
    • [1003... Austin Group Issue Tracker via austin-group-l at The Open Group
    • [1003... Austin Group Issue Tracker via austin-group-l at The Open Group
    • [1003... Austin Group Issue Tracker via austin-group-l at The Open Group

Reply via email to