Java: Thread.currentThread().sleep(x) vs. Thread.sleep(x)

java eclipse multithreading sleep warnings
Omu picture Omu · Jan 16, 2010 · Viewed 76k times · Source

I have this in my code

Thread.currentThread().sleep(x);

Eclipse tells me to use the static

Thread.sleep(x);

instead, why? What's the difference, is there some difference in functionality at all between these 2 methods?

Answer

Sean Owen picture Sean Owen · Jan 16, 2010

There is only one method, not two, and it is static. While you can call a static method via an instance reference, it's not good style. It indicates the programmer thinks he or she is calling an instance method. A confused programmer might be thinking he or she can cause another thread (not the current one) to sleep this way, when that's not what it does.

Both your lines of code do the same thing but the second is better style.

Related questions

Threads: Busy Waiting - Empty While-Loop

During our lessons in the university, we learned about Threads and used the "Busy Waiting" method for an example of a Car waiting at a TrafficLight. For this task we build three classes: TrafficLight (implements Runnable) Car (implements Runnable) Main …

Read More
Can't start Eclipse - Java was started but returned exit code=13

I am trying to get my first taste of Android development using Eclipse. I ran into this problem when trying to run Eclipse, having installed version 4.2 only minutes ago. After first trying to start Eclipse without any parameters to specify …

Read More
Failed to load the JNI shared Library (JDK)

When I try opening Eclipse, a pop-up dialog states: Failed to load the JNI shared library "C:/JDK/bin/client/jvm.dll"`. Following this, Eclipse force closes. Here's a few points I'd like to make: I checked to see if …

Read More