On Tue, Apr 25, 2000 at 09:07:58AM -0700, McCollister, Mike wrote:
> Jon,
>
> > Jon Baer wrote:
>
> > ... and meanwhile they push developers to using
> > the 3.5 SDK which would make it a little obsolete(im guessing) when
> > these new Palms come around.
>
> The Palm OS 3.5 includes types such as Int32, Int16, etc. I recall that a
> Palm representative stated that these types are now being used to make the
> code less dependent on the processor (i.e. more portable). I'm guessing
> that a processor change has been in the plans for a while and I believe that
> Palm is doing the best that they can to make it so that all we have to do is
> recompile our code. I realize that there will be bumps in the road but
> never-the-less I see that Palm will at least try to give us a paved road.
Or possibly just changing other things like the maximum chunk size in calls.
And to other upward-compatible processors.
You are going to have big/little endian problems with the use of
things like 'appl'.
Also there is a huge embedded NOT PALM APPLICATION COMPATIBLE market,
e.g. if I wanted to do a control panel to a radio and not run Impactor
or QuoVadis, I might want to use a bigger or smaller processor.
Just like TiVo uses Linux, but you don't notice, PalmOS's compact GUI
makes an ideal embedded OS for user interfaces.
Also, I would note that POSE doesn't have any non 68K backend, but I
would think that would occur first (like the color device was virtual
before it was real - though they may have had prototypes).
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palm.com/devzone/mailinglists.html
