This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
what is the process if i make a object as static? can i do this? when i make a constructor as static a object for that call becomes static.. so what happens to to the instance variables? what are the advantages of this design and its disadvantage? Is this kind of a design used often?
And an object can't be static, too. I wouldn't even know what it would mean for an object to be static...
The soul is dyed the color of its thoughts. Think only on those things that are in line with your principles and can bear the light of day. The content of your character is your choice. Day by day, what you do is who you become. Your integrity is your destiny - it is the light that guides your way. - Heraclitus
The word "static" is used because it means "resolved at compile time" (as in NOT dynamic like polymorphism is). Please be aware that a variable is NOT "equivalent" to an object. The variable can be static, that does not mean that the object that it references is static.
"JavaRanch, where the deer and the Certified play" - David O'Meara