PHP Wiki

deprecations_php_8_6 - Add commit link for mysqli_stmt_init

girgias (girgias@undisclosed.example.com) — 2026-08-15T12:11:34+00:00

2026/08/12 17:11		current
Line 43:		Line 43:
	* [[https://github.com/php/php-src/commit/2c1c61de07953f901d95fd93e3ce79b50032e65c\|Deprecate spl_object_hash()]]		* [[https://github.com/php/php-src/commit/2c1c61de07953f901d95fd93e3ce79b50032e65c\|Deprecate spl_object_hash()]]
	* Deprecate SplFileObject CSV methods		* Deprecate SplFileObject CSV methods
-	* Deprecate mysql	+	* [[https://github.com/php/php-src/commit/fd8706c64e2975116aae0bef6f129755b6d27dc5\|Deprecate mysqli_stmt_init]]
	* [[https://github.com/php/php-src/commit/d5ecbe1d93694497bd46483bdbb169f2ec8655b4\|Deprecate mysqli_get_charset()]]		* [[https://github.com/php/php-src/commit/d5ecbe1d93694497bd46483bdbb169f2ec8655b4\|Deprecate mysqli_get_charset()]]
	* Deprecate passing a $sessionhandler object to session_set_save_handler() which does not contain the create_sid() and validateId() methods		* Deprecate passing a $sessionhandler object to session_set_save_handler() which does not contain the create_sid() and validateId() methods

rfc - throw_error_for_invalid_characters_for_number_base

sjoerd (sjoerd@undisclosed.example.com) — 2026-08-14T10:14:55+00:00

2026/08/13 11:03		current
Line 19:		Line 19:
	This section is for RFCs that have been announced on the PHP "internals" mail list.		This section is for RFCs that have been announced on the PHP "internals" mail list.

		+	* [[rfc:throw_error_for_invalid_characters_for_number_base\|Throw ValueError for invalid characters in number base functions]] (Created 2026-08-11)
	* [[rfc:function-autoloading-five-oh\|Function Autoloading (mark 5)]] (created 2026-06-16, discussion started 2026-06-16, voting started 2026-07-30)		* [[rfc:function-autoloading-five-oh\|Function Autoloading (mark 5)]] (created 2026-06-16, discussion started 2026-06-16, voting started 2026-07-30)
	* [[rfc:reldateformatter\|IntlRelativeDateTimeFormatter]] (Created 2026-08-07, Discussion started 2026-08-07)		* [[rfc:reldateformatter\|IntlRelativeDateTimeFormatter]] (Created 2026-08-07, Discussion started 2026-08-07)
Line 79:		Line 80:
	* [[rfc:deprecations_php_8_7\|Deprecations for PHP 8.7]] (Created 2026-08-12)		* [[rfc:deprecations_php_8_7\|Deprecations for PHP 8.7]] (Created 2026-08-12)
	* [[rfc:array_search_range\|Array Search Range]] (Created 2026-08-12)		* [[rfc:array_search_range\|Array Search Range]] (Created 2026-08-12)
-	* [[rfc:throw_error_for_invalid_characters_for_number_base\|Throw ValueError for invalid characters in number base functions]] (Created 2026-08-11)
	* [[rfc:immutable_collections\|Native Immutable Collections — "vec", "set" and "tuple"]] (Created 2026-08-04)		* [[rfc:immutable_collections\|Native Immutable Collections — "vec", "set" and "tuple"]] (Created 2026-08-04)
	* [[rfc:direction_aware_property_resolution\|Direction Aware Property Resolution]] (Created 2026-07-14)		* [[rfc:direction_aware_property_resolution\|Direction Aware Property Resolution]] (Created 2026-07-14)

throw_error_for_invalid_characters_for_number_base

sjoerd (sjoerd@undisclosed.example.com) — 2026-08-14T10:09:38+00:00

2026/08/14 10:09		current
Line 86:		Line 86:
	Primary Vote requiring a 2/3 majority to accept the RFC:		Primary Vote requiring a 2/3 majority to accept the RFC:

-	<doodle title="Throw a ''ValueError'' for invalid characters in number base conversion functions?" voteType="single" closed="true" closeon="2026-01-01T15:30:00Z">	+	<doodle title="Throw a ValueError for invalid characters in number base conversion functions?" voteType="single" closed="true" closeon="2026-01-01T15:30:00Z">
	* Yes		* Yes
	* No		* No

php86 - update beta1

sergey (sergey@undisclosed.example.com) — 2026-08-13T15:14:14+00:00

2026/08/13 15:08		current
Line 18:		Line 18:
	\| Jul 30 2026 \| Alpha 3 [[https://www.php.net/archive/2026.php#2026-07-30-3\|Announce]] [[https://downloads.php.net/~mbeccati/\|Files]] \|		\| Jul 30 2026 \| Alpha 3 [[https://www.php.net/archive/2026.php#2026-07-30-3\|Announce]] [[https://downloads.php.net/~mbeccati/\|Files]] \|
	\| Aug 11 2026 \| All RFCs targeting 8.6 should have been merged, so they can be in Beta 1. \|		\| Aug 11 2026 \| All RFCs targeting 8.6 should have been merged, so they can be in Beta 1. \|
-	\| Aug 13 2026 \| Beta 1 + Soft feature freeze: all RFCs must have their voting concluded [[https://www.php.net/archive/2025.php#2025-08-14-1\|Announce]] [[https://downloads.php.net/~svpernova09/\|Files]] \|	+	\| Aug 13 2026 \| Beta 1 + Soft feature freeze: all RFCs must have their voting concluded [[https://www.php.net/archive/2026.php#2026-08-13-1\|Announce]] [[https://downloads.php.net/~svpernova09/\|Files]] \|
	\| Aug 27 2026 \| Beta 2 \|		\| Aug 27 2026 \| Beta 2 \|
	\| Sep 10 2026 \| Beta 3 \|		\| Sep 10 2026 \| Beta 3 \|

array_search_range

sepehrphp (sepehrphp@undisclosed.example.com) — 2026-08-12T22:47:12+00:00

2026/08/12 14:38		current
Line 6:		Line 6:
	* Email: [[mailto:sepehrphpr@gmail.com\|sepehrphpr@gmail.com]]		* Email: [[mailto:sepehrphpr@gmail.com\|sepehrphpr@gmail.com]]
	* Discussion thread: https://externals.io/message/132200		* Discussion thread: https://externals.io/message/132200
-	* Target PHP Version: PHP 8.6	+	* Target PHP Version: PHP 8.7
	* Status: Draft		* Status: Draft
	* Implementation: [[https://github.com/php/php-src/pull/YOUR_PR_NUMBER\|PR #YOUR_PR_NUMBER (Pending)]]		* Implementation: [[https://github.com/php/php-src/pull/YOUR_PR_NUMBER\|PR #YOUR_PR_NUMBER (Pending)]]

deprecations_php_8_7 - created

daniels (daniels@undisclosed.example.com) — 2026-08-12T18:45:17+00:00

2026/08/16 09:15	current
Line 1:	Line 1:
	+	====== PHP RFC: Deprecations for PHP 8.7 ======
	+	* Date: 2026-08-12
	+	* Authors:
	+	* Daniel Scherzer <daniel.e.scherzer@gmail.com>
	+	* Status: Draft
	+	* Discussion thread: Not started yet
	+	* Voting thread: tbd
	+
	+	===== Introduction =====
	+
	+	The RFC proposes to deprecate the listed functionality in PHP 8.7 and remove it in PHP 9 (except where otherwise noted).
	+
	+	The following list provides a short overview of the functionality targeted for deprecation, while more detailed explanation is provided in the Proposal section:
	+
	+	* Deprecate <php>is_a</php> with $object_or_class not being a string or object
	+	* Deprecate <php>is_subclass_of</php> with $object_or_class not being a string or object
	+
	+	===== Proposals =====
	+
	+	Each feature proposed for deprecation is voted separately and requires a 2/3 majority.
	+	All votes refer to deprecation in PHP 8.7 and removal in PHP 9 (except where otherwise noted).
	+
	+	==== Example Deprecation ====
	+
	+	* Author: Name <name@example.com>
	+
	+	Description
	+
	+	==== Deprecate is_a() with $object_or_class not being a string or object ====
	+
	+	* Author: Daniel Scherzer <daniel.e.scherzer@gmail.com>
	+
	+	<php>is_a</php> is used to check if an object or class name is an instance of some other named class/interface. The first parameter can be either an object to check, or the name of a class. It can also be something other than a string or object, in which case the function will always return false. I.e. code like <php>is_a(5, "int")</php> or <php>is_a(true, "bool")</php> will always return false.
	+
	+	Given that <php>is_a</php> always returns false when the first parameter is something other than a string or object, we propose to deprecate providing non-string non-object parameters. If the type of a parameter is not known, the <php>is_a</php> call can be preceded with a call to <php>is_object</php>.
	+
	+	If accepted, calling <php>is_a</php> with non-string non-object parameters will emit a deprecation similar to the following:
	+
	+	<blockquote>
	+	Deprecated: Calling is_a() with $object_or_class of type %s is deprecated.
	+	</blockquote>
	+
	+	==== Deprecate is_subclass_of() with $object_or_class not being a string or object ====
	+
	+	* Author: Daniel Scherzer <daniel.e.scherzer@gmail.com>
	+
	+	<php>is_subclass_of</php> is used to check if an object or class name is an instance of a subclass of some other named class, or an instance of an interface. It works similarly to <php>is_a</php>, except when an object's class is the exact same as the class to check. Like <php>is_a</php>, the first parameter can be either an object to check, or the name of a class. It can also be something other than a string or object, in which case the function will always return false. I.e. code like <php>is_subclass_of(5, "int")</php> or <php>is_subclass_of(true, "bool")</php> will always return false.
	+
	+	Given that <php>is_subclass_of</php> always returns false when the first parameter is something other than a string or object, we propose to deprecate providing non-string non-object parameters. If the type of a parameter is not known, the <php>is_subclass_of</php> call can be preceded with a call to <php>is_object</php>.
	+
	+	Unlike <php>is_a</php>, <php>is_subclass_of</php> also semantically makes no sense for non objects (or string class names) because there is no subclassing concept for non-objects.
	+
	+	If accepted, calling <php>is_subclass_of</php> with non-string non-object parameters will emit a deprecation similar to the following:
	+
	+	<blockquote>
	+	Deprecated: Calling is_subclass_of() with $object_or_class of type %s is deprecated.
	+	</blockquote>

array_search_reange

sepehrphp (sepehrphp@undisclosed.example.com) — 2026-08-11T21:02:41+00:00

2026/08/11 15:40		current
Line 1:		Line 1:
-	====== PHP RFC: array_search_reange() ======	+	====== PHP RFC: array_search_range() ======

	* Version: 0.1 (Draft)		* Version: 0.1 (Draft)
	* Date: 2026-08-11		* Date: 2026-08-11
	* Author: Sepehr Mahmoudi		* Author: Sepehr Mahmoudi
-	* Email: sepehrphpr@gmail.com	+	* Email: [[mailto:sepehrphpr@gmail.com\|sepehrphpr@gmail.com]]
	* Target PHP Version: PHP 8.6		* Target PHP Version: PHP 8.6
	* Status: Draft		* Status: Draft
-	* Implementation: Not yet available	+	* Implementation: Not yet available (PR in progress)

	===== Introduction =====		===== Introduction =====

-	This RFC proposes a new core function named ''array_search_reange()''.	+	This RFC proposes a new core function named ''array_search_range()''.

-	The function searches for a value within a positional reange of an existing	+	The function searches for a value within a positional range of an existing array.
-	array. It is intended for cases where an application needs to search only part	+	It is intended for cases where an application needs to search only a part of an
-	of an array, without first creating an intermediate array using ''array_slice()''.	+	array, without first creating an intermediate array using ''array_slice()''.
-		+
-	The proposed function preserves the familiar return style of ''array_search()''	+
-	while adding parameters that define the reange in which the search is	+
-	performed.	+

	===== Proposed Function Signature =====		===== Proposed Function Signature =====

	<code php>		<code php>
-	function array_search_reange(	+	function array_search_range(
	mixed $needle,		mixed $needle,
	array $haystack,		array $haystack,
Line 35:		Line 31:
	===== Summary =====		===== Summary =====

-	''array_search_reange()'' searches for the first matching value in a selected	+	''array_search_range()'' searches for the first matching value in a selected
-	reange of an array and returns the original key of that value.	+	range of an array and returns the original key of that value.

-	Like ''array_search()'', the function returns:	+	Like ''array_search()'', it returns the actual key of the element. If no value
-		+	matches, it returns ''false''.
-	* An ''int'' key when the matched element has an integer key.	+
-	* A ''string'' key when the matched element has a string key.	+
-	* ''false'' when no matching value exists in the selected reange.	+
-		+
-	The reange is defined by two parameters:	+
-		+
-	* ''$offset'': The zero-based positional offset at which searching starts.	+
-	* ''$length'': The number of elements to inspect after ''$offset''.	+

	===== Motivation =====		===== Motivation =====

-	PHP already provides ''array_search()'' for searching an entire array. When	+	Currently, searching a portion of an array requires ''array_slice()'':
-	developers need to search only a portion of an array, they often combine	+
-	''array_slice()'' and ''array_search()''.	+
-		+
-	However, creating a sliced array solely for a single search operation is often	+
-	unnecessary. The proposed function allows PHP to iterate over the requested	+
-	reange of the original array directly, avoiding the allocation of an	+
-	intermediate array.	+
-		+
-	===== Proposal =====	+
-		+
-	A new function named ''array_search_reange()'' is added to PHP.	+

	<code php>		<code php>
-	function array_search_reange(	+	$range = array_slice($languages, 100, 50, true);
-	mixed $needle,	+	$key = array_search('PHP', $range, true);
-	array $haystack,	+
-	int $offset = 0,	+
-	?int $length = null,	+
-	bool $strict = false,	+
-	): int\|string\|false {}	+
	</code>		</code>

-	The function searches the original array in its normal iteration order.	+	This approach has two main drawbacks:
-	It begins at the positional offset specified by ''$offset'' and searches at	+	1. It creates an intermediate array, which consumes additional memory.
-	most ''$length'' elements when a length is provided.	+	2. It requires two function calls instead of one.
		+
		+	The proposed function iterates over the original array directly, avoiding
		+	unnecessary memory allocation for an intermediate structure.

	===== Parameters =====		===== Parameters =====
Line 87:		Line 62:

	==== $offset ====		==== $offset ====
-	The zero-based positional offset at which searching begins. This refers to the	+	The zero-based positional offset at which searching begins.
-	position in the array's iteration order, defining the start of the **reange**.	+	* If $offset is negative, searching begins relative to the end of the array.
		+	* If $offset is out of bounds (greater than array size), the function returns ''false''.

	==== $length ====		==== $length ====
-	The number of elements to inspect after applying ''$offset''.	+	The number of elements to inspect.
-	When ''$length'' is ''null'', the function searches from ''$offset'' to the end	+	* When ''null'', the function searches from ''$offset'' to the end of the array.
-	of the array.	+	* If $length is 0, the function returns ''false''.
		+	* If $length is negative, the search excludes that number of elements from the end.

	==== $strict ====		==== $strict ====
-	When ''$strict'' is ''true'', values are compared using strict comparison.	+	Whether to use strict comparison (''==='' vs ''=='').

	===== Detailed Behavior =====		===== Detailed Behavior =====

-	==== Positional Reange Versus Array Keys ====	+	==== Positional Range Versus Array Keys ====
-		+	The range is defined by positional order, not by the values of keys.
-	The reange is based on positions in the array's iteration order, not on key	+
-	values.	+
	<code php>		<code php>
-	$array = [	+	$array = [100 => 'alpha', 500 => 'target'];
-	100 => 'alpha',	+	// Search starts at the 2nd element (index 1), even if its key is 500
-	'php' => 'beta',	+	$key = array_search_range('target', $array, 1, 1, true);
-	500 => 'target',	+
-	];	+
-		+
-	// Searches for target in a reange starting at offset 2 (positional)	+
-	$key = array_search_reange('target', $array, 2, 1, true);	+
	var_dump($key); // int(500)		var_dump($key); // int(500)
	</code>		</code>

-	==== Original Keys Are Returned ====	+	==== Error Handling ====
-		+	* If $offset is invalid or outside the array bounds, the function returns ''false''.
-	The function returns the key from the original array, regardless of the	+	* This function does not throw exceptions for valid input ranges, maintaining
-	reange selected.	+	consistency with ''array_slice()''.

	===== Examples =====		===== Examples =====

	==== Basic Search ====		==== Basic Search ====
-
	<code php>		<code php>
	$languages = ['HTML', 'CSS', 'JavaScript', 'PHP', 'Python'];		$languages = ['HTML', 'CSS', 'JavaScript', 'PHP', 'Python'];
-	$key = array_search_reange('PHP', $languages);	+	$key = array_search_range('PHP', $languages, 0, null, true);
	var_dump($key); // int(3)		var_dump($key); // int(3)
	</code>		</code>

-	==== Search Within a Specific Reange ====	+	==== Search Within a Specific Range ====
-		+
-	This example searches only positions 2, 3, and 4.	+
	<code php>		<code php>
-	$items = ['zero', 'one', 'two', 'target', 'four', 'target', 'six'];	+	$items = ['zero', 'one', 'two', 'target', 'four', 'target'];
-	$key = array_search_reange('target', $items, 2, 3, true);	+	$key = array_search_range('target', $items, 2, 3, true);
	var_dump($key); // int(3)		var_dump($key); // int(3)
	</code>		</code>

	==== Persian Associative Array Example ====		==== Persian Associative Array Example ====
-
	<code php>		<code php>
-	$users = [	+	$users = ['u_101' => 'علی', 'u_103' => 'سپهر'];
-	'u_101' => 'علی',	+	$key = array_search_range('سپهر', $users, 0, null, true);
-	'u_102' => 'مینا',	+
-	'u_103' => 'سپهر',	+
-	'u_104' => 'رضا',	+
-	];	+
-		+
-	$key = array_search_reange('سپهر', $users, 1, 2, true);	+
	var_dump($key); // string(5) "u_103"		var_dump($key); // string(5) "u_103"
	</code>		</code>

-	===== Comparison with array_slice() =====	+	===== Performance Considerations =====
-		+
-	The proposed API avoids creating an intermediate array when its only purpose	+
-	is to be searched once. It makes the reange-limited search intention explicit.	+
-		+
-	===== Implementation and Merge Plan =====	+
-		+
-	This RFC is currently a draft. I plan to prepare a php-src implementation	+
-	after the API design and parameter behavior receive feedback.	+
-		+
-	The implementation will include:	+
-		+
-	* The core implementation of ''array_search_reange()''.	+
-	* PHPT tests covering all cases (indexed, associative, strict/loose, negative	+
-	offsets, negative lengths, etc.).	+
-	* Benchmark results comparing this direct reange search with the	+
-	''array_slice()'' pattern.	+
-		+
-	The implementation will be submitted as a pull request. It will not be merged	+
-	until the RFC is accepted and the implementation is reviewed.	+
-		+
-	===== Future Plans =====	+

-	My roadmap for these features is as follows:	+	Compared to ''array_slice()'', this function avoids creating a temporary
		+	''HashTable''. For an array of 100,000 elements, searching a range avoids
		+	allocating memory for the temporary slice, reducing GC pressure and
		+	CPU cycles required for array duplication.

-	1. Finalize the design and implementation of ''array_search_reange()''.	+	===== Implementation Plan =====
-	2. Complete the discussion and merge the pull request into the PHP source.	+
-	3. Prepare the next feature: ''str_mask()''.	+

-	Regarding the future constant for array searching, it remains a separate	+	The implementation will focus on direct ''HashTable'' iteration. The code
-	discussion. I plan to design and document a constant for reange-limited	+	will be submitted as a Pull Request to [[https://github.com/php/php-src\|php-src]].
-	searching only after ''array_search_reange()'' is stable and integrated.	+	I plan to include full PHPT test coverage for edge cases including negative offsets,
		+	negative lengths, and mixed key types.

	===== Proposed PHP Version =====		===== Proposed PHP Version =====

-	The proposed target version for this feature is PHP 8.6.	+	PHP 8.6.

	===== Changelog =====		===== Changelog =====

readonly_property_defaults - Moved to implemented

nicksdot (nicksdot@undisclosed.example.com) — 2026-08-11T19:06:51+00:00

2026/08/07 14:21		current
Line 4:		Line 4:
	* Date: 2026-07-04		* Date: 2026-07-04
	* Author: Nick Sdot, php@nicksdot.dev		* Author: Nick Sdot, php@nicksdot.dev
-	* Status: Accepted	+	* Status: Implemented
-	* Implementation: https://github.com/php/php-src/pull/22588	+	* Implementation: https://github.com/php/php-src/commit/a2640aebc914b3c6fc997c379b1f91a2c4db8c55
	* Discussion thread: https://news-web.php.net/php.internals/131760		* Discussion thread: https://news-web.php.net/php.internals/131760
	* Voting thread: https://news-web.php.net/php.internals/132096		* Voting thread: https://news-web.php.net/php.internals/132096
Line 349:		Line 349:
	===== Implementation =====		===== Implementation =====

-	tbd	+	https://github.com/php/php-src/commit/a2640aebc914b3c6fc997c379b1f91a2c4db8c55

	===== References =====		===== References =====

pipe_assignment_operator

cdwhite3 (cdwhite3@undisclosed.example.com) — 2026-08-11T04:31:57+00:00

2026/07/28 04:31		current
Line 4:		Line 4:
	* Date: 2026-07-07		* Date: 2026-07-07
	* Author: Caleb White, cdwhite3@pm.me		* Author: Caleb White, cdwhite3@pm.me
-	* Status: Voting	+	* Status: Declined
	* Target version: Next PHP 8.x (8.6)		* Target version: Next PHP 8.x (8.6)
	* Implementation: https://github.com/php/php-src/pull/22633		* Implementation: https://github.com/php/php-src/pull/22633
Line 201:		Line 201:
	This RFC requires a 2/3 majority to pass.		This RFC requires a 2/3 majority to pass.

-	<doodle title="Implement the pipe assignment operator as outlined in the RFC?" voteType="single" closed="false" closeon="2026-08-11T04:30:00Z">	+	<doodle title="Implement the pipe assignment operator as outlined in the RFC?" voteType="single" closed="true" closeon="2026-08-11T04:30:00Z">
	* Yes		* Yes
	* No		* No

uri_followup

kocsismate (kocsismate@undisclosed.example.com) — 2026-08-09T12:08:54+00:00

2026/08/09 12:08		current
Line 602:		Line 602:
	The following modes are supported:		The following modes are supported:

-	* Uri\Rfc3986\UriPercentEncoder****	+	* Uri\Rfc3986\UriPercentEncodingMode****
	* UserInfo: Besides [[https://datatracker.ietf.org/doc/html/rfc3986#section-2.3\|unreserved characters]] and [[https://datatracker.ietf.org/doc/html/rfc3986#section-2.2\|sub-delimiters]], it also allows the following characters to be present: ":". Any other characters (including "%" as well) are percent-encoded.		* UserInfo: Besides [[https://datatracker.ietf.org/doc/html/rfc3986#section-2.3\|unreserved characters]] and [[https://datatracker.ietf.org/doc/html/rfc3986#section-2.2\|sub-delimiters]], it also allows the following characters to be present: ":". Any other characters (including "%" as well) are percent-encoded.
	* RegisteredNameHost: [[https://datatracker.ietf.org/doc/html/rfc3986#section-2.3\|Unreserved characters]], and [[https://datatracker.ietf.org/doc/html/rfc3986#section-2.2\|sub-delimiters]] are allowed to be present. Any other characters (including "%" as well) are percent-encoded. Please note that IPv4, IPv6, as well as IPvFuture hosts don't support percent-encoding, and they have a much more restricted syntax, therefore this enum case is only applicable for registered names.		* RegisteredNameHost: [[https://datatracker.ietf.org/doc/html/rfc3986#section-2.3\|Unreserved characters]], and [[https://datatracker.ietf.org/doc/html/rfc3986#section-2.2\|sub-delimiters]] are allowed to be present. Any other characters (including "%" as well) are percent-encoded. Please note that IPv4, IPv6, as well as IPvFuture hosts don't support percent-encoding, and they have a much more restricted syntax, therefore this enum case is only applicable for registered names.
Line 608:		Line 608:
	* PathSegment: Besides [[https://datatracker.ietf.org/doc/html/rfc3986#section-2.3\|unreserved characters]] and [[https://datatracker.ietf.org/doc/html/rfc3986#section-2.2\|sub-delimiters]], it also allows the following characters to be present: ":", "@". Any other characters (including "%" as well) are percent-encoded.		* PathSegment: Besides [[https://datatracker.ietf.org/doc/html/rfc3986#section-2.3\|unreserved characters]] and [[https://datatracker.ietf.org/doc/html/rfc3986#section-2.2\|sub-delimiters]], it also allows the following characters to be present: ":", "@". Any other characters (including "%" as well) are percent-encoded.
	* Query: Besides [[https://datatracker.ietf.org/doc/html/rfc3986#section-2.3\|unreserved characters]] and [[https://datatracker.ietf.org/doc/html/rfc3986#section-2.2\|sub-delimiters]], it also allows the following characters to be present: ":", "@", "/", and "?". Any other characters (including "%" as well) are percent-encoded.		* Query: Besides [[https://datatracker.ietf.org/doc/html/rfc3986#section-2.3\|unreserved characters]] and [[https://datatracker.ietf.org/doc/html/rfc3986#section-2.2\|sub-delimiters]], it also allows the following characters to be present: ":", "@", "/", and "?". Any other characters (including "%" as well) are percent-encoded.
-	* FormQuery: It is mostly the same as ''Uri\Rfc3986\UriPercentEncoder::Query'', but it behaves according to the ''application/x-www-form-urlencode'' media type rather than RFC 3986. The only difference between the two is that " " is encoded as "+".	+	* FormQuery: It is mostly the same as ''Uri\Rfc3986\UriPercentEncodingMode::Query'', but it behaves according to the ''application/x-www-form-urlencode'' media type rather than RFC 3986. The only difference between the two is that " " is encoded as "+".
	* Fragment: Besides [[https://datatracker.ietf.org/doc/html/rfc3986#section-2.3\|unreserved characters]] and [[https://datatracker.ietf.org/doc/html/rfc3986#section-2.2\|sub-delimiters]], it also allows the following characters to be present: ":", "@", "/", and "?". Any other characters (including "%" as well) are percent-encoded.		* Fragment: Besides [[https://datatracker.ietf.org/doc/html/rfc3986#section-2.3\|unreserved characters]] and [[https://datatracker.ietf.org/doc/html/rfc3986#section-2.2\|sub-delimiters]], it also allows the following characters to be present: ":", "@", "/", and "?". Any other characters (including "%" as well) are percent-encoded.
	* AllReservedCharacters: All [[https://datatracker.ietf.org/doc/html/rfc3986#section-2.2\|reserved characters]] are percent-encoded. The rest of the characters are left as-is.		* AllReservedCharacters: All [[https://datatracker.ietf.org/doc/html/rfc3986#section-2.2\|reserved characters]] are percent-encoded. The rest of the characters are left as-is.

reldateformatter

weilindu (weilindu@undisclosed.example.com) — 2026-08-08T17:31:37+00:00

2026/08/08 17:31		current
Line 463:		Line 463:
	===== Rejected Features =====		===== Rejected Features =====

-	* Using a namespace only for this class. This would reduce the chance of	+	* Using a namespace only for this class. This would reduce the chance of userland class-name conflicts, but would be inconsistent with the existing ext/intl formatter classes.
-	userland class-name conflicts, but would be inconsistent with the existing	+	* Replacing this class's integer constants with PHP enums only for this class. This would improve type-safety locally, but would make this formatter different from adjacent intl APIs that expose ICU enum values as integer constants.
-	ext/intl formatter classes.	+
-	* Replacing this class's integer constants with PHP enums only for this class.	+
-	This would improve type-safety locally, but would make this formatter	+
-	different from adjacent intl APIs that expose ICU enum values as integer	+
-	constants.	+

	===== Changelog =====		===== Changelog =====

surface3d.png - created

pajoye (pajoye@undisclosed.example.com) — 2026-07-19T13:48:10+00:00

	current

scaled_on_load_rotate.png - created

pajoye (pajoye@undisclosed.example.com) — 2026-07-17T06:47:24+00:00

	current

watermarked.png - created

pajoye (pajoye@undisclosed.example.com) — 2026-07-17T03:57:25+00:00

	current

scale_entropy_visual_check.png - created

pajoye (pajoye@undisclosed.example.com) — 2026-07-14T03:12:03+00:00

	current

textcurve.png - created

pajoye (pajoye@undisclosed.example.com) — 2026-07-10T14:08:53+00:00

1783692513	current

gradient_art.png - created

pajoye (pajoye@undisclosed.example.com) — 2026-07-06T06:32:24+00:00

	current

tiger.png - created

pajoye (pajoye@undisclosed.example.com) — 2026-07-06T06:32:03+00:00

	current

gradient_operators.png - created

pajoye (pajoye@undisclosed.example.com) — 2026-07-06T06:31:36+00:00

	current

coroutine-lifecycle.svg - created

edmond (edmond@undisclosed.example.com) — 2025-04-16T07:24:46+00:00

	current

2026/08/13 11:03		current
Line 19:		Line 19:
	This section is for RFCs that have been announced on the PHP "internals" mail list.		This section is for RFCs that have been announced on the PHP "internals" mail list.

		+	* [[rfc:throw_error_for_invalid_characters_for_number_base\|Throw ValueError for invalid characters in number base functions]] (Created 2026-08-11)
	* [[rfc:function-autoloading-five-oh\|Function Autoloading (mark 5)]] (created 2026-06-16, discussion started 2026-06-16, voting started 2026-07-30)		* [[rfc:function-autoloading-five-oh\|Function Autoloading (mark 5)]] (created 2026-06-16, discussion started 2026-06-16, voting started 2026-07-30)
	* [[rfc:reldateformatter\|IntlRelativeDateTimeFormatter]] (Created 2026-08-07, Discussion started 2026-08-07)		* [[rfc:reldateformatter\|IntlRelativeDateTimeFormatter]] (Created 2026-08-07, Discussion started 2026-08-07)
Line 79:		Line 80:
	* [[rfc:deprecations_php_8_7\|Deprecations for PHP 8.7]] (Created 2026-08-12)		* [[rfc:deprecations_php_8_7\|Deprecations for PHP 8.7]] (Created 2026-08-12)
	* [[rfc:array_search_range\|Array Search Range]] (Created 2026-08-12)		* [[rfc:array_search_range\|Array Search Range]] (Created 2026-08-12)
-	* [[rfc:throw_error_for_invalid_characters_for_number_base\|Throw ValueError for invalid characters in number base functions]] (Created 2026-08-11)
	* [[rfc:immutable_collections\|Native Immutable Collections — "vec", "set" and "tuple"]] (Created 2026-08-04)		* [[rfc:immutable_collections\|Native Immutable Collections — "vec", "set" and "tuple"]] (Created 2026-08-04)
	* [[rfc:direction_aware_property_resolution\|Direction Aware Property Resolution]] (Created 2026-07-14)		* [[rfc:direction_aware_property_resolution\|Direction Aware Property Resolution]] (Created 2026-07-14)

2026/08/13 15:08		current
Line 18:		Line 18:
	\| Jul 30 2026 \| Alpha 3 [[https://www.php.net/archive/2026.php#2026-07-30-3\|Announce]] [[https://downloads.php.net/~mbeccati/\|Files]] \|		\| Jul 30 2026 \| Alpha 3 [[https://www.php.net/archive/2026.php#2026-07-30-3\|Announce]] [[https://downloads.php.net/~mbeccati/\|Files]] \|
	\| Aug 11 2026 \| All RFCs targeting 8.6 should have been merged, so they can be in Beta 1. \|		\| Aug 11 2026 \| All RFCs targeting 8.6 should have been merged, so they can be in Beta 1. \|
-	\| Aug 13 2026 \| Beta 1 + Soft feature freeze: all RFCs must have their voting concluded [[https://www.php.net/archive/2025.php#2025-08-14-1\|Announce]] [[https://downloads.php.net/~svpernova09/\|Files]] \|	+	\| Aug 13 2026 \| Beta 1 + Soft feature freeze: all RFCs must have their voting concluded [[https://www.php.net/archive/2026.php#2026-08-13-1\|Announce]] [[https://downloads.php.net/~svpernova09/\|Files]] \|
	\| Aug 27 2026 \| Beta 2 \|		\| Aug 27 2026 \| Beta 2 \|
	\| Sep 10 2026 \| Beta 3 \|		\| Sep 10 2026 \| Beta 3 \|

2026/08/09 12:08		current
Line 602:		Line 602:
	The following modes are supported:		The following modes are supported:

-	* Uri\Rfc3986\UriPercentEncoder****	+	* Uri\Rfc3986\UriPercentEncodingMode****
	* UserInfo: Besides [[https://datatracker.ietf.org/doc/html/rfc3986#section-2.3\|unreserved characters]] and [[https://datatracker.ietf.org/doc/html/rfc3986#section-2.2\|sub-delimiters]], it also allows the following characters to be present: ":". Any other characters (including "%" as well) are percent-encoded.		* UserInfo: Besides [[https://datatracker.ietf.org/doc/html/rfc3986#section-2.3\|unreserved characters]] and [[https://datatracker.ietf.org/doc/html/rfc3986#section-2.2\|sub-delimiters]], it also allows the following characters to be present: ":". Any other characters (including "%" as well) are percent-encoded.
	* RegisteredNameHost: [[https://datatracker.ietf.org/doc/html/rfc3986#section-2.3\|Unreserved characters]], and [[https://datatracker.ietf.org/doc/html/rfc3986#section-2.2\|sub-delimiters]] are allowed to be present. Any other characters (including "%" as well) are percent-encoded. Please note that IPv4, IPv6, as well as IPvFuture hosts don't support percent-encoding, and they have a much more restricted syntax, therefore this enum case is only applicable for registered names.		* RegisteredNameHost: [[https://datatracker.ietf.org/doc/html/rfc3986#section-2.3\|Unreserved characters]], and [[https://datatracker.ietf.org/doc/html/rfc3986#section-2.2\|sub-delimiters]] are allowed to be present. Any other characters (including "%" as well) are percent-encoded. Please note that IPv4, IPv6, as well as IPvFuture hosts don't support percent-encoding, and they have a much more restricted syntax, therefore this enum case is only applicable for registered names.
Line 608:		Line 608:
	* PathSegment: Besides [[https://datatracker.ietf.org/doc/html/rfc3986#section-2.3\|unreserved characters]] and [[https://datatracker.ietf.org/doc/html/rfc3986#section-2.2\|sub-delimiters]], it also allows the following characters to be present: ":", "@". Any other characters (including "%" as well) are percent-encoded.		* PathSegment: Besides [[https://datatracker.ietf.org/doc/html/rfc3986#section-2.3\|unreserved characters]] and [[https://datatracker.ietf.org/doc/html/rfc3986#section-2.2\|sub-delimiters]], it also allows the following characters to be present: ":", "@". Any other characters (including "%" as well) are percent-encoded.
	* Query: Besides [[https://datatracker.ietf.org/doc/html/rfc3986#section-2.3\|unreserved characters]] and [[https://datatracker.ietf.org/doc/html/rfc3986#section-2.2\|sub-delimiters]], it also allows the following characters to be present: ":", "@", "/", and "?". Any other characters (including "%" as well) are percent-encoded.		* Query: Besides [[https://datatracker.ietf.org/doc/html/rfc3986#section-2.3\|unreserved characters]] and [[https://datatracker.ietf.org/doc/html/rfc3986#section-2.2\|sub-delimiters]], it also allows the following characters to be present: ":", "@", "/", and "?". Any other characters (including "%" as well) are percent-encoded.
-	* FormQuery: It is mostly the same as ''Uri\Rfc3986\UriPercentEncoder::Query'', but it behaves according to the ''application/x-www-form-urlencode'' media type rather than RFC 3986. The only difference between the two is that " " is encoded as "+".	+	* FormQuery: It is mostly the same as ''Uri\Rfc3986\UriPercentEncodingMode::Query'', but it behaves according to the ''application/x-www-form-urlencode'' media type rather than RFC 3986. The only difference between the two is that " " is encoded as "+".
	* Fragment: Besides [[https://datatracker.ietf.org/doc/html/rfc3986#section-2.3\|unreserved characters]] and [[https://datatracker.ietf.org/doc/html/rfc3986#section-2.2\|sub-delimiters]], it also allows the following characters to be present: ":", "@", "/", and "?". Any other characters (including "%" as well) are percent-encoded.		* Fragment: Besides [[https://datatracker.ietf.org/doc/html/rfc3986#section-2.3\|unreserved characters]] and [[https://datatracker.ietf.org/doc/html/rfc3986#section-2.2\|sub-delimiters]], it also allows the following characters to be present: ":", "@", "/", and "?". Any other characters (including "%" as well) are percent-encoded.
	* AllReservedCharacters: All [[https://datatracker.ietf.org/doc/html/rfc3986#section-2.2\|reserved characters]] are percent-encoded. The rest of the characters are left as-is.		* AllReservedCharacters: All [[https://datatracker.ietf.org/doc/html/rfc3986#section-2.2\|reserved characters]] are percent-encoded. The rest of the characters are left as-is.