We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Given that the ABAP compiler doesn't have proper scope checks for inline field symbols defined in:
LOOP AT lt_table ASSIGNING FIELD-SYMBOLS(<ls_line>). ... ENDLOOP.
Meaning that it is valid code to use <ls_line> after ENDLOOP
<ls_line>
ENDLOOP
then I suggest a new check which will alert the user when such occurrences happen.
For example:
LOOP AT lt_table ASSIGNING FIELD-SYMBOLS(<ls_line>). ... ENDLOOP. WRITE <ls_line>.
The text was updated successfully, but these errors were encountered:
good idea
accessing the compiler information in ABAP is a bit difficult, but instead I might implement this in https://abaplint.org
Sorry, something went wrong.
No branches or pull requests
Given that the ABAP compiler doesn't have proper scope checks for inline field symbols defined in:
Meaning that it is valid code to use
<ls_line>
afterENDLOOP
then I suggest a new check which will alert the user when such occurrences happen.
For example:
The text was updated successfully, but these errors were encountered: