Expression debugging errors

[Jaydude-wb]

In many cases, the debugger comes up with a line number that does not exist. (e.g. an error on line 71, while the expression consists of 69 lines). It's hard to say when exactly this problem shows up, but it occurs a lot, so I guess more users have experienced this behaviour.

[Dan Ebberts]

Yes! Because of this, and the fact the legacy expression engine generally provides better error info, I try to fashion my expressions so they will run in either engine and often switch to the legacy engine when I encounter an error. It's not a good situation.