From: Lawrence Stewart <stewart@serissa.com>
To: Paul Winalski <paul.winalski@gmail.com>
Cc: tuhs@tuhs.org
Subject: [TUHS] Re: I can't drive 55: "GOTO considered harmful" 55th anniversary
Date: Fri, 10 Mar 2023 13:12:32 -0500 [thread overview]
Message-ID: <C4E0DFCA-F455-4F14-BEFE-B4F06E3C9936@serissa.com> (raw)
In-Reply-To: <CABH=_VSooO08bQ5sw9MKaE3DQ8rOHmBJpRuyafb5YsrYtifBZg@mail.gmail.com>
> On Mar 10, 2023, at 12:57 PM, Paul Winalski <paul.winalski@gmail.com> wrote:
>
>> Phil Budne wrote in
>> <202303101630.32AGU2OD008070@ultimate.com>:
>> |ron@ronnatalie.com wrote:
>> |
>> |I still remember the days when you could find C code written by PASCAL
>> |programmers,[.]
>
> Someone once observed that a skilled FORTRAN programmer could write
> FORTRAN in any programming language.
>
> -Paul W.
Once taught a programming languages class at Stanford, with assignments in Pascal, APL, LISP, and SNOBOL. The SNOBOL was to solve a crossword by pattern matching, given the grid and the solution words.
One kid had by far the fastest solution, in SNOBOL, but if you held up the listing at arm’s length you would swear it was FORTRAN.
I write my FORTRAN code in C these days.
-L
next prev parent reply other threads:[~2023-03-10 18:12 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 [this message]
2023-03-10 17:28 ` Clem Cole
2023-03-10 17:54 ` Paul Winalski
-- 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=C4E0DFCA-F455-4F14-BEFE-B4F06E3C9936@serissa.com \
--to=stewart@serissa.com \
--cc=paul.winalski@gmail.com \
--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).