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
The LOOKUP FORWARD, LOOKUP BACKWARD, and LOOKUP INVERT functions takes a lookup as its first argument. This works fine when the lookup is defined using the literal lookup syntax, as in our existing test. However, when the lookup is read from a file with GET DIRECT LOOKUPS, incorrect code is generated: the lookup is dereferenced with _LOOKUP instead of being passed to the function.
The text was updated successfully, but these errors were encountered:
This is solved by handling these three functions as special forms in visitVar. Note that WITH LOOKUP also takes a lookup argument, but this case does not apply there, since the lookup argument is meant to be a literal lookup.
Some function calls in visitVar were unnecessarily repeated many times, so I took the opportunity to refactor it.
I added tests for this case in the directlookups.mdl test model.
The
LOOKUP FORWARD
,LOOKUP BACKWARD
, andLOOKUP INVERT
functions takes a lookup as its first argument. This works fine when the lookup is defined using the literal lookup syntax, as in our existing test. However, when the lookup is read from a file withGET DIRECT LOOKUPS
, incorrect code is generated: the lookup is dereferenced with_LOOKUP
instead of being passed to the function.The text was updated successfully, but these errors were encountered: