On 16/04/2019 14:29, Chase Peeler wrote:
Not once has the fact that an extension exists in PECL instead of core
prevented me from utilizing that extension. The only thing that has ever
prevented me from using an extension is when it is not maintained. I've
been following this entire thread, and I have yet to see what the big deal
about having the extension moved to PECL is. If anything, being in PECL
gives you MORE flexibility as you aren't tied to the PHP release cycle.
The 'advantage' up to now of being in core has been that the BULK of the
code changes have been required to track changes in the PHP side of the
interface. The core SQL interface has not basically changed so up until
now it has worked fine for both Firebird and Interbase. So as long as
someone who understands the PHP side of the equation puts the same
generic changes into the driver as in other core extensions then things
carry on working ... but developments in the PHP side have become a lot
more difficult to track than when I did manage to apply fixes to the
driver code many years ago.
Moving forward there has been some substantial changes on both the
Firebird and Interbase side which today could benefit from a separation
but that is not 'essential' to continue to use the the legacy interfaces
as the vast majority of development work on the Firebird side is in
additional SQL functionality and the core way of passing that has not
changed in 25 years so there has been no reason to 'continually update'
the driver, only the wrappers around the basic driver. Which do not
impact the driver extension itself?
--
Lester Caine - G8HFL
-----------------------------
Contact - https://lsces.co.uk/wiki/?page=contact
L.S.Caine Electronic Services - https://lsces.co.uk
EnquirySolve - https://enquirysolve.com/
Model Engineers Digital Workshop - https://medw.co.uk
Rainbow Digital Media - https://rainbowdigitalmedia.co.uk
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
