> Basically my point is that instead of pushing extensions into the current
> void that is PECL, we need to pull PECL from the void and make it work
> first. You seem to want to take the reverse approach. Push everything
> into PECL and by doing that force someone to fix it, versus fixing PECL
> and then having people fall over themselves trying to get their extensions
> into this new brilliant framework.
I see it as a hybrid approach. At this point, PECL has the
infrastructure to support the development portion of the change. If we
start using it more extensively for such development, then the API
features will come along, and we can start recommending it for end-user
consumption.
I don't think PECL will ever start evolving until we start using it, and
I think its ready for developer usage.
-Sterling
--
"A business that makes nothing but money is a poor kind of business."
- Henry Ford
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
