Ilia Alshanetsky wrote:
The attached patch is a possible solution to the date *crisis*, it renames the class to PhpDate to avoid any namespace conflicts with pear or custom user classes called date.
I do not think it makes sense for PHP to start prefixing internal classes with PHP. We just need a solid userland naming guide so that PHP can keep the right-of-way for internal naming.
As for PEAR if we find better ways of cooperating on the API level it would be a nice dream, however the reality is that API's are a matter of taste and traditionally PEAR developer tastes are radically different from internals developers. This is also due to the fact that PEAR API's are generally designed for completeness, flexibility and extensibility, where as it seems to be that internals traditionally mainly designs for simplicity. This again leads to the conclusion that PEAR needs to prefix just like the rest of the PHP world.
I have attempted to write such a userland naming guide but I am a bit scared to post it here as I expect this to result in 100 emails where people compete with quantity instead of quality. Anyways if anyone has sincere interest in helping please write me offlist. Obviously the powers that are need to nod off the final version.
regards, Lukas -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
