Doesn't this make you wish that C/C++ could more easily enforce type safety between different enums??
I wonder how much dev time has been lost in the world because someone was mistakenly comparing 2 different enums together. On Mon, Mar 7, 2011 at 2:31 PM, Daniel Stenberg <[email protected]> wrote: > On Mon, 7 Mar 2011, Saqib Ali wrote: > >> I have created 3 easy interfaces (that I know have worked in the past) and >> I'm stacking them onto a multi-interface using curl_multi_add_handle(). When >> I then run curl_multi_perform(), I'm surprised to find that it doesn't work. >> In fact the return value of curl_multi_perform is >> CURLE_UNSUPPORTED_PROTOCOL. That's very strange. > > Yes, but that's strange because CURLE_UNSUPPORTED_PROTOCOL is a CURLcode > value, while curl_multi_perform() returns a CURLMcode return code... > > Thus you didn't get that value, you must've gotten CURLM_BAD_HANDLE instead > (which is what a return code of 1 from curl_multi_perform() means). > >> Can anyone advise why this would be happening? It doesn't seem to make >> sense. > > Can you please show us some code that you try to run and tell us what > libcurl version on what operating system you're using? > > -- > > / daniel.haxx.se > ------------------------------------------------------------------- > List admin: http://cool.haxx.se/list/listinfo/curl-library > Etiquette: http://curl.haxx.se/mail/etiquette.html > ------------------------------------------------------------------- List admin: http://cool.haxx.se/list/listinfo/curl-library Etiquette: http://curl.haxx.se/mail/etiquette.html
