4

I noticed this breaking (for me using it with OGNL) change in 2.9.0-1:

I find that, in 2.9, methods declared in a trait become volatile when mixed in a class:

Example in 2.9.0-1

import java.lang.reflect.Modifier

trait SuperTrait {
    def getKnoll = "Kanutten"
}

class KlassWithKnoll extends SuperTrait {
    def getKnall = "Mars"

}

val qsc = classOf[KlassWithKnoll]
val knollGetter = qsc.getDeclaredMethod("getKnoll")
println("isVolatile: " + Modifier.isVolatile(knollGetter.getModifiers()))

This prints out

isVolatile: true

But in 2.8.1:

it prints out

isVolatile: false

This is actually a breaking change for me as OGNL refuses to execute volatile (why I don't know) in its expressions.

So - my question is; Why was this change made?

Jonas
  • 121,568
  • 97
  • 310
  • 388
andreak
  • 902
  • 7
  • 10

1 Answers1

3

There's no such thing as a volatile method. What you are seeing is that the 0x0040 flag is set, which is ACC_VOLATILE for fields, but ACC_BRIDGE for methods. Since the Modifier.isVolatile method takes an Int, it can't really tell you that what you're asking is not meaningful.

psp
  • 12,138
  • 1
  • 41
  • 51
  • Why are methods with body in traits becoming bridge-methods in scala-2.9 as they were not in 2.8? Or is this another SO question? – andreak Jul 22 '11 at 09:47