[Development] Fixing connecting to private signals

[Thiago Macieira]

On sexta-feira, 13 de julho de 2012 10.07.04, Olivier Goffart wrote:
> > > signals:
> > >     void somethingChanged();
> > >     void somethingChanged(int, QPrivateSignal);
> > > 
> > > You can't connect to the private signal because the type QPrivateSignal
> > > is
> > > private.
> > 
> > Yes that's right.
> > But signal overload should be avoided.
> 
> Maybe moc should even warn if the signal overload another function.

That's too late for that.

http://qt-project.org/doc/qabstractsocket.html#error
http://qt-project.org/doc/qabstractsocket.html#error-2

One of them is a signal.

I actually think the warning would be a good idea, but we need a way to tell 
moc not to print it because we know about it already.

-- 
Thiago Macieira - thiago.macieira (AT) intel.com
  Software Architect - Intel Open Source Technology Center
     Intel Sweden AB - Registration Number: 556189-6027
     Knarrarnäsgatan 15, 164 40 Kista, Stockholm, Sweden
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 190 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.qt-project.org/pipermail/development/attachments/20120713/c8418e6a/attachment.sig>