mirrors/php-src
0
0
Fork 0
mirror of https://github.com/php/php-src.git synced 2024-11-23 09:54:15 +08:00
Code Issues Packages Projects Releases Wiki Activity
963511bffa
php-src/UPGRADING

154 lines
4.5 KiB
Plaintext
Raw Normal View History

Prepare for PHP 8.4
2024-09-24 23:03:39 +08:00
PHP 8.5 UPGRADE NOTES
Align section headings with the latest (5.4) migration on-line doc. This will aid future reuse of UPGRADING text.
2012-03-06 04:14:04 +08:00
1. Backward Incompatible Changes
2. New Features
Fixed numbering in UPGRADING file
2014-05-01 18:27:38 +08:00
3. Changes in SAPI modules
4. Deprecated Functionality
5. Changed Functions
6. New Functions
7. New Classes and Interfaces
updated UPGRADING
2015-02-10 15:56:18 +08:00
8. Removed Extensions and SAPIs
Fixed numbering in UPGRADING file
2014-05-01 18:27:38 +08:00
9. Other Changes to Extensions
10. New Global Constants
11. Changes to INI File Handling
updated UPGRADING so far
2014-08-22 19:35:07 +08:00
12. Windows Support
Clear NEWS, UPGRADING and UPGRADING.INTERNALS
2019-01-28 17:34:31 +08:00
13. Other Changes
14. Performance Improvements
Reset this document
2010-03-25 00:23:50 +08:00
========================================
Align section headings with the latest (5.4) migration on-line doc. This will aid future reuse of UPGRADING text.
2012-03-06 04:14:04 +08:00
1. Backward Incompatible Changes
Reset this document
2010-03-25 00:23:50 +08:00
========================================
Forbid dynamic calls to scope introspection functions Per RFC: https://wiki.php.net/rfc/forbid_dynamic_scope_introspection
2016-04-25 05:49:52 +08:00
ext/bz2: Check int params of bzcompress() are correct (#16108) Also add a TODO to check the length of the source strings
2024-09-29 05:38:53 +08:00
- BZ2:
. bzcompress() now throws a ValueError when $block_size is not between
1 and 9.
UPGRADING: Fix parameter name in `bzcompress` `work_factor` param Follow-up to GH-16108, to add the `$` sign to the `work_factor` paremter mention in the `UPGRADING` file.
2024-10-07 14:49:04 +08:00
. bzcompress() now throws a ValueError when $work_factor is not between
ext/bz2: Check int params of bzcompress() are correct (#16108) Also add a TODO to check the length of the source strings
2024-09-29 05:38:53 +08:00
0 and 250.
Fix GH-16665: \array and \callable should not be usable This list was initially introduced in 53a40386, but never included array or callable. I suppose this is because int & friends are not actual tokens, while array and callable are. This means it was never possible to do class array, which is probably the reason this was overlooked. Closes GH-16683.
2024-11-03 01:52:10 +08:00
- Core:
. It is no longer possible to use "array" and "callable" as class alias names
in class_alias().
ext/ldap: Throw a ValueError when passing an unknown option
2024-09-28 07:33:53 +08:00
- LDAP:
. ldap_get_option() and ldap_set_option() now throw a ValueError when
passing an invalid option.
Disallow enums in ArrayObject Closes GH-15775
2024-09-06 18:31:06 +08:00
- SPL:
. ArrayObject no longer accepts enums, as modifying the $name or $value
properties can break engine assumptions.
Align section headings with the latest (5.4) migration on-line doc. This will aid future reuse of UPGRADING text.
2012-03-06 04:14:04 +08:00
========================================
2. New Features
========================================
- Skeleton version taken directly from the scratchpad and tidied. @Lukas, Johannes: This is nowhere near complete, and may contain entries that would be happier in NEWS, but it's OK for the beta IMHO.
2009-01-29 01:23:28 +08:00
NEWS and UPGRADING for outerHTML Closes GH-15887.
2024-10-06 05:26:46 +08:00
- DOM:
. Added Dom\Element::$outerHTML.
Implement request #30622: make $namespace parameter functional This parameter never actually did anything and was forgotten about. We solve this by detecting when we have a $namespace argument (that won't conflict with the name argument) and creating a Clark notation name out of it. Closes GH-16123.
2024-09-30 03:45:55 +08:00
- XSL:
. The $namespace argument of XSLTProcessor::getParameter(),
XSLTProcessor::setParameter() and XSLTProcessor::removeParameter()
now actually works instead of being treated as empty.
This only works if the $name argument does not use Clark notation
and is not a QName because in those cases the namespace is taken
from the namespace href or prefix respectively.
Align section headings with the latest (5.4) migration on-line doc. This will aid future reuse of UPGRADING text.
2012-03-06 04:14:04 +08:00
========================================
Fixed numbering in UPGRADING file
2014-05-01 18:27:38 +08:00
3. Changes in SAPI modules
Align section headings with the latest (5.4) migration on-line doc. This will aid future reuse of UPGRADING text.
2012-03-06 04:14:04 +08:00
========================================
- Skeleton version taken directly from the scratchpad and tidied. @Lukas, Johannes: This is nowhere near complete, and may contain entries that would be happier in NEWS, but it's OK for the beta IMHO.
2009-01-29 01:23:28 +08:00
Align section headings with the latest (5.4) migration on-line doc. This will aid future reuse of UPGRADING text.
2012-03-06 04:14:04 +08:00
========================================
Fixed numbering in UPGRADING file
2014-05-01 18:27:38 +08:00
4. Deprecated Functionality
Align section headings with the latest (5.4) migration on-line doc. This will aid future reuse of UPGRADING text.
2012-03-06 04:14:04 +08:00
========================================
- Skeleton version taken directly from the scratchpad and tidied. @Lukas, Johannes: This is nowhere near complete, and may contain entries that would be happier in NEWS, but it's OK for the beta IMHO.
2009-01-29 01:23:28 +08:00
Deprecate mhash constants The mhash functions already have been deprecated as of PHP 8.1.0[1], but the respective constants appear to have been missed. We catch up on that. [1] <https://wiki.php.net/rfc/deprecations_php_8_1#mhash_function_family> Closes GH-16569.
2024-10-24 21:46:58 +08:00
- Hash:
The MHASH_* constants have been deprecated. These have been overlooked
when the mhash*() function family has been deprecated per
https://wiki.php.net/rfc/deprecations_php_8_1#mhash_function_family
Align section headings with the latest (5.4) migration on-line doc. This will aid future reuse of UPGRADING text.
2012-03-06 04:14:04 +08:00
========================================
Fixed numbering in UPGRADING file
2014-05-01 18:27:38 +08:00
5. Changed Functions
Align section headings with the latest (5.4) migration on-line doc. This will aid future reuse of UPGRADING text.
2012-03-06 04:14:04 +08:00
========================================
Missing items
2009-06-24 03:40:31 +08:00
[skip ci] UPGRADING/NEWS changes
2024-10-14 19:42:01 +08:00
- Zlib:
. The "use_include_path" argument for the
gzfile, gzopen and readgzfile functions had been changed
from int to boolean.
ext/pdo_pgsql: Expanding COPY input from an array to an iterable close GH-15893
2024-09-15 15:57:18 +08:00
- PDO_PGSQL:
. PDO::pgsqlCopyFromArray also supports inputs as Iterable.
Fix / implement GH-15287: add a lazy fetch to Pdo\PgSql Make Pdo\PgSql accept Pdo::setAttribute(PDO::ATTR_PREFETCH, 0) to enter libpq's single row mode. This avoids storing the whole result set in memory before being able to call the first fetch(). close GH-15750
2024-09-04 04:43:58 +08:00
. Pdo\Pgsql::setAttribute and Pdo\Pgsql::prepare supports
PDO::ATTR_PREFETCH sets to 0 which set to lazy fetch mode.
In this mode, statements cannot be run parallely.
ext/pdo_pgsql: Expanding COPY input from an array to an iterable close GH-15893
2024-09-15 15:57:18 +08:00
ext/pgsql: pgsql_copy_from to support iterable. inspired from the Pdo\Pgsql new feature GH-15893. close GH-16124
2024-09-30 04:28:40 +08:00
- PGSQL:
. pg_copy_from also supports inputs as Iterable.
Align section headings with the latest (5.4) migration on-line doc. This will aid future reuse of UPGRADING text.
2012-03-06 04:14:04 +08:00
========================================
Fixed numbering in UPGRADING file
2014-05-01 18:27:38 +08:00
6. New Functions
[ci skip] Fix formatting in UPGRADING - Remove `k` typo that was accidentally added in a headline separator. - Remove premature hard break after very short line length. - Remove dots at the end of constant lists (not used in 8.2).
2022-09-05 02:59:26 +08:00
========================================
[ci skip] NEWS UPGRADING
2022-09-05 02:52:21 +08:00
curl: Add `curl_multi_get_handles()` (#16363) see https://curl.se/libcurl/c/curl_multi_get_handles.html
2024-10-16 22:24:04 +08:00
- Curl:
. curl_multi_get_handles() allows retrieving all CurlHandles current
attached to a CurlMultiHandle. This includes both handles added using
curl_multi_add_handle() and handles accepted by CURLMOPT_PUSHFUNCTION.
[ci skip] Fix typo
2024-09-30 01:33:47 +08:00
- PGSQL:
ext/pgsql: adding pg_close_stmt. up to postgresql 17, when done with a prepared statement, we could release it with DEALLOCATE sql command which is fine ; until we want to implement a cache solution based on statement ids. Since PostgreSQL 17, PQclosePrepared uses internally the `close` protocol allowing to reuse the statement name while still freeing it. Since the close protocol implementation had been added on libpq within this release, no way to reimplement it. close GH-14584
2024-06-16 20:01:36 +08:00
. pg_close_stmt offers an alternative way to close a prepared
statement from the DEALLOCATE sql command in that we can reuse
its name afterwards.
Add ReflectionConstant::getFileName() Allow determining the name of the file that defined a constant, when the constant was defined in userland code via const or define(). For constants defined by PHP core or extensions, false is returned, matching the existing getFileName() methods on other reflection classes. Fixes GH-15723 Closes GH-15847
2024-09-12 09:43:47 +08:00
- Reflection:
. ReflectionConstant::getFileName() was introduced.
Align section headings with the latest (5.4) migration on-line doc. This will aid future reuse of UPGRADING text.
2012-03-06 04:14:04 +08:00
========================================
Fixed numbering in UPGRADING file
2014-05-01 18:27:38 +08:00
7. New Classes and Interfaces
Align section headings with the latest (5.4) migration on-line doc. This will aid future reuse of UPGRADING text.
2012-03-06 04:14:04 +08:00
========================================
- Skeleton version taken directly from the scratchpad and tidied. @Lukas, Johannes: This is nowhere near complete, and may contain entries that would be happier in NEWS, but it's OK for the beta IMHO.
2009-01-29 01:23:28 +08:00
Align section headings with the latest (5.4) migration on-line doc. This will aid future reuse of UPGRADING text.
2012-03-06 04:14:04 +08:00
========================================
updated UPGRADING
2015-02-10 15:56:18 +08:00
8. Removed Extensions and SAPIs
Align section headings with the latest (5.4) migration on-line doc. This will aid future reuse of UPGRADING text.
2012-03-06 04:14:04 +08:00
========================================
- Skeleton version taken directly from the scratchpad and tidied. @Lukas, Johannes: This is nowhere near complete, and may contain entries that would be happier in NEWS, but it's OK for the beta IMHO.
2009-01-29 01:23:28 +08:00
Align section headings with the latest (5.4) migration on-line doc. This will aid future reuse of UPGRADING text.
2012-03-06 04:14:04 +08:00
========================================
Fixed numbering in UPGRADING file
2014-05-01 18:27:38 +08:00
9. Other Changes to Extensions
Align section headings with the latest (5.4) migration on-line doc. This will aid future reuse of UPGRADING text.
2012-03-06 04:14:04 +08:00
========================================
Update NEWS and UPGRADING
2016-07-03 18:43:30 +08:00
ext/readline: update return typehints from `bool` to `true` (#16545) These always return true
2024-10-26 00:35:48 +08:00
- Readline:
. The return types of readline_add_history(), readline_clear_history(), and
readline_callback_handler_install() have been changed to true, rather
than bool.
Align section headings with the latest (5.4) migration on-line doc. This will aid future reuse of UPGRADING text.
2012-03-06 04:14:04 +08:00
========================================
Fixed numbering in UPGRADING file
2014-05-01 18:27:38 +08:00
10. New Global Constants
Align section headings with the latest (5.4) migration on-line doc. This will aid future reuse of UPGRADING text.
2012-03-06 04:14:04 +08:00
========================================
Reset this document
2010-03-25 00:23:50 +08:00
ext/posix: adding POSIX_SC_OPEN_MAX constant. returns the number of file descriptors that a process can handle. e.g. useful after pcntl_fork() to close all the file descriptors up to that boundary. close GH-16681
2024-11-02 20:28:08 +08:00
- POSIX:
. POSIX_SC_OPEN_MAX.
Align section headings with the latest (5.4) migration on-line doc. This will aid future reuse of UPGRADING text.
2012-03-06 04:14:04 +08:00
========================================
Fixed numbering in UPGRADING file
2014-05-01 18:27:38 +08:00
11. Changes to INI File Handling
Align section headings with the latest (5.4) migration on-line doc. This will aid future reuse of UPGRADING text.
2012-03-06 04:14:04 +08:00
========================================
- use TSRMLS_CC instead of TSRMLS_FETCH in virtual_file_ex
2010-08-30 17:38:47 +08:00
updated UPGRADING so far
2014-08-22 19:35:07 +08:00
========================================
12. Windows Support
========================================
Unify types of PHP_VERSION and friends on Windows For `phpize` builds, all three version variables are numbers, but for `buildconf` builds, all are strings. This can yield surprising results when extensions create their `PHP_VERSION_ID` like 10000 * PHP_VERSION + 100 * PHP_MINOR_VERSION + PHP_RELEASE_VERSION Since `phpize` builds are way more common for external extensions nowadays, we change the types for `buildconf` builds. Closes GH-16247.
2024-10-05 21:16:49 +08:00
* The configuration variables PHP_VERSION, PHP_MINOR_VERSION, and
PHP_RELEASE_VERSION are now always numbers. Previously, they have been
strings for buildconf builds.
FFI: support symbol lookup without specifying lib on Windows This works similar to `dlsym(RTLD_DEFAULT, …)` with the caveat that symbols on Windows may not be unique, and are usually qualified by the module they are exported from. That means that wrong symbols may be fetched, potentially causing serious issues; therefore this usage is not recommended for production purposes, but is a nice simplification for quick experiments and the ext/ffi test suite. Closes GH-16351.
2024-10-11 23:50:15 +08:00
* FFI:
. It is no longer necessary to specify the library when using FFI::cdef()
and FFI::load(). However, this convenience feature should not be used in
production.
Document pkg-config related changes Creating a separate section in UPGRADING for this, as there are a lot of these, and there's going to be more of them.
2019-01-15 17:13:39 +08:00
========================================
Clear NEWS, UPGRADING and UPGRADING.INTERNALS
2019-01-28 17:34:31 +08:00
13. Other Changes
Align section headings with the latest (5.4) migration on-line doc. This will aid future reuse of UPGRADING text.
2012-03-06 04:14:04 +08:00
========================================
Add performance improvement section to UPGRADING [ci skip]
2018-12-27 05:26:01 +08:00
========================================
Clear NEWS, UPGRADING and UPGRADING.INTERNALS
2019-01-28 17:34:31 +08:00
14. Performance Improvements
Add performance improvement section to UPGRADING [ci skip]
2018-12-27 05:26:01 +08:00
========================================
Optimize in-memory XMLWriter We're currently using a libxml buffer, which requires copying the buffer to zend_strings every time we want to output the string. Furthermore, its use of the system allocator instead of ZendMM makes it not count towards the memory_limit and hinders performance. This patch adds a custom writer such that the strings are written to a smart_str instance, using ZendMM for improved performance, and giving the ability to not copy the string in the common case where flush has empty set to true. Closes GH-16120.
2024-09-29 18:35:36 +08:00
- XMLWriter:
. Improved performance and reduce memory consumption.
Reference in New Issue Copy Permalink