On 2 Jul 2001, Jeff Trawick wrote: > > We didn't catch this part, though. The apr_lock_t is pcalloc'ed just > > prior to calling create_lock(). Do we really need to do this? If so, > > feel free to add it in... > > no prob, but sanity check the reasoning: > > the app may need to know when the pthread handle vs. the int handle is > being used, thus the storing of -1 in the int handle and the NULL in > the pthread handle
Makes sense to me. All you should have to do is set the -1 (the NULL is implicit from the pcalloc). Right? --Cliff -------------------------------------------------------------- Cliff Woolley [EMAIL PROTECTED] Charlottesville, VA
