A NOTE has been added to this issue. 
====================================================================== 
https://austingroupbugs.net/view.php?id=1550 
====================================================================== 
Reported By:                calestyo
Assigned To:                
====================================================================== 
Project:                    Issue 8 drafts
Issue ID:                   1550
Category:                   Shell and Utilities
Type:                       Enhancement Request
Severity:                   Editorial
Priority:                   normal
Status:                     New
Name:                       Christoph Anton Mitterer 
Organization:                
User Reference:              
Section:                    Utilities, sed 
Page Number:                3132, ff. (in the draft) 
Line Number:                see below 
Final Accepted Text:         
====================================================================== 
Date Submitted:             2022-01-14 05:32 UTC
Last Modified:              2022-04-02 19:47 UTC
====================================================================== 
Summary:                    clarifications/ambiguities in the description of
context addresses and their delimiters for sed
======================================================================
Relationships       ID      Summary
----------------------------------------------------------------------
related to          0001551 sed: ambiguities in the how BREs/EREs a...
related to          0001556 clarify meaning of \n used in a bracket...
====================================================================== 

---------------------------------------------------------------------- 
 (0005777) calestyo (reporter) - 2022-04-02 19:47
 https://austingroupbugs.net/view.php?id=1550#c5777 
---------------------------------------------------------------------- 
That indented paragraph of yours (in Note 0005775) should (if at all) only
go to the Rationale, IMO. At least the part which describes *why*
<backslash> and <newline> cannot be used.

Cause for the purpose of the standard itself it's not really relevant *why*
they mustn't be used, but only *that* this is the case.

Also, I'd rather really forbid their use, instead of just explaining why it
wouldn't work anyway.

Simply because otherwise an (crazy) implementation might try to
"workaround" that limitation in some odd way, which again makes it
non-portable. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2022-01-14 05:32 calestyo       New Issue                                    
2022-01-14 05:32 calestyo       Name                      => Christoph Anton
Mitterer
2022-01-14 05:32 calestyo       Section                   => Utilities, sed  
2022-01-14 05:32 calestyo       Page Number               => 3132, ff. (in the
draft)
2022-01-14 05:32 calestyo       Line Number               => see below       
2022-01-14 05:40 calestyo       Note Added: 0005601                          
2022-01-14 06:34 Don Cragun     Relationship added       related to 0001551  
2022-01-14 06:52 Don Cragun     Project                 
1003.1(2016/18)/Issue7+TC2 => Issue 8 drafts
2022-01-14 06:54 Don Cragun     Note Added: 0005603                          
2022-01-14 06:54 Don Cragun     version                   => Draft 2.1       
2022-03-18 11:15 geoffclare     Note Added: 0005756                          
2022-03-18 11:15 geoffclare     Note Edited: 0005756                         
2022-03-25 16:18 geoffclare     Note Added: 0005761                          
2022-03-25 16:22 geoffclare     Note Edited: 0005761                         
2022-03-26 00:08 calestyo       Note Added: 0005767                          
2022-03-26 00:34 calestyo       Note Edited: 0005767                         
2022-03-31 16:00 nick           Relationship added       related to 0001556  
2022-04-02 01:53 calestyo       Note Added: 0005771                          
2022-04-02 02:30 calestyo       Note Added: 0005772                          
2022-04-02 09:37 kre            Note Added: 0005775                          
2022-04-02 19:47 calestyo       Note Added: 0005777                          
======================================================================


        • ... Geoff Clare via austin-group-l at The Open Group
        • ... Robert Elz via austin-group-l at The Open Group
        • ... Robert Elz via austin-group-l at The Open Group
        • ... Christoph Anton Mitterer via austin-group-l at The Open Group
      • Re:... Christoph Anton Mitterer via austin-group-l at The Open Group
        • ... Geoff Clare via austin-group-l at The Open Group
          • ... Christoph Anton Mitterer via austin-group-l at The Open Group
            • ... Geoff Clare via austin-group-l at The Open Group
  • [Issue 8 dra... Austin Group Bug Tracker via austin-group-l at The Open Group
  • [Issue 8 dra... Austin Group Bug Tracker via austin-group-l at The Open Group
  • [Issue 8 dra... Austin Group Bug Tracker via austin-group-l at The Open Group
  • Re: [Issue 8... Robert Elz via austin-group-l at The Open Group
    • Re: [Is... Christoph Anton Mitterer via austin-group-l at The Open Group
      • Re:... Oğuz via austin-group-l at The Open Group
        • ... Christoph Anton Mitterer via austin-group-l at The Open Group
          • ... Lawrence Velázquez via austin-group-l at The Open Group
  • [Issue 8 dra... Austin Group Bug Tracker via austin-group-l at The Open Group
  • [Issue 8 dra... Austin Group Bug Tracker via austin-group-l at The Open Group
  • [Issue 8 dra... Austin Group Bug Tracker via austin-group-l at The Open Group
  • [Issue 8 dra... Austin Group Bug Tracker via austin-group-l at The Open Group
  • [Issue 8 dra... Austin Group Bug Tracker via austin-group-l at The Open Group

Reply via email to