[Development] [Releasing] HEADS-UP: Qt 5.15 Feature Freeze is in effect now
André Pönitz
apoenitz at t-online.de
Thu Feb 6 20:41:01 CET 2020
On Thu, Feb 06, 2020 at 01:51:17PM +0000, Alex Blasche wrote:
>
> > -----Original Message----- From: Development
> > <development-bounces at qt-project.org> On Behalf Of Thiago Macieira
> >
> > On Wednesday, 5 February 2020 09:41:58 PST Alexander Akulich wrote:
> > > On Wed, Feb 5, 2020 at 6:58 PM Thiago Macieira
> > >
> > > <thiago.macieira at intel.com> wrote:
> > > > The correct signal for an error situation is errorOccurred, like in
> > > > QLocalSocket and QProcess.
> > >
> > > Actually both QLocalSocket and QAbstractSocket renamed the "error()" getter
> > > to keep using "error()" signal as opposed to many other Qt modules
> > > "errorOccurred()" signals.
> >
> > Which is the opposite of QProcess and violates the naming convention. Signals
> > are named after verbs in the past tense and properties & property getters are
> > simple nouns. So "error" is the getter, "errorOccurred" is the signal.
>
> Either option solves the ambiguity. What's more important to our users - a
> consistent naming convention
> or an early warning/compile error when adopting Qt 6?
Consistent naming will be beneficial for a much longer time than any
short term incentive to adopt Qt 6.
Andre'
More information about the Development
mailing list