• Pierre Wieser's avatar
    Do some more tests on virtual methods handling · 0279f49d
    Pierre Wieser authored
    Rationale: The problem to solve is how to make sure all virtual methods of a class hierarchy
    will be actually invoked.
    
    It happends that this depends of whether an intemediate class which would not implement a
    virtual method set this virtual to NULL or not in its class initialization.
    
    If the virtual method pointer is set to NULL, then GObject library recognizes that the
    method is not implemented, and this actually breaks the 'call parent method' paradigm.
    
    Contrarily, if the virtual method is not set to NULL, then the GObject library automatically
    jumps to the next parent which has implemented the method. In other words, using the 'call
    parent method' paradigm implies that we never set a not-used method pointer to NULL.
    0279f49d
Name
Last commit
Last update
data Loading commit data...
docs Loading commit data...
icons Loading commit data...
m4 Loading commit data...
po Loading commit data...
src Loading commit data...
tools Loading commit data...
.gitignore Loading commit data...
AUTHORS Loading commit data...
COPYING Loading commit data...
COPYING-DOCS Loading commit data...
ChangeLog Loading commit data...
ChangeLog-2008 Loading commit data...
ChangeLog-2009 Loading commit data...
ChangeLog-2010 Loading commit data...
INSTALL Loading commit data...
MAINTAINERS Loading commit data...
Makefile.am Loading commit data...
NEWS Loading commit data...
README Loading commit data...
README-GCONF Loading commit data...
TODO Loading commit data...
autogen.sh Loading commit data...
configure.ac Loading commit data...
nautilus-actions.doap Loading commit data...
run-autogen.sh Loading commit data...
run-distcheck.sh Loading commit data...