| commit | 6ad848eb1aa26a6b940831ee4a3a788b0fd54e0d | |
| author | Stef Walter <stefw@redhat.com> | |
| Fri, 3 May 2013 06:07:19 +0000 (3 08:07 +0200) | ||
| committer | Rico Tzschichholz <ricotz@ubuntu.com> | |
| Wed, 20 Jun 2018 13:25:44 +0000 (20 15:25 +0200) | ||
| tree | 4779de4d1d245423803ac60bea280572343b067a | treesnapshot (tar.gz zip) |
| parent | 4c6ab8d3863925ed7545c4e8f16234f1dc1490b5 | commitdiff |
Use default_init instead of base_init when registering interfaces
Using base_init() is overly complex, requires multi-initialization
guards, and in the case of vala generated code these are currently
not thread safe.
The recommended approach is to use default_init() to initialize
interfaces. It is called only once, solves thread safety issues.
https://bugzilla.gnome.org/show_bug.cgi?id=699550
Using base_init() is overly complex, requires multi-initialization
guards, and in the case of vala generated code these are currently
not thread safe.
The recommended approach is to use default_init() to initialize
interfaces. It is called only once, solves thread safety issues.
https://bugzilla.gnome.org/show_bug.cgi?id=699550
| codegen/valagtypemodule.vala | diffblobblamehistory | |
| codegen/valainterfaceregisterfunction.vala | diffblobblamehistory |