From: khm@sciops.net (Kurt H Maier)
Subject: [TUHS] Why Pascal is Not My Favorite Programming Language - Unearthed!
Date: Thu, 31 Aug 2017 18:51:19 -0700 [thread overview]
Message-ID: <20170901015119.GA71864@wopr> (raw)
In-Reply-To: <20170901012655.GH448@mcvoy.com>
On Thu, Aug 31, 2017 at 06:26:55PM -0700, Larry McVoy wrote:
>
> So I'd need to understand more to believe that claim. And for the record,
> what I'm going for is a new C that is still C enough to be useful but
> fixes the problems enough to be a new language. Someone asked about
> C++ and D, nope. Too far from C. I just want a C that fixes enough
> of the problems that it is more acceptable to modern programmers but
> is still C. Not sure if I'm explaining that well enough.
To "fix the problems" without losing functionality you need to pick a
new set of abstractions. If you pick a new set of abstractions you've
stopped being C. This is the gulf between C fans and the "modern"
language set. When you file off the sharp edges, you have fewer
accidents, but you have to solve some problems differently.
khm
next prev parent reply other threads:[~2017-09-01 1:51 UTC|newest]
Thread overview: 68+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-30 12:34 arnold
2017-08-30 14:13 ` Eric Wayte
2017-08-30 14:30 ` Michael Kjörling
2017-08-30 14:43 ` Eric Wayte
2017-08-30 17:10 ` Mutiny
2017-08-30 22:33 ` Michael Parson
2017-08-31 0:55 ` Nemo
2017-08-31 13:29 ` arnold
2017-08-31 18:24 ` Nemo
2017-09-03 0:56 ` Dave Horsfall
2017-09-03 12:07 ` arnold
2017-09-03 22:03 ` Dave Horsfall
2017-09-04 12:12 ` Steffen Nurpmeso
2017-08-31 1:13 ` Bakul Shah
2017-08-31 14:48 ` Larry McVoy
2017-08-31 15:26 ` Eric Wayte
2017-08-31 16:12 ` Warner Losh
2017-08-31 17:51 ` Larry McVoy
2017-08-31 18:40 ` Clem Cole
2017-08-31 19:25 ` Steffen Nurpmeso
2017-09-01 1:57 ` Nemo
2017-09-01 14:17 ` Steffen Nurpmeso
2017-09-01 14:28 ` Arthur Krewat
2017-09-01 14:48 ` William Cheswick
2017-09-01 15:15 ` Clem Cole
2017-09-01 15:47 ` Arthur Krewat
2017-09-01 16:21 ` Nevin Liber
2017-09-01 16:34 ` Dan Cross
2017-09-02 0:24 ` Dave Horsfall
2017-08-31 19:47 ` Toby Thain
2017-08-31 20:37 ` William Cheswick
2017-08-31 20:51 ` Clem Cole
2017-09-01 0:52 ` Bakul Shah
2017-08-31 21:46 ` Larry McVoy
2017-08-31 21:59 ` Arthur Krewat
2017-08-31 22:08 ` Larry McVoy
2017-09-01 1:11 ` Steve Johnson
2017-09-01 0:57 ` David Arnold
2017-09-01 1:22 ` Bakul Shah
2017-09-01 1:26 ` Larry McVoy
2017-09-01 1:51 ` Kurt H Maier [this message]
2017-09-01 2:22 ` Bakul Shah
2017-09-01 2:27 ` Larry McVoy
2017-09-01 2:58 ` Bakul Shah
2017-09-01 3:12 ` Dan Cross
2017-09-01 2:51 ` Dan Cross
2017-08-31 20:37 ` Clem Cole
2017-08-31 21:26 ` Toby Thain
2017-09-01 2:38 ` Dan Cross
2017-09-01 3:59 ` Toby Thain
2017-09-01 15:57 ` Dan Cross
2017-09-01 16:08 ` Toby Thain
2017-09-01 18:15 ` [TUHS] Future Languages (was Pascal not Favorite...) Steve Johnson
2017-09-01 18:43 ` ron minnich
2017-09-01 23:33 ` Chris Torek
2017-09-04 20:55 ` ron minnich
2017-09-01 20:42 ` Clem Cole
2017-09-04 20:44 ` Bakul Shah
2017-09-01 13:46 ` [TUHS] Why Pascal is Not My Favorite Programming Language - Unearthed! Clem Cole
2017-09-01 14:43 ` Toby Thain
2017-09-01 15:14 ` Clem Cole
2017-09-01 16:22 ` Dan Cross
2017-09-01 19:07 ` Toby Thain
2017-09-02 13:25 ` Dan Cross
2017-09-02 15:00 ` Toby Thain
2017-09-02 15:16 Diomidis Spinellis
2017-09-02 19:53 ` Toby Thain
2017-09-03 14:48 Norman Wilson
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=20170901015119.GA71864@wopr \
--to=khm@sciops.net \
/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).