Computer Old Farts Forum
 help / color / mirror / Atom feed
From: Brantley Coile <brantley@coraid.com>
To: Dan Cross <crossd@gmail.com>
Cc: COFF <coff@tuhs.org>
Subject: [COFF] Re: [TUHS] Sad news: Niklaus Wirth
Date: Wed, 3 Jan 2024 14:44:10 -0500	[thread overview]
Message-ID: <A43FF79C-A39F-442E-956F-9C51700FF768@coraid.com> (raw)
In-Reply-To: <CAEoi9W64uG+A96cCrTizD7AvuTiBoOQbLsq33w16JQ=yCVs+sA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 916 bytes --]

Sorry to hear. 

I knew him, I flew us across the US in a small single engine airplane, a rare blessing in a blessed life. We share the month of February as a birth date and would exchange emails every year. (Thompson is another in the February club.) 

Dennis once said that if you look at C and Pascal you might think there was information exchange, even though there was none. Oberon is Pascal++, ++.

Over the years C got more type-safe and Klaus' language got more flexible. Most of the objections to Pascal were gone after he designed Oberon.

Very sad.

Brantley 


> On Jan 3, 2024, at 2:35 PM, Dan Cross <crossd@gmail.com> wrote:
> 
> [TUHS as Bcc]
> 
> I just saw sad news from Bertrand Meyer. Apparently, Niklaus Wirth
> passed away on the 1st. :-(
> 
> I think it's fair to say that it is nearly impossible to overstate his
> influence on modern programming.
> 
>        - Dan C.

[-- Attachment #2.1: Type: text/html, Size: 1670 bytes --]

[-- Attachment #2.2: HOPL2009Jun09-2.jpg --]
[-- Type: image/jpeg, Size: 99296 bytes --]

      reply	other threads:[~2024-01-03 19:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-03 19:35 [COFF] " Dan Cross
2024-01-03 19:44 ` Brantley Coile [this message]

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=A43FF79C-A39F-442E-956F-9C51700FF768@coraid.com \
    --to=brantley@coraid.com \
    --cc=coff@tuhs.org \
    --cc=crossd@gmail.com \
    /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).