On Thu, 26 Feb 2004, Andy Serpa wrote:

> > Care to write a patch for this?

> You're talking to Mr. Non-C coder, remember? So no, I couldn't do that.

Oh well, I failed to trick you into it! ;-)

> But it should be pretty simple, no? Init the callbacks to NULL
> automatically, and if they're NULL, then don't call them. (It appears to
> call them both right away when you set the CURLOPT_SHARE option for the easy
> handle, as well as later when you actually use the handle for a transfer.)

Yeps. We use two functions for locking and unlocking internally, and I just
now made them check that the function pointers provided isn't NULL before
they're used. Fix committed just now.

> For now, I'll just use my two dummy callbacks....

That's a good work-around.

Thanks for pointing out this flaw.

-- 
    Daniel Stenberg -- http://curl.haxx.se/ -- http://daniel.haxx.se/
   [[ Do not send mails to this email address. They won't reach me. ]]