Re: More questions about the QPL for a compiler
"Sylvain LE GALL" <sylvain.le-gall@polytechnique.org> writes:
> Ocaml, as far as i know, is splitted in two differents sets of object
> files :
> - one set represents the compiler, this means the internal guts of the
> compiler, typing system et al
> - another set represents the standards library, stubs system ( foreign
> call ), VM et al
>
> The first set ( compiler ) is under QPL, the second set is under LGPL
> with Ocaml exception. This means, you can produce binary using LGPL (
> with Ocaml exception ) only licenced ocaml objects...
Yes, I understand that the runtime library and such are LGPL'd. But
the compiler, when it compiles a loop, for example, does it in a
particular way. The patterns of assembly code output by the compiler
-- not the parts in the library linked in, but the part actually
written out by the compiler -- are part of the compiler. And they end
up linked with my code.
It's hard for me to believe that the compiler doesn't write any
creative bits into its output -- though maybe there really has been
effort to put those all into the runtime.
-Brian
--
Brian Sniffen bts@alum.mit.edu
Reply to: