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
Copy file name to clipboardExpand all lines: docs/checks/form-routine.md
+2-9Lines changed: 2 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,29 +1,22 @@
1
-
# code pal for ABAP
2
-
3
1
[code pal for ABAP](../../README.md) > [Documentation](../check_documentation.md) > [FORM Routine Check](form-routine.md)
4
2
5
3
## FORM Routine Usage Check
6
4
7
5
### What is the Intent of the Check?
8
6
9
-
`FORM` Routines are sub-routines in procedural programming. With the release of Object Oriented ABAP this syntax became obsolete.
7
+
This check searches for the usage of FORM Routines (procedural programming) since with the release of Object Oriented ABAP this syntax became obsolete.
10
8
11
9
### How does the check work?
12
10
13
11
This check searches for the usage of the `ENDFORM` statement.
14
12
15
-
### Which attributes can be maintained?
16
-
17
-

18
-
19
13
### How to solve the issue?
20
14
21
15
Use classes and methods instead. Methods are similar to subroutines and can be used for modularization.
22
16
23
17
### What to do in case of exception?
24
18
25
-
You can suppress Code Inspector findings generated by this check using the pseudo comment `"#EC CI_FORM`.
26
-
The pseudo comment must be placed right after the `ENDFORM`.
19
+
In exceptional cases, you can suppress this finding by using the pseudo comment `"#EC CI_FORM` which should be placed right after the `ENDFORM`:
0 commit comments