Re: [Development] Request for early MOC support for C++20 Modules

2023-12-15 Thread Kai Uwe Broulik
Hi, > On a related note, when moving a class to modules, it would be handy to > have a way to skip the 'Generate Missing Q_PROPERTY Members' boilerplate > code. My current classes are mostly 50% getter/setter boilerplate, and > in my opinion, this is only manageable because we split our code

Re: [Development] Request for early MOC support for C++20 Modules

2023-12-15 Thread Fabian Kosmale via Development
Hi Elias, let's get your second question out of the way: Doesn't Q_PROPERTY(Qstring text MEMBER m_text) cover that already? Now, for the actual question, moc supporting modules: That certainly wasn't a priority before CMake had official support for modules, but granted, they do now support

Re: [Development] Request for early MOC support for C++20 Modules

2023-12-15 Thread Elias Steurer via Development
Hi Fabian, >let's get your second question out of the way: Doesn't Q_PROPERTY(QString text MEMBER m_text) cover that already? No, I still need all the get/set/notify functions to change/get the variables from the outside. There is currently no way to do that, or am I missing something?

Re: [Development] Request for early MOC support for C++20 Modules

2023-12-15 Thread Sune Vuorela
On 2023-12-15, Elias Steurer via Development wrote: > No, I still need all the get/set/notify functions to change/get the > variables from the outside. There is currently no way to do that, or am > I missing something? Something like this >

Re: [Development] Request for early MOC support for C++20 Modules

2023-12-15 Thread Volker Hilsheimer via Development
> On 15 Dec 2023, at 16:19, Sune Vuorela wrote: > > On 2023-12-15, Elias Steurer via Development > wrote: >> No, I still need all the get/set/notify functions to change/get the >> variables from the outside. There is currently no way to do that, or am >> I missing something? Something like

Re: [Development] Request for early MOC support for C++20 Modules

2023-12-15 Thread Thiago Macieira
On Friday, 15 December 2023 11:07:44 -03 Fabian Kosmale via Development wrote: > 1. moc's parsing logic needs to learn about the relevant new keywords. moc > needs to know at the very least the module (partition)'s name. Please forgive my lack of knowledge on this and asking of very basic

Re: [Development] 6.7 FF vs. C++20 comparisons

2023-12-15 Thread Giuseppe D'Angelo via Development
Il 13/12/23 18:36, Thiago Macieira ha scritto: On Wednesday, 13 December 2023 08:46:57 -03 Marc Mutz via Development wrote: The question I have, therefore, is the following: is converting more classes to the new framework considered a feature as in "affected by FF"? I'd say simple changes

[Development] Update What's new in Qt 6.7 (Was: Re: HEADS-UP: Qt 6.7 Feature Freeze)

2023-12-15 Thread Tuukka Turunen via Development
Hi, There is quite a lot of things missing still from https://codereview.qt-project.org/c/qt/qtdoc/+/524057 Qt 6.7 Beta 1 release is somewhere early next week and we should publish the first iteration of the What’s new page along with it. Yours, Tuukka From: Development on

[Development] Request for early MOC support for C++20 Modules

2023-12-15 Thread Elias Steurer via Development
Hi Devs, I'd like to ask about a possible roadmap update regarding C++20 modules support in moc. There was a discussion a while ago about C++20/23 support for Qt (https://lists.qt-project.org/pipermail/development/2023-May/043823.html), and I would like to know if there has been any internal