Path: utzoo!censor!geac!torsqnt!lethe!yunexus!ists!helios.physics.utoronto.ca!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!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: PYGMY Forth
Message-ID: <2237.UUL1.3#5129@willett.pgh.pa.us>
Date: 16 Jan 91 03:38:15 GMT
Organization: (n.) to be organized.  But that's not important right now.
Lines: 24

Category 1,  Topic 45
Message 64        Mon Jan 14, 1991
F.SERGEANT [Frank]           at 02:15 CST
 

 Oops - Regarding my recent posting of CODE words for SKIP & SCAN:  After
recently re-reading some comments ROEDY GREEN posted in December  '89 I am
inclined to rename SKIP to -LEADING= and rename SCAN to  -LEADING<>.  -LEADING
would eat leading spaces (just as -TRAILING eats  trailing spaces).

 For many years I have referred to bypassing spaces (or whatever) as  "eating
spaces" but until now I hadn't considered using "eat" in the  name of the
Forth word that does it.  I'm not inclined to use  EAT-TRAILING-SPACES and EAT-
LEADING-SPACES and  EAT-LEADING-CHARACTERS-THAT-ARE-NOT-EQUAL, etc but perhaps
I'll start  pronouncing the hyphen in -TRAILING and -LEADING as "eat" (thus  -
TRAILING would be pronounced "eat trailing") and have the best of both 
worlds.

 -- Frank
-----
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