One of the things that I _think_ is happening is that lots of other
scripts/ files are being redone, and thus removing them from the list,
so in effect we're trading out one or two for just Python.
> Why must I install Python in order to compile the kernel? I don't
> understand this. I think there are better alternatives, but kbuild
> seems to be imposed any way.
kbuild != CML2. It all boils down to the current 'language' having no
real definitive spec, and having 3+ incompatible parsers. We could
either try and tweak the language slightly (and probably make it even
harder on external parsers) or throw it out and try again. ESR wrote
CML2 with a Python interpreter, so it uses Python. The spec for CML2 is
out there, and there's even a CML2-in-C project. If you don't want to
use Python, go help (I believe Greg Banks is who ESR mentioned is in
charge of it) that project out and then convince Linus to include it.
> >You don't make the pen yourself when writing a letter either.
>
> I don't like to be forced in a particular pen, that's the reason
> why I use and develop for linux.
To carry this analogy out a bit more, the details on how to make a pen
exist, so if you don't like ESRs pen, go make your own. That's why a
lot of people use Linux too.
> >What are the precise issues with Python? Just claiming it is an
> >issue is not useful for discussing this. Archive pointers are
> >welcome.
>
> Well, let's start writing kernel drivers with Python, Perl, PHP,
> awk, etc... And, why not, C++, Ada, Modula, etc...
>
> The kernel should depend just on the compiler and assembler, IMHO.
The right tools for the right job. C is good for the kernel. Python is
good at manipulating strings.
-- Tom Rini (TR1265) http://gate.crashing.org/~trini/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/