From: Warner Losh <imp@bsdimp.com>
To: John Cowan <cowan@ccil.org>
Cc: TUHS main list <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] roff(7) [ and other related stuff ]
Date: Sat, 1 Jan 2022 20:30:05 -0700 [thread overview]
Message-ID: <CANCZdfoER8e6hcMDraR7xCC5pPi-DyijWG5vT-2Heu4OWCdb0A@mail.gmail.com> (raw)
In-Reply-To: <CAD2gp_Swoy08ifEBuYGx+=6+fUp1+WgVid1Di+j94SyYDVNiKQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1249 bytes --]
On Sat, Jan 1, 2022, 8:05 PM John Cowan <cowan@ccil.org> wrote:
>
>
> On Sat, Jan 1, 2022 at 8:20 PM Larry McVoy <lm@mcvoy.com> wrote:
>
>
>> I'm almost speechless. My progression was Basic, Pascal, C (and later
>> Fortran, Lisp, no Cobol, I did an Ada Compiler so Ada I guess). Then
>> on to awk, perl, tcl, I tried to like C++ but couldn't, tried to like
>> Rust, Go, D, and couldn't.
>>
>> If you think any of those other languages remotely approach the elegance
>> of C, I just don't know what to say.
>>
>
> Elegance? C? I think not. Lisp, _that's_ elegant.
>
LISP is all about the syntax. It was completely opaque until that moment
when prefix notation clicked and it was all clear...
C is beautiful, you look at the code and you can see what the hardware
>> will be doing but it isn't assembler.
>
>
> Not really. You see what the hardware would be doing if it were a PDP-11.
> That's not the same thing at all.
>
Read the CHERI papers to find out that C is just doing approximately what
you want / think is going on... unless you've been burned by UB that you
thought you knew... At least compilers are getting stricter about flagging
it, much to the annoyance of anybody with a code base more than a couple
years old...
Warner
>
[-- Attachment #2: Type: text/html, Size: 2906 bytes --]
next prev parent reply other threads:[~2022-01-02 3:30 UTC|newest]
Thread overview: 104+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-31 15:47 [TUHS] roff(7) Douglas McIlroy
2021-12-31 23:07 ` George Michaelson
2021-12-31 23:40 ` Larry McVoy
2022-01-01 0:56 ` [TUHS] TeX and groff (was: roff(7)) Greg 'groggy' Lehey
2022-01-01 3:15 ` Larry McVoy
2022-01-10 19:00 ` Blake McBride
2022-01-10 20:21 ` Jon Forrest
2022-01-11 22:48 ` Blake McBride
2022-01-11 23:18 ` Larry McVoy
2022-01-12 1:19 ` Dave Horsfall
2022-01-12 1:46 ` Blake McBride
2022-01-12 2:12 ` Bakul Shah
2022-01-12 15:49 ` Larry McVoy
2022-01-12 16:22 ` Adam Thornton
2022-01-12 0:06 ` Jon Steinhart
2022-01-12 1:48 ` Blake McBride
2022-01-12 0:29 ` Nemo Nusquam
2022-01-12 1:53 ` Blake McBride
[not found] ` <E3CC4B8A-4E88-4339-A4D3-4ED26BA80620@gmail.com>
2022-01-12 0:44 ` Jon Forrest
2022-01-12 2:00 ` Blake McBride
2022-01-12 2:10 ` David Arnold
2022-01-12 2:26 ` Adam Thornton
2022-01-12 19:54 ` John Cowan
2022-01-13 10:13 ` Thomas Paulsen
2022-01-13 20:00 ` John Cowan
2022-01-10 20:33 ` Larry McVoy
2022-01-10 20:37 ` Richard Salz
2022-01-10 21:04 ` Dan Cross
2022-01-10 21:48 ` Nemo Nusquam
2022-01-11 2:25 ` Lyndon Nerenberg (VE7TFX/VE6BBM)
2022-01-11 2:47 ` Larry McVoy
2022-01-22 2:34 ` [TUHS] troff environments, traps, and diversions (was: TeX and groff) Branden Robinson
2022-01-22 16:02 ` Douglas McIlroy
2022-01-23 19:45 ` Jon Steinhart
2022-01-23 22:26 ` Jon Steinhart
2022-01-11 1:52 ` [TUHS] Recognizing TeX (was: TeX and groff (was: roff(7))) Greg 'groggy' Lehey
2022-01-12 1:19 ` [TUHS] TeX and groff (was: roff(7)) Mary Ann Horton
2022-01-12 2:03 ` Blake McBride
2022-01-12 2:10 ` Bakul Shah
2022-01-12 3:44 ` Dan Cross
2022-01-12 16:48 ` Steffen Nurpmeso
2022-01-10 20:46 ` Steffen Nurpmeso
2022-01-11 1:59 ` [TUHS] Demise of " Greg 'groggy' Lehey
2022-01-11 2:13 ` Lyndon Nerenberg (VE7TFX/VE6BBM)
2022-01-11 2:42 ` Larry McVoy
2022-01-11 5:12 ` Greg 'groggy' Lehey
2022-01-11 5:59 ` John Labovitz
2022-01-11 8:57 ` arnold
2022-01-11 20:15 ` Jon Steinhart
2022-01-11 20:22 ` Larry McVoy
2022-01-11 20:26 ` Jon Steinhart
2022-01-11 20:36 ` Larry McVoy
2022-01-11 20:41 ` Jon Steinhart
2022-01-11 20:49 ` Larry McVoy
2022-01-11 21:03 ` Jon Steinhart
2022-01-11 8:50 ` arnold
2022-01-11 14:00 ` Larry McVoy
2022-01-12 23:22 ` [TUHS] troff or groff? (was: Demise of TeX and groff (was: roff(7))) Greg 'groggy' Lehey
2022-01-12 23:29 ` Greg 'groggy' Lehey
2022-01-12 23:32 ` Larry McVoy
2022-01-11 15:47 ` [TUHS] Demise of TeX and groff (was: roff(7)) Clem Cole
2022-01-11 16:55 ` Richard Salz
2022-01-11 18:49 ` Clem Cole
2022-01-11 19:20 ` John Cowan
2022-01-11 20:06 ` Clem Cole
2022-01-11 23:57 ` Warner Losh
2022-01-12 0:03 ` Warner Losh
2022-01-12 8:54 ` arnold
2022-01-12 15:17 ` Clem Cole
2022-01-12 16:33 ` Dan Cross
2022-01-12 18:06 ` [TUHS] *roff history as told to GNU G. Branden Robinson
2022-01-12 18:34 ` Dan Halbert
2022-01-12 22:48 ` Clem Cole
2022-01-12 23:27 ` Charles H. Sauer
2022-01-13 0:35 ` Adam Thornton
2022-01-12 20:01 ` Dan Cross
2022-01-12 22:32 ` Clem Cole
2022-01-13 2:38 ` John Labovitz
2022-01-13 7:42 ` Lars Brinkhoff
2022-01-13 13:47 ` John Labovitz
2022-01-12 8:48 ` [TUHS] Demise of TeX and groff (was: roff(7)) arnold
2022-01-12 15:51 ` Larry McVoy
2022-01-12 15:57 ` Clem Cole
2022-01-12 15:56 ` Clem Cole
2022-01-11 3:22 ` Adam Thornton
2022-01-12 0:32 ` Nemo Nusquam
2022-01-01 20:00 ` [TUHS] roff(7) [ and other related stuff ] Jon Steinhart
2022-01-02 0:12 ` Larry McVoy
2022-01-02 1:04 ` John Cowan
2022-01-02 1:20 ` Larry McVoy
2022-01-02 1:47 ` Steve Nickolas
2022-01-02 2:12 ` Larry McVoy
2022-01-02 3:56 ` Jon Steinhart
2022-01-02 1:48 ` Jon Steinhart
2022-01-02 3:04 ` John Cowan
2022-01-02 3:30 ` Warner Losh [this message]
2022-01-01 1:11 ` [TUHS] roff(7) Phil Budne
2022-01-01 1:17 ` Chris Torek
2022-01-01 3:06 ` Larry McVoy
2022-01-01 3:34 ` George Michaelson
2022-01-05 21:15 ` Tony Finch
2022-01-02 4:02 [TUHS] roff(7) [ and other related stuff ] Noel Chiappa
2022-01-02 10:46 ` markus schnalke
2022-01-02 4:10 Douglas McIlroy
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=CANCZdfoER8e6hcMDraR7xCC5pPi-DyijWG5vT-2Heu4OWCdb0A@mail.gmail.com \
--to=imp@bsdimp.com \
--cc=cowan@ccil.org \
--cc=tuhs@minnie.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).