John Cowan <cowan@locke.ccil.org>:
> Peter Samuelson scripsit:
>
> > If it is determined that Python
> > is an absolutely onerous requirement and that the system must build
> > with gcc only, it's not reasonable to expect Linus to run `freeze'
> > every time someone patches the Python source. Nor is it practical to
> > require every CML2 patch submitter to include the patch to frozen C.
>
> Patches *to* cmlcompile and cmlconfig would presumably be in Python,
> and the Makefile for these programs would include a freeze step.
> Changes to the CML itself would not require refreezing anything,
> as they only change the pickled rulebase.
Couldn't have put it better myself.
> Are you under the impression that CML2 is a subset of Python, or
> that it's interpreted by the Python interpreter directly, or something?
> Not so. It is a distinct language, implemented with a compiler and a VM,
> both of which happen in turn to be implemented in Python. Since it
> is possible to compile Python to C, both compiler and VM
> can be supplied in either C-source or executable form.
I wouldn't describe the configurator as a VM exactly, but this is
otherwise correct.
-- <a href="http://www.tuxedo.org/~esr">Eric S. Raymond</a>"The state calls its own violence `law', but that of the individual `crime'" -- Max Stirner
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Wed May 31 2000 - 21:00:13 EST