[Development] important: upcoming rename of _qpa.h to _p.h

[marius.storm-olsen at nokia.com]

Yes, it does.
And for the case of QPA, we have said that we don't want to promise BC, but we haven't said that we will go around breaking SC for every patch release. (And we shouldn't, since SC breakage uses quite a bit of resources on all parties, so avoid them if you can.)

Like some others, I would prefer it to remain in non-private headers, while mark the QPA API with non-BC promise.
IMO, in Qt 5.1 we should be able to promise BC on the QPA APIs too.

--
.marius

From: development-bounces+marius.storm-olsen=nokia.com at qt-project.org [mailto:development-bounces+marius.storm-olsen=nokia.com at qt-project.org] On Behalf Of ext Stephen Kelly
Sent: Tuesday, April 17, 2012 10:27 AM
To: development at qt-project.org
Subject: Re: [Development] important: upcoming rename of _qpa.h to _p.h


On Tuesday, April 17, 2012 15:05:49 marius.storm-olsen at nokia.com<mailto:marius.storm-olsen at nokia.com> wrote:

> Well, that breaks SC for existing projects, which have been ok with the

> missing BC. So you want to improve by promising BC by breaking SC?



_p also means SC is not maintained.



Thanks,



--

Stephen Kelly <stephen.kelly at kdab.com<mailto:stephen.kelly at kdab.com>> | Software Engineer

KDAB (Deutschland) GmbH & Co.KG, a KDAB Group Company

www.kdab.com<http://www.kdab.com> || Germany +49-30-521325470 || Sweden (HQ) +46-563-540090

KDAB - Qt Experts - Platform-Independent Software Solutions
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/development/attachments/20120417/46522bb3/attachment.html>