On Fri, 6 Nov 2009, Xu, Qiang (FXSGSC) wrote:

>> CURLOPT_WRITEDATA points to whatever data you want to point to. libcurl
>> doesn't touch it in any way.
>
> Shouldn't it be pointed to some file pointer for the output purpose?

If you want. Your write callback set with CURLOPT_WRITEFUNCTION is the only
one that uses that data so it can be used for anything you like.

If you *don't* use CURLOPT_WRITEFUNCTION however, you MUST make
CURLOPT_WRITEDATA be a FILE * to a valid file handle if you set the option.
But I would assume that very few applications use that default functionality.

-- 
  / daniel.haxx.se
-------------------------------------------------------------------
List admin: http://cool.haxx.se/list/listinfo/curl-library
Etiquette:  http://curl.haxx.se/mail/etiquette.html