zhomeslice:
so lets say for argument sake, I have 30 different location out there to set the PWM analogWrite(), now lets say I wanted to add my web view code. I would have to find all 30 locations and make sure I save the value into my variable or i could be getting an old value. There is only one way to quickly be sure. and that is to retrieve the value from its final storage spot.
In my opinion (and it is no more than that) your starting point is on very poor foundations.
If someone has a piece of code that uses analogWrite() in several (never mind 30) different locations to set the PWM for a single pin they have already got serious problems that you just don't want to get involved with.
And, again, the user with such complex code would be much better helped by explaining how to organize it. And the need to have the PWM info in a single easily accessed variable might be just the stimulus they need to mend their ways.
...R