>If we're going to be restricted in what we can access, at least provide us a
>legal method to retrieve what we put there through legal methods.
Thanks for the suggestions. I'm actually meeting later on today with some
people to talk about how we can add more such accessor routines into the
PalmOSGlue library, assuming that the attributes in question are ones that
deserve to be supported on an ongoing basis. (That is, that the
engineering team is willing to support forever, thus it has ongoing work
implications.)
This becomes particularly relevant as we move to ARM chips, since
maintaining support for direct access to internal structures becomes
time-consuming and error-prone and thus only something we'll support when
we really have to.
A solution based on PalmOSGlue, which can make sure to do the legal and
supported thing on future OS versions, is far better. (For those who
aren't familiar: many PalmOSGlue routines check the OS version number or
some other identifying fact like that, and based on that information either
do the old hack way, or else call the new supported way.)
-David Fedor
Palm Developer Support
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
