After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 546220 - Maybe all derived classes should get their own GType automatically.
Maybe all derived classes should get their own GType automatically.
Status: RESOLVED OBSOLETE
Product: glibmm
Classification: Bindings
Component: general
2.17.x
Other All
: Normal enhancement
: ---
Assigned To: gtkmm-forge
gtkmm-forge
Depends on:
Blocks:
 
 
Reported: 2008-08-04 11:12 UTC by Murray Cumming
Modified: 2018-05-22 12:08 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Murray Cumming 2008-08-04 11:12:39 UTC 
In some cases we need to call Glib::ObjectBase("somename") to create a new GType for the derived C++ class, sometimes even just using RTTI to get a name. For instance, for derived CellRenderers or TreeModels, though I need to discover why that's really necessary.

If it's possible somehow, maybe we should just do this automatically for all derived classes.
Comment 1 Daniel Elstner 2009-09-20 08:32:38 UTC 
We cannot use real RTTI, because during the construction of an object, typeid() will return different results as the construction progresses. The usage of typeid() you are referring to is different, because it is applied directly to the type itself, rather than an object reference.

Thus, although the RTTI information is being accessed, it is not actually looked up at runtime because the type is known statically.
Comment 2 GNOME Infrastructure Team 2018-05-22 12:08:35 UTC 
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/glibmm/issues/7.