I am reading about reflection at the moment. In the book the following example is given. It shows a method which tries to locate
a method defined by its name and type of its arguments for a specified class. It first looks to see if the method is a declared method in the class
and otherwise traveses the inheritance-tree above it, to see if it has inherited the method:
Is it generally ok coding to use try-catch for the purpose of handling program "flow" ?
And is NoSuchMethodException the most appropriate class if null is passed?
posted 9 years ago
thanks for the inputs. I get new homework by asking a question, when is it due ?!
I am reading up on the exception-handling mechanism to come up with qualified arguments against. To my beginner-eyes
it seems at first that it would be hard writing the code so compactly without using try-catch.
It might be time for learning to use a profilimg tool to compare the time usage for the method using try-catch with a rewritten version of it.
Only problem is, I love the commandline and think IDE's are for when you have learned enough to be able to do by hand everything your IDE can.
But there doesnt seem to be many options for commandline profiling
I will suppress my every urge. But not this shameless plug:
how do I do my own kindle-like thing - without amazon