Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!uakari.primate.wisc.edu!uflorida!beach.cis.ufl.edu!rs0
From: rs0@beach.cis.ufl.edu (Bob Slaughter)
Newsgroups: comp.lang.forth
Subject: Re: New Directions: Forth is not postfix
Message-ID: <22125@uflorida.cis.ufl.EDU>
Date: 6 Feb 90 01:35:30 GMT
References: <284.UUL1.3#5129@willett.UUCP> <2.71SW6xds13@ficc.uu.net> <51523@bbn.COM> <25C9CFEE.22487@maccs.dcss.mcmaster.ca> <6801@tekgvs.LABS.TEK.COM>
Sender: news@uflorida.cis.ufl.EDU
Reply-To: rs0@beach.cis.ufl.edu (Bob Slaughter)
Organization: UF CIS Department
Lines: 28

In article <6801@tekgvs.LABS.TEK.COM> toma@tekgvs.LABS.TEK.COM 
 (Tom Almy) writes:
>
>True, but you need a keyword after <false part> to resolve the forward
>jump around the false part when the condition is true.
>How about:
>	IF	-->  THEN	( as you propose )
>	THEN    -->  ENDIF	( as existed in figForth )
>	NOOP	-->  IF		( a dummy for clarity )
>so one gets:
>
>	IF  <condition>  THEN  <true part>  ELSE <false part>  ENDIF
        ^^^^^^^^^^^^^^^

This is the "non-prefix" part that some object to.  perhaps the
following would be good, allowing for the reference, while maintaining
the prefix orientation of Forth:

       <condition> IF-THEN <true part> ELSE <false part> ENDIF

Looks good to me.... (and avoids a no-op instruction).


--
*     Bob Slaughter                           *  This space for rent       *
*     InterNet#1:  rs0@beach.cis.ufl.edu      *    Call 1-800-FOR-RENT     *
*     InterNet#2:  Haldane@Pine.Circa.Ufl.Edu *   Model Railroading        *
*     Bitnet:      Haldane@UFPine             *          is Fun!!          *