Re: PEAR2 package naming standards (namespace usage)
| From: | Paul M Jones | Date: | Mon, 01 Sep 2008 16:42:20 +0000 |
| Subject: | Re: PEAR2 package naming standards (namespace usage) | ||
| References: | 1 2 3 4 5 6 7 8 9 10 11 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-50696@lists.php.net to get a copy of this message | ||
On Sep 1, 2008, at 11:39 , Lukas Kahwe Smith wrote:
On 01.09.2008, at 18:34, Paul M Jones wrote:Sorry to miss that one Lukas -- those were just the first three that came to mind. :-) Propel, Phing, Creole ... I think those follow the PEAR1 class-to-file naming convention as well. -- Paul M. Jones http://paul-m-jones.com/On Sep 1, 2008, at 10:34 , Travis Swicegood wrote:You can add Doctrine to this list.Howdy all, Greg; On Aug 31, 2008, at 10:37 PM, Gregory Beaver wrote:All due respect, Travis, but there are others *I* know about, and I'm sure many that are not publicly available that neither of us knows about. E.g., SwiftMailer, HTMLPurifier, and Mike Maberezny's "Mad" framework all use the PEAR1 naming convention.Might I ask what problems have we encountered in PEAR1's naming scheme that warrant this?This is warranted by the lack of adoption by anyone outside PEAR and in some cases open hostility toward the PEAR naming schema by those same people. Zend Framework and SolarPHP are the only two packages outside of PEAR that I know that use the PEAR naming schema.