in all translation units. That way I can easily keep track of what different parts of the program are doing at any time by modifying a single variable.
That's a nice idea. You can always put a pointer there if you need more state.
It just doesn't work on machines with different int and pointer sizes. On the benefit of interoperability, I suggest you make it a (void*). So one function can set it program_state = (void*)'K'; while some other one can set it program_state ={1, 32, 768}; and yet another can do program_state = "I'm in the middle of something here!";.
Perl actually uses
myandourto do scope.my @foo;
our $bar;
Young man, could.you explain your shitpost?
int variable => local scope => my int from the perspective of an instance
static int variable => class scope => our int, for all instances of a class
You know what's funny? In PHP it's backwards :D
well of course it is!
I said, young man, what the fuck was that post?
personally I prefer including the file
prog_constants.hint program_state; // Keeps track of stuffin all translation units. That way I can easily keep track of what different parts of the program are doing at any time by modifying a single variable.
That's a nice idea. You can always put a pointer there if you need more state.
It just doesn't work on machines with different int and pointer sizes. On the benefit of interoperability, I suggest you make it a (void*). So one function can set it
program_state = (void*)'K';while some other one can set itprogram_state ={1, 32, 768}; and yet another can doprogram_state = "I'm in the middle of something here!";.I hate how long it took me to get this, but I love it.
This is a great one. I'm definitely using it in class this fall to explain static variables.
Fun fact: I made this meme to explain my classmates static variables.