-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
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
Feature/ls24003953/parm factor1 #606
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If this feature allows to put the parameter output in more than one field, I would add in the test case another parameter.
@lanarimarco test coverage should now be improved.
All these behaviours have been checked on AS400 thanks to the support of @davidepalladino-apuliasoft |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Another little change
Description
When using
PARM
withCALL
operations, the first factor of thePARM
can be used to specify where to put the "updated" value of the parameter when callee terminates its execution.For instance in the following snippet, when
PROCEDURE
ends its execution, the new value of$A
gets put in*IN36
This feature of
PARM
was unsupported.From a technical standpoint changes concern:
result
field inPlistParam
PARM
factor 1execute
method ofCallStmt
misc.kt
during the creation ofPlistParam
sRelated to:
Checklist:
./gradlew ktlintCheck
)../gradlew check
).docs
directory.