3 ms·
In some ways it can be the language fault too #define TURNONFEAT 1 #include <xyz.h> or #define TURNONFEAT 0 #include <xyz.h> That can create wildly different
by sumtechguy 6y ago
In some ways it can be the language fault too
#define TURNONFEAT 1
#include <xyz.h>
or
#define TURNONFEAT 0
#include <xyz.h>
That can create wildly different includes. The upcoming modules feature in C++ may change that. But unfortunately at this point we get to live with a recompile.
Pre compiled headers took some of the sting out of it. It would be nice if they could say 'in this case at this point these flags existed and I used them I will hold onto that for this header'. That way you compile it once and the rest of the project can change things in and out. The pch way seems more 'i know I will not change the flags ever'. It was a good start. Maybe a new object type and it could even live on between compiles?