PHP Wiki

deprecated_attribute

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2024/07/02 07:46		current
Line 4:		Line 4:
	* Date: 2024-05-04		* Date: 2024-05-04
	* Author: Benjamin Eberlei, Tim Düsterhus		* Author: Benjamin Eberlei, Tim Düsterhus
-	* Status: Accepted	+	* Status: Implemented
		+	* Target Version: PHP 8.4
		+	* Implementation: https://github.com/php/php-src/commit/72c874691b99a88feada151fca337ff9e471c31e, https://github.com/php/php-src/commit/29f98e748568ebd66aaae061c0dcefbba92ca058
	* First Published at: http://wiki.php.net/rfc/deprecated_attribute		* First Published at: http://wiki.php.net/rfc/deprecated_attribute

Line 281:		Line 283:
	===== Implementation =====		===== Implementation =====

-	* Attribute: https://github.com/php/php-src/commit/72c874691b99a88feada151fca337ff9e471c31e	+	* Creating the Attribute: https://github.com/php/php-src/commit/72c874691b99a88feada151fca337ff9e471c31e
		+	* Using the Attribute in Stubs: https://github.com/php/php-src/commit/29f98e748568ebd66aaae061c0dcefbba92ca058

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

deprecations_php_8_5

Anonymous (anonymous@undisclosed.example.com) — 2025-09-19T20:30:13+00:00

remove_deprecated_functionality_in_php7

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2015/04/24 16:20		current
Line 2:		Line 2:
	* Date: 2014-09-11		* Date: 2014-09-11
	* Author: Nikita Popov <nikic@php.net>		* Author: Nikita Popov <nikic@php.net>
-	* Status: Accepted	+	* Status: Implemented (PHP 7.0)
	* Targeting: PHP 7		* Targeting: PHP 7
	* Discussion: http://markmail.org/message/vcladdh5sciqjpvg		* Discussion: http://markmail.org/message/vcladdh5sciqjpvg

deprecated-modifier

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2017/09/22 13:28		current
Line 3:		Line 3:
	* Date: 2012-12-25		* Date: 2012-12-25
	* Author: Yussuf Khalil <dev@pp3345.de>		* Author: Yussuf Khalil <dev@pp3345.de>
-	* Status: Inactive	+	* Status: Obsolete
	* First Published at: https://wiki.php.net/rfc/deprecated-modifier		* First Published at: https://wiki.php.net/rfc/deprecated-modifier
		+
		+	> This proposal has been superseded by [[rfc:deprecated_attribute\|#[\Deprecated] Attribute]], which has been implemented in PHP 8.4.

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

rfc

Anonymous (anonymous@undisclosed.example.com) — 2026-05-18T20:05:24+00:00

2026/05/18 19:59		current
Line 14:		Line 14:

	* [[rfc:array_get_and_array_has\|array_path_get and array_path_exists functions]] (Created 2026-04-04, voting started 2026-05-18, ends 2026-06-01)		* [[rfc:array_get_and_array_has\|array_path_get and array_path_exists functions]] (Created 2026-04-04, voting started 2026-05-18, ends 2026-06-01)
-	* [[rfc:session_security_defaults\|Session security defaults]] (Created 2026-04-04)
	* [[rfc:stream_errors\|Stream Error Handling Improvements]] (Created 2025-11-18)		* [[rfc:stream_errors\|Stream Error Handling Improvements]] (Created 2025-11-18)
	* [[rfc:uri_followup\| Followup Improvements for ext/uri]] (Created 2025-10-17, voting started 2026-05-05, ends 2026-05-19)		* [[rfc:uri_followup\| Followup Improvements for ext/uri]] (Created 2025-10-17, voting started 2026-05-05, ends 2026-05-19)
Line 162:		Line 161:
	==== PHP 8.6 ====		==== PHP 8.6 ====
	* [[rfc:debugable-enums\|Debugable Enums]] (Created 2026-03-12; discussion started 2026-03-12; voting started 2026-04-02, ends 2026-04-16)		* [[rfc:debugable-enums\|Debugable Enums]] (Created 2026-03-12; discussion started 2026-03-12; voting started 2026-04-02, ends 2026-04-16)
		+	* [[rfc:session_security_defaults\|Secure Session Configuration Defaults]] (Created 2026-04-04)
	* [[rfc:eol-oniguruma\|Oniguruma maintenance end and end of mbregex]] (Created 2025-08-21; voting started 2026-04-10, ends 2026-04-25)		* [[rfc:eol-oniguruma\|Oniguruma maintenance end and end of mbregex]] (Created 2025-08-21; voting started 2026-04-10, ends 2026-04-25)
	* [[rfc:sort_direction_enum\|enum SortDirection]] (Created 2026-03-02)		* [[rfc:sort_direction_enum\|enum SortDirection]] (Created 2026-03-02)

saner-inc-dec-operators

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2023/07/12 14:11		current
Line 4:		Line 4:
	* Date: 2022-11-21		* Date: 2022-11-21
	* Author: George Peter Banyard, <girgias@php.net>		* Author: George Peter Banyard, <girgias@php.net>
-	* Status: In Voting	+	* Status: Implemented
	* Target Version: PHP 8.3, PHP 8.(3+x), and PHP 9.0		* Target Version: PHP 8.3, PHP 8.(3+x), and PHP 9.0
-	* Implementation: [[https://github.com/php/php-src/pull/10358]]	+	* Implementation: [[https://github.com/php/php-src/commit/d8696f92166eea5e94cc82b64bce72f36fc81d46]]
	* First Published at: [[http://wiki.php.net/rfc/saner-inc-dec-operators]]		* First Published at: [[http://wiki.php.net/rfc/saner-inc-dec-operators]]

Line 597:		Line 597:
	After the project is implemented, this section should contain		After the project is implemented, this section should contain

-	* the version(s) it was merged into	+	* Version: PHP 8.3
-	* a link to the git commit(s)	+	* Implementation :https://github.com/php/php-src/commit/d8696f92166eea5e94cc82b64bce72f36fc81d46
	* a link to the PHP manual entry for the feature		* a link to the PHP manual entry for the feature

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

deprecated_interfaces

Anonymous (anonymous@undisclosed.example.com) — 2026-05-10T16:18:37+00:00

2026/05/19 10:05	current
Line 1:	Line 1:
	+	====== PHP RFC: #[\Deprecated] for interfaces ======
	+	* Version: 0.1
	+	* Date: 2026-05-10
	+	* Author: Daniel Scherzer, daniel.e.scherzer@gmail.com
	+	* Status: Draft
	+	* Implementation: https://github.com/php/php-src/pull/21998
	+	* Discussion thread:

	+	===== Introduction =====
	+
	+	The <php>#[\Deprecated]</php> attribute was introduced in PHP 8.4 ([[rfc:deprecated_attribute]]) and could be used to emit deprecation warnings when calling a function (or class method), or when accessing a class constant (or enum case). Starting in 8.5, deprecation warnings could also be emitted when accessing a global constant ([[rfc:attributes-on-constants]]) or when <php>use</php>ing a trait ([[rfc:deprecated_traits]]). This RFC proposes to add support for emitting deprecation warnings when an interface is extended or implemented.
	+
	+	<PHP>
	+	<?php
	+
	+	#[\Deprecated]
	+	trait DemoInterface {}
	+
	+	class DemoClass implements DemoInterface {}
	+
	+	// Reports:
	+	// Deprecated: Interface DemoInterface implemented by DemoClass is deprecated in %s on line %d
	+	?>
	+	</PHP>
	+
	+	===== Proposal =====
	+	The <php>#[\Deprecated]</php> attribute will be allowed on interfaces. The existing target validation when applied to classes or enums is maintained.
	+
	+	When the interfaces that a class implements are loaded, any deprecated interfaces emit a deprecation message; these can be converted to an exception via a user error handler, and an uncaught exception will be treated the same as trying to implement a non-interface in terms of registration behavior. The same applies to interfaces extending other interfaces if those other interfaces are marked as deprecated.
	+
	+	Interfaces only emit deprecation warnings when //directly// extended or implemented, implementing child interfaces or extending implementing classes does not result in extra errors. See the comparison with existing tools below.
	+
	+	==== Examples ====
	+
	+	Simple example:
	+	<PHP>
	+	<?php
	+
	+	#[\Deprecated]
	+	trait DemoInterface {}
	+
	+	class DemoClass implements DemoInterface {}
	+
	+	// Reports:
	+	// Deprecated: Interface DemoInterface implemented by DemoClass is deprecated in %s on line %d
	+	?>
	+	</PHP>
	+
	+	With an exception:
	+	<PHP>
	+	<?php
	+
	+	function my_error_handler(int $errno, string $errstr, ?string $errfile = null, ?int $errline = null) {
	+	throw new \ErrorException($errstr, 0, $errno, $errfile, $errline);
	+	}
	+
	+	set_error_handler('my_error_handler');
	+
	+	#[\Deprecated]
	+	interface DemoInterface {}
	+
	+	class DemoClass implements DemoInterface {}
	+
	+	// Reports:
	+	// Fatal error: Uncaught ErrorException: Interface DemoInterface implemented by DemoClass is deprecated in %s:%d
	+
	+	?>
	+	</PHP>
	+
	+	==== Tool comparison ====
	+
	+	Given the following code:
	+	<PHP>
	+	<?php
	+
	+	/**
	+	* @deprecated
	+	*/
	+	interface BaseInterface {}
	+
	+	interface ChildInterface extends BaseInterface {}
	+
	+	class ImplementsBase implements BaseInterface {}
	+
	+	class ImplementsBoth implements BaseInterface, ChildInterface {}
	+
	+	class ImplementsChild implements ChildInterface {}
	+
	+	class ExtendsBaseImplementor extends ImplementsBase {}
	+
	+	?>
	+	</PHP>
	+
	+	existing static analysis tools emit warnings for different sets of declarations. The behavior of the tools and the engine is as follows, where "yes" means a warning is emitted (with the engine behavior coming from using <php>#[\Deprecated]</php> rather than a comment):
	+
	+	^ Declaration ^ Phan ^ PHPStan ^ Mago ^ Psalm ^ Engine ^
	+	\| <php>interface ChildInterface... </php> \| yes \| yes \| yes \| no \| yes \|
	+	\| <php>class ImlementsBase... </php> \| yes \| yes \| no \| yes \| yes \|
	+	\| <php>class ImlementsBoth... </php> \| yes \| yes \| no \| yes \| yes \|
	+	\| <php>class ImlementsChild... </php> \| no \| no \| no \| yes \| no \|
	+	\| <php>class ExtendsBaseImplementor...</php> \| no \| no \| no \| yes \| no \|
	+
	+
	+	PHPStan is as of the version on the playground (https://phpstan.org/try) on 2026.05.10, Psalm is as of commit 5c1c31c which was on its playground (https://psalm.dev/) on the same date. Phan is as of version 6.0.5, Mago is as of version 1.26.0.
	+
	+	===== Backward Incompatible Changes =====
	+	None
	+
	+	===== Proposed PHP Version(s) =====
	+	Next PHP (8.6)
	+
	+	===== RFC Impact =====
	+	==== To the Ecosystem ====
	+	IDEs and static analyzers will likely want to update to surface deprecation messages when an interface is extended or implemented without waiting for PHP to emit the errors.
	+
	+	==== To Existing Extensions ====
	+	This lays the engine support for deprecating PHP-provided interfaces, but none are currently marked as deprecated.
	+
	+	==== To SAPIs ====
	+	No impact other than deprecations being emitted when a deprecated interface is used.
	+
	+	===== Open Issues =====
	+	Make sure there are no open issues when the vote starts!
	+
	+	===== Future Scope =====
	+	Other places that <php>#[\Deprecated]</php> could eventually be supported include
	+
	+	* extending a class
	+	* overriding a method
	+	* accessing a property
	+
	+	But the support for deprecating the use of a interface is pretty straightforward and there isn't room for future improvements within the context of deprecating interface.
	+
	+
	+	===== Voting Choices =====
	+	<doodle title="Add support for #[\Deprecated] on interfaces?" voteType="single" closed="true" closeon="2025-08-07T23:59:59Z" auth="daniels">
	+	* Yes
	+	* No
	+	</doodle>
	+
	+	===== Patches and Tests =====
	+	https://github.com/php/php-src/pull/21998
	+
	+	===== Implementation =====
	+	After the RFC is implemented, this section should contain:
	+	- the version(s) it was merged into
	+	- a link to the git commit(s)
	+	- a link to the PHP manual entry for the feature
	+
	+	===== References =====
	+
	+	* [[rfc:deprecated_attribute]]
	+	* [[rfc:attributes-on-constants]]
	+	* [[rfc:deprecated_traits]]
	+
	+	===== Rejected Features =====
	+	Keep this updated with features that were discussed on the mail lists.
	+
	+	===== Changelog =====
	+	If there are major changes to the initial proposal, please include a short summary with a date or a link to the mailing list announcement here, as not everyone has access to the wikis' version history.
	+
	+	* v0.1: created

deprecate_functions_with_overloaded_signatures

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2023/08/07 09:07		current
Line 3:		Line 3:
	* Author: Máté Kocsis <kocsismate@php.net>		* Author: Máté Kocsis <kocsismate@php.net>
	* Target version: PHP 8.3		* Target version: PHP 8.3
-	* Status: Accepted	+	* Status: Implemented
	* Implementation: https://github.com/php/php-src/pull/11703		* Implementation: https://github.com/php/php-src/pull/11703

mysql_deprecation

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2012/12/07 06:07		current
Line 1:		Line 1:
	====== Request for Comments: ext/mysql deprecation ======		====== Request for Comments: ext/mysql deprecation ======
-	* Version: 1.2	+	* Version: 1.2.1
-	* Date: 2012-11-28	+	* Date: 2012-12-10
	* Author: Adam Harvey <aharvey@php.net>		* Author: Adam Harvey <aharvey@php.net>
-	* Status: Accepted	+	* Status: Implemented in PHP 5.5
	* First Published at: https://wiki.php.net/rfc/mysql_deprecation		* First Published at: https://wiki.php.net/rfc/mysql_deprecation
	* Trivial patch: http://files.adamharvey.name/mysql-deprecation.patch		* Trivial patch: http://files.adamharvey.name/mysql-deprecation.patch
Line 164:		Line 164:
	===== Changelog =====		===== Changelog =====

		+	* 1.2.1 (2012-12-10): Update status to Implemented.
	* 1.2 (2012-12-07): Close voting; attempt to summarise the arguments on Internals into a few paragraphs; add links to the discussions for avid readers.		* 1.2 (2012-12-07): Close voting; attempt to summarise the arguments on Internals into a few paragraphs; add links to the discussions for avid readers.
	* 1.1.2 (2012-11-28): Replace the Oracle Wiki link with a link to Ulf's new blog post; moved to voting phase.		* 1.1.2 (2012-11-28): Replace the Oracle Wiki link with a link to Ulf's new blog post; moved to voting phase.

deprecated_traits

Anonymous (anonymous@undisclosed.example.com) — 2025-09-05T19:31:39+00:00

2025/08/08 01:11		current
Line 3:		Line 3:
	* Date: 2025-07-05		* Date: 2025-07-05
	* Author: Daniel Scherzer, daniel.e.scherzer@gmail.com		* Author: Daniel Scherzer, daniel.e.scherzer@gmail.com
-	* Status: Pending implementation / landing	+	* Status: Implemented
	* Implementation: https://github.com/php/php-src/pull/19045		* Implementation: https://github.com/php/php-src/pull/19045

deprecations_php_8_6

Anonymous (anonymous@undisclosed.example.com) — 2026-05-14T07:53:48+00:00

2026/05/14 07:53		current
Line 31:		Line 31:
	* Deprecate <php>ArrayIterator</php> methods that inherit <php>ArrayObject</php> implementation		* Deprecate <php>ArrayIterator</php> methods that inherit <php>ArrayObject</php> implementation
	* Deprecate <php>metaphone</php> function		* Deprecate <php>metaphone</php> function
-	* Deprecate changing by-reference return modifier via inheritance	+	* Deprecate changing by-reference return modifier via inheritance
-	* Deprecate dechunk php filter	+

	===== Proposal =====		===== Proposal =====

newinis

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2011/04/06 10:59		current
Line 3:		Line 3:
	* Date: 2009-02-22		* Date: 2009-02-22
	* Author: Eric Lee Stewart <ericleestewart.at.gmail.com>		* Author: Eric Lee Stewart <ericleestewart.at.gmail.com>
-	* Status: Under Discussion	+	* Status: Implemented in PHP 5.3
	* First Published at: http://wiki.php.net/rfc/newinis		* First Published at: http://wiki.php.net/rfc/newinis

partially-supported-callables-expand-deprecation-notices

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2022/06/19 12:34		current
Line 3:		Line 3:
	* Date: 2022-05-12		* Date: 2022-05-12
	* Author: Juliette Reinders Folmer, <php.net_nospam@adviesenzo.nl>		* Author: Juliette Reinders Folmer, <php.net_nospam@adviesenzo.nl>
-	* Status: Accepted	+	* Status: Implemented
	* Target version: 8.2		* Target version: 8.2
	* Implementation: https://github.com/php/php-src/pull/8823		* Implementation: https://github.com/php/php-src/pull/8823
Line 216:		Line 216:
	===== Implementation =====		===== Implementation =====

-	After the project is implemented, this section should contain	+	- Version 8.2.0
-	- the version(s) it was merged into	+	- Commit: https://github.com/php/php-src/commit/af15923bc340ccc8cca2e6e3411386e88ee5f2ff
-	- a link to the git commit(s)	+
-	- a link to the PHP manual entry for the feature	+
-	- a link to the language specification section (if any)	+

deprecate-fuzzy-and-null-casts

Anonymous (anonymous@undisclosed.example.com) — 2025-11-07T09:28:20+00:00

2025/10/29 09:36		current
Line 1:		Line 1:
-	====== PHP RFC: Deprecate Fuzzy Scalar Casts and Null Casts ======	+	====== PHP RFC: Deprecate Fuzzy Scalar Casts ======

	* Version: 1.0		* Version: 1.0
Line 12:		Line 12:
	PHP's explicit type casting operators (<php>(int)</php>, <php>(float)</php>, <php>(bool)</php>, <php>(string)</php>, <php>(array)</php>, <php>(object)</php>) have historically been maximally permissive, performing lossy conversions when the input value cannot be fully represented in the target type. This behavior, inherited from early PHP versions, creates inconsistencies between explicit casts and function parameter type checking, and can mask bugs by silently converting problematic values.		PHP's explicit type casting operators (<php>(int)</php>, <php>(float)</php>, <php>(bool)</php>, <php>(string)</php>, <php>(array)</php>, <php>(object)</php>) have historically been maximally permissive, performing lossy conversions when the input value cannot be fully represented in the target type. This behavior, inherited from early PHP versions, creates inconsistencies between explicit casts and function parameter type checking, and can mask bugs by silently converting problematic values.

-	This RFC addresses two particularly problematic categories of casts:	+	This RFC addresses a particularly problematic category of casts:

-	1. Fuzzy casts: conversions where information is lost or transformed in unexpected ways:	+	Fuzzy casts: conversions where information is lost or transformed in unexpected ways:

	<PHP>		<PHP>
Line 28:		Line 28:
	</PHP>		</PHP>

-	**2. Null casts**: conversions where <php>null</php> is coerced to type-specific default values, masking the absence of data:	+	This RFC proposes to **deprecate fuzzy casts in PHP 8.6 and make them throw <php>TypeError</php> in PHP 9.0, aligning explicit cast behavior with the existing** validation rules already used for typed function parameters in non-strict mode.

-	<PHP>	+	Important: This RFC specifically targets partial string conversions and **scalar-to-object casts**. Well-formed numeric strings (e.g., <php>"123"</php>, <php>"12.5"</php>) will continue to work as expected.
-	<?php	+
-	(int) null; // Returns 0 (null becomes zero)	+
-	(string) null; // Returns "" (null becomes empty string)	+
-	(bool) null; // Returns false (null becomes false)	+
-	(array) null; // Returns [] (null becomes empty array)	+
-	(object) null; // Returns stdClass object (null becomes empty object)	+
-	?>	+
-	</PHP>	+
-		+
-	This RFC proposes to deprecate both fuzzy casts and null casts in PHP 8.6 and make them throw <php>TypeError</php> in PHP 9.0, aligning explicit cast behavior with the existing validation rules already used for typed function parameters in non-strict mode.	+
-		+
-	Important: This RFC specifically targets partial string conversions and **null conversions**. Well-formed numeric strings (e.g., <php>"123"</php>, <php>"12.5"</php>) will continue to work as expected.	+

	===== Background and Motivation =====		===== Background and Motivation =====
Line 59:		Line 47:
	==== The Inconsistency Problem ====		==== The Inconsistency Problem ====

-	Consider these examples:	+	Consider this example:

	<PHP>		<PHP>
Line 72:		Line 60:
	// Explicit cast - permissive truncation		// Explicit cast - permissive truncation
	$result = (int) "123abc"; // 123 (no error, silently truncates "abc")		$result = (int) "123abc"; // 123 (no error, silently truncates "abc")
-	?>
-	</PHP>
-
-	<PHP>
-	<?php
-	// Function parameter type checking - rejects null
-	function calculate(int $count): void {
-	var_dump($count);
-	}
-
-	calculate(null); // TypeError: Cannot pass null to non-nullable parameter
-
-	// Explicit cast - converts null to 0
-	$result = (int) null; // 0 (no error, null becomes zero)
	?>		?>
	</PHP>		</PHP>
Line 93:		Line 67:
	==== Security and Correctness Issues ====		==== Security and Correctness Issues ====

-	Both fuzzy casts and null casts can introduce security vulnerabilities and correctness issues:	+	Fuzzy casts can introduce security vulnerabilities and correctness issues:
-		+
-	Fuzzy cast issues:	+

	<PHP>		<PHP>
Line 110:		Line 82:
	</PHP>		</PHP>

-	Null cast issues:	+	In these cases, invalid input is silently accepted instead of failing fast, making bugs harder to detect and fix.
-		+
-	<PHP>	+
-	<?php	+
-	// Ambiguity: is 0 a valid value or was it null?	+
-	$age = (int) $row['age']; // If $row['age'] is null, becomes 0	+
-	if ($age === 0) {	+
-	// Is the user a newborn, or was age missing?	+
-	}	+
-		+
-	// Logic error: null becomes falsy	+
-	$hasOptedIn = (bool) $userData['newsletter']; // null becomes false	+
-	// User never answered, but we treat it as "no"	+
-		+
-	// Data loss: null becomes empty string	+
-	$middleName = (string) $person['middle_name']; // null becomes ""	+
-	// Cannot distinguish between empty string and missing value	+
-	?>	+
-	</PHP>	+
-		+
-	In all these cases, invalid or missing input is silently accepted instead of failing fast, making bugs harder to detect and fix.	+

	==== Developer Expectations ====		==== Developer Expectations ====
Line 143:		Line 95:
	===== Current Behavior =====		===== Current Behavior =====

-	PHP's explicit scalar cast operators currently exhibit two problematic behaviors:	+	PHP's explicit scalar cast operators currently exhibit problematic fuzzy conversion behavior:

	==== Fuzzy Conversions ====		==== Fuzzy Conversions ====
Line 187:		Line 139:

	While boolean casts don't perform partial parsing, they still exhibit counterintuitive behavior where <php>"0"</php> is falsy but <php>"false"</php> is truthy.		While boolean casts don't perform partial parsing, they still exhibit counterintuitive behavior where <php>"0"</php> is falsy but <php>"false"</php> is truthy.
-
-	==== Null Conversions ====
-
-	All cast operators convert <php>null</php> to type-specific default values:
-
-	<PHP>
-	<?php
-	// Scalar conversions
-	(int) null; // 0 ⚠️ (null becomes zero)
-	(float) null; // 0.0 ⚠️ (null becomes zero)
-	(string) null; // "" ⚠️ (null becomes empty string)
-	(bool) null; // false ⚠️ (null becomes false)
-
-	// Compound type conversions
-	(array) null; // [] ⚠️ (null becomes empty array)
-	(object) null; // object(stdClass)#1 (0) {} ⚠️ (null becomes empty object)
-	?>
-	</PHP>
-
-	This behavior makes it impossible to distinguish between a legitimate value and the absence of a value:
-
-	<PHP>
-	<?php
-	$age = (int) $row['age']; // If null, becomes 0
-	// Problem: 0 could mean "newborn" or "missing data"
-
-	$name = (string) $row['name']; // If null, becomes ""
-	// Problem: "" could mean "no name" or "missing data"
-
-	$tags = (array) $row['tags']; // If null, becomes []
-	// Problem: [] could mean "no tags" or "missing data"
-	?>
-	</PHP>

	==== Comparison with Function Parameters ====		==== Comparison with Function Parameters ====

-	In contrast, typed function parameters in non-strict mode reject both malformed strings and null:	+	In contrast, typed function parameters in non-strict mode reject malformed strings:

	<PHP>		<PHP>
	<?php		<?php
	function test(int $i): int { return $i; }		function test(int $i): int { return $i; }
		+
		+	// Valid conversions - accepted
		+	test("123"); // 123 (valid numeric string)

	// Fuzzy conversions - rejected		// Fuzzy conversions - rejected
-	test("123"); // 123 (valid numeric string)
	test("123abc"); // TypeError: Cannot convert string to int		test("123abc"); // TypeError: Cannot convert string to int
-
-	// Null conversions - rejected
-	test(null); // TypeError: Cannot pass null to non-nullable parameter
	?>		?>
	</PHP>		</PHP>
Line 242:		Line 160:
	===== Proposal =====		===== Proposal =====

-	This RFC proposes a two-phase deprecation of both fuzzy scalar casts and null casts:	+	This RFC proposes a two-phase deprecation of fuzzy scalar casts:

	==== Phase 1: PHP 8.6 - Deprecation Notice ====		==== Phase 1: PHP 8.6 - Deprecation Notice ====

-	In PHP 8.6, both fuzzy casts and null casts will emit an <php>E_DEPRECATED</php> notice:	+	In PHP 8.6, fuzzy casts will emit an <php>E_DEPRECATED</php> notice when a string value can only be partially converted to the target scalar type, or when a scalar is cast to <php>(object)</php>:
-		+
-	Fuzzy casts - when a string value can only be partially converted to the target scalar type, or when a scalar is cast to <php>(object)</php>:	+
-		+
-	Null casts - when <php>null</php> is cast to any type:	+

	<PHP>		<PHP>
Line 275:		Line 189:
	(object) "hello"; // Deprecated: Conversion from string to object is deprecated		(object) "hello"; // Deprecated: Conversion from string to object is deprecated
	// Returns: stdClass Object ( [scalar] => "hello" )		// Returns: stdClass Object ( [scalar] => "hello" )
-
-	// Null casts - emit E_DEPRECATED
-	(int) null; // Deprecated: Implicit conversion from null to int is deprecated
-	// Returns: 0
-
-	(string) null; // Deprecated: Implicit conversion from null to string is deprecated
-	// Returns: ""
-
-	(array) null; // Deprecated: Implicit conversion from null to array is deprecated
-	// Returns: []
	?>		?>
	</PHP>		</PHP>

-	The deprecation notice will clearly indicate:	+	The deprecation notice will clearly indicate the original value, the target type, and the nature of the problematic conversion, and that these conversions will become errors in PHP 9.0.
-	* For fuzzy casts: The original value, the target type, and the nature of the problematic conversion	+
-	* For null casts: That the conversion from null to the target type is deprecated	+
-	* That these conversions will become errors in PHP 9.0	+

	==== Phase 2: PHP 9.0 - TypeError ====		==== Phase 2: PHP 9.0 - TypeError ====

-	In PHP 9.0, both fuzzy casts and null casts will throw a <php>TypeError</php> instead of performing conversion:	+	In PHP 9.0, fuzzy casts will throw a <php>TypeError</php> instead of performing conversion:

	<PHP>		<PHP>
Line 310:		Line 211:
	(object) 42; // TypeError: Cannot convert int to object		(object) 42; // TypeError: Cannot convert int to object
	(object) "hello"; // TypeError: Cannot convert string to object		(object) "hello"; // TypeError: Cannot convert string to object
-
-	// Null casts - throw TypeError
-	(int) null; // TypeError: Cannot convert null to int
-	(string) null; // TypeError: Cannot convert null to string
-	(bool) null; // TypeError: Cannot convert null to bool
-	(array) null; // TypeError: Cannot convert null to array
-	(object) null; // TypeError: Cannot convert null to object
	?>		?>
	</PHP>		</PHP>
Line 322:		Line 216:
	This aligns explicit cast behavior with the validation rules already used for typed function parameters in non-strict mode.		This aligns explicit cast behavior with the validation rules already used for typed function parameters in non-strict mode.

-	Note: These are not new validation rules. Function parameters in non-strict mode have rejected fuzzy conversions and null values since PHP 7.0. This RFC simply applies the same proven, consistent behavior to explicit cast operators.	+	Note: These are not new validation rules. Function parameters in non-strict mode have rejected fuzzy conversions since PHP 7.0. This RFC simply applies the same proven, consistent behavior to explicit cast operators.

	===== Scope and Affected Cases =====		===== Scope and Affected Cases =====
Line 398:		Line 292:
	// Or for boolean strings:		// Or for boolean strings:
	$enabled = filter_var($value, FILTER_VALIDATE_BOOLEAN, FILTER_NULL_ON_FAILURE);		$enabled = filter_var($value, FILTER_VALIDATE_BOOLEAN, FILTER_NULL_ON_FAILURE);
-	?>
-	</PHP>
-
-	==== What is Considered a Null Cast? ====
-
-	A null cast occurs when:
-
-	- The input value is <php>null</php>
-	- Any explicit cast operator is used on it
-
-	Examples of null casts (affected by this RFC):
-
-	<PHP>
-	<?php
-	(int) null; // ✗ Null cast to int
-	(float) null; // ✗ Null cast to float
-	(string) null; // ✗ Null cast to string
-	(bool) null; // ✗ Null cast to bool
-	(array) null; // ✗ Null cast to array
-	(object) null; // ✗ Null cast to object
-	?>
-	</PHP>
-
-	All null casts are deprecated because they mask the absence of data and create ambiguity.
-
-	Migration strategies for null handling:
-
-	<PHP>
-	<?php
-	// Option 1: Use null coalescing operator
-	$age = $row['age'] ?? 0; // Explicit default value
-
-	// Option 2: Explicit null check
-	if ($value !== null) {
-	$result = (int) $value;
-	} else {
-	// Handle null case explicitly
-	}
-
-	// Option 3: Use nullable types in function signatures
-	function process(?int $value): void {
-	if ($value === null) {
-	// Handle null explicitly
-	} else {
-	// Process non-null value
-	}
-	}
	?>		?>
	</PHP>		</PHP>
Line 458:		Line 305:
	\| String (fuzzy) \| <php>(float) "12.5foo"</php> \| 12.5 \| E_DEPRECATED + 12.5 \| TypeError \|		\| String (fuzzy) \| <php>(float) "12.5foo"</php> \| 12.5 \| E_DEPRECATED + 12.5 \| TypeError \|
	\| String (non-numeric) \| <php>(int) "abc"</php> \| 0 \| 0 \| 0 \|		\| String (non-numeric) \| <php>(int) "abc"</php> \| 0 \| 0 \| 0 \|
-	\| null \| <php>(int) null</php> \| 0 \| E_DEPRECATED + 0 \| TypeError \|
-	\| null \| <php>(string) null</php> \| "" \| E_DEPRECATED + "" \| TypeError \|
-	\| null \| <php>(bool) null</php> \| false \| E_DEPRECATED + false \| TypeError \|
-	\| null \| <php>(array) null</php> \| [] \| E_DEPRECATED + [] \| TypeError \|
-	\| null \| <php>(object) null</php> \| empty <php>stdClass</php> \| E_DEPRECATED + empty <php>stdClass</php> \| TypeError \|
	\| Scalar (fuzzy) \| <php>(object) 42</php> \| <php>stdClass</php> with <php>scalar</php> property \| E_DEPRECATED + <php>stdClass</php> \| TypeError \|		\| Scalar (fuzzy) \| <php>(object) 42</php> \| <php>stdClass</php> with <php>scalar</php> property \| E_DEPRECATED + <php>stdClass</php> \| TypeError \|
	\| Scalar (fuzzy) \| <php>(object) "hello"</php> \| <php>stdClass</php> with <php>scalar</php> property \| E_DEPRECATED + <php>stdClass</php> \| TypeError \|		\| Scalar (fuzzy) \| <php>(object) "hello"</php> \| <php>stdClass</php> with <php>scalar</php> property \| E_DEPRECATED + <php>stdClass</php> \| TypeError \|
Line 471:		Line 313:
	===== Backward Compatibility Impact =====		===== Backward Compatibility Impact =====

-	This RFC introduces backward incompatible changes that will affect existing code relying on fuzzy cast or null cast behavior.	+	This RFC introduces backward incompatible changes that will affect existing code relying on fuzzy cast behavior.

	==== Potential Impact ====		==== Potential Impact ====

-	Code that currently relies on fuzzy casts or null casts will need to be updated. Common patterns that will be affected include:	+	Code that currently relies on fuzzy casts will need to be updated. Common patterns that will be affected include:
-		+
-	Fuzzy cast patterns:	+

	<PHP>		<PHP>
Line 492:		Line 332:
	// Scalar to object wrapping		// Scalar to object wrapping
	$wrapped = (object) $someScalar; // Creates stdClass with 'scalar' property		$wrapped = (object) $someScalar; // Creates stdClass with 'scalar' property
-	?>
-	</PHP>
-
-	Null cast patterns:
-
-	<PHP>
-	<?php
-	// Database columns that may be NULL
-	$age = (int) $row['age']; // If $row['age'] is null, becomes 0
-
-	// Optional form fields
-	$middleName = (string) ($_POST['middle_name'] ?? null); // null becomes ""
-
-	// API responses with optional fields
-	$count = (int) $response['count']; // If 'count' is null, becomes 0
-
-	// Configuration with optional values
-	$maxRetries = (int) $config['max_retries']; // null becomes 0
	?>		?>
	</PHP>		</PHP>
Line 515:		Line 337:
	==== Migration Path ====		==== Migration Path ====

-	Developers have several options to migrate away from fuzzy casts and null casts:	+	Developers have several options to migrate away from fuzzy casts:
-		+
-	For fuzzy casts:	+

	Option 1: Validate before casting		Option 1: Validate before casting
Line 547:		Line 367:
	</PHP>		</PHP>

-	For null casts:	+	**Option 3: For scalar to object casts**

-	Option 1: Use null coalescing operator	+	Create a proper object structure or use an array:
-		+
-	<PHP>	+
-	<?php	+
-	// Provide explicit default value	+
-	$age = $row['age'] ?? 0; // 0 is the intended default	+
-	$name = $row['name'] ?? ''; // Empty string is the intended default	+
-	$tags = $row['tags'] ?? []; // Empty array is the intended default	+
-	?>	+
-	</PHP>	+
-		+
-	Option 2: Explicit null check	+
-		+
-	<PHP>	+
-	<?php	+
-	if ($value !== null) {	+
-	$result = (int) $value;	+
-	} else {	+
-	// Handle null case explicitly	+
-	throw new ValueError("Value cannot be null");	+
-	// Or provide a default:	+
-	// $result = 0;	+
-	}	+
-	?>	+
-	</PHP>	+
-		+
-	Option 3: Use nullable types	+
-		+
-	<PHP>	+
-	<?php	+
-	// Accept and preserve null in type system	+
-	function process(?int $value): void {	+
-	if ($value === null) {	+
-	// Handle null explicitly	+
-	} else {	+
-	// Process non-null value	+
-	}	+
-	}	+
-		+
-	// Or at variable level	+
-	$age = $row['age']; // Keep as ?int, don't cast	+
-	if ($age !== null) {	+
-	// Work with non-null int	+
-	}	+
-	?>	+
-	</PHP>	+
-		+
-	For scalar to object casts (fuzzy cast):	+
-		+
-	Option 1: Create a proper object structure	+

	<PHP>		<PHP>
Line 605:		Line 376:
	$obj = (object) 42;		$obj = (object) 42;

-	// Use:	+	// Option A: Create proper object structure
	$obj = new stdClass();		$obj = new stdClass();
	$obj->value = 42;		$obj->value = 42;

-	// Or create a proper class:	+	// Option B: Or create a proper class
	class ValueWrapper {		class ValueWrapper {
	public function __construct(public mixed $value) {}		public function __construct(public mixed $value) {}
	}		}
	$obj = new ValueWrapper(42);		$obj = new ValueWrapper(42);
-	?>
-	</PHP>

-	Option 2: Use an array if you need a key-value structure	+	// Option C: Use an array if you need a key-value structure
-		+	$data = ['value' => 42];
-	<PHP>	+
-	<?php	+
-	// Instead of:	+
-	$obj = (object) "hello";	+
-		+
-	// Use:	+
-	$data = ['value' => 'hello'];	+
	// Or if object is required:		// Or if object is required:
-	$obj = (object) ['value' => 'hello'];	+	$obj = (object) ['value' => 42];
-	?>	+
-	</PHP>	+

-	Option 3: Question whether object wrapping is necessary	+	// Option D: Question whether object wrapping is necessary
-		+
-	<PHP>	+
-	<?php	+
	// Often, the scalar value can be used directly		// Often, the scalar value can be used directly
-	// Instead of:	+	processValue(42); // Instead of processObject((object) 42)
-	$obj = (object) $count;	+
-	processObject($obj);	+
-		+
-	// Consider:	+
-	processValue($count);	+
	?>		?>
	</PHP>		</PHP>
Line 647:		Line 399:
	==== Detection and Tooling ====		==== Detection and Tooling ====

-	To help developers identify fuzzy casts and null casts in their codebase:	+	To help developers identify fuzzy casts in their codebase:

	* PHP 8.6: The deprecation notices will appear in error logs, making it easy to find affected code		* PHP 8.6: The deprecation notices will appear in error logs, making it easy to find affected code
-	* Static analysis tools: Tools like PHPStan and Psalm can be updated to detect potential fuzzy casts and null casts	+	* Static analysis tools: Tools like PHPStan and Psalm can be updated to detect potential fuzzy casts
-	* Code review: Search for cast patterns like <php>(int)</php>, <php>(float)</php>, <php>(string)</php>, <php>(object)</php> applied to variables that may be null or contain malformed data	+	* Code review: Search for cast patterns like <php>(int)</php>, <php>(float)</php>, <php>(object)</php> applied to variables that may contain malformed data

	===== Rationale =====		===== Rationale =====
Line 663:		Line 415:
	==== Why These Specific Cases? ====		==== Why These Specific Cases? ====

-	This RFC focuses specifically on fuzzy casts (including partial string conversions and scalar to object casts) and null casts because:	+	This RFC focuses specifically on fuzzy casts (including partial string conversions and scalar to object casts) because:

-	* These are the cases where explicit casts diverge from function parameter validation in non-strict mode	+	* These are cases where explicit casts diverge from function parameter validation in non-strict mode
-	* They represent the most problematic cases (silent data loss and ambiguity)	+	* They represent problematic cases of silent data loss
-	* They are the most likely to mask bugs and cause subtle errors	+	* They are likely to mask bugs and cause subtle errors
	* Function parameters already reject these conversions, providing a proven precedent		* Function parameters already reject these conversions, providing a proven precedent

Line 673:		Line 425:
	* Partial string conversions discard trailing data, making malformed input appear valid		* Partial string conversions discard trailing data, making malformed input appear valid
	* Scalar to object casts create objects with an arbitrary <php>scalar</php> property that has no meaningful semantic value		* Scalar to object casts create objects with an arbitrary <php>scalar</php> property that has no meaningful semantic value
-
-	Null casts make it impossible to distinguish between legitimate values (0, "", [], false) and missing data (null).

	Other cast behaviors (e.g., <php>(int) "abc"</php> returning 0) are not addressed by this RFC because:		Other cast behaviors (e.g., <php>(int) "abc"</php> returning 0) are not addressed by this RFC because:
	* They are well-documented and widely understood		* They are well-documented and widely understood
	* They don't involve data loss (the entire string is "consumed")		* They don't involve data loss (the entire string is "consumed")
-	* They don't create ambiguity about data presence
	* Changing them would require broader discussion and different tradeoffs		* Changing them would require broader discussion and different tradeoffs

Line 700:		Line 449:
	===== Examples and Use Cases =====		===== Examples and Use Cases =====

-	==== Example 1: Database Column with NULL ====	+	==== Example 1: Database Column with Corruption ====
-		+
-	<PHP>	+
-	<?php	+
-	// Current behavior - null becomes 0, creating ambiguity	+
-	$row = ['age' => null];	+
-	$age = (int) $row['age']; // 0 (is this a newborn or missing data?)	+
-		+
-	if ($age === 0) {	+
-	echo "Baby!"; // Wrong! This is actually missing data	+
-	}	+
-		+
-	// PHP 8.6 - deprecation notice	+
-	$age = (int) $row['age'];	+
-	// Deprecated: Implicit conversion from null to int is deprecated	+
-		+
-	// PHP 9.0 - explicit error	+
-	$age = (int) $row['age'];	+
-	// TypeError: Cannot convert null to int	+
-		+
-	// Recommended migration - explicit null handling	+
-	$age = $row['age'] ?? throw new RuntimeException("Age is required");	+
-	// Or with default:	+
-	$age = $row['age'] ?? 0; // Explicitly choosing 0 as default	+
-	?>	+
-	</PHP>	+
-		+
-	==== Example 2: Database Column with Corruption ====	+

	<PHP>		<PHP>
Line 751:		Line 473:
	</PHP>		</PHP>

-	==== Example 3: API Response with Units ====	+	==== Example 2: API Response with Units ====

	<PHP>		<PHP>
Line 772:		Line 494:
	</PHP>		</PHP>

-	==== Example 4: Configuration with Sanitization ====	+	==== Example 3: Configuration with Sanitization ====

	<PHP>		<PHP>
Line 797:		Line 519:
	===== Proposed PHP Version =====		===== Proposed PHP Version =====

-	* PHP 8.6: Emit <php>E_DEPRECATED</php> for fuzzy casts and null casts	+	* PHP 8.6: Emit <php>E_DEPRECATED</php> for fuzzy casts
-	* PHP 9.0: Throw <php>TypeError</php> for fuzzy casts and null casts	+	* PHP 9.0: Throw <php>TypeError</php> for fuzzy casts

	===== Voting Choices =====		===== Voting Choices =====

-	These are 2 simple yes/no vote requiring a 2/3 majority.	+	This is a simple yes/no vote requiring a 2/3 majority.

	<doodle title="Accept deprecation of fuzzy scalar casts for PHP 8.6/9.0?" voteType="single" closed="false">		<doodle title="Accept deprecation of fuzzy scalar casts for PHP 8.6/9.0?" voteType="single" closed="false">
-	* Yes
-	* No
-	* Abstain
-	</doodle>
-
-	<doodle title="Accept deprecation of null cast for PHP 8.6/9.0?" voteType="single" closed="false">
	* Yes		* Yes
	* No		* No

deprecate-fuzzy-casts

Anonymous (anonymous@undisclosed.example.com) — 2026-01-26T09:00:06+00:00

2026/01/26 08:53		current
Line 1:		Line 1:
-	====== PHP RFC: Deprecate Fuzzy Type Casts ======	+	====== PHP RFC: Deprecate Fuzzy Type Casts and Allow Stringable in Strict Mode ======

	* Version: 1.0		* Version: 1.0
Line 5:		Line 5:
	* Author: Alexandre Daubois <alexandredaubois@php.net>, Nicolas Grekas <nicolasgrekas@php.net>		* Author: Alexandre Daubois <alexandredaubois@php.net>, Nicolas Grekas <nicolasgrekas@php.net>
	* Status: Under discussion		* Status: Under discussion
-	* Target Version: PHP 8.6 (deprecation), PHP 9.0 (TypeError)	+	* Target Version: PHP 8.6 (deprecation and Stringable support), PHP 9.0 (TypeError)
	* Implementation: https://github.com/alexandre-daubois/php-src/pull/16		* Implementation: https://github.com/alexandre-daubois/php-src/pull/16

	===== Summary =====		===== Summary =====

-	This RFC seeks to address inconsistencies in scalar conversion behavior where explicit casts can perform lossy conversions ("fuzzy casts"), silently discarding part of the input.	+	This RFC seeks to address two differences in scalar conversion behavior:

-	This RFC proposes:	+	* Explicit casts can perform lossy conversions ("fuzzy casts"), silently discarding part of the input.
		+	* In strict typing mode (<php>declare(strict_types=1)</php>), <php>string</php> type declarations reject <php>Stringable</php> values even though they have a well-defined string representation.

-	* PHP 8.6: emit <php>E_DEPRECATED</php> for fuzzy casts.	+	This RFC changes both behaviors:
		+
		+	* PHP 8.6: emit <php>E_DEPRECATED</php> for fuzzy casts; accept <php>Stringable</php> for <php>string</php> parameters in strict mode.
	* PHP 9.0: throw <php>TypeError</php> for fuzzy casts.		* PHP 9.0: throw <php>TypeError</php> for fuzzy casts.

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

-	PHP's type conversion system contains differences between explicit casts and scalar type checks.	+	PHP's type conversion system contains differences between explicit casts and scalar type checks. This RFC addresses two issues:
		+
		+	Issue 1: Fuzzy Casts

	PHP's explicit cast operators can discard part of the input when it cannot be fully represented in the target type:		PHP's explicit cast operators can discard part of the input when it cannot be fully represented in the target type:
Line 28:		Line 33:
	(float) "12.34foo"; // 12.34 (discards "foo")		(float) "12.34foo"; // 12.34 (discards "foo")
	(object) 42; // stdClass { scalar: 42 }		(object) 42; // stdClass { scalar: 42 }
		+	?>
		+	</PHP>
		+
		+	Issue 2: Stringable Objects in Strict Mode
		+
		+	Strict mode rejects <php>Stringable</php> objects for <php>string</php> parameters, despite <php>Stringable</php> being an explicit contract for safe string conversion:
		+
		+	<PHP>
		+	<?php
		+	declare(strict_types=1);
		+
		+	function process(string $value): void { }
		+
		+	$obj = new class implements Stringable {
		+	public function __toString(): string { return "hello"; }
		+	};
		+
		+	process($obj); // TypeError (works in non-strict mode)
	?>		?>
	</PHP>		</PHP>
Line 39:		Line 62:

	===== Motivation =====		===== Motivation =====
		+
		+	==== Fuzzy Casts ====

	Since PHP 7.0, scalar type declarations in the default typing mode reject partial string conversions (<php>process("123abc")</php> throws <php>TypeError</php>), yet explicit casts can truncate (<php>(int) "123abc"</php> returns 123). This difference has several effects:		Since PHP 7.0, scalar type declarations in the default typing mode reject partial string conversions (<php>process("123abc")</php> throws <php>TypeError</php>), yet explicit casts can truncate (<php>(int) "123abc"</php> returns 123). This difference has several effects:
Line 49:		Line 74:
	Making explicit casts follow the same acceptance rules as scalar type checks reduces the incentive to "cast to make it pass" and encourages either valid coercion or explicit parsing.		Making explicit casts follow the same acceptance rules as scalar type checks reduces the incentive to "cast to make it pass" and encourages either valid coercion or explicit parsing.
	This reduces the number of conversion rules that need to be remembered and reduces reliance on explicit casts to satisfy scalar type declarations.		This reduces the number of conversion rules that need to be remembered and reduces reliance on explicit casts to satisfy scalar type declarations.
		+
		+	==== Stringable Objects in Strict Mode ====
		+
		+	In strict typing mode, passing a <php>Stringable</php> object to a <php>string</php> parameter throws <php>TypeError</php>. In the default typing mode, the same call is accepted.
		+
		+	This results in patterns such as:
		+
		+	* using unions like <php>string\|Stringable</php> and casting manually, or
		+	* requiring callers to cast with <php>(string) $value</php>.
		+
		+	This RFC proposes accepting <php>Stringable</php> in strict mode for <php>string</php> parameters, as part of reducing special cases in conversion behavior.
		+
		+	This also matches the longer-term direction of reducing the gap between typing modes (see the [[https://github.com/Girgias/unify-typing-modes-rfc\|Unify PHP's typing modes]] gist).

	===== Proposal =====		===== Proposal =====

-	=== Phase 1: PHP 8.6 - Deprecation ===	+	==== Fuzzy Scalar Casts ====

-	Important note: These behaviors are not arbitrary decisions. The proposed validation rules already exist for function arguments, regardless of the mode strictness.	+	=== Phase 1: PHP 8.6 - Deprecation ===

	Fuzzy casts emit <php>E_DEPRECATED</php>:		Fuzzy casts emit <php>E_DEPRECATED</php>:
Line 84:		Line 122:

	This aligns explicit casts with scalar type coercion rules used by the engine in the default (coercive) typing mode.		This aligns explicit casts with scalar type coercion rules used by the engine in the default (coercive) typing mode.
		+
		+	==== Stringable Objects in Strict Mode ====
		+
		+	=== PHP 8.6 ===
		+
		+	Strict mode will accept <php>Stringable</php> objects for <php>string</php> parameters, converting them via <php>__toString()</php>:
		+
		+	<PHP>
		+	<?php
		+	declare(strict_types=1);
		+
		+	function greet(string $name): string { return "Hello, $name!"; }
		+
		+	$user = new class implements Stringable {
		+	public function __toString(): string { return "John"; }
		+	};
		+
		+	greet($user); // PHP 8.5: TypeError, PHP 8.6: "Hello, John!"
		+	?>
		+	</PHP>
		+
		+	No deprecation in PHP 8.6; this is a relaxation of strict mode restrictions.

	===== Scope and Affected Cases =====		===== Scope and Affected Cases =====

	The proposed fuzzy cast rules align with existing validation used by scalar type declarations in the default (coercive) typing mode since PHP 7.0.		The proposed fuzzy cast rules align with existing validation used by scalar type declarations in the default (coercive) typing mode since PHP 7.0.
-
-	Important note: These behaviors are not arbitrary decisions. The proposed validation rules already exist for function arguments, regardless of the mode strictness.

	^ Input ^ Cast ^ Current ^ PHP 8.6 ^ PHP 9.0 ^		^ Input ^ Cast ^ Current ^ PHP 8.6 ^ PHP 9.0 ^
Line 100:		Line 158:
	\| <php>['a'=>1]</php> \| <php>(object)</php> \| <php>stdClass{a:1}</php> \| Unchanged \| Unchanged \|		\| <php>['a'=>1]</php> \| <php>(object)</php> \| <php>stdClass{a:1}</php> \| Unchanged \| Unchanged \|
	\| <php>"false"</php> \| <php>(bool)</php> \| true \| Unchanged \| Unchanged \|		\| <php>"false"</php> \| <php>(bool)</php> \| true \| Unchanged \| Unchanged \|
		+	\| Stringable (non-strict mode) \| String parameter \| Converts \| Converts \| — \|
		+	\| Stringable (strict mode) \| String parameter \| TypeError \| Converts \| — \|

	Note: Boolean casts use truthiness rules, not numeric parsing, they are unaffected. Float-to-int precision loss (<php>(int) 12.5</php>) is covered by [[rfc:implicit-float-int-deprecate\|a separate RFC]].		Note: Boolean casts use truthiness rules, not numeric parsing, they are unaffected. Float-to-int precision loss (<php>(int) 12.5</php>) is covered by [[rfc:implicit-float-int-deprecate\|a separate RFC]].

	===== Backward Compatibility Impact =====		===== Backward Compatibility Impact =====
		+
		+	==== Fuzzy Casts ====

	Affected patterns:		Affected patterns:
Line 141:		Line 203:

	Deprecation notices in PHP 8.6 will identify affected code. Static analysis tools (PHPStan, Psalm) can also detect these patterns.		Deprecation notices in PHP 8.6 will identify affected code. Static analysis tools (PHPStan, Psalm) can also detect these patterns.
		+
		+	==== Stringable in Strict Mode ====
		+
		+	Code that relies on strict mode rejecting <php>Stringable</php> objects will need adjustment. This is expected to be rare.

	===== Related Functions =====		===== Related Functions =====
Line 150:		Line 216:
	===== Proposed PHP Version =====		===== Proposed PHP Version =====

-	* PHP 8.6: Emit <php>E_DEPRECATED</php> for fuzzy casts	+	* PHP 8.6: Emit <php>E_DEPRECATED</php> for fuzzy casts; accept <php>Stringable</php> for string parameters in strict mode
	* PHP 9.0: Throw <php>TypeError</php> for fuzzy casts		* PHP 9.0: Throw <php>TypeError</php> for fuzzy casts

	===== RFC Impact =====		===== RFC Impact =====

-	Testing against the Symfony codebase raised only a few dozen deprecations across components, bundles, and bridges.	+	Testing against the Symfony codebase raised only a few dozen deprecations across components, bundles, and bridges. Symfony doesn't use strict types, so no impact from the <php>Stringable</php> change.

	===== Vote =====		===== Vote =====
Line 161:		Line 227:
	Single yes/no vote requiring 2/3 majority.		Single yes/no vote requiring 2/3 majority.

-	<doodle title="Deprecate fuzzy casts in PHP 8.6?" voteType="single" closed="false">	+	<doodle title="Deprecate fuzzy casts and allow Stringable in strict mode in PHP 8.6?" voteType="single" closed="false">
	* Yes		* Yes
	* No		* No
Line 176:		Line 242:
	* PHP filter_var() Documentation: https://www.php.net/manual/en/function.filter-var.php		* PHP filter_var() Documentation: https://www.php.net/manual/en/function.filter-var.php
	* RFC: Deprecate implicit float to int conversions: https://wiki.php.net/rfc/implicit-float-int-deprecate		* RFC: Deprecate implicit float to int conversions: https://wiki.php.net/rfc/implicit-float-int-deprecate
		+	* Unify PHP's typing modes (context/motivation): https://github.com/Girgias/unify-typing-modes-rfc
	* Discussion thread: https://news-web.php.net/php.internals/129884		* Discussion thread: https://news-web.php.net/php.internals/129884

eol-oniguruma

Anonymous (anonymous@undisclosed.example.com) — 2026-04-28T02:08:12+00:00

2026/04/25 04:57		current
Line 3:		Line 3:
	* Date: 2025-08-21		* Date: 2025-08-21
	* Author: Yuya Hamada youkidearitai@gmail.com		* Author: Yuya Hamada youkidearitai@gmail.com
-	* Status: Accepted	+	* Status: Implemented
	* Implementation: https://github.com/php/php-src/pull/21490		* Implementation: https://github.com/php/php-src/pull/21490

coercive_sth

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2017/09/22 13:28		current
Line 3:		Line 3:
	* Date: 2015-02-27		* Date: 2015-02-27
	* Authors: Zeev Suraski <zeev@php.net>, Francois Laupretre <francois@php.net>, Dmitry Stogov <dmitry@php.net>		* Authors: Zeev Suraski <zeev@php.net>, Francois Laupretre <francois@php.net>, Dmitry Stogov <dmitry@php.net>
-	* Status: Rejected	+	* Status: Declined
	* First Published at: http://wiki.php.net/rfc/coercive_sth		* First Published at: http://wiki.php.net/rfc/coercive_sth

container-offset-behaviour

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2024/07/16 02:26		current
Line 5:		Line 5:
	* Author: Gina Peter Banyard <girgias@php.net>		* Author: Gina Peter Banyard <girgias@php.net>
	* Status: Under Discussion		* Status: Under Discussion
-	* Target Version: PHP 8.4	+	* Target Version: PHP 8.5
	* Implementations:		* Implementations:
	* New handler API: <https://github.com/Girgias/php-src/pull/19>		* New handler API: <https://github.com/Girgias/php-src/pull/19>

deprecations_php_7_4

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2019/08/10 23:19		current
Line 2:		Line 2:
	* Date: 26th June, 2018		* Date: 26th June, 2018
	* Authors: Kalle Sommer Nielsen <kalle@php.net>, Nikita Popov <nikic@php.net>		* Authors: Kalle Sommer Nielsen <kalle@php.net>, Nikita Popov <nikic@php.net>
-	* Status: Accepted	+	* Status: Implemented
	* Targets: PHP 7.4		* Targets: PHP 7.4

deprecations_php_8_4

Anonymous (anonymous@undisclosed.example.com) — 2025-11-14T04:54:54+00:00

2025/07/10 04:24		current
Line 9:		Line 9:
	* Jorg Sowa <jorg.sowa@gmail.com>		* Jorg Sowa <jorg.sowa@gmail.com>
	* Status: Implemented		* Status: Implemented
-	* Implementation: 8.5 (for user output handlers returning non-strings or producing output), 8.4 (everything else)	+	* Implementation: pending (for user output handlers returning non-strings), 8.5 (for user output handlers producing output), 8.4 (everything else)
	* [[https://github.com/php/php-src/commit/587110c5bf44362fa81606c492c9a668b2160d9a\|Formally deprecate Soft-deprecated DOMDocument and DOMEntity properties]]		* [[https://github.com/php/php-src/commit/587110c5bf44362fa81606c492c9a668b2160d9a\|Formally deprecate Soft-deprecated DOMDocument and DOMEntity properties]]
	* [[https://github.com/php/php-src/commit/d9eb3783bdd6947a635f132f8c240de8f40e8704\|Remove DOMImplementation::getFeature($feature, $version)]]		* [[https://github.com/php/php-src/commit/d9eb3783bdd6947a635f132f8c240de8f40e8704\|Remove DOMImplementation::getFeature($feature, $version)]]
Line 22:		Line 22:
	* [[https://github.com/php/php-src/commit/c818d944cf998b3151e4b312d655c51223612c4e\|Deprecate proprietary CSV escaping mechanism]]		* [[https://github.com/php/php-src/commit/c818d944cf998b3151e4b312d655c51223612c4e\|Deprecate proprietary CSV escaping mechanism]]
	* [[https://github.com/php/php-src/commit/d313ad6098430f4e61f0121a9e7ab392d195e4e4\|Deprecate E_STRICT Constant]]		* [[https://github.com/php/php-src/commit/d313ad6098430f4e61f0121a9e7ab392d195e4e4\|Deprecate E_STRICT Constant]]
-	* [[https://github.com/php/php-src/commit/d8577d9bfbb89bc2924b0bcb60a8e7fb5fd5267a\|Deprecate returning non-string values from a user output handler]]	+	* Deprecate returning non-string values from a user output handler
	* [[https://github.com/php/php-src/commit/07f1cfd9b01ff0f3720c1a5580b9e263eec5fce1\|Deprecate producing output in a user output handler]]		* [[https://github.com/php/php-src/commit/07f1cfd9b01ff0f3720c1a5580b9e263eec5fce1\|Deprecate producing output in a user output handler]]
	* [[https://github.com/php/php-src/commit/cbcad9fdaf816e4512cecfb6c1d50fcc0ea7294d\|Deprecate mysqli_ping() and mysqli::ping()]]		* [[https://github.com/php/php-src/commit/cbcad9fdaf816e4512cecfb6c1d50fcc0ea7294d\|Deprecate mysqli_ping() and mysqli::ping()]]

e-user-deprecated-warning

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2011/04/06 10:59		current
Line 3:		Line 3:
	* Date: 2008-07-18		* Date: 2008-07-18
	* Author: Lars Strojny <lstrojny@php.net>		* Author: Lars Strojny <lstrojny@php.net>
-	* Status: Accepted	+	* Status: Implemented in PHP 5.3
	* First Published at: http://wiki.php.net/rfc/e-user-deprecated-warning		* First Published at: http://wiki.php.net/rfc/e-user-deprecated-warning

ffi-non-static-deprecated

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2024/06/21 08:49		current
Line 3:		Line 3:
	* Date: 2024-06-21		* Date: 2024-06-21
	* Author: Chopins, chopins.xiao@gmail.com		* Author: Chopins, chopins.xiao@gmail.com
		+	* Target version: PHP 8.4
	* Status: Draft		* Status: Draft
	* First Published at: https://wiki.php.net/rfc/ffi-non-static-deprecated		* First Published at: https://wiki.php.net/rfc/ffi-non-static-deprecated
Line 49:		Line 50:
	Since non-static calls are marked as stale, they will result in a stale prompt being received for versions less than PHP 8.3. If PHP 9.0 removes non-static calls to FFICDef::new(), FFICDef::cast(), FFICDef::type(), it will result in an error in the unadapted program.		Since non-static calls are marked as stale, they will result in a stale prompt being received for versions less than PHP 8.3. If PHP 9.0 removes non-static calls to FFICDef::new(), FFICDef::cast(), FFICDef::type(), it will result in an error in the unadapted program.
	===== Proposed PHP Version(s) =====		===== Proposed PHP Version(s) =====
-	PHP 8.3	+	PHP 8.4
	===== Impact on extensions =====		===== Impact on extensions =====
	FFI		FFI

consistent_function_names

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2015/03/07 00:40		current
Line 649:		Line 649:
	* file_stat <- stat (IEEE)		* file_stat <- stat (IEEE)
	* file_stat_clear_cache <- clearstatcache		* file_stat_clear_cache <- clearstatcache
		+
		+	* file_move_uploaded <- move_upload_file

	* file_delete <- unlink (There is dummy "delete()" function entry for unlink(). Unlink is a directory operation in fact, but made it as file_delete(). There will be dir_delete())		* file_delete <- unlink (There is dummy "delete()" function entry for unlink(). Unlink is a directory operation in fact, but made it as file_delete(). There will be dir_delete())
Line 803:		Line 805:

	* Use of namespace to clean up global namespace at all.		* Use of namespace to clean up global namespace at all.
-	* New APIs that replace old APIs.
-	* Parameter order inconsistency.
	* Return type inconsistency.		* Return type inconsistency.
	* Constant name inconsistency.		* Constant name inconsistency.
Line 852:		Line 852:
	* http://php.net/manual/en/ref.classobj.php		* http://php.net/manual/en/ref.classobj.php
	* __autoload — Attempt to load undefined class		* __autoload — Attempt to load undefined class
-	* call_user_method_array — Call a user method given with an array of parameters [deprecated]	+	* class_alias — Creates an alias for a class
-	* call_user_method — Call a user method on an specific object [deprecated]	+
-	* class_alias — Creates an alias for a class (Aliases should not be listed, but they should be searchable)	+
	* class_called — the "Late Static Binding" class name		* class_called — the "Late Static Binding" class name
	* class_declared — Returns an array with the name of the defined classes		* class_declared — Returns an array with the name of the defined classes
Line 871:		Line 869:
	* trait_declared — Returns an array of all declared traits		* trait_declared — Returns an array of all declared traits
	* trait_exists — Checks if the trait exists		* trait_exists — Checks if the trait exists
		+
		+	* call_user_method_array — Call a user method given with an array of parameters [deprecated]
		+	* call_user_method — Call a user method on an specific object [deprecated]


Line 883:		Line 884:
	* gc_enable — Activates the circular reference collector		* gc_enable — Activates the circular reference collector
	* gc_enabled — Returns status of the circular reference collector		* gc_enabled — Returns status of the circular reference collector
-	* get_magic_quotes_gpc — Gets the current configuration setting of magic_quotes_gpc [Deprecated]
-	* get_magic_quotes_runtime — Gets the current active configuration setting of magic_quotes_runtime [Deprecated]
	* get_env — Gets the value of an environment variable		* get_env — Gets the value of an environment variable
	* get_last_mod — Gets time of last page modification		* get_last_mod — Gets time of last page modification
Line 893:		Line 892:
	* get_opt — Gets options from the command line argument list		* get_opt — Gets options from the command line argument list
	* get_rusage — Gets the current resource usages		* get_rusage — Gets the current resource usages
-	* ini_alter — Alias of ini_set (Aliases should not be listed, but they should be searchable)
	* ini_get_all — Gets all configuration options		* ini_get_all — Gets all configuration options
	* ini_get — Gets the value of a configuration option		* ini_get — Gets the value of a configuration option
	* ini_restore — Restores the value of a configuration option		* ini_restore — Restores the value of a configuration option
	* ini_set — Sets the value of a configuration option		* ini_set — Sets the value of a configuration option
-	* magic_quotes_runtime — Alias of set_magic_quotes_runtime [Deprecated] (Aliases should not be listed, but they should be searchable)
	* main — Dummy for main		* main — Dummy for main
	* memory_get_peak_usage — Returns the peak of memory allocated by PHP		* memory_get_peak_usage — Returns the peak of memory allocated by PHP
Line 918:		Line 915:
	* php_ini_scanned_files — Return a list of .ini files parsed from the additional ini dir		* php_ini_scanned_files — Return a list of .ini files parsed from the additional ini dir
	* php_logo_guid — Gets the logo guid		* php_logo_guid — Gets the logo guid
-	* php_required_files — Alias of get_included_files (Aliases should not be listed, but they should be searchable)
	* php_sapi_name — Returns the type of interface between web server and PHP		* php_sapi_name — Returns the type of interface between web server and PHP
	* php_time_limit — Limits the maximum execution time		* php_time_limit — Limits the maximum execution time
Line 924:		Line 920:
	* php_version — Gets the current PHP version		* php_version — Gets the current PHP version
	* put_env — Sets the value of an environment variable		* put_env — Sets the value of an environment variable
-	* set_magic_quotes_runtime — Sets the current active configuration setting of magic_quotes_runtime [Deprecated]
	* sys_get_temp_dir — Returns directory path used for temporary files		* sys_get_temp_dir — Returns directory path used for temporary files
	* version_compare — Compares two "PHP-standardized" version number strings		* version_compare — Compares two "PHP-standardized" version number strings
Line 930:		Line 925:
	* zend_thread_id — Returns a unique identifier for the current thread		* zend_thread_id — Returns a unique identifier for the current thread
	* zend_version — Gets the version of the current Zend engine		* zend_version — Gets the version of the current Zend engine
		+
		+	* get_magic_quotes_gpc — Gets the current configuration setting of magic_quotes_gpc [Deprecated]
		+	* get_magic_quotes_runtime — Gets the current active configuration setting of magic_quotes_runtime [Deprecated]
		+	* magic_quotes_runtime — Alias of set_magic_quotes_runtime [Deprecated] (Aliases should not be listed, but they should be searchable)
		+	* set_magic_quotes_runtime — Sets the current active configuration setting of magic_quotes_runtime [Deprecated]
		+
		+	* ini_alter — Alias of ini_set (Aliases should not be listed, but they should be searchable)
		+	* php_required_files — Alias of get_included_files (Aliases should not be listed, but they should be searchable)
		+

	====Arrays====		====Arrays====
Line 1006:		Line 1010:
	* list — Assign variables as if they were an array		* list — Assign variables as if they were an array
	* next — Advance the internal array pointer of an array		* next — Advance the internal array pointer of an array
-	* pos — Alias of current (Aliases will not be listed)
	* prev — Rewind the internal array pointer		* prev — Rewind the internal array pointer
	* reset — Set the internal pointer of an array to its first element		* reset — Set the internal pointer of an array to its first element
		+
		+	* pos — Alias of current (Aliases will not be listed)
	* sizeof — Alias of count (Aliases will not be listed)		* sizeof — Alias of count (Aliases will not be listed)

Line 1015:		Line 1020:
	* bool_val — Get the boolean value of a variable		* bool_val — Get the boolean value of a variable
	* debug_zval_dump — Dumps a string representation of an internal zend value to output		* debug_zval_dump — Dumps a string representation of an internal zend value to output
-	* double_val — Alias of floatval (Aliases should not be listed, but they should be searchable)
	* empty — Determine whether a variable is empty		* empty — Determine whether a variable is empty
	* float_val — Get float value of a variable		* float_val — Get float value of a variable
Line 1026:		Line 1030:
	* is_float — Finds whether the type of a variable is float		* is_float — Finds whether the type of a variable is float
	* is_int — Find whether the type of a variable is integer		* is_int — Find whether the type of a variable is integer
-	* is_integer — Alias of is_int (Aliases should not be listed, but they should be searchable)
-	* is_long — Alias of is_int (Aliases should not be listed, but they should be searchable)
	* is_null — Finds whether a variable is NULL		* is_null — Finds whether a variable is NULL
	* is_numeric — Finds whether a variable is a number or a numeric string		* is_numeric — Finds whether a variable is a number or a numeric string
	* is_object — Finds whether a variable is an object		* is_object — Finds whether a variable is an object
-	* is_real — Alias of is_float (Aliases should not be listed, but they should be searchable)
	* is_resource — Finds whether a variable is a resource		* is_resource — Finds whether a variable is a resource
	* is_scalar — Finds whether a variable is a scalar		* is_scalar — Finds whether a variable is a scalar
Line 1047:		Line 1048:
	* var_dump — Dumps information about a variable		* var_dump — Dumps information about a variable
	* var_export — Outputs or returns a parsable string representation of a variable		* var_export — Outputs or returns a parsable string representation of a variable
		+
		+	* double_val — Alias of floatval (Aliases should not be listed, but they should be searchable)
		+	* is_integer — Alias of is_int (Aliases should not be listed, but they should be searchable)
		+	* is_long — Alias of is_int (Aliases should not be listed, but they should be searchable)
		+	* is_real — Alias of is_float (Aliases should not be listed, but they should be searchable)

	====Program execution Functions====		====Program execution Functions====
Line 1097:		Line 1103:
	* sprintf — Return a formatted string		* sprintf — Return a formatted string
	* str_case_cmp — Binary safe case-insensitive string comparison		* str_case_cmp — Binary safe case-insensitive string comparison
-	* str_chr — Alias of strstr (Aliases should not be listed, but they should be searchable)
-	* str_chop — Alias of str_rtrim (Aliases should not be listed, but they should be searchable)
	* str_chunk_split — Split a string into smaller chunks		* str_chunk_split — Split a string into smaller chunks
	* str_cmp — Binary safe string comparison		* str_cmp — Binary safe string comparison
Line 1112:		Line 1116:
	* str_ireplace — Case-insensitive version of str_replace.		* str_ireplace — Case-insensitive version of str_replace.
	* str_istr — Case-insensitive strstr		* str_istr — Case-insensitive strstr
-	* str_join — Alias of implode (Aliases should not be listed, but they should be searchable)
	* str_lc_first — Make a string's first character lowercase		* str_lc_first — Make a string's first character lowercase
	* str_len — Get string length		* str_len — Get string length
Line 1163:		Line 1166:
	* vprintf — Output a formatted string		* vprintf — Output a formatted string
	* vsprintf — Return a formatted string		* vsprintf — Return a formatted string
		+
		+	* str_chr — Alias of strstr (Aliases should not be listed, but they should be searchable)
		+	* str_chop — Alias of str_rtrim (Aliases should not be listed, but they should be searchable)
		+	* str_join — Alias of implode (Aliases should not be listed, but they should be searchable)
		+

	====Filesystem Functions====		====Filesystem Functions====
Line 1174:		Line 1182:
	* disk_free_space — Returns available space on filesystem or disk partition		* disk_free_space — Returns available space on filesystem or disk partition
	* disk_total_space — Returns the total size of a filesystem or disk partition		* disk_total_space — Returns the total size of a filesystem or disk partition
-	* diskfreespace — Alias of disk_free_space (Aliases should not be listed, but they should be searchable)
	* fclose — Closes an open file pointer		* fclose — Closes an open file pointer
	* feof — Tests for end-of-file on a file pointer		* feof — Tests for end-of-file on a file pointer
Line 1194:		Line 1201:
	* file_inode — Gets file inode		* file_inode — Gets file inode
	* file_mtime — Gets file modification time		* file_mtime — Gets file modification time
		+	* file_move_uploaded — Moves an uploaded file to a new location
	* file_owner — Gets file owner		* file_owner — Gets file owner
	* file_perms — Gets file permissions		* file_perms — Gets file permissions
Line 1200:		Line 1208:
	* file_passthru — Output all remaining data on a file pointer		* file_passthru — Output all remaining data on a file pointer
	* file_put_csv — Format line as CSV and write to file pointer		* file_put_csv — Format line as CSV and write to file pointer
-	* file_puts — Alias of fwrite (Aliases should not be listed, but they should be searchable)
	* file_size — Gets file size		* file_size — Gets file size
	* file_temp_name — Create file with unique file name		* file_temp_name — Create file with unique file name
Line 1225:		Line 1232:
	* is_uploaded_file — Tells whether the file was uploaded via HTTP POST		* is_uploaded_file — Tells whether the file was uploaded via HTTP POST
	* is_writable — Tells whether the filename is writable		* is_writable — Tells whether the filename is writable
-	* is_writeable — Alias of is_writable (Aliases should not be listed, but they should be searchable)
	* link_chgrp — Changes group ownership of symlink		* link_chgrp — Changes group ownership of symlink
	* link_chown — Changes user ownership of symlink		* link_chown — Changes user ownership of symlink
Line 1233:		Line 1239:
	* link_symbolic — Creates a symbolic link		* link_symbolic — Creates a symbolic link
	* link — Create a hard link		* link — Create a hard link
-	* move_uploaded_file — Moves an uploaded file to a new location
	* parse_ini_file — Parse a configuration file		* parse_ini_file — Parse a configuration file
	* parse_ini_string — Parse a configuration string (This is string function. Or make them ini function? ini_string()/ini_file() )		* parse_ini_string — Parse a configuration string (This is string function. Or make them ini function? ini_string()/ini_file() )
Line 1244:		Line 1249:
	* realpath_cache_size — Get realpath cache size		* realpath_cache_size — Get realpath cache size
	* realpath — Returns canonicalized absolute pathname		* realpath — Returns canonicalized absolute pathname
-	* set_file_buffer — Alias of stream_set_write_buffer (This is kind of deprecated function. User should use stream function)
	* stat_clear_cache — Clears file status cache		* stat_clear_cache — Clears file status cache
	* stat — Gives information about a file		* stat — Gives information about a file

		+	* set_file_buffer — Alias of stream_set_write_buffer (This is kind of deprecated function. User should use stream function)
		+	* diskfreespace — Alias of disk_free_space (Aliases should not be listed, but they should be searchable)
		+	* is_writeable — Alias of is_writable (Aliases should not be listed, but they should be searchable)
		+	* fputs — Alias of fwrite (Aliases should not be listed, but they should be searchable)

deprecate-bareword-strings

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2017/09/22 13:28		current
Line 3:		Line 3:
	* Date: 2017-03-05		* Date: 2017-03-05
	* Author: Rowan Collins rowan.collins@gmail.com		* Author: Rowan Collins rowan.collins@gmail.com
-	* Status: Accepted	+	* Status: Implemented (in PHP 7.2)
	* First Published at: http://wiki.php.net/rfc/deprecate-bareword-strings		* First Published at: http://wiki.php.net/rfc/deprecate-bareword-strings

raising_zero_to_power_of_negative_number

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2024/08/11 21:01		current
Line 82:		Line 82:
	===== Implementation =====		===== Implementation =====
	Commit: https://github.com/php/php-src/commit/23afe57f01e0915eef246eba60e60fda74fd2dcf		Commit: https://github.com/php/php-src/commit/23afe57f01e0915eef246eba60e60fda74fd2dcf
		+
	PR: https://github.com/php/php-src/pull/13128		PR: https://github.com/php/php-src/pull/13128

Line 89:		Line 90:
	===== References =====		===== References =====
	Issue GH-8015: https://github.com/php/php-src/issues/8015		Issue GH-8015: https://github.com/php/php-src/issues/8015
		+
	RFC Division by zero: https://wiki.php.net/rfc/engine_warnings		RFC Division by zero: https://wiki.php.net/rfc/engine_warnings

remove_php4_constructors

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2015/03/10 19:20		current
Line 4:		Line 4:
	* Author: Levi Morrison <levim@php.net>		* Author: Levi Morrison <levim@php.net>
	* Contributors: Andrea Faulds <ajf@ajf.me>		* Contributors: Andrea Faulds <ajf@ajf.me>
-	* Status: Accepted	+	* Status: Deprecation Implemented (in PHP 7.0)
	* First Published at: http://wiki.php.net/rfc/remove_php4_constructors		* First Published at: http://wiki.php.net/rfc/remove_php4_constructors

attributes_v2

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2020/05/04 12:00		current
Line 4:		Line 4:
	* Date: 2020-03-09		* Date: 2020-03-09
	* Author: Benjamin Eberlei (beberlei@php.net), Martin Schröder		* Author: Benjamin Eberlei (beberlei@php.net), Martin Schröder
-	* Status: Accepted	+	* Status: Implemented
	* Target: 8.0		* Target: 8.0
	* First Published at: http://wiki.php.net/rfc/attributes_v2		* First Published at: http://wiki.php.net/rfc/attributes_v2

attributes-on-constants

Anonymous (anonymous@undisclosed.example.com) — 2025-04-29T19:52:21+00:00

2025/04/03 13:08		current
Line 3:		Line 3:
	* Date: 2024-11-30		* Date: 2024-11-30
	* Author: Daniel Scherzer, daniel.e.scherzer@gmail.com		* Author: Daniel Scherzer, daniel.e.scherzer@gmail.com
-	* Status: Pending Implementation	+	* Status: Implemented
	* First Published at: https://wiki.php.net/rfc/attributes-on-constants		* First Published at: https://wiki.php.net/rfc/attributes-on-constants
	* Implementation: https://github.com/php/php-src/pull/16952		* Implementation: https://github.com/php/php-src/pull/16952

binary_string_deprecation

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2017/02/20 20:02		current
Line 67:		Line 67:
	* Implementation: [[https://github.com/php/php-src/pull/2322]]		* Implementation: [[https://github.com/php/php-src/pull/2322]]
	* Language Specification: [[https://github.com/php/php-langspec/pull/188]]		* Language Specification: [[https://github.com/php/php-langspec/pull/188]]
-	* Documentation: [[https://edit.php.net/?patch=en/language/types/type-juggling.xml&project=PHP]]	+	* Documentation: //Patch was deleted. It removed the mention of the prefix from the type-juggling page.//

	===== References =====		===== References =====
	This deprecation is also proposed in [[rfc:deprecations_php_7_2\|PHP RFC: Deprecations for PHP 7.2]]. The reason for a separate RFC is the impact on the PHAR extension.		This deprecation is also proposed in [[rfc:deprecations_php_7_2\|PHP RFC: Deprecations for PHP 7.2]]. The reason for a separate RFC is the impact on the PHAR extension.

nullable-not-nullable-cast-operator

Anonymous (anonymous@undisclosed.example.com) — 2025-10-31T13:46:20+00:00

2025/10/31 13:45		current
Line 593:		Line 593:
	* The syntax <php>(!type)</php> is currently technically correct and could be interpreted as the negation of a constant named <php>type</php>. This would mean that a constant is defined with the name of a built-in scalar type, which seems highly unlikely.		* The syntax <php>(!type)</php> is currently technically correct and could be interpreted as the negation of a constant named <php>type</php>. This would mean that a constant is defined with the name of a built-in scalar type, which seems highly unlikely.

-	Apart from this case, the new syntax and has no backward compatibility issues:	+	Apart from this case, the new syntax has no other backward compatibility issues:

	* The syntax <php>(?type)</php> is currently parse errors		* The syntax <php>(?type)</php> is currently parse errors

php-community

Anonymous (anonymous@undisclosed.example.com) — 2026-03-16T17:21:55+00:00

2026/03/16 17:02		current
Line 27:		Line 27:
	* [[#api\|API]]		* [[#api\|API]]
	* [[#changelog\|Changelog]]		* [[#changelog\|Changelog]]
		+	* [[#110\|1.1.0]]
	* [[#101\|1.0.1]]		* [[#101\|1.0.1]]

Line 182:		Line 183:
	Features introduced by an accepted community RFC can only be removed 6 months after it is accepted, through a separate removal community RFC.		Features introduced by an accepted community RFC can only be removed 6 months after it is accepted, through a separate removal community RFC.

-	A feature is eligible for removal only if both** of the following conditions are met:**	+	Removal community RFCs occur through GitHub reactions as usual open to all (in order to gauge community interest), but **only votes of internals are countedd.**

-	* It has no active maintainer listed in the accepted community RFC design document.\\	+	A feature is eligible for removal if:

-	* Adoption is negligible, as evidenced by Packagist statistics.	+	* It has no active owners (no commits, and listed owners do not reply to emails in the last 6 months).\\
		+	An owner may also be removed from the owners list of an RFC by internals members and maintainers in case of violations.\\

-	The burden of proof lies with the party proposing removal, not with users. When a removal community RFC is accepted, a deprecation period of at least 3 stable ''%%php-community%%'' releases follows, during which the feature is still shipped but marked as deprecated, giving users time to speak up (which can potentially move the RFC back to Active or Pending), take over maintenance (which will automatically reject the removal RFC, even if already accepted), or migrate away.	+	* OR, if adoption is negligible, as evidenced by Packagist statistics (or other telemetry, as defined by later RFCs).
		+
		+	When a removal community RFC is accepted, a deprecation period of at least 1 stable ''%%php-community%%'' release follows, during which the feature is still shipped but marked as deprecated, giving users time to speak up (which can potentially move the RFC back to Active or Pending), take over maintenance (which will automatically reject the removal RFC, even if already accepted), or migrate away.

	This prevents removal of an actively-maintained, well-adopted feature through this process, so that users can calmly rely on PHP feature extensions.		This prevents removal of an actively-maintained, well-adopted feature through this process, so that users can calmly rely on PHP feature extensions.
Line 459:		Line 463:

	==== Changelog ====		==== Changelog ====
		+
		+	=== 1.1.0 ===
		+
		+	* Voting (clarification) — Clarified that only internals members with voting rights count for quorum/veto calculations, and emphasized internals-only quorum wording.
		+	* Community RFC owners (clarification) — Clarified that compatibility fixes caused by breaking internal PHP API changes are handled by whoever introduces those breaking changes.
		+	* Removal of community RFC features (policy update)
		+
		+	Removal voting remains open to all for sentiment, but only internals votes are counted for outcome.
		+
		+	Eligibility changed from strict ''%%AND%%'' conditions to an ''%%OR%%'' policy: - no active owners (defined as no commits and no replies from listed owners in 6 months; with owner removal possible in case of violations); - or negligible adoption, based on Packagist stats/telemetry.
		+
		+	Deprecation period after acceptance of a removal RFC was reduced from at least 3 stable ''%%php-community%%'' releases to at least 1 stable release.
		+
		+	* Feature extensions (new clarifications) — Added guidance that releases should ideally ship all major versions of feature extensions together, that security updates apply to all currently shipped versions, and that retiring old majors is up to feature owners based on adoption.

	=== 1.0.1 ===		=== 1.0.1 ===

faq

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2010/08/17 03:56		current
Line 1:		Line 1:
	====== FAQ ======		====== FAQ ======
	.. and other mailing list answers.		.. and other mailing list answers.
		+
		+	This page is meant to be a quick and easy scratchpad of good answers and ideas - candidates to be polished and migrated into the proper FAQs.

	===== Where's the proper FAQs? ======		===== Where's the proper FAQs? ======
-	* [[http://pear.php.net/manual/en/faq.users.php Users]]	+	* [[http://pear.php.net/manual/en/faq.users.php\|Users]]
-	* [[http://pear.php.net/manual/en/faq.devs.php Developers]]	+	* [[http://pear.php.net/manual/en/faq.devs.php\|Developers]]

	===== How do I become a PEAR developer? =====		===== How do I become a PEAR developer? =====

delayedtargetvalidation_attribute

Anonymous (anonymous@undisclosed.example.com) — 2025-08-20T07:41:59+00:00

2025/08/01 14:23		current
Line 3:		Line 3:
	* Date: 2025.06.17		* Date: 2025.06.17
	* Author: Daniel Scherzer, daniel.e.scherzer@gmail.com		* Author: Daniel Scherzer, daniel.e.scherzer@gmail.com
-	* Status: Pending implementation / landing	+	* Status: Implemented in PHP 8.5
	* First Published at: https://wiki.php.net/rfc/DelayedTargetValidation_attribute		* First Published at: https://wiki.php.net/rfc/DelayedTargetValidation_attribute
		+	* Implementation: https://github.com/php/php-src/pull/18817

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

deprecations_php_8_1

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2021/07/10 02:06		current
Line 2:		Line 2:
	* Date: 2021-02-23		* Date: 2021-02-23
	* Author: Nikita Popov <nikic@php.net>, George Peter Banyard <girgias@php.net>, Máté Kocsis <kocsismate@php.net>, Rowan Tommins <imsop@php.net>		* Author: Nikita Popov <nikic@php.net>, George Peter Banyard <girgias@php.net>, Máté Kocsis <kocsismate@php.net>, Rowan Tommins <imsop@php.net>
-	* Status: Voting	+	* Status: Implemented

	===== Introduction =====		===== Introduction =====
Line 68:		Line 68:
	This was initially discussed in: https://github.com/php/php-src/pull/4423.		This was initially discussed in: https://github.com/php/php-src/pull/4423.

-	<doodle title="Deprecate date_sunrise() and date_sunset()?" auth="nikic" voteType="single" closed="false">	+	<doodle title="Deprecate date_sunrise() and date_sunset()?" auth="nikic" voteType="single" closed="true">
	* Yes		* Yes
	* No		* No
Line 83:		Line 83:
	As such, the proposal is to deprecate key(), current(), next(), prev() and reset() on objects. The suggested replacement is to cast the object to array first, or call ''get_mangled_object_vars()'', depending on what the intention is.		As such, the proposal is to deprecate key(), current(), next(), prev() and reset() on objects. The suggested replacement is to cast the object to array first, or call ''get_mangled_object_vars()'', depending on what the intention is.

-	<doodle title="Deprecate key(), current(), next(), prev(), reset() on objects?" auth="nikic" voteType="single" closed="false">	+	<doodle title="Deprecate key(), current(), next(), prev(), reset() on objects?" auth="nikic" voteType="single" closed="true">
	* Yes		* Yes
	* No		* No
Line 112:		Line 112:
	The proposal is to deprecate calling ''mb_check_encoding()'' without arguments.		The proposal is to deprecate calling ''mb_check_encoding()'' without arguments.

-	<doodle title="Deprecate mb_check_encoding() without argument?" auth="nikic" voteType="single" closed="false">	+	<doodle title="Deprecate mb_check_encoding() without argument?" auth="nikic" voteType="single" closed="true">
	* Yes		* Yes
	* No		* No
Line 125:		Line 125:
	As a caveat, if ''get_parent_class()'' is used to check whether the class has a parent, it is necessary to use ''get_parent_class(self::class)'' instead, because ''parent::class'' will generate an error if used inside a class without parent.		As a caveat, if ''get_parent_class()'' is used to check whether the class has a parent, it is necessary to use ''get_parent_class(self::class)'' instead, because ''parent::class'' will generate an error if used inside a class without parent.

-	<doodle title="Deprecate get_class(), get_parent_class() and get_called_class() without argument?" auth="nikic" voteType="single" closed="false">	+	<doodle title="Deprecate get_class(), get_parent_class() and get_called_class() without argument?" auth="nikic" voteType="single" closed="true">
	* Yes		* Yes
	* No		* No
Line 138:		Line 138:
	This was pointed out in: https://github.com/php/php-src/pull/5556		This was pointed out in: https://github.com/php/php-src/pull/5556

-	<doodle title="Deprecate FILE_BINARY and FILE_TEXT constants?" auth="nikic" voteType="single" closed="false">	+	<doodle title="Deprecate FILE_BINARY and FILE_TEXT constants?" auth="nikic" voteType="single" closed="true">
	* Yes		* Yes
	* No		* No
Line 153:		Line 153:
	While ''fopen()'' defaults to binary mode, some other functions like ''proc_open()'' on pipe descriptors still default to text mode. Cases that use ''t'' as the default mode are excluded from this deprecation for the time being. We may include them in the future, which would require explicitly specifying ''b'' mode for them during a transitionary period.		While ''fopen()'' defaults to binary mode, some other functions like ''proc_open()'' on pipe descriptors still default to text mode. Cases that use ''t'' as the default mode are excluded from this deprecation for the time being. We may include them in the future, which would require explicitly specifying ''b'' mode for them during a transitionary period.

-	<doodle title="Deprecate t fopen mode?" auth="nikic" voteType="single" closed="false">	+	<doodle title="Deprecate t fopen mode?" auth="nikic" voteType="single" closed="true">
	* Yes		* Yes
	* No		* No
Line 166:		Line 166:
	The proposal is to deprecate passing a boolean to this method argument.		The proposal is to deprecate passing a boolean to this method argument.

-	<doodle title="Deprecate passing bool for $value argument of IntlCalendar::roll()?" auth="nikic" voteType="single" closed="false">	+	<doodle title="Deprecate passing bool for $value argument of IntlCalendar::roll()?" auth="nikic" voteType="single" closed="true">
	* Yes		* Yes
	* No		* No
Line 191:		Line 191:
	The proposal is to deprecate the ability to access static properties and static methods directly on traits.		The proposal is to deprecate the ability to access static properties and static methods directly on traits.

-	<doodle title="Deprecate accessing static members on traits?" auth="nikic" voteType="single" closed="false">	+	<doodle title="Deprecate accessing static members on traits?" auth="nikic" voteType="single" closed="true">
	* Yes		* Yes
	* No		* No
Line 208:		Line 208:
	The proposal is to deprecate the ''strptime()'' function in favor of portable alternatives.		The proposal is to deprecate the ''strptime()'' function in favor of portable alternatives.

-	<doodle title="Deprecate strptime()?" auth="nikic" voteType="single" closed="false">	+	<doodle title="Deprecate strptime()?" auth="nikic" voteType="single" closed="true">
	* Yes		* Yes
	* No		* No
Line 221:		Line 221:
	The proposal is to deprecate ''strftime()'' and ''gmstrftime()'' in favor of these alternatives.		The proposal is to deprecate ''strftime()'' and ''gmstrftime()'' in favor of these alternatives.

-	<doodle title="Deprecate strftime() and gmstrftime()?" auth="nikic" voteType="single" closed="false">	+	<doodle title="Deprecate strftime() and gmstrftime()?" auth="nikic" voteType="single" closed="true">
	* Yes		* Yes
	* No		* No
Line 232:		Line 232:
	The proposal is to deprecate ''mhash()'', ''mhash_keygen_s2k()'', ''mhash_count()'', ''mhash_get_block_size()'' and ''mhash_get_hash_name()'' in favor of the standard ext/hash functionality.		The proposal is to deprecate ''mhash()'', ''mhash_keygen_s2k()'', ''mhash_count()'', ''mhash_get_block_size()'' and ''mhash_get_hash_name()'' in favor of the standard ext/hash functionality.

-	<doodle title="Deprecate mhash() family of functions?" auth="nikic" voteType="single" closed="false*">	+	<doodle title="Deprecate mhash() family of functions?" auth="nikic" voteType="single" closed="true*">
	* Yes		* Yes
	* No		* No
Line 251:		Line 251:
	The proposal is to deprecate passing of non-strings to ''ctype_()'' functions. In the next major versions, ''ctype_()'' will be changed to accept a string parameter under standard semantics.		The proposal is to deprecate passing of non-strings to ''ctype_()'' functions. In the next major versions, ''ctype_()'' will be changed to accept a string parameter under standard semantics.

-	<doodle title="Deprecate int parameters to ctype_() functions?" auth="nikic" voteType="single" closed="false*">	+	<doodle title="Deprecate int parameters to ctype_() functions?" auth="nikic" voteType="single" closed="true*">
	* Yes		* Yes
	* No		* No
Line 268:		Line 268:
	The proposal is to throw a compile-time deprecation for function signatures using by-reference returns in conjunction with void.		The proposal is to throw a compile-time deprecation for function signatures using by-reference returns in conjunction with void.

-	<doodle title="Deprecate return by reference with void type?" auth="nikic" voteType="single" closed="false">	+	<doodle title="Deprecate return by reference with void type?" auth="nikic" voteType="single" closed="true">
	* Yes		* Yes
	* No		* No
Line 279:		Line 279:
	The proposal is to deprecate this constant.		The proposal is to deprecate this constant.

-	<doodle title="Deprecate NIL constant defined by the IMAP extension?" auth="nikic" voteType="single" closed="false">	+	<doodle title="Deprecate NIL constant defined by the IMAP extension?" auth="nikic" voteType="single" closed="true">
	* Yes		* Yes
	* No		* No
Line 305:		Line 305:
	The proposal is to deprecate any use of the "default connection" in ext/pgsql. A deprecation notice will be thrown if a pgsql function is called without explicitly specifying the connection.		The proposal is to deprecate any use of the "default connection" in ext/pgsql. A deprecation notice will be thrown if a pgsql function is called without explicitly specifying the connection.

-	<doodle title="Deprecate calling overloaded pgsql functions without the connection argument?" auth="nikic" voteType="single" closed="false">	+	<doodle title="Deprecate calling overloaded pgsql functions without the connection argument?" auth="nikic" voteType="single" closed="true">
	* Yes		* Yes
	* No		* No
Line 330:		Line 330:
	</PHP>		</PHP>

-	<doodle title="Deprecate $num_points parameter of image(open\|filled)polygon?" auth="nikic" voteType="single" closed="false">	+	<doodle title="Deprecate $num_points parameter of image(open\|filled)polygon?" auth="nikic" voteType="single" closed="true">
	* Yes		* Yes
	* No		* No
Line 355:		Line 355:
	</PHP>		</PHP>

-	<doodle title="Deprecate mysqli::init()?" auth="nikic" voteType="single" closed="false">	+	<doodle title="Deprecate mysqli::init()?" auth="nikic" voteType="single" closed="true">
	* Yes		* Yes
	* No		* No
Line 372:		Line 372:
	The proposal is to emit a deprecation warning if ''filter.default'' is set to a value other than ''unsafe_raw'' (the default). No separate deprecation warning is emitted for ''filter.default_options'', but both ini settings will be removed together in the next major version.		The proposal is to emit a deprecation warning if ''filter.default'' is set to a value other than ''unsafe_raw'' (the default). No separate deprecation warning is emitted for ''filter.default_options'', but both ini settings will be removed together in the next major version.

-	<doodle title="Deprecate filter.default ini setting?" auth="nikic" voteType="single" closed="false">	+	<doodle title="Deprecate filter.default ini setting?" auth="nikic" voteType="single" closed="true">
	* Yes		* Yes
	* No		* No
Line 383:		Line 383:
	The proposal is to emit a deprecation warning if ''auto_detect_line_endings'' is enabled.		The proposal is to emit a deprecation warning if ''auto_detect_line_endings'' is enabled.

-	<doodle title="Deprecate auto_detect_line_endings ini setting?" auth="nikic" voteType="single" closed="false">	+	<doodle title="Deprecate auto_detect_line_endings ini setting?" auth="nikic" voteType="single" closed="true">
	* Yes		* Yes
	* No		* No
Line 400:		Line 400:
	The proposal is to deprecate passing an ''ssl_method'' option to the constructor, and recommend the use of ''context'' option instead.		The proposal is to deprecate passing an ''ssl_method'' option to the constructor, and recommend the use of ''context'' option instead.

-	<doodle title="Deprecate ssl_method option to SoapClient constructor?" auth="nikic" voteType="single" closed="false">	+	<doodle title="Deprecate ssl_method option to SoapClient constructor?" auth="nikic" voteType="single" closed="true">
	* Yes		* Yes
	* No		* No
Line 415:		Line 415:
	The proposal is to deprecate the ''FILTER_SANITIZE_STRING'' constant, its alias ''FILTER_SANITIZE_STRIPPED'', as well as use of this filter.		The proposal is to deprecate the ''FILTER_SANITIZE_STRING'' constant, its alias ''FILTER_SANITIZE_STRIPPED'', as well as use of this filter.

-	<doodle title="Deprecate FILTER_SANITIZE_STRING?" auth="nikic" voteType="single" closed="false">	+	<doodle title="Deprecate FILTER_SANITIZE_STRING?" auth="nikic" voteType="single" closed="true">
	* Yes		* Yes
	* No		* No
Line 426:		Line 426:
	The proposal is to throw a deprecation warning if ''oci8.old_oci_close_semantics'' is enabled.		The proposal is to throw a deprecation warning if ''oci8.old_oci_close_semantics'' is enabled.

-	<doodle title="Deprecate oci8.old_oci_close_semantics INI setting?" auth="nikic" voteType="single" closed="false">	+	<doodle title="Deprecate oci8.old_oci_close_semantics INI setting?" auth="nikic" voteType="single" closed="true">
	* Yes		* Yes
	* No		* No
Line 437:		Line 437:
	The proposal is to deprecate the ''odbc_result_all()'' function.		The proposal is to deprecate the ''odbc_result_all()'' function.

-	<doodle title="Deprecate odbc_result_all()?" auth="nikic" voteType="single" closed="false">	+	<doodle title="Deprecate odbc_result_all()?" auth="nikic" voteType="single" closed="true">
	* Yes		* Yes
	* No		* No

internal_method_return_types

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2021/05/06 07:47		current
Line 2:		Line 2:
	* Date: 2021-03-06		* Date: 2021-03-06
	* Author: Máté Kocsis <kocsismate@php.net>		* Author: Máté Kocsis <kocsismate@php.net>
-	* Status: Accepted	+	* Status: Implemented
	* Implementation: https://github.com/php/php-src/pull/6548		* Implementation: https://github.com/php/php-src/pull/6548
	* Target Version: PHP 8.1		* Target Version: PHP 8.1

magicquotes

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2011/07/18 16:21		current
Line 7:		Line 7:
	* Note: //This RFC is about PHP 6.0 (our old HEAD/Trunk) and NOT PHP 5.4//		* Note: //This RFC is about PHP 6.0 (our old HEAD/Trunk) and NOT PHP 5.4//
	* First Published at: http://wiki.php.net/rfc/magicquotes		* First Published at: http://wiki.php.net/rfc/magicquotes
		+	* Followed up by: [[rfc/magicquotes_finale]] for PHP 5.4

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

soft-deprecate-sleep-wakeup

Anonymous (anonymous@undisclosed.example.com) — 2025-10-06T08:33:22+00:00

2025/10/04 14:59		current
Line 3:		Line 3:
	* Date: 2025-09-05		* Date: 2025-09-05
	* Authors: Nicolas Grekas <nicolas.grekas@php.net>, Jakub Zelenka <bukka@php.net>		* Authors: Nicolas Grekas <nicolas.grekas@php.net>, Jakub Zelenka <bukka@php.net>
-	* Status: Accepted	+	* Status: Implemented
	* Implementation: https://github.com/php/php-src/pull/19966		* Implementation: https://github.com/php/php-src/pull/19966

assert-string-eval-cleanup

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2023/07/12 14:14		current
Line 3:		Line 3:
	* Date: 2023-05-31		* Date: 2023-05-31
	* Author: George Peter Banyard, <girgias@php.net>		* Author: George Peter Banyard, <girgias@php.net>
-	* Status: In Voting	+	* Status: Implemented: https://github.com/php/php-src/commit/3d4ff5ae22e73a3f4c41a26c0d2eb11646ecdd88
	* Target Version: PHP 8.3		* Target Version: PHP 8.3
	* First Published at: https://wiki.php.net/rfc/assert-string-eval-cleanup		* First Published at: https://wiki.php.net/rfc/assert-string-eval-cleanup
Line 107:		Line 107:

	===== Implementation =====		===== Implementation =====
-	After the project is implemented, this section should contain	+
-	- the version(s) it was merged into	+	Implemented in PHP 8.3:
-	- a link to the git commit(s)	+
		+	- Commit: https://github.com/php/php-src/commit/3d4ff5ae22e73a3f4c41a26c0d2eb11646ecdd88
	- a link to the PHP manual entry for the feature		- a link to the PHP manual entry for the feature
-	- a link to the language specification section (if any)

continue_on_switch_deprecation

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2018/06/27 16:04		current
Line 3:		Line 3:
	* Author: Nikita Popov <nikic@php.net>		* Author: Nikita Popov <nikic@php.net>
	* Implementation: https://github.com/php/php-src/pull/3323		* Implementation: https://github.com/php/php-src/pull/3323
-	* Status: Under Discussion	+	* Status: Withdrawn
		+
		+	Based on the RFC discussion, we decided to instead implement this as a simple warning, which has happened in https://github.com/php/php-src/pull/3364.

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

deprecate_curly_braces_array_access

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2019/07/19 15:30		current
Line 4:		Line 4:
	* Status: Implemented (in PHP 7.4)		* Status: Implemented (in PHP 7.4)
	* Discussion: https://externals.io/message/104744		* Discussion: https://externals.io/message/104744
-	* Target version: PHP 7.4	+	* Targets: PHP 7.4
	* Implementation: https://github.com/php/php-src/pull/4416		* Implementation: https://github.com/php/php-src/pull/4416

deprecate-implicitly-nullable-types

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2024/03/13 18:22		current
Line 4:		Line 4:
	* Date: 2023-12-20		* Date: 2023-12-20
	* Authors: Máté Kocsis <kocsismate@php.net>, Gina Peter Banyard <girgias@php.net>		* Authors: Máté Kocsis <kocsismate@php.net>, Gina Peter Banyard <girgias@php.net>
-	* Status: Accepted	+	* Status: Implemented
	* Target Version: PHP 8.4		* Target Version: PHP 8.4
	* Implementation: [[https://github.com/php/php-src/pull/12959\|https://github.com/php/php-src/pull/12959]]		* Implementation: [[https://github.com/php/php-src/pull/12959\|https://github.com/php/php-src/pull/12959]]

deprecations_php_8_3

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2023/07/11 15:36		current
Line 2:		Line 2:
	* Date: 2022-08-01		* Date: 2022-08-01
	* Authors: Christoph M. Becker <cmb@php.net>, George Peter Banyard <girgias@php.net>, Máté Kocsis <kocsismate@php.net>		* Authors: Christoph M. Becker <cmb@php.net>, George Peter Banyard <girgias@php.net>, Máté Kocsis <kocsismate@php.net>
-	* Status: Accepted	+	* Status: Implemented
-	* Implementation: https://github.com/php/php-src/commit/61251093ab5b1ebbe112362893ff8b9edba215e0 (MT_RAND_PHP), https://github.com/php/php-src/commit/69a8b63ecf4fec1b35ef4da1ac9579321c45f97f (ldap_connect)	+	* Implementation:
		+	* MT_RAND_PHP: https://github.com/php/php-src/commit/61251093ab5b1ebbe112362893ff8b9edba215e0
		+	* <php>ldap_connect()</php>: https://github.com/php/php-src/commit/69a8b63ecf4fec1b35ef4da1ac9579321c45f97f
		+	* <php>mb_strimwidth()</php>: https://github.com/php/php-src/commit/af3c220abbff2415ccd79aeac1888edfc106ffa6
		+	* NumberFormater::TYPE_CURRENCY: https://github.com/php/php-src/commit/d65251e6e863684f8fc7ddc9c0fba7cf53483f7f

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

null_coercion_consistency

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2022/10/16 07:37		current
Line 14:		Line 14:
	===== Introduction =====		===== Introduction =====

-	PHP 8.1 introduced [[https://wiki.php.net/rfc/deprecate_null_to_scalar_internal_arg\|Deprecate passing null to non-nullable arguments of internal functions]]. While the consistency is welcome (user-defined vs internal functions), for those not using strict Static Analysis or //strict_types=1//, the breaking of NULL coercion creates an upgrade problem.	+	PHP 8.1 introduced [[https://wiki.php.net/rfc/deprecate_null_to_scalar_internal_arg\|Deprecate passing null to non-nullable arguments of internal functions]]. While the consistency is welcome (user-defined vs internal functions), for those not using strict Static Analysis or //strict_types=1//, the breaking of NULL coercion creates a difficult BC problem.

-	This RFC does not change anything for //strict_types=1// (or strict static analysis), as strict type checks can be useful. For example, developers can view NULL as a missing/invalid value (not as a value in itself), and passing NULL to a function like //htmlspecialchars()// could indicate a problem.	+	This RFC does not change anything for //strict_types=1// (or static analysis), as strict type checks can be useful. For example, some developers view NULL as a missing/invalid value (not as a value in itself), and passing NULL to a function like //htmlspecialchars()// might indicate a problem.

-	Roughly 15% of scripts use //strict_types=1// (calculation below).	+	There was a [[https://externals.io/message/112327\|short discussion]] about the original RFC, but with the exception of Craig Duncan, there was no discussion about the BC problems, or the inconsistency of NULL coercion compared to string/int/float/bool coercion, or other contexts like string concatenation, == comparisons, arithmetics, sprintf, print, echo, array keys, etc.

-	Roughly 33% of developers use static analysis (realistically it's less than this, details below).	+	The intention is to also keep [[https://github.com/Girgias/unify-typing-modes-rfc\|Unify PHP's typing modes]] by George Peter Banyard in mind, with coercions like //substr($string, "offset")// and //htmlspecialchars(array())// as being clearly problematic; whereas the following is common:
-		+
-	There was a [[https://externals.io/message/112327\|short discussion]] about the original RFC, but with the exception of Craig Duncan, there was no consideration for the problems this creates with existing code (or the inconsistency of NULL coercion compared to string/int/float/bool coercion; or other contexts like string concatenation, == comparisons, arithmetics, sprintf, etc).	+
-		+
-	The intention is to also keep [[https://github.com/Girgias/unify-typing-modes-rfc\|Unify PHP's typing modes]] by George Peter Banyard in mind, with coercions like //substr($string, "offset")// and //htmlspecialchars(array())// as being clearly problematic; whereas the following is common, and has been fine:	+

	<code php>		<code php>
-	$search = filter_input(INPUT_GET, 'q'); // Or similar (examples below)	+	$search = ($_GET['q'] ?? NULL); // Or similar (examples below)

-	echo 'Results for ' . htmlspecialchars($search);	+	echo 'Results for ' . htmlspecialchars($search); // Fatal Error?!?
	</code>		</code>
		+
		+	Roughly 15% of scripts use //strict_types=1// (calculation below).
		+
		+	Roughly 33% of developers use static analysis (realistically it's less than this, details below).

	===== Problem =====		===== Problem =====
Line 44:		Line 44:
	- [[https://www.php.net/manual/en/language.types.float.php\|To Float]]: "For values of other types, the conversion is performed by converting the value to int first and then to float"		- [[https://www.php.net/manual/en/language.types.float.php\|To Float]]: "For values of other types, the conversion is performed by converting the value to int first and then to float"
	- [[https://www.php.net/manual/en/language.types.boolean.php\|To Boolean]]: "When converting to bool, the following values are considered false [...] the special type NULL"		- [[https://www.php.net/manual/en/language.types.boolean.php\|To Boolean]]: "When converting to bool, the following values are considered false [...] the special type NULL"
		+
		+	String/Int/Float/Bool can be coerced; Arrays, Resources, and Objects (without toString) cannot be coerced (for fairly obvious reasons).
		+
		+	Or, NULL "can be coerced to the type requested by the hint without data loss and without creation of likely unintended data" ([[https://wiki.php.net/rfc/coercive_sth\|ref]]).
		+
		+	PHP 7.0 introduced the ability for user-defined functions to specify parameter types via the [[https://wiki.php.net/rfc/scalar_type_hints_v5#behaviour_of_weak_type_checks\|Scalar Type Declarations RFC]], where the implementation triggered Type Errors for those using //strict_types=1//, and otherwise used coercion for string/int/float/bool, but not NULL, PHP 8.1 updated internal function parameters to work in the same way.

	==== Current State ====		==== Current State ====

	<code php>		<code php>
-	// echo(string ...$expressions): void
-	// print(string $expression): int
	print('A');		print('A');
	print(1);		print(1);
	print(1.2);		print(1.2);
	print(false);		print(false);
-	print(NULL); // Fine, coerced to empty string.	+	print(NULL); // Fine, still coerced to empty string.
		+
		+	echo NULL; // Fine, still coerced to empty string.

	var_dump(3 + '5' + NULL); // Fine, int(8)		var_dump(3 + '5' + NULL); // Fine, int(8)
Line 62:		Line 68:

	$o[] = ('' == '');		$o[] = ('' == '');
-	$o[] = ('' == NULL); // Fine, coerced to empty string.	+	$o[] = ('' == NULL); // Fine, still coerced to empty string.

	$o[] = 'ConCat ' . 'A';		$o[] = 'ConCat ' . 'A';
Line 68:		Line 74:
	$o[] = 'ConCat ' . 1.2;		$o[] = 'ConCat ' . 1.2;
	$o[] = 'ConCat ' . false;		$o[] = 'ConCat ' . false;
-	$o[] = 'ConCat ' . NULL; // Fine, coerced to empty string.	+	$o[] = 'ConCat ' . NULL; // Fine, still coerced to empty string.

	$o[] = sprintf('%s', 'A');		$o[] = sprintf('%s', 'A');
Line 74:		Line 80:
	$o[] = sprintf('%s', 1.2);		$o[] = sprintf('%s', 1.2);
	$o[] = sprintf('%s', false);		$o[] = sprintf('%s', false);
-	$o[] = sprintf('%s', NULL); // Fine, coerced to empty string.	+	$o[] = sprintf('%s', NULL); // Fine, still coerced to empty string.

	$o[] = htmlspecialchars('A');		$o[] = htmlspecialchars('A');
Line 83:		Line 89:
	</code>		</code>

-	With user-defined functions, while there hasn't been a backwards compatibility issue, it still highlights the coercion inconsistency, in an environment that does not expect type checking, despite NULL being a value that "can be coerced to the type requested by the hint without data loss and without creation of likely unintended data":	+	With user-defined functions, this inconsistency is also noted:

	<code php>		<code php>
Line 97:		Line 103:

	user_function(3.3, 3.3, 3.3, 3.3);		user_function(3.3, 3.3, 3.3, 3.3);
-	// string(3) "3.3" / int(3) / float(3.3) / bool(true)	+	// string(3) "3.3" / int(3), lost precision / float(3.3) / bool(true)

	user_function(false, false, false, false);		user_function(false, false, false, false);
Line 103:		Line 109:

	user_function(NULL, NULL, NULL, NULL);		user_function(NULL, NULL, NULL, NULL);
-	// Uncaught TypeError x4?	+	// Fatal error, Uncaught TypeError x4!
	</code>		</code>
-
-	Arrays, Resources, and Objects (without toString) cannot be coerced (for fairly obvious reasons).
-
-	String/Int/Float/Bool can be coerced.
-
-	NULL can usually be coerced (e.g. string concatenation, == comparisons, arithmetics, sprintf, print, echo, array keys), but...
-
-	- PHP 7.0 introduced the ability for user-defined functions to specify parameter types via the [[https://wiki.php.net/rfc/scalar_type_hints_v5#behaviour_of_weak_type_checks\|Scalar Type Declarations RFC]], where the implementation triggered Type Errors for those using //strict_types=1//, and otherwise used coercion for string/int/float/bool, but not NULL.
-	- PHP 8.1 updated internal function parameters to work in the same way.

	==== Scalar Types ====		==== Scalar Types ====

-	[[https://news-web.php.net/php.internals/117523\|George Peter Banyard]] notes that "Userland scalar types [...] did not include coercion from NULL for //very// good reasons". The only reason mentioned in [[https://wiki.php.net/rfc/scalar_type_hints_v5\|Scalar Type Declarations]] is "to be consistent with our existing type declarations" (no further details given).	+	The [[https://wiki.php.net/rfc/scalar_type_hints_v5\|Scalar Type Declarations]] RFC says "it should be possible for existing userland libraries to add scalar type declarations without breaking compatibility", but this is not the case, because of NULL. This has made adoption of type declarations harder, as it does not work like the following:
-		+
-	The RFC also says "it should be possible for existing userland libraries to add scalar type declarations without breaking compatibility", but this is not the case, because of NULL. This has made adoption of type declarations harder, as it does not work like the following:	+

	<code php>		<code php>
Line 137:		Line 132:
	</code>		</code>

-	Some developers view NULL as a missing/invalid value, and passing NULL to a function like //htmlspecialchars()// could indicate a problem (can a be useful check for static analysis, or in the context of //strict_types=1//).	+	[[https://news-web.php.net/php.internals/117523\|George Peter Banyard]] notes that "Userland scalar types [...] did not include coercion from NULL for //very// good reasons".
		+
		+	The [[https://wiki.php.net/rfc/scalar_type_hints_v5\|Scalar Type Declarations]] RFC says "The only exception to this is the handling of NULL: in order to be consistent with our existing type declarations for classes, callables and arrays, NULL is not accepted by default, unless it is a parameter and is explicitly given a default value of NULL", which goes against the documentation (as noted above) where the coercion from NULL is well defined (i.e. NULL is more like a string/int/float/bool, rather than an object/callable/array).

	==== Examples ====		==== Examples ====
Line 155:		Line 152:
	$search = $request->getGet('q'); // CodeIgniter		$search = $request->getGet('q'); // CodeIgniter

-	$value = mysqli_fetch_row($result);
-	$value = json_decode($json); // Invalid JSON, or nesting limit.
	$value = array_pop($empty_array);		$value = array_pop($empty_array);
		+	$value = mysqli_fetch_row($result);
	</code>		</code>

-	Examples functions, often working with user input, where NULL has been fine:	+	Examples functions, often working with user input, where NULL has always been accepted/coerced:

	<code php>		<code php>
Line 198:		Line 194:
	HTML Templating engines like [[https://github.com/laravel/framework/blob/ab1506091b9f166b312b3990d07b2e21d971f2e6/src/Illuminate/Support/helpers.php#L119\|Laravel Blade]] suppress this deprecation with null-coalescing ([[https://github.com/laravel/framework/pull/36262/files#diff-15b0a3e2eb2d683222d19dfacc04c616a3db4e3d3b3517e96e196ccbf838f59eR118\|patch]]); or [[https://github.com/twigphp/Twig/blob/b4d6723715da57667cca851051eba3786714290d/src/Extension/EscaperExtension.php#L195\|Symphony Twig]] which preserves NULL, but it's often passed to //echo// (which accepts it, despite the [[https://www.php.net/echo\|echo documentation]] saying it accepts non-nullable strings).		HTML Templating engines like [[https://github.com/laravel/framework/blob/ab1506091b9f166b312b3990d07b2e21d971f2e6/src/Illuminate/Support/helpers.php#L119\|Laravel Blade]] suppress this deprecation with null-coalescing ([[https://github.com/laravel/framework/pull/36262/files#diff-15b0a3e2eb2d683222d19dfacc04c616a3db4e3d3b3517e96e196ccbf838f59eR118\|patch]]); or [[https://github.com/twigphp/Twig/blob/b4d6723715da57667cca851051eba3786714290d/src/Extension/EscaperExtension.php#L195\|Symphony Twig]] which preserves NULL, but it's often passed to //echo// (which accepts it, despite the [[https://www.php.net/echo\|echo documentation]] saying it accepts non-nullable strings).

-	I'd argue a very strict level of type checking (that prevents all forms of coercion) is best done by Static Analysis, which can check if a variable can be nullable, and it can decide if this is a problem, in the same way that a string (e.g. '15') being provided to integer parameter could be seen as a problem.	+	I'd argue strict type checking (that prevents all forms of coercion) should be done via Static Analysis or via //strict_types=1// opt-in, like how a string (e.g. '15') being provided to integer parameter could identify a problem in some development environments.

	There are approximately [[https://github.com/craigfrancis/php-allow-null-rfc/blob/main/functions-change.md\|335 parameters affected by this deprecation]].		There are approximately [[https://github.com/craigfrancis/php-allow-null-rfc/blob/main/functions-change.md\|335 parameters affected by this deprecation]].
Line 207:		Line 203:

	The only realistic way for developers to find when NULL is passed to these internal functions is to use the deprecation notices (not ideal).		The only realistic way for developers to find when NULL is passed to these internal functions is to use the deprecation notices (not ideal).
		+
		+	And this does not stop new issues being introduced, as developers may not consider when variables might be NULL (e.g. a browser extension or network issues affecting GET/POST variables).

	It is possible to use very strict Static Analysis, to follow every variable from source to sink (to check if a variable could be NULL), but most developers are not in a position to do this (i.e. not using static analysis, or not at a high enough level, or they are using a baseline to ignore).		It is possible to use very strict Static Analysis, to follow every variable from source to sink (to check if a variable could be NULL), but most developers are not in a position to do this (i.e. not using static analysis, or not at a high enough level, or they are using a baseline to ignore).
Line 322:		Line 320:
	</code>		</code>

-	For a typical project (which won't be using strict_types), expect thousands of changes to be made; and note how this does not improve code quality.	+	For a typical project (which won't be using //strict_types=1//), expect thousands of changes to be made; and note how this does not improve code quality.

	==== Temporary Solutions ====		==== Temporary Solutions ====
Line 345:		Line 343:
	==== Updating ====		==== Updating ====

-	While making each change is fairly easy - they are difficult to find, there are many of them (time consuming), and the updates used are often pointless, e.g.	+	While making each change is fairly easy - they are still difficult to find, there are many of them, and the updates used are often pointless, e.g.

	* //urlencode(strval($name));//		* //urlencode(strval($name));//
Line 351:		Line 349:
	* //urlencode($name ?? "");//		* //urlencode($name ?? "");//

-	One example diff didn't exactly make the code easier to read:	+	And often do not make the code easier to read:

	<code diff>		<code diff>
Line 358:		Line 356:
	</code>		</code>

-	As noted above - Rector can add //(string)// type casting automatically, but I have no idea how this improves code quality.	+	As noted above - Rector can add //(string)// type casting automatically, but this does not improve code quality.

	===== Proposal =====		===== Proposal =====

-	Revert the NULL deprecation for parameters (when not using //strict_types=1//), so it continues to work (as NULL coercion does in other contexts), to avoid the upgrade problems (i.e. Fatal Errors in PHP 9.0).	+	Revert the NULL deprecation for parameters (when not using //strict_types=1//), so NULL coercion continues to work (as it does in other contexts) to avoid the upgrade problems (i.e. Fatal Errors in PHP 9.0).

	And, in the spirit of the original RFC to keep user-defined and internal functions consistent, also change user-defined functions so NULL is coerced for non-nullable parameters (when not using //strict_types=1//).		And, in the spirit of the original RFC to keep user-defined and internal functions consistent, also change user-defined functions so NULL is coerced for non-nullable parameters (when not using //strict_types=1//).

-	This means the type "//?int//" will allow NULL or an integer to be provided to the function; whereas the non-nullable type "//int//" would coerce NULL to 0, in the same way the string "0" would be.	+	This means the type "//?int//" will allow NULL or an integer to be provided to the function; whereas the non-nullable type "//int//" would coerce NULL to 0; in exactly the same way the string "0" or the boolean false would be.

	===== Backward Incompatible Changes =====		===== Backward Incompatible Changes =====

-	While the intention of this RFC is to avoid a BC break; for user defined functions to be updated to also coerce NULL (instead of throwing a Type Error), it's possible some code may rely on that behaviour, for example:	+	While the intention of this RFC is to avoid a BC break; for user defined functions to be updated to also coerce NULL (instead of throwing a Type Error), while unlikely, it is possible some non //strict_types// code may rely the TypeError being thrown, for example:

	<code php>		<code php>

removal-of-deprecated-features

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2011/04/06 10:59		current
Line 3:		Line 3:
	* Date: 07/04 - 2010		* Date: 07/04 - 2010
	* Author: Kalle Sommer Nielsen <kalle@php.net>		* Author: Kalle Sommer Nielsen <kalle@php.net>
-	* Status: Under Discussion	+	* Status: Implemented in PHP 5.4

remove_utf8_decode_and_utf8_encode

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2022/04/19 21:44		current
Line 3:		Line 3:
	* Date: 2022-04-04		* Date: 2022-04-04
	* Author: Rowan Tommins <rowan.collins@gmail.com>		* Author: Rowan Tommins <rowan.collins@gmail.com>
-	* Status: Accepted (Pending Implementation)	+	* Status: [[https://github.com/php/php-src/pull/8726\|Implemented]] (PHP 8.2.0)
	* First Published at: https://wiki.php.net/rfc/remove_utf8_decode_and_utf8_encode		* First Published at: https://wiki.php.net/rfc/remove_utf8_decode_and_utf8_encode

switch-case-fallthrough

Anonymous (anonymous@undisclosed.example.com) — 2026-04-21T14:15:02+00:00

2026/04/21 14:13		current
Line 75:		Line 75:
	switch ($token) {		switch ($token) {
	case T_STRING:		case T_STRING:
-	$result[] = normalize($value);	+	$value = normalize($value);
	fallthrough;		fallthrough;
	case T_NAME_QUALIFIED:		case T_NAME_QUALIFIED:

url_parsing_api

Anonymous (anonymous@undisclosed.example.com) — 2026-03-17T13:22:17+00:00

2025/11/12 02:11		current
Line 208:		Line 208:
	public function withFragment(?string $fragment): static {}		public function withFragment(?string $fragment): static {}

-	public function equals(Uri $uri, \Uri\ComparisonMode $comparisonMode = \Uri\ComparisonMode::ExcludeFragment): bool {}	+	public function equals(Uri $uri, \Uri\UriComparisonMode $comparisonMode = \Uri\UriComparisonMode::ExcludeFragment): bool {}

	public function toString(): string {}		public function toString(): string {}
Line 305:		Line 305:
	public function withFragment(?string $fragment): static {}		public function withFragment(?string $fragment): static {}

-	public function equals(Url $url, \Uri\ComparisonMode $comparisonMode = \Uri\ComparisonMode::ExcludeFragment): bool {}	+	public function equals(Url $url, \Uri\UriComparisonMode $comparisonMode = \Uri\UriComparisonMode::ExcludeFragment): bool {}

	public function toAsciiString(): string {}		public function toAsciiString(): string {}

php53

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2011/04/06 10:59		current
Line 151:		Line 151:
	==== After the first stable release ====		==== After the first stable release ====

-	- add firebird/interbase to windows builds	+	- <del>add firebird/interbase to windows builds</del>
	- make all extensions use php implementation of getenv (Pierre)		- make all extensions use php implementation of getenv (Pierre)
	- Improve the build script to ease the parsing of the output and QA		- Improve the build script to ease the parsing of the output and QA

calltimebyref

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2011/04/06 10:59		current
Line 3:		Line 3:
	* Date: 2008-05-21		* Date: 2008-05-21
	* Author: Steph Fox <sfox@php.net>		* Author: Steph Fox <sfox@php.net>
-	* Status: Under Discussion	+	* Status: Implemented
	* First Published at: http://wiki.php.net/rfc/calltimebyref		* First Published at: http://wiki.php.net/rfc/calltimebyref

Line 51:		Line 51:
	- [3] [[http://cvs.php.net/viewvc.cgi/php-src/main/main.c?r1=1.676&r2=1.677]]		- [3] [[http://cvs.php.net/viewvc.cgi/php-src/main/main.c?r1=1.676&r2=1.677]]

-		+	==== Comments ====
		+	currently allow_call_time_pass_reference is set to Off in both php.ini-production and php.ini-development for 5.3, and Call-time pass-by-reference was removed from 5.4, so this RFC is implemented/obsolete.

case_insensitive_constant_deprecation

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2018/07/16 16:56		current
Line 2:		Line 2:
	* Date: 2018-06-24		* Date: 2018-06-24
	* Author: Nikita Popov <nikic@php.net>		* Author: Nikita Popov <nikic@php.net>
-	* Target PHP version: PHP 7.3
	* Implementation: https://github.com/php/php-src/pull/3321		* Implementation: https://github.com/php/php-src/pull/3321
	* Discussion: https://externals.io/message/102389		* Discussion: https://externals.io/message/102389
-	* Status: Accepted	+	* Status: Implemented (in PHP 7.3)

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

deprecate_dollar_brace_string_interpolation

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2022/04/22 12:30		current
Line 3:		Line 3:
	* Date: 2021-03-13		* Date: 2021-03-13
	* Author: Ilija Tovilo, tovilo.ilija@gmail.com		* Author: Ilija Tovilo, tovilo.ilija@gmail.com
-	* Status: Accepted	+	* Status: Implemented
	* Target Version: PHP 8.2		* Target Version: PHP 8.2
	* Implementation: https://github.com/php/php-src/pull/8212		* Implementation: https://github.com/php/php-src/pull/8212

deprecate_dynamic_properties

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2021/11/26 09:03		current
Line 2:		Line 2:
	* Date: 2021-08-23		* Date: 2021-08-23
	* Author: Nikita Popov <nikic@php.net>		* Author: Nikita Popov <nikic@php.net>
-	* Status: Accepted	+	* Status: Implemented
	* Target Version: PHP 8.2		* Target Version: PHP 8.2
	* Implementation: https://github.com/php/php-src/pull/7571		* Implementation: https://github.com/php/php-src/pull/7571

deprecate_ini_set_get_aliases

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2015/01/31 07:46		current
Line 173:		Line 173:
	===== Future Scope =====		===== Future Scope =====

-	None. If proposal 3 (Add E_DEPRECATE error) is rejected, adding E_DEPRECATE error will be future decision.	+	* If proposal 3 (Add E_DEPRECATE error) is rejected, adding E_DEPRECATE error will be future decision.
		+	* All INI values in the manual should be able to be easily searchable.

	===== Proposed Voting Choices =====		===== Proposed Voting Choices =====

deprecate-get-post-sessions

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2024/04/23 17:01		current
Line 4:		Line 4:
	* Date: 2024-03-03		* Date: 2024-03-03
	* Authors: Kamil Tekiela <dharman@php.net>		* Authors: Kamil Tekiela <dharman@php.net>
-	* Status: Accepted	+	* Status: Implemented
	* Target Version: PHP 8.4		* Target Version: PHP 8.4
	* Implementation: https://github.com/php/php-src/pull/13578		* Implementation: https://github.com/php/php-src/pull/13578
Line 81:		Line 81:
	</doodle>		</doodle>

		+	===== Implementation =====

		+	- merged into ''master'' (will become PHP-8.4)
		+	- merged as [[https://github.com/php/php-src/commit/c5bce0d8a2e6794cd6809e4047dd1f488fa3459b]]
		+	- documentation update pending

deprecate-ini-functions

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2017/09/22 13:28		current
Line 5:		Line 5:
	* Modified Date: 2014-03-13		* Modified Date: 2014-03-13
	* Author: Yasuo Ohgaki <yohgaki@ohgaki.net>		* Author: Yasuo Ohgaki <yohgaki@ohgaki.net>
-	* Status: Draft	+	* Status: Withdrawn
	* First Published at: http://wiki.php.net/rfc/deprecate-ini-functions		* First Published at: http://wiki.php.net/rfc/deprecate-ini-functions

deprecate-metaphone

Anonymous (anonymous@undisclosed.example.com) — 2026-05-08T08:27:56+00:00

2026/04/27 14:41		current
Line 3:		Line 3:
	* Date: 2026-04-25		* Date: 2026-04-25
	* Author: Weilin Du, lamentxu@163.com		* Author: Weilin Du, lamentxu@163.com
-	* Status: Under Discussion	+	* Status: Withdrawn
	* Implementation: https://github.com/php/php-src/pull/21889		* Implementation: https://github.com/php/php-src/pull/21889

deprecate-return-value-from-construct

Anonymous (anonymous@undisclosed.example.com) — 2026-05-08T10:34:40+00:00

2026/05/08 08:44		current
Line 115:		Line 115:
	* Mailing List Discussion of making <php>new</php> emit an error if a value is returned: https://news-web.php.net/php.internals/129980		* Mailing List Discussion of making <php>new</php> emit an error if a value is returned: https://news-web.php.net/php.internals/129980
	* An earlier, similar, RFC: [[make_ctor_ret_void\|PHP RFC: Make constructors and destructors return void]]		* An earlier, similar, RFC: [[make_ctor_ret_void\|PHP RFC: Make constructors and destructors return void]]
		+	* Discussion of this RFC: https://news-web.php.net/php.internals/130808

	===== Rejected Features =====		===== Rejected Features =====

deprecations_php_7_3

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2018/07/16 16:59		current
Line 2:		Line 2:
	* Date: 2017-08-02		* Date: 2017-08-02
	* Author: Nikita Popov <nikic@php.net>		* Author: Nikita Popov <nikic@php.net>
-	* Status: Accepted	+	* Status: Implemented (in PHP 7.3)
	* Implementation: https://github.com/php/php-src/pull/3366 (unless other patch linked below)		* Implementation: https://github.com/php/php-src/pull/3366 (unless other patch linked below)
	* Discussion: https://externals.io/message/102394		* Discussion: https://externals.io/message/102394

error_handler_callback_parameters_passed_by_reference

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2015/02/27 23:16		current
Line 1:		Line 1:
	====== PHP RFC: Allow error_handler callback parameters to be passed by reference ======		====== PHP RFC: Allow error_handler callback parameters to be passed by reference ======
	* Version: 0.2		* Version: 0.2
-	* Date: 2015-02-13 (voting)	+	* Date: 2015-02-28
	* Authors: Reeze Xia <reeze@php.net>, Thomas Bley <mails@thomasbley.de>		* Authors: Reeze Xia <reeze@php.net>, Thomas Bley <mails@thomasbley.de>
-	* Status: Voting	+	* Status: Declined
	* First Published at: http://wiki.php.net/rfc/error_handler_callback_parameters_passed_by_reference		* First Published at: http://wiki.php.net/rfc/error_handler_callback_parameters_passed_by_reference

minor-version-compatibility

Anonymous (anonymous@undisclosed.example.com) — 2025-08-31T15:24:41+00:00

2025/04/27 21:30		current
Line 98:		Line 98:
	* Yes		* Yes
	* No		* No
		+	* Abstain
	</doodle>		</doodle>

Line 113:		Line 114:
	* Yes		* Yes
	* No		* No
		+	* Abstain
	</doodle>		</doodle>

Line 129:		Line 131:
	* E_DEPRECATED		* E_DEPRECATED
	* E_WARNING		* E_WARNING
		+	* Abstain
	</doodle>		</doodle>

proper-range-semantics

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2023/06/15 14:47		current
Line 4:		Line 4:
	* Date: 2023-03-13		* Date: 2023-03-13
	* Author: George Peter Banyard, <girgias@php.net>		* Author: George Peter Banyard, <girgias@php.net>
-	* Status: Pending Implementation	+	* Status: Implemented (https://github.com/php/php-src/commit/798c40a739e8f1081a516679a367d76c3d0aabb9)
	* Target Version: PHP 8.3		* Target Version: PHP 8.3
	* Implementation: [[https://github.com/php/php-src/pull/10826]]		* Implementation: [[https://github.com/php/php-src/pull/10826]]
Line 566:		Line 566:
	GitHub pull request: https://github.com/php/php-src/pull/10826		GitHub pull request: https://github.com/php/php-src/pull/10826

-	After the project is implemented, this section should contain	+	Implemented in PHP 8.3, as commit: https://github.com/php/php-src/commit/798c40a739e8f1081a516679a367d76c3d0aabb9
-		+
-	* the version(s) it was merged into	+
-	* a link to the git commit(s)	+
-	* a link to the PHP manual entry for the feature	+

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

consistent_callables

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2019/04/28 03:08		current
Line 3:		Line 3:
	* Date: 2019-04-28		* Date: 2019-04-28
	* Author: Dan Ackroyd		* Author: Dan Ackroyd
-	* Status: Under Discussion	+	* Status: Withdrawn
	* First Published at: https://wiki.php.net/rfc/consistent_callables		* First Published at: https://wiki.php.net/rfc/consistent_callables

core-autoloading

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2023/04/23 14:24		current
Line 3:		Line 3:
	* Version: 0.1		* Version: 0.1
	* Date: 2023-04-03		* Date: 2023-04-03
-	* Author: George Peter Banyard, <girgias@php.net>, Dan Ackroyd, <danack@basereality.com>	+	* Author: Gina P Banyard, <girgias@php.net>, Dan Ackroyd, <danack@basereality.com>
	* Status: Under Discussion		* Status: Under Discussion
	* Target Version: PHP 8.3		* Target Version: PHP 8.3

dedicated_stream_bucket

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2024/04/11 13:01		current
Line 2:		Line 2:
	* Date: 2024-01-19		* Date: 2024-01-19
	* Author: Máté Kocsis <kocsismate@php.net>		* Author: Máté Kocsis <kocsismate@php.net>
-	* Status: Accepted	+	* Status: Implemented
	* Target: next minor version (possibly PHP 8.4)		* Target: next minor version (possibly PHP 8.4)
	* Implementation: https://github.com/php/php-src/pull/13111		* Implementation: https://github.com/php/php-src/pull/13111

deprecate-boolean-string-coercion

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2021/06/25 13:05		current
Line 26:		Line 26:
	is common:		is common:

-	- <php>ini_set()</php>	+	* <php>ini_set()</php>

	===== Rationale =====		===== Rationale =====

deprecations_php_7_2

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2017/06/12 18:18		current
Line 2:		Line 2:
	* Date: 2015-12-28		* Date: 2015-12-28
	* Author: Nikita Popov <nikic@php.net>		* Author: Nikita Popov <nikic@php.net>
-	* Status: Accepted	+	* Status: Implemented (in PHP 7.2)
	* Discussion: http://markmail.org/message/gto22ob4scfbk7ql		* Discussion: http://markmail.org/message/gto22ob4scfbk7ql
	* Originally published under: https://wiki.php.net/rfc/deprecations_php_7_1		* Originally published under: https://wiki.php.net/rfc/deprecations_php_7_1
Line 162:		Line 162:

	Proposed action: Throw deprecation notice if error handler has five or more arguments. Otherwise, do not pass the ''$errcontext''. This prevents circumvention with ''func_get_args()''.		Proposed action: Throw deprecation notice if error handler has five or more arguments. Otherwise, do not pass the ''$errcontext''. This prevents circumvention with ''func_get_args()''.
		+
		+	Update: Due to technical issues, this does not throw a deprecation warning. It is a documentation-only deprecation.

	<doodle title="Deprecate and subsequently remove $errcontext argument of error handler" auth="nikic" voteType="single" closed="true">		<doodle title="Deprecate and subsequently remove $errcontext argument of error handler" auth="nikic" voteType="single" closed="true">

forbid_null_this_in_methods

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2016/04/29 19:23		current
Line 3:		Line 3:
	* Date: 2016-04-29		* Date: 2016-04-29
	* Author: Nikita Popov <nikic@php.net>		* Author: Nikita Popov <nikic@php.net>
-	* Status: Draft	+	* Status: Withdrawn
	* Target version: PHP 7.1		* Target version: PHP 7.1
	* Patch: https://github.com/php/php-src/pull/1894		* Patch: https://github.com/php/php-src/pull/1894

imagettf_deprecation

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2014/07/27 01:16		current
Line 3:		Line 3:
	* Date: 2014-07-26		* Date: 2014-07-26
	* Author: Lonny Kapelushnik, lonny@lonnylot.com		* Author: Lonny Kapelushnik, lonny@lonnylot.com
-	* Status: Draft	+	* Status: Under Discussion
	* First Published at: http://wiki.php.net/rfc/imagettf_deprecation		* First Published at: http://wiki.php.net/rfc/imagettf_deprecation

implicit-float-int-deprecate

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2021/05/31 14:26		current
Line 3:		Line 3:
	* Date: 2021-02-03		* Date: 2021-02-03
	* Author: George Peter Banyard, <girgias@php.net>		* Author: George Peter Banyard, <girgias@php.net>
-	* Status: Accepted https://externals.io/message/113371	+	* Status: Implemented (https://github.com/php/php-src/commit/b6958bb8476306c2f6ce110782330c41e6a5df3a)
		+	* Discussion: https://externals.io/message/113371
	* First Published at: http://wiki.php.net/rfc/implicit-float-int-deprecate		* First Published at: http://wiki.php.net/rfc/implicit-float-int-deprecate
	* GitHub mirror: https://github.com/Girgias/float-int-warning		* GitHub mirror: https://github.com/Girgias/float-int-warning
Line 115:		Line 116:

	===== Implementation =====		===== Implementation =====
-	After the project is implemented, this section should contain	+	Implemented in https://github.com/php/php-src/commit/b6958bb8476306c2f6ce110782330c41e6a5df3a
-	- the version(s) it was merged into	+
-	- a link to the git commit(s)	+
-	- a link to the PHP manual entry for the feature	+
-	- a link to the language specification section (if any)	+
	===== References =====		===== References =====

	Initial mailing list discussion: <https://externals.io/message/113077> \\		Initial mailing list discussion: <https://externals.io/message/113077> \\
	Revised mailing list discussion: <https://externals.io/message/113371> \\		Revised mailing list discussion: <https://externals.io/message/113371> \\

improve_mysqli

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2020/12/30 18:26		current
Line 63:		Line 63:
	=== "new mysqli()" doesn't open a connection with 0 arguments ===		=== "new mysqli()" doesn't open a connection with 0 arguments ===

-	At the moment PHP manual claims that all 6 parameters of ''%%mysqli::__construct()%%'' are optional with default values taken from INI settings. As you might have guessed that is not entirely true. The default values are in fact honoured, but at least 1 argument must be provided, even if that 1 argument is ''NULL''. If absolutely no arguments are passed, then ''%%mysqli::__construct()%%'' behaves as ''mysqli_init()''. What are the workarounds if I want to store all my configuration details in INI?	+	At the moment PHP manual claims that all 6 parameters of ''%%mysqli::__construct()%%'' are optional with default values taken from INI settings. As you might have guessed that is not entirely true. The default values are in fact honoured, but at least 1 argument must be provided, even if that 1 argument is ''NULL''. If absolutely no arguments are passed, then ''%%mysqli::__construct()%%'' behaves as ''mysqli_init()''. Here are the workarounds if you want to store all the configuration details in INI:

	<code php>		<code php>

magicquotes_finale

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2011/08/06 00:03		current
Line 3:		Line 3:
	* Date: 2011-07-18		* Date: 2011-07-18
	* Author: Daniel Convissor <danielc@php.net>		* Author: Daniel Convissor <danielc@php.net>
-	* Status: Declined	+	* Status: Withdrawn
	* First Published at: https://wiki.php.net/rfc/magicquotes_finale		* First Published at: https://wiki.php.net/rfc/magicquotes_finale
	* Extends: https://wiki.php.net/rfc/magicquotes		* Extends: https://wiki.php.net/rfc/magicquotes

negative_array_index

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2018/03/16 17:45		current
Line 3:		Line 3:
	* Date: 2017-04-20		* Date: 2017-04-20
	* Author: Pedro Magalhães, pmmaga@php.net		* Author: Pedro Magalhães, pmmaga@php.net
-	* Status: Accepted	+	* Status: Implemented
	* First Published at: http://wiki.php.net/rfc/negative_array_index		* First Published at: http://wiki.php.net/rfc/negative_array_index

random_migration

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2022/12/21 16:21		current
Line 25:		Line 25:
	All of these functions have global scope issues described in the Random Extension RFC.		All of these functions have global scope issues described in the Random Extension RFC.

-	The rand() and mt_srand() functions can be used without performing explicit seeding, but the seed value used in this case is not reproducible because it uses random_int() internally. In most cases, it is better to use random_int() directly. Also, srand() and mt_srand() are undesirable from a security standpoint because they use a low-quality linear congruence method to generate the seed value as a fallback if a secure seed value cannot be generated.	+	The rand() and mt_srand() functions can be used without performing explicit seeding, but the seed value used in this case is not reproducible because it uses random_int() internally. 1 In most cases, it is better to use random_int() directly. Also, srand() and mt_srand() are undesirable from a security standpoint because they use a low-quality linear congruence method to generate the seed value as a fallback 2 if a secure seed value cannot be generated.

	If reproducibility is required, we should use \Random\Randomizer, which does not have the global scope issue.		If reproducibility is required, we should use \Random\Randomizer, which does not have the global scope issue.
		+
		+	- https://github.com/php/php-src/blob/7f0b228f48ad29c13a84dc8c8bc050f34d3a855a/ext/random/engine_mt19937.c#L240
		+	- https://github.com/php/php-src/blob/f9a1a903805a0c260c97bcc8bf2c14f2dd76ca76/ext/random/php_random.h#L67

	=== lcg_value() function ===		=== lcg_value() function ===

reclassify_e_strict

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2015/03/25 16:11		current
Line 2:		Line 2:
	* Date: 2015-02-22		* Date: 2015-02-22
	* Author: Nikita Popov <nikic@php.net>		* Author: Nikita Popov <nikic@php.net>
-	* Status: Accepted	+	* Status: Implemented (in PHP 7.0)

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

removal_of_dead_sapis_and_exts

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2015/04/06 21:18		current
Line 393:		Line 393:

	The voting options are attached to the corresponding items. The voting starts on 2015-02-02 and ends on 2015-02-09 at 23:00 CET respectively. To be accepted/declined each vote requires 50%+1 acceptance.		The voting options are attached to the corresponding items. The voting starts on 2015-02-02 and ends on 2015-02-09 at 23:00 CET respectively. To be accepted/declined each vote requires 50%+1 acceptance.
		+
		+	===== Implementation =====
		+
		+	Implemented in PHP7, see PRE_NATIVE_TLS_MERGE and POST_NATIVE_TLS_MERGE tags.
		+
		+

ternary_associativity

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2019/05/07 08:33		current
Line 2:		Line 2:
	* Date: 2019-04-09		* Date: 2019-04-09
	* Author: Nikita Popov <nikic@php.net>		* Author: Nikita Popov <nikic@php.net>
-	* Status: Accepted	+	* Status: Implemented
	* Target Version: PHP 7.4 and PHP 8.0		* Target Version: PHP 7.4 and PHP 8.0
	* Implementation: https://github.com/php/php-src/pull/4017		* Implementation: https://github.com/php/php-src/pull/4017

var_deprecation

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2016/03/24 12:27		current
Line 2:		Line 2:
	* Date: 2016-03-10		* Date: 2016-03-10
	* Author: Colin O'Dell <colinodell@php.net>		* Author: Colin O'Dell <colinodell@php.net>
-	* Status: In Voting	+	* Status: Declined
	* Discussion: http://markmail.org/message/523vpfo2q5dwqyed		* Discussion: http://markmail.org/message/523vpfo2q5dwqyed

Line 138:		Line 138:
	Voting started on 2016-03-24 and will end on 2016-03-31 at 12:30 UTC.		Voting started on 2016-03-24 and will end on 2016-03-31 at 12:30 UTC.

-	<doodle title="Deprecate `var` in 7.1 and remove it from 8.0?" auth="colinodell" voteType="single" closed="false">	+	<doodle title="Deprecate `var` in 7.1 and remove it from 8.0?" auth="colinodell" voteType="single" closed="true">
	* Yes		* Yes
	* No		* No

mysqlnd_vs_libmysql

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2011/09/08 14:41		current
Line 28:		Line 28:


		+	Please make sure that you are using a PHP build with Zlib and OpenSSL support when switching from libmysql to mysqlnd. This will ensure that mysqlnd offers the same functionality as libmysql does.
	==== Major feature differences ====		==== Major feature differences ====

objects

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2011/06/23 13:01		current
Line 80:		Line 80:
	* Called when an object is to be cloned (associated with usage of the ''clone'' operator in user space).		* Called when an object is to be cloned (associated with usage of the ''clone'' operator in user space).
	* Should return a ''zend_object_value'' that refers to a newly created object that is equal to the object referred to the passed reference. The two objects should not be identical, i.e., ''=='' applied to the references should return ''true'' but ''==='' should return ''false''. The ''[[#compare_objects\|compare_objects]]'' handlers must be the same since that is a requisite for ''=='' returning ''true'', but typically, as one would want the two objects to have identical behavior, they ought to share all the handlers.		* Should return a ''zend_object_value'' that refers to a newly created object that is equal to the object referred to the passed reference. The two objects should not be identical, i.e., ''=='' applied to the references should return ''true'' but ''==='' should return ''false''. The ''[[#compare_objects\|compare_objects]]'' handlers must be the same since that is a requisite for ''=='' returning ''true'', but typically, as one would want the two objects to have identical behavior, they ought to share all the handlers.
-	* Zend standard object extensions can call ''zend_objects_clone_members'' to copy properties; this functions also calls the class entry ''clone'' function (typically ''%%__clone%%'').	+	* Zend standard object extensions can call ''zend_objects_clone_members'' to copy properties; this function also calls the class entry ''clone'' function (typically ''%%__clone%%'').
	* The created object should be initialized as if it had one reference.		* The created object should be initialized as if it had one reference.
	* May be ''NULL'' to forbid cloning.		* May be ''NULL'' to forbid cloning.

add_values_method_to_backed_enum

Anonymous (anonymous@undisclosed.example.com) — 2026-01-19T04:56:47+00:00

2026/01/18 12:09		current
Line 169:		Line 169:
	This is a Yes/No vote, requiring a 2/3 majority.		This is a Yes/No vote, requiring a 2/3 majority.

-	Voting started on Jan 18, 2026 and ends on Feb 08, 2026	+	Voting will start later
-		+
-	<doodle title="Add BackedEnum::values()?" voteType="single" closed="false" closeon="2026-02-08T00:00:00Z">	+
-	* Yes	+
-	* No	+
-	* Abstain	+
-	</doodle>	+

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

adopt_pie_deprecate_pecl

Anonymous (anonymous@undisclosed.example.com) — 2025-09-22T06:17:34+00:00

2025/09/07 12:09		current
Line 3:		Line 3:
	* Date: 2025-08-20		* Date: 2025-08-20
	* Author: James Titcumb, asgrim@php.net		* Author: James Titcumb, asgrim@php.net
-	* Status: Voting	+	* Status: Accepted

	===== Introduction =====		===== Introduction =====
Line 32:		Line 32:
	Yes / No vote requiring 2/3 Yes votes to pass. Voting ends 2025-09-20T09:00:00Z.		Yes / No vote requiring 2/3 Yes votes to pass. Voting ends 2025-09-20T09:00:00Z.

-	<doodle title="Deprecate PECL and adopt PIE instead?" voteType="single" closed="false" closeon="2025-09-20T09:00:00Z">	+	<doodle title="Deprecate PECL and adopt PIE instead?" voteType="single" closed="true" closeon="2025-09-20T09:00:00Z">
	* Yes		* Yes
	* No		* No

allow_null

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2022/02/20 20:19		current
Line 11:		Line 11:
	* GitHub Repo: https://github.com/craigfrancis/php-allow-null-rfc		* GitHub Repo: https://github.com/craigfrancis/php-allow-null-rfc
	* Implementation: ?		* Implementation: ?
		+
		+	----
		+
		+	This RFC has been superseded by [[https://wiki.php.net/rfc/null_coercion_consistency\|NULL Coercion Consistency]]
		+
		+	----

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

array-to-string

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2017/09/22 13:28		current
Line 100:		Line 100:
	Basic Yes/No : Yes to replace E_NOTICE with E_RECOVERABLE_ERROR, No for no change.		Basic Yes/No : Yes to replace E_NOTICE with E_RECOVERABLE_ERROR, No for no change.

-	<doodle title="array-to-string" auth="francois" voteType="single" closed="false">	+	<doodle title="array-to-string" auth="francois" voteType="single" closed="true">
	* Yes		* Yes
	* No		* No

autovivification_false

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2021/06/23 21:11		current
Line 2:		Line 2:
	* Date: 2021-05-25		* Date: 2021-05-25
	* Author: Kamil Tekiela <dharman@php.net>		* Author: Kamil Tekiela <dharman@php.net>
-	* Status: Accepted	+	* Status: Implemented in PHP 8.1
-	* Draft implementation: https://github.com/php/php-src/pull/7131	+	* Implementation: https://github.com/php/php-src/pull/7131
-	* Target Version: PHP 8.1	+

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

base_convert_improvements

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2020/04/12 20:13		current
Line 3:		Line 3:
	* Date: 2019-05-15		* Date: 2019-05-15
	* Author: Scott Dutton,php@exussum.co.uk		* Author: Scott Dutton,php@exussum.co.uk
-	* Status: Accepted	+	* Status: Implemented (in PHP 7.4)
	* First Published at: https://wiki.php.net/rfc/base_convert_improvements		* First Published at: https://wiki.php.net/rfc/base_convert_improvements

clear-process

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2019/04/25 09:41		current
Line 32:		Line 32:
	Should the focus of an RFC be on removal, and should that RFC be accepted, deprecation shall be carried out as described above.		Should the focus of an RFC be on removal, and should that RFC be accepted, deprecation shall be carried out as described above.

-	===== Voting =====	+	==== Voting ====

	Should this RFC be accepted, a new section in the voting RFC shall be created containing the information agreed upon here.		Should this RFC be accepted, a new section in the voting RFC shall be created containing the information agreed upon here.

-	===== External References =====	+	==== External References ====

	http://externals.io/somewhere		http://externals.io/somewhere

clone_with_v2

Anonymous (anonymous@undisclosed.example.com) — 2025-07-17T19:15:42+00:00

2025/06/30 10:34		current
Line 3:		Line 3:
	* Date: 2025-03-30		* Date: 2025-03-30
	* Author: Volker Dusch (volker@tideways-gmbh.com), Tim Düsterhus (tim@tideways-gmbh.com)		* Author: Volker Dusch (volker@tideways-gmbh.com), Tim Düsterhus (tim@tideways-gmbh.com)
-	* Status: Accepted	+	* Status: Implemented
		+	* Target Version: PHP 8.5
		+	* Implementation: https://github.com/php/php-src/commit/ca49a7bec2a0a8d77bfa4b6d375ca0ffa4edc5ee, https://github.com/php/php-src/commit/c9249e2d3aa401bda5d9a3071e86e0594807ed00, https://github.com/php/php-src/commit/7f4076bae0cf91c5a24f4f908525e739e6bca8fb
	* First Published at: https://wiki.php.net/rfc/clone_with_v2		* First Published at: https://wiki.php.net/rfc/clone_with_v2

Line 477:		Line 479:
	* https://github.com/php/php-src/commit/ca49a7bec2a0a8d77bfa4b6d375ca0ffa4edc5ee		* https://github.com/php/php-src/commit/ca49a7bec2a0a8d77bfa4b6d375ca0ffa4edc5ee
	* https://github.com/php/php-src/commit/c9249e2d3aa401bda5d9a3071e86e0594807ed00		* https://github.com/php/php-src/commit/c9249e2d3aa401bda5d9a3071e86e0594807ed00
		+	* https://github.com/php/php-src/commit/7f4076bae0cf91c5a24f4f908525e739e6bca8fb

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

correctly_name_the_rounding_mode_and_make_it_an_enum

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2024/07/18 06:40		current
Line 3:		Line 3:
	* Date: 2024-04-21		* Date: 2024-04-21
	* Author: Saki Takamachi (saki@php.net), Tim Düsterhus (timwolla@php.net)		* Author: Saki Takamachi (saki@php.net), Tim Düsterhus (timwolla@php.net)
-	* Status: Accepted	+	* Status: Implemented
		+	* Target Version: PHP 8.4
		+	* Implementation: https://github.com/php/php-src/commit/5905857fd2652585989ed03e5a5b0beea89ab18e
	* First Published at: https://wiki.php.net/rfc/correctly_name_the_rounding_mode_and_make_it_an_Enum		* First Published at: https://wiki.php.net/rfc/correctly_name_the_rounding_mode_and_make_it_an_Enum

Line 264:		Line 266:

	===== Implementation =====		===== Implementation =====
-	Yet.	+
		+	* https://github.com/php/php-src/commit/5905857fd2652585989ed03e5a5b0beea89ab18e

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

create-split-alias-to-explode

Anonymous (anonymous@undisclosed.example.com) — 2025-09-22T15:44:26+00:00

2025/09/04 13:54		current
Line 3:		Line 3:
	* Date: 2025-08-17		* Date: 2025-08-17
	* Author: Vinicius Dias, carlosv775@gmail.com		* Author: Vinicius Dias, carlosv775@gmail.com
-	* Status: Voting	+	* Status: Declined
	* Implementation: https://github.com/php/php-src/pull/19490		* Implementation: https://github.com/php/php-src/pull/19490

Line 160:		Line 160:
	===== Voting Choices =====		===== Voting Choices =====

-	<doodle title="Create a new split alias for the explode function?" voteType="single" closed="false" closeon="2025-09-19T00:00:00Z">	+	<doodle title="Create a new split alias for the explode function?" voteType="single" closed="true" closeon="2025-09-19T00:00:00Z">
	* Yes		* Yes
	* No		* No

deprecate_mb_ereg_replace_eval_option

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2016/07/09 14:25		current
Line 3:		Line 3:
	* Date: 2016-01-04		* Date: 2016-01-04
	* Author: Rouven Weßling, me@rouvenwessling.de		* Author: Rouven Weßling, me@rouvenwessling.de
-	* Status: Accepted	+	* Status: Implemented (PHP 7.1)
	* First Published at: https://wiki.php.net/rfc/deprecate_mb_ereg_replace_eval_option		* First Published at: https://wiki.php.net/rfc/deprecate_mb_ereg_replace_eval_option

Line 49:		Line 49:
	===== Patches and Tests =====		===== Patches and Tests =====

-	A patch is available: <https://github.com/php/php-src/pull/1994>.	+	A patch is available: <https://github.com/php/php-src/pull/1994> (merged).

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

	[[rfc:remove_preg_replace_eval_modifier\| RFC: Remove preg_replace /e modifier]]		[[rfc:remove_preg_replace_eval_modifier\| RFC: Remove preg_replace /e modifier]]

deprecate_null_to_scalar_internal_arg

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2021/02/17 11:53		current
Line 82:		Line 82:
	===== Vote =====		===== Vote =====

-	Voting started 2020-01-26 and ended on 2020-02-09.	+	Voting started 2021-01-26 and ended on 2021-02-09.

	<doodle title="Deprecate passing null to non-nullable arguments of internal functions?" auth="nikic" voteType="single" closed="true">		<doodle title="Deprecate passing null to non-nullable arguments of internal functions?" auth="nikic" voteType="single" closed="true">

deprecate_pear_recommend_composer

Anonymous (anonymous@undisclosed.example.com) — 2025-10-09T14:10:37+00:00

2025/10/09 10:28		current
Line 3:		Line 3:
	* Date: 2025-10-09		* Date: 2025-10-09
	* Author: James Titcumb, asgrim@php.net		* Author: James Titcumb, asgrim@php.net
-	* Status: Under Discussion	+	* Status: Withdrawn
	* Implementation: n/a		* Implementation: n/a

deprecate-and-remove-intl_idna_variant_2003

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2017/09/22 13:28		current
Line 49:		Line 49:
	- PR #2355 has been merged into master (which is supposed to become PHP-7.2) with [[https://github.com/php/php-src/commit/6cfbb7f9bd4576f8f6172a33d49e7498b3b617e1\|commit 6cfbb7f9]].		- PR #2355 has been merged into master (which is supposed to become PHP-7.2) with [[https://github.com/php/php-src/commit/6cfbb7f9bd4576f8f6172a33d49e7498b3b617e1\|commit 6cfbb7f9]].
	- The PHP manual has been [[http://svn.php.net/viewvc?view=revision&revision=341894\|updated]]. The migration guide will be written based on UPGRADING, which already has a respective note.		- The PHP manual has been [[http://svn.php.net/viewvc?view=revision&revision=341894\|updated]]. The migration guide will be written based on UPGRADING, which already has a respective note.
		+	- [[http://git.php.net/?p=php-src.git;a=commit;h=3d15a6f86b56c8acbf7363fb5e70a054918dbd64\|Removed for PHP 8]]

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

deprecate-backtick-operator-v2

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2019/10/31 17:46		current
Line 3:		Line 3:
	* Date: 2019-10-04		* Date: 2019-10-04
	* Author: Mark Randall, marandall@php.net		* Author: Mark Randall, marandall@php.net
-	* Status: Voting	+	* Status: Declined
	* First Published at:https://wiki.php.net/rfc/deprecate-backtick-operator-v2		* First Published at:https://wiki.php.net/rfc/deprecate-backtick-operator-v2
	* Target: 8.0		* Target: 8.0
Line 56:		Line 56:
	Voting started 2019-10-31 and will end 2019-11-15. A 2/3 majority is required.		Voting started 2019-10-31 and will end 2019-11-15. A 2/3 majority is required.

-	<doodle title="Deprecate backtick operator in PHP 8.0?" auth="marandall" voteType="single" closed="false">	+	<doodle title="Deprecate backtick operator in PHP 8.0?" auth="marandall" voteType="single" closed="true">
	* Yes		* Yes
	* No		* No

deprecate-inconsistent-cast-keywords

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2017/12/07 16:16		current
Line 3:		Line 3:
	* Date: 2017-12-07		* Date: 2017-12-07
	* Author: Chris Wright <daverandom@php.net>		* Author: Chris Wright <daverandom@php.net>
-	* Status: Draft	+	* Status: Inactive
	* First Published at: https://wiki.php.net/rfc/deprecate-inconsistent-cast-keywords		* First Published at: https://wiki.php.net/rfc/deprecate-inconsistent-cast-keywords

deprecate-json_encode-nonserializable

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2024/09/05 08:44		current
Line 1:		Line 1:
	====== PHP RFC: Deprecate json_encode() on classes marked as non-serializable ======		====== PHP RFC: Deprecate json_encode() on classes marked as non-serializable ======
-	* Version: 0.10	+	* Version: 0.11
	* Date: 2024-09-05		* Date: 2024-09-05
	* Author: Philip Hofstetter, phofstetter@sensational.ch		* Author: Philip Hofstetter, phofstetter@sensational.ch
Line 45:		Line 45:
	At the time of writing this RFC, the following list of classes (and their subclasses) are affected by this RFC and calling <php>json_encode()</php> on them will throw a deprecation warning in the future.		At the time of writing this RFC, the following list of classes (and their subclasses) are affected by this RFC and calling <php>json_encode()</php> on them will throw a deprecation warning in the future.

-	Most of them are currently json-encoded as ''%%{}%%'', no matter what they represent internally (some of these, like <php>PDOStatement</php> have public properties which are present in the output of <php>json_encode()</php>).	+	Some of those are containers of a sort, where this encoding is especially misleading (aside of <php>Generator</php> which was the motivator for this RFC, <php>WeakMap</php> stands out specifically).
		+
		+	Most of the non-serializable classes have no public properties and thus encode as ''%%{}%%''.
		+
		+	Those which currently do have public properties are still mostly meant for internal usage and thus not ideal candidates to <php>json_encode()</php> them. However, if code wants to explicitly turn any such instances into JSON in light of the deprecation currently proposed, casting such instances into <php>array</php> before JSON encoding them is a valid workaround.
		+
		+	<code php>
		+	$a = new SimpleXmlElement('<a><b>3</b><c>foo</c></a>');
		+	echo json_encode($a); // {"b":"3","c":"foo"}, with deprecation warning
		+	echo json_enode((array) $a); // {"b":"3","c":"foo"}, no deprecation warning
		+	</code>
		+
		+	=== Classes with public fields appearing in json_encode() output ===
		+	* CURLFile (has three public properties)
		+	* PDORow (has one public property, queryString)
		+	* PDOStatement (has one public property, queryString)
		+	* SimpleXMLElement (might be useful)
		+	* ReflectionAttribute
		+	* ReflectionClass
		+	* ReflectionClassConstant
		+	* ReflectionConstant
		+	* ReflectionExtension
		+	* ReflectionFiber
		+	* ReflectionFunctionAbstract
		+	* ReflectionGenerator
		+	* ReflectionParameter
		+	* ReflectionProperty
		+	* ReflectionReference
		+	* ReflectionType
		+	* ReflectionZendExtension

-	Some of those are containers of a sort, where this encoding is especially misleading (aside of <php>Generator</php> which was the motivator for this RFC, <php>WeakMap</php> stands out specifically)

	=== Backed by temporary resources ===		=== Backed by temporary resources ===
	* AddressInfo		* AddressInfo
-	* CURLFile
	* Collator		* Collator
	* CurlHandle		* CurlHandle
	* CurlMultiHandle		* CurlMultiHandle
	* CurlShareHandle		* CurlShareHandle
-	* DOMXPath
	* DOMXPath		* DOMXPath
	* Dba\Connection		* Dba\Connection
Line 64:		Line 90:
	* Dom\TokenList		* Dom\TokenList
	* Dom\XPath		* Dom\XPath
		+	* Dom\XMLDocument
	* EnchantBroker		* EnchantBroker
	* EnchantDictionary		* EnchantDictionary
Line 93:		Line 120:
	* OpenSSLCertificateSigningRequest		* OpenSSLCertificateSigningRequest
	* PDO		* PDO
-	* PDORow
-	* PDOStatement
	* Pdo\Dblib		* Pdo\Dblib
	* Pdo\Firebird		* Pdo\Firebird
Line 110:		Line 135:
	* SQLite3Stmt		* SQLite3Stmt
	* Shmop		* Shmop
-	* SimpleXMLElement
	* Soap\Sdl		* Soap\Sdl
	* Soap\Url		* Soap\Url
Line 130:		Line 154:
	* Generator		* Generator
	* InternalIterator		* InternalIterator
-	* ReflectionAttribute
-	* ReflectionClass
-	* ReflectionClassConstant
-	* ReflectionConstant
-	* ReflectionExtension
-	* ReflectionFiber
-	* ReflectionFunctionAbstract
-	* ReflectionGenerator
-	* ReflectionParameter
-	* ReflectionProperty
-	* ReflectionReference
-	* ReflectionType
-	* ReflectionZendExtension
	* SensitiveParameterValue		* SensitiveParameterValue
	* WeakMap		* WeakMap
	* WeakReference		* WeakReference
		+

	===== Backward Incompatible Changes =====		===== Backward Incompatible Changes =====

engine_exceptions

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2013/12/10 13:52		current
Line 2:		Line 2:
	* Date: 2013-10-23		* Date: 2013-10-23
	* Author: Nikita Popov <nikic@php.net>		* Author: Nikita Popov <nikic@php.net>
-	* Status: In Voting	+	* Status: Declined for 5.6
	* Proposed for: PHP 5.6		* Proposed for: PHP 5.6
	* Patch: https://github.com/nikic/php-src/compare/engineExceptions		* Patch: https://github.com/nikic/php-src/compare/engineExceptions
Line 349:		Line 349:
	If you are in favor of this proposal in general, but not for PHP 5.6, use the "No" voting option.		If you are in favor of this proposal in general, but not for PHP 5.6, use the "No" voting option.

-	<doodle title="Implement in PHP 5.6?" auth="nikic" voteType="single" closed="false">	+	<doodle title="Implement in PHP 5.6?" auth="nikic" voteType="single" closed="true">
	* Yes		* Yes
	* Yes, without E_RECOVERABLE_ERROR changes		* Yes, without E_RECOVERABLE_ERROR changes
Line 355:		Line 355:
	</doodle>		</doodle>

-	Vote started on 2013-12-07 and ends on 2013-12-14.	+	Vote started on 2013-12-07 and ended on 2013-12-14.

engine_exceptions_for_php7

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2015/03/08 18:17		current
Line 2:		Line 2:
	* Date: 2014-09-30		* Date: 2014-09-30
	* Author: Nikita Popov <nikic@php.net>		* Author: Nikita Popov <nikic@php.net>
-	* Status: Accepted (for PHP 7.0)	+	* Status: Implemented (in PHP 7.0)

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

error_reporting_e_notice

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2026/05/19 10:05	current
Line 1:	Line 1:
	+	====== Request for Comments: Default error_reporting to include E_NOTICE ======
	+	* Version: 1.0
	+	* Date: 2012-02-27
	+	* Author: Richard Lynch <lynch@php.net>
	+	* Status: Under Discussion
	+	* First Published at: http://wiki.php.net/rfc/error_reporting_e_notice
	+	* PHP Version: 6.x and above only (Backwards Incompatible)
	+
	+	===== Abstract =====
	+
	+	This proposal suggests that PHP 6 change the php.ini.* default settings to include E_NOTICE.
	+
	+	This proposal specifically does not address E_STRICT nor E_DEPRECATED.
	+
	+	Others may wish to create RFCs for that, or merge them. I would prefer to consider them independently, as the reasoning for each is different.
	+
	+	===== Why? =====
	+
	+	I believe most experienced users will agree that E_NOTICE is a good tool for catching uninitialized variables and array elements that can sometimes point out logical errors in code.
	+
	+	While some do not use it, and others turn it off in PRODUCTION for performance purposes, as a development tool for beginners to PHP, it has a great deal of value.
	+
	+	Experts can trivially change the setting in any/all of the available locations for settings.
	+
	+	Certainly, far too many beginners create mailing list traffic with questions that boil down to misspelled variables or similar errors, because webhosts generally stick to default settings.
	+
	+	Including E_NOTICE will reduce the number of such questions and improve the skill-set of new users to PHP, by forcing them to write (arguably) better code, until they can make an informed decision to select their own preferred error_reporting levels.
	+
	+	One can argue that since PHP automatically initializes all variables, initialization is not strictly needed. While this is true:
	+	* Other languages require initialization, and for educational purpose for beginners, the concept is sound, even while not strictly required
	+	* Some bugs are introduced by misnaming / misspelling variables that were supposed to be the initialized value. E_NOTICE catches those.
	+	* In formal Computer Science, it's simply considered best practice to initialize variables, regardless of the "need" to do so.
	+
	+	===== History =====
	+
	+	This has been discussed on the mailing list several times.
	+
	+	Generally it devolves into whether we should also include E_STRICT and/or E_DEPRECATED and goes nowhere, as I recall.
	+
	+	Hence my preference for proposing E_NOTICE and only E_NOTICE, independently of the others.
	+
	+	I do apologize if this has been formally proposed and voted down before. I searched the RFCs for it, and did not find it.
	+
	+	===== Proposal and Patch =====
	+
	+	The php.ini.* files would be altered to: error_reporting = E_ALL
	+
	+	Even I could probably write a patch for that, though such a trivial patch is probably more quickly implemented by somebody with write karma.
	+
	+	===== Changelog =====
	+
	+	2012-02-27 Initial proposal.

function_autoloading

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2015/09/03 05:06		current
Line 32:		Line 32:
	=== bool php\autoload_register(callable $callback, int $type, bool $prepend = false) ===		=== bool php\autoload_register(callable $callback, int $type, bool $prepend = false) ===

-	This function behaves similar to the current //spl_autoload_register// function. You must call this function individually for the specific autoloader that you want to hook into.	+	This function behaves similar to the current //spl_autoload_register// function. You can pass in a bitmask of types to register for this autoloader.

	=== bool php\autoload_unregister(callable $callback, int $type = 0) ===		=== bool php\autoload_unregister(callable $callback, int $type = 0) ===

function_autoloading2

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2013/12/11 23:36		current
Line 6:		Line 6:
	* Author: Igor Wiedler <igor@wiedler.ch>		* Author: Igor Wiedler <igor@wiedler.ch>
	* Status: In Draft		* Status: In Draft
-	* First Published at: http://wiki.php.net/rfc/function_autoloading2 (forked from [[rfc:use_function\|RFC: Use Function]])	+	* First Published at: http://wiki.php.net/rfc/function_autoloading2 (forked from [[rfc:function_autoloading\|RFC: Function Autoloading]])

	===== Introduction =====		===== Introduction =====
Line 366:		Line 366:
	===== Patches and Tests =====		===== Patches and Tests =====

-	There is a proof-of-concept patch against PHP-5.6 (currently master) [[https://github.com/igorw/php-src/compare/function-autoloading\|Github Branch]]. Note that this includes the accepted but not merged implementation of [[rfc:use_function2\|RFC: Use Function]].	+	There is a proof-of-concept patch against PHP-5.6 [[https://github.com/igorw/php-src/compare/function-autoloading\|Github Branch]].

	This patch is not production ready, but serves as a demonstration of the functionality.		This patch is not production ready, but serves as a demonstration of the functionality.

improved-tls-defaults

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2014/06/20 10:09		current
Line 36:		Line 36:
	* [[https://wiki.php.net/rfc/improved-tls-defaults#honor_cipher_order\|Create "honor_cipher_order" context option]]		* [[https://wiki.php.net/rfc/improved-tls-defaults#honor_cipher_order\|Create "honor_cipher_order" context option]]
	* [[https://wiki.php.net/rfc/improved-tls-defaults#expose_negotiated_values\|Expose negotiated values]]		* [[https://wiki.php.net/rfc/improved-tls-defaults#expose_negotiated_values\|Expose negotiated values]]
-	* [[https://wiki.php.net/rfc/improved-tls-defaults#servers_forward_secrecy\|Server forward secrecy]]	+	* [[https://wiki.php.net/rfc/improved-tls-defaults#server_forward_secrecy\|Server forward secrecy]]
	* [[https://wiki.php.net/rfc/improved-tls-defaults#expose_default_cert_paths\|Expose default cert paths]]		* [[https://wiki.php.net/rfc/improved-tls-defaults#expose_default_cert_paths\|Expose default cert paths]]
	* [[https://wiki.php.net/rfc/improved-tls-defaults#stream_wrapper_creep\|Allow fine-grained protocol selection flags]]		* [[https://wiki.php.net/rfc/improved-tls-defaults#stream_wrapper_creep\|Allow fine-grained protocol selection flags]]

marking_return_value_as_important

Anonymous (anonymous@undisclosed.example.com) — 2025-04-15T11:55:00+00:00

2025/04/03 13:08		current
Line 307:		Line 307:
	* (void) cast: https://github.com/php/php-src/commit/8779e2a6031b78bb0e3cac980410eb038b9932c4		* (void) cast: https://github.com/php/php-src/commit/8779e2a6031b78bb0e3cac980410eb038b9932c4
	* #[\NoDiscard] attribute: https://github.com/php/php-src/commit/5544be7018fe64584945c49fffcda20402bece73		* #[\NoDiscard] attribute: https://github.com/php/php-src/commit/5544be7018fe64584945c49fffcda20402bece73
		+
		+	===== Errata =====
		+
		+	* The <php>#[\NoDiscard]</php> attribute was not implemented on <php>flock()</php>: https://github.com/php/php-src/issues/18235
		+	* The <php>(void)</php> cast is allowed in <php>for()</php>’s statement lists (except the last condition statement): https://github.com/php/php-src/pull/18303

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

mcrypt-viking-funeral

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2016/07/10 18:23		current
Line 3:		Line 3:
	* Date: 2016-01-09		* Date: 2016-01-09
	* Author: Scott Arciszewski, security@paragonie.com		* Author: Scott Arciszewski, security@paragonie.com
-	* Status: Accepted	+	* Status: Implemented (PHP 7.1)
	* First Published at: http://wiki.php.net/rfc/mcrypt-viking-funeral		* First Published at: http://wiki.php.net/rfc/mcrypt-viking-funeral

Line 134:		Line 134:

	Patches are available:		Patches are available:
-	* <https://github.com/php/php-src/pull/1995>	+	* <del><https://github.com/php/php-src/pull/1995></del>
-	* <https://github.com/php/php-src/pull/1996>	+	* <https://github.com/php/php-src/pull/1996> (merged)

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

mysqli_quote_string

Anonymous (anonymous@undisclosed.example.com) — 2026-04-05T19:11:05+00:00

2026/03/10 23:24		current
Line 3:		Line 3:
	* Date: 2025-12-18		* Date: 2025-12-18
	* Author: Kamil Tekiela		* Author: Kamil Tekiela
-	* Status: Accepted	+	* Status: Implemented
	* Implementation: https://github.com/php/php-src/pull/20729		* Implementation: https://github.com/php/php-src/pull/20729

Line 117:		Line 117:

	===== Implementation =====		===== Implementation =====
-	After the RFC is implemented, this section should contain:	+	https://github.com/php/php-src/commit/fbf8bf84dbe3bed33a179a668e2c3d5d109d469a
-	- the version(s) it was merged into	+
-	- a link to the git commit(s)	+
-	- a link to the PHP manual entry for the feature	+

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

nameof

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2023/05/13 20:15		current
Line 7:		Line 7:
	===== Introduction =====		===== Introduction =====

-	Currently, it is possible to inspect virtually any aspect of running code, except there is no easy way to inspect the locally executing scope. For example, a developer can get the class of an object with ''get_class()'' or the name with ''MyClass::class'' or ''$myClass::class''. A developer can get the name of a parameter or property via reflection, however, when a developer needs to write a simple error message, that may be overkill, thus the variable name is usually hard-coded into the error message. This usually works fine until a developer refactors the code and forgets to change the name of the variable in the error message.	+	During PHP execution, it is possible to reflect on most of the code currently running. For example, it is easy to get the name of a class and using reflection utilities: names of properties, methods, and so on. However, getting the name of a callable passed via ''(...)'' is complicated, even though the engine knows it. Getting the name of a constant not bound to a class or a simple variable, is virtually impossible. This RFC proposes a ''nameof'' operator that makes it relatively easy to get the name of virtually any identifier passed to it.

-	''nameof()'' allows developers to quickly and easily access the name of a variable in the current scope, in a way that keeps error messages consistent.	+	This can be used in attributes:

-	This RFC proposes a global ''nameof()'' function that allows a developer to get the name of virtually any user-named variable, property, const, or member, quickly and easily:	+	<code PHP>
		+	#[SerializeWith(nameof(Person->serialize))]
		+	class Person {
		+	public function *serialize() { / do stuff / }*
		+	}
		+	</code>
		+
		+	In error messages:

	<code PHP>		<code PHP>
-	echo nameof($variable); // variable	+	function divide(float $numerator, float $denominator): float {
-	echo nameof($object->property); // property	+	if($denominator === 0) throw new InvalidArgumentException(nameof($denominator) . ' is zero');
-	echo nameof(Enum::Case); // Case	+	}
-	echo nameof(Object::Const); // Const	+	</code>
-	echo nameof(myFunction(...)); // myFunction	+
-	echo nameof(MY_CONSTANT); // MY_CONSTANT	+	In match statements:
		+
		+	<code PHP>
		+	match($propertyName) {
		+	nameof(MyClass->property) => $value,
		+	nameof(MyClass->otherProperty) => $otherValue,
		+	}
		+	</code>
		+
		+	Or anywhere a literal string can be used:
		+
		+	<code PHP>
		+	$arr[nameof(myfunc(...))] = true;
	</code>		</code>

-	As named parameters become more prevalent, providing the end user with the name of the parameter is more important, in a way that it is easy to locate when refactoring, especially as part of a deprecation strategy:	+	As named parameters become more prevalent, providing the end user with the name of the parameter is more important than ever, in a way that it is easy to locate when refactoring, especially as part of a deprecation strategy:

	<code PHP>		<code PHP>
Line 33:		Line 52:
	</code>		</code>

-	Further, using ''nameof()'' would allow simpler usage of attributes, by using the silence operator (see error checking):	+	Here are some further examples showing how the identifier is transformed:

	<code PHP>		<code PHP>
-	// evaluates to #[EventHandler(callback: 'handler')]	+	echo nameof($variable); // variable
-	#[EventHandler(callback: @nameof(Operator::handler))]	+	echo nameof(MyClass->property); // property
-	class Operator {	+	echo nameof(MyClass::staticProperty); // staticProperty
-	public function handler() {	+	echo nameof(Enum::Case); // Case
-	// implementation	+	echo nameof(Object::Const); // Const
-	}	+	echo nameof(myFunction(...)); // myFunction
-	}	+	echo nameof(\MyNamespace\myFunction(...)); // \MyNamespace\myFunction
		+	echo nameof(MY_CONSTANT); // MY_CONSTANT
	</code>		</code>

Line 52:		Line 72:
	echo nameof($a($b)); // same as array access		echo nameof($a($b)); // same as array access
	echo nameof($$a); // ask for $a or use the value of $a		echo nameof($$a); // ask for $a or use the value of $a
		+	echo nameof($a->prop); // what is $a?
	</code>		</code>

-	All of these will generate a compile error: "Cannot get the name of an ambiguous expression."	+	These will generate a compile error: "Cannot get the name of an ambiguous expression."
		+
		+	Note that only the right-most part of the identifier is translated to a string. This is because this is almost always what you want. For example, in the case of ''nameof(MyClass->property)'', you are most likely not interested in the name of ''MyClass'' (otherwise, you'd ask for the ''MyClass::class''), but you are interested in the name of ''property'' because that is what you asked for. The key difference between writing ''"property"'' and ''nameof(MyClass->property)'' comes down to humans reading and modifying the code. It is much safer to refactor code when you know the pedigree of a string that should also be refactored.
		+
		+	To continue the ''"property"'' example, it isn't clear what object "property" comes from without digging into the code, perhaps requiring debugging running code. When it is clear that it comes from ''MyClass'', you can know from whence it came. You can also grep the codebase for "MyClass->property" and locate all usages.

	===== Proposal =====		===== Proposal =====

-	The ''nameof()'' function is not necessarily a function in the traditional sense and can be used anywhere a string literal can be used (such as to define static constants, array keys, and attributes). This means that there is an 'identity' for every valid ''nameof()'':	+	A ''nameof'' operator will be introduced into PHP. During compilation, it will validate that all parts of the identifier exist, and if they do not, a warning will be emitted. The right-most identifier will be turned into a string literal.

-	<code PHP>	+	There is a special case for objects:
-	${nameof($variable)} === $variable;	+
-	$object->{nameof($object->property)} === $object->property;	+	1. A ''::'' will denote a static property/method.
-	constant(Enum::class . '::' . nameof(Enum::Case)) === Enum::Case;	+	2. A ''->'' will denote an instanced property/method
-	constant(Object::class . '::' . nameof(Object::Const)) === Object::Const;	+	3. The left-hand side must be the type name; it can be an abstract type or an interface.
-	(nameof(myFunction(...))() === myFunction();	+	4. The left-hand side cannot be a variable.
-	constant(nameof(MY_CONSTANT)) === MY_CONSTANT;	+
-	</code>	+	If the first two rules are broken (e.g., a ''::'' where a ''->'' should be used), a warning will be emitted: "name of a static property/method is asked for, using instanced syntax." If the 3rd rule is broken (e.g., a type cannot be found), then the standard error will be emitted for a missing type, and if the 4th rule is broken, a compilation error will be emitted: "cannot get the name of a variables property/method." The exceptions for rule 4 are ''$this'', ''static::'', and ''self::'', which may be used on the left-hand side in appropriate contexts.

	There are a limited number of expressions that can resolve to a name using ''nameof()'':		There are a limited number of expressions that can resolve to a name using ''nameof()'':

	* variables (but not variable-variables): ''nameof($var)'' resolves to 'var'		* variables (but not variable-variables): ''nameof($var)'' resolves to 'var'
-	* properties: ''nameof($this->prop)'', ''nameof($a?->prop)'' resolves to 'prop'	+	* properties: ''nameof($this->prop)'', ''nameof(MyClass->prop)'' resolves to 'prop'
	* first-class callables: ''nameof(strlen(...))'' resolves to 'strlen'		* first-class callables: ''nameof(strlen(...))'' resolves to 'strlen'
	* static properties and constants: ''nameof(A::Prop)'' resolves to 'Prop'		* static properties and constants: ''nameof(A::Prop)'' resolves to 'Prop'
	* constants: ''nameof(MY_CONST)'' resolves to 'MY_CONST'		* constants: ''nameof(MY_CONST)'' resolves to 'MY_CONST'

-	When getting the name of constants and functions, the name will NOT be the full name, but the lexical name. This means that if the name is ''use'''d, it will be that name. However, if the full name is used in the ''nameof()'', the full name is returned. It's probably easiest to show this with an example:	+	The name will always be fully qualified, with a beginning slash, if it is a first-class callable or constant and it refers to a globally accessible identifier. For example:

	<code PHP>		<code PHP>
-	namespace Name {	+	namespace Example;
-	const MY_CONST = true;	+
-	function namedFunction() {}	+
-	}	+

-	namespace Other {	+	class A {
-	echo nameof(\Name\MY_CONST); // \Name\MY_CONST	+	public function doStuff(): void {}
-	echo nameof(\Name\namedFunction(...)); // \Name\namedFunction	+
	}		}

-	namespace Using {	+	function doStuff(): void {}
-	use const Name\MY_CONST as ;	+
-	use const Name\MY_CONST as ALIASED_CONST;	+
-	use function Name\namedFunction;	+

-	echo nameof(MY_CONST); // MY_CONST	+	echo nameof(doStuff(...)); // \Example\doStuff
-	echo nameof(\Name\MY_CONST); // \Name\MY_CONST	+	echo nameof(A->doStuff(...)); // doStuff
-	echo nameof(ALIASED_CONST); // ALIASED_CONST	+
-	echo nameof(namedFunction(...)); // namedFunction	+
-	echo nameof(\Name\namedFunction(...)); // \Name\namedFunction(...)	+
-	}	+
	</code>		</code>
-
-	In other language implementations (such as C#), a full name usually isn't returned even if you pass one in. However, a 'full name' is rarely required and can often be constructed from parts, if required. However, as a convenience, in this implementation, if a 'full name' is requested entered, a full name is returned. This allows for the 'least surprises' since what you put in is what you get out.

	Additionally, consider traits and aliasing:		Additionally, consider traits and aliasing:
Line 123:		Line 135:
	}		}

-	$a = new C();	+	echo nameof(C->exampleB(...)); // outputs: "exampleB"
-	echo nameof($a->exampleB(...)); // outputs: "exampleB"	+	echo nameof(B->example(...)); // outputs: "example"
	</code>		</code>

-	In the example above, if we were to return the 'full name' of ''$a->exampleB(...)'' it would actually be 'B::example' but that isn't helpful in the context of class ''C''. By returning the lexical name, the developer gets the response they expect.	+	This adheres to the basic refactoring safety mentioned earlier, since refactoring ''B->example()'' will show up in ''C'', which will then be found by looking for ''C->exampleB'', if it needs to be refactored at all. If ''nameof(C->exampleB)'' returned 'example,' other code may accidentally call ''C->example()'', which would not be ideal, not to mention counter-intuitive.
-		+
-	===== Error Handling =====	+
-		+
-	There are several ways to handle errors, each one has its own merits but ultimately will be left up as a secondary vote. It may not provide the best solution, but the author doesn't have a personal preference:	+
-		+
-	1. No error handling	+
-		+
-	In this case, there is no error handling. This would allow using ''nameof'' on things that don't exist. For example, no error would be output if a developer references a static property on an instanced property:	+
-		+
-	<code PHP>	+
-	class MyClass {	+
-	public string $var;	+
-	}	+
-	nameof(MyClass::var); // no error, returns 'var'	+
-	nameof($aVariable); // no error, returns 'aVariable'	+
-	</code>	+
-		+
-	The downside is that PHP won't natively inform a developer that they've used something that doesn't exist. The main benefit of this approach is that it would allow the community to come up with its own rules via static analysis tools.	+
-		+
-	2. Warnings	+
-		+
-	In this case, PHP would output a warning: "nameof(<name>): does not exist." where <name> is the name the developer passed.	+
-		+
-	Using a class name (or any other method that would normally trigger autoloading) that does not exist, will trigger autoloading and attempt to locate the class. If it is not found, a warning will be issued. If a variable does not exist in the current scope, a warning will be issued. If the referenced property/method/const cannot be located, a warning will be issued. If a function or constant cannot be located in the current scope, a warning will be issued.	+
-		+
-	Warnings can be disabled via the 'silence operator' (''@'') to behave just like the first case. This is the best of both worlds, allowing developers to 'break the rules' to specify properties/functions without a reference to the object (''@nameof(Object::method(...))'' vs. ''nameof($object->method)'') but would require assistance via static analysis tooling to catch mistakes.	+
-		+
-	3. Exceptions	+
-		+
-	An exception model was considered, however, the author believes that it would break the concept of "using ''nameof'' wherever a string could be used". For example, if a name cannot be located, an exception would be thrown. This would be true in the case of simply defining an attribute with a non-existent name:	+
-		+
-	#[EventHandler(handler: nameof(I_DO_NOT_EXIST))]	+
-		+
-	which is probably undesirable and nearly impossible to handle in a graceful way.	+

	===== Backward Incompatible Changes =====		===== Backward Incompatible Changes =====
Line 172:		Line 150:
	===== Proposed PHP Version(s) =====		===== Proposed PHP Version(s) =====

-	* 8.3: release	+	* 8.4: release
-	* 8.2.x: ''nameof'' becomes a reserved word, emitting a notice	+	* 8.3.x: ''\nameof'' becomes a reserved word, emitting a deprecation warning.

	===== RFC Impact =====		===== RFC Impact =====
Line 183:		Line 161:

	==== To Opcache ====		==== To Opcache ====
-	Depends on error type vote.

-	First case: compiled to a string literal.	+	a new AST node (similar to isset) will need to be handled.
-		+
-	Second and third case: a new AST node (similar to isset) will need to be handled.	+

	==== New Constants ====		==== New Constants ====
Line 193:		Line 168:

	===== Open Issues =====		===== Open Issues =====
-	- Should first-class callables be allowed? It's relatively easy to get the name of a first-class callable and only included for completeness.

	===== Unaffected PHP Functionality =====		===== Unaffected PHP Functionality =====
-	PHP will largely be unaffected by this change, except that a new global function is introduced.	+	PHP will largely be unaffected by this change.

	===== Future Scope =====		===== Future Scope =====
Line 203:		Line 177:
	===== Proposed Voting Choices =====		===== Proposed Voting Choices =====
	This is a simple yes-or-no vote to include this feature. 2/3 majority required to pass.		This is a simple yes-or-no vote to include this feature. 2/3 majority required to pass.
-
-	There is a subvote for the type of error checking to include. Majority wins.

	===== Patches and Tests =====		===== Patches and Tests =====

-	experimental implementation: https://github.com/php/php-src/pull/11172/files	+	experimental implementation: https://github.com/php/php-src/pull/11172/files (to be updated)

	===== Implementation =====		===== Implementation =====
Line 218:		Line 190:

	===== References =====		===== References =====
-	Links to external references, discussions or RFCs	+	- internals discussion: https://externals.io/message/120256

	===== Rejected Features =====		===== Rejected Features =====
-	Keep this updated with features that were discussed on the mail lists.	+
		+	Classes need not be supported by ''nameof()'' because there is already an easy way to get the class via ''::class''. This would also be ambiguous when a class name matches a constant name.
		+
		+	There were some suggestions to use ''::name'' instead of ''nameof''; however, this introduces some ambiguity. Take, for example:
		+
		+	<code PHP>
		+	class A {
		+	public const name = 'bob';
		+	}
		+
		+	function example(): A {
		+	return new A();
		+	}
		+
		+	echo example()::name;
		+	echo A::name;
		+	</code>
		+
		+	The author believes ''name'' is a rather popular name for variables and would inevitably confuse things. In the example above, "bob" is output, but it looks like we could be getting the name of ''example'' if we don't look hard enough. Further, it prevents us from getting the names of constants:
		+
		+	<code PHP>
		+	const A = 'billy';
		+
		+	class A {
		+	public const name = 'bob';
		+	}
		+
		+	echo A::name;
		+	</code>
		+
		+	Are we getting the string "A" or "bob" in this example? As it is currently, we would output "bob," and the author feels rather strongly that this is correct. Thus, something like ''::name'' is rejected.

namespaces-for-internal-classes

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2011/04/06 10:59		current
Line 1:		Line 1:
-	====== Request for Comments: How to write RFCs ======	+	====== Request for Comments: Namespaces for internal classes ======
	* Version: 0.1		* Version: 0.1
	* Date: 2008-03-06		* Date: 2008-03-06

on_demand_name_mangling

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2019/07/16 12:24		current
Line 62:		Line 62:
	<?php		<?php
	print_r(get_defined_vars());		print_r(get_defined_vars());
-	mangle_superglobals();	+	php_mangle_superglobals();
	print_r(get_defined_vars());		print_r(get_defined_vars());
	?>		?>
Line 87:		Line 87:
	</code>		</code>

-	In this new implementation, the engine no longer mangles marshaled superglobals at startup. Instead, the //ability// to mangle names has moved to an optional, userland-provided polyfill function ''mangle_superglobals()''.	+	In this new implementation, the engine no longer mangles marshaled superglobals at startup. Instead, the //ability// to mangle names has moved to an optional, userland-provided polyfill function ''php_mangle_superglobals()''.

-	In the example above, an ''a_b'' key was externally supplied. The call to ''mangle_superglobals'' clobbered the original value of ''a_b'' with the value of the //last// seen mangle-equivalent key (''a[b'').	+	In the example above, an ''a_b'' key was externally supplied. The call to ''php_mangle_superglobals'' clobbered the original value of ''a_b'' with the value of the //last// seen mangle-equivalent key (''a[b'').

	Importantly, the user made this mangling happen: the engine did not do it automatically.		Importantly, the user made this mangling happen: the engine did not do it automatically.

pdo_driver_specific_subclasses

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2024/01/11 22:24		current
Line 5:		Line 5:
	* Status: Implemented		* Status: Implemented
	* First Published at: https://wiki.php.net/rfc/pdo_driver_specific_subclasses		* First Published at: https://wiki.php.net/rfc/pdo_driver_specific_subclasses
		+	* Target: PHP 8.4

php8_assertions

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2020/08/03 14:16		current
Line 5:		Line 5:
	* First Published at: https://wiki.php.net/rfc/php8_assertions		* First Published at: https://wiki.php.net/rfc/php8_assertions

-	This RFC was abandoned due to time constraints by the author. However, the portion that sets ''assert.exception'' to default to ''1'' has been merged for PHP 8. If anyone picks up this RFC, it only needs to deal with ''assert_options'' and potentially INI settings.	+	This RFC was abandoned due to time constraints by the author. However, the portion that sets ''assert.exception'' to default to ''1'' has been [[https://github.com/php/php-src/pull/5925\|merged for PHP 8]]. If anyone picks up this RFC, it only needs to deal with ''assert_options'' and potentially INI settings.

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

sqlite3_exceptions

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2023/05/23 15:17		current
Line 3:		Line 3:
	* Date: 2022-10-24		* Date: 2022-10-24
	* Author: BohwaZ, php at bohwaz dot net		* Author: BohwaZ, php at bohwaz dot net
-	* Status: Accepted	+	* Status: Implemented
		+	* Implementation: https://github.com/php/php-src/commit/ddd9a08f566d86083d04de320e24f0751a1de759
	* First Published at: http://wiki.php.net/rfc/sqlite3_exceptions		* First Published at: http://wiki.php.net/rfc/sqlite3_exceptions

stable_sorting

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2020/06/17 09:28		current
Line 2:		Line 2:
	* Date: 2020-05-12		* Date: 2020-05-12
	* Author: Nikita Popov <nikic@php.net>		* Author: Nikita Popov <nikic@php.net>
-	* Status: Accepted	+	* Status: Implemented
	* Target Version: PHP 8.0		* Target Version: PHP 8.0
	* Implementation: https://github.com/php/php-src/pull/5236		* Implementation: https://github.com/php/php-src/pull/5236

stricter_implicit_boolean_coercions

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2022/06/05 21:52		current
Line 3:		Line 3:
	* Date: 2022-05-16		* Date: 2022-05-16
	* Author: Andreas Leathley, <a.leathley@gmx.net>		* Author: Andreas Leathley, <a.leathley@gmx.net>
-	* Status: Voting	+	* Status: Declined
	* First Published at: http://wiki.php.net/rfc/stricter_implicit_boolean_coercions		* First Published at: http://wiki.php.net/rfc/stricter_implicit_boolean_coercions

Line 253:		Line 253:
	Voting started on 2022-06-06 and will end on 2022-06-20.		Voting started on 2022-06-06 and will end on 2022-06-20.

-	<doodle title="Accept Stricter implicit boolean coercions RFC as proposed?" auth="iquito" voteType="single" closed="false">	+	<doodle title="Accept Stricter implicit boolean coercions RFC as proposed?" auth="iquito" voteType="single" closed="true">
	* Yes		* Yes
	* No		* No

voting2017

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2019/01/31 13:28		current
Line 1:		Line 1:
-	====== PHP RFC: RFC Workflow & Voting - 2019 update ======	+	====== PHP RFC: RFC Workflow & Voting (2019 update) ======
	* Version: 2.0.0002		* Version: 2.0.0002
	* Date: 2019		* Date: 2019

voting2019

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2019/02/05 11:59		current
Line 3:		Line 3:
	* Date: 2019		* Date: 2019
	* Author: Zeev Suraski <zeev@php.net>		* Author: Zeev Suraski <zeev@php.net>
-	* Status: Under Discussion	+	* Status: Suspended
	* First Published at: http://wiki.php.net/rfc/voting2017 (additional history available there)		* First Published at: http://wiki.php.net/rfc/voting2017 (additional history available there)

services_amazon

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2026/05/19 10:05	current
Line 1:	Line 1:
	+	====== Services_Amazon ======
	+
	+	===== Deprecated Functionality - how to migrate =====
	+	Please use Services_Amazon instead of Services_AmazonECS4.
	+
	+	Deprecated code will not be processed after August 15:
	+	require_once 'Services/AmazonECS4.php';
	+	$amazon = new Services_AmazonECS4(YOUR_ACCESS_KEY_ID);
	+	$amazon->ItemSearch(...);
	+
	+	New code works fine:
	+	require_once 'Services/Amazon.php';
	+	$amazon = new Services_Amazon(YOUR_ACCESS_KEY_ID, YOUR_SECRET_ACCESS_KEY);
	+	$amazon->ItemSearch(...); // <= backward compatible with Services_AmazonECS4
	+

type_safety

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2024/09/01 12:39		current
Line 113:		Line 113:
	- Change the contract of methods to state that default values are covariant, rather than contravariant. To be precise, that the default value of a parameter in a sub-class must be of the same concrete type as the default value in the parent, or a sub-type of it, regardless of the parameter's declared type. This would invalidate a non-trivial amount of existing code, so would need to be introduced in a major version, probably with a deprecation period.		- Change the contract of methods to state that default values are covariant, rather than contravariant. To be precise, that the default value of a parameter in a sub-class must be of the same concrete type as the default value in the parent, or a sub-type of it, regardless of the parameter's declared type. This would invalidate a non-trivial amount of existing code, so would need to be introduced in a major version, probably with a deprecation period.
	- Limit the expressions allowed to those where ''default'' can be safely substituted for any type (i.e. where it can be analysed as of type ''mixed''). In practice, this means conditional expressions where ''default'' is used unchanged as the result, such as <php>$condition ? 'explicit value' : default</php>. This probably requires a different implementation, where ''default'' is compiled as a placeholder value which triggers the function call to act as though no value was passed.		- Limit the expressions allowed to those where ''default'' can be safely substituted for any type (i.e. where it can be analysed as of type ''mixed''). In practice, this means conditional expressions where ''default'' is used unchanged as the result, such as <php>$condition ? 'explicit value' : default</php>. This probably requires a different implementation, where ''default'' is compiled as a placeholder value which triggers the function call to act as though no value was passed.
-	- Limit use further, to only using ''default'' as a stand-alone token to skip a parameter. This is essentially what was proposed and declined in [[skipparams]].	+	- Limit use further, to only using ''default'' as a stand-alone token to skip a parameter. This is essentially what was proposed and declined in [[rfc/skipparams\|Stas Malyshev's "Skipping optional parameters for functions" RFC]].

	This RFC currently proposes option 1.		This RFC currently proposes option 1.

ldap

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2011/04/06 10:59		current
Line 1:		Line 1:
		+	For PHP suitable sources and up-to-date information see [[https://github.com/winlibs/openldap]]
		+
	OpenLDAP support in PHP relies on two of the OpenLDAP libraries:		OpenLDAP support in PHP relies on two of the OpenLDAP libraries:
	* olber32		* olber32

language-feature-usage-survey

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2026/05/19 10:05	current
Line 1:	Line 1:
	+	===== Language Feature Usage Survey =====
	+	//Lead: [[bishop@php.net\|Bishop Bettini]]//,
	+	//Working Group Members: TBD//

	+	The engine development team ("internals", [[mailto:internals@lists.php.net\|internals@lists.php.net]]) continually evolves the PHP language, doing so with a healthy respect for preserving backwards compatibility (BC). When the need - or option - for compatibility breaks arise, internals asks the question: "is the risk of breaking this behavior for existing code worth the gain of doing so?"
	+
	+	It's a tough - and subjective - question to answer. Given the sheer volume of PHP installations, it's impossible to speculate how many sites would be affected by a BC break. So without robust information otherwise, the internals team rushes into the debate using a variety of appeals:
	+
	+	* The appeal to statistics. The reasoning goes like this: "The feature has been around a long time, and there are millions of sites, so it's likely that a high percentage of those sites would be affected."
	+	* The appeal to personal experience. This reads like: "I have never used this feature. I've asked all my colleagues: they've never used this feature. I've been doing this for decades, and I've seen it all, so this feature must not be used at all."
	+	* The appeal to [[https://packagist.org/\|Packagist]]. "I scanned the N most popular open-source packages and counted how many times the feature's used. It was used X times, and 80% of those were in tests, so it's not used much in production code."
	+
	+	Those involved in the debate pick a statistic that resonates, then argue using that statistic as if it was a fact. They're not facts, unfortunately. They're cherry-picked statistics, and no way to make a crucial decision.
	+
	+	==== Idea ====
	+
	+	Let's ask users to send us information about how they're using PHP. Let's build an official static analyzer, which writes its results into a published interchange format, and offers to securely send analysis results to an official repository. Let's work with existing static analyzers and code editors to integrate this into their products. Let's work with continuous integration companies to get the tool as part of their pipeline offerings. Let's promote it on Reddit, Packagist, Github, StackOverflow, and any and everywhere else a developer visits.
	+
	+	=== Benefits ===
	+
	+	To PHP users:
	+	* Representation. When they participate, they know internals will consider their specific usage in evolving design.
	+	* Early warning. If internals made a breaking change, be it big or small, the analyzer will flag it.
	+	* Quality guidance. If internals has deprecated a feature, or has detected a usage that may be vulnerable, the analyzer will flag it.
	+
	+	To PHP internals:
	+	* Data, data, data. With real-world metrics at our finger-tips, we can make informed decisions.
	+	* Encourage change. If a feature has little real-world usage, we have the option to proactively remove it.
	+	* Discourage disruption. If a feature has substantial real-world usage, RFC authors can save their time and work on something that can be changed.
	+
	+	To existing static analysis tools:
	+	* Offload work. Fewer rules to maintain, as they can be handled upstream.
	+	* An open interchange format.
	+
	+	To code editors and continuous integration service vendors:
	+	* Distinguish themselves from the competition.
	+	* Help their customers produce better code, meaning more opportunity to gather new customers.
	+
	+	=== Requirements ===
	+
	+	The tool must be:
	+	* Capable of running correctly on PHP 5.0+
	+	* Quick to run / Efficient in time (measured in RPS, rules per second)
	+	* Small footprint / Efficient in space (measured in bytes)
	+	* Available as a standalone program, from an out-of-band download
	+	* Available to download, in-band, from the php cli executable
	+	* Analysis results:
	+	* Sending results to official PHP repository is _optional_
	+	* Transmission is secure only, and obviously so
	+	* Anonymous by default
	+	* Resistant to spamming
	+	* Timestamped
	+
	+	==== Progress ====
	+	Idea definition only.
	+
	+	==== Status ====
	+	Idea only.

concerns

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2019/08/12 12:03		current
Line 5:		Line 5:
	==== Concerns about the P++ idea ====		==== Concerns about the P++ idea ====

-	Concerns about the ([[https://marc.info/?l=php-internals&m=156529545007909&w=2\|P++ idea]]) are presented in this document.	+	Concerns about the [[https://marc.info/?l=php-internals&m=156529545007909&w=2\|P++ idea]] are presented in this document.

faq

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2019/08/14 13:37		current
Line 50:		Line 50:
	There are many issues with this approach, but these are probably the most important ones:		There are many issues with this approach, but these are probably the most important ones:
	- For the dynamic crowd - more strictness is not equivalent to progress, and as such - they don't want to see future versions of PHP forcing them in that direction. They still want to get other types of new features (non-strictness related), better performance, bug fixes, new extensions and such. Making PHP stricter with newer versions means that for many users - upgrading would mean going backwards as far as their development preferences are concerned.		- For the dynamic crowd - more strictness is not equivalent to progress, and as such - they don't want to see future versions of PHP forcing them in that direction. They still want to get other types of new features (non-strictness related), better performance, bug fixes, new extensions and such. Making PHP stricter with newer versions means that for many users - upgrading would mean going backwards as far as their development preferences are concerned.
-	- Equally important - it's remarkably difficult - arguably impractical - from a development effort point of view. Unlike this proposal - which aims to continue supporting both dialects in the same codebase - having a version that would no longer be actively developed, but would still have to be maintained for security and critical bugfixes - requires resources that we simply don't have (it is arguably a kind of a fork).	+	- Equally important - it's remarkably difficult - arguably impractical - from a development effort point of view. Unlike this proposal - which aims to continue supporting both dialects in the same codebase - having a version that would no longer be actively developed, but would still have to be maintained for security and critical bugfixes over the course of over a decade - requires resources that we simply don't have (it is arguably a kind of a fork).

	==== Will I need to choose between PHP and P++? ====		==== Will I need to choose between PHP and P++? ====

argon2_password_hash

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2017/09/22 13:28		current
Line 3:		Line 3:
	* Date: 2016-07-10		* Date: 2016-07-10
	* Author: Charles R. Portwood II <charlesportwoodii@erianna.com>		* Author: Charles R. Portwood II <charlesportwoodii@erianna.com>
-	* Status: Accepted	+	* Status: Implemented (in PHP 7.2)
	* First Published at: http://wiki.php.net/rfc/argon2_password_hash		* First Published at: http://wiki.php.net/rfc/argon2_password_hash

argon2_password_hash_enhancements

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2018/06/23 17:45		current
Line 14:		Line 14:


-	Argon2id is now the recommended Argon2 variant to use in the ITEF draft spec.	+	Argon2id is now the recommended Argon2 variant to use in the IETF draft spec.

	===== Proposal =====		===== Proposal =====

autodefine

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2011/04/06 10:59		current
Line 3:		Line 3:
	* Date: 2010-12-07		* Date: 2010-12-07
	* Author: Reinier van Loon <reinier.van.loon@gmail.com>		* Author: Reinier van Loon <reinier.van.loon@gmail.com>
-	* Status: Under Discussion	+	* Status: Inactive
	* First Published at: http://wiki.php.net/rfc/autodefine		* First Published at: http://wiki.php.net/rfc/autodefine

backslashnamespaces

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2008/10/25 13:54		current
Line 287:		Line 287:
	* because \ is a single keystroke, it is possible to require \ prefix for all global functions/classes/constants, and conversion is minimally effortful (from personal experience trying to convert files to several namespace separators to see what it was like)		* because \ is a single keystroke, it is possible to require \ prefix for all global functions/classes/constants, and conversion is minimally effortful (from personal experience trying to convert files to several namespace separators to see what it was like)
	* code review ambiguities disappear permanently		* code review ambiguities disappear permanently
-	* name resolution order problems disappear if we decide that "foo/bar" or "foo::bar" is always prefixed with namespace name, and only short names like "bar()" or "new bar" are checked for both "nsname/bar()" and internal function "bar()" or "class nsname/bar" and internal class "bar". "/foo/bar" is used for global scoping.	+	* name resolution order problems disappear if we decide that "foo\bar" or "foo::bar" is always prefixed with namespace name, and only short names like "bar()" or "new bar" are checked for both "nsname\bar()" and internal function "bar()" or "class nsname\bar" and internal class "bar". "\foo\bar" is used for global scoping.
	* code coverage of namespace-related code is so good, it is possible to be very confident of the correctness of the patch.		* code coverage of namespace-related code is so good, it is possible to be very confident of the correctness of the patch.

binary_string_comparison

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2014/08/17 20:04		current
Line 3:		Line 3:
	* Date: 2014-08-01, internals on 2014-08-17		* Date: 2014-08-01, internals on 2014-08-17
	* Author: Marc Bennewitz, php@mabe.berlin		* Author: Marc Bennewitz, php@mabe.berlin
-	* Status: Draft	+	* Status: Under Discussion
	* First Published at: http://wiki.php.net/rfc/binary_string_comparison		* First Published at: http://wiki.php.net/rfc/binary_string_comparison

Line 33:		Line 33:

	=== string == string ===		=== string == string ===
-	(http://3v4l.org/4KA8M)	+	(http://3v4l.org/2bIUj)

	<?php		<?php
	echo ('1' == '1' ? 'true' : 'false') . " ('1' == '1')\n";		echo ('1' == '1' ? 'true' : 'false') . " ('1' == '1')\n";
	echo ('2' == '1' ? 'true' : 'false') . " ('2' == '1')\n";		echo ('2' == '1' ? 'true' : 'false') . " ('2' == '1')\n";
		+	echo ('0' == '0x0' ? 'true' : 'false') . " ('0' == '0x0')\n";
		+	echo ('0' == '00' ? 'true' : 'false') . " ('0' == '00')\n";
	echo ('1e1' == '10' ? 'true' : 'false') . " ('1e1' == '10')\n";		echo ('1e1' == '10' ? 'true' : 'false') . " ('1e1' == '10')\n";
	echo ('1E1' == '10' ? 'true' : 'false') . " ('1E1' == '10')\n";		echo ('1E1' == '10' ? 'true' : 'false') . " ('1E1' == '10')\n";
Line 53:		Line 55:
	true ('1' == '1')		true ('1' == '1')
	false ('2' == '1')		false ('2' == '1')
		+	true ('0' == '0x0')
		+	true ('0' == '00')
	true ('1e1' == '10')		true ('1e1' == '10')
	true ('1E1' == '10')		true ('1E1' == '10')
Line 68:		Line 72:
	true ('1' == '1')		true ('1' == '1')
	false ('2' == '1')		false ('2' == '1')
		+	false ('0' == '0x0')
		+	false ('0' == '00')
	false ('1e1' == '10')		false ('1e1' == '10')
	false ('1E1' == '10')		false ('1E1' == '10')

cachediterable_straw_poll

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2021/06/05 18:27		current
Line 3:		Line 3:
	* Date: 2021-06-01		* Date: 2021-06-01
	* Author: Tyson Andre, <tandre@php.net>		* Author: Tyson Andre, <tandre@php.net>
-	* Status: Voting	+	* Status: Closed
	* First Published at: https://wiki.php.net/rfc/cachediterable_straw_poll		* First Published at: https://wiki.php.net/rfc/cachediterable_straw_poll

Line 54:		Line 54:
	(No namespace alternatives were suggested between announcing the straw poll and opening the straw poll in https://externals.io/message/114687#114687)		(No namespace alternatives were suggested between announcing the straw poll and opening the straw poll in https://externals.io/message/114687#114687)

-	<doodle title="Preferred namespacing choice for CachedIterable" auth="tandre" votetype="multi" closed="false">	+	<doodle title="Preferred namespacing choice for CachedIterable" auth="tandre" votetype="multi" closed="true">
	* Iterable\CachedIterable		* Iterable\CachedIterable
	* CachedIterable		* CachedIterable
Line 67:		Line 67:
	Preferred namespacing choice for successors to the [[rfc:any_all_on_iterable\|any() and all() on iterables]] RFC: [[https://github.com/php/php-src/pull/6053\|any()/all()/none()/find()/reduce()]]		Preferred namespacing choice for successors to the [[rfc:any_all_on_iterable\|any() and all() on iterables]] RFC: [[https://github.com/php/php-src/pull/6053\|any()/all()/none()/find()/reduce()]]

-	<doodle title="Preferred namespacing choice for any()/all()/none()/reduce()/find()" auth="tandre" votetype="multi" closed="false">	+	<doodle title="Preferred namespacing choice for any()/all()/none()/reduce()/find()" auth="tandre" votetype="multi" closed="true">
	* Iterable\any()		* Iterable\any()
	* iterable_any()		* iterable_any()
Line 86:		Line 86:
	("Still too small in scope" means you would probably vote against the implementation as-is for that reason)		("Still too small in scope" means you would probably vote against the implementation as-is for that reason)

-	<doodle title="Global functions I would want to add to PHP to act on iterables as described in implementation link" auth="tandre" votetype="multi" closed="false">	+	<doodle title="Global functions I would want to add to PHP to act on iterables as described in implementation link" auth="tandre" votetype="multi" closed="true">
	* any(...)/all(iterable $input, $callback = null): bool		* any(...)/all(iterable $input, $callback = null): bool
	* none(...): bool		* none(...): bool
Line 123:		Line 123:
	(Aside: shorter namespace names such as iter were unpopular in a [[rfc:any_all_on_iterable_straw_poll_namespace\|previous straw poll]], and iter would conflict with https://github.com/nikic/iter)		(Aside: shorter namespace names such as iter were unpopular in a [[rfc:any_all_on_iterable_straw_poll_namespace\|previous straw poll]], and iter would conflict with https://github.com/nikic/iter)

-	<doodle title="Preferred namespacing for iterable\" auth="tandre" votetype="single" closed="false">	+	<doodle title="Preferred namespacing for iterable\" auth="tandre" votetype="single" closed="true">
	* iterable\ (lowercase)		* iterable\ (lowercase)
	* Iterable\ (CamelCase)		* Iterable\ (CamelCase)

change-terminology-to-allowlist-and-blocklist

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2020/06/16 12:08		current
Line 3:		Line 3:
	* Date: 2020-06-09		* Date: 2020-06-09
	* Author: Michał Marcin Brzuchalski <brzuchal@php.net>		* Author: Michał Marcin Brzuchalski <brzuchal@php.net>
-	* Status: Under Discussion	+	* Status: Draft
	* Target Version: PHP 8.0		* Target Version: PHP 8.0
-	* First Published at: http://wiki.php.net/rfc/change-terminology-to-allowlist-and-blocklist	+	* First Published at: https://wiki.php.net/rfc/change-terminology-to-excludelist

	Change the use of "blacklist" in Opcache configuration with better self-descriptive terminology.		Change the use of "blacklist" in Opcache configuration with better self-descriptive terminology.

change-terminology-to-excludelist

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2026/05/19 10:05	current
Line 1:	Line 1:
	+	====== PHP RFC: Change terminology to ExcludeList ======
	+	* Version: 0.9
	+	* Date: 2020-06-09
	+	* Author: Michał Marcin Brzuchalski <brzuchal@php.net>
	+	* Status: Under Discussion
	+	* Target Version: PHP 8.0
	+	* First Published at: http://wiki.php.net/rfc/change-terminology-to-excludelist
	+
	+	Change the use of "blacklist" in Opcache configuration with better self-descriptive terminology.
	+
	+	===== Introduction =====
	+	The word "blacklist" require additional context to figure out the exact intention of a specific
	+	configuration. This proposal suggest to change this to a name that better reflects what the functionality does.
	+
	+	===== Proposal =====
	+	The proposal is to replace all occurrences of "blacklist" to the alternative "exclude_list".
	+
	+	A list of Open Source projects with similar terminology change is listed in [[https://wiki.php.net/rfc/change-terminology-to-allowlist-and-blocklist#references\|references]] section. There is also a draft [[https://tools.ietf.org/id/draft-knodel-terminology-00.html\|IETF document]].
	+
	+	==== Change INI directive name ====
	+	A new INI directive called ''opcache.exclude_list_filename'' will be introduced and will configure the same internal value as the already existing ''opcache.blacklist_filename''.
	+
	+	The INI directive called ''opcache.blacklist_filename'' will remain as is but with additional soft-deprecation in the docs and
	+	in ''php.ini-development'' and ''php.ini-production''.
	+
	+	==== Change in opcache_get_configuration function ====
	+	The ''opcache_get_configuration()'' function currently returns an associative array with information about Opcache.
	+	A new key named ''exclude_list'' will be added to resulting array with the same value as the original ''blacklist''
	+	key which will remain untouched with additional soft-deprecation in the docs.
	+
	+
	+	===== Backward Incompatible Changes =====
	+	Most of the changes are internal only with two exceptions for which this patch requires RFC:
	+
	+	- The new ''opcache.exclude_list_filename'' INI directive
	+	- An extra ''exclude_list'' key in the returned array value of ''opcache_get_configuration()''
	+
	+	Whether the use of the ''opcache.blacklist_filename'' INI directive triggers a deprecation notice is a subject to a secondary vote.
	+
	+	===== Proposed PHP Version(s) =====
	+	Next PHP version 8.0.
	+
	+	===== RFC Impact =====
	+	==== To SAPIs ====
	+	None.
	+
	+	==== To Existing Extensions ====
	+	Only in Opcache.
	+
	+	==== To Opcache ====
	+	This proposal modifies Opcache structure and function names by replacing "blacklist" with "exclude_list".
	+
	+	==== php.ini Defaults ====
	+
	+	* php.ini-development changed name of ''opcache.blacklist_filename'' into ''opcache.exclude_list_filename''
	+	* php.ini-production changed name of ''opcache.blacklist_filename'' into ''opcache.exclude__filename''
	+
	+	===== Future scope =====
	+	The possibility to remove ''opcache.blacklist_filename'' INI directive and ''opcache_get_configuration()["exclude_list"]'' in the next
	+	minor PHP version: 8.1.
	+
	+	===== Proposed Voting Choices =====
	+	Accept changing terminology in PHP 8.0? Yes/No with 2/3 majority required.
	+	Add deprecation notice when deprecated INI directive used? Yes/No
	+
	+	===== Implementation =====
	+	- [[https://github.com/php/php-src/pull/5685]]
	+
	+	===== References =====
	+	- [[https://github.com/sebastianbergmann/phpunit/blob/master/ChangeLog-9.3.md#930---2020-08-07\|PHPUnit]]
	+	- [[https://github.com/xdebug/xdebug/commit/63b43b51e43b794cf8cd740e54089b2b7320fbe1\|Xdebug]]
	+	- [[https://www.drupal.org/project/drupal/issues/2993575\|Drupal]]
	+	- [[https://gitlab.com/gitlab-org/gitlab/-/issues/7554\|Gitlab]]
	+	- [[https://go-review.googlesource.com/c/go/+/236857/\|GoLang]]
	+	- [[https://github.com/rails/rails/issues/33677\|RoR]]
	+	- [[https://github.com/rubocop-hq/rubocop/pull/7469\|Ruby Static Analyser]]

checkdnsrr-default-type

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2026/05/19 10:05	current
Line 1:	Line 1:
	+	====== Request for Comments: Change checkdnsrr() $type argument behavior ======
	+	* RFC Version: 1.00
	+	* Target PHP Version: 5.7 & 7.0
	+	* Date: 2014-09-19
	+	* Author: Kris Craig <nowiki><</nowiki><kriscraig@php.net><nowiki>></nowiki>
	+	* Status: Under Discussion
	+	* First Published at: http://wiki.php.net/rfc/checkdnsrr-default-type
	+
	+	===== Abstract =====
	+
	+	This RFC proposes that the default behavior of the checkdnsrr() function be changed such that it no longer checks only for MX records by default.
	+
	+	===== Background =====
	+
	+	The checkdnsrr() function is used to check if a given hostname exists. It's essentially PHP's basic DNS lookup function. It returns TRUE if the hostname is found, FALSE otherwise. It accepts 2 arguments, the $host as a string and the record $type as a string. The possible values for $type are: "A", "MX", "NS", "SOA", "PTR", "CNAME", "AAAA", "A6", "SRV", "NAPTR", "TXT", and "ANY". If "ANY", it'll return TRUE regardless of the record type it finds.
	+
	+	===== Current Behavior =====
	+
	+	The $type argument is currently optional and defaults to "MX".
	+
	+	===== The Problem =====
	+
	+	The current behavior is very counter-intuitive because the function is most commonly used for general DNS lookups. In most circumstances, these lookups are not for MX records. As a result, developers who implement this function without noticing the "MX" default in the documentation will have their DNS lookups fail even if the hostname is there. This can lead to a lot of time being wasted triaging what appears to be a DNS issue.
	+
	+	What makes this even more perplexing is the fact that there is already a function dedicated specifically for performing MX record lookups: getmxrr().
	+
	+	There does not appear to be any compelling use case for the default value for PHP's general DNS lookup function being "MX".
	+
	+	===== Solution #1 =====
	+
	+	Change the default value of $type from "MX" to "ANY". This would be implemented in PHP 7.0.
	+
	+	==== Pros ====
	+
	+	This would be the most convenient and intuitive option for developers, as they'd only have to supply the hostname and it would return a general DNS lookup, which is what most people would expect.
	+
	+	==== Cons ====
	+
	+	Though the potential for BC breakage would be the same, this would make it much harder to spot since no error would be generated. Instead, it would just silently fail for anyone expecting the default to be "MX". Concerns have also been raised on Internals that this could be a potential vector for amplification attacks.
	+
	+	===== Solution #2 =====
	+
	+	Make the $type argument required. Starting in PHP 5.7, not including the second argument would cause an E_DEPRECATED to be thrown. Starting in PHP 7.0, it would throw an E_ERROR, causing script execution to abort.
	+
	+	==== Pros ====
	+
	+	For the relatively few instances in which a script is passing only one argument with the expectation that it be checking for "MX", this will make it much easier for devs to spot this BC and adapt their code accordingly. It may also be less susceptible to amplification attacks.
	+
	+	==== Cons ====
	+
	+	The intuitive behavior for virtually any DNS lookup function/utility/etc is for it to accept a hostname and return whether there are any matches. Requiring people to specify a second "ANY" argument would be somewhat cumbersome and may raise complaints from devs who question why the behavior that the overwhelming number of users are looking for is not the default.
	+
	+	===== Final Thoughts =====
	+
	+	This one appears to be pretty much a no-brainer. I believe the much trickier question is whether to change the default or make the argument required. I'm honestly on the fence as far as that goes, so I would encourage everyone with an opinion on this to weigh-in and make their case on Internals.
	+
	+	===== Vote =====
	+
	+	Though this could be reasonably interpreted as language-touching and otherwise, I'll err on the side of caution and require the greater 2/3 majority in order for this RFC to pass. A separate vote will be held simultaneously to determine which solution will be implemented if the RFC passes. Whichever one gets the most votes will win.
	+
	+	===== Changelog =====
	+
	+	Version 1.00 : Initial proposal.

consistent-names

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2017/09/22 13:28		current
Line 3:		Line 3:
	* Date: 2014-01-23		* Date: 2014-01-23
	* Author: Yasuo Ohgaki, yohgaki@ohgaki.net		* Author: Yasuo Ohgaki, yohgaki@ohgaki.net
-	* Status: Draft	+	* Status: Inactive
	* First Published at: http://wiki.php.net/rfc/consistent-names		* First Published at: http://wiki.php.net/rfc/consistent-names

covariant-returns-and-contravariant-parameters

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2019/01/16 18:18		current
Line 3:		Line 3:
	* Date: 2018-09-20		* Date: 2018-09-20
	* Author: Levi Morrison <levim@php.net>		* Author: Levi Morrison <levim@php.net>
-	* Status: Accepted	+	* Status: Implemented (in PHP 7.4)
	* First Published at: http://wiki.php.net/rfc/covariant-returns-and-contravariant-parameters		* First Published at: http://wiki.php.net/rfc/covariant-returns-and-contravariant-parameters

curl-file-upload

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2017/09/22 13:28		current
Line 19:		Line 19:
	</code>		</code>

-	This API is both invonvenient and insecure, it is impossible to send data starting with '@' to the POST, and any user data that is being re-sent via cURL need to be sanitized so that the data value does not start with @. In general, in-bound signalling usually vulnerable to all sorts of injections and better not done in this way.	+	This API is both inconvenient and insecure, it is impossible to send data starting with '@' to the POST, and any user data that is being re-sent via cURL need to be sanitized so that the data value does not start with @. In general, in-bound signalling usually vulnerable to all sorts of injections and better not done in this way.

	===== CurlFile proposal =====		===== CurlFile proposal =====

data_encoding_api

Anonymous (anonymous@undisclosed.example.com) — 2025-11-27T10:35:50+00:00

2025/11/25 10:04		current
Line 522:		Line 522:
	$encodedUpper = "48656C6C6F20776F726C6421"; // using uppercase characters		$encodedUpper = "48656C6C6F20776F726C6421"; // using uppercase characters
	$encodedLower = "48656c6c6f20776f726c6421"; // using lowercase characters		$encodedLower = "48656c6c6f20776f726c6421"; // using lowercase characters
-		+	$encodedUpperWithSpaces = "48 65\n6C\t6C\r6F 2C 20 57 6F 72 6C 64 21";
		+	$encodedWithSpaces = "48 65\n6C\t6C\r6F 2c 20 57 6f 72 6C 64 21";
	echo base16_encode($data);		echo base16_encode($data);
	// returns "48656C6C6F20776F726C6421" the letters are uppercased by default		// returns "48656C6C6F20776F726C6421" the letters are uppercased by default
Line 530:		Line 532:

	echo base16_decode($encodedUpper);		echo base16_decode($encodedUpper);
		+	// returns 'Hello world!'
		+
		+	echo base16_decode($encodedUpperWithSpaces);
	// returns 'Hello world!'		// returns 'Hello world!'

Line 535:		Line 540:
	// throws a UnableToDecodeException exception		// throws a UnableToDecodeException exception
	// by default value is expected with uppercased letters		// by default value is expected with uppercased letters
		+
		+
		+	echo base16_decode($encodedWithSpaces);
		+	// throws a UnableToDecodeException exception
		+	// by default value is expected with uppercased letters
		+	// the example contains lowercased letters (the space do not affect decoding)


Line 542:		Line 553:
	echo base16_decode($encodedLower, variant: Base16::Upper, decodingMode: DecodingMode::Forgiving);		echo base16_decode($encodedLower, variant: Base16::Upper, decodingMode: DecodingMode::Forgiving);
	// 'Hello world!' the decoding is case-insensitive.		// 'Hello world!' the decoding is case-insensitive.
		+
		+	echo base16_decode($encodedWithSpaces, variant: Base16::Upper, decodingMode: DecodingMode::Forgiving);
		+	// 'Hello world!' the decoding is case-insensitive and is not affected by the whitespaces.

	</code>		</code>
Line 553:		Line 567:
	If the input includes lowercase characters, an `UnableToDecodeException` WILL be raised.		If the input includes lowercase characters, an `UnableToDecodeException` WILL be raised.
	To permit case-insensitive decoding, the ''DecodingMode::Forgiving'' mode MAY be used.		To permit case-insensitive decoding, the ''DecodingMode::Forgiving'' mode MAY be used.
		+
		+	As for all the encoding algorithms, whitespaces should not be taken into account during decoding.

debugging_pdo_prepared_statement_emulation

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2017/09/22 13:28		current
Line 3:		Line 3:
	* Date: 2016-10-17		* Date: 2016-10-17
	* Author: Adam Baratz adambaratz@php.net		* Author: Adam Baratz adambaratz@php.net
-	* Status: Accepted	+	* Status: Implemented (in PHP 7.2)
	* First Published at: https://wiki.php.net/rfc/debugging_pdo_prepared_statement_emulation		* First Published at: https://wiki.php.net/rfc/debugging_pdo_prepared_statement_emulation

decode_html

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2024/09/06 18:56		current
Line 125:		Line 125:
	A new enum specifies supported HTML contexts. For the most part the enum specifies three internal properties:		A new enum specifies supported HTML contexts. For the most part the enum specifies three internal properties:

-	- Are character references decoded?	+	* Are character references decoded?
-	- Are ambiguous ampersand references interpreted?	+	* Are ambiguous ampersand references interpreted?
-	- Are NULL bytes replace or removed?	+	* Are NULL bytes replace or removed?

	While these could be handled via three boolean flags, that would require developers to understand the nuances involved in the different situations where they imply. By focusing the API on the kind of situations developers work in, the burden is removed to know the internal details of HTML parsing. For this reason there is overlap in ''Script'', ''Style'', and ''Comment'' contexts, because the parsing rules are identical.		While these could be handled via three boolean flags, that would require developers to understand the nuances involved in the different situations where they imply. By focusing the API on the kind of situations developers work in, the burden is removed to know the internal details of HTML parsing. For this reason there is overlap in ''Script'', ''Style'', and ''Comment'' contexts, because the parsing rules are identical.

default_encoding

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2014/02/14 06:34		current
Line 128:		Line 128:
	* http://svn.php.net/viewvc?view=revision&revision=332851		* http://svn.php.net/viewvc?view=revision&revision=332851
	* http://svn.php.net/viewvc?view=revision&revision=332852		* http://svn.php.net/viewvc?view=revision&revision=332852
		+	* http://svn.php.net/viewvc?view=revision&revision=332857

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

deprecate_partially_supported_callables

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2021/10/22 08:01		current
Line 2:		Line 2:
	* Date: 2021-09-02		* Date: 2021-09-02
	* Author: Nikita Popov <nikic@php.net>		* Author: Nikita Popov <nikic@php.net>
-	* Status: Accepted	+	* Status: Implemented
	* Target Version: PHP 8.2		* Target Version: PHP 8.2
	* Implementation: https://github.com/php/php-src/pull/7446		* Implementation: https://github.com/php/php-src/pull/7446

deprecate_ticks

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2021/06/10 13:19		current
Line 2:		Line 2:
	* Date: 2021-05-11		* Date: 2021-05-11
	* Author: Nikita Popov <nikic@php.net>		* Author: Nikita Popov <nikic@php.net>
-	* Status: Under Discussion	+	* Status: Withdrawn
	* Target Version: PHP 8.1		* Target Version: PHP 8.1
	* Implementation: https://github.com/php/php-src/pull/6967		* Implementation: https://github.com/php/php-src/pull/6967
		+	* Discussion: https://externals.io/message/114368

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

deprecate-backtick-operator

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2018/02/11 20:19		current
Line 15:		Line 15:
	===== Proposal =====		===== Proposal =====

-	This RFC proposes to deprecate (E_DEPRECATED) it in PHP 7.3 and suggest to use ''shell_exec()'' instead:	+	This RFC proposes to deprecate (by triggering one among E_DEPRECATED, E_STRICT or E_NOTICE) it in PHP 7.3 and suggest to use ''shell_exec()'' instead:

	* in case PHP decided in future to use backtick enclosed strings for Unicode strings		* in case PHP decided in future to use backtick enclosed strings for Unicode strings

deprecate-png-jpeg-2wbmp

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2017/09/22 13:28		current
Line 54:		Line 54:
	- PR #2164 has been merged into master (what is supposed to become PHP-7.2) with https://github.com/php/php-src/commit/189bbb58		- PR #2164 has been merged into master (what is supposed to become PHP-7.2) with https://github.com/php/php-src/commit/189bbb58
	- The deprecation and removal has been documented with http://svn.php.net/viewvc?view=revision&revision=341003		- The deprecation and removal has been documented with http://svn.php.net/viewvc?view=revision&revision=341003
		+	- [[http://git.php.net/?p=php-src.git;a=commit;h=e9736638828f3037b1b04fc02718d8d04351f9e0\|Removed for PHP 8]]
	- The language specification is not affected by this RFC		- The language specification is not affected by this RFC

disallow-multiple-constructor-calls

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2017/09/22 13:28		current
Line 3:		Line 3:
	* Date: 2017-01-17		* Date: 2017-01-17
	* Author: Richard Fussenegger <php@fleshgrinder.com>, Tim Behashvyly <tim.bezhashvyly@gmail.com>		* Author: Richard Fussenegger <php@fleshgrinder.com>, Tim Behashvyly <tim.bezhashvyly@gmail.com>
-	* Status: Draft	+	* Status: Inactive
	* First Published at: https://wiki.php.net/rfc/disallow-multiple-constructor-calls		* First Published at: https://wiki.php.net/rfc/disallow-multiple-constructor-calls

display_error_function_args

Anonymous (anonymous@undisclosed.example.com) — 2026-05-15T21:08:54+00:00

2026/05/02 18:09		current
Line 3:		Line 3:
	* Date: 2026-03-09		* Date: 2026-03-09
	* Author: Calvin Buckley, calvinb@php.net		* Author: Calvin Buckley, calvinb@php.net
-	* Status: Voting	+	* Status: Approved
	* Implementation: https://github.com/php/php-src/pull/12276		* Implementation: https://github.com/php/php-src/pull/12276

domdocument_html5_parser

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2024/08/05 20:18		current
Line 8:		Line 8:

	===== Introduction =====		===== Introduction =====
		+
		+	Important: parts of this RFC were further enhanced by https://wiki.php.net/rfc/opt_in_dom_spec_compliance

	PHP's DOM extension supports loading HTML documents using the methods <php>\DOMDocument::loadHTML</php> and <php>\DOMDocument::loadHTMLFile</php>.		PHP's DOM extension supports loading HTML documents using the methods <php>\DOMDocument::loadHTML</php> and <php>\DOMDocument::loadHTMLFile</php>.

errors_as_exceptions

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2011/04/06 10:59		current
Line 3:		Line 3:
	* Date: 2009-07-24		* Date: 2009-07-24
	* Author: Ben Scholzen <mail@dasprids.de>		* Author: Ben Scholzen <mail@dasprids.de>
-	* Status: Under Discussion	+	* Status: Inactive
	* First Published at: http://wiki.php.net/rfc/errors_as_exceptions		* First Published at: http://wiki.php.net/rfc/errors_as_exceptions

exit-as-function

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2024/08/13 11:33		current
Line 4:		Line 4:
	* Date: 2024-05-05		* Date: 2024-05-05
	* Author: Gina Peter Banyard <girgias@php.net>		* Author: Gina Peter Banyard <girgias@php.net>
-	* Status: Pending	+	* Status: Implemented
	* Target Version: PHP 8.4		* Target Version: PHP 8.4
	* Implementation: <https://github.com/php/php-src/pull/13483>		* Implementation: <https://github.com/php/php-src/pull/13483>

explicit_send_by_ref

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2020/02/21 11:42		current
Line 4:		Line 4:
	* Proposed for: PHP 8.0		* Proposed for: PHP 8.0
	* Implementation: https://github.com/php/php-src/pull/2958		* Implementation: https://github.com/php/php-src/pull/2958
-	* Status: Under Discussion	+	* Status: Inactive

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

explicit_this_parameter

Anonymous (anonymous@undisclosed.example.com) — 2026-04-07T15:29:25+00:00

2026/04/05 19:06		current
Line 43:		Line 43:
	We propose allowing a named argument <php>this:</php> to be combined with the “scope resolution operator” syntax of referring to a method to be used as an alternative way of calling an instance method. The value passed to the <php>this:</php> argument will effectively be used as the left side of the <php>-></php> operator.		We propose allowing a named argument <php>this:</php> to be combined with the “scope resolution operator” syntax of referring to a method to be used as an alternative way of calling an instance method. The value passed to the <php>this:</php> argument will effectively be used as the left side of the <php>-></php> operator.

-	Since the <php>this:</php> argument does not refer to a parameter in the underlying argument list and thus there is no ambiguity with regard to positional arguments it may be placed at any position of the argument list. In particular it may appear at the first position, before all positional arguments, mirroring the left-most position for a regular method call.	+	Since the <php>this:</php> argument does not refer to a parameter in the underlying parameter list and thus there is no ambiguity with regard to positional arguments it may be placed at any position of the argument list. In particular it may appear at the first position, before all positional arguments, mirroring the left-most position for a regular method call.

	<PHP>		<PHP>

function_alias

Anonymous (anonymous@undisclosed.example.com) — 2025-07-24T07:09:40+00:00

2026/05/19 10:05	current
Line 1:	Line 1:
	+	====== PHP RFC: Function Alias for class methods declaration ======
	+	* Version: 1
	+	* Date: 2025-07-24
	+	* Author: Dmitrii Derepko, xepozzd@gmail.com
	+	* Status: Draft (Later in the RFC process "Under Discussion", "Voting", and finally "Accepted", "Declined" or "Implemented")
	+	* Implementation: https://github.com/...

	+	===== Introduction =====
	+
	+	Modern languages use short constructions to boost developer experience. PHP as a modern language should follow in steps as well and re-use best practices of the others. I would like to make the <php>fn</php> keyword available to declare class methods.
	+
	+	Modern languages, such as Kotlin, Rust, Python use short function declaration keywords such as <php>fn</php>, <php>fun</php>, <php>def</php>.
	+
	+	PHP uses <php>function</php> which is 4x longer that <php>fn</php>, which is already in use in other parts of the language, such as closures.
	+
	+
	+	===== Proposal =====
	+
	+	Make <php>fn</php> keyword fully aliased for class methods:
	+
	+
	+	<PHP>
	+	<?php
	+
	+	class A {
	+	fn main() { // "fn" instead "function"
	+	echo "main function";
	+	}
	+
	+	fn __construct() { // constructor's function can be changed as well
	+	echo "__construct function";
	+	}
	+
	+	function __destruct() { // classic "function" is still available
	+	echo "__destruct function";
	+	}
	+	}
	+
	+	?>
	+	</PHP>
	+
	+	This is fully equivalent to
	+
	+	<PHP>
	+	<?php
	+
	+	class A {
	+	function __construct() {
	+	echo "__construct function";
	+	}
	+
	+	function main() {
	+	echo "main function";
	+	}
	+
	+	function __destruct() {
	+	echo "__destruct function";
	+	}
	+	}
	+
	+	?>
	+	</PHP>
	+
	+	==== Examples ====
	+	Remember that the RFC contents should be easily reusable in the PHP Documentation. This means, if at all possible, they should be runnable as standalone, self-contained code with the proof-of-concept implementation.
	+
	+	Simple example:
	+	<PHP>
	+	<?php
	+
	+	class A {
	+	fn main() { // all methods are public by default
	+	echo "main function";
	+	}
	+
	+	public fn main() {
	+	echo "main function";
	+	}
	+
	+	protected fn main() {
	+	echo "main function";
	+	}
	+
	+	private fn main() {
	+	echo "main function";
	+	}
	+
	+	abstract fn main();
	+	}
	+	?>
	+	</PHP>
	+
	+	Example showing an edge case:
	+	<PHP>
	+	<?php
	+
	+	echo "Edge case";
	+
	+	?>
	+	</PHP>
	+
	+	===== Backward Incompatible Changes =====
	+
	+	- Breaks backward compatibility because of new syntax construction.
	+
	+	===== Proposed PHP Version(s) =====
	+
	+	PHP 9.0
	+
	+	===== RFC Impact =====
	+	==== To the Ecosystem ====
	+	What effect will the RFC have on IDEs, Language Servers (LSPs), Static Analyzers, Auto-Formatters, Linters and commonly used userland PHP libraries?
	+
	+	==== To Existing Extensions ====
	+	Will existing extensions be affected?
	+
	+	==== To SAPIs ====
	+	Describe the impact to CLI, Development web server, embedded PHP etc.
	+
	+	===== Open Issues =====
	+	Make sure there are no open issues when the vote starts!
	+
	+	===== Future Scope =====
	+
	+	- [RFC] Function Alias for function declaration
	+
	+	Modern languages provide developers simple ways to define most popular constructions, such as short constructors, short functions, omitting mindless keywords and etc.
	+
	+	This RFC make PHP a step closer to a modern PHP look:
	+
	+
	+	<PHP>
	+	<?php
	+
	+	class MyService(private AnotherService $service): AbstractService(prefix: 'my') {
	+	fn getApiVersion() => 1;
	+
	+	fn doProxy() {
	+	return $this->service->main();
	+	}
	+	}
	+
	+	?>
	+	</PHP>
	+
	+	Instead, classic syntax is still available and much verbose:
	+
	+	<PHP>
	+	<?php
	+
	+	class MyService extends AbstractService {
	+	function __construct(private AnotherService $service) {
	+	parent::__construct(prefix: 'my');
	+	}
	+
	+	function getApiVersion() {
	+	return 1;
	+	}
	+
	+	function doProxy() {
	+	return $this->service->main();
	+	}
	+	}
	+
	+	?>
	+	</PHP>
	+
	+	This examples uses short constructor RFC syntax, single expression function syntax and have function -> fn alias
	+
	+
	+	===== Question / Answer =====
	+
	+	==== Should be "function" deprecated? ====
	+
	+	Yes, it should, but with no deprecation warning. Modern codebase will use short syntax (on demand), old projects/libraries won't be re-writed, so classic "functions" should live longer.
	+
	+	==== Will single function declaration be affected as well? ====
	+
	+	Yes, in another RFC.
	+
	+
	+	==== Can I use both <php>fn</php> and <php>function</php> keywords in the same class? ====
	+
	+	Yes, as you wish:
	+
	+	<PHP>
	+	<?php
	+
	+	class A {
	+	fn get() {...}
	+	function set($value) {...}
	+	}
	+	</PHP>
	+
	+	As it's fully-alised it can be replaced vise-versa. The reason to use it so is up to you.
	+
	+
	+	===== Voting Choices =====
	+	Pick a title that reflects the concrete choice people will vote on.
	+
	+	Please consult [[https://github.com/php/policies/blob/main/feature-proposals.rst#voting\|the php/policies repository]] for the current voting guidelines.
	+
	+	<doodle title="Implement $feature as outlined in the RFC?" voteType="single" closed="true" closeon="2025-01-01T15:30:00Z">
	+	* Yes
	+	* No
	+	</doodle>
	+
	+	===== Patches and Tests =====
	+	Links to proof of concept PR.
	+
	+	If there is no patch, make it clear who will create a patch, or whether a volunteer to help with implementation is needed.
	+
	+	===== Implementation =====
	+	After the RFC is implemented, this section should contain:
	+	- the version(s) it was merged into
	+	- a link to the git commit(s)
	+	- a link to the PHP manual entry for the feature
	+
	+	===== References =====
	+	Links to external references, discussions, or RFCs.
	+
	+	===== Rejected Features =====
	+	Keep this updated with features that were discussed on the mail lists.
	+
	+	===== Changelog =====
	+	If there are major changes to the initial proposal, please include a short summary with a date or a link to the mailing list announcement here, as not everyone has access to the wikis' version history.

get_declared_enums

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2024/08/20 08:02		current
Line 3:		Line 3:
	* Date: 2024-08-19		* Date: 2024-08-19
	* Author: Juliette Reinders Folmer (<php.net_nospam@adviesenzo.nl>), Ayesh Karunaratne (<ayesh@php.watch>)		* Author: Juliette Reinders Folmer (<php.net_nospam@adviesenzo.nl>), Ayesh Karunaratne (<ayesh@php.watch>)
-	* Status: Draft	+	* Status: Under Discussion
	* Implementation: https://github.com/php/php-src/pull/15443		* Implementation: https://github.com/php/php-src/pull/15443
	* First Published at: http://wiki.php.net/rfc/get_declared_enums		* First Published at: http://wiki.php.net/rfc/get_declared_enums

http-last-response-headers

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2024/02/14 14:09		current
Line 4:		Line 4:
	* Date: 2024-01-03		* Date: 2024-01-03
	* Author: Gina Peter Banyard <girgias@php.net>		* Author: Gina Peter Banyard <girgias@php.net>
-	* Status: Pending Implementation	+	* Status: Implemented in PHP 8.4: https://github.com/php/php-src/commit/47a199c8b43dbf84e66ff6b63f665541ab4eb1d0
	* Target Version: PHP 8.4		* Target Version: PHP 8.4
	* Implementation: [[https://github.com/php/php-src/pull/12500\|https://github.com/php/php-src/pull/12500]]		* Implementation: [[https://github.com/php/php-src/pull/12500\|https://github.com/php/php-src/pull/12500]]

image2wbmp

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2018/06/09 22:37		current
Line 61:		Line 61:
	- Implemented in PHP 7.3 via [[http://git.php.net/?p=php-src.git;a=commit;h=3cbf594dfd0708dc36f1655c50e16fa963e61501]]		- Implemented in PHP 7.3 via [[http://git.php.net/?p=php-src.git;a=commit;h=3cbf594dfd0708dc36f1655c50e16fa963e61501]]
	- [[http://php.net/manual/en/function.image2wbmp.php\|doc]] [[http://svn.php.net/viewvc?view=revision&revision=345112\|fix]]		- [[http://php.net/manual/en/function.image2wbmp.php\|doc]] [[http://svn.php.net/viewvc?view=revision&revision=345112\|fix]]
		+	- [[http://git.php.net/?p=php-src.git;a=commit;h=dfa6c2046a8d7b66c4be52e46888f0fefccbcfd4\|Removed for PHP 8]]

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

improved-tls-constants

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2017/06/05 09:08		current
Line 3:		Line 3:
	* Date: 2017-05-15		* Date: 2017-05-15
	* Author: Niklas Keller, me@kelunik.com		* Author: Niklas Keller, me@kelunik.com
-	* Status: Accepted	+	* Status: Merged to 7.2
	* First Published at: http://wiki.php.net/rfc/improved-tls-constants		* First Published at: http://wiki.php.net/rfc/improved-tls-constants

Line 36:		Line 36:
	===== Patches and Tests =====		===== Patches and Tests =====
	* https://github.com/php/php-src/pull/2518		* https://github.com/php/php-src/pull/2518
		+	* https://github.com/php/php-src/commit/bec91e1117fd3527897cde2f8a26eab9a20fa3dc

	===== References =====		===== References =====
	* https://externals.io/thread/864		* https://externals.io/thread/864

iterable_to_array-and-iterable_count

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2018/07/03 22:40		current
Line 3:		Line 3:
	* Date: 2018-06-19		* Date: 2018-06-19
	* Author: Michael Moravec (php.net@majkl578.cz)		* Author: Michael Moravec (php.net@majkl578.cz)
-	* Status: Voting	+	* Status: Declined
	* First Published at: https://wiki.php.net/rfc/iterable_to_array-and-iterable_count		* First Published at: https://wiki.php.net/rfc/iterable_to_array-and-iterable_count

Line 92:		Line 92:
	Voting starts on 2018-07-03 20:30 UTC and closes on 2018-07-16 23:00 UTC.		Voting starts on 2018-07-03 20:30 UTC and closes on 2018-07-16 23:00 UTC.

-	<doodle title="Add iterable_to_array()?" auth="majkl" voteType="single" closed="false">	+	<doodle title="Add iterable_to_array()?" auth="majkl" voteType="single" closed="true">
	* Yes		* Yes
	* No		* No
	</doodle>		</doodle>
	.		.
-	<doodle title="Add iterable_count()?" auth="majkl" voteType="single" closed="false">	+	<doodle title="Add iterable_count()?" auth="majkl" voteType="single" closed="true">
	* Yes		* Yes
	* No		* No

kill_real

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2015/10/26 10:02		current
Line 2:		Line 2:
	* Version: 1.0		* Version: 1.0
	* Date: 2015-10-26		* Date: 2015-10-26
-	* Author: YKalle Sommer Nielsen <kalle@php.net>	+	* Author: Kalle Sommer Nielsen <kalle@php.net>
	* Status: Draft		* Status: Draft
	* First Published at: http://wiki.php.net/rfc/kill_real		* First Published at: http://wiki.php.net/rfc/kill_real

ldap_controls

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2017/07/13 09:01		current
Line 1:		Line 1:
-	====== PHP RFC: Your Title Here ======	+	====== PHP RFC: LDAP controls ======
	* Version: 0.1		* Version: 0.1
	* Date: 2017-07-13		* Date: 2017-07-13
Line 13:		Line 13:

	===== Proposal =====		===== Proposal =====
-	All the features and examples of the proposal.	+	In the actual state, controls can be set or get with ldap_get_option and ldap_set_option, in which case they are represented by associative arrays like this:
		+	<code php>
		+	array(
		+	'oid' => <string>,
		+	'iscritical' => <boolean>,
		+	'value' => <ber encoded value>
		+	)
		+	</code>
		+	The value is directly the ber encoded value, and PHP provides no easy way to encode/decode ber encoding directly.
		+
		+	The other way controls can be used is through ldap_control_paged_results/ldap_control_paged_result_response for the control for paged results.

	===== Backward Incompatible Changes =====		===== Backward Incompatible Changes =====

locale_independent_float_to_string

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2020/05/07 12:39		current
Line 4:		Line 4:
	* Author: George Peter Banyard <girgias@php.net>, Máté Kocsis <kocsismate@php.net>		* Author: George Peter Banyard <girgias@php.net>, Máté Kocsis <kocsismate@php.net>
	* Target Version: PHP 8.0		* Target Version: PHP 8.0
-	* Status: Accepted	+	* Status: Implemented
	* Implementation: https://github.com/php/php-src/pull/5224		* Implementation: https://github.com/php/php-src/pull/5224

make_ctor_ret_void

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2020/07/22 15:29		current
Line 1:		Line 1:
	====== PHP RFC: Make constructors and destructors return void ======		====== PHP RFC: Make constructors and destructors return void ======
	* Date: 2020-06-17		* Date: 2020-06-17
-	* Author: Benas Seliuginas, <benas.molis.iml@gmail.com>	+	* Author: Benas Seliuginas, <benas.molis@gmail.com>
	* Target version: PHP 8.0		* Target version: PHP 8.0
	* Status: Declined		* Status: Declined

mysqli_execute_parameters

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2020/12/26 11:16		current
Line 15:		Line 15:
	Using parameterised queries with //mysqli// is too complicated:		Using parameterised queries with //mysqli// is too complicated:

-	$db = new mysqli('localhost', 'test', 'test', 'test');	+	<code php>
		+	$db = new mysqli('localhost', 'test', 'test', 'test');

-	$sql = 'SELECT * FROM user WHERE name LIKE ? AND type = ?';	+	$sql = 'SELECT * FROM user WHERE name LIKE ? AND type = ?';
-		+
-	$name = '%a%';	+	$name = '%a%';
-	$type = 'admin';	+	$type = 'admin';
-		+
-	$statement = $db->prepare($sql);	+	$statement = $db->prepare($sql);
-	$statement->bind_param('ss', $name, $type);	+	$statement->bind_param('ss', $name, $type);
-	$statement->execute();	+	$statement->execute();
-		+
-	$result = $statement->get_result();	+	$result = $statement->get_result();
-		+
-	while ($row = $result->fetch_assoc()) {	+	while ($row = $result->fetch_assoc()) {
-	print_r($row);	+	print_r($row);
-	}	+	}
		+	</code>

	Note that variables need to be used in //bind_param()//, because values cannot be passed by reference.		Note that variables need to be used in //bind_param()//, because values cannot be passed by reference.
Line 42:		Line 44:
	Introduce //mysqli::execute//() (and replace the deprecated //mysqli_execute()// function) to make parameterised queries much easier, e.g.		Introduce //mysqli::execute//() (and replace the deprecated //mysqli_execute()// function) to make parameterised queries much easier, e.g.

-	$sql = 'SELECT * FROM user WHERE name LIKE ? AND type = ?';	+	<code php>
-		+	$sql = 'SELECT * FROM user WHERE name LIKE ? AND type = ?';
-	$parameters = ['%a%', 'admin'];	+
-		+	$parameters = ['%a%', 'admin'];
-	$result = $db->execute($sql, $parameters);	+
-		+	$result = $db->execute($sql, $parameters);
-	while ($row = $result->fetch_assoc()) {	+
-	print_r($row);	+	while ($row = $result->fetch_assoc()) {
-	}	+	print_r($row);
		+	}
		+	</code>

	We probably cannot change //mysqli::query()// because it's second argument is //$resultmode//.		We probably cannot change //mysqli::query()// because it's second argument is //$resultmode//.
Line 58:		Line 62:
	Something like this:		Something like this:

-	class mysqli_rfc extends mysqli {	+	<code php>
-		+	<?php
-	function execute($sql, $parameters = []) {	+
-		+	class mysqli_rfc extends mysqli {
		+	function execute($sql, $parameters = []) {
	$statement = mysqli_prepare($this, $sql);		$statement = mysqli_prepare($this, $sql);
-		+
	$ref_types = '';		$ref_types = '';
	foreach ($parameters as $key => $value) {		foreach ($parameters as $key => $value) {
-	$ref_types .= (is_int($value) ? 'i' : 's'); // 'd' for double, or 'b' for blob.	+	$ref_types .= (is_int($value) ? 'i' : 's'); // 'd' for double, or 'b' for blob.
-	$ref_values[] = &$parameters[$key];	+	$ref_values[] = &$parameters[$key];
	}		}
-		+
	array_unshift($ref_values, $ref_types);		array_unshift($ref_values, $ref_types);
-		+
	call_user_func_array([$statement, 'bind_param'], $ref_values);		call_user_func_array([$statement, 'bind_param'], $ref_values);
-		+
	$statement->execute();		$statement->execute();
-		+
	return $statement->get_result();		return $statement->get_result();
-
-	}
-
	}		}
		+	}
		+	</code>

	Where //$sql// should be a [[https://wiki.php.net/rfc/is_literal\|safe literal string]].		Where //$sql// should be a [[https://wiki.php.net/rfc/is_literal\|safe literal string]].

mysqli_execute_query

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2022/05/25 19:18		current
Line 8:		Line 8:
	* Author: Kamil Tekiela, and Craig Francis [craig#at#craigfrancis.co.uk]		* Author: Kamil Tekiela, and Craig Francis [craig#at#craigfrancis.co.uk]
	* Status: Accepted		* Status: Accepted
		+	* Target Version: PHP 8.2
	* First Published at: https://wiki.php.net/rfc/mysqli_execute_query		* First Published at: https://wiki.php.net/rfc/mysqli_execute_query
	* GitHub Repo: https://github.com/craigfrancis/php-mysqli-execute-query-rfc		* GitHub Repo: https://github.com/craigfrancis/php-mysqli-execute-query-rfc

mysqlnd_localhost_override

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2013/02/12 11:33		current
Line 1:		Line 1:
	====== Add mysqlnd.localhost_override option ======		====== Add mysqlnd.localhost_override option ======
-	* Version: 0.1	+	* Version: 0.2
	* Date: 2013-02-12		* Date: 2013-02-12
	* Author: Asbjørn Sannes <asbjorn.sannes.at.interhost.no>		* Author: Asbjørn Sannes <asbjorn.sannes.at.interhost.no>
-	* Status: In Draft	+	* Status: Widthdrawn
	* First Published at: https://wiki.php.net/rfc/mysqlnd_localhost_override		* First Published at: https://wiki.php.net/rfc/mysqlnd_localhost_override

		+	===== Withdrawn =====
		+
		+	There are methods to work around this:
		+
		+	* write a mysqlnd plugin (Johannes Schlüter)
		+	* PDO already support DSN-alias, php.net/pdo.configuration#ini.pdo.dsn (Sebastian Krebs)

	===== Introduction =====		===== Introduction =====
Line 38:		Line 44:

	0.1 Initial draft		0.1 Initial draft
		+	0.2 Withdrawn

native_regular_expressions

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2014/08/15 13:34		current
Line 1:		Line 1:
	====== PHP RFC: Native Regular Expression ======		====== PHP RFC: Native Regular Expression ======
-	* Version: 0.1
	* Date: 2014-08-13		* Date: 2014-08-13
	* Author: Bishop Bettini, bishop@php.net		* Author: Bishop Bettini, bishop@php.net
	* Status: Draft		* Status: Draft
-	* First Published at: http://wiki.php.net/rfc/native_regular_expressions

	FIXME FIXME FIXME		FIXME FIXME FIXME
	Jotting my ideas down here. Move along. Maybe called "first_class_citizens_regex" or something.		Jotting my ideas down here. Move along. Maybe called "first_class_citizens_regex" or something.
		+	Consider emulating structure of https://wiki.php.net/rfc/abstract_syntax_tree
		+	https://wiki.php.net/rfc/generators
		+
		+
		+	===== Introduction =====
		+
		+	Regular expressions provide powerful string matching capabilities and play a critical role in most software written in PHP. For example, Github reports [[https://github.com/search?q=language%3Aphp+preg_filter+OR+preg_grep+OR+preg_match+OR+preg_match_all+OR+preg_replace+OR+preg_split&type=Code\|10.5 million instances of the ''preg_*()'' family of functions]]((Compared with [[https://github.com/search?q=language%3Aphp+str_replace+OR+explode+OR+strpos&type=Code\|16 million instances]] of the ''explode()'', ''strpos()'', and ''str_replace()'' related functions.))((This RFC does not consider the deprecated POSIX regular expressions to be an active part of PHP and any implementation of this RFC will focus solely upon PCRE regular expressions.)).
		+
		+	In the current engine, regular expressions are plain old strings:
		+
		+	<code php>
		+	while (preg_match('/^\s*[^#]/', $line[$i++])) {}
		+	</code>
		+
		+	The primary disadvantage with string representation comes when the regular expression itself needs to contain a single quote, double quote, or the delimiters bracketing the regular expression. When that happens, the programmer has to make mental shifts to workaround the string representation, sometimes making the regular expression harder to read and maintain. Example:
		+
		+	<code php>
		+	// match foo in examples: ="foo" and ='foo' and = "foo"
		+	preg_match_all('(=\s['."'".'"]([^'."'".'"/])['."'".'"])x', $string, $matches);
		+	</code>((PCRE wizards might rightly scold me for using that example, as it doesn't actually work as described for unbalanced quotation marks or escaped quotation marks, and that a realistic working example would be ''(["'])(?:\\?+.)*?\1'', thus needing only one single quote escaped. I agree, but I generated this example to illustrate a point.))
		+
		+	In some other languages, regular expressions are part of the language itself.
		+
		+
		+
		+
		+	Another problem with regular expressions buried in plain old strings is that syntax highlighting becomes much more difficult.
		+
		+
		+	<code php>
		+	function getLinesFromFile($fileName) {
		+	if (!$fileHandle = fopen($fileName, 'r')) {
		+	return;
		+	}
		+
		+	while (false !== $line = fgets($fileHandle)) {
		+	yield $line;
		+	}
		+
		+	fclose($fileHandle);
		+	}
		+
		+	$lines = getLinesFromFile($fileName);
		+	foreach ($lines as $line) {
		+	// do something with $line
		+	}
		+	</code>
		+
		+	The code looks very similar to the array-based implementation. The main difference is that instead of pushing
		+	values into an array the values are ''yield''ed.
		+
		+	Generators work by passing control back and forth between the generator and the calling code:
		+
		+	When you first call the generator function (''$lines = getLinesFromFile($fileName)'') the passed argument is bound,
		+	but nothing of the code is actually executed. Instead the function directly returns a ''Generator'' object. That
		+	''Generator'' object implements the ''Iterator'' interface and is what is eventually traversed by the ''foreach''
		+	loop:
		+
		+	Whenever the ''Iterator::next()'' method is called PHP resumes the execution of the generator function until it
		+	hits a ''yield'' expression. The value of that ''yield'' expression is what ''Iterator::current()'' then returns.
		+
		+	Generator methods, together with the ''IteratorAggregate'' interface, can be used to easily implement traversable
		+	classes too:
		+
		+	<code php>
		+	class Test implements IteratorAggregate {
		+	protected $data;
		+
		+	public function __construct(array $data) {
		+	$this->data = $data;
		+	}
		+
		+	public function getIterator() {
		+	foreach ($this->data as $key => $value) {
		+	yield $key => $value;
		+	}
		+	// or whatever other traversation logic the class has
		+	}
		+	}
		+
		+	$test = new Test(['foo' => 'bar', 'bar' => 'foo']);
		+	foreach ($test as $k => $v) {
		+	echo $k, ' => ', $v, "\n";
		+	}
		+	</code>
		+
		+	Generators can also be used the other way around, i.e. instead of producing values they can also consume them. When
		+	used in this way they are often referred to as enhanced generators, reverse generators or coroutines.
		+
		+	Coroutines are a rather advanced concept, so it very hard to come up with not too contrived an short examples.
		+	For an introduction see an example [[https://gist.github.com/3111288\|on how to parse streaming XML using coroutines]].
		+	If you want to know more, I highly recommend checking out [[http://www.dabeaz.com/coroutines/Coroutines.pdf\|a presentation
		+	on this subject]].
		+
		+
		+
		+
		+

	New built-in "re". BNF is roughly:		New built-in "re". BNF is roughly:

new_rounding_modes_to_round_function

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2024/11/04 21:47		current
Line 17:		Line 17:


-	> Note: The aforementioned have been transformed into an enum in a [[https://wiki.php.net/rfc/correctly_name_the_rounding_mode_and_make_it_an_enum\|follow-up RFC]].	+	> Note: The aforementioned constants have been transformed into an enum in a [[https://wiki.php.net/rfc/correctly_name_the_rounding_mode_and_make_it_an_enum\|follow-up RFC]].

	Two first comments on the [[https://www.php.net/manual/en/function.round.php\|documentation page of the round()]] function are related to the missing modes of rounding. The first comment has an outstanding number of 309 votes.		Two first comments on the [[https://www.php.net/manual/en/function.round.php\|documentation page of the round()]] function are related to the missing modes of rounding. The first comment has an outstanding number of 309 votes.

non_coercing_array_keys_in_strict_mode

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2017/07/27 22:30		current
Line 8:		Line 8:
	===== Proposal =====		===== Proposal =====

-	This RFC proposes to emit a strict standards deprecation notice when PHP would coerce array keys' types (e.g. float to int), in case the page is declared using ''strict_types''.	+	This RFC proposes to emit a strict-standards deprecation notice when PHP would coerce array keys' types (e.g. float to int), in case the page uses ''strict_types = 1''.

	For example:		For example:
Line 15:		Line 15:
	<?php declare(strict_types = 1);		<?php declare(strict_types = 1);
	$array = [];		$array = [];
-	$array[42.42] = 123; // Deprecated / Strict Standards: invalid key float(42.42), assuming int(42)	+	$array[42.42] = 123;
		+	// 7.3+ Deprecated / Strict Standards: invalid key float(42.42), assuming int(42)
		+	// 8.0+ TypeError invalid array key type "float", expecting int or string
	</code>		</code>

Line 22:		Line 24:

	===== Impact on generics =====		===== Impact on generics =====
-	This proposal is friends with generics, as this change won't directly influence future decisions about generics.	+	This proposal is friends with generics, as this change won't directly influence future decisions about them.

	For example, arrays could be declared as ''Array<KT, CT> where KT is mixed and CT is mixed'' thus allowing any key type to be used.		For example, arrays could be declared as ''Array<KT, CT> where KT is mixed and CT is mixed'' thus allowing any key type to be used.

-	However in non-strict, people will continue to rely on coercion of keys, so when type arguments are not specified, the array "constructors" should continue to default to ''<int\|string, mixed>''.	+	However in non-strict, people will continue to rely on coercion of keys, so when type arguments are not specified, the array "constructors" could continue to default to ''<int\|string, mixed>''.

	<code php>		<code php>

normalize_inc_dec

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2017/09/22 13:28		current
Line 4:		Line 4:
	* Date: 2013-12-19		* Date: 2013-12-19
	* Author: Tjerk Meesters (datibbaw)		* Author: Tjerk Meesters (datibbaw)
-	* Status: Abandoned	+	* Status: Inactive
	* First Published at: https://wiki.php.net/rfc/normalize_inc_dec		* First Published at: https://wiki.php.net/rfc/normalize_inc_dec

not_serializable_attribute

Anonymous (anonymous@undisclosed.example.com) — 2025-10-13T23:16:48+00:00

2025/10/13 23:00		current
Line 127:		Line 127:

	===== Backward Incompatible Changes =====		===== Backward Incompatible Changes =====
-	NotSerializable can no longer be used as a class name in the global namespace. A GitHub search for “class NotSerializable ” language:php revealed a total of 3 matches in source code. One of them is in the php-src tests.	+	The NotSerializable class name can no longer be used in the global namespace. A GitHub search for “class NotSerializable ” language:php revealed a total of 28 matches in source code. Almost all of them are in the tests.

	===== Proposed PHP Version(s) =====		===== Proposed PHP Version(s) =====
-	PHP 8.6 (or the next minor). The change is isolated and low risk.	+	PHP 8.6

	===== RFC Impact =====		===== RFC Impact =====

nullable-casting

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2019/04/09 05:54		current
Line 175:		Line 175:

	* Working prototype: https://github.com/php/php-src/pull/3764		* Working prototype: https://github.com/php/php-src/pull/3764
		+
		+	===== Discussion =====
		+
		+	==== "Not 100% needed" ====
		+
		+	Current alternatives:
		+	* Use a test (ternary conditional operator or ''if'' statement), possibly with a temporary variable
		+	* Write (and [auto]load) custom casting functions
		+	* Disable (i.e. do not enable) strict typing mode in the concerned file //(not strictly equivalent, e.g. for ''%%"foo"%%'' to ''int'')//
		+
		+	==== "A cast where you can't be sure of what you'll get back" ====
		+
		+	"I understand the use-case for when you want to pass something to a nullable parameter, but if you think about this cast in isolation, it hardly makes sense."
		+
		+	==== "What about e.g. nullable_intval()?" ====
		+
		+	But we're missing "arrayval()" and "objectval()"... And we might use short closure ''%%fn($x) => (?int)$x%%''
		+
		+	==== Fallible Casting ====
		+
		+	One might expect to also have e.g. ''%%(?int)"foo"%%'' and ''%%(?int)""%%'' give ''null'' rather than ''0'', ''(?string)[42]'' give ''null'' rather than ''%%"Array"%%''... and to be able to use ''(?int)$value ?? $default'', ''%%(?string)$_GET["input"] ?? ""%%''...
		+
		+	==== Alternative syntax ====
		+
		+	E.g. "''(null\|int) $x''"

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

object_cast_magic

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2012/03/04 01:02		current
Line 3:		Line 3:
	* Date: 2012-02-28		* Date: 2012-02-28
	* Author: Anthony Ferrara <ircmaxell@php.net>		* Author: Anthony Ferrara <ircmaxell@php.net>
-	* Status: In Draft	+	* Status: Withdrawn
		+
		+	Note that this RFC has been withdrawn in favor of the updated https://wiki.php.net/rfc/object_cast_to_types RFC (due to feedback from several developers).

	===== Introduction =====		===== Introduction =====
Line 116:		Line 118:

	===== Questions =====		===== Questions =====
-	How would this RFC affect:
-
-	resources
-
-	streams
-
-	filters
-
-	...

object-initializer

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2019/10/07 11:14		current
Line 3:		Line 3:
	* Date: 2019-09-03		* Date: 2019-09-03
	* Author: Michał Brzuchalski <brzuchal@php.net>		* Author: Michał Brzuchalski <brzuchal@php.net>
-	* Status: Voting	+	* Status: Declined
	* First Published at: http://wiki.php.net/rfc/object-initializer		* First Published at: http://wiki.php.net/rfc/object-initializer

Line 307:		Line 307:
	The vote is a straight Yes/No vote for accepting the RFC.		The vote is a straight Yes/No vote for accepting the RFC.

-	<doodle title="Accept object initializer?" auth="brzuchal" voteType="single" closed="false">	+	<doodle title="Accept object initializer?" auth="brzuchal" voteType="single" closed="true">
	* Yes		* Yes
	* No		* No
	</doodle>		</doodle>
	.		.
-	<doodle title="Choose between two tokens as an assign operator in object initializer block?" auth="brzuchal" voteType="single" closed="false">	+	<doodle title="Choose between two tokens as an assign operator in object initializer block?" auth="brzuchal" voteType="single" closed="true">
	* =		* =
	* =>		* =>

optin_block_scoping

Anonymous (anonymous@undisclosed.example.com) — 2026-02-05T10:31:01+00:00

2026/01/22 09:17		current
Line 4:		Line 4:
	* Date: 2025-09-08		* Date: 2025-09-08
	* Author: Seifeddine Gmati azjezz@carthage.software, Tim Düsterhus timwolla@php.net		* Author: Seifeddine Gmati azjezz@carthage.software, Tim Düsterhus timwolla@php.net
-	* Status: Voting	+	* Status: Declined
	* Implementation: https://github.com/php/php-src/compare/master...TimWolla:php-src:block-scope		* Implementation: https://github.com/php/php-src/compare/master...TimWolla:php-src:block-scope

Line 314:		Line 314:
	Primary Vote requiring a 2/3 majority to accept the RFC:		Primary Vote requiring a 2/3 majority to accept the RFC:

-	<doodle title="Add the let construct for block-scoping?" auth="azjezz" voteType="single" closed="false" closeon="2026-02-05T09:30:00Z">	+	<doodle title="Add the let construct for block-scoping?" auth="azjezz" voteType="single" closed="true" closeon="2026-02-05T09:30:00Z">
	* Yes		* Yes
	* No		* No

override_constants

Anonymous (anonymous@undisclosed.example.com) — 2026-05-08T02:03:13+00:00

2026/05/08 02:00		current
Line 23:		Line 23:

	* Public and protected constants of a parent class or implemented interface satisfy <php>#[\Override]</php>. Private constants do not satisfy the attribute.		* Public and protected constants of a parent class or implemented interface satisfy <php>#[\Override]</php>. Private constants do not satisfy the attribute.
-	* <php>#[\Override]</php> is ignored on traits, but constants from a used trait behave as if the property definition was copied and pasted into the target class. Specifically the <php>#[\Override]</php> attribute on a trait constant requires the existence of a matching constant in a parent class or implemented interface.	+	* <php>#[\Override]</php> is ignored on traits, but constants from a used trait behave as if the constant definition was copied and pasted into the target class. Specifically the <php>#[\Override]</php> attribute on a trait constant requires the existence of a matching constant in a parent class or implemented interface.
	* <php>#[\Override]</php> works as expected on anonymous classes.		* <php>#[\Override]</php> works as expected on anonymous classes.
	* <php>#[\Override]</php> works as expected on interfaces: a matching constant needs to exist in a parent interface.		* <php>#[\Override]</php> works as expected on interfaces: a matching constant needs to exist in a parent interface.

parse_str_alternative

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2021/08/06 19:37		current
Line 2:		Line 2:
	* Date: 2021-06-23		* Date: 2021-06-23
	* Author: Kamil Tekiela <dharman@php.net>		* Author: Kamil Tekiela <dharman@php.net>
-	* Status: Discussion	+	* Status: Withdrawn
	* Implementation: https://github.com/php/php-src/pull/7344		* Implementation: https://github.com/php/php-src/pull/7344
	* Target Version: PHP 8.2		* Target Version: PHP 8.2
Line 8:		Line 8:
	===== Introduction =====		===== Introduction =====

-	PHP offers a function for parsing query string into an array. The function historically has been a mockery as it allowed to register the values as global variables. Since PHP 8.0 this is no longer possible. The function still has two main downsides: a confusing name, and no return value (it returns by out parameter instead).	+	PHP offers a function for parsing query string into an array. The function, for historical reasons, has been designed to allow registering the values as global variables. Since PHP 8.0 this is no longer possible. The function still has two main downsides: a confusing name, and no return value (it returns by out parameter instead).

	<PHP>		<PHP>
Line 67:		Line 67:

	===== Discussion on internals ======		===== Discussion on internals ======
		+	https://externals.io/message/115546

partial_function_application_v2

Anonymous (anonymous@undisclosed.example.com) — 2026-02-11T00:02:13+00:00

2026/02/10 21:11		current
Line 761:		Line 761:
	==== Late Static Binding ====		==== Late Static Binding ====

-	Although not stated explicitly in the RFC, a partialed Closure inherits the scope in which it is created, just like any other closure (first-class or otherwise). That means, for instance, you can partial a private method and pass it somewhere, making it available to call from where it is passed.	+	Although not stated explicitly in the RFC, a partialed Closure inherits the scope in which it is created, just like any other closure (first-class or otherwise). Any dynamic keywords such as ''static'' are evaluated when the closure is created. That means, for instance, you can partial a private method and pass it somewhere, making it available to call from where it is passed.

-	Additionally, ''static'' and similar keywords will be evaluated properly at runtime. That is:	+	Put another way:

	<code php>		<code php>
Line 794:		Line 794:
	array(0) {		array(0) {
	}		}
		+
		+	// The static::m(?) call compiles to
		+
		+	fn(string $a) => ResolvedClass::m($a);
		+
		+	// For whatever the resolved class is at that point.
	</code>		</code>

	This is not a change in the RFC behavior, just clarifying what it was already doing.		This is not a change in the RFC behavior, just clarifying what it was already doing.

pdo_driver_specific_parsers

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2024/06/17 15:04		current
Line 3:		Line 3:
	* Date: 2024-04-11		* Date: 2024-04-11
	* Author: Matteo Beccati, mbeccati@php.net		* Author: Matteo Beccati, mbeccati@php.net
-	* Status: Accepted	+	* Status: Implemented
-	* Discussion: [[https://externals.io/message/123141]]	+	* Target Version: 8.4
		+	* Implementation: [[https://github.com/php/php-src/commit/fbe317bf2179c65b750cc945c3530b28db1670e0]]
	* First Published at: [[https://wiki.php.net/rfc/pdo_driver_specific_parsers]]		* First Published at: [[https://wiki.php.net/rfc/pdo_driver_specific_parsers]]
-	* Implementation: [[https://github.com/php/php-src/pull/14035]]

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

preg_replace_callback_array

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2015/03/21 08:04		current
Line 3:		Line 3:
	* Date: 2015-03-10		* Date: 2015-03-10
	* Author: Wei Dai, demon@php.net		* Author: Wei Dai, demon@php.net
-	* Status: Accepted	+	* Status: Implemented (in PHP 7.0)
	* First Published at: https://wiki.php.net/rfc/preg_replace_callback_array		* First Published at: https://wiki.php.net/rfc/preg_replace_callback_array

readonly_amendments

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2023/02/07 10:14		current
Line 2:		Line 2:
	* Date: 2022-10-24		* Date: 2022-10-24
	* Author: Nicolas Grekas <nicolasgrekas@php.net>, Máté Kocsis <kocsismate@php.net>		* Author: Nicolas Grekas <nicolasgrekas@php.net>, Máté Kocsis <kocsismate@php.net>
-	* Status: Accepted	+	* Status: Implemented
	* Target Version: PHP 8.3		* Target Version: PHP 8.3
	* Implementation: https://github.com/php/php-src/pull/9827 (proposal #1), https://github.com/php/php-src/pull/10389 (proposal #2)		* Implementation: https://github.com/php/php-src/pull/9827 (proposal #1), https://github.com/php/php-src/pull/10389 (proposal #2)

remove_preg_replace_eval_modifier

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2012/03/13 17:30		current
Line 104:		Line 104:
	===== Vote =====		===== Vote =====

-	<doodle	+	The vote ended with 23 in favor and 4 against the proposal.
-	title="Should the /e modifier be deprecated in trunk and removed at some later point in time?" auth="nikic" voteType="single">	+
-	* yes	+
-	* no	+
-	</doodle>	+

	===== Current state =====		===== Current state =====

remove_utf_8_decode_encode

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2022/02/20 18:52		current
Line 3:		Line 3:
	* Date: 2016-08-15		* Date: 2016-08-15
	* Author: Yasuo Ohgaki <yohgaki@ohgaki.net>		* Author: Yasuo Ohgaki <yohgaki@ohgaki.net>
-	* Status: Abandoned	+	* Status: Abandoned; succeeded by [[rfc:remove_utf8_decode_and_utf8_encode]]
	* First Published at: http://wiki.php.net/rfc/remove_utf_8_decode_encode		* First Published at: http://wiki.php.net/rfc/remove_utf_8_decode_encode

resource_to_object_conversion

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2024/05/24 12:09		current
Line 140:		Line 140:
	* dba: connection resource returned by ''dba_open()''		* dba: connection resource returned by ''dba_open()''
	* dba persistent: persistent connection resource returned by ''dba_popen()''		* dba persistent: persistent connection resource returned by ''dba_popen()''
-	* ODBC (implementation: https://github.com/php/php-src/pull/12040/)	+	* ODBC (implementation: https://github.com/php/php-src/pull/12040)
	* odbc link: connection resource returned by ''odbc_connect()''		* odbc link: connection resource returned by ''odbc_connect()''
	* odbc link persistent: persistent connection returned by ''odbc_pconnect()''		* odbc link persistent: persistent connection returned by ''odbc_pconnect()''
	* odbc result: result resources returned by various ''odbc_*'' functions		* odbc result: result resources returned by various ''odbc_*'' functions
-	* SOAP (implementation: https://github.com/php/php-src/pull/14121)	+	* SOAP (implementation: https://github.com/php/php-src/pull/14121, https://github.com/php/php-src/pull/14174)
	* SOAP SDL: ''SoapClient::$sdl''		* SOAP SDL: ''SoapClient::$sdl''
	* SOAP table: ''SoapClient::$typemap''		* SOAP table: ''SoapClient::$typemap''

rng_fixes

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2016/07/16 00:13		current
Line 3:		Line 3:
	* Date: 2016-05-03		* Date: 2016-05-03
	* Author: Leigh T <leigh@php.net>		* Author: Leigh T <leigh@php.net>
-	* Status: Accepted	+	* Status: Implemented (PHP 7.1)
	* First Published at: https://wiki.php.net/rfc/rng_fixes		* First Published at: https://wiki.php.net/rfc/rng_fixes

Line 120:		Line 120:
	===== Implementation =====		===== Implementation =====

		+	https://github.com/php/php-src/commit/ab834f4

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

sleep_function_float_support

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2024/03/05 09:37		current
Line 46:		Line 46:

	==== To SAPIs ====		==== To SAPIs ====
		+
	No impact on SAPIs is anticipated.		No impact on SAPIs is anticipated.

	==== To Existing Extensions ====		==== To Existing Extensions ====
		+
	No existing extensions are expected to be affected by this change.		No existing extensions are expected to be affected by this change.

	==== To Opcache ====		==== To Opcache ====
		+
	No impact on Opcache is anticipated.		No impact on Opcache is anticipated.

	==== New Constants ====		==== New Constants ====
		+
	No new constants will be introduced by this RFC.		No new constants will be introduced by this RFC.

	==== php.ini Defaults ====		==== php.ini Defaults ====
		+
	This RFC does not introduce or alter any php.ini settings.		This RFC does not introduce or alter any php.ini settings.

	===== Open Issues =====		===== Open Issues =====
		+
	There are no open issues related to this RFC.		There are no open issues related to this RFC.

	===== Proposed Voting Choices =====		===== Proposed Voting Choices =====

-	The voting will be organized into three main questions. Each question aims to gather community consensus on whether to implement the proposed enhancements and, if so, in which version of PHP these changes should be applied.	+	### 1. Enhancement of Precision: Float Arguments for Sub-Second Precision

		+	Should we extend `sleep()` to accept floats for sub-second delays?
		+	- Yes
		+	- No

-	**1. Float Arguments for Sub-Second Precision**	+	**Which PHP version should implement this feature if accepted?**
		+	- 8.4
		+	- 9.0

-	Extend `sleep()` to accept floats for sub-second delays?	+	### 2. Normalized Return Values on Windows
-	- No	+
-	- PHP 8.4	+
-	- PHP 9.0	+

-	**2. Normalized Return Values on Windows**	+	**Should we modify `sleep()` on Windows for consistent return values?**
		+	- Yes
		+	- No

-	**Modify `sleep()` on Windows for consistent return values?**	+	**Which PHP version should implement this feature if accepted?**
-	- No	+	- 8.4
-	- PHP 8.4	+	- 9.0
-	- PHP 9.0	+

-	3. Enhanced Return Value Precision	+	### 3. Enhanced Return Value Precision

-	**Increase `sleep()` return value precision to include fractions of a second?**	+	**Should we increase `sleep()` return value precision to include fractions of a second?**
-	- No	+	- Yes
-	- PHP 8.4	+	- No
-	- PHP 9.0	+

		+	Which PHP version should implement this feature if accepted?
		+	- 8.4
		+	- 9.0


	===== Patches and Tests =====		===== Patches and Tests =====
		+
	A pull request has already been submitted and is available for review at: https://github.com/php/php-src/pull/13401		A pull request has already been submitted and is available for review at: https://github.com/php/php-src/pull/13401

	===== Implementation =====		===== Implementation =====
		+
	Upon acceptance, the feature will be merged into the specified PHP version, and all relevant documentation will be updated accordingly.		Upon acceptance, the feature will be merged into the specified PHP version, and all relevant documentation will be updated accordingly.

sleep_without_return_array

Anonymous (anonymous@undisclosed.example.com) — 2025-11-15T15:19:09+00:00

2025/10/29 22:32		current
Line 65:		Line 65:


-	==== 3. Excluding specific properties from serialization ====	+	==== 2. Excluding specific properties from serialization ====

	Previously, developers had to manually list serializable properties:		Previously, developers had to manually list serializable properties:
Line 108:		Line 108:


-	==== 4. Preparing data before serialization (the main use case of this RFC) ====	+	==== 3. Preparing data before serialization (the main use case of this RFC) ====

	Previously:		Previously:

sort_direction_enum

Anonymous (anonymous@undisclosed.example.com) — 2026-04-02T19:20:36+00:00

2026/04/01 17:32		current
Line 3:		Line 3:
	* Date: 2026-03-02		* Date: 2026-03-02
	* Author: Tim Düsterhus, timwolla@php.net		* Author: Tim Düsterhus, timwolla@php.net
-	* Status: Accepted	+	* Status: Implemented
-	* Implementation: tbd	+	* Implementation: https://github.com/php/php-src/commit/32c1931f18109655bc074dd5cda3248b838de636

	===== Introduction =====		===== Introduction =====
Line 105:		Line 105:

	===== Implementation =====		===== Implementation =====
-	After the RFC is implemented, this section should contain:	+
-	- the version(s) it was merged into	+	* https://github.com/php/php-src/commit/32c1931f18109655bc074dd5cda3248b838de636
-	- a link to the git commit(s)	+
-	- a link to the PHP manual entry for the feature	+

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

streamline-phar-api

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2008/03/28 15:42		current
Line 28:		Line 28:
	=== Adding isWritable() method ===		=== Adding isWritable() method ===
	== Proposal ==		== Proposal ==
-	Add an isWritable() method to determine whether an archive can be written or not. Not being able to write an archive either means it is disabled in the php.ini (see Phar::canWrite()) or that PHP can't write to the requested location of the phar archive.	+	Add an isWritable() method to determine whether an archive can be written or not. Not being able to write an archive either means it is disabled in the php.ini (see Phar::canWrite()) or that PHP can't write to the requested location of the phar archive. PharFileInfo must overload the method in order to accomplish that.
	== Code ==		== Code ==
	<code php>		<code php>

strict_argcount

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2015/03/16 05:17		current
Line 3:		Line 3:
	* Date: 2015-02-20		* Date: 2015-02-20
	* Author: Márcio Almada		* Author: Márcio Almada
-	* Status: Voting	+	* Status: Withdraw
	* First Published at: http://wiki.php.net/rfc/strict_argcount		* First Published at: http://wiki.php.net/rfc/strict_argcount
		+
		+	=> The RFC was withdraw due to many controversial points and overall rejection and won't be proposed again by the RFC author. The RFC author advises to not revive this RFC as it was already rejected. Even if you think you have a much better idea, think twice.

	===== Introduction =====		===== Introduction =====
Line 438:		Line 440:
	As this is a language change, the main voting requires a 2/3 majority to pass.		As this is a language change, the main voting requires a 2/3 majority to pass.

-	<doodle title="Should PHP7 warn about exceeding argument count on function calls?" auth="marcio" voteType="single" closed="false">	+	<doodle title="Should PHP7 warn about exceeding argument count on function calls?" auth="marcio" voteType="single" closed="true">
	* Yes		* Yes
	* No		* No
Line 448:		Line 450:
	A ''50% + 1'' majority is required. In the event of a tie the RFC author will take the final decision.		A ''50% + 1'' majority is required. In the event of a tie the RFC author will take the final decision.

-	<doodle title="What's the error level that should be emitted?" auth="marcio" voteType="single" closed="false">	+	<doodle title="What's the error level that should be emitted?" auth="marcio" voteType="single" closed="true">
	* E_WARNING		* E_WARNING
	* E_NOTICE		* E_NOTICE

switch.default.multiple

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2014/09/16 14:11		current
Line 32:		Line 32:

	* PHP 5.7: https://github.com/php/php-src/pull/807		* PHP 5.7: https://github.com/php/php-src/pull/807
-	* PHP 7.0: https://github.com/php/php-src/pull/808	+	* PHP 7.0: https://github.com/php/php-src/pull/808 (commit [[http://git.php.net/?p=php-src.git;a=commit;h=6967f78cc95ef6166f82dcb7e4395f594ce5ad0b\|6967f78cc95ef6166f82dcb7e4395f594ce5ad0b]])

	Already landed in HHVM:		Already landed in HHVM:

union_types_v2

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2019/11/08 09:23		current
Line 3:		Line 3:
	* Date: 2019-09-02		* Date: 2019-09-02
	* Author: Nikita Popov <nikic@php.net>		* Author: Nikita Popov <nikic@php.net>
-	* Status: Accepted	+	* Status: Implemented
	* Proposed Version: PHP 8.0		* Proposed Version: PHP 8.0
	* Pull request discussion: [[https://github.com/php/php-rfcs/pull/1\|php/php-rfcs#0001]]		* Pull request discussion: [[https://github.com/php/php-rfcs/pull/1\|php/php-rfcs#0001]]

uniqid

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2018/03/01 23:16		current
Line 4:		Line 4:
	* Date Modified: 2016-09-12		* Date Modified: 2016-09-12
	* Author: Yasuo Ohgaki <yohgaki@ohgaki.net>		* Author: Yasuo Ohgaki <yohgaki@ohgaki.net>
-	* Status: Under Discussion	+	* Status: Inactive
	* First Published at: http://wiki.php.net/rfc/uniqid		* First Published at: http://wiki.php.net/rfc/uniqid

wddx-deprecate-class-instance-deserialization

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2017/08/15 16:50		current
Line 3:		Line 3:
	* Date: 2017-08-15		* Date: 2017-08-15
	* Author: Christoph M. Becker, cmb@php.net		* Author: Christoph M. Becker, cmb@php.net
-	* Status: Under Discussion	+	* Status: Withdrawn
	* First Published at: https://wiki.php.net/rfc/wddx-deprecate-class-instance-deserialization		* First Published at: https://wiki.php.net/rfc/wddx-deprecate-class-instance-deserialization

backlog

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2009/03/12 21:38		current
Line 26:		Line 26:
	- [[rfc:nonbreakabletraits\|traits]]		- [[rfc:nonbreakabletraits\|traits]]
	- [[rfc:taint\|taint]]		- [[rfc:taint\|taint]]
-	- switch from bison to lemon
	- [[rfc:static-classes\|static classes]]		- [[rfc:static-classes\|static classes]]
	- "real" properties with attached getters and setters		- "real" properties with attached getters and setters
Line 53:		Line 52:
	- provide a global __call for non existing functions (george)		- provide a global __call for non existing functions (george)
	- reimplement ext/zlib based on pecl/http code (mike)		- reimplement ext/zlib based on pecl/http code (mike)
-	- Replace bison scripts with lemon. This will fix the memleak issues of the parser, make the parser threadsafe and reentrant and allows to use emalloc on temp blocks automatically. (marcus)
	- Make it possible to use objects implementing ArrayObject interface anywhere arrays are used.		- Make it possible to use objects implementing ArrayObject interface anywhere arrays are used.

php56

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2014/07/01 20:46		current
Line 13:		Line 13:
	===== RFC merged =====		===== RFC merged =====

-	{{page>rfc:#php_56&noheader&noeditbtn&nofooter}}	+	* [[rfc:debug-info\|__debugInfo() magic method]]\\ Support get_debug_info hook for userspace classes
		+	* [[rfc:pow-operator\|Exponential operator]]\\ Exponential operator
		+	* [[rfc:use_function\|Importing namespaced functions]]\\ Proposes to allow importing namespaced functions through a new `use function` sequence.
		+	* [[rfc:const_scalar_exprs\|Constant Scalar Expressions (with constants)]]\\ This RFC proposes adding support for Constant Scalar Expressions with support for constants being operands.
		+	* [[rfc:incompat_ctx\|Remove calls from incompatible context]]\\ Calls from incompatible context deprecated in 5.6 (will be removed in next version).
		+	* [[rfc:variadics\|Dedicated syntax for variadic functions]]\\ This RFC introduces a dedicated syntax for variadic functions.
		+	* [[rfc:argument_unpacking\|Argument unpacking]]\\ This RFC proposes a syntax for argument unpacking.
		+	* [[rfc:operator_overloading_gmp\|Internal operator overloading and GMP improvements]]\\ Add support for operator overloading in internal classes and improve GMP using it
		+	* [[rfc:phpdbg\|phpdbg]]\\ Distribute phpdbg with PHP, a PHP debugger
		+	* [[rfc:slim_post_data\|Slim POST data]]\\ Use a temp PHP stream for HTTP payload.
		+	* [[rfc:crypt_function_salt\|Crypt() function salt]]\\ This RFC proposes changing crypt() function's salt parameter treatment.
		+	* [[rfc:fpm_change_hat\|Apparmor change_hat functionality for php-fpm]]\\ Proposes to add the possibility to change to a different hat under the apparmor LSM
		+	* [[rfc:tls-peer-verification\|TLS Peer Verification]]\\ Enable peer verification by default for encrypted client streams.
		+	* [[rfc::improved-tls-defaults\|Improved TLS Defaults]]\\ Implement more secure defaults for encrypted stream transfers
		+	* [[rfc:default_encoding\|Default character encoding]]\\ Default character encoding handling in PHP.
		+	* [[rfc:pack_unpack_64bit_formats\|64 bit format codes for pack() and unpack()]]\\ Adds format codes for converting 64 bit integers to and from binary strings.
		+	* [[rfc:timing_attack\|Timing attack safe string comparison function]]\\ New function to perform time-constant string comparison (Created 2013/12/22)

	===== Todos =====		===== Todos =====

undoc54

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2011/10/16 02:15		current
Line 18:		Line 18:
	* import_request_variables, define_syslog_variables, session_is_registered, session_register, session_unregister - not documented as removed in 5.4		* import_request_variables, define_syslog_variables, session_is_registered, session_register, session_unregister - not documented as removed in 5.4
	* Ini options allow_call_time_pass_reference, define_syslog_variables, highlight.bg - not documented as removed in 5.4		* Ini options allow_call_time_pass_reference, define_syslog_variables, highlight.bg - not documented as removed in 5.4
-	* class_uses - Stefan
	* Magic quotes removal in 5.4 not documented - Pierrick, Pierre		* Magic quotes removal in 5.4 not documented - Pierrick, Pierre
	* Short array notation - Pierre		* Short array notation - Pierre

philip

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2012/01/08 06:04		current
Line 5:		Line 5:
	* ext/mysql/migration should exist, with mysqli+PDO_MySQL examples		* ext/mysql/migration should exist, with mysqli+PDO_MySQL examples

		+	PHP.NET update:
		+	* mysql->mysqli migration, where appropriate. Begin with master.

	=== Notes about this TODO ===		=== Notes about this TODO ===

undocumented

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2010/01/08 21:11		current
Line 124:		Line 124:
	* ''Closures''		* ''Closures''
	===== PHP 5.x ====		===== PHP 5.x ====
		+	* SplObjectStorage::getHash
	* Type hints: ''self'', ''parent'' and interfaces.		* Type hints: ''self'', ''parent'' and interfaces.
	<code php>		<code php>

bugtracker

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2009/06/01 16:02		current
Line 20:		Line 20:
	* May 20 : Decided to use pear/Bugtracker and phpweb/bugs as a base		* May 20 : Decided to use pear/Bugtracker and phpweb/bugs as a base
	* May 28 : Began coding part of GSoC. Starting with removing deprecated libraries from bugtracker, and merging in code from phpweb/bugs		* May 28 : Began coding part of GSoC. Starting with removing deprecated libraries from bugtracker, and merging in code from phpweb/bugs
-	* May 30 : Decided to replace DB, DB_Object and Tree with mysqli	+	* May 30 : Decided to replace DB with MDB2
		+	* Jun 26 : Finished migration from DB to MDB2, remove Savant and Damblan
		+	* Jul 1 : Decided to implement and SVN integration
		+	* Jul 15 : Implemented RSS 2.0
		+	* Jul 20 : Implemented SVN Client and we're discussing how to integrate with bugtracker

	===== Notes =====		===== Notes =====
	* Initial code is [[http://cvs.php.net/viewvc.cgi/pear/Bugtracker/\|pear/Bugtracker]] which is a fork of [[http://cvs.php.net/viewvc.cgi/pearweb/public_html/bugs/\|pearweb/bugs]] from a couple years ago with modifications made by Jani to unify and convert the current bugs database		* Initial code is [[http://cvs.php.net/viewvc.cgi/pear/Bugtracker/\|pear/Bugtracker]] which is a fork of [[http://cvs.php.net/viewvc.cgi/pearweb/public_html/bugs/\|pearweb/bugs]] from a couple years ago with modifications made by Jani to unify and convert the current bugs database

notes

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2026/05/19 10:05	current
Line 1:	Line 1:
	+	===== CMake Work Notes =====
	+
	+	==== Linux buildchain ====
	+
	+
	+	* buildconf
	+	Shell script to recreate user tarball, two options --force and --debug, if --$force regenerate anyway, if debug only add SUPPRESS_WARNINGS="" to make invocation. Extract version from `grep '^PHP_EXTRA_VERSION=' configure.in` to check if is dev, and check Zend directory to check if is Zend v1 or Zend v2 (this is deprecated?) At end call make -s -f build/build.mk ZENDDIR=Zend
	+
	+	* build/build.mk
	+	* ($STAMP) - call buildcheck.sh (check autoconf version > 2.13 and inform)
	+	* ($ALWAYS) == generated_lists - makefile_am_files, config_h_files, config_m4_files >> generated_lists
	+	* (action) call build/build2.mk - all: mkinstalldirs install-sh missing configure main/php_config.h.in
	+	* touch mkinstalldirs install-sh missing
	+	* cat acinclude.m4 ./build/libtool.m4 > aclocal.m4
	+	* autoconf (to regenerate ./configure)
	+	* autoheader (to regenerate acconfig.h)
	+	* Ready to configure.
	+
	+	At this step generated files are:
	+	<code>
	+	? acconfig.h
	+	? aclocal.m4
	+	? autom4te.cache/output.0
	+	? autom4te.cache/requests
	+	? autom4te.cache/traces.0
	+	? configure
	+	? generated_lists
	+	? install-sh
	+	? main/php_config.h.in
	+	? missing
	+	? mkinstalldirs
	+	</code>
	+
	+	* ./configure
	+
	+	<code>
	+	? Makefile
	+	? Makefile.fragments
	+	? Makefile.objects
	+	? TSRM/tsrm_config.h
	+	? Zend/zend_config.h
	+	? config.log
	+	? config.nice
	+	? config.status
	+	? ext/date/lib/timelib_config.h
	+	? ext/iconv/php_have_bsd_iconv.h
	+	? ext/iconv/php_have_glibc_iconv.h
	+	? ext/iconv/php_have_ibm_iconv.h
	+	? ext/iconv/php_have_iconv.h
	+	? ext/iconv/php_have_libiconv.h
	+	? ext/iconv/php_iconv_supports_errno.h
	+	? ext/iconv/php_php_iconv_h_path.h
	+	? ext/iconv/php_php_iconv_impl.h
	+	? ext/pdo_sqlite/sqlite/src/config.h
	+	? ext/pdo_sqlite/sqlite/src/sqlite3.h
	+	? ext/sqlite/libsqlite/src/config.h
	+	? ext/sqlite/libsqlite/src/sqlite.h
	+	? libtool
	+	? main/build-defs.h
	+	? main/internal_functions.c
	+	? main/internal_functions_cli.c
	+	? main/php_config.h
	+	? php5.spec
	+	? sapi/cli/php.1
	+	? scripts/man1/php-config.1
	+	? scripts/man1/phpize.1
	+	? scripts/php-config
	+	? scripts/phpize
	+	</code>
	+
	+	==== Windows buildchain ====
	+
	+	* Windows side: buildconf.bat execute -> cscript /nologo win32\build\buildconf.js %*, Javascript script that build the configure.js.
	+
	+	===== Components =====
	+
	+	==== Zend ====
	+
	+	* Zend/Makefile.am
	+	* Zend/acconfig.h
	+	* Zend/Zend.m4
	+
	+	<code>
	+	Configuring Zend
	+	checking for bison version... (cached) 2.3 (ok)
	+	checking for inttypes.h... (cached) yes
	+	checking for stdint.h... (cached) yes
	+	checking for limits.h... (cached) yes
	+	checking malloc.h usability... yes
	+	checking malloc.h presence... yes
	+	checking for malloc.h... yes
	+	checking for string.h... (cached) yes
	+	checking for unistd.h... (cached) yes
	+	checking for stdarg.h... (cached) yes
	+	checking for sys/types.h... (cached) yes
	+	checking for sys/time.h... (cached) yes
	+	checking for signal.h... (cached) yes
	+	checking for unix.h... (cached) no
	+	checking for stdlib.h... (cached) yes
	+	checking for dlfcn.h... (cached) yes
	+	checking for mach-o/dyld.h... (cached) no
	+	checking for size_t... (cached) yes
	+	checking return type of signal handlers... void
	+	checking for uint... yes
	+	checking for ulong... yes
	+	checking for int32_t... yes
	+	checking for uint32_t... yes
	+	checking for vprintf... (cached) yes
	+	checking for _doprnt... (cached) no
	+	checking for working memcmp... yes
	+	checking for working alloca.h... (cached) yes
	+	checking for alloca... (cached) yes
	+	checking for memcpy... (cached) yes
	+	checking for strdup... (cached) yes
	+	checking for getpid... yes
	+	checking for kill... yes
	+	checking for strtod... yes
	+	checking for strtol... yes
	+	checking for finite... yes
	+	checking for fpclass... (cached) no
	+	checking for sigsetjmp... no
	+	checking whether sprintf is broken... no
	+	checking for finite... (cached) yes
	+	checking for isfinite... no
	+	checking for isinf... (cached) yes
	+	checking for isnan... (cached) yes
	+	checking whether fp_except is defined... no
	+	checking for dlfcn.h... (cached) yes
	+	checking whether dlsym() requires a leading underscore in symbol names... no
	+	checking virtual machine dispatch method... CALL
	+	checking whether to enable thread-safety... no
	+	checking whether to enable inline optimization for GCC... yes
	+	checking whether to enable Zend debugging... no
	+	checking for inline... inline
	+	checking target system is Darwin... no
	+	checking for MM alignment and log values... done
	+	checking for memory allocation using mmap(MAP_ANON)... yes
	+	checking for memory allocation using mmap("/dev/zero")... yes
	+	checking for mremap... yes
	+	</code>
	+
	+	Generated post-configued:
	+	* zend_config.h
	+
	+
	+	==== configure.in ====
	+
	+	* [[.:Zend:acinclude.m4 \| Zend/acinclude.m4]] (Zend specific macro definitions)
	+	* PHP_CONFIG_NICE(config.nice) - ??
	+	* PHP_CANONICAL_HOST_TARGET
	+	* AC_CONFIG_HEADER(main/php_config.h)
	+
	+	* PHP_MAJOR_VERSION=5
	+	* PHP_MINOR_VERSION=3
	+	* PHP_RELEASE_VERSION=0
	+	* PHP_EXTRA_VERSION="-dev"
	+	* PHP_VERSION="$PHP_MAJOR_VERSION.$PHP_MINOR_VERSION.$PHP_RELEASE_VERSION$PHP_EXTRA_VERSION"
	+	* PHP_VERSION_ID=`expr [$]PHP_MAJOR_VERSION \* 10000 + [$]PHP_MINOR_VERSION \* 100 + [$]PHP_RELEASE_VERSION`
	+
	+
	+	==== Extension PHP Macros ====
	+
	+	* PHP_ARG_WITH()
	+	* PHP_ARG_ENABLE()
	+	* PHP_ADD_INCLUDE()
	+	* PHP_CHECK_LIBRARY()
	+	* PHP_ADD_LIBRARY_WITH_PATH()
	+	* PHP_SUBST()
	+	* PHP_NEW_EXTENSION()
	+	* PHP_ADD_BUILD_DIR()
	+	* PHP_ADD_MAKEFILE_FRAGMENT()
	+
	+	==== acinclude.m4 Macros ====
	+
	+	=== Output stylize macros for configure (help/runtime) ===
	+
	+	* <del>PHP_HELP_SEPARATOR(title)</del> - Adds separator title into the configure --help display.
	+	* <del>PHP_CONFIGURE_PART(title)</del> - Adds separator title configure output.
	+
	+	=== Build system helper macros ===
	+
	+	* PHP_DEF_HAVE(what) - Generates 'AC_DEFINE(HAVE_WHAT, 1, [ ])'.
	+	* PHP_RUN_ONCE(namespace, variable, code) - execute code, if variable is not set in namespace.
	+	* <del>PHP_EXPAND_PATH(path, variable)</del> - expands path to an absolute path and assigns it to variable.
	+	* PHP_DEFINE(WHAT [, value[, directory]]) - Creates builddir/include/what.h and in there #define WHAT value.
	+	* PHP_SUBST(varname) - Adds variable with it's value into Makefile, e.g.: CC = gcc
	+	* PHP_SUBST_OLD(varname) - Same as PHP_SUBST() but also substitutes all @VARNAME@ instances in every file passed to AC_OUTPUT()
	+	* PHP_OUTPUT(file) - Adds "file" to the list of files generated by AC_OUTPUT
	+
	+	=== Build system base macros ===
	+
	+	* <del>PHP_CANONICAL_HOST_TARGET</del>
	+	* <del>PHP_INIT_BUILD_SYSTEM</del>
	+	* PHP_GEN_GLOBAL_MAKEFILE
	+	* PHP_ADD_MAKEFILE_FRAGMENT([srcfile [, ext_srcdir [, ext_builddir]]])
	+	* PHP_ADD_SOURCES(source-path, sources [, special-flags [, type]])
	+
	+	=== Compiler characteristics checks ===
	+
	+	* PHP_TARGET_RDYNAMIC - Checks whether -rdynamic is supported by the compiler. This is necessary for some targets to populate the global symbol table. Otherwise, dynamic modules would not be able to resolve PHP-related symbols. If successful, adds -rdynamic to PHP_LDFLAGS.
	+	* PHP_RUNPATH_SWITCH - Checks for -R, etc. switch.
	+	* PHP_CHECK_GCC_ARG(arg, action-if-found, action-if-not-found)
	+	* PHP_LIBGCC_LIBPATH(gcc) - Stores the location of libgcc in libgcc_libpath
	+
	+	=== Macros to modify LIBS, INCLUDES, etc. variables ===
	+
	+	* PHP_REMOVE_USR_LIB(NAME) - Removes all -L/usr/$PHP_LIBDIR entries from variable NAME
	+	* PHP_EVAL_LIBLINE(libline, SHARED-LIBADD) - Use this macro, if you need to add libraries and or library search paths to the PHP build system which are only given in compiler notation.
	+	* PHP_EVAL_INCLINE(headerline) - Use this macro, if you need to add header search paths to the PHP build system which are only given in compiler notation.
	+	* PHP_ADD_LIBPATH(path [, SHARED-LIBADD]) - Adds a path to linkpath/runpath (LDFLAGS)
	+	* PHP_UTILIZE_RPATHS() - builds RPATHS/LDFLAGS from PHP_RPATHS
	+	* PHP_ADD_INCLUDE(path [,before]) - add an include path. if before is 1, add in the beginning of INCLUDES.
	+	* PHP_ADD_LIBRARY(library[, append[, shared-libadd]]) - add a library to the link line
	+	* PHP_ADD_LIBRARY_DEFER(library[, append[, shared-libadd]]) - add a library to the link line (deferred, not used during configure)
	+	* PHP_ADD_LIBRARY_WITH_PATH(library, path[, shared-libadd]) - add a library to the link line and path to linkpath/runpath.if shared-libadd is not empty and $ext_shared is yes,shared-libadd will be assigned the library information
	+	* PHP_ADD_LIBRARY_DEFER_WITH_PATH(library, path[, shared-libadd]) - add a library to the link line (deferred) and path to linkpath/runpath (not deferred) if shared-libadd is not empty and $ext_shared is yes,shared-libadd will be assigned the library information
	+	* PHP_ADD_FRAMEWORK(framework [,before]) - add a (Darwin / Mac OS X) framework to the link line. if before is 1, the framework is added to the beginning of the line.
	+	* PHP_ADD_FRAMEWORKPATH(path [,before]) - add a (Darwin / Mac OS X) framework path to the link and include lines. default paths include (but are not limited to) /Local/Library/Frameworks and /System/Library/Frameworks, so these don't need to be specifically added. if before is 1, the framework path is added to the beginning of the relevant lines.
	+	* PHP_ADD_FRAMEWORK_WITH_PATH(framework, path) - Adds a (Darwin / Mac OS X) framework path and the framework itself to the link and include lines.
	+	* PHP_SET_LIBTOOL_VARIABLE(var) - Set libtool variable.
	+
	+	=== Wrapper macros for AC_ARG_WITH / AC_ARG_ENABLE ===
	+
	+	* PHP_ARG_WITH(arg-name, check message, help text[, default-val[, extension-or-not]]) - Sets PHP_ARG_NAME either to the user value or to the default value. default-val defaults to no. This will also set the variable ext_shared,and will overwrite any previous variable of that name.If extension-or-not is yes (default), then do the ENABLE_ALL check and run the PHP_ARG_ANALYZE_EX.
	+	* PHP_ARG_ENABLE(arg-name, check message, help text[, default-val[, extension-or-not]]) - Sets PHP_ARG_NAME either to the user value or to the default value. default-val defaults to no. This will also set the variable ext_shared, and will overwrite any previous variable of that name. If extension-or-not is yes (default), then do the ENABLE_ALL check and run the PHP_ARG_ANALYZE_EX.
	+
	+	=== Build macros ===
	+
	+	* PHP_BUILD_THREAD_SAFE
	+	* PHP_REQUIRE_CXX
	+	* PHP_BUILD_SHARED
	+	* PHP_BUILD_STATIC
	+	* PHP_BUILD_BUNDLE
	+	* PHP_BUILD_PROGRAM
	+	* PHP_SHARED_MODULE(module-name, object-var, build-dir, cxx, zend_ext) - Basically sets up the link-stage for building module-name from object_var in build-dir.
	+	* PHP_SELECT_SAPI(name, type[, sources [, extra-cflags [, build-target]]]) - Selects the SAPI name and type (static, shared, programm) and optionally also the source-files for the SAPI-specific objects.
	+	* PHP_NEW_EXTENSION(extname, sources [, shared [,sapi_class[, extra-cflags[, cxx[, zend_ext]]]]]) - dnl Includes an extension in the build.
	+	"extname" is the name of the ext/ subdir where the extension resides.
	+	"sources" is a list of files relative to the subdir which are used to build the extension.
	+	"shared" can be set to "shared" or "yes" to build the extension as a dynamically loadable library. Optional parameter "sapi_class" can be set to "cli" to mark extension build only with CLI or CGI sapi's.
	+	"extra-cflags" are passed to the compiler, with @ext_srcdir@ and @ext_builddir@ being substituted.
	+	* PHP_WITH_SHARED - Checks whether $withval is "shared" or starts with "shared,XXX" and sets $shared to "yes" or "no", and removes "shared,?" stuff from $withval.
	+	* PHP_ADD_EXTENSION_DEP(extname, depends [, depconf]) - This macro is scanned by genif.sh when it builds the internal functions list, so that modules can be init'd in the correct order
	+	$1 = name of extension, $2 = extension upon which it depends
	+	$3 = optional: if true, it's ok for $2 to have not been configured default is false and should halt the build.
	+
	+	=== Checks for structures, typedefs, broken functions, etc. ===
	+
	+	* _PHP_CHECK_SIZEOF(type, cross-value, extra-headers [, found-action [, not-found-action]])
	+	* PHP_CHECK_SIZEOF(type, cross-value, extra-headers)
	+	* PHP_CHECK_TYPES(type-list, include-file [, extra-headers])
	+	* PHP_CHECK_IN_ADDR_T
	+	* PHP_TIME_R_TYPE - Check type of reentrant time-related functions Type can be: irix, hpux or POSIX
	+	* PHP_PWRITE_TEST
	+	* PHP_PREAD_TEST
	+	* PHP_MISSING_TIME_R_DECL
	+	* PHP_READDIR_R_TYPE
	+	* PHP_TM_GMTOFF
	+	* PHP_STRUCT_FLOCK
	+	* PHP_SOCKLEN_T
	+	* PHP_MISSING_FCLOSE_DECL - See if we have broken header files like SunOS has.
	+	* PHP_AC_BROKEN_SPRINTF - Check for broken sprintf(), C99 conformance
	+	* PHP_AC_BROKEN_SNPRINTF - Check for broken snprintf(), C99 conformance
	+	* PHP_SOLARIS_PIC_WEIRDNESS - Solaris requires main code to be position independent in order to let shared objects find symbols. Weird. Ugly.
	+	Must be run after all --with-NN options that let the user choose dynamic extensions, and after the gcc test.
	+	* PHP_SYS_LFS - dnl The problem is that the default compilation flags in Solaris 2.6 won't let programs access large files; you need to tell the compiler that you actually want your programs to work on large files. For more details about this brain damage please see: http://www.sas.com/standards/large.file/x_open.20Mar96.html
	+	* PHP_SOCKADDR_CHECKS
	+	* PHP_DECLARED_TIMEZONE
	+	* PHP_EBCDIC
	+	* PHP_BROKEN_GETCWD - Some systems, notably Solaris, cause getcwd() or realpath to fail if a component of the path has execute but not read permissions
	+	* PHP_BROKEN_GLIBC_FOPEN_APPEND
	+	* PHP_FOPENCOOKIE
	+
	+	=== Library/function existance and build sanity checks ===
	+
	+	* PHP_CHECK_LIBRARY(library, function [, action-found [, action-not-found [, extra-libs]]]) - Wrapper for AC_CHECK_LIB
	+	* PHP_CHECK_FRAMEWORK(framework, function [, action-found [, action-not-found ]]) - El cheapo wrapper for AC_CHECK_LIB
	+	* PHP_CHECK_FUNC_LIB(func, libs) - This macro checks whether 'func' or '__func' exists in the specified library. Defines HAVE_func and HAVE_library if found and adds the library to LIBS. This should be called in the ACTION-IF-NOT-FOUND part of PHP_CHECK_FUNC
	+	* PHP_CHECK_FUNC(func, ...) - This macro checks whether 'func' or '__func' exists in the default libraries and as a fall back in the specified library. Defines HAVE_func and HAVE_library if found and adds the library to LIBS.
	+	* PHP_TEST_BUILD(function, action-if-ok, action-if-not-ok [, extra-libs [, extra-source]]) - This macro checks whether build works and given function exists.
	+
	+
	+
	+

union_types_v2

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2026/05/19 10:05	current
Line 1:	Line 1:
	+	====== PHP RFC: Union Types 2.0 ======
	+
	+	* Date: 2019-09-02
	+	* Author: Nikita Popov <nikic@php.net>
	+	* Proposed Version: PHP 8.0
	+	* RFC PR: [[https://github.com/php/php-rfcs/pull/1\|php/php-rfcs#0001]]
	+	* Mailing list thread: https://externals.io/message/106844
	+	* Implementation: [[https://github.com/php/php-src/pull/4838\|php/php-src#4838]]
	+
	+	===== Introduction =====
	+
	+	A "union type" accepts values of multiple different types, rather than a single one. PHP already supports two special union types:
	+
	+	* ''Type'' or ''null'', using the special ''?Type'' syntax.
	+	* ''array'' or ''Traversable'', using the special ''iterable'' type.
	+
	+	However, arbitrary union types are currently not supported by the language. Instead, phpdoc annotations have to be used, such as in the following example:
	+
	+	<code php>
	+	class Number {
	+	/**
	+	* @var int\|float $number
	+	*/
	+	private $number;
	+
	+	/**
	+	* @param int\|float $number
	+	*/
	+	public function setNumber($number) {
	+	$this->number = $number;
	+	}
	+
	+	/**
	+	* @return int\|float
	+	*/
	+	public function getNumber() {
	+	return $this->number;
	+	}
	+	}
	+	</code>
	+
	+	The [[#statistics\|statistics section]] shows that the use of union types is indeed pervasive in the open-source ecosystem, as well as PHP's own standard library.
	+
	+	Supporting union types in the language allows us to move more type information from phpdoc into function signatures, with the usual advantages this brings:
	+
	+	* Types are actually enforced, so mistakes can be caught early.
	+	* Because they are enforced, type information is less likely to become outdated or miss edge-cases.
	+	* Types are checked during inheritance, enforcing the Liskov Substitution Principle.
	+	* Types are available through Reflection.
	+	* The syntax is a lot less boilerplate-y than phpdoc.
	+
	+	After generics, union types are currently the largest "hole" in our type declaration system.
	+
	+	===== Proposal =====
	+
	+	Union types are specified using the syntax ''T1\|T2\|...'' and can be used in all positions where types are currently accepted:
	+
	+	<code php>
	+	class Number {
	+	private int\|float $number;
	+
	+	public function setNumber(int\|float $number): void {
	+	$this->number = $number;
	+	}
	+
	+	public function getNumber(): int\|float {
	+	return $this->number;
	+	}
	+	}
	+	</code>
	+
	+	==== Supported Types ====
	+
	+	Union types support all types currently supported by PHP, with some caveats outlined in the following.
	+
	+	=== void type ===
	+
	+	The ''void'' type can never be part of a union. As such, types like ''T\|void'' are illegal in all positions, including return types.
	+
	+	The ''void'' type indicates that the function has no return value, and enforces that argument-less ''return;'' is used to return from the function. It is fundamentally incompatible with non-void return types.
	+
	+	What is likely intended instead is ''?T'', which allows returning either ''T'' or ''null''.
	+
	+	=== Nullable union types ===
	+
	+	The ''null'' type is supported as part of unions, such that ''T1\|T2\|null'' can be used to create a nullable union. The existing ''?T'' notation is considered a shorthand for the common case of ''T\|null''.
	+
	+	An earlier version of this RFC proposed to use ''?(T1\|T2)'' for nullable union types instead, to avoid having two ways of expressing nullability in PHP. However, this notation is both rather awkward syntactically, and differs from the well-established ''T1\|T2\|null'' syntax used by phpdoc comments. The discussion feedback was overwhelmingly in favor of supporting the ''T1\|T2\|null'' notation.
	+
	+	''?T'' remains valid syntax that denotes the same type as ''T\|null''. It is neither discouraged nor deprecated, and there are no plans to deprecate it in the future. It is merely a shorthand alias for a particularly common union type.
	+
	+	The ''null'' type is only allowed as part of a union, and can not be used as a standalone type. Allowing it as a standalone type would make both ''function foo(): void'' and ''function foo(): null'' legal function signatures, with similar but not identical semantics. This would negatively impact teachability for an unclear benefit.
	+
	+	Union types and the ''?T'' nullable type notation cannot be mixed. Writing ''?T1\|T2'', ''T1\|?T2'' or ''?(T1\|T2)'' is not supported and ''T1\|T2\|null'' needs to be used instead. I'm open to permitting the ''?(T1\|T2)'' syntax though, if this is considered desirable.
	+
	+	=== false pseudo-type ===
	+
	+	While we nowadays encourage the use of ''null'' over ''false'' as an error or absence return value, for historical reasons many internal functions continue to use ''false'' instead. As shown in the [[#statistics\|statistics section]], the vast majority of union return types for internal functions include ''false''.
	+
	+	A classical example is the ''strpos()'' family of functions, which returns ''int\|false''.
	+
	+	While it would be possible to model this less accurately as ''int\|bool'', this gives the false impression that the function can also return a ''true'' value, which makes this type information significantly less useful to humans and static analyzers both.
	+
	+	For this reason, support for the ''false'' pseudo-type is included in this proposal. A ''true'' pseudo-type is //not// part of the proposal, because similar historical reasons for its necessity do not exist.
	+
	+	The ''false'' pseudo-type cannot be used as a standalone type (including nullable standalone type). As such, all of ''false'', ''false\|null'' and ''?false'' are not permitted.
	+
	+	=== Duplicate and redundant types ===
	+
	+	To catch some simple bugs in union type declarations, redundant types that can be detected without performing class loading will result in a compile-time error. This includes:
	+
	+	* Each name-resolved type may only occur once. Types like ''int\|string\|INT'' result in an error.
	+	* If ''bool'' is used, ''false'' cannot be used additionally.
	+	* If ''object'' is used, class types cannot be used additionally.
	+	* If ''iterable'' is used, ''array'' and ''Traversable'' cannot be used additionally.
	+
	+	This does not guarantee that the type is "minimal", because doing so would require loading all used class types.
	+
	+	For example, if ''A'' and ''B'' are class aliases, then ''A\|B'' remains a legal union type, even though it could be reduced to either ''A'' or ''B''. Similarly, if ''class B extends A {}'', then ''A\|B'' is also a legal union type, even though it could be reduced to just ''A''.
	+
	+	<code php>
	+	function foo(): int\|INT {} // Disallowed
	+	function foo(): bool\|false {} // Disallowed
	+
	+	use A as B;
	+	function foo(): A\|B {} // Disallowed ("use" is part of name resolution)
	+
	+	class_alias('X', 'Y');
	+	function foo(): X\|Y {} // Allowed (redundancy is only known at runtime)
	+	</code>
	+
	+	=== Type grammar ===
	+
	+	Excluding the special ''void'' type, PHP's type syntax may now be described by the following grammar:
	+
	+	<code>
	+	type: simple_type
	+	\| "?" simple_type
	+	\| union_type
	+	;
	+
	+	union_type: simple_type "\|" simple_type
	+	\| union_type "\|" simple_type
	+	;
	+
	+	simple_type: "false" # only legal in unions
	+	\| "null" # only legal in unions
	+	\| "bool"
	+	\| "int"
	+	\| "float"
	+	\| "string"
	+	\| "array"
	+	\| "object"
	+	\| "iterable"
	+	\| "callable" # not legal in property types
	+	\| "self"
	+	\| "parent"
	+	\| namespaced_name
	+	;
	+	</code>
	+
	+	==== Variance ====
	+
	+	Union types follow the existing variance rules:
	+
	+	* Return types are covariant (child must be subtype).
	+	* Parameter types are contravariant (child must be supertype).
	+	* Property types are invariant (child must be subtype and supertype).
	+
	+	The only change is in how union types interact with subtyping, with three additional rules:
	+
	+	* A union ''U_1\|...\|U_n'' is a subtype of ''V_1\|...\|V_m'' if for each ''U_i'' there exists a ''V_j'' such that ''U_i'' is a subtype of ''V_j''.
	+	* The ''iterable'' type is considered to be the same (i.e. both subtype and supertype) as ''array\|Traversable''.
	+	* The ''false'' pseudo-type is considered a subtype of ''bool''.
	+
	+	In the following, some examples of what is allowed and what isn't are given.
	+
	+	=== Property types ===
	+
	+	Property types are invariant, which means that types must stay the same during inheritance. However, the "same" type may be expressed in different ways. Prior to union types, one such possibility was to have two aliased classes ''A'' and ''B'', in which case a property type may legally change from ''A'' to ''B'' or vice versa.
	+
	+	Union types expand the possibilities in this area: For example ''int\|string'' and ''string\|int'' represent the same type. The following example shows a more complex case:
	+
	+	<code php>
	+	class A {}
	+	class B extends A {}
	+
	+	class Test {
	+	public A\|B $prop;
	+	}
	+	class Test2 extends Test {
	+	public A $prop;
	+	}
	+	</code>
	+
	+	In this example, the union ''A\|B'' actually represents the same type as just ''A'', and this inheritance is legal, despite the type not being syntactically the same.
	+
	+	Formally, we arrive at this result as follows: First, ''A'' is a subtype of ''A\|B'', because it is a subtype of ''A''. Second, ''A\|B'' is a subtype of ''A'', because ''A'' is a subtype of ''A'' and ''B'' is a subtype of ''A''.
	+
	+	=== Adding and removing union types ===
	+
	+	It is legal to remove union types in return position and add union types in parameter position:
	+
	+	<code php>
	+	class Test {
	+	public function param1(int $param) {}
	+	public function param2(int\|float $param) {}
	+
	+	public function return1(): int\|float {}
	+	public function return2(): int {}
	+	}
	+
	+	class Test2 extends Test {
	+	public function param1(int\|float $param) {} // Allowed: Adding extra param type
	+	public function param2(int $param) {} // FORBIDDEN: Removing param type
	+
	+	public function return1(): int {} // Allowed: Removing return type
	+	public function return2(): int\|float {} // FORBIDDEN: Adding extra return type
	+	}
	+	</code>
	+
	+	=== Variance of individual union members ===
	+
	+	Similarly, it is possible to restrict a union member in return position, or widen a union member in parameter position:
	+
	+	<code php>
	+	class A {}
	+	class B extends A {}
	+
	+	class Test {
	+	public function param1(B\|string $param) {}
	+	public function param2(A\|string $param) {}
	+
	+	public function return1(): A\|string {}
	+	public function return2(): B\|string {}
	+	}
	+
	+	class Test2 extends Test {
	+	public function param1(A\|string $param) {} // Allowed: Widening union member B -> A
	+	public function param2(B\|string $param) {} // FORBIDDEN: Restricting union member A -> B
	+
	+	public function return1(): B\|string {} // Allowed: Restricting union member A -> B
	+	public function return2(): A\|string {} // FORBIDDEN: Widening union member B -> A
	+	}
	+	</code>
	+
	+	Of course, the same can also be done with multiple union members at a time, and be combined with the addition/removal of types mentioned previously.
	+
	+	==== Coercive typing mode ====
	+
	+	When ''strict_types'' is not enabled, scalar type declarations are subject to limited implicit type coercions. These are problematic in conjunction with union types, because it is not always obvious which type the input should be converted to. For example, when passing a boolean to an ''int\|string'' argument, both ''0'' and ''""'' would be viable coercion candidates.
	+
	+	If the exact type of the value is not part of the union, then the target type is chosen in the following order of preference:
	+
	+	- ''int''
	+	- ''float''
	+	- ''string''
	+	- ''bool''
	+
	+	If the type both exists in the union, and the value can be coerced to the type under PHPs existing type checking semantics, then the type is chosen. Otherwise the next type is tried.
	+
	+	As an exception, if the value is a string and both ''int'' and ''float'' are part of the union, the preferred type is determined by the existing "numeric string" semantics. For example, for ''"42"'' we choose ''int'', while for ''"42.0"'' we choose ''float''.
	+
	+	Types that are not part of the above preference list are not eligible targets for implicit coercion. In particular no implicit coercions to the ''null'' and ''false'' types occur.
	+
	+	=== Conversion Table ===
	+
	+	The following table shows how the above order of preference plays out for different input types, assuming that the exact type is not part of the union:
	+
	+	^Original type ^1st try ^2nd try ^3rd try ^
	+	\|bool \|int \|float \|string \|
	+	\|int \|float \|string \|bool \|
	+	\|float \|int \|string \|bool \|
	+	\|string \|int/float \|bool \| \|
	+	\|object \|string \| \| \|
	+
	+	=== Examples ===
	+
	+	<code php>
	+	// int\|string
	+	42 --> 42 // exact type
	+	"42" --> "42" // exact type
	+	new ObjectWithToString --> "Result of __toString()"
	+	// object never compatible with int, fall back to string
	+	42.0 --> 42 // float compatible with int
	+	42.1 --> 42 // float compatible with int
	+	1e100 --> "1.0E+100" // float too large for int type, fall back to string
	+	INF --> "INF" // float too large for int type, fall back to string
	+	true --> 1 // bool compatible with int
	+	[] --> TypeError // array not compatible with int or string
	+
	+	// int\|float\|bool
	+	"45" --> 45 // int numeric string
	+	"45.0" --> 45.0 // float numeric string
	+	"45X" --> 45 + Notice: Non well formed numeric string
	+	// int numeric string
	+	"" --> false // not numeric string, fall back to bool
	+	"X" --> true // not numeric string, fall back to bool
	+	[] --> TypeError // array not compatible with int, float or bool
	+	</code>
	+
	+	==== Alternatives ====
	+
	+	There are two main alternatives to the preference-based approach used by this proposal:
	+
	+	The first is to specify that union types //always// use strict typing, thus avoiding any complicated coercion semantics altogether. Apart from the inconsistency this introduces in the language, this has two main disadvantages: First going from a type like ''float'' to ''int\|float'' would actually //reduce// the number of valid inputs, which is highly unintuitive. Second, it breaks the variance model for union types, because we can no longer say that ''float'' is a subtype of ''int\|float''.
	+
	+	The second is to perform the coercions based on the order of types. This would mean that ''int\|string'' and ''string\|int'' are distinct types, where the former would favor integers and the latter strings. Depending on whether exact type matches are still prioritized, the string type would //always// be used for the latter case. Once again, this is unintuitive and has very unclear implications for the subtyping relationship on which variance is based.
	+
	+	==== Property types and references ====
	+
	+	References to typed properties with union types follow the semantics outlined in the [[rfc/typed_properties_v2#general_semantics\|typed properties RFC]]:
	+
	+	> If typed properties are part of the reference set, then the value is checked against each property type. If a type check fails, a TypeError is generated and the value of the reference remains unchanged.
	+	>
	+	> There is one additional caveat: If a type check requires a coercion of the assigned value, it may happen that all type checks succeed, but result in different coerced values. As a reference can only have a single value, this situation also leads to a TypeError.
	+
	+	The [[rfc/typed_properties_v2#future_interaction_with_union_types\|interaction with union types]] was already considered at the time, because it impacts the detailed reference semantics. Repeating the example given there:
	+
	+	<code php>
	+	class Test {
	+	public int\|string $x;
	+	public float\|string $y;
	+	}
	+	$test = new Test;
	+	$r = "foobar";
	+	$test->x =& $r;
	+	$test->y =& $r;
	+
	+	// Reference set: { $r, $test->x, $test->y }
	+	// Types: { mixed, int\|string, float\|string }
	+
	+	$r = 42; // TypeError
	+	</code>
	+
	+	The basic issue is that the final assigned value (after type coercions have been performed) must be compatible with all types that are part of the reference set. However, in this case the coerced value will be ''int(42)'' for property ''Test::$x'', while it will be ''float(42.0)'' for property ''Test::$y''. Because these values are not the same, this is considered illegal and a ''TypeError'' is thrown.
	+
	+	An alternative approach would be to cast the value to the only common type ''string'' instead, with the major disadvantage that this matches //neither// of the values you would get from a direct property assignment.
	+
	+	==== Reflection ====
	+
	+	To support union types, a new class ''ReflectionUnionType'' is added:
	+
	+	<code php>
	+	class ReflectionUnionType extends ReflectionType {
	+	/** @return ReflectionType[] */
	+	public function getTypes();
	+
	+	/* Inherited from ReflectionType */
	+	/** @return bool */
	+	public function allowsNull();
	+
	+	/* Inherited from ReflectionType */
	+	/** @return string */
	+	public function __toString();
	+	}
	+	</code>
	+
	+	The ''getTypes()'' method returns an array of ''ReflectionType''s that are part of the union. The types may be returned in an arbitrary order that does not match the original type declaration. The types may also be subject to equivalence transformations.
	+
	+	For example, the type ''int\|string'' may return types in the order ''["string", "int"]'' instead. The type ''iterable\|array\|string'' might be canonicalized to ''iterable\|string'' or ''Traversable\|array\|string''. The only requirement on the Reflection API is that the ultimately represented type is equivalent.
	+
	+	The ''allowsNull()'' method returns whether the union contains the type ''null''.
	+
	+	The ''%%__toString()%%'' method returns a string representation of the type that constitutes a valid code representation of the type in a non-namespaced context. It is not necessarily the same as what was used in the original code.
	+
	+	For backwards-compatibility reasons, union types that only include ''null'' and one other type (written as ''?T'', ''T\|null'', or through implicit parameter nullability), will instead use ''ReflectionNamedType''.
	+
	+	=== Examples ===
	+
	+	<code php>
	+	// This is one possible output, getTypes() and __toString() could
	+	// also provide the types in the reverse order instead.
	+	function test(): float\|int {}
	+	$rt = (new ReflectionFunction('test'))->getReturnType();
	+	var_dump(get_class($rt)); // "ReflectionUnionType"
	+	var_dump($rt->allowsNull()); // false
	+	var_dump($rt->getTypes()); // [ReflectionType("int"), ReflectionType("float")]
	+	var_dump((string) $rt); // "int\|float"
	+
	+	function test2(): float\|int\|null {}
	+	$rt = (new ReflectionFunction('test2'))->getReturnType();
	+	var_dump(get_class($rt)); // "ReflectionUnionType"
	+	var_dump($rt->allowsNull()); // true
	+	var_dump($rt->getTypes()); // [ReflectionType("int"), ReflectionType("float"),
	+	// ReflectionType("null")]
	+	var_dump((string) $rt); // "int\|float\|null"
	+
	+	function test3(): int\|null {}
	+	$rt = (new ReflectionFunction('test3'))->getReturnType();
	+	var_dump(get_class($rt)); // "ReflectionNamedType"
	+	var_dump($rt->allowsNull()); // true
	+	var_dump($rt->getName()); // "int"
	+	var_dump((string) $rt); // "?int"
	+	</code>
	+
	+	===== Backwards Incompatible Changes =====
	+
	+	This RFC does not contain any backwards incompatible changes. However, existing ReflectionType based code will have to be adjusted in order to support processing of code that uses union types.
	+
	+	===== Future Scope =====
	+
	+	The features discussed in the following are not part of this proposal.
	+
	+	==== Intersection Types ====
	+
	+	Intersection types are logically conjugated with union types. Instead of requiring that (at least) a single type constraints is satisfied, all of them must be.
	+
	+	For example ''Traversable\|Countable'' requires that the passed value is either ''Traversable'' or ''Countable'', while ''Traversable&Countable'' requires that it is both.
	+
	+	==== Mixed Type ====
	+
	+	The ''mixed'' type allows to explicitly annotate that any value is acceptable. While specifying no type has the same behavior on the surface, it does not make clear whether the type is simply missing (because nobody bothered adding it yet, or because it can't be added for backwards compatibility reasons), or whether genuinely any value is acceptable.
	+
	+	We've held off on adding a ''mixed'' type out of fear that it would be used in cases where a more specific union could have been specified. Once union types are supported, it would probably also make sense to add the ''mixed'' type.
	+
	+	==== Literal Types ====
	+
	+	The ''false'' pseudo-type introduced in this RFC is a special case of a "literal type", such as supported by [[https://www.typescriptlang.org/docs/handbook/advanced-types.html#string-literal-types\|TypeScript]]. They allow specifying enum-like types, which are limited to specific values.
	+
	+	<code php>
	+	type ArrayFilterFlags = 0\|ARRAY_FILTER_USE_KEY\|ARRAY_FILTER_USE_BOTH;
	+	array_filter(array $array, callable $callback, ArrayFilterFlags $flag): array;
	+
	+	</code>
	+	A benefit of using a union of literal types instead of an enum, is that it works directly with values of the underlying type, rather than an opaque enum value. As such, it is easier to retrofit without breaking backwards-compatibility.
	+
	+	This RFC intentionally supports the ''false'' type in a maximally restricted form, which is enough to model internal function return values, but avoids unnecessarily constraining a future proposal for introducing first-class literal types. In particular:
	+
	+	* No values implicitly coerce to ''false'', while it would also be possible to follow ''bool'' parameter coercion semantics, restricted to input values that coerce to ''false''. Both approaches have advantages, but we pick the conservative option, which permits future extension, here.
	+	* Only ''false'' is supported, but not ''true''. Once both are supported, the subtyping relationship between ''false\|true'' and ''bool'' needs to be defined (which is also tightly related to the question of implicit coercions).
	+
	+	==== Type Aliases ====
	+
	+	As types become increasingly complex, it may be worthwhile to allow reusing type declarations. There are two general ways in which this could work. One is a local alias, such as:
	+
	+	<code php>
	+	use int\|float as number;
	+
	+	function foo(number $x) {}
	+	</code>
	+
	+	In this case ''number'' is a symbol that is only visible locally and will be resolved to the original ''int\|float'' type during compilation.
	+
	+	The second possibility is an exported typedef:
	+
	+	<code php>
	+	namespace Foo;
	+	type number = int\|float;
	+
	+	// Usable as \Foo\number from elsewhere
	+	</code>
	+
	+	===== Proposed Voting Choices =====
	+
	+	Simple yes/no vote.
	+
	+	===== Statistics =====
	+
	+	To illustrate the use of union types in the wild, the use of union types in ''@param'' and ''@return'' annotations in phpdoc comments has been analyzed.
	+
	+	In the top two thousand composer packages there are:
	+
	+	* 25k parameter union types: [[https://gist.github.com/nikic/64ff90c5038522606643eac1259a9dae#file-param_union_types-json\|Full JSON data]]
	+	* 14k return union types: [[https://gist.github.com/nikic/64ff90c5038522606643eac1259a9dae#file-return_union_types-json\|Full JSON data]]
	+
	+	In the PHP stubs for internal functions (these are incomplete right now, so the actual numbers should be at least twice as large) there are:
	+
	+	* 336 union return types
	+	* of which 312 include ''false'' as a value
	+
	+	This illustrates that the ''false'' pseudo-type in unions is necessary to express the return type of many existing internal functions.
	+

20070513

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2008/11/09 03:03		current
Line 63:		Line 63:
	* Why so many dead proposals?		* Why so many dead proposals?
	* Some sort of Design Guide to go along with coding standards		* Some sort of Design Guide to go along with coding standards
		+
		+	===== Minutes =====
		+	These are the minutes from the May 13th PEAR Group meeting, if you have any questions feel free to send us an email (pear-group at php.net).
		+
		+	These minutes will be posted on the pear website at a latter date.
		+	-josh
		+	--------
		+
		+	===Attending===
		+
		+	* Arnaud Limbourg (arnaud)
		+	* Christian Weiske (cweiske)
		+	* Helgi Pormar (helgi)
		+	* Joshua Eichorn (jeichorn)
		+	* Lukas Smith (lsmith)
		+
		+	* Pear President Greg Beaver (cellog)
		+
		+	===Not Attending===
		+	* David Coallier (davidc)
		+	* Martin Jansen (mj)
		+
		+
		+	arnaud and lsmith left the meeting after the first hour
		+	cellog arrived 2 hours into the meeting
		+
		+	==Discussion==
		+
		+	Agenda for meeting is at: [[MeetingAgenda20070513]]
		+
		+	===Making decisions (non-policy)===
		+	Decisions are made by consensus (http://en.wikipedia.org/wiki/Consensus), any member can call for a vote if they disagree, voting has to be seconded
		+	If the entire pear group is available in a meeting voting can be done during the meeting otherwise an email vote is done
		+	Email votes should be a minmum of 7 days (or until all votes are cast) with sponsor of vote having the ability to set a longer time
		+	Email votes should be managed by any PEAR Group momber other then the membe rhwo called for the vote
		+	All Votes are final
		+
		+	Community notification will be on a case by case basis depending on the importance of the decision, with a minimum of an email to pear-dev
		+	A pear group member can call for a pear group vote to decide an issue by full pear election
		+
		+	====action items====
		+	* jeichorn - post this wording to the group for review
		+	* helgi - find a place on the website for items like this
		+
		+	===Community Notification, increasing transparency===
		+	Minutes will be posted from each meeting to a new section of the website with notifications to pear-dev and website front page
		+
		+	====action items====
		+	* arnaud - sending current thoughts to the rest of the pear group and making sure everyone else is fine with our solution
		+	* helgi - creating a new section on the website to post minutes too
		+	* jeichorn - post minutes from this meeting
		+
		+	===Vice President===
		+	candidates:
		+	* jeichorn
		+
		+	====action items====
		+	* postponing until after the runoff election to give winner a chance to be a candidate if they want
		+
		+	===Meeting Schedule===
		+	Meet every 2 weeks, need at least 3 members present to have a meeting
		+
		+	====action items====
		+	* helgi - schedule another meeting next week
		+
		+	===Constitution updates===
		+	Cover pear group tie for last position runoff
		+	Cover winning president less then 50% of votes
		+	Schedule election on new wording within a month
		+
		+	====action items====
		+	* cweiske will work on the language of the amendment
		+
		+	===Defining Collectives===
		+	Goal is for each collective to have at least 5 packages
		+	Review with pear group, and then entire community
		+	http://wiki.bluga.net/pear/collectives
		+	We will need to create a guide to help collectives get started
		+
		+	====action items====
		+	* jeichorn- send out url and ask for feedback
		+	* jeichorn- put back on agenda for next meeting
		+
		+	===Managing ongoing tasks===
		+	Were just going to leave this to whoever has time, we seem to be covering things well right now
		+
		+	====action items====
		+	* helgi - add a feature request for a cron check on limbo account approvals http://pear.php.net/bugs/bug.php?id=11026
		+
		+	===RFC Process===
		+	http://wiki.bluga.net/pear/rfc
		+	Working off current proposal
		+	Need to look at when to do a full pear vote
		+
		+	====action items====
		+	* jeichorn - get review from rest of the pear group
		+	* cweiske - create RFC section of the manual
		+
		+	Skip Items #9 to #11 on agenda
		+
		+	===Licensing in general===
		+	were not going to push any license on the approved list, but we will discourage the php license on none extension code
		+	recommendations about handling multiple copyright owners on code, and license compatibility would be good
		+	recommend GFDL for the manual
		+
		+	====action items====
		+	* cellog - search for legal advice to help review current licenses
		+
		+	===Mozilla Code and the MPL===
		+	We don't want another license in PEAR it's hard enough as it stands
		+
		+	====action items====
		+	* cellog - contact and mozilla and work out their concerns
		+	* jeichorn - find original pear-dev email
		+
		+	===Review Suggestions===
		+	Need to cover more, with the rest of the group
		+	spent some time covering a new include proposal from cellog for pear2 that would solve include_path concerns
		+
		+	Prop Summary:
		+	1 file per package that includes all its code
		+	Support autoload for people who want that
		+	PEAR2 provides an autoload class
		+
		+	====action items====
		+	* jeichorn - make sure all of pear group has read the comments
		+
		+	All other items on the Agenda were moved to the next meeting
		+
		+	===General Action Items===
		+	* jeichorn - start agenda for the next meeting
		+	* jeichorn - get minutes approved and published on pear-dev
		+

20070520

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2026/05/19 10:05	current
Line 1:	Line 1:
	+	====== PEAR Group Meeting Sunday 20th May 2007 ======
	+
	+	Looks like the meeting will be on Sunday the 20th 7pm UTC, check the pear clock for your timezone
	+
	+	http://clock.bluga.net/pear.php
	+
	+	You should all watch this before the meeting: http://video.google.com/videoplay?docid=-4216011961522818645
	+
	+	* Review last weeks action items
	+	* Review decision making process http://wiki.bluga.net/pear/decision_making?
	+	* Vote on vice president
	+	* Schedule some future meetings
	+	* Defining Collectives
	+	* Review RFC Proposal ((rfc))
	+	* Getting more people involved
	+	* Mentor Program
	+	* Reduction of adversarial attitude to new proposals
	+	* Community Outreach program (phpwomen, phpgtk, users groups)
	+	* PEAR Evangelist(s) who reach out to other libraries/frameworks/communities to try and foster PEAR use within their projects
	+	* Overall attitude and behaviors of current developers
	+	* Figuring out what people think of PEAR (and how we can make that positive)
	+	* I don't think its all great thoughts
	+	* Lots of people are turned off by the installer21
	+	* We have lots of positive aspects too, how do we focus on them
	+	* Website organization/updates
	+	* get users' feedback. A lot of people use pear or even write articles yet very little exists to show this material on the site
	+	* Review Suggestions from:
	+	* http://blog.joshuaeichorn.com/archives/2007/05/03/how-would-you-improve-pear/
	+	* http://www.sitepoint.com/blogs/2004/04/12/more-debate-on-pear/
	+	* Dealing with unmaintained/deprecated/dead packages
	+	* Also dead pepr proposals
	+	* Thoughts on PEAR2
	+	* Creating some sort of roadmap to move us forward
	+	* Creation of working groups to move projects forward
	+	* Reviewing RFCs
	+	* Creating a mentoring program
	+	* Community outreach
	+	* Evangelists (Driven by Greg?)
	+	* Success Stories
	+	* porting peardoc to livedoc (mainly helping the php effort, has to be this summer, phillip has more details)
	+	* Website Look/Feel Redesign/Update
	+	* Some kind of news effort, weekly/bi-weekly/monthly, perhaps working with Steph, this would only be couple of people that would over see the project and other people should be able to contribute easily
	+	* Good way to get outside people more in sync what's happening in the community
	+	* PEAR's week of code (David)
	+	* Idea
	+	* Sponsorship
	+	* Priorities
	+	* Tools
	+	* how to keep track of all that (wiki, trac, other: basecamp, etc) ?
	+	* have a serendipity install or other to manage publishing news on the site (committing to cvs and updating the site is not the greatest thing). We can also have a PEAR official blog.
	+	* Some sort of Design Guide to go along with coding standards, this would be a more in depth guide covering some common patterns guidelines for class/method sizes etc, would also be non binding just a guide, would need lots of community help

20070603

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2026/05/19 10:05	current
Line 1:	Line 1:
	+	====== PEAR Group Meeting Sunday 3rd June 20077 ======
	+	Looks like the meeting will be on Sunday June 3rd 7pm UTC, check the pear clock for your timezone
	+
	+	http://clock.bluga.net/pear.php
	+
	+	You should all watch this before the meeting: http://video.google.com/videoplay?docid=-4216011961522818645
	+
	+	* Review last weeks action items
	+	* Schedule Next meeting
	+	* Vote on Vice President
	+	* Accept constitution extension. This should be added to the constitution on II Checks and balances:
	+	''PEAR Group and president elections take one month.
	+	In case of a tie, a runoff election between
	+	the tied competitors will be held. The runoff election will commence 10
	+	days after the previous election concludes, and will last 10 days.''
	+	* Review Collective List
	+	* Vote on RFC
	+	* Review Suggestions from:
	+	* http://blog.joshuaeichorn.com/archives/2007/05/03/how-would-you-improve-pear/
	+	* http://www.sitepoint.com/blogs/2004/04/12/more-debate-on-pear/
	+	* Dealing with unmaintained/deprecated/dead packages
	+	* Also dead pepr proposals
	+	* Coding standards: How to deal with "{" after "class Foo" -> Current consensus is a newline, then {, but that's not written down
	+	* Thoughts on PEAR2
	+	* Creating some sort of roadmap to move us forward
	+	* Naming (branding) of new installer/repository (Pyrus/Peach? Pyrus/PEAR2? etc.)
	+	* Creation of working groups to move projects forward
	+	* Reviewing RFCs
	+	* Creating a mentoring program
	+	* Community outreach
	+	* Evangelists (Driven by Greg?)
	+	* Success Stories
	+	* porting peardoc to livedoc (mainly helping the php effort, has to be this summer, phillip has more details)
	+	* Website Look/Feel Redesign/Update
	+	* Some kind of news effort, weekly/bi-weekly/monthly, perhaps working with Steph, this would only be couple of people that would over see the project and other people should be able to contribute easily
	+	* Good way to get outside people more in sync what's happening in the community
	+	* PEAR's week of code (David)
	+	* Idea
	+	* Sponsorship
	+	* Priorities
	+	* Tools
	+	* how to keep track of all that (wiki, trac, other: basecamp, etc) ?
	+	* Wiki needs to accept pear logins, not require pear devs to register.
	+	* have a serendipity install or other to manage publishing news on the site (committing to cvs and updating the site is not the greatest thing). We can also have a PEAR official blog.
	+	* Some sort of Design Guide to go along with coding standards, this would be a more in depth guide covering some common patterns guidelines for class/method sizes etc, would also be non binding just a guide, would need lots of community help
	+	* Mission statement
	+	* have a wiki page with the mission statement (thread from october 2006 on pear-dev)

2026/05/18 19:59		current
Line 14:		Line 14:

	* [[rfc:array_get_and_array_has\|array_path_get and array_path_exists functions]] (Created 2026-04-04, voting started 2026-05-18, ends 2026-06-01)		* [[rfc:array_get_and_array_has\|array_path_get and array_path_exists functions]] (Created 2026-04-04, voting started 2026-05-18, ends 2026-06-01)
-	* [[rfc:session_security_defaults\|Session security defaults]] (Created 2026-04-04)
	* [[rfc:stream_errors\|Stream Error Handling Improvements]] (Created 2025-11-18)		* [[rfc:stream_errors\|Stream Error Handling Improvements]] (Created 2025-11-18)
	* [[rfc:uri_followup\| Followup Improvements for ext/uri]] (Created 2025-10-17, voting started 2026-05-05, ends 2026-05-19)		* [[rfc:uri_followup\| Followup Improvements for ext/uri]] (Created 2025-10-17, voting started 2026-05-05, ends 2026-05-19)
Line 162:		Line 161:
	==== PHP 8.6 ====		==== PHP 8.6 ====
	* [[rfc:debugable-enums\|Debugable Enums]] (Created 2026-03-12; discussion started 2026-03-12; voting started 2026-04-02, ends 2026-04-16)		* [[rfc:debugable-enums\|Debugable Enums]] (Created 2026-03-12; discussion started 2026-03-12; voting started 2026-04-02, ends 2026-04-16)
		+	* [[rfc:session_security_defaults\|Secure Session Configuration Defaults]] (Created 2026-04-04)
	* [[rfc:eol-oniguruma\|Oniguruma maintenance end and end of mbregex]] (Created 2025-08-21; voting started 2026-04-10, ends 2026-04-25)		* [[rfc:eol-oniguruma\|Oniguruma maintenance end and end of mbregex]] (Created 2025-08-21; voting started 2026-04-10, ends 2026-04-25)
	* [[rfc:sort_direction_enum\|enum SortDirection]] (Created 2026-03-02)		* [[rfc:sort_direction_enum\|enum SortDirection]] (Created 2026-03-02)

2025/09/19 10:05		current
Line 13:		Line 13:
	* Volker Dusch <edorian@php.net>		* Volker Dusch <edorian@php.net>
	* Calvin Buckley <calvinb@php.net>		* Calvin Buckley <calvinb@php.net>
-	* Status: Pending Implementations	+	* Status: Implemented (for the accepted proposals)
-	* Implementation: TBD	+	* Implementation: 8.5
	* [[https://github.com/php/php-src/commit/5f8d648af6ef4e29a3c7f2b2029d08466c12bc6f\|Deprecate semicolon after case in switch statement]]		* [[https://github.com/php/php-src/commit/5f8d648af6ef4e29a3c7f2b2029d08466c12bc6f\|Deprecate semicolon after case in switch statement]]
	* [[https://github.com/php/php-src/commit/3bf21a0d43e8bc8084a19937e5d5dc354f0c07cd\|Deprecate non-standard cast names]]		* [[https://github.com/php/php-src/commit/3bf21a0d43e8bc8084a19937e5d5dc354f0c07cd\|Deprecate non-standard cast names]]
	* [[https://github.com/php/php-src/commit/3d9d68e1cacf8d185de6281bfec058b22e3094f8\|Deprecate backticks as an alias for shell_exec]]		* [[https://github.com/php/php-src/commit/3d9d68e1cacf8d185de6281bfec058b22e3094f8\|Deprecate backticks as an alias for shell_exec]]
-	* Deprecate the <php>__sleep()</php> and <php>__wakeup()</php> magic methods	+	* Deprecate the <php>__sleep()</php> and <php>__wakeup()</php> magic methods ([[https://github.com/php/php-src/commit/f18e99244b675a31a8ee5dea5dbfd75e5abf610a\|__sleep()]], [[https://github.com/php/php-src/commit/a5f2eee785d99ab97e2bfd877f015608d9e9f94e\|__wakeup()]])
-	* Deprecate using values null as an array offset and when calling array_key_exists()	+	* [[https://github.com/php/php-src/commit/49e3956b703b4aeb24c7a42ae3ee89e2a339560d\|Deprecate using values null as an array offset and when calling array_key_exists()]]
	* [[https://github.com/php/php-src/commit/3dc962b9f765f5f4a7f8c4fa93f55fee8dad84ca\|Deprecate __debugInfo() returning null]]		* [[https://github.com/php/php-src/commit/3dc962b9f765f5f4a7f8c4fa93f55fee8dad84ca\|Deprecate __debugInfo() returning null]]
	* [[https://github.com/php/php-src/commit/010fe2bb42abba0d383e9f677850ddadab46ba6a\|Deprecate constant redeclaration]]		* [[https://github.com/php/php-src/commit/010fe2bb42abba0d383e9f677850ddadab46ba6a\|Deprecate constant redeclaration]]
Line 26:		Line 26:
	* [[https://github.com/php/php-src/commit/a84a82ed88cde4dd2e73c2448e089d31c876705a\|Deprecate the report_memleaks INI directive]]		* [[https://github.com/php/php-src/commit/a84a82ed88cde4dd2e73c2448e089d31c876705a\|Deprecate the report_memleaks INI directive]]
	* [[https://github.com/php/php-src/commit/37bf0ec9610d7faf5d24bad58c8873f2452fcb4d\|Deprecate the register_argc_argv INI directive]]		* [[https://github.com/php/php-src/commit/37bf0ec9610d7faf5d24bad58c8873f2452fcb4d\|Deprecate the register_argc_argv INI directive]]
-	* Remove disable_classes INI setting	+	* [[https://github.com/php/php-src/commit/f4e2e91d4b6d28448104500819b68edf58bd263c\|Remove disable_classes INI setting]]
	* [[https://github.com/php/php-src/commit/922c225fbf1a5a7a2e43ebfdff8d91ad91e9cc25\|Deprecate Reflection*::setAccessible()]]		* [[https://github.com/php/php-src/commit/922c225fbf1a5a7a2e43ebfdff8d91ad91e9cc25\|Deprecate Reflection*::setAccessible()]]
	* [[https://github.com/php/php-src/commit/ffdc1044c9bfb6a70cd3112827135333fbdb0ca8\|Deprecate ReflectionClass::getConstant() for missing constants]]		* [[https://github.com/php/php-src/commit/ffdc1044c9bfb6a70cd3112827135333fbdb0ca8\|Deprecate ReflectionClass::getConstant() for missing constants]]
Line 35:		Line 35:
	* [[https://github.com/php/php-src/commit/94a15cc92f2593c4f7bbf0a4ef734e3f80e43e07\|Deprecate the $exclude_disabled parameter of get_defined_functions()]]		* [[https://github.com/php/php-src/commit/94a15cc92f2593c4f7bbf0a4ef734e3f80e43e07\|Deprecate the $exclude_disabled parameter of get_defined_functions()]]
	* [[https://github.com/php/php-src/commit/dc0962c2439d6140c918f132e2a24129c0b3c262\|Deprecate passing null to readdir(), rewinddir(), and closedir()]]		* [[https://github.com/php/php-src/commit/dc0962c2439d6140c918f132e2a24129c0b3c262\|Deprecate passing null to readdir(), rewinddir(), and closedir()]]
-	* Deprecate passing string which are not one byte long to ord()	+	* [[https://github.com/php/php-src/commit/93676a0425147de239f3758de6b0bce359dccdc6\|Deprecate passing string which are not one byte long to ord()]]
	* [[https://github.com/php/php-src/commit/cab46b27b9d0a91c30b596a9e1838ba1e353359c\|Deprecate passing integers outside the interval [0, 255] to chr()]]		* [[https://github.com/php/php-src/commit/cab46b27b9d0a91c30b596a9e1838ba1e353359c\|Deprecate passing integers outside the interval [0, 255] to chr()]]
	* [[https://github.com/php/php-src/commit/21625006e5e20b21f0f814ef6a3903de273f88e2\|Formally deprecate socket_set_timeout()]]		* [[https://github.com/php/php-src/commit/21625006e5e20b21f0f814ef6a3903de273f88e2\|Formally deprecate socket_set_timeout()]]
-	* Deprecate the $http_response_header predefined variable	+	* [[https://github.com/php/php-src/commit/8a5972fd83d801bdf7486178f5898d25de033a90\|Deprecate the $http_response_header predefined variable]]
-	* [ODBC] Remove flags for building against specific drivers directly	+	* [[https://github.com/php/php-src/commit/cebe50a1afa4ec0c4ebe548738975ef585000225\|[ODBC] Remove flags for building against specific drivers directly]]
	* [[https://github.com/php/php-src/commit/60047025db8451ba4a37ded3be4dc9c4afbfbeaa\|Remove support for older ODBC versions]]		* [[https://github.com/php/php-src/commit/60047025db8451ba4a37ded3be4dc9c4afbfbeaa\|Remove support for older ODBC versions]]
	* [[https://github.com/php/php-src/commit/732069d98bcd63c10360ab3f77ae376cab6d6f0d\|Deprecate PDO's 'uri:' scheme]]		* [[https://github.com/php/php-src/commit/732069d98bcd63c10360ab3f77ae376cab6d6f0d\|Deprecate PDO's 'uri:' scheme]]
-	* Deprecate driver specific PDO constants and methods	+	* Deprecate driver specific PDO constants and methods ([[https://github.com/php/php-src/commit/6f32e1c690b07f64df31b3145374ace15cc0c661\|constants]], [[https://github.com/php/php-src/commit/a4afc57f1d5f59296998ef5e3187ca42c0ab1166\|methods]])
-	* Deprecate Pdo\Pgsql constants related to statement transaction state	+	* [[https://github.com/php/php-src/commit/9f8802c41661442d1a18294fb9e9edcfb7c95bab\|Deprecate Pdo\Pgsql constants related to statement transaction state]]
	* [[https://github.com/php/php-src/commit/ccb716dcadf60d989db48e4d2963e14d7dc63df3\|Deprecate finfo_close()]]		* [[https://github.com/php/php-src/commit/ccb716dcadf60d989db48e4d2963e14d7dc63df3\|Deprecate finfo_close()]]
	* [[https://github.com/php/php-src/commit/4de2ec3895e904478df891cb31ca9f425a98dff5\|Deprecate xml_parser_free()]]		* [[https://github.com/php/php-src/commit/4de2ec3895e904478df891cb31ca9f425a98dff5\|Deprecate xml_parser_free()]]