Chuck Blake wrote:
> I'm not sure you read what I said very carefully { about use case 3, too,
> but that use case is admittedly pretty lame :-/ }.I didn't mean to say you shouldn't change it. I was just explaining how it came to be the way it is now. My original intention was that Pyrex would always generate correct C code, so the user should never see an error (or even a warning) from the C compiler. Given that, there was no need to emit #line directives, and in fact some reasons not to. It's become apparent since that it's not feasible for Pyrex to guarantee correct C code in all cases, since there's always a possibility of a mismatch between Pyrex declarations and external .h files. So there may be some benefit in generating #line directives after all. -- Greg _______________________________________________ Cython-dev mailing list [email protected] http://codespeak.net/mailman/listinfo/cython-dev
