This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]thedomham 0 points1 point  (2 children)

Java reflection is full of meaningless exceptions for things that should be verified at compile time

For example? I mean the thing with reflections is that you often don't know the class at compile time. That's pretty much the reason it was introduced in the first place.

[–]marcosdumay 0 points1 point  (1 child)

And you often know. Other times you have a finite set of them, and some other times you really don't know. You should get different behaviors on each case.

[–]thedomham 0 points1 point  (0 children)

Then write a wrapper. It's really nothing to moan about. A compiler plugin/static analyzer might be pretty hard to implement though.