RE: Re: Plan to Update GPC

--===============2162859629733809875==
Content-Type: multipart/alternative;
 boundary="=_d4f9a50c01e694b953ead695980c6538"

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

Thomas,
=20
Yes, I would not mind a decent Mac OS compiler as well. I used to think I w=
ould move
all of my work to MacOS, generally being a better OS that the others, but t=
hese days
I am to heavily involved with Linux to do that. In any case, I have all thr=
ee types of
machines (and then some) here at my house, Windows, Linux and Mac, so its j=
ust
a matter of what I need at the moment. In any case, I have sympathy for you=
r
position.
=20
FPC certainly qualifies as a cross platform OS, and I believe it runs well =
on MacOS??
I have never tried it. In the past it was always a big deal to convert the =
source, but
nowadays, with the ISO 7185 mode, that should be a lot less work. It really=
 depends
on FPC. I know with some other compilers, the ISO 7185 switch enabled stand=
ard
mode, but locked you into "ISO 7185 jail", ie, made it inconvienent or impo=
ssible 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
Believe me I have been there myself. I used to keep a file called "basicio=
=2Epas" where
I kept all of the nonstandard procedures used to access OS functions like o=
pen and
close files, etc. Then I would have one of those per compiler installation/=
vendor.
Because a lot of Pascal compiler makers had a string type that was incompat=
ible
with pascal string types (which is in fact "packed array [1..xxx] of char")=
 the open
file function often translated the Pascal string to whatever the string typ=
e was on
the particular implementation (point of fact there are things like that in =
Pascal-P6
to allow GPC calls).
=20
Your association with P2C interests me. I used that to translate Pascal lib=
raries
for Petit-Ami (another one of my projects). The tool is awful. It crashes i=
f you give
it any sources that are even slightly wrong, and the (original) author take=
s pains
to mention in the documentation that he knows quite well about this and doe=
s not,
in fact, care. I wonder if you had improved that situation?
=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."
=20
Well, ok, but note that the name for my project is Pascal-P5, has been so f=
or
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
Regards,
=20
Scott Franco
=20
=20
--------- Original Message --------- Subject: Re: Plan to Update GPC
From: "Schneider, Thomas (NIH/NCI) [E]" <[email protected]>
Date: 8/13/20 8:28 am
To: "scott andrew franco" <[email protected]>, "[email protected]" <[email protected]>

Scott:
=20
 I'm just looking for Pascal compilers that run on macOS. My programs
 follow the original compilers in which the files listed at the top of
 the program are directly read and written to by the Pascal program.=20
 GPC used to do this. P2C (which I maintain apparently) translates to
 C and then provides this. I don't know what ISO that corresponds to.
