David Welton wrote:
> Cool - I'd be interested to see the results of your work with that.
> What are you looking at as a target for the apk size, roughly?
For what it's worth: hello-debug.apk compiled from "hello.scm"
and the kawa .jar is 830405 bytes. This is based on a kawa.jar
whose size is 1747647 bytes.
Of course this is with little or no attempt to minimize the
included classes from kawa.jar. It includes lots of run-time
classes, to support XML, various Scheme library classes,
pretty-printing, GUI programming, etc etc. It shouldn't be
too difficult to "configure out" unneeded functionality at a
finer grain.
Also included is the full Kawa compiler tools (gnu.bytecode,
gnu.expr, etc), which you wouldn't need if you don't use eval
or reflection. It would be a little more work to untangle
these. For example if you reference + (the addition operator) as a
Scheme first-class function (as opposed compiling it away to
inlined bytecode) than you have a reference to the
gnu.kawa.functions.AddOp class. And that class knows how to
optimize itself (inlining, type propagation, etc), which means
it references the compiler classes in gnu.bytecode and gnu.expr.
So this would have to be fixed to avoid pulling those classes in.
--
--Per Bothner
[email protected] http://per.bothner.com/
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "JVM
Languages" 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/jvm-languages?hl=en
-~----------~----~----~----~------~----~------~--~---
