On 20 April 2010 18:52, Jochen Theodorou <[email protected]> wrote: > Charles Oliver Nutter wrote: > [...] > > Can you explain in terms of the Groovy codebase what you mean by "the >> Groovy speed problem"? I may be able to explain what we have done in >> JRuby for similar situations. >> > > I spend uite some time to get an overview and counted about 20 points were > concurrent stuff is involved on the first call of a method. If the method is > called again, this is reduced to some volatile access to see if a category > is active and some other things.
[snip] Categories are thread specific so you don't need volatile access to see if a Category has been applied. You do need volatile to see if a global change has been made to the behaviour of a class and I can't see any way round that. John Wilson -- You received this message because you are subscribed to the Google Groups "JVM Languages" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/jvm-languages?hl=en.
