--nextPart2130197.Xx14NSWD34
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

I'd like to propose a change of policy in the KDE libraries: remove all=20
virtual_hook functions from QObject-derived classes.

The reason for that is that we *already* have a virtual_hook function in=20
those classes and it's called qt_metacall. It's automatically generated=20
by moc, so we're safe that it'll always exist.

This policy is inspired in the "Using signals instead of virtual=20
functions" section of=20
http://developer.kde.org/documentation/other/binarycompatibility.html.

Given the use we've had of virtual_hooks in the KDE3 series and given that=
=20
KDE4 is supposed to be more stable than before, I think this solution=20
will be cleaner in the long run.

Also note that classes not deriving from QObject do not have this luxury.=20
If you have a tree of classes that don't use QObject, you should either=20
consider using it, if possible, or add virtual_hooks.
=2D-=20
  Thiago Macieira  -  thiago (AT) macieira.info - thiago (AT) kde.org
    PGP/GPG: 0x6EF45358; fingerprint:
    E067 918B B660 DBD1 105C  966C 33F5 F005 6EF4 5358

4. And =E6fter se scieppend ingelogode, he wr=E1t "cenn", ac eala! se=20
rihtendgesamnung andswarode "cenn: ne w=E1t h=FA cennan 'eall'. =C1stynt."

--nextPart2130197.Xx14NSWD34
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.1 (GNU/Linux)

iD8DBQBECXd4M/XwBW70U1gRAlNAAJ9f3ptoCtfQ39Fbjvmy3GgOP/QhywCePhRs
JEFWKNUiQZrfkCkjFtjeCSc=
=X/yB
-----END PGP SIGNATURE-----

--nextPart2130197.Xx14NSWD34--