Jean-Marc Ranger pointed out that the returned data doesn't survive a call

to curl_multi_remove_handle() either.
This commit is contained in:
Daniel Stenberg 2004-12-18 10:24:49 +00:00
parent a07dcfd850
commit 6e43a4ccce
1 changed files with 2 additions and 2 deletions

View File

@ -1,6 +1,6 @@
.\" $Id$
.\"
.TH curl_multi_info_read 3 "27 Feb 2002" "libcurl 7.10.3" "libcurl Manual"
.TH curl_multi_info_read 3 "18 Dec 2004" "libcurl 7.10.3" "libcurl Manual"
.SH NAME
curl_multi_info_read - read multi stack informationals
.SH SYNOPSIS
@ -21,7 +21,7 @@ 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
\fIcurl_multi_cleanup(3)\fP.
\fIcurl_multi_cleanup(3)\fP or \fIcurl_multi_remove_handle(3)\fP.
The 'CURLMsg' struct is very simple and only contain very basic information.
If more involved information is wanted, the particular "easy handle" in