Hi Francois, I'm in favour of shipping PHP code as part of either PHP core, and for extensions.
I would use this for Imagick. There are several 'helper' functions that would make this library easier to use, that are trivial to write in PHP, that are incredibly not trivial to write in C. > Please give examples of core extensions that, in your opinion, are > susceptible to be partially or fully converted to PHP. Uh - I don't really agree that any existing core code should be converted to PHP. If the code is already there and working as C code, there are very few benefits converting it to PHP now. If we ever get around to refactoring how strings are stored in PHP, it's at that point that converting existing functionality to PHP code might be a good idea. > Suggestions to complement existing core extensions (like an additional curl > OO layer) are welcome too. If you want this RFC to pass, I'd strongly recommend having conversations about adding those as separate RFCs, once the "having PHP code distributed with PHP" RFC is passed as otherwise the signal-to-noise ratios will be terrible. cheers Dan Ack -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
