From: Paul Winalski <paul.winalski@gmail.com>
To: Bakul Shah <bakul@iitbombay.org>
Cc: Alejandro Colomar <alx.manpages@gmail.com>, TUHS <tuhs@tuhs.org>
Subject: [TUHS] Re: [TUHS]: C dialects (was: I can't drive 55: "GOTO considered harmful" 55th anniversary)
Date: Mon, 13 Mar 2023 17:28:10 -0400 [thread overview]
Message-ID: <CABH=_VSvEYEU=0yEkah2OiLFV35x_dOdVNA7-JccvE8G-XkjPA@mail.gmail.com> (raw)
In-Reply-To: <10C77771-5232-4DBB-8685-ADC38C5E8350@iitbombay.org>
On 3/13/23, Bakul Shah <bakul@iitbombay.org> wrote:
>
> You can't drop features from a widely deployed language;
It has been done, with advanced warning of the deprecation, and over
several iterations of the standard so that there's advanced warning.
But it's rare and not advisable.
But you can create new subsets of the full standard.
> but while
> we are dreaming, what I'd like to see is a total *ban* on any and
> all optimizations. What you get is what you see!
>
Be careful what you wish for. That just won't fly on modern computer
architectures, with their many execution units and complicated memory
hierarchies. Not if you want anything resembling reasonable
performance that is also maintainable.
-Paul W.
next prev parent reply other threads:[~2023-03-13 21:28 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-10 11:37 [TUHS] Re: I can't drive 55: "GOTO considered harmful" 55th anniversary Noel Chiappa
2023-03-10 11:51 ` [TUHS] Conditions, AKA exceptions. (Was: I can't drive 55: "GOTO considered harmful" 55th anniversary) Ralph Corderoy
2023-03-10 15:54 ` [TUHS] Re: I can't drive 55: "GOTO considered harmful" 55th anniversary 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-13 12:43 ` [TUHS] [TUHS]: C dialects (was: I can't drive 55: "GOTO considered harmful" 55th anniversary) Alejandro Colomar
2023-03-13 12:46 ` [TUHS] " Dan Cross
2023-03-13 16:00 ` Paul Winalski
2023-03-13 19:00 ` Clem Cole
2023-03-13 19:09 ` Larry McVoy
2023-03-13 19:17 ` Steve Nickolas
2023-03-13 20:26 ` Dan Cross
2023-03-13 22:25 ` Alejandro Colomar (man-pages)
2023-03-13 19:24 ` [TUHS] Re: [TUHS]: C dialects Luther Johnson
2023-03-13 19:38 ` Luther Johnson
2023-03-14 19:48 ` John Cowan
2023-03-14 19:56 ` Joseph Holsten
2023-03-14 20:01 ` Luther Johnson
2023-03-13 20:48 ` [TUHS] Re: [TUHS]: C dialects (was: I can't drive 55: "GOTO considered harmful" 55th anniversary) Paul Winalski
2023-03-13 20:56 ` Bakul Shah
2023-03-14 1:06 ` Larry McVoy
2023-03-13 21:00 ` Paul Winalski
2023-03-13 21:07 ` Bakul Shah
2023-03-13 21:14 ` Dan Cross
2023-03-13 22:15 ` Dave Horsfall
2023-03-13 22:47 ` Dave Horsfall
2023-03-14 0:23 ` Dan Cross
2023-03-14 0:21 ` Dan Cross
2023-03-14 13:52 ` Chet Ramey
2023-03-14 1:27 ` Bakul Shah
2023-03-13 21:28 ` Paul Winalski [this message]
2023-03-14 10:04 ` [TUHS] C dialects Ralph Corderoy
2023-03-14 20:02 ` [TUHS] " John Cowan
2023-03-14 21:34 ` Thomas Paulsen
2023-03-14 0:38 ` [TUHS] Re: [TUHS]: C dialects (was: I can't drive 55: "GOTO considered harmful" 55th anniversary) John Cowan
2023-03-14 2:49 ` Theodore Ts'o
2023-03-14 3:06 ` G. Branden Robinson
2023-03-15 3:59 Noel Chiappa
2023-03-15 4:33 ` John Cowan
2023-03-16 22:50 ` Bakul Shah
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=_VSvEYEU=0yEkah2OiLFV35x_dOdVNA7-JccvE8G-XkjPA@mail.gmail.com' \
--to=paul.winalski@gmail.com \
--cc=alx.manpages@gmail.com \
--cc=bakul@iitbombay.org \
--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).