View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0000269 | 1003.1(2004)/Issue 6 | Shell and Utilities | public | 2010-06-25 16:27 | 2015-06-18 16:37 |
| Reporter | geoffclare | Assigned To | ajosey | ||
| Priority | normal | Severity | Objection | Type | Error |
| Status | Closed | Resolution | Accepted | ||
| Name | Geoff Clare | ||||
| Organization | The Open Group | ||||
| User Reference | |||||
| Section | sed | ||||
| Page Number | 845 | ||||
| Line Number | 32735-32743 | ||||
| Interp Status | Approved | ||||
| Final Accepted Text | 0000269:0000445 | ||||
| Summary | 0000269: sed addr in braces | ||||
| Description | The description of the { command verb begins: [2addr] {function function ... } Execute a list of sed functions only when the pattern space is selected. Since it refers to "function(s)", and the beginning of the EXTENDED DESCRIPTION says a function is a command verb followed by any applicable arguments, this means sed is not required to support the use of addresses within braces. It seems likely that this is unintentional, as such usage is common in applications (and applications which use it do not appear to be having any portability problems). For example: sed -n '1,/^$/{ /^Subject: /p }' To require sed to support the use of addresses within braces, the description should use the term "editing command" instead of "function". | ||||
| Desired Action | Change "function" to "editing command" throughout the description of the { command verb. | ||||
| Tags | tc1-2008 | ||||
|
|
Copied from xcubug2.txt ERN 181 |
|
|
Interpretation response ------------------------ The standard states the requirements for the { command verb in sed, and conforming implementations must conform to this. However, concerns have been raised about this which are being referred to the sponsor. Rationale: ------------- None. Notes to the Editor (not part of this interpretation): ------------------------------------------------------- Make the change suggested by the submitter. |
|
|
Comments/objections on the proposed interpretation are due by COB Aug 31 2010 |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2010-06-25 16:27 | geoffclare | New Issue | |
| 2010-06-25 16:27 | geoffclare | Status | New => Under Review |
| 2010-06-25 16:27 | geoffclare | Assigned To | => ajosey |
| 2010-06-25 16:27 | geoffclare | Name | => Geoff Clare |
| 2010-06-25 16:27 | geoffclare | Organization | => The Open Group |
| 2010-06-25 16:27 | geoffclare | Section | => sed |
| 2010-06-25 16:27 | geoffclare | Page Number | => 845 |
| 2010-06-25 16:27 | geoffclare | Line Number | => 32735-32743 |
| 2010-06-25 16:27 | geoffclare | Interp Status | => --- |
| 2010-06-25 16:27 | geoffclare | Note Added: 0000439 | |
| 2010-06-25 16:31 | geoffclare | Relationship added | has duplicate 0000264 |
| 2010-06-26 18:06 | geoffclare | Note Added: 0000445 | |
| 2010-06-26 18:07 | geoffclare | Interp Status | --- => Pending |
| 2010-06-26 18:07 | geoffclare | Final Accepted Text | => 0000269:0000445 |
| 2010-06-26 18:07 | geoffclare | Status | Under Review => Interpretation Required |
| 2010-06-26 18:07 | geoffclare | Resolution | Open => Accepted |
| 2010-07-30 08:19 | ajosey | Interp Status | Pending => Proposed |
| 2010-07-30 08:19 | ajosey | Note Added: 0000495 | |
| 2010-09-03 16:39 | ajosey | Interp Status | Proposed => Approved |
| 2010-09-08 19:43 | Don Cragun | Tag Attached: tc1-2008 | |
| 2013-04-16 13:06 | ajosey | Status | Interpretation Required => Closed |
| 2015-06-18 16:36 | eblake | Relationship added | related to 0000944 |
| 2015-06-18 16:37 | eblake | Relationship added | related to 0000262 |
