Thanks Mike,
Both have been fixed.
CJ
Le 17/07/2014 21:50, Mike Rumph a écrit :
A few comments on typos below:
On 7/16/2014 10:34 PM, jaillet...@apache.org wrote:
Improve layout, add trailing '.' in function description, capitalize
first letter of description, fix typo, turn \0 into \\0.
Move the detailled description after @defgroup so that it is taken
into account.
s/detailled/detailed/
Modified:
httpd/httpd/trunk/include/util_varbuf.h
Modified: httpd/httpd/trunk/include/util_varbuf.h
URL:
http://svn.apache.org/viewvc/httpd/httpd/trunk/include/util_varbuf.h?rev=1611252&r1=1611251&r2=1611252&view=diff
==============================================================================
--- httpd/httpd/trunk/include/util_varbuf.h (original)
+++ httpd/httpd/trunk/include/util_varbuf.h Thu Jul 17 05:34:12 2014
@@ -42,87 +43,93 @@ extern "C" {
.....
-/** initialize a resizable buffer. It is safe to re-initialize a
prevously
- * used ap_varbuf. The old buffer will be released when the
corresponding
- * pool is cleared. The buffer remains usable until the pool is
cleared,
- * even if the ap_varbuf was located on the stack and has gone out
of scope.
- * @param pool the pool to allocate small buffers from and to
register the
- * cleanup with
- * @param vb pointer to the ap_varbuf struct
- * @param init_size the initial size of the buffer (see
ap_varbuf_grow() for details)
+/**
+ * Initialize a resizable buffer. It is safe to re-initialize a
prevously
s/prevously/previously/
+ * used ap_varbuf. The old buffer will be released when the
corresponding
+ * pool is cleared. The buffer remains usable until the pool is
cleared,
+ * even if the ap_varbuf was located on the stack and has gone out
of scope.
+ * @param pool The pool to allocate small buffers from and
to register
+ * the cleanup with
+ * @param vb Pointer to the ap_varbuf struct
+ * @param init_size The initial size of the buffer (see
ap_varbuf_grow() for
+ * details)
*/
AP_DECLARE(void) ap_varbuf_init(apr_pool_t *pool, struct ap_varbuf
*vb,
apr_size_t init_size);
....
