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
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 into
Von: Development im Auftrag von Elias
Steurer via Development
Gesendet: Freitag, 15. Dezember 2023 14:36
An: development@qt-project.org
Betreff: [Development] Request for early MOC support for C++20 Modules
Hi Devs,
I'd like to ask about a possib
x27;s not a blocker for getting support for the "easy" parts in.
Fabian
Von: Development im Auftrag von Elias Steurer
via Development
Gesendet: Freitag, 15. Dezember 2023 14:36
An:development@qt-project.org
Betreff: [Development] Request for early MOC s
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
> https://gitlab.com/kelteseth/ScreenPlay/-/blob/master/
> 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 thi
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
questio
On Fri, Dec 15, 2023 at 04:25:43PM +, Volker Hilsheimer via Development
wrote:
> > 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 o
Il 15/12/23 21:33, Thiago Macieira ha scritto:
Is the file format for the imported modules already standardised? Is it in the
C++ standard? I don't remember seeing it there.
If it's not a standard (ISO C++ standard or otherwise), we'd need to write
format parsers for each compiler, which raises
On Monday, 18 December 2023 07:54:07 -03 Giuseppe D'Angelo via Development
wrote:
> If anything I think this discussion ties up with the one about the
> future of moc, and whether it should become a compiler plugin. In
> principle this would bypass the problem of parsing the binary module
> format
Am 16.12.2023 um 09:21 schrieb apoenitz:
I haven't tried yet, but I have the gut feeling that one should be able
to get away with
Seems your gut feeling is right. Did a little experiment[1], and ended
up with this:
class MyObject :public Object
{
M_OBJECT
public:
using Object::
11 matches
Mail list logo
