View Single Post
Posts: 992 | Thanked: 995 times | Joined on Dec 2009 @ California
#74
Originally Posted by Milhouse View Post
2) Given the existence of dx, why go to the lengths of creating your own Java/Dalvik language compiler - just use an existing Java language compiler and bolt the dx tool on at the end to convert the newly generated Java bytecode into Dalvik bytecode. No need to reinvent the wheel.
Actually, bytecode conversion is much less efficient at run time. Taking into account a lot of tools for syntax parsing it is much easy to create a clean Java compiler.

Unless anyone can state categorically that Google have their own clean-room Java language compiler which spits out Dalvik bytecode without generating intermediary Java bytecode I think Google may be on a slightly sticky wicket.
Does Google use DX for Dalvik or they just provide DX for people?
It would be interesting to discover that Google has their own compiler but doesn't distribute it because of copyright/patents/etc.

Anywhere, Java future is in clouds now. You can easily have a problem with Oracle if you are successful with Java even as tool.
 

The Following User Says Thank You to egoshin For This Useful Post: