Signals: Is this the expected behaviour of connect() ?

Thiago Macieira thiago at
Tue Feb 26 11:28:20 GMT 2008

On Tuesday 26 February 2008 11:55:32 Percy Camilo Triveño Aucahuasi wrote:
> so is a bug? or feature?
> 2008/2/26, Thiago Macieira <thiago at>:
> > Eduardo Robles Elvira wrote:
> > >The private slot A::debugMe() is executed, triggered by B::signalB(),
> > > even if B and A are not friend classes, so it's clear that in this case
> > > connect() doesn't take into accound if the scope is private/public.
> >
> > That is correct. There's no way for QObject::connect() to know the
> > friendship between two classes and where the call to it was made.

Neither. It's an impossibility/limitation.

The correct thing would be to not allow that. But cannot be done.

  Thiago Macieira  -  thiago (AT) - thiago (AT)
    PGP/GPG: 0x6EF45358; fingerprint:
    E067 918B B660 DBD1 105C  966C 33F5 F005 6EF4 5358
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part.
URL: <>

More information about the kde-core-devel mailing list