[Python-3000] pyrex vs. gcc -Wall
solipsis at pitrou.net
Thu Oct 19 10:04:50 CEST 2006
> I don't accept that the code generator needs to be
> "fixed", because I don't regard it as broken. The
> code it generates is perfectly correct. Its only
> crime is not conforming to some C compiler writer's
> notion of what spotlessly tidy C code should look
> like. That's completely irrelevant for Pyrex-
> generated code, since humans aren't required to
> ever look at it.
In the rare cases where the C compiler gives an error on Pyrex-generated
code, I've found it desirable to read the C code to diagnose the problem.
It happened to me a few times when using function pointers and casts
(IIRC). Pyrex would generate C code but gcc would choke on it.
That's when you realize that C code generated by Pyrex is not very
But Pyrex is a great tool anyway.
More information about the Python-3000