Re: Why can't I start a thread twice?
Chuan C. wrote:
Lew
Lew wrote:
Chuan C. wrote:
This is what I do:
class X extends Thread {
It is usually better to implement 'Runnable' and pass it to a 'Thread'
than to extend 'Thread'.
It is about introducing Threads. This particular excercise is to be
solved this way.
Not much better, but better.
Why?
Boolean go;
Why did you choose 'Boolean' instead of 'boolean'?
Sorry, that was a typo.
If the variable were 'boolean' it would be initialized to 'false' for
you automatically.
This a habbit from other languages, where it is a not a good idea to
depend on default values. Is there concense in Java that numerical
types will be initialized to zero?
It's part of the very definition of the Java language that instance and static
variables will be initialized to their default values (false, 0, '\u0000', 0L,
0.0F, 0.0 or null depending on type), but that local variables will not be.
There is a subtlety involving 'final' fields, which require an explicit
assignment.
From the Java Language Specification (JLS):
<http://java.sun.com/docs/books/jls/third_edition/html/typesValues.html#4.12.5>
--
Lew