At 10:47 PM 4/24/99, you wrote:
>Hi Jean,
>
>The patch for this bug is under development right now. It will need to be
>validated and once that's done we'll release it on the website. As a
>temporary workaround, Eric mentioned that you could divide using temporaries
>since this remains unaffected by the bug.
>
>Stay tuned for more info,
>
>- jk
Do you realize what you are asking? You want us to review each line of
code to see if it might be affected by this bug! Then you want us to
replace each incident with something that will generate the division,
instead of letting the compiler pre-calculate the constant and simply
load it.
We would not do such a thing. Instead we have reverted to a previous
compiler. I have been critical of Metrowerks in the past and your
response re-enforces my belief. It shows a lack of understanding
of the development environment on the part of Metrowerks.
1) In a mature design, not all lines of code are known by a single
designer. To suggest that all code can be reviewed and simply fixed
using a sub-optimal work around is preposterous.
2) Why was a bug in the most basic part of compiler operation not caught
in the first place? How could this get by your so called validation
process? Do you really have a validation suite?
I will end my rant now, since this is not specifically a programming
issue. I sure wish Palm/3Com could understand that to move the Palm
to the next stage, they need to pay attention to such issues. This
ain't your basement hacker's platform anymore.
