are any debugger enhancements planned? especially "evaluate expression" (from code selection) is almost unusable right now because of the different syntax
Better breakpoint control is definitely needed. Line-level breakpoints are inadequate for Scala, as witnessed by the fact that many lines will, if bearing a breakpoint, stop far too many times. Apparently multiple bytecode blocks can be associated with a given line number (and file name).
I'm sure Scala will prove a real challenge for debugger support, but it's a pretty important capability to have.
Better breakpoint control is definitely needed. Line-level breakpoints are inadequate for Scala, as witnessed by the fact that many lines will, if bearing a breakpoint, stop far too many times. Apparently multiple bytecode blocks can be associated with a given line number (and file name).
I'm sure Scala will prove a real challenge for debugger support, but it's a pretty important capability to have.
Randall Schulz
And also the opposite is true: Often a line-level breakpoint will never break. In the snippet below, breakpoints at "//*** break" will not break.
class MySpecification extends Specification {
"smoke" should {
"smoke 1" in {
10 must be_== (11) //*** break
}
"smoke 2" in {
10 must be_== (10) //*** break
}
}
}
(new topic really)
Which has caused me to use to @Test instead. BUT, I just noticed today that this test will pass:
class MyJSpecification extends BaseSpecification with Expectations {
@Test def smoke {
10 must be_== (11)
}
}