The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: scj@yaccman.com (scj@yaccman.com)
Subject: [TUHS] Questions regarding early Unix contributors
Date: Mon, 28 Sep 2015 09:55:47 -0700	[thread overview]
Message-ID: <4186b45fab3f28605b55591d7d97fd2f.squirrel@webmail.yaccman.com> (raw)
In-Reply-To: <alpine.BSF.2.11.1509290029030.70078@aneurin.horsfall.org>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1425 bytes --]

Lions' books on Unix and PCC were brilliant, although they had limited
circulation.  I confess that the PCC book was sometimes difficult reading,
as code that I cobbled together at 2AM was laid bare to the world.  I
remember a particularly tangled mess of 10 or so lines that John displayed
with the comment "advocates of structured programming might have preferred
to see:" followed by 3 short, elegant lines of code...



> On Sat, 26 Sep 2015, Armando Stettner wrote:
>
>> I also seem to recall him finish up the paper.  I was lucky in my
>> office
>> mates: I had John Lions and tjk.  Some place, I have a few pics of
>> USG’s
>> computer room.  I only recall RP04s however.  :(    aps.
>
> Dr. John Lions?  He was one of my Comp.Sci lecturers, and a brilliant
> bloke.
>
> It was a sad day when we lost him.
>
> I remember a USENET posting from long ago (yeah, I know), when someone
> swore that it was Lyons.  Someone then replied along the lines of "Well,
> I've just walked past his office door; it's Lions, as in the big cat."
>
> Of course, my memory could be a little flakey by now.
>
> --
> Dave Horsfall DTM (VK2KFU)  "Those who don't understand security will
> suffer."
>               Ph'nglui mglw'nafh Cthulhu R'lyeh wgah'nagl fhtagn!
> _______________________________________________
> TUHS mailing list
> TUHS at minnie.tuhs.org
> https://minnie.tuhs.org/mailman/listinfo/tuhs
>





  reply	other threads:[~2015-09-28 16:55 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-24 14:08 Clem Cole
2015-09-24 15:20 ` Mary Ann Horton
2015-09-24 17:08   ` Jeremy C. Reed
2015-09-24 17:28   ` Clem Cole
2015-09-26  2:37     ` Dave Horsfall
2015-09-26 23:22       ` Clement T. Cole
2015-09-27  6:52     ` Armando Stettner
2015-09-27 17:31       ` Clem Cole
2015-09-28 14:59       ` Dave Horsfall
2015-09-28 16:55         ` scj [this message]
2015-09-28 23:23           ` Greg 'groggy' Lehey
2015-10-01  2:09             ` Dave Horsfall
2015-10-01  3:52               ` Greg 'groggy' Lehey
2015-10-01  4:51                 ` Dave Horsfall
2015-09-29  6:57           ` arnold
2015-09-24 19:04 ` Jeremy C. Reed
2015-09-24 20:13   ` Clem Cole
2015-09-24 20:16     ` Clem Cole
2015-09-25  8:04   ` Diomidis Spinellis
2015-09-25 12:04   ` Clem Cole
  -- strict thread matches above, loose matches on Subject: below --
2015-10-07 13:26 Nelson H. F. Beebe
2015-10-02 18:00 Nelson H. F. Beebe
2015-10-01 16:37 Norman Wilson
2015-10-01 18:57 ` Dave Horsfall
2015-09-29  8:07 Hellwig Geisse
2015-09-29 15:35 ` scj
2015-10-01 18:00   ` Aharon Robbins
2015-09-25  2:14 Doug McIlroy
2015-09-24 17:12 Norman Wilson
2015-09-24 20:07 ` scj
2015-09-24 13:56 Noel Chiappa
2015-09-24 14:38 ` Lawrence Stewart
2015-09-24  9:27 Diomidis Spinellis
2015-09-24  9:52 ` Warren Toomey
2015-09-24 12:59 ` Clem Cole
2015-09-24 13:27 ` arnold
2015-09-24 16:12 ` John Cowan
2015-09-24 17:58 ` Jeremy C. Reed

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=4186b45fab3f28605b55591d7d97fd2f.squirrel@webmail.yaccman.com \
    --to=scj@yaccman.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).