home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.lang.forth
- Path: sparky!uunet!munnari.oz.au!bruce.cs.monash.edu.au!monu6!lindblat.cc.monash.edu.au!int452w
- From: int452w@lindblat.cc.monash.edu.au (Michael R. Geddes)
- Subject: Re: Sampler Forth
- Message-ID: <int452w.716514917@lindblat.cc.monash.edu.au>
- Sender: news@monu6.cc.monash.edu.au (Usenet system)
- Organization: Monash University, Melb., Australia.
- References: <15034@mindlink.bc.ca>
- Date: Mon, 14 Sep 1992 23:55:17 GMT
- Lines: 23
-
- Nick_Janow@mindlink.bc.ca (Nick Janow) writes:
-
- >> (a) Forth is NEVER going to be the fastest executing language.
-
- >That's not necessarily true. If Forth had the support C has, it would also
- >have nice systems with Forth CPUs, and I think for equal investment in hardware
- >and programming time, the application in Forth would run a lot faster.
-
- I agree with this, but also, I have been told that better hardware can often
- give you a reasonable increase in speed, but better algorithms give you an
- order of magnitude increase in speed. Forth is 'slow' on most systems
- because of the forth 'engine' that goes between machine code and forth code..
- Forth is 'fast' because you can code all the critical bits with an efficient
- algorithm (not just by putting it into assembler, you don't always get small
- critical bits.).
-
- Michael
-
- --
- Michael Geddes int452w@linblat.cc.monash.edu.au
- -----------------------------------------------------------------------
- A blink, I think, is the same as a wink, But a blink is a wink that grew.
- For a wink you blink with one eye, and a blink you wink with two.
-