Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.1 6/24/83; site cadovax.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!allegra!mit-eddie!genrad!decvax!ittvax!dcdwest!sdcsvax!sdcrdcf!trwrba!cadovax!keithd
From: keithd@cadovax.UUCP (Keith Doyle)
Newsgroups: net.lang.forth
Subject: Speaking of Princeton
Message-ID: <128@cadovax.UUCP>
Date: Mon, 17-Sep-84 14:01:44 EDT
Article-I.D.: cadovax.128
Posted: Mon Sep 17 14:01:44 1984
Date-Received: Tue, 25-Sep-84 05:21:31 EDT
References: <3033@utah-cs.UUCP>
Organization: Contel Cado, Torrance, CA
Lines: 24


While the recent distribution of Princeton FORTH is still fresh
on our computers, I've been evolving a list of "how do you do it"'s
and was wondering if any of you out there have had similar problems/
successes:

1. How do I implement the equivalent of ?TERMINAL  ?

2. How can I implement my own control structures ( such as Charles Eaker's
   CASE statement ) without resorting to otherwise unknown assembly language?

3. Is it absolutely impossible (under UNIX or on a VAX) to implement the
   capability to re-save FORTH after an application has been compiled?
   (useful when writing canned applications invoked from the O.S. - there's
   no need for some users to know what language it was written in, and
   there's little need to wait for your editor to compile EVERY time you
   enter FORTH )

Except for these problems, I find Princeton FORTH an excellent version,
and FAST!.

Keith Doyle
{ucbvax,decvax}!trwrb!cadovax!keithd