Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!wuarchive!usc!apple!voder!pyramid!pyrnj!esquire!yost
From: yost@esquire.UUCP (David A. Yost)
Newsgroups: comp.sys.mac
Subject: Re: Do I Want system 6.0.5?
Summary: Wingz has the bug, not 6.0.5
Message-ID: <1921@esquire.UUCP>
Date: 8 Apr 90 05:15:59 GMT
References: <1554@blackbird.afit.af.mil> <11009@bsu-cs.bsu.edu> <2036@mit-amt.MEDIA.MIT.EDU> <13580@cgl.ucsf.EDU> <1906@esquire.UUCP>
Reply-To: yost@esquire.UUCP (David A. Yost)
Distribution: usa
Organization: DP&W, New York, NY
Lines: 34

In article <1906@esquire.UUCP> yost@esquire.UUCP (I, David A. Yost) writes:
>I personally saw Wings 1.1 and 1.1c crash 6.0.5 upon quitting and trying to
>launch it again under Multifinder.  Wingz tech support only discovered this
>on March 22 or so, and they say it is a problem that Apple will have to fix.
>Anyone know anything more on this?
>
>I reluctantly backed off to 6.0.4.

Keith Esau at Informix just posted this on Applelink:

    Well, the egg is on my face.

    A couple of days ago I claimed to have found a bug in the Memory
    Manager of System 6.0.5.  I WAS WRONG.  After careful examination of
    the problem, the problem ends up being in my code because of an
    oversight in an obscure area of my code.

    Fortunately for me, the fix in my code is easy.  Unfortunately, the
    things I said in my other note have propagated far beyond where I
    intended.  I hope that this message will make up for.

    As for other developers out there, please don't take anything at face
    value;  CHECK IT OUT FOR YOURSELF!  This includes both new Systems and
    alleged bugs found.  And if you do find bugs in System software,
    contact Mac DTS and let them help you verify it (which I did, but
    unfortunately I also left a note on a bulletin board).

    I hope this clears the air.

    Keith Esau, Informix Software
 
 --dave yost
   yost@dpw.com or uunet!esquire!yost
   Please ignore the From or Reply-To fields above, if different.