| Related articles |
|---|
| Decompilability s720@ii.uib.no (Thomas M. Farrelly) (1997-03-14) |
| Re: Decompilability monnier@cs.yale.edu (Stefan Monnier) (1997-03-16) |
| Re: Decompilability afstanto@omni.cc.purdue.edu (Aaron F Stanton) (1997-03-16) |
| From: | Stefan Monnier <monnier@cs.yale.edu> |
| Newsgroups: | comp.compilers |
| Date: | 16 Mar 1997 23:17:56 -0500 |
| Organization: | Compilers Central |
| References: | 97-03-063 |
| Keywords: | Java |
"Thomas M. Farrelly" <s720@ii.uib.no> writes:
> Would the ability to be decompilable (make close to original source code
> out of a binary file) be a drawback for a programming-language?
> [Doesn't seem to have hurt Java too badly. -John]
I doubt this is a Java characteritic. It looks more like a JVM for
Java characteristic.
It also depends on the compiler's sophistication. I'm sure that a Java
program compiled with an aggressive compiler (using partial evaluation
for instance) will not be easily decompilable.
So I would say that it's probably not a drawback in and of itself, but
it shows that your compiler is pretty dumb (which is not to say it's
bad: very few people expect a compiler from assembly to binary to be
clever).
Stefan
--
Return to the
comp.compilers page.
Search the
comp.compilers archives again.