[Gtk-sharp-list] Fwd: Re: Gtk# instability nightmares

Alp Toker alp at atoker.com
Sun Apr 8 04:37:23 EDT 2007

Mike Kestner wrote:
> On Sat, 2007-04-07 at 19:43 +0100, Alp Toker wrote:
>> This isn't only an issue on Win32, it's an issue on any runtime that 
>> isn't Mono.
>>  From mini_init() in mono/mono/mini.c:
>> 	if (!g_thread_supported ())
>> 		g_thread_init (NULL);
> Wasn't aware of that, and it clarifies things a bit.  Thanks.

Sorry for the wording of my post, I read over it again in the morning 
and noticed it wasn't too positive ;-)

I'd actually like to see g_thread_init() removed from Mono eventually, 
and have Gtk# work by default without calling it in Application.Init(). 
I think nearly all of the major Gtk# applications are providing their 
own locking so this just adds overhead with little benefit. I'm sure 
there's a solution to the current finalizer/Idle.Add issue that doesn't 
involve relying on GLib thread support.

More information about the Gtk-sharp-list mailing list