Work will teach you how to do it!<br />----------------------
ConstructorModifier: one of
public protected private
Unlike methods, a constructor cannot be abstract, static, final, native, strictfp, or synchronized. A constructor is not inherited, so there is no need to declare it final and an abstract constructor could never be implemented. A constructor is always invoked with respect to an object, so it makes no sense for a constructor to be static. There is no practical need for a constructor to be synchronized, because it would lock the object under construction, which is normally not made available to other threads until all constructors for the object have completed their work. The lack of native constructors is an arbitrary language design choice that makes it easy for an implementation of the Java virtual machine to verify that superclass constructors are always properly invoked during object creation.
Originally posted by Beny Na:
By the way, i still have a problem with collection chapter for the exam next week, do you have any idea how to grasp the concept from this chapter.
and the thread chapter is quite hard..and i can't learn it within one/two week to get a good concept in order to solve complicated question.
if you could explain the concept or any good link that explain about thread it would be helful for my exam.
thanks
Don't get me started about those stupid light bulbs. |