Submitted by a Jlint user:
----
It appears that JLint can't tell the difference
between: assert(arg != null) -and- if(arg!=null)throw
AnException. I'd rather not use a bunch of if's. They
are bulkier than asserts, and would reduce performance
in the production build.
I would be so very happy if JLint could treat asserts
the same as if-throws.
----
This suggests that assertions are not recognized in the
sense that execution will continue to assume the
pointer is unchecked.
The analysis logics should set that pointer to non-NULL
when such an assertion is encountered. Unfortunately it
may be non-trivial to extract such assertions from byte
code.
Logged In: YES
user_id=339047
I have just encountered this - and note that this bug was reported over a
year ago now, and is not assigned to anyone. Should I assume from this
that it is unlikely to be looked at in the near future?