Re: PATCH: zsh-4.2.1: unset does not follow spec

[Peter Stephenson <pws@csr.com>]

We discussed this problem with unset before.  I don't think we were
interested enough to do anything about it.  However, I think the
requirement that unsetting an unset variable isn't an error is explicit.

It's a question (I'm sure I or someone said this last time) of whether
you want to know whether the variable was unset by the call, or was in
an unset state at the end of the call.  I can see why you might consider
the latter more useful.  After all, you wouldn't want setting a variable
to fail if it was already set.

The zsh documentation isn't explicit about the return status.  So I
wouldn't think there's any harm in the change.

-- 
Peter Stephenson <pws@csr.com>                  Software Engineer
CSR Ltd., Science Park, Milton Road,
Cambridge, CB4 0WH, 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.

This footnote also confirms that this email message has been swept by
MIMEsweeper for the presence of computer viruses.

www.mimesweeper.com
**********************************************************************