On 8/20/05, Nick Kew <[EMAIL PROTECTED]> wrote: > Jeff Trawick wrote:
> > If APR always provides such APIs and acts like they work, what is to > > signal to a threaded APR app that they are picking up a non-threaded > > libapr? > > With reference to anything in particular? Surely you wouldn't use > apr_thread_mutex unless you were using apr_threads? Doesn't that > principle extend to other applications? perhaps I'm a library that needs to be thread-safe, and I'm called by a threaded app but find a non-thread-capable apr at load time? (too far fetched) okay ;)
