> -----Original Message----- > From: Development <development-boun...@qt-project.org> On Behalf Of > Shawn Rutledge > Sent: Friday, 21 February 2020 1:59 PM > To: development@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.cur...@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@qt-project.org > https://lists.qt-project.org/listinfo/development _______________________________________________ Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development