Developers and getting them to improve their code.

[Harri Porten]

On Thu, 9 Jan 2003, Benjamin Meyer wrote:

> > I can make the change to ommit the empty destructor (if we come to some
> > agreement re the benefit). But as the Q_OBJECT macro also has the purpose
> >  of supplying a className() definition it's not easy to remove without
> > breaking people's code. How about extra command line arguments ?
> 
> It would only remove ther Q_OBJECT marcro if the generated file was a 
> constructor and had no signals and no slots.  Why would you need the 
> className() function for those classes?

To check inheritence. There's for sure code out there that does

  if (o->inherits("MyDialogBase")) {
    MyDialogBase *b = (MyDialogBase*)o;
    // ...
  }

Harri.