Re: [PATCH] latest ash has broken 'echo' command
Marek Habersack <grendel@vip.net.pl> writes:
> > The fact of the matter for ash is, do we want it to be a shell that can o=
> nly
> > run POSIX compliant scripts (defined as scripts that can execute with all
> > POSIX compliant shells), or do we want it to be a shell that includes all
> > the optional features allowed by POSIX so that it can run shell scripts
> > that aren't POSIX compliant?
> Hmm... If it supports both optional and mandatory features allowed by POSIX
> it's still POSIX compliant, right? Then I vote for ash to support all POSIX
> features.
Remember nethack ...
POSIX says:
If ... "-n" ..., the results are implementation defined.
So a POSIX-conforming application can choose to clean the harddisk and
reboot.
There is nothing like "all POSIX features". POSIX has enough places to
allow every nonsense.
Sven
--
Sven Rudolph <sr1@sax.de> http://www.sax.de/~sr1/
Reply to: