The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Luther Johnson <luther.johnson@makerlisp.com>
To: tuhs@tuhs.org
Subject: [TUHS] Re: Minimum Array Sizes in 16 bit C (was Maximum)
Date: Sun, 29 Sep 2024 18:37:10 -0700	[thread overview]
Message-ID: <d2d70aa8-0d7c-0a1e-9152-a4f8c50ae33d@makerlisp.com> (raw)
In-Reply-To: <e23f7d87-1d17-f484-74ad-53deb5cc278f@makerlisp.com>

'Go' is also a pretty C-like advanced C kind of thing. What do Go
writers think of it vs. C, for safety, reliability, clarity of
expression, etc. ?

On 09/29/2024 06:09 PM, Luther Johnson wrote:
> C# addresses some of the things being discussed here. I've used it, I
> don't care for it all that much, I prefer straight, not-at-all modern
> C, but I think there are probably a few dialects over the years
> (Objective C ?) that have addressed some of these desires for a
> "better C, but not C++". Do others here have comments on these
> inspired by C, kind of C-like, but with a few other computer science
> components, thrown into the language machine ?
>
> On 09/29/2024 05:36 PM, Larry McVoy wrote:
>> It doesn't have to be that way, C could be evolved, I built a very C
>> like language (to the point that one of my engineers, who hated the
>> new language on principle, fixed a bug in some diffs that flew by,
>> he thought he was fixing a bug in C).  No pointers, reference counted
>> garbage collection, pass by value or reference, switch values could be
>> anything, values, variables, regular expressions, etc.
>>
>> If I had infinite energy and money, I'd fund a gcc dialect of that C.
>> Alas, I don't.  But C is very fixable.
>>
>> On Mon, Sep 30, 2024 at 09:56:47AM +1000, Rob Pike wrote:
>>> I'm saying the exact opposite: they are unavoidably unsafe.
>>>
>>> -rob
>>>
>>>
>>> On Mon, Sep 30, 2024 at 8:21???AM Rich Salz <rich.salz@gmail.com>
>>> wrote:
>>>
>>>> C and C++ have become non-portable and dangerously insecure, as
>>>> well as
>>>>> often very surprising to the point that the US government arguing
>>>>> against
>>>>> using them.
>>>>>
>>>> I thought their main arguments were to use memory-safe languages.
>>>> Are you
>>>> saying the C language can be as safe s go, rust, etc., by language
>>>> design?
>>>> (I don't think you are, but the sentence I quoted kinda implies
>>>> that, at
>>>> least to me.)
>>>>
>


  reply	other threads:[~2024-09-30  1:37 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 [this message]
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
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=d2d70aa8-0d7c-0a1e-9152-a4f8c50ae33d@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).