|
|
Featured White Papers
- Why choose an Open Source BPM?
- 10 FAQs on Business Process Management
- Best Practices for Getting Started with BPM
- Free Your Devs From The Pain Of Java Redeploys
- Increase Velocity 40% by Using JRebel
- What Developers Want: The End of Application Redeploys
- Developer Productivity Report: Java Tools, Tech, Devs, and Data
- Coding with JRebel: Java Forever Changed
- Utilizing Fast Testing to Transform Java Development
- Do You Really Get Classloaders?
- Pragmatic Continuous Delivery with Jenkins, Nexus, and LiveRebel
- Your Next Java Web App: Less XML, No Long Restarts, Fewer Hassles
- Coding with JRebel, Java Forever Changed
- 2012 Developer Productivity Report: Java Tools, Tech, Devs, and Data
Instantiating object in main method
Submitted by VonQ on Mon, 03/23/2009 - 17:10.
This is a really, really dumb question but I'm trying to wrap my mind around why all my beginner java books use the main method to instantiate objects of a different class than the one it is being instantiated in, such as the one below. I've tested it and know it works but why don't I ever see it in the books? Is there a drawback to creating a new object of the same object that you are in?
Thanks, Von and sorry if this is a crazy question!!!!!!
public class TestClass
int id = 6;
{
public static void main(String[] args)
{
TestClass firstTest = new TestClass();
firstTest.id = 5;
System.out.println(firstTest.id);
}
}