apr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "MATHIHALLI,MADHUSUDAN (HP-Cupertino,ex1)" <mad...@hp.com>
Subject RE: [PATCH] Be verbose during shl_load on HP-UX
Date Thu, 05 Jun 2003 01:01:34 GMT

>-----Original Message-----
>From: Sander Striker [mailto:striker@apache.org]

>> Anyways, the disconnect is because you're trying to solve 
>the case when
>> stderr is closed/disabled - and I'm not.
>> I don't think we're converging on any solution here. I'd 
>appreciate if we
>> could get more inputs to which case is more reasonable for 
>the library.
>A library can return errors from called functions.  That's it.  It's up
>to the application to handle those errors and display messages 
>if appropiate.

If I understand you correctly, libraries should return the errno (because
errors may mean strings also), and not try writing anything to stderr. The
application should do the job of writing to stderr.

Is that just your opinion OR is it accepted programming practice OR is it
documented somewhere ?..

The reason I ask this is because I know of atleast one library (pthread)
that writes stuff to stderr (ofcourse, only under some circumstances)


View raw message