Path: utzoo!news-server.csri.toronto.edu!cs.utexas.edu!uunet!stanford.edu!agate!ucbvax!PRIME-A.TEES-POLY.AC.UK!NER034
From: NER034@PRIME-A.TEES-POLY.AC.UK
Newsgroups: comp.lang.forth
Subject: Conditionals (with a bit of CS)
Message-ID: <9103081547.AA14541@ucbvax.Berkeley.EDU>
Date: 7 Mar 91 17:28:28 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Reply-To: NER034%PRIME-A.TEES-POLY.AC.UK@SCFVM.GSFC.NASA.GOV
Organization: The Internet
Lines: 26

I do not like the words .IF .ELSE and .THEN, personally I would go for
[IF], [ELSE], and [THEN], although I did put forward a proposal for
/IF( ), /ELSE, /ENDIF, /ELSEIF( ), witch I feal is significantly different
from any existing words.  Also the use of the parenthesis means that you
can define your flag normally.  Ie:

      TRUE CONSTANT DEBUG
      ...
      /IF( DEBUG ) ... /ENDIF


However, I would like to point out that we *DO* teach Forth to two of
our classes.  One of the first words we get them to define is .IF
This simply displays the text True or False.  However it is a vary useful
debugging word and a most logical name (according to the naming conventions).


Peter Knaggs
+-----------------------------+-----------------------------------------------+
! School of Comp. & Maths.,   !    Janet: NER034 @ uk.ac.tees-poly            !
! Teesside Polytechnic,       !   Bitnet: NER034 % tp.ac.uk @ UKACRL          !
! Middlesbrough,              ! Internet: NER034 % tp.ac.uk @ cunyvm.cuny.edu !
! Cleveland, England. TS1 3BA !     Uucp: NER034 % tpoly.ac.uk @ ukc.uucp     !
!-----------------------------+-----------------------------------------------!
! It is not enough to do the right thing; one must also do it the right way.  !
+-----------------------------------------------------------------------------+