But the other side of the coin is, why hold up a release for a relatively minor
bug like this? The number of people who use bitfields is very small, and for
those that do, there are simple workarounds. Why hold up a major release for
something this minor?
Most software releases have known bugs in them when shipped. Something as large
as CodeWarrior no doubt has hundreds of known and deferred bugs when it's
shipped. The line has to be drawn somewhere. There's no way you're ever going to
get something as large as CodeWarrior squeaky clean. If you waited that long, it
would *never* ship.
-- Keith
"Stephen Best" <[EMAIL PROTECTED]> on 10/04/99 11:41:59 PM
Please respond to [EMAIL PROTECTED]
Sent by: "Stephen Best" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc: (Keith Rollin/HQ/3Com)
Subject: Re: Debugger Bug in R5 update
> Yes, unfortunately, we are aware of a debugger bug in which bitfields
> don't appear correctly in the debugger. Unfortunately, this bug won't be
> fixed in time for R6 (the fix broke something else and we thought it'd be
> better to back it out) but we'll try to get this patched.
Better still, hold R6 until it's squeaky clean! Installing brand new
software with known bugs like this isn't a particularly attractive
proposition ...
Stephen Best
Bitware Australia Pty. Ltd.
