[
https://issues.apache.org/jira/browse/BCEL-257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sebb resolved BCEL-257.
-----------------------
Resolution: Fixed
Fix Version/s: 6.0
Note: the unit test submitted as part of BCEL-258 showed that the fixes here
were needed
URL: http://svn.apache.org/r1697982
Log:
BCEL-257 INVOKESPECIAL, INVOKESTATIC, INVOKEVIRTUAL need to define dump()
methods
Modified:
commons/proper/bcel/trunk/src/changes/changes.xml
commons/proper/bcel/trunk/src/main/java/org/apache/commons/bcel6/generic/INVOKESPECIAL.java
commons/proper/bcel/trunk/src/main/java/org/apache/commons/bcel6/generic/INVOKESTATIC.java
commons/proper/bcel/trunk/src/main/java/org/apache/commons/bcel6/generic/INVOKEVIRTUAL.java
> INVOKESPECIAL, INVOKESTATIC, INVOKEVIRTUAL need to define dump() methods
> ------------------------------------------------------------------------
>
> Key: BCEL-257
> URL: https://issues.apache.org/jira/browse/BCEL-257
> Project: Commons BCEL
> Issue Type: Bug
> Reporter: Sebb
> Assignee: Sebb
> Fix For: 6.0
>
>
> It looks like the INVOKESPECIAL, INVOKESTATIC, INVOKEVIRTUAL classes need to
> define dump() methods, otherwise they will just dump the opcode.
> Note that INVOKEDYNAMIC and INVOKEINTERFACE both define dump() methods that
> correspond with their descriptions in the JVMS 6.5
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
