On Wed, Aug 31, 2016 at 09:38:21AM +0200, Marc Mutz wrote: > My porting guide for Q_FOREACH -> C++11 ranged for has created the expected > outcry from users.
Expectedly so. And since you seem to be surprised: There are a few people that have just given up on commenting each and every mailing list topic, so silence does not imply affirmation. The main problem here is, again, that more or less independent issues are mangled into one: 1. The intent to not use certain functionality in Qt *internally* anymore. 2. The attempt to enforce those ideas on users. They are not completely independent, but a 'Q_FOREACH' ban in Qt proper does not have to imply its removal for users. If it is not useful in your view, you can mention it in the docs. Breaking formerly compilable code for no good reason is not a good base for a 'contract'. [Same for other 'helpful' deprecation activities or enforced development restrictions] Andre' _______________________________________________ Development mailing list [email protected] http://lists.qt-project.org/mailman/listinfo/development
