Re: Re: PEAR2 Coding standards, Autoloading and Namespaces
| From: | Joshua Eichorn | Date: | Fri, 04 Apr 2008 22:01:33 +0000 |
| Subject: | Re: Re: PEAR2 Coding standards, Autoloading and Namespaces | ||
| References: | 1 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-49623@lists.php.net to get a copy of this message | ||
Baptiste Autin wrote:
A whole lot of thought provoking stuffI don't have a lot to say about this except there is a real case made for a HTTP package. It would contain an HTTP class which gives you constants for all the http codes It could also include HTTP classes that would be shared (though these could be other packages if you wanted) HTTP_Message etc etc For groups like tools there is much less of a need for a package with the base name, but for something like HTTP where everything relates to a protocol there could be shared code at the first level of the naming. -josh