alphaman-src VS spdlog

> I’m not old enough to know how much that affected full computers

I recently helped someone open source a roguelike they wrote in the 90s - https://github.com/superjamie/alphaman-src

The source is terse as you describe, some parts are written in assembly, and strings are actually one big string with functions that extract substrings. There isn't a clear PRINT statement in the whole program.

All of this because he wanted the source to fit on one floppy.

I realise this is the hard way, but my long-term intention is to reimplement Alphaman from the original source, so I figured start with the existing software interfaces.

Why a new lib instead of using or contributing to an existing one as spdlog?

https://github.com/gabime/spdlog

GitHub repo: gabime/spdlog

SpdLog https://github.com/gabime/spdlog

The usual recommendation when logging libraries are brought up is spdlog, which is however header-only. It's available on Conan-center.

* Aha! In digging up the docs for NDC, I found this[1], which does mention a book for your reading list: "Patterns for Logging Diagnostic Messages" part of the book "Pattern Languages of Program Design 3" edited by Martin et al.

[1] https://github.com/gabime/spdlog

FetchContent_Declare( spdlog GIT_REPOSITORY https://github.com/gabime/spdlog GIT_TAG origin/v1.x ) FetchContent_MakeAvailable(spdlog)

Typically, you'd use a logging library to handle stuff like this. I personally like spdlog. You use different logger functions (info, warn, error) and depending on what level you have set for the logger (or globally) some of the functions become no-ops. E.g. When not running in verbose mode all spdlog::info() do nothing.