> Does this mean your patches are mutually exclusive? and work
> only on certain platforms and fail on others?
> To answer your question - I am using NT 4 SP 6 on PII/128.
This is not the intent, though we are aware that fixes to one bug have
created new bugs in other parts of the software.
> The issue is not about whether your software has bugs or not.
> Why can't you just have two versions of the software - "Most
> stable version"
> (say 5.1.2...) and the "Latest version" (6.0.3) etc...
Since our software comes on CD, it is difficult to make several versions of
a piece of software available. Would you have our sales people ask each
customer which they would like to have shipped to them? This is different
from the Emulator (but only slightly) since it is not downloadable over the
web.
> reliably every time to a PRC and will never destroy my source.
> (before someone suggests gcc... don't, I already use it & I am happy
> with it)
I am not denying that our software has bugs. I know it does. I maintain
the buglist. However, I am simply asserting that it is very difficult for
me to track down issues and get them logged and fixed with only vague
references such as this. Do you have a project where you can show me how
the CodeWarrior complier destroys your source? If our compiler is
corrupting executables, we absolutely want to get that fixed ASAP. However,
be aware that code that compiles under GCC is not guaranteed to compile
under our compiler. Partly, this is because ours is ANSI-compliant, and GCC
has some added features that, if used and then compiled with a compiler that
doesn't support those added features, may not compile cleanly, or at all.
> You guys were not able to make even the compiler stable
> (forget the IDE which may be a really complicated piece of
> software). How could we trust anything generate by the compiler
> which swaps numerator with denominator in a division!!, corrupts
> a bitmap while it is being linked in, and a linker which generates
> a GPF once in a while.
This is the kind of statement that I have difficulty resolving. You say our
compiler is not stable, but when you come across issues, you haven't
reported them to [EMAIL PROTECTED] or [EMAIL PROTECTED] so that they
can be logged and fixed. The numerator/denominator swapping issue was with
R5, and a patch was released to fix that as soon as we were made aware of it
and got it fixed (check http://www.metrowerks.com/download/ and search for
patches released with CW for Palm R5 for that patch). Are you using release
5 on Win2k? That might be part of the problem. The 3.5 SDK, Update 1, and
the debugger plugins will not work with R5. I'm not aware of bitmaps being
corrupted while being linked in. Which version of the linker/post-linker
are you using? Could you send me a reproducible case so it can get fixed?
I would also like to see a reproducible case of the general protection fault
you mention.
Our software is not perfect. I and everyone else at Metrowerks recognize
that, and we apologize for any issues you have had with our software. Just
realize that we want to make our product the best it can be. We need your
feedback and bug reports in order to make that happen. I simply can't use
the tools as extensively as any of you do to be able to find every bug that
exists in this environment.
So, send your reports in. Send reproducible cases. The more issues I can
get logged, the more that can get fixed.
-hkmlt
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
