Creating a thread. Unexpected output.

[Zarah]

package Threads;

public class Threads1 implements Runnable {
	public void run(){
		System.out.println("\n\t*\t*\t*\t*\t*\n");
	}
	public static void main(String[] args) {
		System.out.println("I am going to show you five stars.\n");
		new Thread(new Threads1()).start();
		System.out.println("\n HAPPY NOW? Yayyyy!\n");
	}
}

What I expected from this piece of code is:

I am going to show you five stars.

	*	*	*	*	*

 HAPPY NOW? Yayyyy!

But the output I got is:

I am going to show you five stars.


 HAPPY NOW? Yayyyy!


	*	*	*	*	*

Can anyone tell me why?

new Thread(new Threads1()).start();

should execute the thread associated with the run() and then the control should return to the next statement in the calling thread (the thread from which the other thread (associated with run()) was called); isn't it?

[sehudson]

Is there any particular reason you need to execute the code in a thread?
I think that in order to ensure that the 'Happy Now' line doesn't execute until after the thread has started, you need to use a CountdownLatch.

The fact that you're executing the * printing code in a thread suggests that it is an asynchronous operation, when in reality, what you want is things to be printed in order, so a thread doesn't seem appropriate there.
I could be wrong, though.

[Norm]

execute the thread associated with the run() and then the control should return to the next statement

The start() method tells the JVM to put the Thread in a queue where it will be executed some time in the future. The start() method immediately returns and execution continues.
To make the execution of the statements be serial, use a standard call to the run() method.

[jim829]

Hah. Actually, with threads the unexpected is the expected.

Regards,
Jim

[Zarah]

The start() method tells the JVM to put the Thread in a queue where it will be executed some time in the future. The start() method immediately returns and execution continues.
To make the execution of the statements be serial, use a standard call to the run() method.

OK great, thank you.

Hah. Actually, with threads the unexpected is the expected.

Oh OK, I'll try to avoid using them.

[Zarah]

Is there any particular reason you need to execute the code in a thread?
I think that in order to ensure that the 'Happy Now' line doesn't execute until after the thread has started, you need to use a CountdownLatch.

The fact that you're executing the * printing code in a thread suggests that it is an asynchronous operation, when in reality, what you want is things to be printed in order, so a thread doesn't seem appropriate there.
I could be wrong, though.

This was just the simplest example; I was reading a tutorial on threads and trying it to see how things work. Thank you for answering.

[SurfMan]

OK great, thank you.

Oh OK, I'll try to avoid using them.

Don't avoid using Threads because you can't line up the output. Threads are very important when you are writing user interfaces, client/server programs or general computation programs and lots more. Use Threads (or their brethren SwingWorkers, Future) when you need to, but don't use them "just because you can". Everybody can spawn a Thread, but proper multithreading is hard to master. Fortunately, the java.util.concurrent package makes it easy for us. Check out the links below for more concurrency goodies.

Lesson: Concurrency (The Java™ Tutorials > Essential Classes)
java.util.concurrent (Java Platform SE 7 )

[Zarah]

Don't avoid using Threads because you can't line up the output. Threads are very important when you are writing user interfaces, client/server programs or general computation programs and lots more. Use Threads (or their brethren SwingWorkers, Future) when you need to, but don't use them "just because you can". Everybody can spawn a Thread, but proper multithreading is hard to master. Fortunately, the java.util.concurrent package makes it easy for us. Check out the links below for more concurrency goodies.

Lesson: Concurrency (The Java™ Tutorials > Essential Classes)
java.util.concurrent (Java Platform SE 7 )

Thank you. I am actually already following the first one of your links. I'll get to multithreading (I think multithreading is an advanced concept) if any of my future projects demands it, because I've learnt from experience that it is no use to learn something if you are not putting it into real, serious practice.