David Reid wrote: > > When this happens the function return APR_EGENERIC which means that the > user knows a problem happens, that it was related to a subsystem and > that there is more information available. They would then call another > function to get the error structure. This could then be used to generate > an error string via apr.
Offhand; this doesn't sound terribly thread safe nor reentrant. Does it make more sense for more complex functions to return a richer result? Or how are you thinking of associating the error with the additional information in a reentrant manner?
