apr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jim Jagielski <...@jaguNET.com>
Subject Re: default locking ordering
Date Thu, 13 Oct 2005 00:37:34 GMT

On Oct 12, 2005, at 3:44 PM, Jeff Trawick wrote:

> On 10/12/05, Jim Jagielski <jim@jagunet.com> wrote:
>
>> It's looking like the logic in selecting the default lock
>> method is somewhat wonky... We recreate the order, kinda, in
>> 2 places (configure.in and proc_mutex.c), and have
>> a combo of APR_HAS and APR_USE taken from the old 1.3
>> logic.
>>
>> I'd like to propose streamlining it, doing away with the
>> APR_USE stuff and having the default order specified
>> fully in proc_mutex.c.
>>
>> Comments?
>>
>
> don't forget that hints are set for some platforms to override the
> selection algorithm; such hints are available to configure logic but
> not to proc_mutex.c unless some extra work is performed to convert
> hints into preprocessor symbols
>

Yeah, that's the tricky part... I'll see if anything I come
up with is cleaner that what we have. Just having those doubled
up APR_IFALLYES lines slap my sensitivities :)


Mime
View raw message