Re: more details for errors

[Folkert van Heusden]

> > Some functions return an errorcode when something fails, like ERR or NULL.
> > That is not so helpfull in all situations :)
> > Maybe adding something that logs to syslog or something?
> > Like: ncurses checks for an environment ('NCURSES_DO_ERROR_LOG' or so) being
> > set and then logs to syslog.
> The debug library has a trace feature which shows the parameters for
> most (perhaps all) of the ncurses functions.  It also shows the return
> value.

Yes, but it doesn't show the reason why it failed, or does it? Like:
subwin() failed because parameters out of range or so or no memory. Stuff
like that.


Folkert van Heusden

+--------------------------------------------------------------------------+
| UNIX sysop? Then give MultiTail ( http://www.vanheusden.com/multitail/ ) |
| a try, it brings monitoring logfiles to a different level! See:          |
| http://www.vanheusden.com/multitail/features.html for a feature list.    |
+---------------------------------------------------= www.vanheusden.com =-+