Make Glib::Object subclassing more robust
Rearrange how we register the interfaces, properties and signals of a newly created type so that: • The outcome is independent of the order of the arguments passed to Glib::Object::Subclass or Glib::Type->register. This also avoids fallout from the change to hash randomization in perl 5.17.6. • We register things in the correct order: interfaces first, before entering class_init; then properties and signals from within class_init. This also avoids prematurely creating the new type's class.
parent
a38e5233
Please register or sign in to comment