Path: utzoo!utgpu!attcan!uunet!wuarchive!gem.mps.ohio-state.edu!ginosko!uakari.primate.wisc.edu!uflorida!haven!adm!smoke!gwyn From: gwyn@smoke.BRL.MIL (Doug Gwyn) Newsgroups: comp.sys.apple Subject: Re: Orca/C V1.0 bugs Message-ID: <11203@smoke.BRL.MIL> Date: 1 Oct 89 00:40:08 GMT References: <8909300944.AA10553@trout.nosc.mil> Reply-To: gwyn@brl.arpa (Doug Gwyn) Organization: Ballistic Research Lab (BRL), APG, MD. Lines: 15 In article <8909300944.AA10553@trout.nosc.mil> lvirden@pro-tcc.UUCP (Larry Virden) writes: >then some folks are distressed that the one or two programmers for BW only >got 60% or so of the bugs out of Orca/C... I don't recall anyone indicating distress, upset, or anything else of the sort. One person commented that he had enough trouble with Orca/C V1.0 that he found it "unusable" and reverted to APW C, but that can be taken as a simple description of his experience. I know I've had to work around all the problems that I reported; some people would just give up. To me the Orca development environment is sufficiently superior to the other IIGS alternatives that I prefer to develop work-arounds and hope that future releases will fix the problems. "Getting 60% of the bugs out" is a meaningless software metric, by the way.