[Development] A modest proposal: disable lower-case keywords (emit, foreach, forever, signals, slots) by default
Mitch Curtis
mitch.curtis at qt.io
Fri Feb 21 14:13:13 CET 2020
> -----Original Message-----
> From: Development <development-bounces at qt-project.org> On Behalf Of
> Shawn Rutledge
> Sent: Friday, 21 February 2020 1:59 PM
> To: development at qt-project.org
> Subject: Re: [Development] A modest proposal: disable lower-case
> keywords (emit, foreach, forever, signals, slots) by default
>
>
> > On 21 Feb 2020, at 13:30, Mitch Curtis <mitch.curtis at qt.io> wrote:
> > How can you tell if it's a signal being emitted or just a function call without
> the emit syntax? With the emit syntax before the signal emission, it's
> immediately obvious that it's a signal. Not all signals follow the *Changed()
> naming convention, nor should they, so it becomes even less obvious in
> those cases.
>
> Invent a naming convention? Add a feature to Creator that makes it clear,
> like different syntax highlighting or a little symbol next to it?
>
> (Some people name every slot function starting with the word “slot” to make
> clear what it is.)
Or just use an existing convention, perhaps just under a different name. qEmit looks good to me.
> _______________________________________________
> Development mailing list
> Development at qt-project.org
> https://lists.qt-project.org/listinfo/development
More information about the Development
mailing list