Searched refs:curl_escape (Results 1 – 13 of 13) sorted by relevance
31 curl_version_info.3 curl_escape.3 curl_unescape.3 curl_free.3 \50 curl_escape.html curl_unescape.html curl_free.html curl_strequal.html \70 curl_escape.pdf curl_unescape.pdf curl_free.pdf curl_strequal.pdf \
41 f 0644 cowo pppusers ${mandir}/man3/curl_escape.3 ./docs/curl_escape.3
15 curl_escape @ 6 ;
68 char *curl_escape(const char *string, int inlength) in curl_escape() function
13 curl_escape @ 12 NONAME
76 SYMBOL_VECTOR=(curl_escape=PROCEDURE)77 SYMBOL_VECTOR=(CURL_ESCAPE/curl_escape=PROCEDURE)
87 [gnv.usr.share.man.man3]curl_escape.3
39 CURL_EXTERN char *curl_escape(const char *string,
1541 CURL_EXTERN char *curl_escape(const char *string,
1938 CURL_EXTERN char *curl_escape(const char *string,
1860 d curl_escape pr * extproc('curl_escape') char *
11510 curl_escape() that would happen when realloc() returns NULL...11890 to the application, as curl_escape() and curl_unescape() do.12081 - Chris Combes pointed out a flaw in curl_escape(). I fixed. We no longer12538 - Peter Verhas pointed out that the curl_escape and curl_unscape man pages13946 - curl_escape() no longer treats already encoded characters in the input14384 - Andr�s Garc�a fixed a problem in curl_escape() and pointed out a flaw in14465 - Jim Drash suggested curl_escape() should not re-encode what already looks14476 - Talking with Jim Drash made me finally put the curl_escape and curl_unescape