From: Peter Stephenson <pws@csr.com>
To: zsh-workers@sunsite.dk
Subject: Re: Parse errors don't cause a non-zero exit code?
Date: Fri, 01 Apr 2005 13:08:05 +0100 [thread overview]
Message-ID: <200504011208.j31C86Qo018462@news01.csr.com> (raw)
In-Reply-To: <20050329231719.GH51674@dan.emsphone.com>
Dan Nelson wrote:
> A related comment: The zsh documentation uses all six combinations of
> "{exit,return} {code,value,status}", making it hard to search :(
I've committed a very dull patch to standardise on "status" for return
and exit statuses.
It's still not completely consistent about distinguishing an exit status
(the value returned by a command as seen by the caller) from a return
status (the value returned by a function or builtin as seen by the
command itself), but that would take more thought; what's more, "the
builtin/function returns status X" is a perfectly natural way of saying
"returns the exit status X" given that the command doesn't actually exit
(in the UNIX sense). In other words, I don't think I want to play any
more.
--
Peter Stephenson <pws@csr.com> Software Engineer
CSR PLC, Churchill House, Cambridge Business Park, Cowley Road
Cambridge, CB4 0WZ, UK Tel: +44 (0)1223 692070
**********************************************************************
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the system manager.
**********************************************************************
next prev parent reply other threads:[~2005-04-01 12:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-29 23:17 Dan Nelson
2005-03-31 17:14 ` Dan Nelson
2005-04-01 10:07 ` Peter Stephenson
2005-04-01 20:06 ` Dan Nelson
2005-04-01 12:08 ` Peter Stephenson [this message]
2005-04-09 0:50 ` Felipe Kellermann
2005-04-11 10:13 ` Peter Stephenson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200504011208.j31C86Qo018462@news01.csr.com \
--to=pws@csr.com \
--cc=zsh-workers@sunsite.dk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).