The following issue has been SUBMITTED. 
====================================================================== 
https://austingroupbugs.net/view.php?id=1870 
====================================================================== 
Reported By:                geoffclare
Assigned To:                
====================================================================== 
Project:                    1003.1(2024)/Issue8
Issue ID:                   1870
Category:                   Base Definitions and Headers
Type:                       Clarification Requested
Severity:                   Comment
Priority:                   normal
Status:                     New
Name:                       Geoff Clare 
Organization:               The Open Group 
User Reference:              
Section:                    9.5 Regular Expression Grammar 
Page Number:                191 
Line Number:                6814 
Interp Status:              --- 
Final Accepted Text:         
====================================================================== 
Date Submitted:             2024-11-05 16:30 UTC
Last Modified:              2024-11-05 16:30 UTC
====================================================================== 
Summary:                    ISO editors Issue 8 comment 070
Description: 
In their comment 070 on Issue 8 the ISO editors requested that the
statement "The grammar takes precedence over the text" be clarified.  The
Austin Group's response was that this change would be considered for the
next TC.

Comment 070 was specifically about section 9.5 but there are similar
statements for other grammars and these should also change.

When considering how to clarify the wording, I found myself questioning
whether the statement is actually misleading.  If a conflict between the
grammar and the text is reported in a bug, there is no guarantee that the
bug will be resolved by changing the text to match the grammar, rather than
vice versa.  Bugs in grammars have been identified in the past.

My suggested solution is to state, as we do for conflicts with the ISO C
standard, that any conflict is unintentional, while clarifying what it is
that the grammar might conflict with.

Desired Action: 
On page 160 line 5523 section 7.4 Locale Definition Grammar,
change:<blockquote>The grammar shall take precedence over the text in this
chapter.</blockquote>to:<blockquote>Any conflict between the grammar
specified in this section and requirements described in [xref to 7.1]
through [xref to 7.3], inclusive, is unintentional.</blockquote>
On page 191 line 6814 section 9.5 Regular Expression Grammar,
change:<blockquote>The grammar takes precedence over the
text.</blockquote>to:<blockquote>Any conflict between the grammars
specified in this section and requirements described in [xref to 9.1]
through [xref to 9.4], inclusive, is unintentional.</blockquote>
On page 2512 line 81713 section 2.10 Shell Grammar, change:<blockquote>This
formal syntax shall take precedence over the preceding text syntax
description.</blockquote>to:<blockquote>Any conflict between the grammar
specified in this section and requirements described in [xref to 2.1]
through [xref to 2.9], inclusive, is unintentional.</blockquote>
On page 2597 line 84860 section at, change:<blockquote>This formal syntax
shall take precedence over the preceding text syntax
description.</blockquote>to:<blockquote>Any conflict between this grammar
and requirements described elsewhere in OPERANDS is
unintentional.</blockquote>
On page 2624 line 85991 section awk, change:<blockquote>A valid program can
be represented as the non-terminal symbol <i>program</i> in the grammar.
This formal syntax shall take precedence over the preceding text syntax
description.</blockquote>to:<blockquote>Any conflict between the grammar
specified in this section and requirements described elsewhere in EXTENDED
DESCRIPTION is unintentional. A valid program can be represented as the
non-terminal symbol <i>program</i> in the grammar.</blockquote>
On page 2652 line 87127 section bc, change:<blockquote>A valid program can
be represented as the non-terminal symbol <i>program</i> in the grammar.
This formal syntax shall take precedence over the text syntax
description.</blockquote>to:<blockquote>Any conflict between the grammar
specified in this section and requirements described elsewhere in EXTENDED
DESCRIPTION is unintentional. A valid program can be represented as the
non-terminal symbol <i>program</i> in the grammar.</blockquote>
On page 2707 line 89285 section chmod, change:<blockquote>A valid
<i>symbolic_mode</i> can be represented as the non-terminal symbol
<i>symbolic_mode</i> in the grammar. This formal syntax shall take
precedence over the preceding text syntax
description.</blockquote>to:<blockquote>Any conflict between the grammar
specified in this section and requirements described elsewhere in EXTENDED
DESCRIPTION is unintentional. A valid <i>symbolic_mode</i> can be
represented as the non-terminal symbol <i>symbolic_mode</i> in the
grammar.</blockquote>

====================================================================== 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2024-11-05 16:30 geoffclare     New Issue                                    
2024-11-05 16:30 geoffclare     Name                      => Geoff Clare     
2024-11-05 16:30 geoffclare     Organization              => The Open Group  
2024-11-05 16:30 geoffclare     Section                   => 9.5 Regular
Expression Grammar
2024-11-05 16:30 geoffclare     Page Number               => 191             
2024-11-05 16:30 geoffclare     Line Number               => 6814            
2024-11-05 16:30 geoffclare     Interp Status             => ---             
======================================================================


  • [1003.1(20... Austin Group Bug Tracker via austin-group-l at The Open Group
    • [1003... Austin Group Bug Tracker via austin-group-l at The Open Group
    • [1003... Austin Group Bug 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