hhg@alice.UUCP (Healfdene Goguen) (07/09/84)
I am planning to write a ``game'' that will teach people C by letting them write code to perform specific functions and then watch it execute on the screen. In order to do so, I need a C interpreter, something I've never heard of before and have no desire to write. Any pointers would be appreciated. Thanks in advance, Healfdene Goguen (ucbvax!alice!hhg)
DEPSTEIN@BBNG.ARPA (07/18/84)
Russ Lopez, Sesha Pratap, and Steve Kauffer at Harvard are currently working on a C interpreter that is currently fairly far along. You can contact them at: ARPA: lopez@harvard UUCP: decvax!wjh12!harvard!lopez Dave Epstein depstein@bbn-unix
kurt@fluke.UUCP (Kurt Guntheroth) (08/03/84)
<go ahead bug...make my day>
I would like to know how the c interpreter is going to handle #defines
efficiently. By efficiently i mean without
1. keeping 2 versions of each source line around and
2. without having to rescan each line and expand defines on the fly.
I once considered a c interpreter. It all worked except the preprocessor.
I eventually gave up the plan. Pascal interpreter? Sure. C interpreter?
probably not.
--
Kurt Guntheroth
John Fluke Mfg. Co., Inc.
{uw-beaver,decvax!microsof,ucbvax!lbl-csam,allegra,ssc-vax}!fluke!kurtsjh@PURDUE.ARPA (08/03/84)
From: Steve Holmes <sjh@PURDUE.ARPA> This is a vote in favor of the C Interpreter. sjh@purdue.arpa ----------
bsa@ncoast.UUCP (The WITNESS) (08/07/84)
The preprocessor would probably work exactly the way the current one does
(and in fact it may even use /lib/cpp): it would process the source into
a temporary file (file.i?) and then interpret that. cpp is fast enough to
be used as a "first pass" -- at least on our system. :-)
--
Brandon Allbery: decvax!cwruecmp{!atvax}!bsafw
6504 Chestnut Road, Independence, OH 44131
Witness, n. To watch and learn, joyously.