[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    Re: Strange linking warnings
From:       David Faure <faure () alpha ! tat ! physik ! uni-tuebingen ! de>
Date:       1999-05-21 6:15:30
[Download RAW message or body]

On Fri, May 21, 1999 at 01:08:29AM +0200, Bernd Gehrmann wrote:
> On Thu, 20 May 1999 Dirk A. Mueller wrote:
> >David Faure <faure@alpha.tat.physik.uni-tuebingen.de> wrote:
> 
> >I didn't investigate, but until last week or so everything worked fine
> >with -fno-rtti everywhere (Qt&KDE). I used that setup since early KDE
> >pre something.
> >
> >Some changes in kdeui last week broke it. Do we really need that rtti
> >interface for KDE ?
> 
> I think it's KActions which uses dynamic_cast. Normally such
> casts can be checked with Qt's mechanism QObject::inherits(),
> but that obviously works only with classes inheriting QObject,
> which is not the case with QMenuData. 
Can't we ask TT to make QMenuData inherit QObject for that purpose ?

... but I know we use rtti in various other places as well.

> Anyway, I doubt that
> these dynamic casts are necessary. At least for KDE's purposes,
> it should be enough to check whether the given object inherits
> QPopupMenu or QMenuBar or KMenuBar. Or is there anything else
> I am missing? Taj?
> 
> Bernd.

-- 
David FAURE
david.faure@insa-lyon.fr, faure@kde.org
http://www.insa-lyon.fr/People/AEDI/dfaure/index.html 
KDE, Making The Future of Computing Available Today

[prev in list] [next in list] [prev in thread] [next in thread]