On Monday, 26 August 2019 09:20:49 PDT Lars Knoll wrote:
> > GCC and Clang default to UTF-8 *unless* you pass -finput-charset to
> > something different, independent of what your locale is.
>
> That wasn’t how I understood it. Here’s the corresponding man page entry
> from gcc:
>
> -finput-charse
El dilluns, 26 d’agost de 2019, a les 18:14:01 CEST, Edward Welbourne va
escriure:
> Hi all,
>
> As some have clearly noticed unprompted, I've now posted the first
> drafts of the 5.14 API change reviews [0], in accordance with QUIP 10
> [1]. Please file bugs in Jira for any changes you object t
> On 26 Aug 2019, at 07:53, Thiago Macieira wrote:
>
> On Monday, 26 August 2019 05:02:28 PDT Lars Knoll wrote:
>>> And we've done that and all of Qt's modules build like that.
>>
>> Really? It’s probably what happens in practice in most cases on Linux and
>> macOS, as their locale is utf-8, but
Hi all,
As some have clearly noticed unprompted, I've now posted the first
drafts of the 5.14 API change reviews [0], in accordance with QUIP 10
[1]. Please file bugs in Jira for any changes you object to and link
those bugs to QTBUG-77839 [2], blocking it. Please tag any changes you
make to fix
On Monday, 26 August 2019 05:02:28 PDT Lars Knoll wrote:
> > And we've done that and all of Qt's modules build like that.
>
> Really? It’s probably what happens in practice in most cases on Linux and
> macOS, as their locale is utf-8, but we do not force the input encoding to
> anything as far as
On Monday, 26 August 2019 00:42:52 PDT Olivier Goffart wrote:
> > People using std::thread are unlikely to be using QThreadStorage. If they
> > have a problem with thread_local and want to use QThreadStorage, they can
> > change the thread start too.
>
> This is not only about QThreadStorage. The
> On 23 Aug 2019, at 17:04, Thiago Macieira wrote:
>
> On Thursday, 22 August 2019 23:44:02 PDT Ville Voutilainen wrote:
>>> This doesn’t solve the problem that you’re having when you want to use
>>> anything outside the ascii range inside “literal”, as the encoding of the
>>> source code on disk
On 25.08.19 17:43, Thiago Macieira wrote:
On Sunday, 25 August 2019 00:44:51 PDT Olivier Goffart wrote:
One could fix the leak by re-implementing DllMain in QtCore and using the
DLL_THREAD_DETACH hook to delete the QAdoptedThread
https://docs.microsoft.com/en-us/windows/win32/dlls/dllmain
That
