4 ms·
If there is a problem with java bytecode, then that is hard to verify. You need multiple passes over the bytecode, until you've reached a steady state. There is
by readittwice 9y ago
If there is a problem with java bytecode, then that is hard to verify. You need multiple passes over the bytecode, until you've reached a steady state.
There is also the "issue" that Java bytecode allows arbitrary control flows with goto, while Java doesn't.
IMHO WebAssembly solves that better but I also need to admit that they could already learn from Java.
- kodablah 9y ago> IMHO WebAssembly solves that better but I also need to admit that they could already learn from Java. While that may be true of the language Java, WebAssembly's jump instructions are not without their annoyances too. For example, the JVM bytecode requires your stack to be precise when jumping, WebAssembly just cares about the most recent piece. If you expect your jump targets to have the same stack layout, WebAssembly makes the impl handle it. I had to account for this and other differences in my compiler [0]. 0 - https://github.com/cretz/asmble#control-flow-operations https://github.com/cretz/asmble#control-flow-operations