On 3/14/14 at 3:02 PM, fitzgen at gmail.com (Nick Fitzgerald) wrote:

>I feel very strongly that users debugging their sources that were
>compiled to js should be able to set watch expressions and conditional
>breakpoints in their source language.

My experience with debuggers says the while the vast majority of 
the time you want to be able to debug it in the language you 
wrote, sometimes you want to debug it in the language it broke 
in. Being able to look at the lower level language can clear up 
misconceptions about what a higher level construct means. It can 
also reveal compiler bugs.

It should also be recognized that all compiled programs break in 
machine language. :-)

Cheers - Bill

-----------------------------------------------------------------------
Bill Frantz        | Concurrency is hard. 12 out  | Periwinkle
(408)356-8506      | 10 programmers get it wrong. | 16345 
Englewood Ave
www.pwpconsult.com |                - Jeff Frantz | Los Gatos, 
CA 95032

On 3/14/14 at 3:02 PM, fitzgen at gmail.com (Nick Fitzgerald) wrote:

>I feel very strongly that users debugging their sources that were
>compiled to js should be able to set watch expressions and conditional
>breakpoints in their source language.

My experience with debuggers says the while the vast majority of 
the time you want to be able to debug it in the language you 
wrote, sometimes you want to debug it in the language it broke 
in. Being able to look at the lower level language can clear up 
misconceptions about what a higher level construct means. It can 
also reveal compiler bugs.

It should also be recognized that all compiled programs break in 
machine language. :-)