Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!clyde.concordia.ca!uunet!samsung!zaphod.mps.ohio-state.edu!mips!excelan!unix!hplabs!well!brecher From: brecher@well.UUCP (Steve Brecher) Newsgroups: comp.sys.mac.programmer Subject: Re: How to Argue Technical Points (now documenting tail patches) Message-ID: <15079@well.UUCP> Date: 18 Dec 89 04:52:28 GMT References: <2744@dogie.macc.wisc.edu> <5540@internal.Apple.COM> Reply-To: brecher@well.UUCP (Steve Brecher) Organization: Software Supply, Sunnyvale, CA Lines: 24 In article <5540@internal.Apple.COM> usenet@Apple.COM (Larry Rosenstein) writes: >> In article rang@cs.wisc.edu (Anton >> Rang) writes: >> I like the idea of a Tech Note documenting bugs fixed in various >> system releases, though.... > > We have distributed change notices for recent versions of the system. > Some of these are available for FTP on Apple.COM. Ya, but there is no detailed list of known bugs. On several occasions I have spent considerable time diagnosing bugs in ROM or system software and reported them, only to be told that they were already known. For example, there is now a bug in FMSwapFont (possible LoadResource between dereference to a handle and use of the pointer) which is fixed in the IIci and Portable ROMs (but not on other machines running the current System) -- which I learned in response to the bug report. It would be very helpful if Apple maintained list of known ROM and system software bugs; it could be accessible, e.g., on AppleLink. -- brecher@well.UUCP (Steve Brecher)