ilya minkov

To the contrary of what i said before, a interpreter should be aesy to
do, as the most job has already been done.

I stumbled over a '98 Sather distro, containing 1.1 Sather and, based
upon the same version, a complete JAVA bytecode compiler back-end (!!!)
which generates bytecode directly without any further intermediate
steps. Both the compiler, and the library are patched. No bugs of its
own are mentioned, but Sather compiler had some minor bugs by itself
that time.

This bytecode can be then run in (almost) any runtime environment
directly, and the C parsing and compilation step is eliminated. If
someone just found a not memory-hungry Java runtime... But that's
quite another question. I bet i could make one... in a few years. The
..NET back-end would also be interesting, since it should be more
lightweight.

So, you find this distro here.
http://www.tat.physik.uni-tuebingen....hnette/Sather/

Sather would profit from that a lot, also from the ability to call Java
GUIs and wide availability...

-i.

ilya minkov

Argh. Don't listen to me. I already discovered the old interpreter which
contains a compiled class loader and C interface, which are the most
crucial parts. This interpreter is interesting all by itself -- imagine
an embeddable version as a scripter!

-i.


......