First the question: Would it be possible to add line numbers to runtime errors for the JS target?
My understanding is (please correct me if wrong), runtime errors have stack tracing because they are pushed into a stack var at the start and end of a function block. We dont have line numbers is because they would have to be put in before every single equivilant JS line. And trace statements have line numbers because the compiler can statically insert the line number at the call point.
Am I right there?
The reason for my question is at the moment its quite painful to debug a problem in your JS code, particularly when you are using a library like Jeash. The chrome or firebug debug tools are good but its pretty tricky to understand whats going on when there are thousands of lines of code in one file and the code generated is pretty cryptic compared to your haXe source.
The perfect solution would be is that JS is just considered a blackbox like the Flash byte code is. When you are debugging your program you arent stepping over byte code but your source that represents it.
I dont know enough about writing languages to know if its possible but would it be possible to output more information into the generated code (when using -debug) or even generate another file "MyApplication_debug.js" which could contain some more debug info tooling could use?