jimblandy
commented
12 years ago Column support is certainly on our to-do list, but I don't think we have all the bugs filed that we should. I'll check tomorrow morning. On May 20, 2012 4:33 AM, "David Bruant" < reply@reply.github.com> wrote:
Currently, the relationship between source code and bytecode instruction offsets is at the line granularity. For instance the Debugger.Script.prototype.getLineOffsets method returns all bytecode instruction offsets for a given line. When setting a breakpoint on all of the offsets of this line (if there are several of them), it's impossible to know where in the source code this offset refers to. They just all refer to the same line. Since some lines do a lot of things (like a for(i=0; i<=4 ; i++)), it could be convenient to know which instruction is being run within the same line (without having to tweak the source code just for that purpose).
Having the column information could be handy here.
An alternative could be to know where in the parse tree the breakpoint is.
Reply to this email directly or view it on GitHub: https://github.com/jimblandy/DebuggerDocs/issues/2
DavidBruant
Currently, the relationship between source code and bytecode instruction offsets is at the line granularity. For instance the Debugger.Script.prototype.getLineOffsets method returns all bytecode instruction offsets for a given line. When setting a breakpoint on all of the offsets of this line (if there are several of them), it's impossible to know where in the source code this offset refers to. They just all refer to the same line. Since some lines do a lot of things (like a for(i=0; i<=4 ; i++)), it could be convenient to know which instruction is being run within the same line (without having to tweak the source code just for that purpose).
Having the column information could be handy here.
An alternative could be to know where in the parse tree the breakpoint is.