The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: blake@mcbride.name (Blake McBride)
Subject: [TUHS] Comments on "C"
Date: Wed, 7 Sep 2016 20:19:14 -0500	[thread overview]
Message-ID: <CABwHSOtvOrs7rhWf+fv+8JN-EY1pKhMAWk7WbvqqZkE0hPXZew@mail.gmail.com> (raw)
In-Reply-To: <20160829004237.GC14366@mcvoy.com>

After about 30 years of C, there are only three things I would have liked
to see:

1.  Computed goto

2.  goto a line in a different function (more than setjmp/longjmp)

3.  Easy / standard access to registers

Computed goto's are good for interpreters.

Goto a line in a different function makes it easier to implement languages
with tail recursion without a trampoline.  (Or perhaps require C to support
tail recursion.)

Some sort of standard way to access registers makes it easier to implement
garbage collectors without resorting to assembler.

Blake McBride


On Sun, Aug 28, 2016 at 7:42 PM, Larry McVoy <lm at mcvoy.com> wrote:

> I'm with Marc.  I think the C syntax is really pleasant, and while I
> enjoyed
> writing PDP-11 assembler (by far my favorite out the ones I've done which
> include VAX, m68k, 32032, z80, sparc, some x86 but not much), I don't want
> go back to writing assembler unless I have to.  C is a pleasant language
> that easily compiles to assembler.
>
> I happen to like it so much I made a scripting language that looks very
> C like, with some perl pleasantness tossed in (without all the dollar
> signs).  Check it out at
>
> http://www.little-lang.org
>
> 100% open source, actively developed, yada, yada.
>
> On Sun, Aug 28, 2016 at 06:37:21PM -0600, Marc Rochkind wrote:
> > Yeah, OK, another one of those clever glib UNIXy aphorisms.
> >
> > But, as anyone who's actually programmed seriously in assembly language
> > knows, C is not assembler. It is a system programming language low enough
> > to be used for things that were once done in assembler, the most
> important
> > of which is an OS.
> >
> > So, for most of us, we no longer had to write in assembler. But that
> > doesn't mean C is assembler.
> >
> > So, are we just having fun over a few beers, or talking seriously? I like
> > both!
> >
> > --Marc Rochkind
> >
> > On Sun, Aug 28, 2016 at 12:21 PM, Dave Horsfall <dave at horsfall.org>
> wrote:
> >
> > > Seen on another list...  And I got quoted by Steve Bellovin :-)
> > >
> > > --
> > > Dave Horsfall DTM (VK2KFU)  "Those who don't understand security will
> > > suffer."
> > >
> > > ---------- Forwarded message ----------
> > > From: Kent Borg
> > > To: cryptography at metzdowd.com
> > > Subject: Re: [Cryptography]
> > >     "NSA-linked Cisco exploit poses bigger threat than previously
> thought"
> > >
> > > On 08/25/2016 06:06 PM, Steven M. Bellovin wrote:
> > >
> > > > I first heard more or less that line from Doug McIlroy himself; he
> > > > called C the best assembler language he'd ever used.
> > >
> > > Ancient fun-fact: Years ago there was an article in Byte magazine
> > > describing how a useful subset of C could be directly assembled into
> 68000
> > > code. Not compiled, assembled.
> > >
> > > C is a stunning assembly language. When those wild-eyed nerds at AT&T
> > > decided to write Unix not in assembly but in C (where was
> management!?),
> > > it was radical. But C was up to (down to?) the task, it was pioneering
> > > then and is still doing useful things decades later: From the fastest
> > > supercomputers to some pretty slim microcontrollers (plus a hell of a
> lot
> > > of Android devices) multitudes of computers run a Linux kernel compiled
> > > from the *same* C source code, with almost no assembly. Big-endian,
> > > little-endian: no matter. Different word lengths: no matter.
> > >
> > > That is one impressive cross-platform assembly language!
> > >
> > > Unfortunately, C is also a dangerous language that mortal programmers
> > > cannot reliably wield.
> > >
> > > -kb, the Kent who knows he is pressing his luck on a moderated
> > > cryptography mailing list, but C deserves a lot of respect, as it also
> > > deserves to be efficiently sent into a dignified retirement.
> > >
> > > _______________________________________________
> > > The cryptography mailing list
> > > cryptography at metzdowd.com
> > > http://www.metzdowd.com/mailman/listinfo/cryptography
> > >
> > >
>
> --
> ---
> Larry McVoy                  lm at mcvoy.com
> http://www.mcvoy.com/lm
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20160907/3f23527d/attachment.html>


  parent reply	other threads:[~2016-09-08  1:19 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-28 18:21 Dave Horsfall
2016-08-29  0:37 ` Marc Rochkind
2016-08-29  0:42   ` Larry McVoy
2016-08-29  1:54     ` Steve Nickolas
2016-09-08  1:19     ` Blake McBride [this message]
2016-08-29  3:16   ` Greg 'groggy' Lehey
2016-08-31 10:02     ` Tim Bradshaw
2016-08-31 12:59       ` John Cowan
2016-08-31 13:32         ` Ron Natalie
2016-08-31 14:37           ` John Cowan
2016-08-31 13:57   ` Brantley Coile
2016-09-01  9:17 Norman Wilson
2016-09-01 15:11 ` Clem Cole
2016-09-01 21:47 ` Tim Bradshaw
2016-09-02  0:11   ` Mary Ann Horton
2016-09-02  7:10     ` Steve Simon
2016-09-02 10:02       ` Steve Nickolas
2016-09-02 14:13       ` Random832
2016-09-02 21:23 ` Dave Horsfall
2016-09-04 17:03   ` scj
2016-09-05 13:07     ` Ron Natalie
2016-09-04 22:24   ` Nemo
2016-09-08 12:35 Doug McIlroy
2016-09-09 17:07 ` scj
2016-09-08 13:30 Noel Chiappa
2016-09-08 14:22 ` Tony Finch
2016-09-08 19:20   ` Ron Natalie
2016-09-08 22:06     ` Dave Horsfall
2016-09-09  3:02       ` Ronald Natalie
2016-09-09  6:06         ` Diomidis Spinellis
2016-09-09 21:15 ` Mary Ann Horton
2016-09-09  2:43 Doug 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=CABwHSOtvOrs7rhWf+fv+8JN-EY1pKhMAWk7WbvqqZkE0hPXZew@mail.gmail.com \
    --to=blake@mcbride.name \
    /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).