On Monday, April 30, 2012 22:36:41 Olivier Goffart wrote: > On Monday 30 April 2012 19:55:25 lars.kn...@nokia.com wrote: > > On 4/30/12 9:07 PM, "ext bradley.hug...@nokia.com" > > >> Peraps we could add back the const overload, but as deprecated? > > > > > >Too late now. Change is already in qtbase and Qt Creator. Time has > > >already been spent. Nothing we can do about that now. > > > > Agree that it's to late for this change. > > It is not too late. > When we do a SIC change in the public API, the proplem we have within qt- > project are not our main concern. > The bigger concern is all the "customers" using it. They need to do it all > at once, and they have a lesser knoweldge about the required changes than > we. > > So we can still make it less intrusive for others.
I agree with Olivier. You might think the problem is solved when you have Qt 5 and QtCreator building after changes like this, but that's nothing compared to the amount of code in the wild which is broken by changes like this. This one is particularly nasty because you can't easily grep for 'uses of the problematic methods on const QRegExp objects'. False positives would likely drown it out. Thanks, -- Stephen Kelly <stephen.ke...@kdab.com> | Software Engineer KDAB (Deutschland) GmbH & Co.KG, a KDAB Group Company www.kdab.com || Germany +49-30-521325470 || Sweden (HQ) +46-563-540090 KDAB - Qt Experts - Platform-Independent Software Solutions
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
