From: Luther Johnson <luther.johnson@makerlisp.com>
To: tuhs@tuhs.org
Subject: [TUHS] Re: Minimum Array Sizes in 16 bit C (was Maximum)
Date: Mon, 18 Nov 2024 11:56:26 -0700 [thread overview]
Message-ID: <b3b6b69e-02b3-cec1-1ac8-67554d8f8cee@makerlisp.com> (raw)
In-Reply-To: <20241118165229.7o735e6l3qsxmdqz@illithid>
I think both Ada and VHDL, started formally, and proceeded formally. I
don't have experience with either of them, but from the outside they
appear to be competent and rational.
I was mostly commenting on early C and Lisp (or Verilog is another
example, although I think Verilog has stayed pretty close to the
original versions), of being less formal, with more implicit defaults,
that just do pretty much what you would expect them to, which gives a
great deal of concise leverage. Some of that gets lost when the language
gets more formally "correct" or "complete", or you have to be more
verbose, or maybe just stay away from certain constructs altogether, if
you're not willing to qualify to the nth degree. And so, the later
variants become less useful (to me) than the original versions. It's
true that the first, informal versions of these languages, do require us
to understand, and buy in to, the mindset of the language inventors. But
with the later versions, you have to devour 1000 pages of detail from
the standards committee. Which gets us to working, productive code
faster ? Some prefer one path, some prefer another, but I like to learn
the point of view and approach of the original authors, to me it's like
reading a novel compared to reading an encyclopedia.
On 11/18/2024 09:52 AM, G. Branden Robinson wrote:
> At 2024-11-18T14:55:55-0000, Anton Shepelev wrote:
>> Yes, big money makes things strive not for excellence but for
>> accessibility and a low, if not negative, entry threshold.
> I think that's an overgeneralization.
>
> The Ada language, for example, drew much wariness and even criticism for
> being funded by the U.S. Department of Defense, probably the most
> profligate spender in the history of mankind,[1] and at the same time
> was condemned for being too hard a language to grasp (too "big") and too
> hard to write a compiler for.
>
> Further, I would argue that Ada was indeed an excellent language,
> certainly for its time and arguably still. But it was not easy to
> acquire by programmers who took an absolutely slovenly attitude toward
> data type discipline, a characterization that fits many pre-ANSI C
> programmers perfectly.
>
> Perhaps those who learn how to manage data types using C as their first
> language suffer irrevocable brain damage, and are fit subjects for pity
> and mockery. You won't find _that_ opinion in the Jargon File.
>
> Regards,
> Branden
>
> [1] https://www.npr.org/2021/05/19/997961646/the-pentagon-has-never-passed-an-audit-some-senators-want-to-change-that
next prev parent reply other threads:[~2024-11-18 18:56 UTC|newest]
Thread overview: 73+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-29 16:56 Douglas McIlroy
2024-09-29 20:29 ` Rob Pike
2024-09-29 21:13 ` Rik Farrow
2024-09-29 22:21 ` Rich Salz
2024-09-29 23:56 ` Rob Pike
2024-09-30 0:36 ` Larry McVoy
2024-09-30 0:55 ` Larry McVoy
2024-09-30 1:09 ` Luther Johnson
2024-09-30 1:37 ` Luther Johnson
2024-09-30 3:52 ` ron minnich
2024-10-01 12:43 ` arnold
2024-09-30 19:12 ` Steffen Nurpmeso
2024-09-30 20:03 ` Rich Salz
2024-09-30 21:15 ` Steffen Nurpmeso
2024-09-30 22:14 ` Bakul Shah via TUHS
2024-10-01 1:42 ` Alexis
2024-09-30 20:14 ` Rik Farrow
2024-09-30 22:00 ` Steffen Nurpmeso
2024-10-01 12:53 ` Dan Cross
2024-11-18 12:00 ` Anton Shepelev
2024-11-18 12:46 ` Luther Johnson
2024-11-18 14:05 ` Steve Nickolas
2024-11-18 15:00 ` Anton Shepelev
2024-11-23 22:29 ` Alexander Schreiber
2024-11-18 14:55 ` Anton Shepelev
2024-11-18 16:52 ` G. Branden Robinson
2024-11-18 17:00 ` Anton Shepelev
2024-11-18 18:56 ` Luther Johnson [this message]
2024-11-22 1:53 ` Dan Cross
2024-11-22 2:55 ` Luther Johnson
2024-09-29 21:24 ` Ralph Corderoy
-- strict thread matches above, loose matches on Subject: below --
2024-09-28 13:34 Douglas McIlroy
2024-09-28 16:58 ` G. Branden Robinson
2024-09-28 17:47 ` Luther Johnson
2024-09-28 17:52 ` Luther Johnson
2024-09-28 18:46 ` G. Branden Robinson
2024-09-28 22:08 ` Luther Johnson
2024-09-28 22:45 ` Luther Johnson
2024-09-28 22:50 ` Luther Johnson
2024-09-28 17:59 ` Bakul Shah via TUHS
2024-09-28 22:07 ` Douglas McIlroy
2024-09-28 23:05 ` Rob Pike
2024-09-28 23:30 ` Warner Losh
2024-09-29 10:06 ` Ralph Corderoy
2024-09-29 12:25 ` Warner Losh
2024-09-29 15:17 ` Ralph Corderoy
2024-09-30 12:15 ` Dan Cross
2024-09-28 18:01 ` G. Branden Robinson
2024-10-01 13:13 ` arnold
2024-10-01 13:32 ` Larry McVoy
2024-10-01 13:47 ` arnold
2024-10-01 14:01 ` Larry McVoy
2024-10-01 14:18 ` arnold
2024-10-01 14:25 ` Luther Johnson
2024-10-01 14:56 ` Dan Cross
2024-10-01 15:08 ` Stuff Received
2024-10-01 15:20 ` Larry McVoy
2024-10-01 15:38 ` Peter Weinberger (温博格) via TUHS
2024-10-01 15:50 ` ron minnich
2024-10-01 19:04 ` arnold
2024-10-01 16:49 ` Paul Winalski
2024-10-01 15:44 ` Bakul Shah via TUHS
2024-10-01 19:07 ` arnold
2024-10-01 20:34 ` Rik Farrow
2024-10-02 0:55 ` Steffen Nurpmeso
2024-10-02 5:49 ` arnold
2024-10-02 20:42 ` Dan Cross
2024-10-02 21:54 ` Marc Donner
2024-10-05 17:45 ` arnold
2024-10-06 12:20 ` Dan Cross
2024-10-01 16:40 ` Paul Winalski
2024-09-28 18:05 ` Larry McVoy
2024-09-30 15:49 ` Paul Winalski
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=b3b6b69e-02b3-cec1-1ac8-67554d8f8cee@makerlisp.com \
--to=luther.johnson@makerlisp.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).