Bug#48247: echo -n
On Mon, Oct 25, 1999 at 01:36:26AM -0400, Raul Miller wrote:
> > Rereading my copy of chapter 4.19 of the POSIX 1003.2 draft:
> >
> > <quote>
> > 4.19.3 Options
> >
> > The echo utility shall not recognize the -- argument in the manner
> > specified by utility syntax guideline 10 in 2.10.2; -- shall be
> > recognized as a string operand.
> >
> > Implementations need not support any options.
> > </quote>
> >
> > I see nothing here that forbids supporting -e
On Mon, Oct 25, 1999 at 03:48:03PM +1000, Herbert Xu wrote:
> OK, POSIX actually sanctions the use of -e *if* the string to echo
> contains back slashes. But it is not because of the above bit,
> since it is overridden by this:
...
None of the text you quoted forbids supporting -e without backslashes.
There's a very big difference between what POSIX says:
"Implementations need not support any options"
and what you're saying, which seems to be something along the lines of:
"any option not ennumerated by POSIX must not be implemented"
--
Raul
Reply to: