Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!uunet!willett!ForthNet
From: ForthNet@willett.UUCP (ForthNet articles from GEnie)
Newsgroups: comp.lang.forth
Subject: PYGMY FORTH
Message-ID: <106.UUL1.3#5129@willett.UUCP>
Date: 4 Jan 90 21:08:53 GMT
Organization: Latest Link in ForthNet Chain
Lines: 32


 Date: 12-28-89 (08:16)              Number: 1553 (Echo)
   To: R.BERKEY [ROBERT]             Refer#: 1494
 From: ZAFAR ESSAK                     Read: NO
 Subj: PYGMY FORTH                   Status: PUBLIC MESSAGE

 I have read the comments by you and Frank regarding LMOVE and MOVEL 
 naming conventions and the premise 

 RB> the Forth convention of having the least-changing object on top 

 However, from a human User/programmer point of view having the segment 
 followed by the offset seems the easiest to handle.  The representation 
 on the stack would automatically follow with the segment below the 
 offset. 

 As I have said in prior messages I prefer the naming as LMOVE & LFILL 
 and (now historically) LCMOVE LCMOVE> because the leading "L" serves to 
 identify a family of words which can be found quickly in a search. 
 Having two names based on position of parameters on the stack will 
 serve to confuse newcomers too, I'd bet. 

 As for the premise, I would think the top of the stack is the place 
 where one would want to see the parameters that are apt to change most. 
 I must be missing something. 
 ---
  * Via Qwikmail 2.01

 NET/Mail : British Columbia Forth Board - Burnaby BC - (604)434-5886   
-----
This message came from GEnie via willett through a semi-automated program.
Report problems to: 'uunet!willett!dwp' or 'willett!dwp@gateway.sei.cmu.edu'