Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!pacific.mps.ohio-state.edu!linac!att!ucbvax!MITCH.ENG.SUN.COM!wmb From: wmb@MITCH.ENG.SUN.COM (Mitch Bradley) Newsgroups: comp.lang.forth Subject: Broken cmForth Message-ID: <9102211446.AA20543@ucbvax.Berkeley.EDU> Date: 20 Feb 91 19:14:13 GMT Sender: daemon@ucbvax.BERKELEY.EDU Reply-To: Mitch Bradley Organization: The Internet Lines: 22 > > I find it amusing that Chuck introduced a bug in cmForth because of > > his zeal for eliminating DO .. LOOP > There was no need in cmFORTH to compile colon or CODE definitions across > screen boundaries, thus its THRU worked just fine. And, as Jan Stout pointed > out, it is easily modified to allow compiling colon or CODE words across > screen boundaries, if one's factoring is so poor (as mine is on occasion) > that he needs that facility. A bug that doesn't happen to show up in a particular application is still a bug. A bug that is easy to fix is still a bug. One of the reasons that Forth has a bad reputation is because there are so many half-hearted Forth implementations floating around. Too many Forth implementors have a tendency to take shortcuts that compromise the quality of their implementations. The "I don't need that feature this week, so the heck with it" attitude has probably damaged Forth's reputation more than anything else. Mitch