This is the mail archive of the
gsl-discuss@sources.redhat.com
mailing list for the GSL project.
Re: gsl_histogram*_clone should fail silently
- From: Achim Gaedke <Achim dot Gaedke at uni-koeln dot de>
- To: Brian Gough <bjg at network-theory dot co dot uk>
- Cc: gsl discussion list <gsl-discuss at sources dot redhat dot com>
- Date: Mon, 21 Jan 2002 18:32:34 +0100
- Subject: Re: gsl_histogram*_clone should fail silently
- References: <3C4AE14C.778AC716@uni-koeln.de> <15435.12274.673538.566684@debian>
Sorry for that ambiguous subject. Of course GSL_ERROR should be used. Before
suggesting that patch I assured that the error handler is called in every case
of failure.
To my shame I must admit, that I have forgotten to free the histograms in my
example.
Yours, Achim
Brian Gough writes:
> Hi,
>
> The general philosophy is to use GSL_ERROR for every error condition.
> In some cases this gives multiple error messages but this "is not a
> bug, it's a feature" -- more error messages, more information. For
> example, two inconsistent error messages immediately suggests an
> uninitialized variable, which is the correct interpretation here.
>
> --
> Brian