3 ms·
Because of some track record of Java, or because you just have a feeling about it? I don't program in Java at all, and frankly, I was flabbergasted to see a ch
by kbenson 8y ago
Because of some track record of Java, or because you just have a feeling about it?
I don't program in Java at all, and frankly, I was flabbergasted to see a change as obvious and useful as this wasn't already in there a decade ago. Or at least 3-4 years ago where a lot more languages started advertising better compilation error messages.
- cesarb 8y ago> Because of some track record of Java, or because you just have a feeling about it? It's proposing to reverse-engineer the corresponding source code from the bytecode when encountering the exception. That does sound like a potentially unreliable hack.
- repolfx 8y agoNot necessarily. The sort of dataflow analysis they're talking about is an inherent part of bytecode verification already. A more advanced version of it is done every time a class is loaded. JVM bytecode is designed to make this sort of thing possible.