Update
This commit is contained in:
@@ -298,7 +298,7 @@ ENDIF.
|
||||
|
||||
> **💡 Note**<br>
|
||||
> - Control structures can be nested. It is recommended that you do not include more than 5 nested control structures since the code will
|
||||
> get really hard to understand. Better go for outsourcing functionality into methods to reduce nested control control structures.
|
||||
> get really hard to understand. Better go for outsourcing functionality into methods to reduce nested control structures.
|
||||
> - Keep the number of consecutive control structures low.
|
||||
> - If you are convinced that a specified logical expression must always be true, you might include a statement like `ASSERT 1 = 0.` to go
|
||||
> sure - as implied in the example's `ELSE` statement above. However, an `ELSE` statement that is never executed might be a hint that
|
||||
@@ -579,7 +579,7 @@ Function modules ...
|
||||
...
|
||||
ENDFUNCTION.
|
||||
```
|
||||
- have a parameter interface that's similar to ABAP classes. Note: In ADT, the parameter interface of a function module is defined in ABAP pseudo syntax. These statements are not compiled like genuine ABAP statements and are not subject to the regular ABAP syntax checks. Find more information on the parameter inteface in the [ABAP Keyword Documentation](https://help.sap.com/doc/abapdocu_cp_index_htm/CLOUD/en-US/index.htm?file=abenfunction.htm).
|
||||
- have a parameter interface that's similar to ABAP classes. Note: In ADT, the parameter interface of a function module is defined in ABAP pseudo syntax. These statements are not compiled like genuine ABAP statements and are not subject to the regular ABAP syntax checks. Find more information on the parameter interface in the [ABAP Keyword Documentation](https://help.sap.com/doc/abapdocu_cp_index_htm/CLOUD/en-US/index.htm?file=abenfunction.htm).
|
||||
- are called using `CALL FUNCTION` statements.
|
||||
|
||||
Function pools ...
|
||||
|
||||
Reference in New Issue
Block a user