Re: Re: [PEPr] +1 for WebServices::Services_W3C_CSSValidator
| From: | Laurent Laville | Date: | Thu, 25 Oct 2007 07:42:51 +0000 |
| Subject: | Re: Re: [PEPr] +1 for WebServices::Services_W3C_CSSValidator | ||
| References: | 1 2 3 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-48328@lists.php.net to get a copy of this message | ||
Christian ,
I don't read PEAR manual every days ;-) Long time ago since I visited this page (when there is only php code sample without explains if I remember).
OK. But I know, at least that all my packages won't follow this rule (to be coherent with my purpose), and why not probably some others.
Is it possible to have a way to remember PEAR community of Coding Standard changes, without to read again and again the manual.
Something like a blog or a new RSS ( http://pear.php.net/feeds/ )
Laurent,BTW, if I agree with you on @access tag for PHP5 package, I don't see why I should not include @since for the first release. It allows to know directly what is the first release, without reading the changelog of versions history.The CS state it: http://pear.php.net/manual/en/standards.header.php @since This tag is required when a file or class is added after the package's initial release. Do not use it in an initial release.