I am scared of the same thing but with a twist :-) Whenever you are
emulating processors the host processor should be much faster than the
processor getting emulated. This is one of the reason why in case of Win
CE/Pocket PC development we don't have an ARM emulator. You have to build
application separately for emulation (x86 binaries) and for release version
(ARM). Most of the time WinCE developers cry when their application don't
run on device while it seems perfect on emulator. The problem is on emulator
side, the emulator says the API is supported while device says it's not. You
can't complain to MS or the hardware provider. MS will put the reponsibility
on h/w vendors and vendors will have the right to support any API or not.
The result, a highly painful development environment. I am not saying that
emulator should be hundred percent bug free (It's part of development
process, bugs are bound to be present in the first release no matter how
much care you take) but rather it should be capable of emulating the
hardware in the true sense, like at present applications can play baseball
with the system globals, take memory management for a ride or do what ever
you want to do on the device ("almost" :-) but try to do it on emulator :-D
Emulator should not require binaries made up of native environment opcodes
in order to debug them or else Palm's development will also become a night
mare.
Khurram+
PS: On the lighter side. It has a good side effect for ARM developers who
have to develop applications separately for release and debug versions.
Untill or unless you have the device (really costly and that too from all
vendors) you can't tests your cracks and hence s/w piracy becomes really
costly to maintain :-)
----- Original Message -----
From: "Aaron Ardiri" <[EMAIL PROTECTED]>
To: "Palm Developer Forum" <[EMAIL PROTECTED]>
Sent: Friday, January 04, 2002 2:35 PM
Subject: Re: Palm and ARM (Was: PL/I for Palm ?)
> On Fri, 4 Jan 2002, John Marshall wrote:
> > > but in both cases there is no apparent relation to PalmOS.
> >
> > Of course, what a native ARM Palm OS runtime might look like is
> > another question.
>
> question is, who said you will be able to write native ARM apps
> at all on the ARM units? i assume palm will be disclosing
> their "timeline" for developers at palmsource.. and, that is
> not too far away :)
>
> from public discussions, it is obvious that m68k emulation
> will be provided with native OS call implementations.. but,
> it has not been disclosed that developers will be able to hook
> directly to the ARM hardware..
>
> it opens up too many problems.. what happens when you beam
> from an ARM unit to an m68k unit? blah blah blah.. do we,
> as developers, feel for devloping two seperate builds like
> winCE/PPC has to do?
>
> // az "fun fun fun... "
> [EMAIL PROTECTED]
> http://www.ardiri.com/
>
>
> --
> For information on using the Palm Developer Forums, or to unsubscribe,
please see http://www.palmos.com/dev/tech/support/forums/
>
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
