On 05/20/2013 01:03 PM, Peter van der Zee wrote:
> This may not be the right place, but what should browsers do when an error
> is raised in an area of the translated code? As a dev I would not like to
> be sent to a wild goose chase, only to find out later that the error wasn't
> due to my code but due to the way it was translated.
I don' think there's any way the browser can distinguish these two
cases, even if source maps could be changed to help.
If your translator correctly preserves the meaning of the program you
translated, and your program doesn't have a bug, it shouldn't crash.
If your program is correct, but the translated code crashes, that is, by
definition, a bug in the translator.
Am I missing something?