ooc-dev team mailing list archive

[Amos Wenger <amoswenger@xxxxxxxxx>]

Depending on what you read, it means either the rock compiler
project<http://github.com/amoswenger/rock>(in which case standalone
means not dependant from Java / self-hosting),
either that: currently, generating C files is the only "real backend" that's
implemented for the ooc language. However, I had in mind from the start that
the language's design should stay flexible enough that we could implement
other backends. Before ooc, I had another project, which generated assembly
code as understood by Nasm, the Netwide Assembler. But for ooc it seemed
simpler to just generate C code and be done with it.
However, for the future, I'd love to see appear a LibJIT backend, an LLVM
backend, and maybe a GNU as backend (the assembler that gcc uses).
Implementing such backends would help the ooc language specification to stay
target-agnostic. It can only do good, as long as every implementation
conform to the standard (still under discussion/construction).

Amos

2009/6/30 Vincent R. <forumer@xxxxxxxxxxxxxxx>

> I read somewhere from ooc website (cannot find post anymore) that a
> standalone compiler is in study.
> What does it mean ? It will generate directly binaries withouit the
> intermediate step of generating C files ?
>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~ooc-dev<https://launchpad.net/%7Eooc-dev>
> Post to     : ooc-dev@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~ooc-dev<https://launchpad.net/%7Eooc-dev>
> More help   : https://help.launchpad.net/ListHelp
>