I am aware of it.
Actually I think that C and C++ will still be around for a very long time,
many more years than any of us.
Indeed. In fact, C is pretty much lowest common denominator, as it’s about as
close to machine code you get without going CPU specific.
(In terms of what machine code can theoretically be generated, C++ doesn’t add
all that much, but as long as we’re pure, portable C - ie no C99, GNU
extensions etc - C++ does offer some tools that can be handy in VMs and
compilers…)
It doesn’t change the fact that the future is full with higher level
languages.
…which could, be implemented using VMs written in C, or compiled to native
code via C using translators. 
I’m doing the former with EEL (roughly as fast as Lua), and I’m going for the
latter as a first quick and portable way of turning it into native code when
run-time compilation isn’t required. JIT is a big job, and either way, it
doesn’t mix very well with realtime constraints, so I’m not sure it’s an
option for EEL at all… (“Just In Time before the application starts” would
work, though - but that’s just a traditional native compiler that happens to
be built into the run-time library of the language.)
[…]
There is an alpha version of Dalvik with JIT support, but I don’t
understand why Google hasn’t provided since the beginning.
Like I said, a JIT is a big job, and it’s pretty hairy stuff to get right -
and you really want a VM in a production system to work correctly…
Meanwhile, time is money, and all that stuff. :-)On Wednesday 31 March 2010, at 16.25.37, Paulo Pinto wrote:
–
//David Olofson - Developer, Artist, Open Source Advocate
.— Games, examples, libraries, scripting, sound, music, graphics —.
| http://olofson.net http://kobodeluxe.com http://audiality.org |
| http://eel.olofson.net http://zeespace.net http://reologica.se |
’---------------------------------------------------------------------’