Re: Re: cvs: php-src / CODING_STANDARDS
| From: | Hartmut Holzgraefe | Date: | Wed, 03 Dec 2003 10:38:25 +0000 |
| Subject: | Re: Re: cvs: php-src / CODING_STANDARDS | ||
| References: | 1 2 3 4 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-6060@lists.php.net to get a copy of this message | ||
Pierre-Alain Joye wrote:
See http://pear.php.net/news/meeting-2003-summary.php. Especially this line: "PHP object-oriented APIs should follow the PEAR coding standards."i don't remember this and even if i did i don't think a PEAR project meeting is able to take any decision on how PHP core developement should be done (and vice versa) (to me it looks more like it happened the other way round with PEAR deciding in the distant past not to use the coding conventions that we finally came up with for PHP function names but to do it the very other way as we still have it with the gd and oci functions but do not want to see in any further extensions ...)
Meeting where you, Sebastian Bergmann, Hartmut Holzgraefe, ...just for the records: some of us left early to catch our train ...
And now I'm wondering why that suddenly becomes uglyIMHO it has been ugly ever since ...
and, as pointed Sebastion, why PHP should follow different things than 99.9999% of others OO langages.OTOH: why should we? PS: can you prove that 99.9999% figure? i'd believe a value of maybe
80% but definetly not 99.9999% ;)-- Hartmut Holzgraefe <hartmut@php.net>