Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!mailrus!ames!pacbell!well!jax
From: jax@well.UUCP (Jack J. Woehr)
Newsgroups: comp.lang.forth
Subject: Re: FORTH and memory
Summary: What connection DO ... LOOP <==> the interpreter?
Keywords: DO, LOOP, interpreter, aardvarks
Message-ID: <6700@well.UUCP>
Date: 2 Aug 88 07:04:32 GMT
References: <ZMLEB@SCFVM> <8807211846.AA27919@jade.berkeley.edu> <9428@dartvax.Dartmouth.EDU> <2353@pt.cs.cmu.edu> <1530@crete.cs.glasgow.ac.uk> <132@kolvi.hut.fi> <17597@glacier.STANFORD.EDU>
Reply-To: jax@well.UUCP (Jack J. Woehr)
Organization: Whole Earth 'Lectronic Link, Sausalito, CA
Lines: 16

In article <17597@glacier.STANFORD.EDU> jbn@glacier.UUCP (John B. Nagle) writes:
>
>      I have used the New Micros Forth on the M68HC11.  It is painfully
>slow.  10000 0 DO LOOP takes about one full second.  Interpreters are
>slow, there's no getting around it.
>
>

	Fancy meeting you here, John! Anyway, good buddy, what does the
interpreter have to do with the execution speed of 10000 0 DO LOOP unless
you are saying that serial communication with the 68HaCk takes a full
second? The interpreter is not invoked in a DO ... LOOP in Forth.

	Jack "I wanted to buy 64 Novixen but one Super8 was cheaper" Woehr
	jax@well jax@chariot JAX on GEnie
	: SMARTER ( ---) 10000 0 DO READ-TING :-) LOOP ;