sendf: Curl_client_write(), make passed in buf const

This commit is contained in:
Stefan Eissing 2024-02-06 12:10:19 +01:00 committed by Daniel Stenberg
parent e26c362544
commit 5b41fac587
No known key found for this signature in database
GPG Key ID: 5CC908FDB71E12C2
3 changed files with 3 additions and 3 deletions

View File

@ -14,7 +14,7 @@ With this naming established, client writers are concerned with writing response
All code in `libcurl` that handles response data is ultimately expected to forward this data via `Curl_client_write()` to the application. The exact prototype of this function is: All code in `libcurl` that handles response data is ultimately expected to forward this data via `Curl_client_write()` to the application. The exact prototype of this function is:
``` ```
CURLcode Curl_client_write(struct Curl_easy *data, int type, char *buf, size_t blen); CURLcode Curl_client_write(struct Curl_easy *data, int type, const char *buf, size_t blen);
``` ```
The `type` argument specifies what the bytes in `buf` actually are. The following bits are defined: The `type` argument specifies what the bytes in `buf` actually are. The following bits are defined:

View File

@ -296,7 +296,7 @@ static CURLcode chop_write(struct Curl_easy *data,
The defines are in sendf.h of course. The defines are in sendf.h of course.
*/ */
CURLcode Curl_client_write(struct Curl_easy *data, CURLcode Curl_client_write(struct Curl_easy *data,
int type, char *buf, size_t blen) int type, const char *buf, size_t blen)
{ {
CURLcode result; CURLcode result;

View File

@ -55,7 +55,7 @@
* Write `len` bytes at `prt` to the client. `type` indicates what * Write `len` bytes at `prt` to the client. `type` indicates what
* kind of data is being written. * kind of data is being written.
*/ */
CURLcode Curl_client_write(struct Curl_easy *data, int type, char *ptr, CURLcode Curl_client_write(struct Curl_easy *data, int type, const char *ptr,
size_t len) WARN_UNUSED_RESULT; size_t len) WARN_UNUSED_RESULT;
/** /**