[
https://issues.apache.org/jira/browse/BCEL-183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14251666#comment-14251666
]
Jérôme Leroux commented on BCEL-183:
------------------------------------
Tested on the following JVM: java version "1.7.0_65" OpenJDK Runtime
Environment (IcedTea 2.5.3).
There are no restrictions on the methods named {{<clinit>}}, they can be
abstract, native, …
A method named {{<init>}} cannot be abstract, native or static.
http://docs.oracle.com/javase/specs/jvms/se7/html/jvms-4.html#jvms-4.6
{quote}
A specific instance initialization method (§2.9) may have at most one of its
ACC_PRIVATE, ACC_PROTECTED, and ACC_PUBLIC flags set, and may also have its
ACC_STRICT, ACC_VARARGS and ACC_SYNTHETIC flags set, but must not have any of
the other flags in Table 4.5 set.
{quote}
> Implement Java 7 field/method name validation rules
> ---------------------------------------------------
>
> Key: BCEL-183
> URL: https://issues.apache.org/jira/browse/BCEL-183
> Project: Commons BCEL
> Issue Type: Improvement
> Components: Verifier
> Affects Versions: 5.2
> Reporter: Jérôme Leroux
> Fix For: 6.0
>
> Attachments: BCEL-183-2.patch, BCEL-183-2.zip, BCEL-183-src.zip,
> BCEL-183.patch, BCEL-183.zip
>
> Original Estimate: 2h
> Remaining Estimate: 2h
>
> The JustIce bytecode verifier checks the validity of the field name and the
> variable name considering the java langage specification.
> This check is not specified by the bytecode verifier specification.
> This may lead to bytecode verification errors in pass2 on valid classfiles.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
