Re: Info about the -Mdelphi mode

Warren Postma via fpc-pascal <[email protected]> Sun, 26 Apr 2026 10:04:26 -0700
Newsgroups gmane.comp.compilers.free-pascal.general
Message-ID <CAPJ9avO+xwDcV14R5ohbSmb2FraCAv+PggEnp3mg4iaFcmxm0Q@mail.gmail.com>
--===============1990868527089012820==
Content-Type: multipart/alternative; boundary="0000000000004a675506505ffec5"

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

Failure to track valuable delphi capabilities and compatibilotu reads as
people being stuck in the mud of =E2=80=9Cwe never dun it this way before=
=E2=80=9D.




On Sun, Apr 26, 2026 at 4:41=E2=80=AFAM Tomas Hajny via fpc-pascal <
[email protected]> wrote:

> 25. dubna 2026 21:09:55 SEL=C4=8C, Graeme Geldenhuys via fpc-pascal <
> [email protected]> napsal:
> > On Saturday, 25 April 2026 18:38:09 BST Tomas Hajny via fpc-pascal wrot=
e:
> > > it should be strongly discouraged because it is not compliant to
> Pascal.
> >
> > Ummm... Let's use examples:
>  .
>  .
> > It's called language evolution.
>
> Your examples are (mostly) new features rather than changes to the syntax
> rules of the language. While weakening previously existing rules may be
> considered "evolution", others may consider them degradation.
>
> Tomas
>
> _______________________________________________
> fpc-pascal maillist  -  [email protected]
> https://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal
>

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

<div dir=3D"auto">Failure to track valuable delphi capabilities and compati=
bilotu reads as people being stuck in the mud of =E2=80=9Cwe never dun it t=
his way before=E2=80=9D.</div><div dir=3D"auto"><br></div><div dir=3D"auto"=
><br></div><div dir=3D"auto"><br></div><div><br><div class=3D"gmail_quote g=
mail_quote_container"><div dir=3D"ltr" class=3D"gmail_attr">On Sun, Apr 26,=
 2026 at 4:41=E2=80=AFAM Tomas Hajny via fpc-pascal &lt;<a href=3D"mailto:f=
[email protected]">[email protected]</a>&gt; wro=
te:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px =
0.8ex;border-left-width:1px;border-left-style:solid;padding-left:1ex;border=
-left-color:rgb(204,204,204)">25. dubna 2026 21:09:55 SEL=C4=8C, Graeme Gel=
denhuys via fpc-pascal &lt;<a href=3D"mailto:[email protected]=
g" target=3D"_blank">[email protected]</a>&gt; napsal:<br>
&gt; On Saturday, 25 April 2026 18:38:09 BST Tomas Hajny via fpc-pascal wro=
te:<br>
&gt; &gt; it should be strongly discouraged because it is not compliant to =
Pascal.<br>
&gt; <br>
&gt; Ummm... Let&#39;s use examples:<br>
=C2=A0.<br>
=C2=A0.<br>
&gt; It&#39;s called language evolution.<br>
<br>
Your examples are (mostly) new features rather than changes to the syntax r=
ules of the language. While weakening previously existing rules may be cons=
idered &quot;evolution&quot;, others may consider them degradation.<br>
<br>
Tomas<br>
<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></div>

--0000000000004a675506505ffec5--

--===============1990868527089012820==
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

--===============1990868527089012820==--