On Fri, Nov 1, 2013 at 6:05 PM, Alan Dert <[email protected]> wrote:
> sorry, but this doesn't make sense to me. a library can be created in any > jvm language and android (java) can use it without knowledge what language > the library has been created by. > (composed this a long time ago, but never hit the send button. I think it might still be useful) It's a size problem, not a language problem. Here's my article including a bunch of links that should tell you more than you want to know about the issues: http://blog.restphone.com/2012/07/scala-on-android-what-you-need-to-know.html. (Needs to be updated to deal with Kitkat) You're right about being able to use any jvm bytecode (Java 6, and parts of Java 7 on the very latest release) on Android. The problem is that there's an issue with the Android toolchain that prevents the use of applications that use more than 64k (method declarations + method calls). The scala standard library is larger than the limit that the Android tools can handle. It's not a Scala-specific problem; any large codebase could see the same issue. -- James Moore [email protected] http://blog.restphone.com/ http://www.linkedin.com/in/jamesmmooreiv -- You received this message because you are subscribed to the Google Groups "scala-on-android" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
