Skip to content

Crash with formal expression names #1

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

Open
a-maier opened this issue Jul 20, 2020 · 0 comments · May be fixed by #3
Open

Crash with formal expression names #1

a-maier opened this issue Jul 20, 2020 · 0 comments · May be fixed by #3

Comments

@a-maier
Copy link

a-maier commented Jul 20, 2020

Hi Ben,

if I use expression names in square brackets (e.g. [expression]) I get a crash with the following error

ReduceEdge Line 47 --> Illegal LHS for expression definition
++++Errors in Loop
ReduceEdge Line 107 --> Illegal LHS for expression definition
ReduceEdge Line 107 --> Illegal position for d3
ReduceEdge Line 107 --> Undeclared variable d3
ReduceEdge Line 115 ==> Proper syntax: #exchange expr1,expr2 or #exchange $var1
,$var2

I guess a simple fix would be to wrap the names of the temporary expressions themselves in square brackets, for instance [NAMEtmp] instead of NAMEtmp.

tueda added a commit to tueda/forcer that referenced this issue Mar 14, 2023
@tueda tueda linked a pull request Mar 14, 2023 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant