Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!uunet!willett!ForthNet
From: ForthNet@willett.UUCP (ForthNet articles from GEnie)
Newsgroups: comp.lang.forth
Subject: Basics of the Forth Language
Message-ID: <289.UUL1.3#5129@willett.UUCP>
Date: 19 Jan 90 23:18:36 GMT
Organization: Latest Link in ForthNet Chain (Pittsburgh, PA)
Lines: 31


 Date: 01-18-90 (04:33)              Number: 1563 (Echo)
   To: STEVE PALINCSAR               Refer#: 1549
 From: ARCHIE WARNOCK                  Read: 01-18-90 (13:15)
 Subj: BASICS OF THE FORTH LANGU     Status: PUBLIC MESSAGE

 SP>And at the same time, again following what Ray Duncan has said, it se
 SP>to be a smart thing these days to understand C -- since so much that 
 SP>appears in journals uses C to illustrate and explain.  So I've decide
 SP>to learn enough about C this year to be able to do that.  And so far,

 Me, too.  Actually, I had a text processing program to write and thought
 to myself, "Here's a good opportunity to use all those fancy string
 handling functions I've heard of, and to learn C to boot."  Actually,
 the string stuff in standard C is nowhere near as powerful or useful as
 George's package.  Sigh...  But the add-on libraries (CXL in particular)
 make a big difference.

 I'm not sure there's a whole lot more you can do with straight "vanilla"
 C than with an ANSI Forth system.  The power comes from the libraries.
 But lots of the C libraries will run under more than one compiler (at
 least by using conditional compilation), and we sure can't do that with
 our various Forth systems.  Again, George's strings package was the most
 portable thing I've ever seen, and it still needed some diddling to make
 it work.

 ---
  ~ EZ 1.24 ~ We don't know the ********* words!
-----
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'