Re: Info about the -Mdelphi mode

--===============6590590947434124762==
Content-Type: multipart/alternative; boundary="00000000000077f8f506504b9f2f"

--00000000000077f8f506504b9f2f
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Every modern language has inline variabler declarations because it was
always a thing in the one most of us care about.

Not having inline variables means that our strongly typed language Pascal
doesn't have as precise a scoping of variables as possible, preventing read
access before initialization, which is a major smell in the pascal language
and compiler designs.

Warren

On Fri, Apr 24, 2026 at 1:53=E2=80=AFAM Marco van de Voort via fpc-pascal <
[email protected]> wrote:

>
> Op 24-4-2026 om 10:12 schreef Martin Frb via fpc-pascal:
> > CC'ed to [email protected] =3D> for follow ups
> >
> > On 23/04/2026 15:23, Graeme Geldenhuys via fpc-pascal wrote:
> >> On Thursday, 23 April 2026 10:53:02 BST michael via fpc-pascal wrote:
> >>> Other than that I have no knowledge of missing delphi things except
> >>> inline variables.
> >> I just just reading a article from a few years ago, explaining the pro=
s
> and
> >> cons of inline variables. It actually made a really good case for that=
.
> There
> >> is a open MR for inline variables already - just not review/merged.
> >>
> >>
> https://blogs.embarcadero.com/introducing-inline-variables-in-the-delphi-=
language/
> > Apart from the general yes/no question....
> > (and I haven't looked deep into language design..., still...)
> >
> (also, many people want to read in that stack layout follows the nesting
> of inline variables. I however think that there is no direct relation
> between declaring and where the stackframe is created. (probably once at
> the beginning only) But I don't have a new enough Delphi, and the thread
> died before anybody answered)
> _______________________________________________
> fpc-pascal maillist  -  [email protected]
> https://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal
>

--00000000000077f8f506504b9f2f
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>Every modern language has inline variabler declaratio=
ns because it was always a thing in the one most of us care about.<br><br><=
/div><div>Not having inline variables means that our strongly typed languag=
e Pascal doesn&#39;t have as precise a scoping of variables as possible, pr=
eventing read access before initialization, which is a major smell in the p=
ascal language and compiler designs.</div><div><br></div><div>Warren</div><=
/div><br><div class=3D"gmail_quote gmail_quote_container"><div dir=3D"ltr" =
class=3D"gmail_attr">On Fri, Apr 24, 2026 at 1:53=E2=80=AFAM Marco van de V=
oort via fpc-pascal &lt;<a href=3D"mailto:[email protected]">=
[email protected]</a>&gt; wrote:<br></div><blockquote class=
=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rg=
b(204,204,204);padding-left:1ex"><br>
Op 24-4-2026 om 10:12 schreef Martin Frb via fpc-pascal:<br>
&gt; CC&#39;ed to <a href=3D"mailto:[email protected]" target=
=3D"_blank">[email protected]</a> =3D&gt; for follow ups<br>
&gt;<br>
&gt; On 23/04/2026 15:23, Graeme Geldenhuys via fpc-pascal wrote:<br>
&gt;&gt; On Thursday, 23 April 2026 10:53:02 BST michael via fpc-pascal wro=
te:<br>
&gt;&gt;&gt; Other than that I have no knowledge of missing delphi things e=
xcept<br>
&gt;&gt;&gt; inline variables.<br>
&gt;&gt; I just just reading a article from a few years ago, explaining the=
 pros and<br>
&gt;&gt; cons of inline variables. It actually made a really good case for =
that. There<br>
&gt;&gt; is a open MR for inline variables already - just not review/merged=
.<br>
&gt;&gt;<br>
&gt;&gt; <a href=3D"https://blogs.embarcadero.com/introducing-inline-variab=
les-in-the-delphi-language/" rel=3D"noreferrer" target=3D"_blank">https://b=
logs.embarcadero.com/introducing-inline-variables-in-the-delphi-language/</=
a><br>
&gt; Apart from the general yes/no question....<br>
&gt; (and I haven&#39;t looked deep into language design..., still...)<br>
&gt;<br>
(also, many people want to read in that stack layout follows the nesting <b=
r>
of inline variables. I however think that there is no direct relation <br>
between declaring and where the stackframe is created. (probably once at <b=
r>
the beginning only) But I don&#39;t have a new enough Delphi, and the threa=
d <br>
died before anybody answered)<br>
_______________________________________________<br>
fpc-pascal maillist=C2=A0 -=C2=A0 <a href=3D"mailto:[email protected]=
scal.org" target=3D"_blank">[email protected]</a><br>
<a href=3D"https://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal=
" rel=3D"noreferrer" target=3D"_blank">https://lists.freepascal.org/cgi-bin=
/mailman/listinfo/fpc-pascal</a><br>
</blockquote></div>

--00000000000077f8f506504b9f2f--

--===============6590590947434124762==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
fpc-pascal maillist  -  [email protected]
https://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal

--===============6590590947434124762==--