My idea was inspired by compilers. They usually build a parse tree where the nodes store the matched text, logical information (what kind of token is this?) and the position in the source file.

Now if that parse tree is converted to an abstrac syntax tree, they still keep that line information, so if there is an execution error (let's say division by zero) the compiler can tell you which line of code caused that error.

So you can create a class "Traceable" that stores a string and its position in an input file to keep track of where it comes from.

It might be a bit overkill in your project, but for larger projects (parser, compiler) that is common practice.

(BTW it's nice to see that the quality of your questions improve over time ;)

Thanks moritz---I think I got (some of) that, I don't think I can justify doing this for my current work project. (which doesn't neccessarily mean I won't try to do it anyway :) ). I might try it at home when I get some time, but think I have a way to go with OO before attempting something like that..

But if the compiler knows what calls what and from where (since it prints that kind of stuff in error messages) is there a way to hi-jack that information?

Also.. did you mean my questions were getting clearer or less stupid? :P

Cheers why_bird
........
Those are my principles. If you don't like them I have others.
-- Groucho Marx
.......