[Development] Source break policy for function overloads

Giuseppe D'Angelo giuseppe.dangelo at kdab.com
Wed Jul 13 14:15:44 CEST 2016

Il 13/07/2016 12:44, Alexander Blasche ha scritto:
> While talking to several devs in the office I could not find a congruent opinion on this issue. Do we or even can we care? Do we have a policy?

While it would be nice not to add overloads to signals and slots, and we 
can keep an eye on that, the fact that you can connect to *any* function 
makes such a policy hard to enforce (unless we start introducing a weird 
naming policy for functions).

Note that this has nothing to do with Qt, but it's a C++ language 
"feature" -- hence I would say that if you care about your source 
compatibility you should start using qOverload in your code base every 
time you take a pointer to a function.

My 2 cents,
Giuseppe D'Angelo | giuseppe.dangelo at kdab.com | Senior Software Engineer
KDAB (UK) Ltd., a KDAB Group company | Tel: UK +44-1625-809908
KDAB - The Qt Experts

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4007 bytes
Desc: Firma crittografica S/MIME
URL: <http://lists.qt-project.org/pipermail/development/attachments/20160713/aa519212/attachment.bin>

More information about the Development mailing list