From: "Matthias B." <msbREMOVE-THIS@winterdrache.de>
To: zsh-workers@sunsite.dk
Subject: Re: PATCH: zsh-4.2.1: unset does not follow spec
Date: Wed, 22 Sep 2004 20:55:46 +0200 [thread overview]
Message-ID: <20040922205546.1fb37a99@buddha.localdomain.de> (raw)
In-Reply-To: <Pine.LNX.4.61.0409220822040.16822@toltec.zanshin.com>
On Wed, 22 Sep 2004 08:28:03 -0700 (PDT) Bart Schaefer
<schaefer@brasslantern.com> wrote:
> It appears to me that FreeBSD and Zsh are interpreting "could not be
> unset" to include variables that were not set in the first place.
Arguing over the letter of a specification is not useful. You'll have to
ask yourself what the user expects and wants. Users are almost always
interested in results. They want to know if a function has produced the
result that they wanted it to produce. When your boss tells you to hammer
a nail into the wall at spot X, you go there and find that there is
already a nail, what do you do? Do you go crying to your boss that you
can't finish the task? Do you think he cares? Do you think he'll
appreciate it, if you mention this as a problem in your report that could
potentially halt the complete project?
BTW, the behaviour of unset should, I think, depend on the UNSET option.
If UNSET is off, then unset should report an error if the variable is
already unset.
MSB
--
Want to learn long division in ternary?
Contact me at ICQ 2101001122212.01/0.00002
next prev parent reply other threads:[~2004-09-22 18:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-22 15:04 Sean C. Farley
2004-09-22 15:28 ` Bart Schaefer
2004-09-22 15:37 ` Sean C. Farley
2004-09-22 18:55 ` Matthias B. [this message]
2004-09-23 7:54 ` Bart Schaefer
2004-09-23 9:20 ` Peter Stephenson
2004-09-23 9:26 ` Oliver Kiddle
2004-09-23 16:14 ` Bart Schaefer
2004-09-22 15:44 ` 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=20040922205546.1fb37a99@buddha.localdomain.de \
--to=msbremove-this@winterdrache.de \
--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).