Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!ub!uhura.cc.rochester.edu!rochester!pt.cs.cmu.edu!dsl.pitt.edu!pitt!willett!ForthNet
From: ForthNet@willett.pgh.pa.us (ForthNet articles from GEnie)
Newsgroups: comp.lang.forth
Subject: PYGMY Forth
Message-ID: <1777.UUL1.3#5129@willett.pgh.pa.us>
Date: 21 Sep 90 04:49:31 GMT
Organization: String, Scotch tape, and Paperclips.  (in Pgh, PA)
Lines: 86

Category 1,  Topic 45
Message 43        Wed Sep 19, 1990
F.SERGEANT [Frank]           at 23:06 CDT
 
 Pygmy Forth version 1.3

     Here it is.  I uploaded it last night, so it should be available  in the
near future as file #2202 in library #12 as PYGMY13.ZIP (67K).

[See previous ForthNet note, under subject "Files on-line".  -dwp]

     The previous versions were put in library #4, but for variety I  put this
version in the "Experimental Systems" library.

     Thanks to all who made suggestions.  I have acted on some and at  least
thought about the others.  For example, Steve Palincsar suggested  it was
confusing to have the documentation in block files with a .DOC  extension.  I
took that one step further.  I put all the source code in  a single (block)
file, PYGMY.SCR.  This now includes the kernel,  meta-compiler, editor,
assembler, *Starting Forth* examples, and  miscellaneous source code.  I put
all the documentation into the single  (text) file, PYGMY.TXT.  The file
PYGMY.COM, naturally, is the  executable file.  Pygmy Forth with kernel &
editor & assembler now fits  in a 14K file, however PYGMY.COM is 15,368 bytes
long.  The extra is  due to the inclusion of SEE, >SCR, >PRN, and words to
print source code  &/or shadows, 3 or 6 screens per page.  That was done to
make it easier  (as suggested by Chris Waters) for the new recipient of Pygmy
to print  out the source code.  I also have attempted to make CONDENSED
default  to put an Epson printer into 17 cpi mode (and have also included the 
code as before for Okidata printers).  I have included YOURFILE.SCR as  an
empty block file 8 screens long so the person new to Pygmy can get  started
right away with a place to put the code he writes, without  worrying about how
to MAKE or OPEN a file.

     The major changes have to do with file handling.  New file read  and
write words let you read arbitrary numbers of bytes either directly  or
sequentially.  All file accesses are via a unit# or via block  numbers (which
ultimately find the file based on its unit#).  This has  smoothed out and
regularized and added greater flexibility, in my  opinion.  The editor (and
BLOCK) will no longer let you access past the  end of file.  Holes (spread
open the file to insert blank blocks),  SETTLE (let the "heavy" screens settle
to the bottom), & CHOP (delete  the trailing blank screens at the end of a
file) make maintenance of  block files considerably easier.

     The question I might have on my mind, if I had a previous version  of
Pygmy, is whether I should bother downloading version 1.3.  I think  it
depends on what you want to do with it.  If you downloaded it as a  curiosity
to look at briefly and set aside, I'd say no, don't bother.   You've already
seen the main ideas.  If you downloaded it and wanted to  use it, but it
wasn't quite polished enough, I'd say 1.3 is worth a  look.  If you are
actually using a previous version, I'd say you  definitely should get 1.3.  If
you are looking for a Forth for the  IBM/clone world, and think F-PC is too
large for you, I think you could  be happy with Pygmy Forth.  It is easy to
download and easy to change  so it does things your way if you don't like how
I did it.

     I might be surprised, but I think 1.3 can stand as the final  version.  I
didn't feel that way about the previous versions.  I think  I've cleaned up
all the little things that had to be cleaned up.

     I have asked myself whether there is any point to Pygmy.  There 
certainly was for me personally.  I've had fun with it.  I've enjoyed  the
correspondence connected with it.  It is the Forth I use for  everything.  It
has grown large enough to be comfortable, and thereby  lost the attribute of
being tiny (I mean, 14K is pretty big for a  Forth, don't you think?).  I
think I could have been happy using plain  BBL (not Abundance) or Guy Kelly's
Forth. Compared to F83, they and  Pygmy have more comfortable editors.  I
think Pygmy's file handling  suits me better.  I think Pygmy's meta-
compilation is the simplest.   EForth is interesting and more easily portable,
but is pretty slow,  without the re-writing that would make it less portable.
It and Beta  Forth (the Russian Forth) and Zen (I think) aren't really usable
(I  think) without an editor and assembler.  F83 is certainly usable and 
deserves a lot of credit.  Abundance and F-PC are in an entirely  different
category, and not really usable by me at all, at this time.  So, all in all, I
think Pygmy has a good mix of speed, small size, file  handling, and comfort.
At least it is a mix that seems to suit me  better than the non-commercial
alternatives that I'm aware of.  One  advantage for me is that Pygmy is mine. 
For you it is just another  Forth competing for your time & attention &
download dollar.  It is  hard for me to look at it objectively!

     I don't know why, but I have the urge for people to use it and  enjoy it.


  -- Frank
-----
This message came from GEnie via willett through a semi-automated process.
Report problems to: dwp@willett.pgh.pa.us or uunet!willett!dwp