=20
 > For your second point, I assume you are talking about the
 > Pascal-P1-P6 thing? (not sure I understand your point about "name
 > change breaks the code")
=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. For example, if the Unix 'ls' command were named ls763
 and then a new version were named ls764 lots of code would break.
=20
 > Can Pascal-P be used on the Mac? Well, actually yes. Pascal-P6
 > includes sufficient tooling to port without GPC (see the interpreter
 > written in C). I don't really push that capability because P6 is
 > still in development, and also because interpreters are not really
 > my thing (yes, I know that sounds funny). I like compilers. To me
 > interpreters are more of a fun toy than not, although I note that
 > there is a group pushing interpreters as "VM"s for professional use.
 > Pascal-P5 has actually been written up as such. Again, not bad, just
 > not my thing.
=20
 Ok, maybe when P6 is stablized and GPC independent it can be used to
 compile on macOS.
=20
 > I should mention there is a branch from P5 known as P5c that that
 > changed the compiler into a Pascal to C translator that accomplishes
 > porting in a different way. You would have to look into that
 > yourself, I'm not really up to speed on that.
=20
 That's interesting, thanks.
=20
 https://sourceforge.net/projects/pascal-p5c/
=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

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

<div>Thomas,</div>
<div>&nbsp;</div>
<div>Yes, I would not mind a decent Mac OS compiler as well. I used to thin=
k I would move</div>
<div>all of my work to MacOS, generally being a better OS that the others, =
but these days</div>
<div>I am to heavily involved with Linux to do that. In any case, I have al=
l three types of</div>
<div>machines (and then some) here at my house, Windows, Linux and Mac, so =
its just</div>
<div>a matter of what I need at the moment. In any case, I have sympathy fo=
r your</div>
<div>position.</div>
<div>&nbsp;</div>
<div>FPC certainly qualifies as a cross platform OS, and I believe it runs =
well on MacOS??</div>
<div>I have never tried it. In the past it was always a big deal to convert=
 the source, but</div>
<div>nowadays, with the ISO 7185 mode, that should be a lot less work. It r=
eally depends</div>
<div>on FPC. I know with some other compilers, the ISO 7185 switch enabled =
standard</div>
<div>mode, but locked you into "ISO 7185 jail", ie, made it inconvienent or=
 impossible to</div>
<div>use their extensions unless you drop the option, in which case most of=
 your source</div>
<div>would not compile, etc. Perhaps someone with FPC experience could weig=
h in</div>
<div>here.</div>
<div>&nbsp;</div>
<div>Believe me I have been there myself. I used to keep a file called "bas=
icio.pas" where</div>
<div>I kept all of the nonstandard procedures used to access OS functions l=
ike open and</div>
<div>close files, etc. Then I would have one of those per compiler installa=
tion/vendor.</div>
<div>Because a lot of Pascal compiler makers had a string type that was inc=
ompatible</div>
<div>with pascal string types (which is in fact "packed array [1..xxx] of c=
har") the open</div>
<div>file function often translated the Pascal string to whatever the strin=
g type was on</div>
<div>the particular implementation (point of fact there are things like tha=
t in Pascal-P6</div>
<div>to allow GPC calls).</div>
<div>&nbsp;</div>
<div>Your association with P2C interests me. I used that to translate Pasca=
l libraries</div>
<div>for Petit-Ami (another one of my projects). The tool is awful. It cras=
hes if you give</div>
<div>it any sources that are even slightly wrong, and the (original) author=
 takes pains</div>
<div>to mention in the documentation that he knows quite well about this an=
d does not,</div>
<div>in fact, care. I wonder if you had improved that situation?</div>
<div>&nbsp;</div>
<div>"I write scripts that call compilers with the parameters needed to<br =
/>compile my programs. If the name of the compiler changes then the<br />sc=
ripts break."</div>
<div>&nbsp;</div>
<div>Well, ok, but note that the name for my project is Pascal-P5, has been=
 so for</div>
<div>10 years, and will always be named that. Pascal-P6 is a whole 'nuther =
beast</div>
<div>entirely. At my development rate (glacial) I don't think anyone is goi=
ng to need</div>
<div>to rewrite their scripts a lot.</div>
<div>&nbsp;</div>
<div>Regards,</div>
<div>&nbsp;</div>
<div>Scott Franco</div>
<div>&nbsp;</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: "Schneider, Thomas (NIH/NCI=
) [E]" &lt;[email protected]&gt;<br />Date: 8/13/20 8:28 am<br />To: "s=
cott andrew franco" &lt;[email protected]&gt;, "[email protected]" &lt;gpc@gnu=
=2Ede&gt;<br /><br />Scott:<br /> <br /> I'm just looking for Pascal compil=
ers that run on macOS. My programs<br /> follow the original compilers in w=
hich the files listed at the top of<br /> the program are directly read and=
 written to by the Pascal program. <br /> GPC used to do this. P2C (which I=
 maintain apparently) translates to<br /> C and then provides this. I don't=
 know what ISO that corresponds to.<br /> <br /> &gt; For your second point=
, I assume you are talking about the<br /> &gt; Pascal-P1-P6 thing? (not su=
re I understand your point about "name<br /> &gt; change breaks the code")<=
br /> <br /> I write scripts that call compilers with the parameters needed=
 to<br /> compile my programs. If the name of the compiler changes then the=
<br /> scripts break. For example, if the Unix 'ls' command were named ls76=
3<br /> and then a new version were named ls764 lots of code would break.<b=
r /> <br /> &gt; Can Pascal-P be used on the Mac? Well, actually yes. Pasca=
l-P6<br /> &gt; includes sufficient tooling to port without GPC (see the in=
terpreter<br /> &gt; written in C). I don't really push that capability bec=
ause P6 is<br /> &gt; still in development, and also because interpreters a=
re not really<br /> &gt; my thing (yes, I know that sounds funny). I like c=
ompilers. To me<br /> &gt; interpreters are more of a fun toy than not, alt=
hough I note that<br /> &gt; there is a group pushing interpreters as "VM"s=
 for professional use.<br /> &gt; Pascal-P5 has actually been written up as=
 such. Again, not bad, just<br /> &gt; not my thing.<br /> <br /> Ok, maybe=
 when P6 is stablized and GPC independent it can be used to<br /> compile o=
n macOS.<br /> <br /> &gt; I should mention there is a branch from P5 known=
 as P5c that that<br /> &gt; changed the compiler into a Pascal to C transl=
ator that accomplishes<br /> &gt; porting in a different way. You would hav=
e to look into that<br /> &gt; yourself, I'm not really up to speed on that=
=2E<br /> <br /> That's interesting, thanks.<br /> <br /> https://sourcefor=
ge.net/projects/pascal-p5c/<br /> <br /> Tom<br /> <br /> Thomas D. Schneid=
er, Ph.D.<br /> Senior Investigator<br /> National Institutes of Health<br =
/> National Cancer Institute<br /> Center for Cancer Research<br /> RNA Bio=
logy Laboratory<br /> Biological Information Theory Group<br /> Frederick, =
Maryland 21702-1201<br /> [email protected]<br /> https://alum.mit.edu/=
www/toms<br /> </div>
</blockquote>

--=_d4f9a50c01e694b953ead695980c6538--


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

--===============2162859629733809875==--