Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!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: Conditionals !
Message-ID: <2589.UUL1.3#5129@willett.pgh.pa.us>
Date: 6 Apr 91 02:25:03 GMT
Organization: (n.) to be organized.  But that's not important right now.
Lines: 38


 Date: 04-01-91 (18:07)              Number: 1717 of 1724
   To: GARY SMITH                    Refer#: NONE
 From: CHRIS WATERS                    Read: NO
 Subj: CONDITIONALS !                Status: PUBLIC MESSAGE
 Conf: FORTH (58)                 Read Type: GENERAL (+)

 Reply to: eaker sunbelt.crd.ge.com (Charles E Eaker)
  Subject: Re: Conditionals !

 > However, thinking quickly, I miraculously turn this into an argument
 > for my
 >
 >      IF(   )ELSE(   )THEN

 If you're going to name it something like that, why not:

        (IF   (ELSE)   THEN)

 Which would allow you to use the standard names in minimal memory
 conditions, as long as you didn't have any nested comments or
 conditionals, simply by substituting the (admittedly non-standard)
 definitions for query-paren.

 Otherwise, I think it's too easy to accidentally leave out a space, and
 end up with "IF(" when what you really meant was "IF (".  That's my main
 objection to your proposal, which I otherwise think is very good.
 ---
 Tag 1.3 * If this had been a real emergency, you would be dust!

 PCRelay:IDCBBS -> #918
 4.10              IDC BBS ~ Alameda, CA ~ (415) 865-7115 ~ HST
 <<<>>>
-----
This message came from GEnie via willett.  You *cannot* reply to the author
using e-mail.  Please post a follow-up article, or use any instructions
the author may have included (USMail addresses, telephone #, etc.).
Report problems to: dwp@willett.pgh.pa.us _or_ uunet!willett!dwp