Dag Sverre Seljebotn wrote: > We all wish Fabrizio had got his SoC. The question is though, what do we > do now? > > I was thinking about if it is scaled down a lot and one only considers > the PyPy parser and a parser consumer that builds the existing Pyrex > tree (drop-in replacement of Scanning.py and Parsing.py). How much work > would that be?
Implied question: how much work is it to keep in sync with the PyPy parser development? We'd have to extend the parser to understand C types and 'cdef', so the first thing to check is if there's a way to do that without having to patch into the parser too heavily. So, even in the long term, the PyPy parser does not come for free. We're actually lucky we have a couple of compiler tests by now, but the first thing to do before starting such a project is growing the test suite. We should consider including the test suites of Python and PyPy, but that still wouldn't give us enough tests for the stuff that is most important here: the C type integration, which is neither a part of Python nor PyPy. To some extent, the question of parser rewriting reminds me of this: http://www.joelonsoftware.com/articles/fog0000000069.html Doesn't "if it ain't broken, don't fix it" apply here? Stefan _______________________________________________ Cython-dev mailing list [email protected] http://codespeak.net/mailman/listinfo/cython-dev
