apr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Reid" <da...@jetnet.co.uk>
Subject Re: request for comments: new atomic API
Date Sun, 14 Sep 2003 13:20:47 GMT
As we're approaching the time when we do a 1.0 why not simply remove the old
interface rather than simply deprecate them? We shouldn't carry more into
1.0 then we need to after all!

Otherwise, anything that makes the api more consistent seems like a good

----- Original Message ----- 
From: "Brian Pane" <brian.pane@cnet.com>
To: <dev@apr.apache.org>
Sent: Saturday, September 13, 2003 6:46 AM
Subject: request for comments: new atomic API

> The current apr_atomic API has a couple of limitations:
> * The size of apr_atomic_t varies among platforms, which
>   makes it hard to guarantee portability of applications
>   that use this type to store large values.
> * The arithmetic functions use apr_atomic_t, while the
>   compare-and-swap function uses a mix of apr_uint32_t
>   and long int.  Thus it's impossible to portably write
>   code that uses, say, apr_atomic_dec() and apr_atomic_cas()
>   on the same variable.
> This patch presents a proposed new API in which the
> atomic functions explicitly operate on 32-bit ints.
> I'd like to add commit this new API (plus an implementation)
> next week.  But if anyone has objections or suggested changes,
> please let me know...
> Thanks,
> Brian

View raw message