The Qt MOC and Preprocessor
-
wrote on 27 May 2017, 08:22 last edited by
Hi all!
I understand that the MOC tool reads any class containing Q_OBJECT (as well as any other Qt extensions such as 'signals' and 'slots') and generates a separate source file containing the appropriate member function definitions.
I also know that the MOC tool runs before the preprocessor.
What I'm wondering is if after the MOC tool generates the definitions, the preprocessor goes in and expands the Q_OBJECT macro into the source file (in order to get the function prototypes), or does the MOC tool take care of expanding macros as well?
I'm a bit confused on this point as I've heard that starting with Qt 5.0, the MOC is capable of macro expansion... Does the preprocessor still run after the MOC then?
Thanks for your time!
-
Moc is a pre-compilation step. It is a separate tool, does not communicate with the compiler in any way and does not modify the files it processes. All its work results are placed in a separate file. Basically it just reads some code and generates more files for the compiler to compile.
So the basic toolchain without moc is:
compiler foo.h foo.cpp ->foo.obj
linker foo.obj -> foo.exe
and with moc it's
moc foo.h -> moc_foo.cpp
compiler foo.h foo.cpp -> foo.obj
compiler foo.h moc_foo.cpp -> moc_foo.obj
linker foo.obj moc_foo.obj -> foo.exeAs for the "moc understands macros" part - it just means that it runs its own pre-processing pass to make sure macros are respected ie. something like this
#if 0 Q_OBJECT #endifwill be understood and no code will be generated, where previously it would generate unconditionally. It has nothing to do with macro expansion the compiler does when it runs.
Q_OBJECT is special only for moc. It understands what it is and generates members implementations in the
moc_foo.cpp. For compiler Q_OBJECT is just a regular macro and is expanded as usual to crate the members declarations while processingfoo.h. -
Moc is a pre-compilation step. It is a separate tool, does not communicate with the compiler in any way and does not modify the files it processes. All its work results are placed in a separate file. Basically it just reads some code and generates more files for the compiler to compile.
So the basic toolchain without moc is:
compiler foo.h foo.cpp ->foo.obj
linker foo.obj -> foo.exe
and with moc it's
moc foo.h -> moc_foo.cpp
compiler foo.h foo.cpp -> foo.obj
compiler foo.h moc_foo.cpp -> moc_foo.obj
linker foo.obj moc_foo.obj -> foo.exeAs for the "moc understands macros" part - it just means that it runs its own pre-processing pass to make sure macros are respected ie. something like this
#if 0 Q_OBJECT #endifwill be understood and no code will be generated, where previously it would generate unconditionally. It has nothing to do with macro expansion the compiler does when it runs.
Q_OBJECT is special only for moc. It understands what it is and generates members implementations in the
moc_foo.cpp. For compiler Q_OBJECT is just a regular macro and is expanded as usual to crate the members declarations while processingfoo.h.wrote on 27 May 2017, 14:56 last edited byThanks so much! I had a feeling it was like this, but just wasn't sure :) Thanks again!
-
Thanks so much! I had a feeling it was like this, but just wasn't sure :) Thanks again!
wrote on 27 May 2017, 16:58 last edited by@ConcordSpark https://woboq.com/blog/moc-myths.html gives some interesting details.
-
wrote on 27 May 2017, 18:20 last edited by
@Chris-Kawa
Your post reads like poetry ;-)Eddy
-
@ConcordSpark https://woboq.com/blog/moc-myths.html gives some interesting details.
wrote on 28 May 2017, 07:28 last edited by@Eeli-K Thanks for that!
4/6