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
Wrong priority reported for the ('|')/2 operator #1571
Comments
Pushed a Logtalk test that exposes this bug:
|
The same problem is present in ?- current_op(Pre, Fix, '|'). Pre = 0, Fix = xfy, unexpected ; false. ?- X = (a|b). error(syntax_error(incomplete_reduction),read_term/3:1). % expected ?- use_module(library(dcgs)). true. ?- current_op(Pre, Fix, '|'). Pre = 1105, Fix = xfy % expected ; false. ?- X = (a|b). X = (a | b). % expected |
mthom
added a commit
that referenced
this issue
Aug 20, 2022
Thanks for the fix. All tests pass now:
|
mthom
added a commit
that referenced
this issue
Oct 27, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In the
rebis-dev
branch (df779bb):Same issue in the
master
branch.After some more digging, I believe this bug is responsible for #1569. The FCube port only defines this operator if the backend Prolog system doesn't define it itself. But a compliant definition is assumed (actual code simplified here):
The text was updated successfully, but these errors were encountered: