-
Notifications
You must be signed in to change notification settings - Fork 3
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
Actual integer function parameter not being coerced in the presence of a real parameter? #440
Comments
Also need to handle |
dbenn
added a commit
that referenced
this issue
Jul 12, 2024
…; added conversion of bool, int, real to string function params
I think I may be mutating actual parameters (which could be bound to variables) in the process of type conversion. Will test and confirm including adding a regression test. Need to copy operands on mutation and replace in the actual parameter list. |
dbenn
added a commit
that referenced
this issue
Jul 13, 2024
…erand (original or modified) and changed calling code to accommodate; added a UT to check that parameter conversion does not change actual parameter
Fixed now |
dbenn
added a commit
that referenced
this issue
Jul 14, 2024
…ter-not-being-coerced-in-the-presence-of-a-real-parameter #440: ensured that converted operand is returned and fixed UT results…
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The following:
yields:
Since the actual parameter 4 should have been coerced from an
integer
into areal
, the message should be:This suggests a problem with type coercion from actual to formal parameters.
The text was updated successfully, but these errors were encountered: