Hi Leonardo, Leonardo Santagada wrote: > I remember some time ago people on #pypy were talking about redoing > the parser for python because it was not good enough or something. > Also the parser generator that cfbolz wrote doesn't support unicode > and was not suited for automatic-semicolon-insertion. > > I think it would be good for a javascript parser that supports unicode > because the specs call for it and maybe it would be good to python too > (don't know about prolog/smalltalk though). What would be better, to > have a parser generator that supports unicode or just everyone write > their own recursive descendant parser by hand?
Are you sure that we shouldn't rather try to steal one of the existing JS parsers? If license really is a problem, maybe we could ask the authors whether they would be fine with relicensing under MIT. Cheers, Carl Friedrich _______________________________________________ [email protected] http://codespeak.net/mailman/listinfo/pypy-dev
