Path: utzoo!attcan!uunet!willett!ForthNet
From: ForthNet@willett.UUCP (ForthNet articles from GEnie)
Newsgroups: comp.lang.forth
Subject: for us beginners?  Help
Message-ID: <1299.UUL1.3#5129@willett.UUCP>
Date: 11 Jul 90 03:01:25 GMT
Organization: String, Scotch tape, and Paperclips.  (in Pgh, PA)
Lines: 36


 Date: 07-08-90 (11:26)              Number: 1666 (Echo)
   To: MATTHIAS GIWER                Refer#: 1665
 From: DOJUN YOSHIKAMI                 Read: NO
 Subj: LEARNING FORTH                Status: PUBLIC MESSAGE

 You might try reading some of the bulletin listings describing the
 various highlights and lowlights of the various forth packages in
 existance (it may be a bitty bit out of date by now).  A bit of warning
 on F-PC, it tends to be big!  F83 although older, is much smaller, and a
 bit more brodie like. I personally would recommend getting familiar iwth
 f83 and once you have the fundimentals down then get F-PC (which is A
 BIG package but has a lot of nifty stuff in it).  

 N.b. When the ANSI standard forth comes out, it would probably be a
 goood idea to become familiar with that.  There is still a goodly amount
 of interesting ideas going into it (not to mention some battles too!)

 dy ;-)

 (By the way, one of the best ways to learn forth is to write a forth
 interpreter of your own.  It's not too hard to do at all, and well worth
 the time.  You might want to snag a copy of kelly and spies's book 
 _Forth: A Text and Reference_; Either maryland book exch or reiter's
 technical books has a copy , or if neither does, Fig has it.  K&S
 cover the innards, particularly in the last chapter, in greater depth
 than brodie, and they give enough information to enable someone to code
 a forth interpreter from scratch, given they have enough energy to fight
 with an assembler in the early stages.)

 (Also by the way, make sure you understand what CREATE and DOES>
 accomplish.  Has to do with the subject of Binding times.  [let me know
 if this is confusing])
-----
This message came from GEnie via willett through a semi-automated process.
Report problems to: uunet!willett!dwp or willett!dwp@hobbes.cert.sei.cmu.edu