The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Arrigo Triulzi <arrigo@alchemistowl.org>
To: Steve Johnson <scj@yaccman.com>
Cc: tuhs@tuhs.org
Subject: Re: [TUHS] Any Good dmr Anecdotes?
Date: Sat, 30 Jun 2018 13:44:30 +0200	[thread overview]
Message-ID: <5D272962-0063-4D28-B551-F381D3D10239@alchemistowl.org> (raw)
In-Reply-To: <3386fb80b5282f7bca0ccf34252182c2398232c1@webmail.yaccman.com>

My memories of dmr are limited to one encounter when he came to Italy, more precisely to the University of Milan, in the late 70s or early 80s (cannot remember exactly, there’s a picture in Peter Salus’ book though).

I was a child, had been introduced to Lisp as part of an experiment in teaching to primary school children but my dad, at the time teaching robotics in the nascent “Cybernetics” group of the Physics department, was starting me on C. 

As I was told this visitor was the R in the “K&R” book I felt I could finally ask “someone who knew” how printf() worked with a variable number of arguments. I was at best 10 and dmr patiently sat down and explained it to me in terms I could understand. I remember that he asked me if I understood pointers, I told him it was like putting a big arrow which you could move around, pointing to a house instead of actually using the house number and he smiled then taking the explanation on from there.

I wish I could have met him again in my life to thank him for that time he dedicated to a child to demystify printf().

Arrigo 



  reply	other threads:[~2018-06-30 22:16 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-29  7:53 Warren Toomey
2018-06-29 10:53 ` ches@Cheswick.com
2018-06-29 12:51   ` John P. Linderman
2018-06-30  0:50   ` Steve Johnson
2018-06-30 11:44     ` Arrigo Triulzi [this message]
2018-06-30 22:42       ` Arthur Krewat
2018-06-30 23:29         ` Arrigo Triulzi
2018-07-01  4:17           ` Larry McVoy
2018-07-01 11:42           ` ron
2018-07-01  5:29       ` Dave Horsfall
2018-07-01  8:28         ` Arrigo Triulzi
2018-07-01 11:34         ` ron
2018-07-09 16:30           ` Random832
2018-07-09 17:13             ` Clem Cole
2018-07-10  5:54               ` arnold
2018-07-10  6:09                 ` George Michaelson
2018-07-10  7:19                   ` arnold
2018-07-11  0:20                     ` Noel Hunt
2018-07-11  1:31                       ` Larry McVoy
2018-07-11  1:37                         ` George Michaelson
2018-07-11  1:37                         ` ron minnich
2018-07-11  3:12                           ` Larry McVoy
2018-07-11  3:34                         ` [TUHS] getopt (was " Bakul Shah
2018-07-13  9:08                       ` [TUHS] " ches@Cheswick.com
2018-07-13 14:10                         ` ron
2018-07-10 14:10                 ` Clem Cole
2018-07-03 17:34       ` Perry E. Metzger
2018-06-29 23:55 ` Dave Horsfall
2018-06-30  0:06   ` Greg 'groggy' Lehey
2018-06-30 14:20   ` John P. Linderman
2018-06-30  1:31 Larry McVoy
2018-06-30  1:45 ` Jon Forrest
2018-06-30 18:43   ` Steve Johnson
2018-07-01 16:35 Norman Wilson
2018-07-02 19:55 Paul Ruizendaal
2018-07-03  7:27 arnold
2018-07-18  9:42 Hendrik Jan Thomassen

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=5D272962-0063-4D28-B551-F381D3D10239@alchemistowl.org \
    --to=arrigo@alchemistowl.org \
    --cc=scj@yaccman.com \
    --cc=tuhs@tuhs.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).