\0, Pablo,
IMHO although the runtime and VM both provide facilities such as garbage
collection, scheduling ect they are not alike at all. Actually that is the
ONLY way they are alike. VM run compiled bytcode like others stated, but
the VM is a whole program on its own, which is run, and handled by the os
like a compiled-to-machine code program would be, and then that (VM)
program reads and runs the bytecode compiled program.
Whereas instead of being a seperate program in it's own right, Go's runtime
is actually just a set of libraries that are compiled into every Go binary.
Just like the std libraries that you import into your program (ie "fmt")
they are compiled and linked along with user code into a single program. In
fact, you can also import these libraries into your code manually and play
with it; with a VM you don't have the same ability. (*some VMs can be
'tuned', but only from knobs that are specifically givin to you, not
arbitrarily)
The end result is that you get all the facilities for managing memory,
goroutine schedualing, ect that you want from a virtual machine, but
interwoven into your code, which as a whole is then compiled down to raw
machine code.
If you want to learn more about how this is all implemented, I find that
the go source is extremely approchable, and even a beginner should be able
to get some idea about what the code is doing. ("$GOROOT/src/runtime is a
good starting place)
--
You received this message because you are subscribed to the Google Groups
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to golang-nuts+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
