Game runtime - disabling development features at compile time

[clagrisenti]

Hey everyone,
I just started out checking out this project while learning C++ and I wondered about creating new flags to disable some features for development (similar to the custom asserts) for performance improvements for the release version.
Some features that came to mind was the log and profiler section of the code. I created the NO_LOG and NO_PROFILER flags that disable the entire code using if constexpr (...).
I thought about this while learning about performance improvements in C++ but this modifications would probably be overkill in this project.
I created 2 branches in my fork of the project if you are interested.

• NO_LOG
• NO_PROFILER

Thanks and kudos to all the developer of the project

[ManDude]

The profiler is off by default. There is literally no performance improvement brought about by that change because the branch you removed only runs if the user turns on a checkbox that is off by default.

For the logging tools, there is no interest in removing all information logging because that makes debugging and tech support borderline impossible. If there is a non-negligible performance impact of the logging messages, this should be profiled to see if there is a specific message or set of messages that are causing too much overhead. By itself, the logging system is sufficiently fast. OpenGOAL is not a CPU-throttled application, it is GPU-throttled.