Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!zaphod.mps.ohio-state.edu!uakari.primate.wisc.edu!aplcen!uunet!willett!ForthNet
From: ForthNet@willett.UUCP (ForthNet articles from GEnie)
Newsgroups: comp.lang.forth
Subject: ANS FORTH TECHNICAL COMMITTEE
Message-ID: <482.UUL1.3#5129@willett.UUCP>
Date: 16 Feb 90 02:35:58 GMT
Organization: Latest link in the ForthNet chain.  (Pgh, PA)
Lines: 21


 Date: 02-14-90 (00:42)              Number: 2903 (Echo)
   To: BOB LEE                       Refer#: 2897
 From: JERRY SHIFRIN                   Read: NO
 Subj: ANS FORTH                     Status: PUBLIC MESSAGE

 BL>One of the things I noticed in the Basis 10 Summary was a word I'd never
 BL>heard of: >COLROW  - what an ugly word!  I don't see why such a word is
 BL>necessary in a standard system.  Even if it must be included for some
 BL>reason or another, I wish it had a more readable name (POSITION maybe?).

 One of the problems the standards team runs into is the existing
 use of certain words, parhaps with slightly different meanings.
 >COLROW is implemented in most vendors' Forths, frequently named
 AT or GOTOXY. >COLROW is, at least, more explicit about its
 function and parameters.
 ---
  * QDeLuxe 1.10 #214s
-----
This message came from GEnie via willett through a semi-automated process.
Report problems to: 'uunet!willett!dwp' or 'willett!dwp@gateway.sei.cmu.edu'