Re: PEARifying Doctrine

Hi Lukas, You can get usage information for the current PHP_CodeSniffer release at: http://matrix.squiz.net/developer/tools/php_cs/usage but I would recommend the CVS version if you want PHP_CodeSniffer to check for file/class/function comment blocks as well. And of course, you can get a description of everything being tested by reading the PEAR coding standards document. If you need any additional help with PHP_CodeSniffer, let me know. I'd be happy to help. Greg Lukas Kahwe Smith wrote:

Hi, So I am starting on PEARifying Doctrine. This should give me a good opportunity to learn the source code more in depth as I fix minor formating issues. The file structure is already quite in line with our CS, so I do not envision the need for drastic changes. I will try to use PHP_CodeSniffer here, though due to the lack of documentation and examples I will first have to poke through the tests I guess. The idea is to split things into packages as follows: Doctrine DBAL core - sub packages for all drivers - sub package for ORM core - sub packages for Util, DQL etc. Currently Doctrine uses SimpleTest, which is not E_STRICT so we might also migrate to PHPUnit3. Are most of our PHP5 regulations in the manual these days? regards, Lukas

-- Greg Sherwood MySource Matrix Lead Developer Squiz 92 Jarrett St Leichhardt, Sydney NSW, Australia 2040 t: 13000 SQUIZ ( Support ) t: +61 2 8507 9900 / 1300 130 661 f: +61 2 8507 9988 e: gsherwood@squiz.net w: http://matrix.squiz.net w: http://www.squiz.net Sydney | Melbourne | Canberra | Hobart | Wellington | London Open Source - Own it - Squiz.net