From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 9119 invoked from network); 22 Sep 2004 18:56:08 -0000 Received: from news.dotsrc.org (HELO a.mx.sunsite.dk) (130.225.247.88) by ns1.primenet.com.au with SMTP; 22 Sep 2004 18:56:08 -0000 Received: (qmail 31209 invoked from network); 22 Sep 2004 18:56:02 -0000 Received: from sunsite.dk (130.225.247.90) by a.mx.sunsite.dk with SMTP; 22 Sep 2004 18:56:02 -0000 Received: (qmail 19385 invoked by alias); 22 Sep 2004 18:55:48 -0000 Mailing-List: contact zsh-workers-help@sunsite.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 20403 Received: (qmail 19364 invoked from network); 22 Sep 2004 18:55:47 -0000 Received: from news.dotsrc.org (HELO a.mx.sunsite.dk) (130.225.247.88) by sunsite.dk with SMTP; 22 Sep 2004 18:55:47 -0000 Received: (qmail 30945 invoked from network); 22 Sep 2004 18:55:47 -0000 Received: from moutng.kundenserver.de (212.227.126.177) by a.mx.sunsite.dk with SMTP; 22 Sep 2004 18:55:45 -0000 Received: from [212.227.126.207] (helo=mrelayng.kundenserver.de) by moutng.kundenserver.de with esmtp (Exim 3.35 #1) id 1CACHI-0002Bk-00 for zsh-workers@sunsite.dk; Wed, 22 Sep 2004 20:55:44 +0200 Received: from [217.233.113.1] (helo=buddha.localdomain.de) by mrelayng.kundenserver.de with asmtp (Exim 3.35 #1) id 1CACHI-0006JN-00 for zsh-workers@sunsite.dk; Wed, 22 Sep 2004 20:55:45 +0200 Date: Wed, 22 Sep 2004 20:55:46 +0200 From: "Matthias B." To: zsh-workers@sunsite.dk Subject: Re: PATCH: zsh-4.2.1: unset does not follow spec Message-Id: <20040922205546.1fb37a99@buddha.localdomain.de> In-Reply-To: References: <20040922091323.V45751@thor.farley.org> X-Mailer: Sylpheed version 0.9.8claws (GTK+ 1.2.10; i586-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Provags-ID: kundenserver.de abuse@kundenserver.de auth:95d11223a40b7ac6df081cef1fe1fef2 X-Spam-Checker-Version: SpamAssassin 2.63 on a.mx.sunsite.dk X-Spam-Level: * X-Spam-Status: No, hits=1.6 required=6.0 tests=RCVD_IN_NJABL,RCVD_IN_SORBS autolearn=no version=2.63 X-Spam-Hits: 1.6 On Wed, 22 Sep 2004 08:28:03 -0700 (PDT) Bart Schaefer 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