From: arnold@skeeve.com
To: 9fans@9fans.net
Subject: Re: [9fans] APL
Date: Tue, 23 Feb 2021 02:57:44 -0700 [thread overview]
Message-ID: <202102230957.11N9vi3x030633@freefriends.org> (raw)
In-Reply-To: <20210223092051.GA2248@polynum.com>
This is getting off topic ...
> > There was an interpreter for P-code and (I think later) a compiler
> > for the Vax. You'd have to port it to current architectures, and
> > compiling TeX would probably make TeX run more slowly than the C version.
> >
> > The Berkeley Pascals were some of the compilers used for "Software Tools
> > in Pascal".
>
> The Pascal version would probably be a bit slower. And it would be more
> an alternative to verify the code than a primary way, since in fact
> D.E.K. has not written the program in some Pascal but in Algol, a high
> level abstract description, the wizardry being in the data structures.
It's Pascal, but in literate form with WEB. I've read "Tex: The Program". :-)
> And, indeed, only the control flows are being translated from pseudo
> Pascal to C, the core---the data structures---being handled by ad-hoc
> code.
Could be, I'm not familiar with how web2c works.
> And for the architectures, like other compilers, the aim would be to
> convert to some intermediate language (perhaps assembly) and to borrow
> the back-ends.
I think the Pascal compiler used the PCC back end, but I no longer
remember for sure. If so, you might could hook it up to the revived PCC
project.
Although it sounds like a fun project, there are probably better
uses for your time. :-)
Arnold
------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/T476a1d7b83269775-Mc80e8615b718f628a8468339
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
next prev parent reply other threads:[~2021-02-23 9:58 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-21 22:31 Lyndon Nerenberg (VE7TFX/VE6BBM)
2021-02-21 23:01 ` Skip Tavakkolian
2021-02-21 23:19 ` Kurt H Maier
2021-02-22 1:24 ` Bakul Shah
2021-02-22 16:53 ` jas
2021-02-22 17:46 ` arnold
2021-02-22 18:28 ` tlaronde
2021-02-22 20:35 ` Lyndon Nerenberg (VE7TFX/VE6BBM)
2021-02-22 21:44 ` Charles Forsyth
2021-02-23 8:14 ` tlaronde
2021-02-23 8:58 ` arnold
2021-02-23 9:20 ` tlaronde
2021-02-23 9:57 ` arnold [this message]
2021-02-23 10:09 ` tlaronde
2021-02-23 7:57 ` tlaronde
2021-02-22 22:01 ` Bakul Shah
2021-02-22 22:43 ` Charles Forsyth
2021-02-22 23:09 ` Bakul Shah
2021-02-22 23:56 ` Charles Forsyth
2021-02-23 0:13 ` Bakul Shah
2021-02-23 0:03 ` Steffen Nurpmeso
2021-02-23 0:47 ` Lyndon Nerenberg (VE7TFX/VE6BBM)
2021-02-23 4:41 ` ori
2021-02-23 5:11 ` Lyndon Nerenberg (VE7TFX/VE6BBM)
2021-02-23 5:16 ` Bakul Shah
2021-02-24 13:48 ` Steffen Nurpmeso
2021-03-08 22:11 ` Jerome Ibanes
2021-02-24 0:33 Lyndon Nerenberg (VE7TFX/VE6BBM)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=202102230957.11N9vi3x030633@freefriends.org \
--to=arnold@skeeve.com \
--cc=9fans@9fans.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).