It's not always that simple. A single line of code could have a dozen variables that relate to it, and it could even be a problem of one variable added to or divided by another. Telling the line that causes the error is about as fine as any compiler is capable of.
However, the better compilers out there will show you the line of code causing the problem, which I think could be tremendously useful. Even a non programmer who sees something like: sashWidth/WindowDivisions might figure out that having zero divisions would be a bad thing.
Tom Waltz
