On Monday, 24 February 2020 03:30:25 PST André Somers wrote: > > In any case, I do understand why Qt added emit as a keyword 25 years ago. > > But today, we do have IDEs which should be able to figure out on the fly > > whether a function call is a signal emission (as they already do for > > virtual vs non virtual methods). So why don’t we move the over to be a > > tooling problem? Simply highlight signal emissions differently in the IDE > > and you don’t need a keyword for it anymore. It’s also safer, as the > > keyword can be forgotten or applied to the wrong places. > > You seem to assume everyone used QtCreator as their IDE of choice. That is > not a reasonable assumption I think.
It is a reasonable feature request for ALL IDEs to understand what a Qt signal is. -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel System Software Products _______________________________________________ Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
