apr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Garrett Rooney <roo...@electricjellyfish.net>
Subject Re: [PATCH] global mutex for anylock
Date Sun, 05 Feb 2006 04:34:36 GMT
On 2/4/06, William A. Rowe, Jr. <wrowe@rowe-clan.net> wrote:
> Something we need to make a decision on that was discussed on IRC...
> the new patch introduces a new enumerated possible lock type.  Now in theory,
> if you compile into a apr-util derived module built against 1.2 and prior,
> after this patch it can create an 'unknown lock type'.  Any operation on
> this apr_anylock by the older module results in APR_EINVAL.
> Do our versioning rules permit this fail (with no corruption) case to let
> us commit this to 1.3.0?  Or will this have to be an APR 2.0.0 change?

I believe this is valid in 1.3.0, we can add new enum types just like
we add new functions or #defines, it's only within a minor version
number that we can't add those.


View raw message