I am about to rewrite most of my game after realising that the static keyword is, well, not logical in my case (I think atleast). I wrote many of my classes static - most of these classes were classes that I thought would only be initalized once. Although after realising how easy it would be to just recreate a corrupted object when a corruption occurs (by corruption I mean basically anything, from a multiplayer connection failing, to a incompatable object state) I was like "WHAT HAVE I DONE?".
What are other programmers thoughts on the static keyword in OOP?
Sure the static keyword can be extremely helpful in certain cases, but in general what do you think?
Edited by Xanather, 08 October 2012 - 05:41 AM.