From b9183e6e724e2b3f544f1b605983c8d35a9ee153 Mon Sep 17 00:00:00 2001 From: Daniel Stenberg Date: Mon, 23 Aug 2021 08:38:32 +0200 Subject: 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 --- docs/libcurl/libcurl-errors.3 | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/libcurl/libcurl-errors.3 b/docs/libcurl/libcurl-errors.3 index fefb0ee62..707503f4e 100644 --- a/docs/libcurl/libcurl-errors.3 +++ b/docs/libcurl/libcurl-errors.3 @@ -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) .SH "CURLUcode" .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)" -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)" A malformed input was passed to a URL API function. .IP "CURLUE_BAD_PORT_NUMBER (4)" -- cgit v1.2.1