What is the design pattern of a program that uses global arrays to store variables?
Specifically, I mean code structured in a way where storage is global. Bare with me, as my terminology is all over the place. If I want to create a variable, I "load" it into a global cache. Any time I want to refer to this variable, I use an index. It feels like the opposite of OOP, where there's a ton of abstraction and most objects inherit from some other object, etc... I think OpenGL employs something like what I'm trying to put a name to (i.e. one has to "bind" variables)? I just can't seem to put the right words into Google to find what I'm looking for, so I thought I'd pop a simple question here. Thank you for your help!
Specifically, I mean code structured in a way where storage is global. Bare with me, as my terminology is all over the place. If I want to create a variable, I "load" it into a global cache. Any time I want to refer to this variable, I use an index.
It feels like the opposite of OOP, where there's a ton of abstraction and most objects inherit from some other object, etc...
I think OpenGL employs something like what I'm trying to put a name to (i.e. one has to "bind" variables)?
I just can't seem to put the right words into Google to find what I'm looking for, so I thought I'd pop a simple question here. Thank you for your help!
