X-Git-Url: https://git.m6w6.name/?a=blobdiff_plain;f=docs%2Fman%2Fhashkit_is_allocated.3;h=b4ceff29c5020170ccf11f67382055c30ffe8dcf;hb=133c8ed7290daf0143bb14fba174be39996646a6;hp=b2fcc2e8fb4c3db91f2ad579d8d1d412efa6812e;hpb=6dab4c45effc85493d9e097d0df3446e202f3e8e;p=m6w6%2Flibmemcached

diff --git a/docs/man/hashkit_is_allocated.3 b/docs/man/hashkit_is_allocated.3
index b2fcc2e8..b4ceff29 100644
--- a/docs/man/hashkit_is_allocated.3
+++ b/docs/man/hashkit_is_allocated.3
@@ -1,4 +1,4 @@
-.TH "HASHKIT_IS_ALLOCATED" "3" "January 26, 2012" "1.0.4" "libmemcached"
+.TH "HASHKIT_IS_ALLOCATED" "3" "July 05, 2012" "1.0.9" "libmemcached"
 .SH NAME
 hashkit_is_allocated \- libhashkit Documentation
 .
@@ -39,46 +39,46 @@ level margin: \\n[rst2man-indent\\n[rst2man-indent-level]]
 .UNINDENT
 .INDENT 0.0
 .TP
-.B hashkit_st *hashkit_create(hashkit_st *hash);
+.B \fI\%hashkit_st\fP *hashkit_create(\fI\%hashkit_st\fP\fI\ *hash\fP)
 .UNINDENT
 .INDENT 0.0
 .TP
-.B hashkit_st *hashkit_clone(hashkit_st *destination, const hashkit_st *ptr);
+.B \fI\%hashkit_st\fP *hashkit_clone(\fI\%hashkit_st\fP\fI\ *destination\fP, const \fI\%hashkit_st\fP\fI\ *ptr\fP)
 .UNINDENT
 .INDENT 0.0
 .TP
-.B void hashkit_free(hashkit_st *hash);
+.B void hashkit_free(\fI\%hashkit_st\fP\fI\ *hash\fP)
 .UNINDENT
 .INDENT 0.0
 .TP
-.B bool hashkit_is_allocated(const hashkit_st *hash);
+.B bool hashkit_is_allocated(const \fI\%hashkit_st\fP\fI\ *hash\fP)
 .UNINDENT
 .sp
 Compile and link with \-lhashkit
 .SH DESCRIPTION
 .sp
-The \fBhashkit_create()\fP function initializes a hashkit object for use. If
+The \fI\%hashkit_create()\fP function initializes a hashkit object for use. If
 you pass a NULL argument for hash, then the memory for the object is
 allocated. If you specify a pre\-allocated piece of memory, that is
 initialized for use.
 .sp
-The \fBhashkit_clone()\fP function initializes a hashkit object much like
-\fBhashkit_create()\fP, but instead of using default settings it will use
+The \fI\%hashkit_clone()\fP function initializes a hashkit object much like
+\fI\%hashkit_create()\fP, but instead of using default settings it will use
 the settings of the ptr hashkit object.
 .sp
-The \fBhashkit_free()\fP frees any resources being consumed by the hashkit
-objects that were initialized with \fBhashkit_create()\fP or \fBhashkit_clone()\fP.
+The \fI\%hashkit_free()\fP frees any resources being consumed by the hashkit
+objects that were initialized with \fI\%hashkit_create()\fP or \fI\%hashkit_clone()\fP.
 .sp
-The \fBhashkit_is_allocated()\fP reports where the memory was allocated
+The \fI\%hashkit_is_allocated()\fP reports where the memory was allocated
 for a hashkit object.
 .SH RETURN VALUE
 .sp
-\fBhashkit_create()\fP and \fBhashkit_clone()\fP will return NULL on
+\fI\%hashkit_create()\fP and \fI\%hashkit_clone()\fP will return NULL on
 failure or non\-NULL on success.
 .sp
-\fBhashkit_is_allocated()\fP returns true if the memory for the hashkit
-object was allocated inside of \fBhashkit_create()\fP or
-\fBhashkit_clone()\fP, otherwise it is false and was user\-supplied memory.
+\fI\%hashkit_is_allocated()\fP returns true if the memory for the hashkit
+object was allocated inside of \fI\%hashkit_create()\fP or
+\fI\%hashkit_clone()\fP, otherwise it is false and was user\-supplied memory.
 .SH HOME
 .sp
 To find out more information please check: