Aaron Bannert <[EMAIL PROTECTED]> writes:
> In many cases, the underlying library can already do nested locking if
> requested. I propose we simply require that this capability be passed
> through an attribute flag in the lock initialization routine, so that
> code not requiring the nested capability can benefit from a faster
> lock/unlock cycle.
I do agree that an app should have to request it. I dunno how many
libraries support nested locking... I fear that if the app is designed
to require nested locking, APR will need to implement the nesting
itself in order for the app to work portably.
--
Jeff Trawick | [EMAIL PROTECTED] | PGP public key at web site:
http://www.geocities.com/SiliconValley/Park/9289/
Born in Roswell... married an alien...
