Den tir. 16. apr. 2019 kl. 20.09 skrev Lester Caine <les...@lsces.co.uk>: > 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.
Everytime the topic of interbase comes up, you always referer to applying fixes, yet I'm yet to see any contributions from you to actually maintain the code at php-src, am I to understand that this means you patch your own builds of PHP? Because it is not something that strengths the argument that has any merit of strengthen the argument of keeping it, quite the contrary if anything. > 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? -- regards, Kalle Sommer Nielsen ka...@php.net -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
