Path: utzoo!mnetor!uunet!husc6!bbn!rochester!PT.CS.CMU.EDU!A.GP.CS.CMU.EDU!koopman
From: koopman@A.GP.CS.CMU.EDU (Philip Koopman)
Newsgroups: comp.lang.forth
Subject: Forth environments
Message-ID: <1208@PT.CS.CMU.EDU>
Date: 23 Mar 88 19:35:18 GMT
Sender: netnews@PT.CS.CMU.EDU
Organization: Carnegie-Mellon University, CS/RI
Lines: 31

I'm in the process of selecting a working environment
for use with the WISC CPU/32 processor.  The issues
of how to deal with a hardware-rich environment are
quite interesting, and different than the issues
that arose during Forth's creation in the tightly
constrained world of early micros.

Does anyone have comments on what kind of support environment is
appropriate for Forth programming on high-speed machines with
lots of memory and disk space?

Some of the issues I am struggling with include:

- screens vs. text files vs. blocked text files
- floating point as part of the system environment
- string handling
- whether a built-in heap manager is appropriate
- debugging support
- source code migration between 16- and 32-bit environments
- multi-tasking (pre-emptive)
- lessening the culture shock to UNIX/C programmers learning Forth


~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~  Phil Koopman             5551 Beacon St.             ~
~                           Pittsburgh, PA  15217       ~
~  koopman@faraday.ece.cmu.edu                          ~ 
~                                                       ~
~  I'm a PhD student at CMU, and I do some              ~
~  work for WISC Technologies.                          ~
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~