From: tfb@tfeb.org (Tim Bradshaw)
Subject: [TUHS] Documentation on B language?
Date: Tue, 8 Mar 2016 23:13:42 +0000 [thread overview]
Message-ID: <DD655F22-7463-4A56-B656-A66570FF6871@tfeb.org> (raw)
In-Reply-To: <20160308194348.GK32247@mercury.ccil.org>
> On 8 Mar 2016, at 19:43, John Cowan <cowan at mercury.ccil.org> wrote:
>
> They may not have been in the very earliest 1.5, but rather in one of the
> many 1.5 and 1.6 offshoots (which are documented mostly, if at all,
> in unsearchable PDFs), probably spelled inc and dec.
I am reasonably sure that they weren't in MACLISP (SETF is there) and fairly sure also they were not in InterLisp. They do appear in Lisp Machine Lisp, so I would suspect that this was how they found their way into CL.
However as soon as macros appeared (sometime shortly after Lisp 1.5 I think) things like this become so easy to implement (in the usual cases at least: fully-fledged ones are harder until SETF and its machinery exists, although that itself can be implemented with macrology) that probably they appeared many times in programs informally before this without anyone bothering to document them.
--tim
next prev parent reply other threads:[~2016-03-08 23:13 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
2016-03-08 19:43 ` John Cowan
2016-03-08 23:13 ` Tim Bradshaw [this message]
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=DD655F22-7463-4A56-B656-A66570FF6871@tfeb.org \
--to=tfb@tfeb.org \
/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).