refactor: Replace a bunch of global vars with macro

[EttyKitty]

I'm not 100% why, but you can't reference a macro directly, i.e. array_length(macro) fails on build. Because of that, I had to assign macro into local vars beforehand.

I just want to generally note: globals that are used as constants are a bad practice. Very bad.

Todo:

• I want to see if it's possible to replace global static structs with something. Macro can't hold structs, so it should be something else. You can use a function, that'll return a struct, but this is no better in terms of reference overhead and additionally creates struct to be garbage collected on every call. So, no, there is no better way, I don' think.
• Figure out if using static variables is actually worse for performance than locals. They are. Unless you want a variable to preform like a persistent instance variable of a function, that you can modify and reference throughout your code, kinda like a global var, you shouldn't use static vars. They take up memory and are never freed, the same way as globals.
  Honestly, I'm not even sure how are they different from globals. Maybe only in how you reference them, with function_name.static_name.

[OH296]

Can we come up with some sort of standardised syntax for macro names, imo it would remove chances for confusion?

[EttyKitty]

Can we come up with some sort of standardised syntax for macro names, imo it would remove chances for confusion?

Oh, my bad. I actually forgot about it.
We already have some, not sure what prefixes to use here tho.

Maybe a better idea to just use all CAPS for them.
I guess we can start naming them by what data type they are holding.
I.e. ARR_body_parts, STR_date_time, etc.

[OH296]

Can we come up with some sort of standardised syntax for macro names, imo it would remove chances for confusion?

Oh, my bad. I actually forgot about it. We already have some, not sure what prefixes to use here tho. Maybe a better idea to just use all CAPS for them. I guess we can start naming them by what data type they are holding. I.e. ARR_body_parts, STR_date_time, etc.

forgot that this was probably on hold waiting for me to reply. I have no problem using the example approach