On Sat, Feb 15, 2014 at 1:57 AM, Jason McIntyre <j...@cvs.openbsd.org> wrote: > CVSROOT: /cvs > Module name: src > Changes by: j...@cvs.openbsd.org 2014/02/15 02:57:31 > > Modified files: > bin/echo : echo.1 > > Log message: > schwarze poinits out that -n conflicts with posix, so document it as such, > rather than as an extension;
Conflict? What conflict? The behavior of "echo -n whatever" is explicitly left by POSIX to be implementation-defined. To quote http://pubs.opengroup.org/onlinepubs/9699919799/utilities/echo.html ---- The following operands shall be supported: string A string to be written to standard output. If the first operand is -n, or if any of the operands contain a <backslash> character, the results are implementation-defined. ---- In case it influences the documenting of this, here's how POSIX defines the phrase "implementation-defined": ---- Describes a value or behavior that is not defined by POSIX.1-2008 but is selected by an implementor. The value or behavior may vary among implementations that conform to POSIX.1-2008. An application should not rely on the existence of the value or behavior. An application that relies on such a value or behavior cannot be assured to be portable across conforming implementations. The implementor shall document such a value or behavior so that it can be used correctly by an application. ---- Philip Guenther
