Path: utzoo!attcan!uunet!lll-winken!lll-tis!helios.ee.lbl.gov!nosc!ucsd!rutgers!rochester!pt.cs.cmu.edu!a.gp.cs.cmu.edu!koopman From: koopman@a.gp.cs.cmu.edu (Philip Koopman) Newsgroups: comp.lang.forth Subject: Re: type checking Summary: Let's get the word out. Message-ID: <3045@pt.cs.cmu.edu> Date: 19 Sep 88 15:09:00 GMT References: <8808121826.AA23206@jade.berkeley.edu> <1575@crete.cs.glasgow.ac.uk> <504@smegma.UUCP> Sender: netnews@pt.cs.cmu.edu Organization: Carnegie-Mellon University, CS/RI Lines: 31 In article <504@smegma.UUCP>, mdg@smegma.UUCP (Marc de Groot) writes: ......... > One of my clients has a data acquisition package for the IBM PC written in > Forth. 14 megabytes of source, or approximately 100,000 lines of Forth code. > The project has been running for six years. The code is VERY maintainable, > due to the self-discipline of the programmers involved. The project has been > worked on by about a dozen different people over six years, some who were short- > term, and others who have been there the whole time. >......... The way to get the word out is to publish. I would urge Marc and any others who have done large software projects to publish something about them. A good place to publish would be in the ACM or IEEE journals if you can. It's a lot of work, but Forth has almost zero respectability in the academic arena now. If you don't think you can publish in one of the heavy journals, try IEEE Micro, they're more willing to take chances and they are usually looking for material. You can also try the EE professional magazines. These are targetted at EE managers, and those are the people we need to reach to get Forth used on more projects. Publishing in JFAR is all well and good (and you ought to do it, since they can use the support), but it doesn't get the message out to the "unwashed masses", and *that's* the group we need to inform. Phil Koopman koopman@maxwell.ece.cmu.edu Arpanet 5551 Beacon St. Pittsburgh, PA 15217 PhD student at CMU and sometime consultant to Harris Semiconductor.