Date: Tue, 1 Apr 2025 18:38:13 +0200
Does it have to be called std::wprint? Or should we just overload std::print with wchar_t?
Don‘t forget that in order for wprint to work you also need to write a proposal for the whole formatting (e.g. std::format_string) to allow for wide chars.
BTW, I use C++ for portable code and prefer UTF-8 everywhere. Windows has a proper codepage for UTF-8 and you can call setlocale(“.utf8”) so that all Windows functions (A versions of functions instead of W versions) work with UTF-8 (e.g. file names).
If you are writing a proposal for wprint and its formatting functions, make sure it is not Windows specific—wchar_t is 32 bits on Linux! Its width is implementation defined!
On Mar 31, 2025, at 10:14 PM, Tymi via Std-Proposals <std-proposals_at_[hidden]> wrote:
Well, whatever it is, I definitely want that. I don't mind scheduling it for a later version of C++, as I understand it will take implementers and committee time and that might put C++26 away in time. I suggest I write a draft, and then we can vote & refine.Tymi.--On Sun, Mar 30, 2025 at 7:42 PM Tymi <tymi.cpp_at_[hidden]> wrote:We can schedule it for C++29 then
On Sun, Mar 30, 2025 at 7:38 PM Jonathan Wakely <cxx_at_[hidden]> wrote:On Sun, 30 Mar 2025, 11:59 Tymi via Std-Proposals, <std-proposals_at_[hidden]> wrote:It wouldn't harm anyone if it was in C++,Apart from the implementers who have to do it for you, and everybody who has to wait for other features to be implemented because that has to be done.And the people who have to maintain the spec.Every addition to the standard has a cost.also generally it would make sense to complete std::print by adding wide string support.
Std-Proposals mailing list
Std-Proposals_at_[hidden]
https://lists.isocpp.org/mailman/listinfo.cgi/std-proposals
Received on 2025-04-01 16:38:29