From: Zach Laine (whatwasthataddress_at_[hidden])
Date: 2024-03-01 00:42:40
On Thu, Feb 29, 2024 at 12:25 PM Vinnie Falco via Boost
<boost_at_[hidden]> wrote:
>
> On Thu, Feb 29, 2024 at 10:17 AM Tom Honermann via Boost
> <boost_at_[hidden]> wrote:
> > Now, Zach, as a long time SG16 participant and contributor, you know
> > full well that wchar_t doesn't imply Unicode :)
>
> I despise wchar_t and avoid it completely in public interfaces. I'll
> drop down to using it inside an implementation, but my functions which
> accept Unicode strings use char, and I perform the conversion in the
> implementation even when doing so has a performance cost (such as on
> Windows which wants a "wide string"). I try to offer only utf-8 as the
> choice of encoding for Unicode (again even on Windows).
>
> It's a thankless job but someone has to protect the world from the
> ugliness of wide characters.
Not going to argue with that at all. I also never use it. I do think
that in this case, to have that be the only character type the API
doesn't accept would be too weird.
Zach