|
» Subscribe » Favorite Links » What is S60? » Freeware & Trials » S60 devices » Hints and tips » About this blog |
» Blognotes (15) » Bugs and Workarounds (2) » Carbide.c++ 1.1 (3) » Carbide.c++ 1.2 (7) » Carbide Plug-Ins (2) » CodeWarrior (2) » FAQ (5) » Future directions (17) » General (41) » Off-topic (3) » On-device debugging (7) » Performance Investigator (1) » Product features (13) » Product releases (16) » Screencast (5) » Support (12) » Tool setup (4) » UI Designer (8) » Usability (6) » Work in Progress (11) » Write-build-debug (3) |
|
» Don't get lost in the code.. » What's your Perspective? » Launching the Emulator » New controversial addition in v1.3 » Upgrading your license illustrated, plus screencast requests. |
|
Subscribe to RSS feed For email notification, please click here ยป |
« Don't get lost in the code.. | Main
The difference between an emulator and a simulator is that an emulator emulates s60 phone via x86 instruction set and a simulator emulates s60 device with ARM instructions.
We are currently exploring the option to replace emulation debugging with simulation debugging.
There are many benefits to the developers to switch, mostly arising from the shortcomings of current emulator. The problem is that this technology is rather expensive. I believe that if the performance and usability of simulation debugging will exceed that of a current emulator then we can safely add it to our Developer and/or Professional addition of Carbide C++. Personally, I think that it should be there in Express addition to begin with, but am afraid that product planners and cost watchers will not be happy about my enthusiasm... In any case I hope that we will be able to add this technology to the toolset soon. Maybe initially as an addition to emulation and later as a full replacement.