Re: Why "lock" functionality is introduced for all the objects?

From	Roedy Green <see_website@mindprod.com.invalid>
Newsgroups	comp.lang.java.machine
Subject	Re: Why "lock" functionality is introduced for all the objects?
Date	2011-06-28 10:02 -0700
Organization	Canadian Mind Products
Message-ID	<pv1k079tki8fcbie5umqtc54e3tackak21@4ax.com> (permalink)
References	<736a142e-85ae-4790-a1f1-afb09bfed755@em7g2000vbb.googlegroups.com>

Show all headers | View raw

On Tue, 28 Jun 2011 02:30:17 -0700 (PDT), Alex J <vstrength@gmail.com>
wrote, quoted or indirectly quoted someone who said :

>I'm curious why Java designers once decided to allow every object to
>be lockable (i.e. allow using lock on those).

The alternative would be to insist that objects to be locked implement
a Lockable interface.  Then you would need two versions of every
class, because potentially everything is lockable.
-- 
Roedy Green Canadian Mind Products
http://mindprod.com
One of the curses of the computer age is manufacturers now design 
home appliances to die on the very day the warranty expires.
It is deliberate waste in the service of mindless profit.

Back to comp.lang.java.machine | Previous | Next — Previous in thread | Next in thread | Find similar

Thread

Why "lock" functionality is introduced for all the objects? Alex J <vstrength@gmail.com> - 2011-06-28 02:30 -0700
  Re: Why "lock" functionality is introduced for all the objects? Roedy Green <see_website@mindprod.com.invalid> - 2011-06-28 10:02 -0700
  Re: Why "lock" functionality is introduced for all the objects? Barb Knox <see@sig.below> - 2011-06-30 18:11 +1200

csiph-web