You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now the behavior or MOCKABLE_FUNCTION is that between #define ENABLE_MOCKS / #undef ENABLE_MOCKS will generate code.
This improvement wants to have MOCKABLE_FUNCTION generate SEPARATE "proper declarations for a header" and "proper definitions for a source file", possibly based on some more #defines, suggestions would be along the lines of ENABLE_HEADER_MOCKS / ENABLE_SOURCE_MOCKS.
This will greatly reduce compilation time, as the "source file" would only need be compiled once (and then used as object). This would also allow use of precompiled headers (maybe), but would greatly reduce our huge compilation times as we'd have a c_util_mocks library that would be compiled/linked once and re-used everywhere where any component of it would be used.
Best Regards,
Andrei Porumb
The text was updated successfully, but these errors were encountered:
Right now the behavior or MOCKABLE_FUNCTION is that between
#define ENABLE_MOCKS
/#undef ENABLE_MOCKS
will generate code.This improvement wants to have MOCKABLE_FUNCTION generate SEPARATE "proper declarations for a header" and "proper definitions for a source file", possibly based on some more #defines, suggestions would be along the lines of
ENABLE_HEADER_MOCKS
/ENABLE_SOURCE_MOCKS
.This will greatly reduce compilation time, as the "source file" would only need be compiled once (and then used as object). This would also allow use of precompiled headers (maybe), but would greatly reduce our huge compilation times as we'd have a c_util_mocks library that would be compiled/linked once and re-used everywhere where any component of it would be used.
Best Regards,
Andrei Porumb
The text was updated successfully, but these errors were encountered: