java.lang.Object

[dmitry.z...@gmail.com]

When importing code from java, how shall we treat java.lang.Object
class? Shall compiler replace reference to it with
Phantom's .internal.object class? It will lead to situation where Java
program requests class name and receives something it can't
understand. Make java.lang.Object to be a child of .internal.object?
Seems to be better way. Or am I missing something?

[Alexey Aristov]

Here we should check how Google handles transformation of java byte code to dalvik code. They do it in their Android platform.

--
Aleksey Aristov
Research & Development Director
___________________

Weigle Wilczek GmbH
Martinstrasse 42-44
D-73728 Esslingen
Germany

T (+49) 711 / 459 998 - 0
F (+49) 711 / 459 998 - 29
www.weiglewilczek.com

___________________

The information in this email is confidential. If you are not the
intended recipient, you must not copy, disclose or use its contents. If
you have received it in error, please inform us immediately by
return-email and delete the document.

[dmitry.z...@gmail.com]

Do they have the same problem? 'native' classes?

[Alexey Aristov]

I don't really know. But I'm sure they have some very special handling
for things like Class.forName(), etc

2009/2/19 dmitry.z...@gmail.com <dmitry.z...@gmail.com>: