Re: When to call g_thread_init(), again...
- From: "Tor Lillqvist" <tml iki fi>
- To: "Andrew W. Nosenko" <andrew w nosenko gmail com>
- Cc: gtk-devel-list gnome org
- Subject: Re: When to call g_thread_init(), again...
- Date: Fri, 15 Aug 2008 15:45:29 +0300
> For example, Glib have g_mem_set_vtable() that alose requires to be first.
Whee, so GLib documentation is internally inconsistent then. What a mess.
> Current wording of the g_thread_init() documentation doesn't
> introduces such ambiguility at least...
It doesn't? I think "You must call g_thread_init() before executing
any other GLib functions in a threaded GLib program." is pretty
unambiguous assuming you can decide what "threaded program" means.
Or do you interpret this as "once you have created a thread (thus
turning your program into a threaded one), you must call
g_thread_init()" ? I don't think that makes sense.
--tml
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]