• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Tim Cooke
  • Ron McLeod
  • paul wheaton
  • Jeanne Boyarsky
Sheriffs:
  • Paul Clapham
  • Devaka Cooray
Saloon Keepers:
  • Tim Holloway
  • Roland Mueller
  • Himai Minh
Bartenders:

Threads Dan Exam Not-runnable vs. ready

 
Ranch Hand
Posts: 30
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
On the Dan exam he uses the terms not-runnable and ready, I was originally thinking of not-runnable as dead, but in the context of some of his answers it seems to have the same definition as ready. Can anyone define these terms?
 
Ranch Hand
Posts: 1865
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Gerald,
The Java Language Specification does not define state names, so there is no general consensus on what the names should be. For example, Doug Lea uses the names Created, Runnable, Running, Blocked, and Terminated. Cay Horstmann uses the names New, Runnable, Blocked and Dead. My exam uses the state names that appear in Sun's Java tutorial.
The JLS can not define state names, because Java makes use of threading functionality that existed before Java. In other words, Java really just provides an API to products that were already up and running.
The "Not-Runnable" state can also be called the "Blocked" state. The "Ready" state could also be called the "Runnable" state.
 
Don't get me started about those stupid light bulbs.
reply
    Bookmark Topic Watch Topic
  • New Topic