From: Bakul Shah <bakul@iitbombay.org>
To: Dan Cross <crossd@gmail.com>
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 18:27:04 -0700 [thread overview]
Message-ID: <B8E93F32-58D6-4B94-AA05-31CC8B4E3494@iitbombay.org> (raw)
In-Reply-To: <CAEoi9W7LiTHaUghE6Ts=YV8HiPqRDVX+u_1vsJdE8fcdf66_KA@mail.gmail.com>
On Mar 13, 2023, at 2:14 PM, Dan Cross <crossd@gmail.com> wrote:
>
> On Mon, Mar 13, 2023 at 5:08 PM Bakul Shah <bakul@iitbombay.org> wrote:
>> On Mar 13, 2023, at 2:00 PM, Paul Winalski <paul.winalski@gmail.com> wrote:
>>>
>>> On 3/13/23, Clem Cole <clemc@ccc.com> wrote:
>>>>
>>>> Frankly, I'd probably rather see ISO drop a bunch of the stuff they are now
>>>> requiring and fall back at least to K&R2 -- keep it simple.
>>>
>>> I agree. Every language has toxic features--things that seemed like
>>> good ideas at the time but turn out to have been mistakes when they're
>>> better understood. Every good programming shop has its rules
>>> concerning certain language features or practices that are not allowed
>>> in the code, usually for safety or maintainability reasons.
>>
>> You can't drop features from a widely deployed language; 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!
>
> Hey, they dropped `gets` from the standard library! Never say never.
It is easy to see that incorrect use of gets can lead to buffer
overflow problems so they "fixed" the easier downstream issue but
not the root cause! And that is the problem. Easy things are fixed
but nobody dares fix more fundamental problems.
And that was my point. All that standardization committees can do
is tweak a few things here and there.
next prev parent reply other threads:[~2023-03-14 1:27 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 [this message]
2023-03-13 21:28 ` Paul Winalski
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=B8E93F32-58D6-4B94-AA05-31CC8B4E3494@iitbombay.org \
--to=bakul@iitbombay.org \
--cc=alx.manpages@gmail.com \
--cc=crossd@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).