You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Converting CHECK outside loop to IF NOT ... RETURN considering BREAK-POINT #135
Could BREAK-POINT statement be considered the same way as local declarations at the beginning of the method so that CHECK in the following code is NOT converted to IF ... RETURN ... ENDIF?
METHOD process.
DATA a TYPE c LENGTH 1.
BREAK-POINT ID fins_rev_rec_acdocp.
CHECK a IS INITIAL.
ENDMETHOD.
that's a good point, thanks for bringing this up! And I think this is valid for all Checkpoints (ASSERT, BREAK-POINT, LOG-POINT). However, rather than considering them like local declarations, I think it would be better to add an option like "[X] Keep CHECK statement independent of previous ASSERT, BREAK-POINT, or LOG-POINT".
Activity
jmgrassau commentedon Oct 10, 2023
Hi blackfish5,
that's a good point, thanks for bringing this up! And I think this is valid for all Checkpoints (ASSERT, BREAK-POINT, LOG-POINT). However, rather than considering them like local declarations, I think it would be better to add an option like "[X] Keep CHECK statement independent of previous ASSERT, BREAK-POINT, or LOG-POINT".
Kind regards,
Jörg-Michael
add option to allow CHECK after checkpoints (SAP#135)
add option to allow CHECK after checkpoints (#135)
jmgrassau commentedon Oct 10, 2023
Hi blackfish5,
the new option is now available with version 1.7.0, which was just released! My initial wording was a bit complicated, hope this works better:
Kind regards,
Jörg-Michael
blackfish5 commentedon Oct 11, 2023
I have updated to 1.7.1 and it works as expected. Thanks a lot for swift implementation.
BR
Michal