HaxeManual icon indicating copy to clipboard operation
HaxeManual copied to clipboard

Document differences between Java and JVM targets.

Open indolering opened this issue 5 years ago • 5 comments

I read that the JVM target, "gets rid of issues with incompatibility between Haxe and Java type parameters."

It would be best if any compatibility issues with Java and differences between the two targets were detailed in section 12.8.

indolering avatar Apr 26 '20 20:04 indolering

I wouldn't really know what to document in that regard. The Java target generates .java files, the JVM target skips that step and makes a .jar. Not sure what other kind of information end users really need to learn about.

Simn avatar Apr 26 '20 21:04 Simn

Me neither! Maybe @waneck can pipe in?

indolering avatar Apr 30 '20 04:04 indolering

Simn says that JVM target relies on some API which is unavailable on some android devices ten months ago. Simn, can you give more details about this?

RblSb avatar Apr 30 '20 05:04 RblSb

That was when it was using MethodHandle, which is no longer the case. @ibilon tested it on various android versions and concluded that it seems to work fine.

Simn avatar Apr 30 '20 05:04 Simn

I left a comment on the original blog post about the type incompatibility, but it would still be good to include any differences between the targets. Even if it is just that the JVM target doesn't require OpenJDK to compile everything.

indolering avatar May 03 '20 23:05 indolering