Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!apple!ames!haven!uvaarpa!hudson!vivaldi.acc.Virginia.EDU!pmy
From: pmy@vivaldi.acc.Virginia.EDU (Pete Yadlowsky)
Newsgroups: comp.lang.forth
Subject: Re: Forth on the Amiga
Keywords: amiga, jforth, multiforth, mvp, a4th
Message-ID: <1715@hudson.acc.virginia.edu>
Date: 5 Jul 89 19:56:04 GMT
References: <20076@cup.portal.com> <12575@well.UUCP>
Sender: news@hudson.acc.virginia.edu
Reply-To: pmy@vivaldi.acc.Virginia.EDU.acc.Virginia.EDU (Pete Yadlowsky)
Organization: University of Virginia, Charlottesville
Lines: 31

In article <12575@well.UUCP> jax@well.UUCP (Jack J. Woehr) writes:
>In article <20076@cup.portal.com> Peter_Warren_Lee@cup.portal.com writes:
>	 ... stuff ...
>> Can anyone tell me how it stacks up in terms of speed compared to C or
>>assembly language? Also if anyone could suggest a good PD version to
>>learn FORTH on,I'd be grateful.

>	The best Amiga Forth, JForth, runs roughly at 80% the speed of
>a C application,

You may be right, I don't know, but I'm wondering how you come up with
this number. Doesn't it depend on the application, compiler, programmer's
skill, etc? For instance, when writing a JForth application, I tend to code
time-critical stuff in assembler. This is quite easy to do in JForth, and
I consider mixed Forth/asm to be a natural characteristic of the Forth
environment. Not so, C.

>while occupying somewhat less memory. I have a 5-k
>demo that opens a window and an autorequester then flakes off when
>you make a selection.

Qu'est-ce que c'est "flakes off"?

	a fellow JForther...



Peter M. Yadlowsky		| "Pay no attention to that man
Academic Computing Center	|	behind the curtain!"
University of Virginia		|
pmy@Virginia.EDU		|