Smoother step over/in in the debugger
When using the step over/step in actions on Scala code, the result is not the expected one.
The the points to improve are:
The the points to improve are:
- Stepping over/through setter/getter and forwarders. When trying to step into a method or function call, the debugger often stops on the class definition. It should always got directly to the into the method called. This may require changes in the debug information generated by the compiler.
- Stepping over/through closures. When stepping over a the 'for' line of a for comprehension,the debugger execute fully the foreach call, and stop and the first line of code after the for comprehension. One would expect to go the first line of code of the closure. It should be possible to get the 'right' behavior by setting breakpoints at the beginning at the closures.
- Stepping over pattern matcher cases. When stepping over code in a pattern matcher, the debugger often stops on the line containing the 'match' key word. It is not the expected behavior, the debugger should step over the case statements until it arrives to the valid one.
Leave a comment
Development is done in the feature/scala-debugger-1000864 branch.
More in depth documentation is being created at http://scala-ide.org/docs/helium/features/scaladebugger.html
More in depth documentation is being created at http://scala-ide.org/docs/helium/features/scaladebugger.html
on 2012-12-03 10:48 *
By Iulian Dragos
Version changed from 2.0.0-final-29 to 2.1.0-nightly-29
Assigned to set to skyluc
Status changed from Accepted to Fixed