2016-08-09 12:49 GMT+03:00 Daniel Stenberg <[email protected]>: > On Tue, 9 Aug 2016, Sergei Nikulov wrote: > >> All conversion is used to be done automatically by defining UNICODE and >> _UNICODE for Windows. So my idea is simple - typedef some kind of CURL_CHAR >> and use it instead of plain char. This typedef will be simple char on >> Unix/Linux variants and TCHAR for Windows. > > > I take it that's a take for using file names using unicode? > > What happens to existing applications if we'd ship a libcurl with that > enabled, won't there be (a risk of) breakage? Ie ABI incompatibility?
Theoretically, it should not for Linux/Unix, because typedef just type alias. But practically depends on gcc compiler (not sure). For Windows it definitely breaks ABI depending on UNICODE define set/not set during build. But not sure if libcurl used from common places as on Linux/Unix > > -- > > / daniel.haxx.se > > ------------------------------------------------------------------- > List admin: https://cool.haxx.se/list/listinfo/curl-library > Etiquette: https://curl.haxx.se/mail/etiquette.html -- Best Regards, Sergei Nikulov ------------------------------------------------------------------- List admin: https://cool.haxx.se/list/listinfo/curl-library Etiquette: https://curl.haxx.se/mail/etiquette.html
