Re: taking over SQL_Parser

Sebastian Mendel schrieb: > Christian Weiske schrieb: > >> it'd be good if you would fix some of the bugs and attach a patch to them at the >> bugtracker. This way we could review them first, until we let you do it all on your own some time >> later. > > i added some patches and some new bug reports including patches > > but most of the bug reports are not really bug reports but just missing > features or missing support for SQL syntax > > the big problem is how SQL_Parser handles unknown syntax - it should not > stop in unknown syntax but extract as much information as possible without putting pressure on your, ti would be nice if you would come to any conclusion about getting developer status for SQL_Parser for me there are some things that needs to be done - much documentation - bringing code to PEAR standards - putting dialect data files into data? - renaming Lexer to SQL_Lexer? ^^ needs this a second package? how should this be handled? - does SQL_Compiler needs a seperate Package? - what about ctype.php? is this the correct way to handle possible missing functions? - what about tests, can i upgrade them to use PHPUnit 3? - does anybody knows what was the intention for Expressions/incldue.php? - package2.xml -- Sebastian Mendel www.sebastianmendel.de