I read some article ,it says static concept in Java really kill object oriented concept,then why this feature still exist in java???.IT is used for utility class is less priority!!! [ November 20, 2008: Message edited by: jacob deiter ]
What do you mean by "kills object oriented concept"?
To me, this is a sort of theoretical debate, along the lines of "pure oo". Depending on how you want to define the terms, Java is or is not OO. The same goes for C++ and most other languages you could name.
There are only two hard things in computer science: cache invalidation, naming things, and off-by-one errors
The Java lanuguage supports non-object-oriented design and code as well. Everything is not "automatically" OO simply because it was written in Java.
I have seen "extremely anti-object-oriented" servlets with everything in the world (100's of statements) crammed in its service() method.
I would say, using "static" in certain places might be considered anti-OO design. Using it in other places might not be so bad. It depends on how and where it is used. [ November 20, 2008: Message edited by: James Clark ]
subject: static concept in Java really kill object oriented concept