Post #3921091
2026-05-19 16:37 UTC
@erisceleste@tech.lgbt @eniko@mastodon.gamedev.place abusing the preprocessor is imo something that should never be done as it makes the code significantly more difficult to read, as a reader needs to think about what the macro will do, and such macros are usually written in a way that is completely unreadable
Replies (1)
-
@erisceleste@tech.lgbt 2026-05-19 17:00
@SRAZKVT@tech.lgbt well, you get into interesting library design philosophy questions there a well-designed library interface for any feature shouldn't leave the user needing to think about how its macros expand any more than they usually should think about what lies behind a function call boundary - which is a non-zero amount of the time but it is comparatively very low (obviously anything built with #include INCREMENT failed hard at the first hurdle but ygwim) @eniko@mastodon.gamedev.place