OberonCore

* type identifier "Base" shall not be used in declaring itself

Description: Oxford Oberon-2 compiler
This compiler translates Oberon-2 into a portable bytecode, and comes
with an interpreter (or on some architecures, a JIT) for the bytecode.

There’s something a little unusual about the Oberon compiler we’ll be us-
ing, and that’s the fact that (like most compilers for Java) it doesn’t actually
translate your program into instructions for the physical computer you are
using. Instead, the designer of the compiler has invented a simple ‘virtual’
computer specially for implementing Oberon, and the file fac contains in-
structions for that computer instead. The gap between the virtual computer
and the actual, physical computer is bridged in one of two ways: either by
means of an interpreter program that uses the physical computer to carry
out a simulation of the virtual computer, or by means of a just-in-time trans-
lator (JIT) that compiles code for the physical machine after the program is
loaded, but before each piece of it starts to run. The biggest advantage of
using a virtual machine is that the compiler can be ported to a new computer
just by making a new interpreter – and since the interpreter is itself written
in a highish-level language (C), that’s usually just a matter of re-compiling it
on the new computer. JIT translators must be designed separately for each
machine architecture, though they may share common parts. At present,
translators exist for the x86 architecture used by PCs and Macs and for the
ARM architecture used by the Raspberry Pi.

Не совсем новый, уже здесь сообщалось.
viewtopic.php?f=30&t=5983&p=99944&hilit=congdm#p99944

Показательны выводы человека в двух его заметках.

Там самое интересное, что 64-битный. Некоторые его очень хотели.

В каком месте они закрыты? https://github.com/congdm/Patchouli-Com ... erator.mod

Не совсем новый, уже здесь сообщалось.
viewtopic.php?f=30&t=5983&p=99944&hilit=congdm#p99944