开发者

Methods in trait become volatile methods when mixed in concrete classes in 2.9.0-1 but not 2.8.1

开发者 https://www.devze.com 2023-03-22 02:50 出处:网络
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:

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:

开发者_如何学Pythonit 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?


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.

0

精彩评论

暂无评论...
验证码 换一张
取 消