Foundation - Logging #6

Closed
opened 2026-01-04 18:35:21 +01:00 by cat · 1 comment
Owner

Logging is a must have of any game engine to quickly debug any unexpected behaviour. So to not have to shoehorn this critical feature I decided to make this.

Few Ideas:

  • Logging should allow few outputs from Critical to Debug and also require that the logger specifies where it is calling it from.
  • Run time asserts should be done by the logger with ability to log additional info with the error.
  • Logger should be able to log specific built-in classes by taking them as arguments (Expand with full reflection on C++26 for non built-in classes)
Logging is a must have of any game engine to quickly debug any unexpected behaviour. So to not have to shoehorn this critical feature I decided to make this. Few Ideas: - Logging should allow few outputs from Critical to Debug and also require that the logger specifies where it is calling it from. - Run time asserts should be done by the logger with ability to log additional info with the error. - Logger should be able to log specific built-in classes by taking them as arguments (Expand with full reflection on C++26 for non built-in classes)
cat added this to the Tourmaline Engine - Basics project 2026-01-04 18:35:21 +01:00
cat moved this to In Progress in Tourmaline Engine - Basics on 2026-01-04 18:35:32 +01:00
cat moved this to Done in Tourmaline Engine - Basics on 2026-01-04 21:35:18 +01:00
Author
Owner

Done with 8174c19f00

Done with https://git.thenight.club/cat/Tourmaline-Engine/commit/8174c19f00251e7b5c073a42deaa838ef21b2762
cat closed this issue 2026-01-04 21:35:26 +01:00
Sign in to join this conversation.