java.lang.NullPointerException would like a word, but at least that usually comes with a 50,000-line stack trace. Unless you're working with some piece of shit enterprise software vendor whose "platform" suppresses those after about 20 lines, and the thing in your code that caused it is on the 35th line in the trace.
Newer versions of Java also have a feature ported from another JVM that shows the variable that was null and what method call caused the NPE to happen. NPEs are the opposite of generic, although you have to find why the the thing was null in the first place.
Okay but what other language would throw you an error like [object Object] and refuses to elaborate.
java.lang.NullPointerExceptionwould like a word, but at least that usually comes with a 50,000-line stack trace. Unless you're working with some piece of shit enterprise software vendor whose "platform" suppresses those after about 20 lines, and the thing in your code that caused it is on the 35th line in the trace.Newer versions of Java also have a feature ported from another JVM that shows the variable that was null and what method call caused the NPE to happen. NPEs are the opposite of generic, although you have to find why the the thing was null in the first place.