I stumbled over this case which crashes Cython: http://hg.cython.org/cython-dagss/rev/50ec882441d0
Now, I could just go on and fix it in the switch transform; however I believe this is suboptimal... What happens is that an error is reported during expressino analysis, and then life goes on, to code which expects everything to be in order. So I propose this change: There is a cutoff in the pipeline at which stage errors are reported (and if any, processing stops). Any transforms after this stage (like those in Optimize.py) can happily assume there are no errors in the code. I can do it in 10 minutes but I wanted some feedback first. (In particular, a simpler solution would be to always report only 1 error -- this is what Python does, but Cython (and gcc) usually tries to gather up more than one error.) (I'm simply assuming that this is present somewhere in the Pyrex code so that one aborts right prior to code generation, so this is really a problem with the new pipeline stuff). -- Dag Sverre _______________________________________________ Cython-dev mailing list [email protected] http://codespeak.net/mailman/listinfo/cython-dev
