RE: Re: Re: Plan to Update GPC

--===============7980290503198446881==
Content-Type: multipart/alternative;
 boundary="=_0c44180018a33f53214143c25c0da7d0"

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

"
> FPC certainly qualifies as a cross platform OS, and I believe it
> runs well on MacOS??

It does run, but because they have a legacy of bells and whistles it
doesn't comple vanilla Pascal from 1982 (ISO 7185?)
"
=20
I'd like some more details on that. I have very extensive testing services =
with Pascal-P5,
and FPC passes, or did pass, my ISO 7185 tests.
=20
You can also just compile your stuff with Pascal-P5. As mentioned, it is pe=
rhaps the
most rigorous test of ISO 7185 compliance you will find today.
=20
You sound like a pretty advanced user of ISO 7185 Pascal, we should keep in=
 touch.
=20
I am at [email protected].
=20
Scott Franco
=20
--------- Original Message --------- Subject: Re: Re: Plan to Update GPC
From: "Thomas Schneider" <[email protected]>
Date: 8/13/20 11:23 am
To: "scott andrew franco" <[email protected]>
Cc: "[email protected]" <[email protected]>, "[email protected]" <[email protected]=
=2Egov>

Scott:
=20
 > Yes, I would not mind a decent Mac OS compiler as well. I used to
 > think I would move all of my work to MacOS, generally being a better
 > OS that the others, but these days I am to heavily involved with
 > Linux to do that. In any case, I have all three types of machines
 > (and then some) here at my house, Windows, Linux and Mac, so its
 > just a matter of what I need at the moment. In any case, I have
 > sympathy for your position.
=20
 Though I'm now using macOS for all my machines, I'm not wedded to it.=20
 If Apple keeps doing stupid things (like preventing one from doing ls
 in ~/.Trash/ !!!) then eventually I'll be forced to migrate away to
 Linux. I avoid the evil empire.
=20
 > FPC certainly qualifies as a cross platform OS, and I believe it
 > runs well on MacOS??
=20
 It does run, but because they have a legacy of bells and whistles it
 doesn't comple vanilla Pascal from 1982 (ISO 7185?) ... Since p2c will
 compile bad code and produce garbage without warning (!) I use FPC as
 an error checker and then if the program passes I give it to p2c. The
 script for this is not public. The FPC folks are working on getting
 my programs to compile properly so eventually I may be able to use
 that.
=20
 > mode, but locked you into "ISO 7185 jail", ie, made it inconvienent
 > or impossible to use their extensions unless you drop the option, in
 > which case most of your source would not compile, etc. Perhaps
 > someone with FPC experience could weigh in here.
=20
 I have intentionally avoided system dependent extensions (except for
 date/time) and as a result my programs written 30+ years ago still
 compile ... I built a 'module' system that uses comments to mark
 sections of code and inserts the sections from a library into a
 program. This way I'm not dependent on compiler dependent insertion
 commands. https://alum.mit.edu/www/toms/delila/module.html
=20
 > Your association with P2C interests me. I used that to translate
 > Pascal libraries for Petit-Ami (another one of my projects). The
 > tool is awful. It crashes if you give it any sources that are even
 > slightly wrong, and the (original) author takes pains to mention in
 > the documentation that he knows quite well about this and does not,
 > in fact, care. I wonder if you had improved that situation?
=20
 No, I provide the original with minor changes only.
 https://alum.mit.edu/www/toms/pascalp2c.html
=20
 > "I write scripts that call compilers with the parameters needed to
 > compile my programs. If the name of the compiler changes then the
 > scripts break."
 >
 > Well, ok, but note that the name for my project is Pascal-P5, has
 > been so for 10 years, and will always be named that. Pascal-P6 is a
 > whole 'nuther beast entirely. At my development rate (glacial) I
 > don't think anyone is going to need to rewrite their scripts a lot.
=20
 Ok, cool.
=20
 Tom
=20
 Thomas D. Schneider, Ph.D.
 Senior Investigator
 National Institutes of Health
 National Cancer Institute
 Center for Cancer Research
 RNA Biology Laboratory
 Biological Information Theory Group
 Frederick, Maryland 21702-1201
 [email protected]
 https://alum.mit.edu/www/toms

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

<div>"</div>
<div>&gt; FPC certainly qualifies as a cross platform OS, and I believe it<=
br />&gt; runs well on MacOS??<br /><br />It does run, but because they hav=
e a legacy of bells and whistles it<br />doesn't comple vanilla Pascal from=
 1982 (ISO 7185?)</div>
