Anonymous-Inner classes showing unwanted modifier

2019-01-15 05:22发布

To my understanding, the following code should have printed true.

However, when I ran this code it is printing false.

From Java docs of Anonymous Classes 15.9.5. :

An anonymous class is always implicitly final

public class Test {
    public static void main(String args[]) {
        Object o = new Object() {
        };
        System.out.println("Annonymous class is final: " + Modifier.isFinal(o.getClass().getModifiers()));
    }
}

Can some one please help me understand this behavior.

4条回答
Evening l夕情丶
2楼-- · 2019-01-15 05:36

An anonymous class is never final (§8.1.1.2).

JLS 11 - 15.9.5. Anonymous Class Declarations

I didn't know the reasoning behind this, but, according to @Hulk's answer and this bug report, it seems the specification of previous versions slightly misled us saying that anonymous classes are final.

查看更多
手持菜刀,她持情操
3楼-- · 2019-01-15 05:39

Anonymous classes are considered implicitly final since you can't create sub-classes of them. That doesn't mean that the Modifier.FINAL modifier should be set for anonymous classes.

查看更多
Luminary・发光体
4楼-- · 2019-01-15 05:42

Note that the wording in the JLS of that particular section has changed significantly since then. It now (JLS 11) reads:

15.9.5. Anonymous Class Declarations:

An anonymous class is never final (§8.1.1.2).

The fact that an anonymous class is not final is relevant in casting, in particular the narrowing reference conversion allowed for the cast operator (§5.5). It is also of interest in subclassing, in that it is impossible to declare a subclass of an anonymous class, despite an anonymous class being non-final, because an anonymous class cannot be named by an extends clause (§8.1.4).

This change in wording was introduced in JLS 9. The semantics of anonymous classes and the behavior of the methods in the question remained unchanged, the intention was to avoid exactly the kind of confusion this question is about.

The ticket that caused the change says:

Longstanding behavior of javac, since 1.3, has been, for the most part, not to treat the classes as 'final'. To address this inconsistency, the specification should be changed to accurately reflect the reference implementation.

Specifically, anonymous classes are almost never generated with the ACC_FINAL flag set. We can't change this longstanding behavior without impacting some serialization clients (this would be permissible, but is unnecessarily disruptive). And we can't faithfully implement Class.getModifers (which promises to provide the "Java language modifiers") without the class files encoding the language's modifiers.

查看更多
ら.Afraid
5楼-- · 2019-01-15 05:50

See Javadoc of Class.getModifiers(): https://docs.oracle.com/javase/10/docs/api/java/lang/Class.html#getModifiers()

It says "...The values of its other modifiers are not determined by this specification".

查看更多
登录 后发表回答