Re: bugs regarding late g_thread_init() calls

 > > In my opinion what needs to be done is this: GLib should normally
 > > always be threaded (behave as if g_thread_init(NULL) had been called
 > > at the very start of main()), and g_thread_init(NULL) will thus turn
 > > into a no-op.

 > This is very hard to do. You need a way to hook the g_thread_init()
 > call into the startup sequence.

Is that necessary? Couldn't the data structures and variables which
g_thread_init() sets up just be statically initialized like they are
now by the code in g_thread_init(NULL)?


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