94 votesUnder review · 13 comments · Feature Requests and Feedback » Office Developer Tools · Flag idea as inappropriate… · Admin →
An error occurred while saving the commentMathieu Guindon commented
No, no, no, no. Line numbers are NOT useful for error trapping at all, and the undocumented Erl function is broken and only has integer resolution while line numbers can be a long.
Making VBA code default to looking like 1980 can't be the way forward, and makes line labels superfluous which is dumb. Use On Error statements with line labels, and write smaller functions. If you can't tell what threw an error, you've written a procedure that's doing too many things. Refactor your code, don't force line numbers down my throat!
A MUCH better idea would be to give VBA programmatic access to the call stack, so we could have current-century error reporting. See what vbWatchdog does.