Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.java.programmer > #6391

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

Show all headers | View raw

On 7/21/2011 5:33 PM, Arne Vajhøj wrote:
...
> For all the simple cases:
>
> public class Foobar {
> ...
> private Object lock = new Object();
> ...
> public void test() {
> ...
> synchronized(lock) {
> ...
> }
> ...
> }
> ...
> }
>
> having to use LockingObject instead of Object would have worked fine.
>
> But in more complex scenarios where you have multiple methods modifying
> multiple objects, then the only safe way is to lock on the actual
> objects (obviously in a fixed order to avoid deadlocks).

I'm not sure how that would have worked for synchronized methods, as
distinct from synchronized blocks.

Patricia

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

Thread

Re: Why "lock" functionality is introduced for all the objects? Arne Vajhøj <arne@vajhoej.dk> - 2011-07-21 20:33 -0400
  Re: Why "lock" functionality is introduced for all the objects? Patricia Shanahan <pats@acm.org> - 2011-07-21 21:08 -0700
    Re: Why "lock" functionality is introduced for all the objects? Arne Vajhøj <arne@vajhoej.dk> - 2011-07-22 10:20 -0400

csiph-web