Well, whenever you override something, you're expected to do it in a way that does not violate the stated API of the original method. The API says start() is supposed to start a thread; therefore you shouldn't override it in a way that does not start a new thread. But Sun can't prevent every possible coding mistake you might make. The decided to give us the power to revise behavior of methods in our classes; it's our responsibility to use this power sensibly.
Here's one possible example of an override of start() that does something potentially useful, but still fulfills the requirements of the API:
The key is that at some point, amidst doing whatever other functionality you want to add, you call the original method you're overriding. Depending on what class and method you're dealing with, in some cases you may not need to call the original method while overriding; in other cases, it's your only sensible option.
"I'm not back." - Bill Harding, Twister
Joined: Dec 09, 2000
Thanks for the swift reply.
What you say sure makes sense...
I was limiting my thinking to doing initialising and so forth in the thread's constructor.
However, I am now the wiser (note - not the wisest).