rfc:deprecate-and-remove-ext-interbase
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
rfc:deprecate-and-remove-ext-interbase [2019/03/22 18:48] – kalle | rfc:deprecate-and-remove-ext-interbase [2019/04/10 15:05] – salathe | ||
---|---|---|---|
Line 1: | Line 1: | ||
====== PHP RFC: Unbundle ext/ | ====== PHP RFC: Unbundle ext/ | ||
- | * Version: 1.0.0 | + | * Version: 1.0.3 |
* Date: 2019-03-22 | * Date: 2019-03-22 | ||
* Author: Kalle Sommer Nielsen < | * Author: Kalle Sommer Nielsen < | ||
- | * Status: | + | * Status: |
* First Published at: https:// | * First Published at: https:// | ||
Line 15: | Line 15: | ||
===== Proposal ===== | ===== Proposal ===== | ||
- | Given the unacceptable nature of the status of this extension, I therefore propose | + | Given the unacceptable nature of the status of this extension, I therefore propose |
- | === 7.4 === | + | ===== Backward Incompatible Changes ===== |
- | Any function or alias called, which is exposed by ext/ | + | Codebases relying on ext/ |
- | === 8.0 === | + | ===== Further rationale ===== |
- | The ext/ | + | Like already stated above, it is very vital for PHP to provide a set of high quality extensions to come with the default distribution. However, if the PHP Development Team no longer can give the support to an extension |
- | ===== Backward Incompatible Changes ===== | + | The usual procedure is to move extensions that once were in the Core into PECL. An extension in PECL does not mean the extension will cease to exist, it just means that it will not be updated by the PHP Development Team in any capacity. This allows the communities of relevant extensions to take them over, and let them follow their preferred release schedule, instead of the monthly one that PHP follows. Extensions in PECL also can follow their own versioning scheme, and can change as they feel like, and do not have to follow the strict rules of the Core to be released. Many extensions in PECL are also distributed by popular Linux distributions and the PECL infrastructure allows automatic compilation of Windows versions in many flavors of an extension. |
- | Obviously, code using the interbase extension would issue deprecation warnings, and/or would have to use the PDO_Firebird extension in the Core in 8.0. | + | ===== What is broken about it? ===== |
- | ===== Open Issues ===== | + | There is a long list of things that is broken with this extension, which the PHP Development Team is unable to work around as we do not have any abled person who understands the extension available, below is some of the popular ones: |
- | * None | + | * Reference counting and management of connection resource links is broken |
+ | * Multiple connections is broken | ||
+ | * PHP4 style " | ||
+ | * Thread safety is poorly broken | ||
+ | * A small subset of field types are supported, anything else crashes | ||
===== Voting ===== | ===== Voting ===== | ||
- | The primary vote is about whether to unbundle ext/ | + | The primary vote is about whether to unbundle ext/ |
- | <doodle title=" | + | <doodle title=" |
* Yes | * Yes | ||
* No | * No | ||
</ | </ | ||
- | |||
- | ===== Patches and Tests ===== | ||
- | |||
- | None, yet. | ||
===== References ===== | ===== References ===== | ||
* Internals discussion: [[http:// | * Internals discussion: [[http:// | ||
- | |||
- | ===== Rejected Features ===== | ||
- | |||
- | None. |
rfc/deprecate-and-remove-ext-interbase.txt · Last modified: 2019/05/07 08:28 by kalle