From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
Subject: [TUHS] Documentation on B language?
Date: Wed, 9 Mar 2016 07:34:47 -0500 (EST) [thread overview]
Message-ID: <20160309123447.ABE5D18C0AB@mercury.lcs.mit.edu> (raw)
> From: Brantley Coile
> But B's ++ and -- operators seem to be unique.
B seems to be like UNIX itself in this regard: a carefully selected set of
old ideas, along with a few new ones of equal value.
Noel
next reply other threads:[~2016-03-09 12:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-09 12:34 Noel Chiappa [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-03-09 21:34 Doug McIlroy
2016-03-09 21:43 ` John Cowan
2016-03-10 18:09 ` scj
2016-03-08 13:01 Doug McIlroy
2016-03-08 18:00 ` John Cowan
2016-03-08 19:10 ` Andru Luvisi
2016-03-08 19:43 ` John Cowan
2016-03-08 23:13 ` Tim Bradshaw
2016-03-09 11:09 ` Christian Neukirchen
2016-03-09 11:29 ` Brantley Coile
2016-03-07 0:57 Norman Wilson
2016-03-07 8:39 ` Angelo Papenhoff
2016-03-07 0:20 Warren Toomey
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=20160309123447.ABE5D18C0AB@mercury.lcs.mit.edu \
--to=jnc@mercury.lcs.mit.edu \
/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).