apr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Cliff Woolley <jwool...@virginia.edu>
Subject Re: [doc patch] clarify the issue with uniqueness of the key in apr_pool_userdata_set
Date Thu, 25 Sep 2003 07:15:11 GMT
On Thu, 25 Sep 2003, Stas Bekman wrote:

> Hopefully this makes things less confusing.

>    *      use for their data.  It is possible to accidentally overwrite
>    *      data by choosing a key that another part of the program is using
>    *      It is advised that steps are taken to ensure that a unique
> - *      key is used at all times.
> + *      key is used at all times. This is of course inside one pool;
> + *      Two pools, or a pool and sub-pool can use identical keys.

Getting better... how about:

"... It is advised that steps are taken to ensure that unique keys are
used for all of the userdata objects in a given pool at all times.
Careful namespace prefixing of key names typically helps to ensure this
uniqueness."

--Cliff

Mime
View raw message