I don't know how else to handle this problem other than having tons of variables ...
Settings parameters. There are about 400 of them that change to control various aspect of the program.
What say ye?
I know that global objects are frowned upon
There are about 400 of them that change to control various aspect of the program.
int widget_count = settings ["widget_count"];
int widget_count = settings [WIDGET_COUNT];
It is a Mega 2560 so I have enough RAM.
This seems easy: collect a bunch of very frequently access variables and related functions that need to persist across iterations of loop() ... Pretty much all of these are accessed from other objects and functions all the time.
The reason I am asking this is because all standard C++ practices, books, and instructors say that it is bad to have objects at the global scope.
Please enter a valid email to subscribe
We need to confirm your email address.
To complete the subscription, please click the link in the
email we just sent you.
Thank you for subscribing!
via Egeo 16