.
Last update: 1997-05-20
9945-2-35.2
_____________________________________________________________________________
Topic: Sed editing commands
Relevant Sections: 4.55.7.3
Classification: Defects
Defect Report:
-----------------------
Reference: Page 410, Section 4.55.7.3, "sed Editing Commands".
(i) Lines 8700-8703:
Was it the intention of the standard to change historical
practice by not including 'n' as a command which can cause
the appended text to be written to standard output?
(ii) Lines 8727-8734:
The newline character is listed in Table 2-16. Was it the
intent of the standard to change historical practice by having
sed display the newline terminating each line in a special
format?
(iii) Lines 8767-8770:
Was it the intent of the standard to change historic practice
by not discarding the backslashes from the replacement string?
Please clarify this.
(Keith Bostic)
WG15 response for 9945-2:1993
-----------------------------------
(i) The standard states that the N command only is acceptable in this
case, and conforming implementations shall conform to this.
Concerns about the wording of this part of the standard have
been forwarded to the sponsor.
(ii)The standard states that sed shall display the newline
terminating each line in a special format, and conforming
implementations shall conform to this.
Concerns about the wording of this part of the standard have
been forwarded to the sponsor.
(iii)The standard states that "For each backslash (\) encountered
in scanning replacement from beginning to end, the following character
shall lose its special meaning (if any)", and conforming
implementations shall conform to this.
Concerns about the wording of this part of the standard have
been forwarded to the sponsor.
Rationale for Interpretation:
-----------------------------
None.
_____________________________________________________________________________