RE: Re: Plan to Update GPC

"scott andrew franco" <[email protected]> Thu, 13 Aug 2020 10:56:39 -0700
Newsgroups gmane.comp.compilers.gpc
Message-ID <20200813105639.6c61c97e98fe7bb02193b2d6dca4a85a.acbe81ea22.mailapi@email15.godaddy.com>
--===============3460147149680674339==
Content-Type: multipart/alternative;
 boundary="=_890484a95cd27e5ddc4d064064db6882"

--=_890484a95cd27e5ddc4d064064db6882
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
 charset=utf-8

Excellent. And I also know that you have put a lot of work into that mode=
=2E
=20
I'd like to get some more time to play with the FPC ISO 7185 mode.
=20
Scott Franco
=20
--------- Original Message --------- Subject: Re: Plan to Update GPC
From: "[email protected]" <[email protected]>
Date: 8/13/20 10:48 am
To: "[email protected]" <[email protected]>


=20
 > FPC certainly qualifies as a cross platform OS, and I believe it runs we=
ll on MacOS??
 > I have never tried it. In the past it was always a big deal to convert t=
he source, but
 > nowadays, with the ISO 7185 mode, that should be a lot less work. It rea=
lly depends
 > on FPC. I know with some other compilers, the ISO 7185 switch enabled st=
andard
 > mode, but locked you into "ISO 7185 jail", ie, made it inconvienent or i=
mpossible to
 > use their extensions unless you drop the option, in which case most of y=
our source
 > would not compile, etc. Perhaps someone with FPC experience could weigh =
in
 > here.
=20
 The problem are keywords. E.g. uses is valid identifier in ISO Pascal so i=
t cannot be used as keyword to include units etc. Besides this, FPC does no=
t disable non ISO extensions in ISO mode.
=20
 _______________________________________________
 Gpc mailing list
 [email protected]
 https://www.g-n-u.de/mailman/listinfo/gpc

--=_890484a95cd27e5ddc4d064064db6882
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
 charset=utf-8

<div>Excellent. And I also know that you have put a lot of work into that m=
ode.</div>
<div>&nbsp;</div>
<div>I'd like to get some more time to play with the FPC ISO 7185 mode.</di=
v>
<div>&nbsp;</div>
<div>Scott Franco</div>
<div>&nbsp;</div>
<blockquote class=3D"threadBlockQuote" style=3D"border-left: 2px solid #C2C=
2C2; padding-left: 3px; margin-left: 4px;">--------- Original Message -----=
----
<div>Subject: Re: Plan to Update GPC<br />From: "[email protected]" &l=
t;[email protected]&gt;<br />Date: 8/13/20 10:48 am<br />To: "gpc@gnu=
=2Ede" &lt;[email protected]&gt;<br /><br /><br /> <br /> &gt; FPC certainly quali=
fies as a cross platform OS, and I believe it runs well on MacOS??<br /> &g=
t; I have never tried it. In the past it was always a big deal to convert t=
he source, but<br /> &gt; nowadays, with the ISO 7185 mode, that should be =
a lot less work. It really depends<br /> &gt; on FPC. I know with some othe=
r compilers, the ISO 7185 switch enabled standard<br /> &gt; mode, but lock=
ed you into "ISO 7185 jail", ie, made it inconvienent or impossible to<br /=
> &gt; use their extensions unless you drop the option, in which case most =
of your source<br /> &gt; would not compile, etc. Perhaps someone with FPC =
experience could weigh in<br /> &gt; here.<br /> <br /> The problem are key=
words. E.g. uses is valid identifier in ISO Pascal so it cannot be used as =
keyword to include units etc. Besides this, FPC does not disable non ISO ex=
tensions in ISO mode.<br /> <br /> ________________________________________=
_______<br /> Gpc mailing list<br /> [email protected]<br /> https://www.g-n-u.de/=
mailman/listinfo/gpc</div>
</blockquote>

--=_890484a95cd27e5ddc4d064064db6882--


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

_______________________________________________
Gpc mailing list
[email protected]
https://www.g-n-u.de/mailman/listinfo/gpc

--===============3460147149680674339==--