The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Luther Johnson <luther@makerlisp.com>
To: John Cowan <cowan@ccil.org>
Cc: tuhs@tuhs.org
Subject: [TUHS] Re: [TUHS]: C dialects
Date: Tue, 14 Mar 2023 13:01:31 -0700	[thread overview]
Message-ID: <ec8eac92-1bec-e2de-5091-ba2bfea3e0e0@makerlisp.com> (raw)
In-Reply-To: <CAD2gp_QDw4Vn+QBgRpB1rrbejHoSND9ZT9pepVvB+Nddfqnp5w@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1712 bytes --]

I take your points. C gives a lot of freedom, but all things are not 
possible. I think what comes to mind for me is when I see the idea of 
trying to limit solutions to use only certain certain "design patterns", 
I usually would go in the direction of more freedom and less rules.

On 03/14/2023 12:48 PM, John Cowan wrote:
>
>
> On Mon, Mar 13, 2023 at 3:24 PM Luther Johnson <luther@makerlisp.com 
> <mailto:luther@makerlisp.com>> wrote:
>
>     I'm talking more about where the intent is to invest languages
>     with more "safety", "good practices", to bake certain preferences
>     into language features, so that writers no longer recognize these
>     as engineering choices, and the language as a means of expression
>     of any choice we might make, but that the language has built-in
>     "the right way" to do things, and if the program compiles and runs
>     at all, then it must be safe and working in certain respects.
>
>
> ORLY?  Do you reject C, then, because it does not support 
> self-modifying code or the ability to jump into the middle of a 
> procedure without going through the prologue?  These are baked-in 
> preferences, and if a C program compiles at all, you can be sure that 
> it does neither of these things, even if it would benefit your program 
> greatly if they were available.
>
>     Some people would say that's exactly what the new dialects bring
>     us, but I see too much artificial orthodoxy invented last week,
>     and too many declarations of the "one true way", in many of the
>     most recent languages, for my taste.
>
>
> Since you agree that it is a matter of taste, there can of course be 
> no disputing it.


[-- Attachment #2: Type: text/html, Size: 3721 bytes --]

  parent reply	other threads:[~2023-03-14 20:01 UTC|newest]

Thread overview: 42+ 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 [this message]
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
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  2:23 [TUHS] Re: [TUHS]: C dialects 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=ec8eac92-1bec-e2de-5091-ba2bfea3e0e0@makerlisp.com \
    --to=luther@makerlisp.com \
    --cc=cowan@ccil.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).