From:	Hans-Bernhard Broeker <broeker AT physik DOT rwth-aachen DOT de>
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: interpreting C ???
Date:	7 Mar 2001 12:03:30 GMT
Organization:	Aachen University of Technology (RWTH)
Lines:	27
Message-ID:	<98582i$dk9$1@nets3.rz.RWTH-Aachen.DE>
References:	<3A9D5EC9 DOT CE9D100C AT t-online DOT de> <983hcu$d4p$1 AT nets3 DOT rz DOT RWTH-Aachen DOT DE> <slrn9aajjt DOT 7mh DOT rpolzer AT rebounce DOT rpolzer-lx>
NNTP-Posting-Host:	acp3bf.physik.rwth-aachen.de
X-Trace:	nets3.rz.RWTH-Aachen.DE 983966610 13961 137.226.32.75 (7 Mar 2001 12:03:30 GMT)
X-Complaints-To:	abuse AT rwth-aachen DOT de
NNTP-Posting-Date:	7 Mar 2001 12:03:30 GMT
Originator:	broeker@
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com

Rudolf Polzer <rpolzer AT web DOT de> wrote:
> Hans-Bernhard Broeker <broeker AT physik DOT rwth-aachen DOT de> schrieb Folgendes:
[...]
>> By nature, C is not a very interpreter-friendly language. Elements
>> that cause this include the preprocessor, complicated data structures,
>                               ^^^^^^^^^^^^
> maybe...
>                                             ^^^^^^^^^^^^^^^^^^^^^^^^^^^
> QBasic, an _OLD_ BASIC interpreter, supports them.

Up to and including pointers, dynamic memory allocation, 11 basic
numeric datatypes, and unions? I don't recall my short time of QBasic
coding very well, but I don't think it had all those.

>> I'd recommend a text book on compiler construction and the
>> comp.compilers newsgroup (they deal with interpreters, too, despite of
>> the name).

> Why a C interpreter? 

I don't know. The OP didn't provide any rationale.

But the real question would be: if an interpreter, why one for C, of
all all possible languages?
-- 
Hans-Bernhard Broeker (broeker AT physik DOT rwth-aachen DOT de)
Even if all the snow were burnt, ashes would remain.

- Raw text -