From: wendellp@operamail.com (Wendell P)
Subject: [TUHS] Fwd: Interactive C Environments
Date: Wed, 06 Jul 2016 14:30:11 -0700 [thread overview]
Message-ID: <1467840611.1583090.658884417.3CFE9DEC@webmail.messagingengine.com> (raw)
In-Reply-To: <CAC20D2OeqWQoFEXhZUv6Q3=bc9nOzZG+kPVfVg5Z9DfhfSk-9w@mail.gmail.com>
Thanks for reminding me about that one, Clem. I think I even have
Darnell's book somewhere.
I haven't decided what to do about batch interpreters for C. They aren't
interactive but there is still some overlap of concerns. I'll probably
post a list of them somewhere. I also have Al Stevens' Quincy,
Przemyslaw Podsiadly's SeeR, and Herb Schildt's from "Building your own
C interpreter."
On Wed, Jul 6, 2016, at 12:22 PM, Clem Cole wrote:
> From the The Unix Historical Society mailing list, I discovered your
> historical interest in C interpreters. It looks like you are missing at
> least one, so I though I would introduce you all.
>
> Paul/Wendell meet Peter Darnell -- Pete wrote one an early C interpreter
> for his C programming book. I'll leave it to you folks to discuss what
> he
> did, its current status et al.
>
> Best Wishes,
>
> Clem Cole (old time UNIX and C guy)
>
>
>
> ---------- Forwarded message ----------
> From: Warren Toomey <wkt at tuhs.org>
> Date: Sat, Jul 2, 2016 at 6:01 PM
> Subject: [TUHS] Interactive C Environments
> To: tuhs at tuhs.org
>
>
> All, I've been asked by Wendell to forward this query about C
> interpreters to the mailing list for him.
>
> ----- Forwarded message from Wendell P <wendellp at operamail.com> -----
>
> I have a project at softwarepreservation.org to collect work done,
> mostly in the 1970s and 80s, on C interpreters.
>
> http://www.softwarepreservation.org/projects/interactive_c
>
> One thing I'm trying to track down is Cin, the C interpreter in UNIX
> v10. I found the man page online and the tutorial in v2 of the Saunders
> book, but that's it. Can anyone help me to find files or docs?
>
> BTW, if you have anything related to the other commercial systems
> listed, I'd like to hear. I've found that in nearly all cases, the
> original developers did not keep the files or papers.
>
> Cheers,
> Wendell
>
> ----- End forwarded message -----
--
http://www.fastmail.com - The professional email service
next prev parent reply other threads:[~2016-07-06 21:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-02 22:01 [TUHS] " Warren Toomey
[not found] ` <CAC20D2OeqWQoFEXhZUv6Q3=bc9nOzZG+kPVfVg5Z9DfhfSk-9w@mail.gmail.com>
2016-07-06 21:30 ` Wendell P [this message]
2016-07-06 21:43 ` [TUHS] Fwd: " A. P. Garcia
2016-07-09 2:53 ` [TUHS] " Win Treese
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=1467840611.1583090.658884417.3CFE9DEC@webmail.messagingengine.com \
--to=wendellp@operamail.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).