Request for feature: more support for method calls in debugger [message #1601991] |
Thu, 05 February 2015 08:50 |
Ulrich Scholz Messages: 15 Registered: September 2013 |
Junior Member |
|
|
I'd like to see more information for method calls: return values and cascading method calls.
Case 1:
if(someClass.someMethod() == 2) {
// do something
}
Imagine that the return value of someClass.someMethod() is not 2. Then, one could use inspect to find out the actual return value. But that might have side effects and be clumsy. As the result should be already available to the debugger, one could imagine to have some temporary line among the variables, like "current return value" or so.
Case 2:
someClass.someMethod().someOtherMethod().someThirdMethod();
Same point as for case 1 applies. In addition, Eclipse could visually indicate which method has already been executed. So first, someClass.someMethod() would be highlighted, then someClass.someMethod().someOtherMethod() and so on.
|
|
|
Powered by
FUDForum. Page generated in 0.03037 seconds