The following issue has been SUBMITTED. ====================================================================== 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-02-28 02:37 UTC ====================================================================== Summary: Clearify & consistently define "subexpression" for ERE. Description: In https://www.austingroupbugs.net/view.php?id=1857 wording was revised to clarify the behavior of lazy matches. Subsequently, further issues were noted. In particular, the use of ''subpatterns'' and ''subexpressions'' were found not used consistently.
As mentioned on the mailing list, the word ''subpattern'' is eliminated by Bug-1857; ''subexpression'' were defined for BRE to mean the content of a (escaped) parenthesized substring of the spelling of an expression, however this was not done for ERE. Desired Action: On the mailing list, it was mentioned this consistency be best addressed in a separate bug. The desired action for this bug is to consistently define the term ''subexpression'' for ERE (as had been done for BRE). ====================================================================== Issue History Date Modified Username Field Change ====================================================================== 2025-02-28 02:37 dannyniu New Issue ======================================================================
