The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: crossd@gmail.com (Dan Cross)
Subject: [TUHS] Happy birthday, Niklaus Wirth!
Date: Thu, 15 Feb 2018 19:51:14 -0500	[thread overview]
Message-ID: <CAEoi9W51rVASfMjMrK8RhPorWuPNmUa7YYg0Oy56pF6hVaV4Cg@mail.gmail.com> (raw)
In-Reply-To: <alpine.BSF.2.21.1802161058010.798@aneurin.horsfall.org>

On Thu, Feb 15, 2018 at 7:01 PM, Dave Horsfall <dave at horsfall.org> wrote:

> On Wed, 14 Feb 2018, Toby Thain wrote:
>
>> ALGOL, one of the most influential languages ever, with just about every
>>> programming language in use today tracing its roots to it.
>>>
>>
>> Worth mentioning one significant exception: the Lisp family.
>>
>
> I know about LISP (and even used it); it's on my history list.
>
> Actually, I can't think of any language that derived exclusively from LISP
> (other than Scheme etc)...  Oh, and EMACS :-)
>

There were (and are!) a whole bunch of dialects of Lisp: Common Lisp and
Scheme might be the best known, with Clojure a modern entrant. Arc is sort
of a thing. Most folks know about emacs Lisp. All of these derive from the
original Lisp.

But there were a whole slew of historical dialects descended from Lisp 1.5:
MacLisp, InterLisp, FranzLisp, Lisp Machine Lisp, the original variant
implemented by Symbolics before they adopted Common Lisp, Portable Standard
Lisp...and any number of others that were implemented as extension
languages: AutoLisp from AutoCAD, the aforementioned Emacs Lisp, the
pseudo-Lisp from Gosling's Emacs, and plenty of others. And how about
implementations? VAX Lisp, LispWorks, Allegro, etc. I think the thing is
that "Lisp" isn't a single language, but rather a family of languages that
all share common features (code is data, macros, etc, etc, etc) with lots
of variation between them (I understand that there was serious argument
about whether integer literals should be written in octal in Common Lisp,
as they were in MacLisp. Somehow common sense prevailed).

So, how's this relevant to Unix? Well, I'd like to know more about the
historical interplay between the Unix and Lisp communities. What about the
Lisp done at Berkeley on the VAX (Franz Lisp).

One of the things that strikes me about Lisp and Unix is the conceptual
similarity between image based languages (like Lisp) with a REPL and the
Unix "process as virtual machine" model with a shell and set of utilities.
An image is a sort of virtual machine and a REPL is a sort of shell;
callable functions in the REPL are sort of like discrete programs in the
$PATH. To a first order approximation, at any rate.

So anyway...some of you who were there, was there cross-pollination? Was
Franz Lisp a thing Unix people at Berkeley played with, or was it mostly
Lisp people who just happened to be using Unix because VAXen were expensive?

        - Dan C.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20180215/c5e5d828/attachment.html>


  reply	other threads:[~2018-02-16  0:51 UTC|newest]

Thread overview: 53+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-14 21:06 Dave Horsfall
2018-02-14 21:12 ` Clem Cole
2018-02-14 22:15   ` George Michaelson
2018-02-14 23:37   ` Dave Horsfall
2018-02-14 21:24 ` Toby Thain
2018-02-16  0:01   ` Dave Horsfall
2018-02-16  0:51     ` Dan Cross [this message]
2018-02-16  1:06       ` Clem cole
2018-02-16  3:10         ` Toby Thain
2018-02-16 13:36           ` Clem Cole
2018-02-16  1:18       ` Larry McVoy
2018-02-16  1:55         ` George Michaelson
2018-02-16  1:56         ` Lawrence Stewart
2018-02-16  2:38           ` Dan Cross
2018-02-16  2:41             ` Larry McVoy
2018-02-16  2:51               ` Dan Cross
2018-02-16  2:56                 ` George Michaelson
2018-02-16  2:51               ` [TUHS] Clueless programmers - was " Toby Thain
2018-02-16  2:55                 ` Larry McVoy
2018-02-16 10:26               ` [TUHS] " Tim Bradshaw
2018-02-16  1:25       ` Ian Zimmerman
2018-04-24  0:59         ` Ian Zimmerman
2018-04-24  3:26           ` Dave Horsfall
2018-04-24  4:31           ` Dan Stromberg
2018-04-24 13:42             ` Clem Cole
2018-02-16  2:09       ` Bakul Shah
2018-02-16  2:31         ` Toby Thain
2018-02-16 10:01         ` Tim Bradshaw
2018-02-16 12:10           ` Bakul Shah
2018-02-16 12:37             ` tfb
2018-02-16 13:34               ` Bakul Shah
2018-02-16 14:07                 ` Bakul Shah
2018-02-16 20:13                 ` tfb
2018-02-16  3:17       ` Dan Stromberg
2018-02-14 23:19 ` Greg 'groggy' Lehey
2018-02-14 23:31   ` Dave Horsfall
2018-02-15 17:32     ` Steffen Nurpmeso
2018-02-15 19:18       ` Ian Zimmerman
2018-02-15 20:56         ` Steffen Nurpmeso
2018-02-15 21:31         ` Jeremy C. Reed
2018-02-15  2:30 ` Nemo
2018-02-16  2:19 Noel Chiappa
2018-02-16  2:48 ` Larry McVoy
2018-02-16  4:19   ` Steve Nickolas
2018-02-16 11:27   ` Tim Bradshaw
2018-02-16 15:45     ` Nemo
     [not found] <mailman.1.1518746401.1018.tuhs@minnie.tuhs.org>
2018-02-16  2:40 ` Paul McJones
2018-02-16 13:42 Noel Chiappa
2018-02-16 21:02 ` Tim Bradshaw
     [not found] <mailman.22.1518790085.20342.tuhs@minnie.tuhs.org>
2018-02-16 17:40 ` Paul McJones
2018-02-16 19:24   ` Bakul Shah
2018-02-18 20:50 Norman Wilson
2018-02-19  0:28 ` Dave Horsfall

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=CAEoi9W51rVASfMjMrK8RhPorWuPNmUa7YYg0Oy56pF6hVaV4Cg@mail.gmail.com \
    --to=crossd@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).