Re: bugs regarding late g_thread_init() calls

I am looking around and I am having trouble finding a single application
that does this new (yes, new) required initialization right.


1. Applications do not explicitly call g_thread_init and call gtk_init too late.
2. Applications call g_thread_init too late.
3. Applications call g_thread_init too early.

Does anyone want to claim a case that is right for a non-trivial application?
Something with a translated GUI.



   if (!g_thread_supported ())
       g_thread_init (NULL);

bzzzzz!  g_thread_supported called too early.

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]