Roger,
> Andreas, it sounds like you have a programming technique problem.
Hopefully a misunderstanding. Don't be quick with judgements about someone
you don't even know.
I was referring to POSE warnings that pop up because of bugs in the OS. If I
do not use memory manager calls in a particular part of code,
yet receive warnings about directly accessing memory manager data
structures, it's obviously a problem in the OS or in POSE.
Keith continuously improves POSE and I wasn't able to reproduce any of these
cases with 3.0a6.
Besides I'm still not convinced that memory manager data structures are
particularly subject to change. What about all the other internal structures
that are revealed in the API? Should POSE warn about these as well?
Of course, POSE and many of its warnings (especially about unlocked and free
chunks) are inevitable. Others need to be turned off in certain cases, e.g.
when you have an application that has to do 4bit grayscale on a EZ with
PalmOS pre-3.3 (e.g. ScreenShot Hack).
> Note: the Microsoft release style of releasing code with "acceptable
> levels of bugs" is not the Palm OS release style.
If you believe this then you probably never tried PalmOS 3.2 (where e.g. you
can't remove hacks) or 3.5 (with e.g. blatant German spelling errors and
applications that are repeatedly put back into the Unfiled category).
"Whichever one of you has committed no bug may throw the first stone." :-)
Best regards,
Andreas
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
