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
parameters are modelled as FASTFortranAssignmentStatement, which does not work for the cases like err=10 when the right part of the expression is an instance of FASTFortranLabelReference which is not a subclass of FASTFortranExpression expected there.
Possible solutions:
make FASTFortranLabelReference inherit FASTFortranExpression
allow FASTFortranAssignmentStatement to have FASTFortranLabelReference in the right side. (Requires changes in FAST-Core!)
when FASTFortranLabelReference used as parameter, recreate is as FASTFortranIntegerLiteral
design some new type of entities or reuse existent ones to model such parameters
The text was updated successfully, but these errors were encountered:
Yes, it has been changed as a start_pos was added to a label reference.
Before the rule <110b:label_ref> = %unsigned_int_constant was returning $ptext ("%unsigned_int_constant") which was then treated as an integer in pharo.
Currently for statements like
parameters are modelled as
FASTFortranAssignmentStatement
, which does not work for the cases likeerr=10
when the right part of the expression is an instance ofFASTFortranLabelReference
which is not a subclass ofFASTFortranExpression
expected there.Possible solutions:
FASTFortranLabelReference
inheritFASTFortranExpression
FASTFortranAssignmentStatement
to haveFASTFortranLabelReference
in the right side. (Requires changes in FAST-Core!)FASTFortranLabelReference
used as parameter, recreate is asFASTFortranIntegerLiteral
The text was updated successfully, but these errors were encountered: