Mailing-List: contact dev-help@groovy.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@groovy.incubator.apache.org
Subject: @Synchronized on fields
To: dev@groovy.incubator.apache.org
References: 
 <CAJ2HCd-E+eDa05=T=xD7V=jdPMeRjFPzKp7JGq8CL99EPC9k-Q@mail.gmail.com>
From: Mauro Molinari <mauromol@tiscali.it>
Message-ID: <55D44094.6030108@tiscali.it>
Date: Wed, 19 Aug 2015 10:38:44 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101
 Thunderbird/38.2.0
MIME-Version: 1.0
In-Reply-To: 
 <CAJ2HCd-E+eDa05=T=xD7V=jdPMeRjFPzKp7JGq8CL99EPC9k-Q@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit

Hi,
I wrote this as a post-mortem comment to bug GROOVY-4697, but didn't 
receive any answer.
Probably, there's something obvious I'm missing, anyway I was wondering 
why Groovy doesn't support @Synchronized on fields, something like this:

class MyClass {
   @Synchronized
   String  foo
}

that is, to say that the generated getter and setter methods should be 
synchronized (in the same way they are if I write them explicitly and 
annotate themselves with @Synchronized). Right now, to get a simple 
synchronized access to a field, I have to write something almost as much 
verbose as Java.

Thanks in advance for any hint.
Mauro