Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!elroy.jpl.nasa.gov!sdd.hp.com!zaphod.mps.ohio-state.edu!unix.cis.pitt.edu!pitt!willett!ForthNet
From: ForthNet@willett.pgh.pa.us (ForthNet articles from GEnie)
Newsgroups: comp.lang.forth
Subject: ANS TC Magnet for Control, ABORT,QUIT..
Message-ID: <2261.UUL1.3#5129@willett.pgh.pa.us>
Date: 23 Jan 91 16:34:15 GMT
Organization: (n.) to be organized.  But that's not important right now.
Lines: 32

Category 10,  Topic 27
Message 35        Mon Jan 21, 1991
W.BADEN1 [Wil]               at 21:04 PST
 
I had thought that the rationale for WHILE had made it clear that the X3J14
definition is not something new, but how WHILE has been implemented in
polyForth and other industrial strength Forth's for many years.

Outside of that arena there had been a clamor for multiple WHILE's, with
varying exotic definitions, by persons who were not aware of the classical
Forth definition, now X3J14 definition.

The ability had been in hard-line, lean 'n' mean, Forth systems for a long,
long time.  X3J14 just acknowledged that fact, and recognized how WHILE would
continue to be implemented in that section of the Forth community.

This approach to control flow can be implemented in every system, while
xBranch, etc., would *never* be implemented by the hard-liners.  Indeed 72
percent of it has already been implemented in *every* system.

This approach lets everyone do what was wanted to be done with xBranch, but
could not be done.

It is as simple as it can be, but not simpler.

Procedamus in Pace.

-----
This message came from GEnie via willett.  You cannot Reply to the author
using email.  Please post a follow-up article, or use any instructions
the author may have included (USMail addresses, telephone #, whatever).
Report problems to: dwp@willett.pgh.pa.us or uunet!willett!dwp