libcurl-errors.3: clarify two CURLUcode errors

CURLUE_BAD_HANDLE and CURLUE_BAD_PARTPOINTER should be for "bad" or
wrong pointers in a generic sense, not just for NULL pointers.

Reviewed-by: Jay Satiro

Ref: #7605
Closes #7611
This commit is contained in:
Daniel Stenberg 2021-08-23 08:38:32 +02:00
parent d5a27064a0
commit b9183e6e72
No known key found for this signature in database
GPG Key ID: 5CC908FDB71E12C2

View File

@ -326,9 +326,9 @@ The requested sharing could not be done because the library you use don't have
that particular feature enabled. (Added in 7.23.0) that particular feature enabled. (Added in 7.23.0)
.SH "CURLUcode" .SH "CURLUcode"
.IP "CURLUE_BAD_HANDLE (1)" .IP "CURLUE_BAD_HANDLE (1)"
An argument that should be a CURLU pointer was passed in as a NULL. An invalid CURLU pointer was passed as argument.
.IP "CURLUE_BAD_PARTPOINTER (2)" .IP "CURLUE_BAD_PARTPOINTER (2)"
A NULL pointer was passed to the 'part' argument of \fIcurl_url_get(3)\fP. An invalid 'part' argument was passed as argument.
.IP "CURLUE_MALFORMED_INPUT (3)" .IP "CURLUE_MALFORMED_INPUT (3)"
A malformed input was passed to a URL API function. A malformed input was passed to a URL API function.
.IP "CURLUE_BAD_PORT_NUMBER (4)" .IP "CURLUE_BAD_PORT_NUMBER (4)"