subversion-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject svn commit: r1639548 - /subversion/site/publish/docs/community-guide/conventions.part.html
Date Thu, 13 Nov 2014 23:14:16 GMT
Author: kotkov
Date: Thu Nov 13 23:14:16 2014
New Revision: 1639548

* publish/docs/community-guide/conventions.part.html
  (apr-pools): Provide a better example in the part of the summary covering
   the subpool creation and destruction.

Suggested by: julianfoad


Modified: subversion/site/publish/docs/community-guide/conventions.part.html
--- subversion/site/publish/docs/community-guide/conventions.part.html (original)
+++ subversion/site/publish/docs/community-guide/conventions.part.html Thu Nov 13 23:14:16
@@ -342,11 +342,11 @@ cleaned up when that pool is destroyed.<
        often, how many times, etc. thus, it should be in charge of the
        function's memory usage.</p>
-    <p>For example, the caller might know that the app will exit upon
-       the function's return. Thus, the function would create extra
-       work if it built/destroyed a pool. Instead, it should use the
-       passed-in pool, which the caller is going to be tossing as part
-       of app-exit anyway.</p>
+    <p>For example, think of a function that is being called multiple
+       times in a tight loop. The caller clears the scratch pool on each
+       iteration. Thus, the creation of an internal subpool is unnecessary
+       and could be a significant overhead; instead, the function should
+       just use the passed-in pool.</p>
 <li><p>Whenever an unbounded iteration occurs, an iteration subpool

View raw message