On Fri, Jul 6, 2012 at 8:31 AM, Chris Vine <chris@xxxxxxxxxxxxxxxxxxxxx> wrote: > On Fri, 6 Jul 2012 07:29:18 -0400 > Earnie Boyd <earnie@xxxxxxxxxxxxxxxxxxxxx> wrote: > [snip] >> It may depend on which compiler, the compiler version and whose >> distribution of that compiler is being used. Are you using MSVC to >> build or are you using GCC? If the later it would help to know which >> distribution? > > I really don't think there is much point in spending significant time on > this. Maybe not ... > The overarching point is that the OP's code is not supported in > win32. But if it can work just by changing options of GCC or GCC distribution would it not be beneficial to ... > It could be said the fact that it deadlocks early on is a > feature rather than a bug, as it brings to the early attention of the > coder that he/she has got it wrong (although the proximate cause is > almost certainly the threading backend changes in glib-2.32). > > What might be beneficial is for a documentation bug to be posted with > respect to the GTK+ FAQ, which does not adequately make the point that > the advertised code on which the OP relied is for the X11 backend only. > It is not just that it won't work in win32: it won't work in wayland, > broadway or quartz either. also document that fact? -- Earnie -- https://sites.google.com/site/earnieboyd _______________________________________________ gtk-list mailing list gtk-list@xxxxxxxxx https://mail.gnome.org/mailman/listinfo/gtk-list
