Re: Documentation inconsistency

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

 



Hello,

if you are sure your software will never be compiled against older versions of GLib, then you can take it off. It's really not needed.

The fact vtable is mentioned for versions 2.32+ is because you can still use it; it didn't disappear (yet), it's just deprecated.

Best,
Gergely

On 5 Aug 2015 07:00, "Igor Korot" <ikorot01@xxxxxxxxx> wrote:
Hi, ALL,

The documentation here: states

[quote]
g_thread_init ()

void g_thread_init (gpointer vtable);

g_thread_init has been deprecated since version 2.32 and should not be
used in newly-written code.
This function is no longer necessary. The GLib threading system is
automatically initialized at the start of your program.

If you use GLib from more than one thread, you must initialize the
thread system by calling g_thread_init().
Since version 2.24, calling g_thread_init() multiple times is allowed,
but nothing happens except for the first call.
Since version 2.32, GLib does not support custom thread
implementations anymore and the vtable parameter is ignored and you
should pass NULL.
[/quote]

In the beginning it says that this function is deprecated and shuoldn't be used.
Then in the last quoted paragraph it implies that you can use it by
passing "NULL" as a parameter.

What is the proper way? What to rely on?
I can turn it off for GTK+-2.32+ (no replacement, right?), but I want
to make sure
it's a right thing to do.

Thank you.
_______________________________________________
gtk-list mailing list
gtk-list@xxxxxxxxx
https://mail.gnome.org/mailman/listinfo/gtk-list
_______________________________________________
gtk-list mailing list
gtk-list@xxxxxxxxx
https://mail.gnome.org/mailman/listinfo/gtk-list

[Index of Archives]     [Touch Screen Library]     [GIMP Users]     [Gnome]     [KDE]     [Yosemite News]     [Steve's Art]

  Powered by Linux