Marcus Boerger wrote: > Hello Helgi, > > obviously one problem is that PEAR does ignore coding standards. Classes > should be prefixed in both pear and core. And neither Date nor File is in > any way prefixed. In th end all we see here is that we want namespaces asap.
I absolutely agree with these points. It is also worth noting that the coding standards of prefixing classes were introduced long after packages like "Date" existed. We have a case of a userbase and a shifting foundation that is PHP. Perhaps the best future of PEAR is to design with those shifting sands in mind as more of a primary design concern. There's plenty of time before PHP 6, so we can get this taken care of by then, I think. These are just preliminary thoughts, but it is imperative that all PEAR classes be tested, and by inference testable, with PHP releases. Anything that comes from .php.net should work with PHP, or at least be given a chance to fix the problem before the release. This means a tighter integration of PEAR developers and PHP internals, by no means an easy task, as is shown by Pierre's tribulations over Date. At the least, it would make sense to provide some kind of PEAR-related RC cycle for PHP releases. I will see if I can shake up some ideas on how to get PEAR more involved (at least better involved) in the PHP release process over on pear-dev and report back. Greg -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
