moparisthebest/curl
1
0
Fork 0
mirror of https://github.com/moparisthebest/curl synced 2024-12-21 23:58:49 -05:00
Code Issues Releases Wiki Activity

Jason Nye pointed out that callbacks don't need to use the "C namespace"

Browse Source
This commit is contained in:
Daniel Stenberg 2004-07-14 15:32:09 +00:00
parent 0c54013ee3
commit a92b7c1b16
1 changed files with 5 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
docs/libcurl/libcurl-tutorial.3
View File

@ -571,24 +571,20 @@ CURLOPT_PROGRESSDATA. libcurl won't touch it.
There's basically only one thing to keep in mind when using C++ instead of C
when interfacing libcurl:
"The Callbacks Must Be Plain C"
The callbacks CANNOT be non-static class member functions
So if you want a write callback set in libcurl, you should put it within
\&'extern'. Similar to this:
Example C++ code:
.nf
extern "C" {
size_t write_data(void *ptr, size_t size, size_t nmemb,
void *ourpointer)
class AClass {
static size_t write_data(void *ptr, size_t size, size_t nmemb,
void *ourpointer)
{
/* do what you want with the data */
}
}
.fi
This will of course effectively turn the callback code into C. There won't be
any "this" pointer available etc.
.SH "Proxies"
What "proxy" means according to Merriam-Webster: "a person authorized to act