Class BreakPoint

Materializes a breakpoint. A breakpoint can be defined at a line number or an offset character in its document. For JavaScript, we only support lineno for the underlying Rhino engine does support only the line numbers. Note: this is unfortunate for this prevents setting a breakpoint on different statements on the same line... A breakpoint is remembered at either the document level (DocumentCell) or the function/script level (FnOrScript). It is remembered at the document level when a FnOrScript is not yet known for the breakpoint line number. When a matching FnOrScrip will become known (compiled in Rhino), the breakpoint will be remembered at the FnOrScript level. Additionally, a breakpoint can be correlated or not to a compilation unit. When not correlated (m_unit==null), it means a compilation unit for the breakpoint line has not been seen yet. It may be because the breakpoint is on an invalid line but it may be also that the breakpoint is in a script or function that has not been compiled yet. Indeed, there is a delay between knowing about a FnOrScript and knowing about all its compilation unit. When a FnOrScript is about to be compiled in Rhino, we create the FnOrScript, with no known compilation unit. As a side effect of compiling, the Rhino engine calls us back with compilation units such as independent functions or scripts. This is when those units, represented by our class CompilationUnit are added to the corresponding FnOrScript.

UNKNOWN: Olivier Gruber