Path: csiph.com!eternal-september.org!feeder.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail From: rickman Newsgroups: comp.lang.forth Subject: Re: Really? Date: Tue, 7 Feb 2017 06:29:34 -0500 Organization: A noiseless patient Spider Lines: 37 Message-ID: References: <1239a88b-a574-401b-9454-50ac7e000049@googlegroups.com> <5899a408.386236853@news.eternal-september.org> Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Injection-Date: Tue, 7 Feb 2017 11:27:48 -0000 (UTC) Injection-Info: mx02.eternal-september.org; posting-host="b6443822665b11d600c80c1d7678cd9f"; logging-data="30296"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/0SQA7AMmq0Y30UIbP97vK" User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0 In-Reply-To: <5899a408.386236853@news.eternal-september.org> Cancel-Lock: sha1:62y7PTHXeF2TddcX2DTeYfapZYQ= Xref: csiph.com comp.lang.forth:54684 On 2/7/2017 6:01 AM, Stephen Pelc wrote: > On Mon, 6 Feb 2017 06:46:00 -0800 (PST), Mark Wills > wrote: > >> "As for Forth, although it has dedicated advocates, it's >> explicit stack orientation and its lack of modularity limit >> the scale of Forth programs. One of the largest Forth efforts >> was an integrated operating system called Valdocs (Valuable >> Document System) on the Epson QX-10. The software remained buggy >> couldn't be updated quickly enough for the machine to remain >> competitive - although you could just as easilly blame the >> computer's Z-80 processor (since at the time the 8088 based IBM PC >> and 68000 based Apple Macintosh were being introduced) and difficulty >> in finding experienced Forth programmers. Whatever the cause, this >> soured the acceptance of Forth for large scale projects." >> >> http://www.cpushack.com/CPU/cpuAppendB.html#Forth > > I have met several of the Valdocs people. The critical problems > with the project were project management problems. In any large > project, project management is really, really important. > > To give an example of a current large Forth project that has > evolved over 30 years, see the Candy system at > http://constructioncomputersoftware.com/ > which is currently built on VFX Forth for Windows. Candy consists > of 55 Mb of source code in 1.2 million lines of code and generates > an executable of 27 Mb. I always quote this one because I do a full > rebuild before each VFX Forth release. Just out of curiosity, how long does it take to compile this code? Any idea of what feature of the computer limits the speed? CPU speed, disk speed, memory speed, cache size? -- Rick C