From rodney.bates at gmx.com  Tue Nov  1 17:08:44 2022
From: rodney.bates at gmx.com (Rodney Bates)
Date: Tue, 1 Nov 2022 11:08:44 -0500
Subject: [M3devel] [modula3/cm3] Float literal exceeding type exponent
 produces error in C backend (Issue #1111)
In-Reply-To: <modula3/cm3/issues/1111@github.com>
References: <modula3/cm3/issues/1111@github.com>
Message-ID: <713c0197-2315-4564-9198-f9a41f387960@gmx.com>

So do we want the front end to object?? I would expect the limits
to be more nuanced than just limiting the exponent, i.e, would the
validity of a maximal exponent depend on the mantissa value?
Particularly if the mantissa is not normalized?

On 10/31/22 23:17, peter mckinna wrote:
>
> Declaring a REAL variable
> r := 1.23E123; (the exponent's legal range is -37..38 from memory)
>
> produces error Infinity not declared in this scope in the C backend.
> Similarly for LONGREAL and EXTENDED (although they are the same)
> for exponents exceeding 308.
>
> ?
> Reply to this email directly, view it on GitHub <https://github.com/modula3/cm3/issues/1111>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABSVZNENG4QCB4FZIQW6QYTWGCKVPANCNFSM6AAAAAARTWH5LI>.
> You are receiving this because you are subscribed to this thread.Message ID: <modula3/cm3/issues/1111 at github.com>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://m3lists.elegosoft.com/pipermail/m3devel/attachments/20221101/7da3e25a/attachment.html>

From rodney.bates at gmx.com  Wed Nov  2 17:46:03 2022
From: rodney.bates at gmx.com (Rodney Bates)
Date: Wed, 2 Nov 2022 11:46:03 -0500
Subject: [M3devel] rodney-new branch Re: [modula3/cm3] illegal recursive
 declaration crashes frontend (Issue #1109)
In-Reply-To: <2434561667376561@mail.yandex.by>
References: <modula3/cm3/issues/1109/1293776014@github.com>
 <22051666890363@mail.yandex.by> <1923231667200037@mail.yandex.by>
 <1927431667200413@mail.yandex.by> <2434561667376561@mail.yandex.by>
Message-ID: <a33f0b9b-7424-cf66-eb12-ce8660bc6674@gmx.com>



On 11/2/22 03:14, vvm at tut.by wrote:
> Hi!
> ( In any key, pkginfo.txt in rodney-new branch is very, very strange on 2022-11-02)

In the normal github repositories, pkginfo.txt causes complete
recompile of the gcc backend.? This is very slow compared to
compiling Modula-3 code.? Most of the time,I make no changes
to m3cc, but only to code in Modula-3, which I sometimes recompile
very frequently, especially to test front end or runtime
system changes, which requires 3 complete recompiles in
rapid succession.? So I edit my local pkginfo.txt to not do m3cc,
for this reason.

But I don't want to push that change up.? I got in a mess
forgetting to undo it before committing and pushing, and the
history now shows evidence of my convoluted process to
clean it up before pushing.

> Are You special do not update master branch?
> ? ? ? ? ? ? ? ? ? ? ? ? ? ? ^^^^^^^
> Instead You update rodney-new branch?
> ( I.e. there is all good?)

After lots of past grief pushing to master, breaking things,
and lots of work to unravel it, I now push to master
only *after* pushing to rodney-new and being satisfied
with the automatic CI tests done there.? Then I push
the (hopefully) identical commit to master.? CI is
now failing to build with gcc, so I am not yet satisfied
to push to master.

> Best regards, Victor Miasnikov
> 31.10.2022, 10:16, "vvm at tut.by" <vvm at tut.by>:
>
>     Hi!
>     Are You see p280 test results?
>     It is good in half of test environments (?)
>     Best regards, Victor Miasnikov
>     31.10.2022, 10:11, "vvm at tut.by" <vvm at tut.by>:
>
>         Hi!
>         ( again personal)
>         ?About:
>         pkginfo.txt
>         We loss history in "blame view".
>         "History for cm3 / scripts / pkginfo.txt" looks good
>         Best regards, Victor Miasnikov
>         27.10.2022, 20:17, "vvm at tut.by" <vvm at tut.by>:
>
>             Hi!
>
>             ( non Github,? but personal message)
>
>             ? Are You online at this moment?
>             I don't remember Time Zone
>
>
>             Variant B
>
>             "What are You doing?"
>
>             As I known, anyone with "write rights" on Github can merge rodney-new branch to master branch.
>
>             ?Yes? Or no?
>             Variant A
>
>             I usual use GUI utility "GIT Kraken", but new version 8.10.1 is "hi experimental".
>
>             ?May be best avoid use 8.10.X at near next week or month
>
>
>             Best regards, Victor Miasnikov
>
>
>
>             -------- Forward message --------
>             27.10.2022, 19:23, "Rodney M. Bates" <notifications at github.com>:
>
>
>
>             On 10/26/22 16:46, peter mckinna wrote:
>             > I didn't see a git pull in your earlier email.
>             > You did the fetch which just gets the commits but not
>             > the pull which puts them into the branch. Was that an oversight?
>             >
>             >
>
>             No, no oversight.? Per Eric's advice from months ago,
>             for getting my local master updated, I fetch, then
>             rebase.? But in backscrolling, I see a mistake.? I
>             actually did a merge upstream/master instead of a rebase,
>             and that was what refused:
>
>             ? :~/proj/m3/git-merge/cm3/master$ git merge upstream/master
>             ? fatal: Not possible to fast-forward, aborting.
>
>             Moreover, I remember doing some kind of config on merge,
>             that makes it do fast-forward only, which explains the
>             refusal to do it another way.
>
>             So I tried again with the rebase.? That refused too, but
>             unlike merge, it told me about one simple change to my
>             local master that explains why fast-forward was impossible.
>             Fixing that, the rebase worked as expected.
>
>             So thanks for the question, as it made me look in the right
>             place to discover the problem.
>
>             >
>             > On Thu, 27 Oct 2022 at 03:35, Rodney M. Bates ***@***.***>
>             > wrote:
>             >
>             > >
>             > >
>             > > On 10/24/22 17:46, peter mckinna wrote:
>             > > > Your local rodney-new should be in sync with the remote, so just
>             > > > merge into master locally, then push. Are the CI testers making
>             > > > changes to rodney-new?
>             > >
>             > > I don't think so.
>             > >
>             > > I prefer creating a merged (or rebased) local rodney-new and pushing
>             > > it first, to avoid risking introducing breakage in github master.
>             > > But.. regardless of that, before I can create a merge either way,
>             > > I have to get github master to pull down, which is where I am stuck
>             > > right now. This used to work.
>             > >
>             > > > I'm not sure about remote merging.
>             > > >
>             > > > This whole CI thing might need examination. I get they are testing
>             > > > on all architectures but as far as I can tell they are only using the C
>             > > > backend whereas they should be testing other backends as well.
>             > > > Also which branches do they test?
>             > > \
>             > > As of the last time I pushed rodney-new, it provoked tests.
>             > >
>             > > > Surely not all branches. How
>             > > > would one get them to test a particular branch? And while we are at it,
>             > > > I think a bit of judicious pruning of some of those github branches
>             > > would be
>             > > > beneficial.
>             > > >
>             > > > On Tue, 25 Oct 2022 at 08:53, Rodney M. Bates ***@***.***>
>             > > > wrote:
>             > > >
>             > > > > I have been using an even more conservative (I think) procedure. I
>             > > alter
>             > > > > local master only from github master. Then merge or rebase into my
>             > > local
>             > > > > branch rodney-new, push that up to github rodney-new, and let the CI
>             > > tests
>             > > > > run on it. If they are good enough, then I push local rodney-new to
>             > > > > github master. But now I can't even do step one.
>             > > > >
>             > > > > On 10/24/22 16:05, peter mckinna wrote:
>             > > > > > Eric may have better solutions but I do the following.
>             > > > > >
>             > > > > > If I have been making minor changes on master make sure you are on
>             > > the
>             > > > > > master branch
>             > > > > > on your local machine.
>             > > > > >
>             > > > > > git checkout master
>             > > > > > git branch (to make sure)
>             > > > > > git fetch
>             > > > > > git pull --rebase origin master (rebase creates commits on your local
>             > > > > > master so your changes are the latest - may provoke conflicts)
>             > > > > > git push origin master (sends your local master to remote)
>             > > > > >
>             > > > > > If I have created a local branch I merge on my local machine first
>             > > then
>             > > > > do
>             > > > > > the push.
>             > > > > >
>             > > > > > git checkout master (make sure you are on master locally)
>             > > > > > git fetch
>             > > > > > git pull --rebase origin master
>             > > > > > git merge other-branch (may have conflicts gti tells you what to do)
>             > > > > > git commit -a ( creates a merge commit)
>             > > > > > git push origin master (or just git push works for me)
>             > > > > >
>             > > > > > now master branch should be the same on local and remote.
>             > > > > >
>             > > > > > git log (verify your commits are in place)
>             > > > > >
>             > > > > >
>             > > > > >
>             > > > > >
>             > > > > > On Tue, 25 Oct 2022 at 07:30, Rodney M. Bates ***@***.***>
>             > > > > > wrote:
>             > > > > >
>             > > > > > > PS:
>             > > > > > >
>             > > > > > > 1. I am quite sure this is the way I did this last time, some
>             > > months
>             > > > > ago.
>             > > > > > >
>             > > > > > > 2. I have definitely made no changes to my local master copy since
>             > > > > then.
>             > > > > > >
>             > > > > > > 3. I pushed my rodney-new branch up to github, in case somebody
>             > > has an
>             > > > > > > urgent need for its contents.
>             > > > > > >
>             > > > > > > 4. I added a bunch of cases to e019. All give compile errors, as
>             > > > > expected
>             > > > > > > using my latest compiler, built from rodney-new, but don't crash. A
>             > > > > > > couple give a second, probably extraneous, compile message.
>             > > > > > >
>             > > > > > > On 10/24/22 15:01, Rodney Bates wrote:
>             > > > > > > > OK, excuse my frustration, but once again, I can't seem to
>             > > > > > > > get the most basic things done in git, despite a 300+ page
>             > > > > > > > book, a 400+ page book, and lots of helpful emails from last
>             > > fall.
>             > > > > > > >
>             > > > > > > > All I am trying at this point is to get my local master branch
>             > > > > > > > up to date with the github master branch. I have:
>             > > > > > > >
>             > > > > > > > ~/proj/m3/git-merge/cm3/master$ git remote -v
>             > > > > > > > eric https://github.com/coder5506/cm3.git (fetch)
>             > > > > > > > eric https://github.com/coder5506/cm3.git (push)
>             > > > > > > > origin /home/rodney/proj/m3/git-devel/cm3 (fetch)
>             > > > > > > > origin /home/rodney/proj/m3/git-devel/cm3 (push)
>             > > > > > > > upstream https://github.com/modula3/cm3.git (fetch)
>             > > > > > > > upstream https://github.com/modula3/cm3.git (push)
>             > > > > > > >
>             > > > > > > > and have done git fetch:
>             > > > > > > >
>             > > > > > > > ~/proj/m3/git-merge/cm3/master$ git remote -v
>             > > > > > > > eric https://github.com/coder5506/cm3.git (fetch)
>             > > > > > > > eric https://github.com/coder5506/cm3.git (push)
>             > > > > > > > origin /home/rodney/proj/m3/git-devel/cm3 (fetch)
>             > > > > > > > origin /home/rodney/proj/m3/git-devel/cm3 (push)
>             > > > > > > > upstream https://github.com/modula3/cm3.git (fetch)
>             > > > > > > > upstream https://github.com/modula3/cm3.git (push)
>             > > > > > > > ***@***.***:~/proj/m3/git-merge/cm3/master$ git fetch upstream
>             > > > > > > > remote: Enumerating objects: 615, done.
>             > > > > > > > remote: Counting objects: 100% (614/614), done.
>             > > > > > > > remote: Compressing objects: 100% (231/231), done.
>             > > > > > > > remote: Total 615 (delta 373), reused 592 (delta 367),
>             > > pack-reused 1
>             > > > > > > > Receiving objects: 100% (615/615), 556.76 KiB | 1.66 MiB/s, done.
>             > > > > > > > Resolving deltas: 100% (373/373), completed with 27 local
>             > > objects.
>             > > > > > > > From https://github.com/modula3/cm3
>             > > > > > > > 57ee5febdb..65ca3e1248 master -> upstream/master
>             > > > > > > > * [new branch] zcxh -> upstream/zcxh
>             > > > > > > >
>             > > > > > > > apparently successfully. so all the files of master on github
>             > > > > > > > should be copied locally inside my .git, and my "remote"
>             > > > > > > > (confusingly misnamed) named upstream should point to my
>             > > > > > > > local copy of the latest github.master.head.
>             > > > > > > >
>             > > > > > > > But:
>             > > > > > > >
>             > > > > > > > ~/proj/m3/git-merge/cm3/master$ git merge upstream/master
>             > > > > > > > fatal: Not possible to fast-forward, aborting.
>             > > > > > > > ***@***.***:~/proj/m3/git-merge/cm3/master$ git merge upstream
>             > > master
>             > > > > > > > merge: upstream - not something we can merge
>             > > > > > > >
>             > > > > > > >
>             > > > > > > > Previously, I remember discovering that some git
>             > > > > > > > commands call for "upstream/master" and others "upstream master"
>             > > to
>             > > > > > > > name a (local copy of) a branch at a remote location, but I don't
>             > > > > find
>             > > > > > > > any reference material telling me which, particularly for git
>             > > merge,
>             > > > > > > > so I tried both. Looks like the slash was the right one, but why
>             > > > > > > > does it refuse and what to do?
>             > > > > > > >
>             > > > > > > >
>             > > > > > > > On 10/18/22 21:17, peter mckinna wrote:
>             > > > > > > >> No worries,
>             > > > > > > >>
>             > > > > > > >> I have had merge problems of my own in the past.
>             > > > > > > >> While you are at it, have a look at e020. It compiles but
>             > > crashes.
>             > > > > > > >> The stderr.pgm file suggests it should produce a runtime
>             > > > > > > >> error - invalid cycle in super types.
>             > > > > > > >>
>             > > > > > > >
>             > > > > > >
>             > > > > > > ?
>             > > > > > > Reply to this email directly, view it on GitHub
>             > > > > > > <
>             > > https://github.com/modula3/cm3/issues/1109#issuecomment-1289576520>,
>             > > > > or
>             > > > > > > unsubscribe
>             > > > > > > <
>             > > > >
>             > > https://github.com/notifications/unsubscribe-auth/ABALZX34KOPHPTMBMK22FETWE3WXVANCNFSM6AAAAAARHTSKR4
>             > > > > >
>             > > > > > > .
>             > > > > > > You are receiving this because you authored the thread.Message ID:
>             > > > > > > ***@***.***>
>             > > > > > >
>             > > > > >
>             > > > > > ?
>             > > > > > Reply to this email directly, view it on GitHub <
>             > > > > https://github.com/modula3/cm3/issues/1109#issuecomment-1289615617>,
>             > > or
>             > > > > unsubscribe <
>             > > > >
>             > > https://github.com/notifications/unsubscribe-auth/ABSVZNDIIQRY5SENVUIWEODWE32ZFANCNFSM6AAAAAARHTSKR4
>             > > > > >.
>             > > > > > You are receiving this because you commented.Message ID: ***@***.***>
>             > > > > >
>             > > > >
>             > > > > ?
>             > > > > Reply to this email directly, view it on GitHub
>             > > > > <https://github.com/modula3/cm3/issues/1109#issuecomment-1289664620>,
>             > > or
>             > > > > unsubscribe
>             > > > > <
>             > > https://github.com/notifications/unsubscribe-auth/ABALZX4HSACTPBLNRB6X2XTWE4AMZANCNFSM6AAAAAARHTSKR4
>             > > >
>             > > > > .
>             > > > > You are receiving this because you authored the thread.Message ID:
>             > > > > ***@***.***>
>             > > > >
>             > > >
>             > > > ?
>             > > > Reply to this email directly, view it on GitHub <
>             > > https://github.com/modula3/cm3/issues/1109#issuecomment-1289727310>, or
>             > > unsubscribe <
>             > > https://github.com/notifications/unsubscribe-auth/ABSVZNFFRN2YUCATIPIH2CDWE4GTZANCNFSM6AAAAAARHTSKR4
>             > > >.
>             > > > You are receiving this because you commented.Message ID: ***@***.***>
>             > > >
>             > >
>             > > ?
>             > > Reply to this email directly, view it on GitHub
>             > > <https://github.com/modula3/cm3/issues/1109#issuecomment-1292311346>, or
>             > > unsubscribe
>             > > <https://github.com/notifications/unsubscribe-auth/ABALZX7ZJUSZN5HCHHXBDGTWFFMTVANCNFSM6AAAAAARHTSKR4>
>             > > .
>             > > You are receiving this because you authored the thread.Message ID:
>             > > ***@***.***>
>             > >
>             >
>             > ?
>             > Reply to this email directly, view it on GitHub <https://github.com/modula3/cm3/issues/1109#issuecomment-1292689196>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABSVZNHO42WKQZRYYEJ2KRDWFGRDDANCNFSM6AAAAAARHTSKR4>.
>             > You are receiving this because you commented.Message ID: ***@***.***>
>             >
>
>             ?
>             Reply to this email directly, view it on GitHub <https://github.com/modula3/cm3/issues/1109#issuecomment-1293776014>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ALUI7HGJEQ3SVKAUW3GZ56LWFKT6NANCNFSM6AAAAAARHTSKR4>.
>             You are receiving this because you commented.Message ID: <modula3/cm3/issues/1109/1293776014 at github.com>
>
>
>             -------- ????? ????????????? ????????? --------
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://m3lists.elegosoft.com/pipermail/m3devel/attachments/20221102/04125437/attachment-0001.html>

From vvm at tut.by  Wed Nov  2 18:06:55 2022
From: vvm at tut.by (vvm at tut.by)
Date: Wed, 02 Nov 2022 20:06:55 +0300
Subject: [M3devel] rodney-new branch Re: [modula3/cm3] illegal recursive
 declaration crashes frontend (Issue #1109)
In-Reply-To: <a33f0b9b-7424-cf66-eb12-ce8660bc6674@gmx.com>
References: <modula3/cm3/issues/1109/1293776014@github.com>
 <22051666890363@mail.yandex.by> <1923231667200037@mail.yandex.by>
 <1927431667200413@mail.yandex.by> <2434561667376561@mail.yandex.by>
 <a33f0b9b-7424-cf66-eb12-ce8660bc6674@gmx.com>
Message-ID: <2588361667407956@mail.yandex.by>

An HTML attachment was scrubbed...
URL: <http://m3lists.elegosoft.com/pipermail/m3devel/attachments/20221102/2b054d58/attachment-0001.html>

From vvm at tut.by  Thu Nov  3 10:46:59 2022
From: vvm at tut.by (vvm at tut.by)
Date: Thu, 03 Nov 2022 12:46:59 +0300
Subject: [M3devel] rodney-new branch Re: [modula3/cm3] illegal recursive
 declaration crashes frontend (Issue #1109)
In-Reply-To: <b13450ec-257d-07ce-c2ba-9672024b1392@gmx.com>
References: <modula3/cm3/issues/1109/1293776014@github.com>
 <22051666890363@mail.yandex.by> <1923231667200037@mail.yandex.by>
 <1927431667200413@mail.yandex.by> <2434561667376561@mail.yandex.by>
 <a33f0b9b-7424-cf66-eb12-ce8660bc6674@gmx.com>
 <2588361667407956@mail.yandex.by>
 <b13450ec-257d-07ce-c2ba-9672024b1392@gmx.com>
Message-ID: <3164431667468041@mail.yandex.by>

An HTML attachment was scrubbed...
URL: <http://m3lists.elegosoft.com/pipermail/m3devel/attachments/20221103/519c4a08/attachment-0001.html>

From rodney.bates at gmx.com  Fri Nov 11 20:47:30 2022
From: rodney.bates at gmx.com (Rodney Bates)
Date: Fri, 11 Nov 2022 13:47:30 -0600
Subject: [M3devel] My changes merged, won't build on gcc
In-Reply-To: <598551667070682@mail.yandex.by>
References: <ba75ebb9-dd7b-82d0-b0dc-771d370e7d57@gmx.com>
 <MWHPR1401MB195194A3312229BFC55B9F11E6359@MWHPR1401MB1951.namprd14.prod.outlook.com>
 <598551667070682@mail.yandex.by>
Message-ID: <3d331750-fcd2-1ab1-22f4-7a2771700733@gmx.com>



On 10/29/22 14:14, vvm at tut.by wrote:
> + coder5506@, peter.mckinna@
> Hi!
>
>
> CI/CD has been fixed ( in fact there is upgraded bootstrap used in Github Actions runner) two weeks ago

So where is this fix, and how do I get it into the CI run that
is triggered by pushing to branch rodney-new?? As of my latest
push, the gcc version error is still happening.

>
>
> Beat regards, Victor Miasnikov
>
> 29.10.2022, 20:51, "Jay K" <jayk123 at hotmail.com>:
>
>     Unfortunately the CI is not written /quite /correctly so this is "normal".
>     It isn't written to accomodate changes to the cm3/gcc interchange format.
>     It isn't very wrong, just slightly.
>
>     ? - Jay
>     ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>     *From:* M3devel <m3devel-bounces at elegosoft.com> on behalf of Rodney Bates <rodney.bates at gmx.com>
>     *Sent:* Saturday, October 29, 2022 3:54 PM
>     *To:* m3devel <m3devel at elegosoft.com>; modula3/cm3 <cm3 at noreply.github.com>; Rodney Bates <rodney.m.bates at acm.org>
>     *Subject:* [M3devel] My changes merged, won't build on gcc
>     The merge of my changes with the master branch are now pushed to
>     github in branch rodney-new.? It fails to build with the gcc back
>     end with:
>
>     cm3cg: fatal error: *** bad M3CG version stamp (0x110), expected 0x120
>
>     It builds for me locally, and front group recompiles itself twice.
>
>
>     ,
>
>     _______________________________________________
>     M3devel mailing list
>     M3devel at elegosoft.com
>     https://m3lists.elegosoft.com/mailman/listinfo/m3devel
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://m3lists.elegosoft.com/pipermail/m3devel/attachments/20221111/006c8260/attachment.html>

From vvm at tut.by  Sat Nov 12 08:38:07 2022
From: vvm at tut.by (vvm at tut.by)
Date: Sat, 12 Nov 2022 10:38:07 +0300
Subject: [M3devel] My changes merged, won't build on gcc
In-Reply-To: <3d331750-fcd2-1ab1-22f4-7a2771700733@gmx.com>
References: <ba75ebb9-dd7b-82d0-b0dc-771d370e7d57@gmx.com>
 <MWHPR1401MB195194A3312229BFC55B9F11E6359@MWHPR1401MB1951.namprd14.prod.outlook.com>
 <598551667070682@mail.yandex.by>
 <3d331750-fcd2-1ab1-22f4-7a2771700733@gmx.com>
Message-ID: <4405611668238405@mail.yandex.by>

An HTML attachment was scrubbed...
URL: <http://m3lists.elegosoft.com/pipermail/m3devel/attachments/20221112/13a5107c/attachment.html>

From vvm at tut.by  Wed Nov 16 09:10:48 2022
From: vvm at tut.by (vvm at tut.by)
Date: Wed, 16 Nov 2022 11:10:48 +0300
Subject: [M3devel] My changes merged, won't build on gcc
In-Reply-To: <4405611668238405@mail.yandex.by>
References: <ba75ebb9-dd7b-82d0-b0dc-771d370e7d57@gmx.com>
 <MWHPR1401MB195194A3312229BFC55B9F11E6359@MWHPR1401MB1951.namprd14.prod.outlook.com>
 <598551667070682@mail.yandex.by>
 <3d331750-fcd2-1ab1-22f4-7a2771700733@gmx.com>
 <4405611668238405@mail.yandex.by>
Message-ID: <6939101668585938@mail.yandex.by>

An HTML attachment was scrubbed...
URL: <http://m3lists.elegosoft.com/pipermail/m3devel/attachments/20221116/6d127963/attachment-0001.html>