We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
The read_term/3 option variable_names/1 doesn't returns pairs in left-to-right traversal order as required by the ISO standard. For details, see e.g.
read_term/3
variable_names/1
http://www.complang.tuwien.ac.at/ulrich/iso-prolog/WDCor3
Example to reproduce the compliance bug:
?- current_input(S), read_term(S, T, [variables(L), variable_names(Variables)]). |: circle(_Id_, _Radius_, _Color_). L = [_B,_A,_C], S = user_input, T = circle(_B,_A,_C), Variables = ['_Color_'=_C,'_Id_'=_B,'_Radius_'=_A] ? yes
It should be:
Variables = [_Id_'=_B,'_Radius_'=_A,'_Color_'=_C,] ?
This notably breaks Logtalk's parametric object examples.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
The
read_term/3
optionvariable_names/1
doesn't returns pairs in left-to-right traversal order as required by the ISO standard. For details, see e.g.http://www.complang.tuwien.ac.at/ulrich/iso-prolog/WDCor3
Example to reproduce the compliance bug:
It should be:
This notably breaks Logtalk's parametric object examples.
The text was updated successfully, but these errors were encountered: