Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: questions - calling matheval() for printf
- X-seq: zsh-workers 16023
- From: Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx>
- To: Oliver Kiddle <okiddle@xxxxxxxxxxx>, zsh-workers@xxxxxxxxxx
- Subject: Re: questions - calling matheval() for printf
- Date: Fri, 12 Oct 2001 14:19:43 +0000
- In-reply-to: <3BC6F841.8AB53A42@xxxxxxxxxxx>
- Mailing-list: contact zsh-workers-help@xxxxxxxxxx; run by ezmlm
- References: <3BC6F841.8AB53A42@xxxxxxxxxxx>
On Oct 12, 3:03pm, Oliver Kiddle wrote:
}
} What is going on with this errval and zerr/zwarn stuff? I don't
} entirely understand which I should be calling on errors and whether I
} am right to zero errval after calling matheval() and reading it?
(What's "errval"? I grepped the source but didn't find it.)
In the long ago and far away, there was only zerr(). Calling zerr() would
cause zsh to print a message to stderr and abort whatever it was doing.
Aborting wasn't always what was wanted, though, so sometimes the code
called zerr() and then zeroed the global error flag.
Later zwarn() was introduced, so one could call zerr() when zsh should
abort and zwarn() when all it needed to do was print the error message.
A sweep was done to change zerr() calls to zwarn() as appropriate, but
some of them either weren't caught or it was unclear what should happen.
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.brasslantern.com
Zsh: http://www.zsh.org | PHPerl Project: http://phperl.sourceforge.net
Messages sorted by:
Reverse Date,
Date,
Thread,
Author