diff options
| author | Daniel Stenberg <daniel@haxx.se> | 2004-03-15 11:30:29 +0000 |
|---|---|---|
| committer | Daniel Stenberg <daniel@haxx.se> | 2004-03-15 11:30:29 +0000 |
| commit | 8114f8562b2c9762e8bd164de4b2d73b8094a781 (patch) | |
| tree | 0b59573e4857c29e0ea167c453a620b1b39ba6d2 | |
| parent | c79fa187b97ea6cf78e1162fdf04aedd32d51778 (diff) | |
use .NF for the struct part to looke better in HTML
format some function references properly
| -rw-r--r-- | docs/libcurl/curl_multi_info_read.3 | 5 |
1 files changed, 3 insertions, 2 deletions
diff --git a/docs/libcurl/curl_multi_info_read.3 b/docs/libcurl/curl_multi_info_read.3 index 4abd91e51..eb8363c0b 100644 --- a/docs/libcurl/curl_multi_info_read.3 +++ b/docs/libcurl/curl_multi_info_read.3 @@ -21,13 +21,14 @@ integer pointed to with \fImsgs_in_queue\fP will contain the number of remaining messages after this function was called. The data the returned pointer points to will not survive calling -curl_multi_cleanup(). +\fIcurl_multi_cleanup(3)\fP. The 'CURLMsg' struct is very simple and only contain very basic informations. If more involved information is wanted, the particular "easy handle" in present in that struct and can thus be used in subsequent regular -curl_easy_getinfo() calls (or similar): +\fIcurl_easy_getinfo(3)\fP calls (or similar): +.NF struct CURLMsg { CURLMSG msg; /* what this message means */ CURL *easy_handle; /* the handle it concerns */ |