"Thorsten Glaser via austin-group-l at The Open Group"
<austin-grou...@opengroup.org> wrote:
> This is because m4.opengroup.org runs qmail, the arsehole under the MTAs,
> which auto-converted the mail from quoted-printable to 8bit, sending it
> as 8bit even to MTAs that don't offer 8BITMIME (I configured my sendmail
> not to do that as well, so I got the same truncated mail back :( other
> than qmail, exim is known to break the MIME and SMTP standards like that).
Thank you for this information.
> >From IRC:
>
> 15:57 < orbea> yash matches the bash behavior fwiw
> 16:26 < orbea> pdksh, oksh, loksh, zsh and posh match mksh's behavior with
> 'exec', everything else including
> ksh2020 and hsh match bash/yash
> 16:26 < orbea> as reproduced with: ls () { echo foo; }; exec ls
> 16:27 < miskatonic> and the difference is what?
> 16:28 < orbea> mksh prints 'foo', yash executes ls(1)
OK, mksh pdksh and posh have te same origin.
I don't know oksh, loksh
> I can live with it being open to implementations as well, but it's
> best to clarify.
Well, the Bourne Shell man page says:
The command specified by the arguments is executed in
place of this shell without creating a new process. ...
The POSIX text is:
If exec is specified with command, it shall replace the shell
with command without creating a new process. ...
So the main statement in both is that the command is executed in place of
the shell. This seems to be obviously a hint that the shell cannot run
anymore and thus the function cannot be executed.
Jörg
--
EMail:jo...@schily.net Jörg Schilling D-13353 Berlin
Blog: http://schily.blogspot.com/
URL: http://cdrecord.org/private/
http://sourceforge.net/projects/schilytools/files/
