OpenEuphoria

Re: euForth

• Posted by "Cuny, David" <David.Cuny at DSS.CA.GOV> Aug 23, 1999
• 464 views

Peter Lawrence wrote:

> "Portability", in this sense, does NOT mean someone
> already laid out a red carpet for you. It means you
> have a go-anywhere toolkit available, which can be
> installed in a very few man-weeks.

So basically, it's portable except for the stuff that's not. 

> True - but the virtual memory feature does not mean
> all memory, just the transparent use of mass storage...

So you're still stuck with a 64K memory model without dynamic *real* memory
allocation. It seems to me that with dynamic structure allocation (and
reallocations), lookups to convert handles to addresses, and simply reading
and manipulating structures you'll be thrashing the disk.

Disk access is going to be a constant bottleneck - no matter how much you
tune the code, the speed will still be throttled by the rate of disk access.

> See what FOLDOC has to say about Forth.

   "Some Forth systems support virtual memory without specific hardware
   support like MMUs. However, Forth virtual memory is usually only a sort
   of extended data space and does not usually support executable code."

-- David Cuny