Peter

@UWN thank you for trying this... I've replicated that and it does work, via the interactive [user] way. But the same text does not work/yields the errors, if I load...

@UWN thank you for letting me know, for your further inquiry of the issue, and sir, If I'm right, thank you for your great, great work in, how to say...

I've written: "Unfortunately, it's even worse: trad_simp_both("愛", "爱", "愛爱"). % yields error ... and spaces do not help." But it seems that even in this case spaces help: if I...

@triska: It works; thank you! ("scryer-prolog -v" says: "cargo:0.9.1". I've downloaded (as ZIP) and built it today.)

@triska Yes, thank you. I've noted it only to be sure that I have it "via ZIP", meaning I don't know if there is another version number somewhere "via Git"....

> I suspect the issue was introduced with https://github.com/mthom/scryer-prolog/commit/0e583d620ab4ad95e55371905482c65dc5431bc9 and has since then (i.e., for more than 5 months) affected all Scryer versions since then. Is that the case? The...

Now, I don't have time to experiment/minimalize further. But here is my new observation/example: The code to consult/test: ``` :- use_module(library(clpz)). test([],_). test([P|Ps], Q0) :- P #= Q, Q0 #<...

In the good Scryer version in my test example the order of variables in the line `P #= Q` does not matter: `P #= Q` or `Q #= P`, both...

We can run the **Golfer Problem** code in the bad version **successfully**, if we change `P//S #= Q` to `Q #= P//S` in `ascending_quotient/2` and `ascending_quotient/3`.

There is one thing, perhaps irrelevant, so I apologize in advance. A mix of feelings and thinking of a Prolog beginner. Yes, you can imagine my own mental model of...