From: luvisi@gmail.com (Andru Luvisi)
Subject: [TUHS] Documentation on B language?
Date: Tue, 8 Mar 2016 11:10:39 -0800 [thread overview]
Message-ID: <CAObyg6a0sPpxQ3ENDVj+hvOc_nU=bE-+5Hf8_9ftdoDMvKPZpg@mail.gmail.com> (raw)
In-Reply-To: <20160308180019.GD32247@mercury.ccil.org>
How were they spelled in Lisp 1.5? The manual lists add1 and sub1, but says
nothing about them modifying the value of a variable.
Sent from my phone. Please excuse my brevity.
On Mar 8, 2016 10:20 AM, "John Cowan" <cowan at mercury.ccil.org> wrote:
> Doug McIlroy scripsit:
>
> > Various aspects of the language were borrowed from PL/I, BCPL and Algol
> > 68. ++ and -- were novel operators. The reversal of Algol's assignment
> > operators (e.g. -= became =-) was eventually repealed in C.
>
> Algol 68, like Algol 60 and Pascal, used := (pronounced "becomes") for
> assignment, and the Algol 68 assignment operators were spelled :+=,
> :-=, etc. (pronounced "plus and becomes", "minus and becomes", etc.)
> Pre-increment operators were already known in Lisp 1.5 long before;
> they are now spelled incf and decf in Common Lisp.
>
> --
> John Cowan http://www.ccil.org/~cowan cowan at ccil.org
> If I have not seen as far as others, it is because giants were standing
> on my shoulders. --Hal Abelson
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20160308/598b2f1b/attachment.html>
next prev parent reply other threads:[~2016-03-08 19:10 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-08 13:01 Doug McIlroy
2016-03-08 18:00 ` John Cowan
2016-03-08 19:10 ` Andru Luvisi [this message]
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
-- 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-09 12:34 Noel Chiappa
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='CAObyg6a0sPpxQ3ENDVj+hvOc_nU=bE-+5Hf8_9ftdoDMvKPZpg@mail.gmail.com' \
--to=luvisi@gmail.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).