Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!uunet!cs.utexas.edu!samsung!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: What's WRONG with Forth?
Message-ID: <2222.UUL1.3#5129@willett.pgh.pa.us>
Date: 12 Jan 91 03:55:55 GMT
Organization: (n.) to be organized.  But that's not important right now.
Lines: 28

Category 2,  Topic 9
Message 46        Thu Jan 10, 1991
B.RODRIGUEZ2 [Brad]          at 07:32 EST
 
Larry, my condolences; I learned Forth in Peoria, IL in the late '70s, so I
can sympathize.  Fortunately we now have GEnie.

I agree with your analysis (and the many replies) -- IF you design and
document your code properly, there is no problem.  I have pointed out to some
prospective Forthers that they had better damn well learn good programming
practice, out of self defense!  (A bonus: my experience with Forth has made me
a much better C programmer.)

I find myself factoring my code into many short words, with detailed stack
comments and a prose description for each word.  And I, like you, find that
module testing is easier in Forth than any other language I've used.  (I could
tell horror stories about testing a B- tree written in C.)

BTW, let me stick in a plug for the many Forth journals and conferences, any
of whom would be delighted to hear you write/talk about your vehicle
simulation in Forth.  "Success is a great deodorant."

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