[m-users.] Correct use of solutions.
Sean Charles (emacstheviking)
objitsu at gmail.com
Mon Jul 31 19:55:49 AEST 2023
Agreed. I was reading your code for that the other day actually.
As much as I sometimes still struggle with things, Mercury is now me go-to language for things larger than a quick throwaway python script.
I just like the rock solid output from it.
Douglas Adams' "Deep Thought" computer was obviously programmed using Mercury, by mice. He just didn't know it.
> On 31 Jul 2023, at 10:52, Volker Wysk <post at volker-wysk.de> wrote:
>
> Am Montag, dem 31.07.2023 um 11:58 +1000 schrieb Mark Brown:
>> In all seriousness, I think SWI Prolog is an excellent system with
>> which to implement a compiler. Even if intending to build a compiler
>> in Mercury in the long term, rapidly prototyping (parts of) it in
>> Prolog is often an excellent approach to take in my opinion.
>
> I thought that, too. But when I rapidly prototyped my command line parser in
> Prolog, I found that I missed types, determinism categories, modes...
> Declarative IO is something like this, too, but wasn't important for that
> command line parser. Things that help to get your head straight. I came to
> the conclusion that doing it "right" from the beginning is better.
>
> (That parser turned out to be much more involved than I thought.)
>
> But it's a matter of taste, I guess.
>
> Bye
> Volker
> _______________________________________________
> users mailing list
> users at lists.mercurylang.org
> https://lists.mercurylang.org/listinfo/users
More information about the users
mailing list