Bounding space usage of conservative garbage collectors
POPL '02 Proceedings of the 29th ACM SIGPLAN-SIGACT symposium on Principles of programming languages
Java Virtual Machine Specification
Java Virtual Machine Specification
The case for virtual register machines
Proceedings of the 2003 workshop on Interpreters, virtual machines and emulators
A cross-language framework for developing AJAX applications
Proceedings of the 5th international symposium on Principles and practice of programming in Java
Virtual machine showdown: Stack versus registers
ACM Transactions on Architecture and Code Optimization (TACO)
| Hi-index | 0.00 |
Smartphones such as Android-based devices and Apple's iPhone have become popular platforms for mobile applications. In particular, they allow the development of native applications that can take advantage of special purpose hardware such as accelerometers or GPS. While similar in capabilities, smartphones differ greatly in the way native applications have to be written for them. Google's Android is based on Java with an Android-specific set of widgets, while Objective-C is Apple's first choice for developing iPhone applications. In fact, Apple explicitly prohibits Java virtual machines on the iPhone per license agreement. Objective-C and Java are two radically different programming languages. While Java features strong typing and garbage collection, Objective-C supports dynamic typing but no garbage collection. This paper describes a technique how Java-based Android applications can be cross-compiled to native iPhone applications. Furthermore, it is shown how the Android API can be mapped to the iPhone-specific Cocoa Touch API.