Re: No curl_*_strerror() for CURLUcode

2021-08-13 Thread Daniel Stenberg via curl-library
On Fri, 13 Aug 2021, Gleb Ivanovsky wrote: It is my first time contributing to libcurl. Are there additional steps required or do I just create a pull request? Nothing special, no. A pull-request is perfect and we take it from there. Perhaps eye through this first:

Re: No curl_*_strerror() for CURLUcode

2021-08-13 Thread Gleb Ivanovsky via curl-library
On Fri, Aug 13, 2021 at 12:00 PM Daniel Stenberg wrote: > > On Fri, 13 Aug 2021, Gleb Ivanovsky via curl-library wrote: > > > Would be nice to have something like: > > const char *curl_url_strerror(CURLUcode errornum); > > I agree. It would be consistent with how the API works generally. > > Do

Re: No curl_*_strerror() for CURLUcode

2021-08-13 Thread Daniel Stenberg via curl-library
On Fri, 13 Aug 2021, Gleb Ivanovsky via curl-library wrote: Would be nice to have something like: const char *curl_url_strerror(CURLUcode errornum); I agree. It would be consistent with how the API works generally. Do you want to work on it and make it happen? -- / daniel.haxx.se |

Re: External WS library?

2021-08-13 Thread Daniel Stenberg via curl-library
On Thu, 12 Aug 2021, Felipe Gasper via curl-library wrote: Regarding the plan to add WebSocket to curl, would it be useful to consider, instead of writing a new implementation, incorporating an existing library? Yes, I think that's a very sensible way to imlement the discussed API and