Re: [xml] Disabling error messages (again)

[Daniel Veillard <veillard redhat com>]

On Thu, Mar 13, 2003 at 11:02:04AM -0800, Rick Jones wrote:
> > > I don't understand why clients of the library need to be saddled
> > > with its messages. If my application calls a function and an error
> > > occurs, tell my application and let it deal with it; don't tell the
> > > world.
> >
> >   Why is the existing function not usable ?
> >   http://xmlsoft.org/html/libxml-xmlerror.html#XMLSETGENERICERRORFUNC
> > or why didn't you find it ?
> > I also don't see the point of your rant about stdout and stderr...
>
>
> If one thinks of making a call into the curl library as being the same
> as making a system call, or a call into malloc() or whatnot, I could see
> where one might desire that the curl library not make calls to
> stdout/stderr/whatever since system calls and stuff like libc don't
> (usually?) do that on error.  Consider a situation where say "connect()"
> emitted a message to stderr each time a call failed - I suspect lots of
> apps would take exception to that :)
>
> Now, when a library or whatnot is still under development/debug those
> sorts of messages could be quite useful.  If it helps, presume that
> someone taking exception to those messages is really paying the
> compliment of assuming that the libcurl code is stable and robust :)
>
> I expect that for my uses, should I have problems with the defalt
> behaviour I'll try the function to change the error function.
>
> just a few thoughts,

  You totally missed my point. The library *always* redirect messages
through the error handler, the default one uses stderr. Now if you dislike
this you can capture *all* error messages with a single call to install
your own handler ... This is exactly what the funtion I pointed at allows.

Daniel

-- 
Daniel Veillard      | Red Hat Network https://rhn.redhat.com/
veillard redhat com  | libxml GNOME XML XSLT toolkit  http://xmlsoft.org/
http://veillard.com/ | Rpmfind RPM search engine http://rpmfind.net/