I done something similar. It was a class which told you which class and method called you. It worked good excepted the fact that the stupid getStackTrace api doesn't tell you what the parameters of the methods called are so if you have multiple methods with the same name but not the same parameters you couldn't tell which method was called.

Why do you do a loop to find where in the stack you are? aren't you always supposed to be on the top because you are the last caller?

Why don't you make a method which returns a class instead of passing a class parameter and returning a boolean?

And finally i think that your method will fail (badly) if the main method calls your method!

Quote:Why do you do a loop to find where in the stack you are? aren't you always supposed to be on the top because you are the last caller?

Well I did a test run where it printed out what the stack actually looked like, and the first two stack frames were actually inside the Thread class. Which I guess kinda makes sense. And I didn't want to make any assumptions about how many frames Thread.getStackTrace() uses (maybe it won't use two in a later version), which is why I have that loop.

Quote:Why don't you make a method which returns a class instead of passing a class parameter and returning a boolean?

Yeah, no reason why it can't do that. My goal for this function was to make things as clean and simple as possible for the calling function.

Note that StackFrameElement can only give you the class name, so you have to use Class.forName() to get the actual class object.

Quote:
And finally i think that your method will fail (badly) if the main method calls your method!

Yeah, you're right it does fail, but all that happens is you get an ArrayIndexOutOfBoundsException.