4 ms·

IDEs understand preprocessor macros, so IDE features (jump2def, etc) work with this. IDEs also can expand the macro invocations. So, I prefer the macros when po

IDEs understand preprocessor macros, so IDE features (jump2def, etc) work with this. IDEs also can expand the macro invocations. So, I prefer the macros when possible :-).

deleted 2y ago
[deleted]
Someone 2y ago
> IDEs understand preprocessor macros, so IDE features (jump2def, etc) work with this. Do they? X macros often are used with token pasting (https://gcc.gnu.org/onlinedocs/cpp/Concatenation.html https://gcc.gnu.org/onlinedocs/cpp/Concatenation.html), as for example in (FTA) #define AST_BEGIN_SUBCLASSES(NAME) START_##NAME , Are modern IDEs/compiler toolchains smart enough to tell you that START_foo was created by an expansion of that macro?
- jcelerier 2y ago
  any non-toy IDE can do that. Most IDEs use clang directly for parsing nowadays.
- tom_ 2y ago
  Yes. I use this with VS2019 for generating enum names, and they interact fine with auto complete and go to definition.