Thursday
10
April
2008

ZF Coding Standard

Actually there have been several discussions about API doc failures.

This was for me the reason to force the coding standard. I am actually working on a coding standard which does automatically check the whole framework and returns all failures which have been found.

By using CodeSniffer, which is a perfect tool for this purpose, and the existing coding standard which can be found on the ZF page, I already created several rules.

Running the test on the framework showed me that there is not really a coded standard… it’s more a “everyone does what he thinks to be the best” thing.

Until now there exist about 15 tests and I already found more than 70.000 failures and warnings.
But I must confess that I am pedantic on the rules.

For example: I integrated a test which looks if the indenting is 4 spaces or not… or if the keywords are written lowercase…

Details for this process can be found in these links:
http://framework.zend.com/wiki/display/ZFDEV/ZF Coding Standards (RC)
http://framework.zend.com/issues/browse/ZF-3027
http://framework.zend.com/issues/browse/ZF-3065
http://framework.zend.com/wiki/display/ZFDEV/PHP Coding Standard (draft)

Back to top
  1. acheter ethylotest

    Monday, April 16, 2012 - 03:56:16

    yeah, i think you are right !
    ethylotest are important and alcootest too !

Add comment

Fill out the form below to add your own comments

User data




Add your comment