Quite right. I remember when I first started writing largeish projects, and was using some OOness that got pretty convoluted at times. Often, when Perl died it spat out a filename and line number that was completely useless. It would be the file that was calling a function in another file that called a function in another file where there was a bug. I quickly learned to output readable and informative debug messages.

Actually, AFAIR (and my memory is patchy at best) if there's a bug inside an eval statement, don't the dying words say that the problem was on line 0 or something... or just not complain at all...

Anyway, now I have fun with error messages. Looking at debug output of my code you may see stuff like the following:

The Command Dispatcher hates you beause: java.lang.NullPointerExceptio
+n
The GUI farted the following: ArrayOutOfBoundsException: 3 >= 1
[download]

or whatever. Like I said, way too much Java lately :o)

LAI
:eof