Banjo

52 thoughts
last posted Nov. 9, 2015, 7:13 p.m.

33 earlier thoughts

0

Lazy errors for "bad" programs

It has become clear from using Java that even if there are errors detected in the code, one should allow the program to run nonetheless. The piece of code that has the error may not be part of what the programmer is trying to test. This allows the programmer to build their program incrementally and leave areas unimplemented that are truly unimplemented rather than having to stub things out.

Of course, if the code with errors is encountered, the program should exit with as helpful an error as possible.

And, the IDE or toolchain should be reporting these errors while still allowing the program to be run as much as possible.

18 later thoughts