Alain Farmer wrote:
> Michael Fair: Using the GCC underlying architecture
> will create licensing problems unless we reimplement
> the whole shebang.
>
> Alain: We must avoid licencing problems. What are they
> in this case?
This was from an old model of how I was going about the
problem. The way I had intended on leveraging the work
GCC had done was stealing the design and some of the code
that produced it. With the code being under the GPL and the
OK license incompatible with that, we couldn't use GCC code.
What I now propose is creating a GCC frontend to the
OK stack files. In essence a bytecode compiler for the
OK scripts. The OK bytecodes can be viewed as their
own programming language. If it's a programming language
it can be compiled.
That frontend may be GPL because it will most likely
share code with GCC itself, however this does not
present a problem to OK. It just means that GCC can
compile OK stacks into platform specific compiled binary
executables. It's a nice clean separated project that
someone could be the maintainer of. It's a beast of its own
and proposes no licensing issues.
-- Michael --