<div>"</div>
<div>&nbsp;</div>
<div>I'd like some more details on that. I have very extensive testing serv=
ices with Pascal-P5,</div>
<div>and FPC passes, or did pass, my ISO 7185 tests.</div>
<div>&nbsp;</div>
<div>You can also just compile your stuff with Pascal-P5. As mentioned, it =
is perhaps the</div>
<div>most rigorous test of ISO 7185 compliance you will find today.</div>
<div>&nbsp;</div>
<div>You sound like a pretty advanced user of ISO 7185 Pascal, we should ke=
ep in touch.</div>
<div>&nbsp;</div>
<div>I am at [email protected].</div>
<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: Re: Plan to Update GPC<br />From: "Thomas Schneider" &lt;=
[email protected]&gt;<br />Date: 8/13/20 11:23 am<br />To: "scott andre=
w franco" &lt;[email protected]&gt;<br />Cc: "[email protected]" &lt;[email protected]&=
gt;, "[email protected]" &lt;[email protected]&gt;<br /><br />Scott=
:<br /> <br /> &gt; Yes, I would not mind a decent Mac OS compiler as well=
=2E I used to<br /> &gt; think I would move all of my work to MacOS, genera=
lly being a better<br /> &gt; OS that the others, but these days I am to he=
avily involved with<br /> &gt; Linux to do that. In any case, I have all th=
ree types of machines<br /> &gt; (and then some) here at my house, Windows,=
 Linux and Mac, so its<br /> &gt; just a matter of what I need at the momen=
t. In any case, I have<br /> &gt; sympathy for your position.<br /> <br /> =
Though I'm now using macOS for all my machines, I'm not wedded to it. <br /=
> If Apple keeps doing stupid things (like preventing one from doing ls<br =
/> in ~/.Trash/ !!!) then eventually I'll be forced to migrate away to<br /=
> Linux. I avoid the evil empire.<br /> <br /> &gt; FPC certainly qualifies=
 as a cross platform OS, and I believe it<br /> &gt; runs well on MacOS??<b=
r /> <br /> It does run, but because they have a legacy of bells and whistl=
es it<br /> doesn't comple vanilla Pascal from 1982 (ISO 7185?) ... Since p=
2c will<br /> compile bad code and produce garbage without warning (!) I us=
e FPC as<br /> an error checker and then if the program passes I give it to=
 p2c. The<br /> script for this is not public. The FPC folks are working on=
 getting<br /> my programs to compile properly so eventually I may be able =
to use<br /> that.<br /> <br /> &gt; mode, but locked you into "ISO 7185 ja=
il", ie, made it inconvienent<br /> &gt; or impossible to use their extensi=
ons unless you drop the option, in<br /> &gt; which case most of your sourc=
e would not compile, etc. Perhaps<br /> &gt; someone with FPC experience co=
uld weigh in here.<br /> <br /> I have intentionally avoided system depende=
nt extensions (except for<br /> date/time) and as a result my programs writ=
ten 30+ years ago still<br /> compile ... I built a 'module' system that us=
es comments to mark<br /> sections of code and inserts the sections from a =
library into a<br /> program. This way I'm not dependent on compiler depend=
ent insertion<br /> commands. https://alum.mit.edu/www/toms/delila/module=
=2Ehtml<br /> <br /> &gt; Your association with P2C interests me. I used th=
at to translate<br /> &gt; Pascal libraries for Petit-Ami (another one of m=
y projects). The<br /> &gt; tool is awful. It crashes if you give it any so=
urces that are even<br /> &gt; slightly wrong, and the (original) author ta=
kes pains to mention in<br /> &gt; the documentation that he knows quite we=
ll about this and does not,<br /> &gt; in fact, care. I wonder if you had i=
mproved that situation?<br /> <br /> No, I provide the original with minor =
changes only.<br /> https://alum.mit.edu/www/toms/pascalp2c.html<br /> <br =
/> &gt; "I write scripts that call compilers with the parameters needed to<=
br /> &gt; compile my programs. If the name of the compiler changes then th=
e<br /> &gt; scripts break."<br /> &gt;<br /> &gt; Well, ok, but note that =
the name for my project is Pascal-P5, has<br /> &gt; been so for 10 years, =
and will always be named that. Pascal-P6 is a<br /> &gt; whole 'nuther beas=
t entirely. At my development rate (glacial) I<br /> &gt; don't think anyon=
e is going to need to rewrite their scripts a lot.<br /> <br /> Ok, cool.<b=
r /> <br /> Tom<br /> <br /> Thomas D. Schneider, Ph.D.<br /> Senior Invest=
igator<br /> National Institutes of Health<br /> National Cancer Institute<=
br /> Center for Cancer Research<br /> RNA Biology Laboratory<br /> Biologi=
cal Information Theory Group<br /> Frederick, Maryland 21702-1201<br /> sch=
[email protected]<br /> https://alum.mit.edu/www/toms</div>
</blockquote>

--=_0c44180018a33f53214143c25c0da7d0--


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

--===============7980290503198446881==--