comment on

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
.......

In reply to Re^4: Tracking down errors in data from input files. by why_bird
in thread Tracking down errors in data from input files. by why_bird

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


Come for the quick hacks, stay for the epiphanies.
	PerlMonks