Re: AW: java bytecode produced by "Ant javac" different from "command line javac" bytecode

2009-11-23 Thread td.com
catch (IOException localIOException) { } finally { System.out.println("Done..."); } } } Is there something particular to javac that makes the throw in the catch block "disappear" once the bytecode is decompiled? td.com wrote: > > Hello all! >

Re: AW: java bytecode produced by "Ant javac" different from "command line javac" bytecode

2009-11-21 Thread td.com
result when you decompile the same file twice? >> >> I am not an expert but i think the decompiler can produce different code >> that achieves the same thing. Try to decompile the same file twice and >> see >> if the decompiler produces the same code. >> &

Re: AW: java bytecode produced by "Ant javac" different from "command line javac" bytecode

2009-11-20 Thread td.com
Hello all and thanks for your replies By different I mean that once decompiled (with jd) or dissassembled with javap, the resulting files are different. In order to use the same javac options on the command line, I ran Ant with the -debug option. That being done I was able to copy the argument

java bytecode produced by "Ant javac" different from "command line javac" bytecode

2009-11-20 Thread td.com
Hello All, when compiling using the Ant javac task on my machine (JDK1.5) I end up getting bytecode that's different then when I compile the same code on the same machine but through the command line javac. Does anyone know what could be causing this? Thanks in advance! -- View this message in