Lines Matching refs:POSIX

1 #	@(#)POSIX	8.1 (Berkeley) 6/6/93
14 the POSIX 1003.2 standard.  All the comments are notes taken while
15 implementing a POSIX-compatible version of sed, and should not be
16 interpreted as official opinions or criticism towards the POSIX committee.
17 All uses of "POSIX" refer to section 4.55, Draft 12 of POSIX 1003.2.
35 	POSIX does not specify this behavior as the System V versions of
46 	is obvious, but not specified in POSIX.
49 	flag to an s command.  This is not specified in POSIX.  This
54 	POSIX.  This implementation permits whitespace but does not
60 	digit octal numbers, too, not three as specified by POSIX.  POSIX
63  6.	The POSIX specification for ! does not specify that for a single
75  7.	POSIX does not specify what happens with consecutive ! commands
83 	three lines of a file.  This is not specified by POSIX.
98 	did not produce any output.  POSIX does not specify this behavior.
105 	is greater than the second (e.g. 3,1).  POSIX requires that the
107 	any particular purpose, this implementation follows the POSIX
110 12.	POSIX does not specify whether address ranges are checked and
132 	beginning of -e arguments as well as in a script file.  POSIX
136 14.	POSIX does not explicitly specify how sed behaves if no script is
144 15.	The POSIX requirement to open all w files at the beginning makes
147 	follows historic practice and POSIX, by default, and provides the
150 16.	POSIX does not specify how escape sequences other than \n and \D
154 	POSIX would be that "echo xyz | sed s/./\a" would display "\ayz".
158 17.	POSIX specifies that an address can be "empty".  This implies
163 18.	The b t and : commands are documented in POSIX to ignore leading
171 19.	Although POSIX specifies that reading from files that do not exist
179 	POSIX.  This implementation follows historic practice.
184 	within character classes.  This is not specified in POSIX.  This
189 	whether in an address or elsewhere.  POSIX does not document this