This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Step into doesn't handle the TERNARY OPERATOR. === result = someCondition ? value1 : value2; === Solution: Evaluate condition first and then to offer method calls for stepping based on the result.
*** Issue 157166 has been marked as a duplicate of this issue. ***
*** Issue 156311 has been marked as a duplicate of this issue. ***
A similar problem occurs in the case of conditional expressions, see the related report in issue 156311.
Fixed. http://hg.netbeans.org/main/rev/60bdc4a1c32c For a ternary operator: Condition ? TrueExpr : FalseExpr behavior has been changed in the following way: - If Step Into is invoked at Condition and there is no method call to be executed (in Condition), Condition is evaluated. The selection mode is activated having the debugger stopped before the first method call in TrueExpr, resp. FalseExpr. - If Condition contains a method call, it is not evaluated. The selection mode is displayed immediately. Method calls from both, TrueExpr and FalseExpr, are offered, however, they are highlighted in gray, meaning that it is not clear whether they will be reached or not. It is up to the user to decide if he wish to step into them directly. However, there is always possibility to step into a method call in Condition which of execution is guaranteed. - Binary conditional operators || and && are handled using an analogous logic. In (LeftOperand || RightOperand), LeftOperand is treated like Condition and RightOperand like TrueExpr : FalseExpr part.
Integrated into 'main-golden', will be available in build *201004020200* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main/rev/60bdc4a1c32c User: Daniel Prusa <dprusa@netbeans.org> Log: #155097: Step into ternary and binary conditional operators fixed.