Re: class referencing and type implementation mutations (Re: Audit module)
- From: Havoc Pennington <hp redhat com>
- To: Tim Janik <timj gtk org>
- Cc: Owen Taylor <otaylor redhat com>, James Henstridge <james daa com au>, Gtk+ Developers <gtk-devel-list gnome org>
- Subject: Re: class referencing and type implementation mutations (Re: Audit module)
- Date: 23 Jun 2001 17:52:15 -0400
Hi,
My remaining question on this is why a static class gets unloaded ever
at all - I would expect get_type() to result in making that class
permanently resident. I think we have code in GTK even that assumes
class_init will run only one time. I know Darin was also worried about
this behavior since Nautilus has similar assumptions. Obviously
dynamic classes would be different in this respect.
Regardless of that issue, why not put in a warning in
g_signal_lookup() etc., if the class is not registered - the silent
return of 0 is extremely hard to figure out, and calling
g_signal_lookup() on an unregistered class seems like it's always a
bug.
Havoc
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]