If we think about it javac would not be a compiler otherwise :-)
If we think about it javac would not be a compiler otherwise :-)
In the case of JSC, a binary is produced currently but it must be launched by a Node app. So it doesn't exactly meet my criteria. But being able to produce embedded V8 code will not be significantly more difficult for these examples. (Recreating Node's stdlib would of course be difficult but that's separate.) I'm hoping to have a Node-independent target soon.
You are "dependent" if you want on the RunTime (rt.jar). The way it was explained to me, and the model which I sticking to in my mind is:
Abstract Machine/language + RunTime = Level of the onions of a computer.
Assembly/CPU + libc Bytecode/JVM + rt.jar
The language manipulates the resources provided by the machine (registers, stack-machine etc etc).
My recollections are fading though - but I found this model to be good enough to explain me well how a computer works.
I don’t know D enough to know whether GC is enabled in this project, which is a major weakness in many dynamic languages that one might imagine aot compilation could eliminate.