Hi, > I have a side question for this discussion(raised by Ivan in personal > conversation): > Should we also force the -fexec-charset= for the gcc-like compilers? > Currently we use the system default one, which in most cases is UTF-8.
actually, I raised this question in the personal conversation because I suspected that minGW acts differently and uses the system charset. However, I did some more testing, and it seems that I was wrong. So, I also think that no further action is required at this point. Best regards, Ivan ------------------------------ Ivan Solovev Senior Software Engineer The Qt Company GmbH Erich-Thilo-Str. 10 12489 Berlin, Germany ivan.solo...@qt.io www.qt.io Geschäftsführer: Mika Pälsi, Juha Varelius, Jouni Lintunen Sitz der Gesellschaft: Berlin, Registergericht: Amtsgericht Charlottenburg, HRB 144331 B ________________________________________ From: Development <development-boun...@qt-project.org> on behalf of Thiago Macieira <thiago.macie...@intel.com> Sent: Wednesday, June 19, 2024 5:22 PM To: development@qt-project.org Subject: Re: [Development] std::format support for Qt string types On Wednesday 19 June 2024 04:32:42 GMT-7 Giuseppe D'Angelo via Development wrote: > I wouldn't say "force", but we could certainly check for it. We depend > on that: we assume that string literals in our headers are UTF-8 encoded. > > I it worth it though? Since we're talking about user code, this would > mean a static_assert in a global header. (There's some precedent for > this, like the check for /permissive-). I don't see the point. Hardly anyone even knows the option is there for GCC and Clang, as they default to UTF-8. So it's not a problem that needs solving. We already enforce in QCoreApplication where it matters: the setlocale() call. -- Thiago Macieira - thiago.macieira (AT) intel.com Principal Engineer - Intel DCAI Fleet Systems Engineering -- Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
