Chuck Blake wrote: > Pyrexc/Cython are already not such good citizens. They could but > do not put file and line number directives in the generated C.
There are reasons for that. In theory, Pyrex should never generate invalid C code, so if there are any C compilation errors, I usually want to see where they came from in the C file so that I can figure out what went wrong. I know this doesn't apply to things like misspelled names referring to external C functions, but there's no way of selectively reporting .pyx file positions just for those, and they're usually easy to track down by searching for the relevant name. There's also the problem that some of the code Pyrex generates isn't clearly attributable to any particular place in a .pxd or .pyx file. -- Greg _______________________________________________ Cython-dev mailing list [email protected] http://codespeak.net/mailman/listinfo/cython-dev
