On Wednesday 01 August 2001 08:09, Graham Leggett wrote:
> Ian Holsman wrote:
> > I mentioned this a while back
> > (as I too would like 1 apr_strerror to register callbacks) but
> > the consensus was that each library should take care of it self
>
> This is yucky - often you want a generic error handling that will print
> an error regardless of whether it originated in the OS, or some other
> library.

It doesn't make any sense to have a single library try to implement a strerror 
like call
for everything.  The application knows what kind of function it just called, so 
it knows
the correct strerror function to call.

Ryan
_____________________________________________________________________________
Ryan Bloom                              [EMAIL PROTECTED]
Covalent Technologies                   [EMAIL PROTECTED]
-----------------------------------------------------------------------------

Reply via email to