summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorjwoolley <jwoolley@13f79535-47bb-0310-9956-ffa450edef68>2003-09-26 19:13:28 +0000
committerjwoolley <jwoolley@13f79535-47bb-0310-9956-ffa450edef68>2003-09-26 19:13:28 +0000
commitad70bcfdaf0ed9490682ce9a74109a17811e371f (patch)
treef7796768054b856cf48578e508278e3291deb1fe
parent15897966394a7f5c8e04002648bb9ce4f10c620a (diff)
downloadlibapr-ad70bcfdaf0ed9490682ce9a74109a17811e371f.tar.gz
clarify docs.
submitted by: stas git-svn-id: http://svn.apache.org/repos/asf/apr/apr/trunk@64654 13f79535-47bb-0310-9956-ffa450edef68
-rw-r--r--include/apr_pools.h11
1 files changed, 6 insertions, 5 deletions
diff --git a/include/apr_pools.h b/include/apr_pools.h
index 03f498368..00cfa6149 100644
--- a/include/apr_pools.h
+++ b/include/apr_pools.h
@@ -460,11 +460,12 @@ APR_DECLARE(void) apr_pool_tag(apr_pool_t *pool, const char *tag);
*
* Users of APR must take EXTREME care when choosing a key to
* 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 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.
+ * data by choosing a key that another part of the program is using.
+ * Therefore it is advised that steps are taken to ensure that unique
+ * keys are used for all of the userdata objects in a particular pool
+ * (the same key in two different pools or a pool and one of its
+ * subpools is okay) at all times. Careful namespace prefixing of
+ * key names is a typical way to help ensure this uniqueness.
*
*/
APR_DECLARE(apr_status_t) apr_pool_userdata_set(