From post at volker-wysk.de  Wed May  1 04:34:01 2024
From: post at volker-wysk.de (Volker Wysk)
Date: Tue, 30 Apr 2024 20:34:01 +0200
Subject: [m-users.] Change in compiler behaviour for 22.01.8 ? Pointer
 type strictness increased?
In-Reply-To: <CAJpH_7KMAAfpxNbpVrbk5YXttLkUqr5X8YJ_PsJBVidxXwMo_Q@mail.gmail.com>
References: <CAJpH_7KMAAfpxNbpVrbk5YXttLkUqr5X8YJ_PsJBVidxXwMo_Q@mail.gmail.com>
Message-ID: <0033d36478c95e7cba965c4f5161dca6a5ab1ac1.camel@volker-wysk.de>

Am Samstag, dem 27.04.2024 um 10:25 -0700 schrieb M McDonough:
> 
> I just want to note this, as it's caused me issues in the past. It's a
> bad idea to have anything other than a variable or integral expression
> (no function calls, no macros, etc) as the argument to MR_list_cons
> (and I would generally say any of the MR_* macros unless you've read
> them carefully). You can end up with issues where things are executed
> in an unexpected order, and in particular on the low-level C grades,
> this can cause big issues with Mercury registers being clobbered
> leading to very hard to debug issues with seemingly impossible
> behavior.

Hmmm... I've read your thread from July 2023 about this problem. I'm
wondering if it could be remedied by wrapping it in an inline C function,
like this:


static inline MR_Word mr_list_cons(MR_Word head, MR_Word tail)
{
   MR_Word result = MR_list_cons(head, tail); 
   return result;
}


This would ensure that the expressions head, tail and the body of
MR_list_cons are evaluated in the expected order.

Cheers,
Volker

From w.karpiel at o2.pl  Sun May 12 15:55:25 2024
From: w.karpiel at o2.pl (Wojciech Karpiel)
Date: Sun, 12 May 2024 07:55:25 +0200
Subject: [m-users.] Mercury for the web
Message-ID: <53508676-fdf3-4906-a645-e10dc7052ce6@o2.pl>

Hi!

Have you managed to run Mercury client-side on the web (e.g. compiled to 
Javascript/WebAssembly)? If yes, then how?
I saw an attempt here [1] tough i don't know if there was any followup 
to that e-mail thread.

[1] https://lists.mercurylang.org/archives/reviews/2020-March/021184.html

Regards
Wojciech Karpiel


From jfischer at opturion.com  Sun May 12 23:01:58 2024
From: jfischer at opturion.com (Julien Fischer)
Date: Sun, 12 May 2024 23:01:58 +1000 (AEST)
Subject: [m-users.] Mercury for the web
In-Reply-To: <53508676-fdf3-4906-a645-e10dc7052ce6@o2.pl>
References: <53508676-fdf3-4906-a645-e10dc7052ce6@o2.pl>
Message-ID: <d1fa0f3-fbfd-6910-f1fa-80d3871b5458@opturion.com>


On Sun, 12 May 2024, Wojciech Karpiel wrote:

> Have you managed to run Mercury client-side on the web (e.g. compiled to 
> Javascript/WebAssembly)? If yes, then how?
> I saw an attempt here [1] tough i don't know if there was any followup to 
> that e-mail thread.
>
> [1] https://lists.mercurylang.org/archives/reviews/2020-March/021184.html

I'm not aware of anything since 2020.

Julien.