|
Re: pyrex vs. gcc -Wall: msg#00184python.python-3000.devel
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. |
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| Previous by Date: | Re: Cheeseshop: 00184, Fred L. Drake, Jr. |
|---|---|
| Next by Date: | Re: Pre-PEP: Easy Text File Decoding: 00184, "Martin v. Löwis" |
| Previous by Thread: | Re: Proposal: No more standard library additionsi: 00184, Greg Ewing |
| Next by Thread: | Re: Proposal: No more standard library additions: 00184, "Martin v. Löwis" |
| Indexes: | [Date] [Thread] [Top] [All Lists] |
| News | FAQ | advertise |