I’m an enthusiastic amateur and I like SWI very much. I’ve often been tempted, however, to put my energies into Mercury instead because of its promises of smarter compile-time checks etc. I only write medium-sized programs (10000 lines max); I do find I spend a heck of a long time debugging my code…

Without really answering your question, did you discover the SSU rules (Head => Body) and det/1? Since I use those, debugging time has been reduced a lot. Other recent goodies are trap/1 and gtrap/1 to quickly get the debugger at an exception. And of course, there is check/0 to do some static…

I’ve kept an eye on posts about => and I’ve dabbled with BProlog which, I think, has a similar feature. Thanks for all those suggestions as I’d be very happy to stick with SWI + new debugging aids.

[image] calatcryptomathic: there’s people who have experience in both and know the real upsides to each I have used Mercury in the past (~10 years ago) but don’t at present, mostly because getting support was not easy but that is slowly changing. One post of note from the creator of Mercury …

[image] calatcryptomathic: I’ve kept an eye on posts about => and I’ve dabbled with BProlog which, I think, has a similar feature. I got it from Picat. As that is a successor of BProlog, it could well come from there. Note that I made an important change though: if no rule matches it is an e…

Reasons for sticking with SWI, as opposed to Mercury

General

Topic		Replies	Views
Bridge to Mercury General	17	2410	July 7, 2019
A general comment on Prolog programming General	17	1122	April 5, 2020
How many of you realize that SWI-Prolog is an excellent, genuinely excellent language? Nice to know	3	1560	December 2, 2021
Ann: SWI-Prolog 9.3.21 Releases	3	206	March 13, 2025
Ann: SWI-Prolog 8.3.23 Releases	0	425	April 28, 2021

Reasons for sticking with SWI, as opposed to Mercury

Related topics