You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@groovy.apache.org by Guillaume Laforge <gl...@gmail.com> on 2015/08/16 00:15:44 UTC
[ANN] Groovy Weekly #75
Hi all,
My Groovy Weekly column is not very weekly at all I reckon, but here's a
new edition with tons of content to read and watch! In particular, lots of
videos from the GR8Conf US 2015 conference!
http://glaforge.appspot.com/article/groovy-weekly-75
Enjoy,
--
Guillaume Laforge
Apache Groovy committer & PMC member
Product Ninja & Advocate at Restlet <http://restlet.com>
Blog: http://glaforge.appspot.com/
Social: @glaforge <http://twitter.com/glaforge> / Google+
<https://plus.google.com/u/0/114130972232398734985/posts>
Re: @Synchronized on fields
Posted by Mauro Molinari <ma...@tiscali.it>.
Il 19/08/2015 10:38, Mauro Molinari ha scritto:
> I wrote this as a post-mortem comment to bug GROOVY-4697, but didn't
> receive any answer.
Oh, well, sorry, looking at it better the mentioned bug is still open,
anyway it talks about applying @Synchronized specifically on closures
rather than on simple fields.
Mauro
@Synchronized on fields
Posted by Mauro Molinari <ma...@tiscali.it>.
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