Roger, The main changes I am aware of on master are:
(1) some updates to xpp to add a bracket matching capability. It would = probably be best if I merged those into the utf8 branch via the utf8xpp = branch, as I now the xpp code. (2) Some small additions to the proof support for Z that D-RisQ needed. = You would probably be best placed to merge those, as you know more about = the conversion from EXT to UTF8. I don=E2=80=99t know what you mean by the commits that "address problems = arising in the build". Which commits did you have in mind? It would be good at least to keep the utf8 work in sync with other = developments, so I=E2=80=99d be very grateful if you did spend some time = on this. If you feel really keen, would you be able to set up a Linux = environment so that we could try to make some progress on the issues = with sieve? (If you remember, when I tried to build our utf8 work on = Linux, the utf8 support in gcc on Linux turned out to martinetishly = reject code and data that was OK on Mac OS). Regards, Rob. > On 14 Apr 2025, at 23:08, Roger Jones <[email protected]> wrote: >=20 > Rob, >=20 > The master branch of ProofPower is 35 commits ahead of utf8, and some = of those commits address problems arising in the build which now prevent = the utf8 branch from building. >=20 > Do you have any sense of how much of it might need to be retrofitted = for utf8 to build? >=20 > Is it likely that a pull request would facilitate applying those = commits to the utf8 branch, or is might there be a better way to = approach it? >=20 > This is not a big issue for me, but if it can be sorted without too = much effort I=E2=80=99m willing to put a bit of time in, I converted all = my ProofPower scripts to utf8 back in the day. >=20 > Roger _______________________________________________ Proofpower mailing list [email protected] http://lemma-one.com/mailman/listinfo/proofpower_lemma-one.com
