Hi, > 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 readable ;-P But Pyrex is a great tool anyway. Regards Antoine. _______________________________________________ Python-3000 mailing list Python-3000@python.org http://mail.python.org/mailman/listinfo/python-3000 Unsubscribe: http://mail.python.org/mailman/options/python-3000/archive%40mail-archive.com