On Wednesday, May 28, 2003, at 06:33 PM, MATHIHALLI,MADHUSUDAN (HP-Cupertino,ex1) wrote:
Huh.. In that case, do we use the apr_dso_error to tell the user why the
shl_load failed ?.. Because, I don't see it.. In my case, there were a bunch
of unresolved symbols in some module, and the only error message that I got
in the log file was "unable to load blah blah blah"..
OTOH, if I enable BIND_VERBOSE, it gives me exactly what was the cause -
unresolved symbol or unable to open a dependent library or something like
that.. I would think that the users would 'prefer' to know whatz happening.
Be that as it may, it's not APR's place to start spewing random stuff (however interesting to the programmer) to stderr. APR is a general purpose library, and you have no idea what kind of application it is being used in. Perhaps it's not appropriate for there to be any output at all to the terminal? Perhaps there is no terminal at all? There's simply no way we can tell if it is or is not appropriate to send output to that file descriptor, so we must assume that we cannot.
-garrett
