1. Re: euForth
- Posted by Peter Lawrence <peterl at NETLINK.COM.AU>
Aug 23, 1999
-
Last edited Aug 24, 1999
Clearly I need to clarify.
>When I think of increased portability, Forth isn't something that comes to
>mind - at least in the 'free' Forth realm. For example, it doesn't seem that
>Pocket Forth (for the Mac) is compatible with Win32Forth (for Windows). I
>haven't seen a BeForth.
"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. Once you install it, you're over the
hump - anything that's already in that Forth, or anyone trained in it, is
portable to that platform. "Portable" does not mean that one Forth is
compatible with another, unless specifically designed for it - it just means
you have a less impossible job starting from scratch.
>
>> BTW, Forth provides a virtual memory feature in
>> most implementations, which would also help.
>
>Welcome news to me - when I used to code in PolyForth, we were restricted to
>64K of static memory.
True - but the virtual memory feature does not mean all memory, just the
transparent use of mass storage (which is why I put on the word "feature").
Granted, that's less than many hardware supported virtual memories, but it's
more than enough to support sophisticated data structures. See what FOLDOC
has to say about Forth. PML.
GST+NPT=JOBS
I.e., a Goods and Services Tax (or almost any other broad based production
tax), with a Negative Payroll Tax, promotes employment.
See http://users.netlink.com.au/~peterl/publicns.html#AFRLET2 and the other
items on that page for some reasons why.
