From: grog@lemis.com (Greg 'groggy' Lehey)
Subject: [TUHS] Comments on "C"
Date: Mon, 29 Aug 2016 13:16:19 +1000 [thread overview]
Message-ID: <20160829031619.GB48170@eureka.lemis.com> (raw)
In-Reply-To: <CAOkr1zXkmRx7p1sET=a+1ffh=nSeh0G-vTDipiZPAjTbVVYQ_Q@mail.gmail.com>
On Sunday, 28 August 2016 at 18:37:21 -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.
Agreed, calling assembler is being deliberately a little silly. But
there is a connection: when I write C, I can envision what code is
going to be produced. With many languages, including C++, you can't
be so sure.
"A LISP programmer knows the value of everything and the cost of
nothing".
> So, are we just having fun over a few beers, or talking seriously? I
> like both!
I'll go for the beer.
Greg
--
Sent from my desktop computer.
Finger grog at FreeBSD.org for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed. If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: not available
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20160829/22dc6a9a/attachment.sig>
next prev parent reply other threads:[~2016-08-29 3:16 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
2016-08-29 3:16 ` Greg 'groggy' Lehey [this message]
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=20160829031619.GB48170@eureka.lemis.com \
--to=grog@lemis.com \
/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).