From: Paul Winalski <paul.winalski@gmail.com>
To: Clem Cole <clemc@ccc.com>
Cc: Noel Chiappa <jnc@mercury.lcs.mit.edu>, tuhs@tuhs.org
Subject: [TUHS] Re: I can't drive 55: "GOTO considered harmful" 55th anniversary
Date: Fri, 10 Mar 2023 12:54:21 -0500 [thread overview]
Message-ID: <CABH=_VSwui_phS0UMZ9VtqE3f=cvaEM5G-OTA5m+d0WB6Qh4Qw@mail.gmail.com> (raw)
In-Reply-To: <CAC20D2NNLwA_Hv2OrgG9+xXTNoBCKVvnuYk5v0j8GzP8h3u4Dg@mail.gmail.com>
On 3/10/23, Clem Cole <clemc@ccc.com> wrote:
>
> Arnold's observation about trying to be small is reasonable,
> although contemporaries like BLISS did have support. So the comparison
> should really be to BCPL, PL/360, BLISS, *et al*. for features/size
> [although Wulf cheated, the BLISS-11 compiler was not self-hosting and
> needed a PDP-10 to run it].
For what it's worth, BLISS does not have a GOTO expression (BLISS
doesn't have statements per se--everything is an expression and can be
used as a value).
Wulf was studying code optimization. His BLISS-11 compiler, and its
successor at DEC, BLISS-16, implemented many advanced (for the day)
optimizations. In the programming environments at CMU and DEC it was
easier to suffer the mild inconvenience of cross-compilation than to
try to shoehorn the compiler into a 16-bit address space.
It certainly would be possible to implement a native BLISS compiler
for the PDP-11, but you'd have to sacrifice either some of the
optimizations or take a big hit in compilation speed.
-Paul W.
next prev parent reply other threads:[~2023-03-10 17:54 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-10 11:51 Noel Chiappa
2023-03-10 14:16 ` Ronald Natalie
2023-03-10 14:39 ` John Cowan
2023-03-10 16:30 ` Phil Budne
2023-03-10 17:50 ` Steffen Nurpmeso
2023-03-10 17:57 ` Paul Winalski
2023-03-10 18:12 ` Lawrence Stewart
2023-03-10 17:28 ` Clem Cole
2023-03-10 17:54 ` Paul Winalski [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-03-10 15:37 Noel Chiappa
2023-03-10 15:46 ` Larry McVoy
2023-03-10 16:04 ` Dan Cross
2023-03-10 18:55 ` Ron Natalie
2023-03-10 19:04 ` Dan Cross
2023-03-10 19:35 ` segaloco via TUHS
2023-03-10 11:37 Noel Chiappa
2023-03-10 15:54 ` Dan Cross
2023-03-12 7:39 ` Anthony Martin
2023-03-12 11:40 ` Dan Cross
2023-03-12 16:40 ` Paul Winalski
2023-03-13 3:25 ` John Cowan
2023-03-13 10:40 ` Alejandro Colomar (man-pages)
2023-03-13 12:19 ` Dan Cross
2023-03-09 23:01 [TUHS] " Steffen Nurpmeso
2023-03-09 23:18 ` [TUHS] " segaloco via TUHS
2023-03-09 23:21 ` Warner Losh
2023-03-09 23:31 ` Luther Johnson
2023-03-09 23:44 ` josh
2023-03-09 23:54 ` Warner Losh
2023-03-10 0:54 ` segaloco via TUHS
2023-03-10 1:08 ` Warner Losh
2023-03-10 10:08 ` Ralph Corderoy
2023-03-10 11:37 ` arnold
2023-03-10 11:56 ` Ralph Corderoy
2023-03-10 11:59 ` arnold
2023-03-10 12:11 ` Ralph Corderoy
2023-03-10 6:15 ` Dave Horsfall
2023-03-10 16:55 ` Steffen Nurpmeso
2023-03-10 17:02 ` Bakul Shah
2023-03-12 20:47 ` Dave Horsfall
2023-03-12 21:50 ` Warner Losh
2023-03-12 22:27 ` Steffen Nurpmeso
2023-03-10 1:31 ` Rich Morin
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='CABH=_VSwui_phS0UMZ9VtqE3f=cvaEM5G-OTA5m+d0WB6Qh4Qw@mail.gmail.com' \
--to=paul.winalski@gmail.com \
--cc=clemc@ccc.com \
--cc=jnc@mercury.lcs.mit.edu \
--cc=tuhs@tuhs.org \
/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).