> Well, it seems you didn't understand the point. The discussion is about > _directly_ compiling Java into native code,
I thought that this discussion was about C#/Java iPhone development, specifically by way of Objective-C cross compilers... I actually thought, "Hmm... maybe he is referring to direct to CPU compilation." But in the context of iPhone development that doesn't make sense either. I understand the points made about the historic evolution of the standard desktop .NET vs Java virtual machines... But how does this limit or shape any current-day Objective-C cross-compiler efforts? Java and C# are syntactically very similar, and in this context, the differences are purely non-technical ones. The xmlvm.org Objective-C cross compiler can use either Java or C#. I don't see any technical reasons that would have prohibited Novell from supporting both as well (there are obvious non-technical reasons of course). --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/javaposse?hl=en -~----------~----~----~----~------~----~------~--~---
