Buy commercial curl support from WolfSSL. We help you work
out your issues, debug your libcurl applications, use the API, port to new
platforms, add new features and more. With a team lead by the curl founder
himself.
Re: How to handle _wcsdup() memory allocation
- Contemporary messages sorted: [ by date ] [ by thread ] [ by subject ] [ by author ] [ by messages with attachments ]
From: Daniel Stenberg via curl-library <curl-library_at_cool.haxx.se>
Date: Fri, 30 Jul 2021 12:43:08 +0200 (CEST)
On Thu, 29 Jul 2021, Jeff Mears via curl-library wrote:
> Another answer would be for libcurl to implement its own wcsdup, because
> it's just wcslen + Curl_cmalloc + memcpy.
Not being a Windows guy at all, this seems like the most reasonable way that
doesn't introduce a new API and make things work transparently. Is there a
downside with this?
Feel like making a PR?
Date: Fri, 30 Jul 2021 12:43:08 +0200 (CEST)
On Thu, 29 Jul 2021, Jeff Mears via curl-library wrote:
> Another answer would be for libcurl to implement its own wcsdup, because
> it's just wcslen + Curl_cmalloc + memcpy.
Not being a Windows guy at all, this seems like the most reasonable way that
doesn't introduce a new API and make things work transparently. Is there a
downside with this?
Feel like making a PR?
-- / daniel.haxx.se | Commercial curl support up to 24x7 is available! | Private help, bug fixes, support, ports, new features | https://www.wolfssl.com/contact/ ------------------------------------------------------------------- Unsubscribe: https://cool.haxx.se/list/listinfo/curl-library Etiquette: https://curl.se/mail/etiquette.htmlReceived on 2021-07-30