PHP Wiki

reldateformatter - Add voting start time

weilindu (weilindu@undisclosed.example.com) — 2026-09-14T14:44:40+00:00

2026/09/08 08:51		current
Line 400:		Line 400:
	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 IntlRelativeDateTimeFormatter to ext/intl?" voteType="single" closed="false">	+	<doodle title="Add IntlRelativeDateTimeFormatter to ext/intl?" voteType="single" closed="false" start="2026-09-15T00:00:00Z" end="2026-09-29T00:00:00Z">
	* Yes		* Yes
	* No		* No

php86 - add beta 3

sergey (sergey@undisclosed.example.com) — 2026-09-14T09:16:52+00:00

2026/09/01 16:23		current
Line 20:		Line 20:
	\| Aug 13 2026 \| Beta 1 + Soft feature freeze: all RFCs must have their voting concluded [[https://www.php.net/archive/2026.php#2026-08-13-1\|Announce]] [[https://downloads.php.net/~svpernova09/\|Files]] \|		\| Aug 13 2026 \| Beta 1 + Soft feature freeze: all RFCs must have their voting concluded [[https://www.php.net/archive/2026.php#2026-08-13-1\|Announce]] [[https://downloads.php.net/~svpernova09/\|Files]] \|
	\| Aug 27 2026 \| Beta 2 [[https://www.php.net/archive/2026.php#2026-08-27-1\|Announce]] [[https://downloads.php.net/~mbeccati/\|Files]] \|		\| Aug 27 2026 \| Beta 2 [[https://www.php.net/archive/2026.php#2026-08-27-1\|Announce]] [[https://downloads.php.net/~mbeccati/\|Files]] \|
-	\| Sep 10 2026 \| Beta 3 \|	+	\| Sep 10 2026 \| Beta 3 [[https://www.php.net/archive/2026.php#2026-09-10-1\|Announce]] [[https://downloads.php.net/~svpernova09/\|Files]] \|
	\| Sep 22 2026 \| Hard feature freeze: features, whether requiring an RFC or not, must be merged only with approval from the RMs. \|		\| Sep 22 2026 \| Hard feature freeze: features, whether requiring an RFC or not, must be merged only with approval from the RMs. \|
	\| Sep 24 2026 \| RC1 \|		\| Sep 24 2026 \| RC1 \|

end_pear_endorsement - Reflect PEAR support; added archive timeline.

nicksdot (nicksdot@undisclosed.example.com) — 2026-09-14T03:36:46+00:00

2026/08/27 03:46		current
Line 1:		Line 1:
	====== PHP RFC: End PEAR Project Endorsement ======		====== PHP RFC: End PEAR Project Endorsement ======

-	* Version: 0.9	+	* Version: 0.9.1
	* Date: 2026-08-27		* Date: 2026-08-27
	* Author: Nick Sdot, php@nicksdot.dev		* Author: Nick Sdot, php@nicksdot.dev
Line 21:		Line 21:
	* PEAR mailing lists on news-web.php.net are effectively abandoned, leaving users without meaningful project response.		* PEAR mailing lists on news-web.php.net are effectively abandoned, leaving users without meaningful project response.

-	Attempts to find solutions with PEAR maintainers, directly and through official channels, did not lead to results. All this combined is a bad look, and a reputational risk for the PHP project. There were similar RFCs [4][5] in the past (last in 2025), but never brought to a vote. This RFC takes the concerns from earlier discussion into account: PHP internals cannot vote to stop independent maintainers from maintaining PEAR elsewhere. PHP internals can, however, decide what PHP bundles, what PHP domains serve, and what official websites endorse.	+	All this combined is a bad look, and a reputational risk for the PHP project. There were similar RFCs [4][5] in the past (last in 2025), but never brought to a vote. This RFC takes the concerns from earlier discussion into account: PHP internals cannot vote to stop independent maintainers from maintaining PEAR elsewhere. PHP internals can, however, decide what PHP bundles, what PHP domains serve, and what official websites endorse.
		+
		+	===== PEAR Support =====
		+
		+	Since this RFC entered discussion, Chuck Burgess, long-time PEAR maintainer and member of the PEAR Group, contacted the RFC author and expressed support for sunsetting the PEAR website and removing PEAR from PHP source. The proposal can therefore proceed with explicit support and assistance from an PEAR representative.

	===== Proposal =====		===== Proposal =====
Line 29:		Line 33:
	==== 1. Provide Archive ====		==== 1. Provide Archive ====

-	All relevant, public pages of the current PEAR website will be served as a static archive. The infrastructure team will decide technical details. The archive includes package details, downloads, manuals, and public bug reports. PEAR CLI endpoints will keep working to not break the PEAR CLI for legacy users.	+	All relevant, public pages of the current PEAR website will be served as a static archive. The infrastructure team will decide technical details. The archive includes package details, downloads, manuals, and public bug reports. The browsable archive, including PEAR CLI endpoints, will remain available until 2027-12-31 to not abruptly break legacy users. After that, the archive will be provided as a download.
-		+
-	The archive preview can be found under https://nicksdot.github.io/pear.	+

	==== 2. Unbundle PEAR ====		==== 2. Unbundle PEAR ====
Line 57:		Line 59:

	8.7 for the ''php-src'' unbundling.		8.7 for the ''php-src'' unbundling.
-
-	===== Future Scope =====
-
-	Members of the infrastructure team pointed out that providing the browsable archive should be temporary so as not to abruptly break legacy projects. At some point in the future the archive should be removed to avoid wasting project resources.

	===== Voting =====		===== Voting =====
Line 87:		Line 85:
	===== Changelog =====		===== Changelog =====

		+	* 2026-09-14: Reflect PEAR support; added archive timeline.
	* 2026-08-27: Moved to discussion.		* 2026-08-27: Moved to discussion.
	* 2026-06-24: Initial.		* 2026-06-24: Initial.

snmp_improvements_2026

eskyuu (eskyuu@undisclosed.example.com) — 2026-09-10T12:57:13+00:00

2026/05/13 14:03		current
Line 3:		Line 3:
	* Date: 2026-03-27		* Date: 2026-03-27
	* Author: Steven Wilton, swilton@fluentit.au		* Author: Steven Wilton, swilton@fluentit.au
-	* Status: Accepted	+	* Status: Implemented
	* Implementation:		* Implementation:
	* https://github.com/php/php-src/pull/21451 (Increase security protocol options)		* https://github.com/php/php-src/pull/21451 (Increase security protocol options)
	* https://github.com/php/php-src/pull/21452 (MIB reset)		* https://github.com/php/php-src/pull/21452 (MIB reset)
	* https://github.com/php/php-src/pull/21502 (Increase output options)		* https://github.com/php/php-src/pull/21502 (Increase output options)
-	* https://github.com/php/php-src/pull/21577 (combined)

	===== Introduction =====		===== Introduction =====
Line 148:		Line 147:
	* https://github.com/php/php-src/pull/21452		* https://github.com/php/php-src/pull/21452
	* https://github.com/php/php-src/pull/21502		* https://github.com/php/php-src/pull/21502
		+
		+	===== Errata =====
		+
		+	During code review it was noted that the "Increase output options" should use PHP enums to improve type safety in userland. The also involved allowing both the enums and original constant values to be provided in the original functions. The resulting example code looks like this:
		+
		+	<PHP>
		+	<?php
		+
		+	// For snmp functions
		+	snmp_set_output_format(Snmp\Output::ExtendedIndex, true);
		+	snmp_set_output_format(Snmp\Output::DontPrintUnits, true);
		+
		+	// Using the Object
		+	$snmp = new SNMP(...);
		+	$snmp->extended_index = true;
		+	$snmp->dont_print_units = true;
		+	$snmp->setOidOutputFormat(Snmp\OidOutput::Numeric);
		+	$snmp->setStringOutputFormat(Snmp\StringOutput::Ascii);
		+
		+	?>
		+	</PHP>

	===== Implementation =====		===== Implementation =====

no_serialize_attribute - v0.9: ecosystem examples, symmetric unserialize(), explicit stub migration, exception spec

dkulyk (dkulyk@undisclosed.example.com) — 2026-09-07T13:17:00+00:00

2025/11/13 19:45		current
Line 1:		Line 1:
	====== PHP RFC: Add #[NoSerialize] attribute for excluding properties or classes from serialization ======		====== PHP RFC: Add #[NoSerialize] attribute for excluding properties or classes from serialization ======
-	* Version: 0.8	+	* Version: 0.9
	* Date: 2025-10-06		* Date: 2025-10-06
	* Author: Dmytro Kulyk, lnkvisitor.ts@gmail.com		* Author: Dmytro Kulyk, lnkvisitor.ts@gmail.com
Line 14:		Line 14:

	Currently, developers must manually handle this by overriding <php>__sleep()</php> or <php>__serialize()</php>, which can lead to repetitive boilerplate and maintenance overhead.		Currently, developers must manually handle this by overriding <php>__sleep()</php> or <php>__serialize()</php>, which can lead to repetitive boilerplate and maintenance overhead.
		+
		+	This pattern is common in large codebases. A few representative examples:
		+
		+	^ Project ^ Pattern ^ What #[NoSerialize] replaces ^
		+	\| Magento 2 \| <php>__sleep()</php> chains five levels deep, each doing <php>array_diff(parent::__sleep(), [...])</php> to strip ~30 injected services \| one attribute per transient property, no per-class <php>__sleep()</php> \|
		+	\| Symfony \| six identical <php>__serialize()</php> implementations whose only body throws an exception \| class-level <php>#[NoSerialize]</php> \|
		+	\| Laravel, Doctrine ORM \| whitelist <php>__sleep()</php> returning two of N properties \| marking the transient properties instead of enumerating the persistent ones \|
		+
		+	Note that <php>__serialize()</php> is not a substitute here: it requires describing the //entire// format by hand, whereas the attribute expresses a single exception to the default format.


Line 32:		Line 41:
	* Marks a property or class as excluded from native serialization.		* Marks a property or class as excluded from native serialization.
	*		*
-	* When applied to a property, it will be skipped during serialize().	+	* When applied to a property, it is excluded from the serialized form in
-	* When applied to a class, serialization will be forbidden.	+	* both directions: skipped by serialize(), ignored by unserialize().
		+	* When applied to a class, serialization and unserialization are forbidden.
	*/		*/
	#[Attribute(Attribute::TARGET_PROPERTY \| Attribute::TARGET_CLASS)]		#[Attribute(Attribute::TARGET_PROPERTY \| Attribute::TARGET_CLASS)]
Line 68:		Line 78:
	=== 2.1 Property-level Behavior ===		=== 2.1 Property-level Behavior ===

-	When the <php>#[NoSerialize]</php> attribute is applied to a property, it instructs the engine to skip that property during native serialization.	+	When the <php>#[NoSerialize]</php> attribute is applied to a property, it declares that the property is not part of the serialized form of the object, in either direction.

	* When <php>serialize()</php> is invoked and the class does not define its own <php>__serialize()</php> or <php>__sleep()</php>, properties marked with <php>#[NoSerialize]</php> are skipped automatically.		* When <php>serialize()</php> is invoked and the class does not define its own <php>__serialize()</php> or <php>__sleep()</php>, properties marked with <php>#[NoSerialize]</php> are skipped automatically.
	* The resulting serialized data omits these properties entirely.		* The resulting serialized data omits these properties entirely.
-	* Upon <php>unserialize()</php>, all properties present in the serialized payload are restored normally.	+	* When <php>unserialize()</php> encounters such a property in the payload — for example, in data produced by an older version of the class, or by a custom serializer — the value is parsed and discarded, and the property is left untouched. No warning is emitted, since this is precisely the migration case the attribute is expected to handle.
-	* The <php>#[NoSerialize]</php> attribute does not affect deserialization — if a property exists in the serialized data (for example, from an older class version or custom serializer), it will still be deserialized.	+	* Properties that are not restored keep their declared default value, or remain uninitialized if they have no default.
-	* Skipped properties (those not serialized) remain uninitialized if they have no default, or are restored to their declared default value.	+
		+	This symmetry matches the meaning of ''transient'' in Java and ''[NonSerialized]'' in C#: the field is excluded from the serialized representation, not merely from the writing side of it.
		+
		+	It also avoids an injection surface: without it, a property that the class author has explicitly declared to be outside the serialized form could still be populated from an attacker-controlled payload.

	<PHP>		<PHP>
Line 82:		Line 95:

	#[NoSerialize]		#[NoSerialize]
-	public $resource; // transient field	+	public mixed $resource; // transient field

	public function __construct()		public function __construct()
Line 102:		Line 115:
	</PHP>		</PHP>

-	== Interaction with __serialize() and __sleep() ==	+	== Interaction with the serialization magic methods ==

	If a class defines its own serialization logic via <php>__serialize()</php> or <php>__sleep()</php>, the <php>#[NoSerialize]</php> attribute on properties has no effect.		If a class defines its own serialization logic via <php>__serialize()</php> or <php>__sleep()</php>, the <php>#[NoSerialize]</php> attribute on properties has no effect.

-	These methods are entirely user-defined, and PHP does not automatically filter out properties or classes marked with <php>#[NoSerialize]</php>.	+	These methods are entirely user-defined, and PHP does not automatically filter out properties marked with <php>#[NoSerialize]</php>.
	This design maintains explicit and consistent behavior with existing PHP semantics — developer-defined serialization always takes precedence.		This design maintains explicit and consistent behavior with existing PHP semantics — developer-defined serialization always takes precedence.
		+
		+	The same applies to the reading side. <php>__unserialize()</php> receives the payload as a plain array, exactly as written, including any entry whose name matches a property marked with <php>#[NoSerialize]</php>; the engine does not inspect it.
		+
		+	<php>__wakeup()</php> is different, because it is a post-processing hook rather than a format definition: properties are assigned by the engine first — and therefore filtered — and the hook runs afterwards on the resulting object.
		+
		+	^ Path ^ Attribute applied? ^
		+	\| Default serialization and deserialization \| yes \|
		+	\| <php>__serialize()</php> / <php>__sleep()</php> \| no — the return value is used as-is \|
		+	\| <php>__unserialize()</php> \| no — the payload array is passed through untouched \|
		+	\| <php>__wakeup()</php> \| yes — properties are filtered before the hook is invoked \|
		+	\| <php>Serializable</php>, or an internal class with a custom serializer \| no \|

	Example:		Example:
Line 170:		Line 194:
	=== 2.2 Class-level Behavior ===		=== 2.2 Class-level Behavior ===

-	When the <php>#[NoSerialize]</php> attribute is applied to a class, any attempt to serialize an instance of that class will throw an exception, explicitly forbidding its serialization.	+	When the <php>#[NoSerialize]</php> attribute is applied to a class, any attempt to serialize //or unserialize// an instance of that class throws an <php>Exception</php>, explicitly forbidding it.

-	This behavior uses the same internal mechanism as for built-in non-serializable classes (such as <php>Random\Engine\Secure</php> or <php>CurlHandle</php>).	+	This behavior uses the same internal mechanism as for built-in non-serializable classes (such as <php>Random\Engine\Secure</php> or <php>CurlHandle</php>), and therefore the same exception: the base <php>\Exception</php> class, with code 0, and the messages <php>Serialization of 'ClassName' is not allowed</php> and <php>Unserialization of 'ClassName' is not allowed</php>. The exception is catchable; it is not a fatal error.

	This ensures that invalid or unintended serialization attempts are immediately visible to developers and cannot result in partial or lossy data structures.		This ensures that invalid or unintended serialization attempts are immediately visible to developers and cannot result in partial or lossy data structures.
Line 203:		Line 227:

	/*		/*
-	Fatal error: Cannot serialize instance of class Connection marked with #[NoSerialize]	+	Fatal error: Uncaught Exception: Serialization of 'Connection' is not allowed
	*/		*/
	</PHP>		</PHP>

	Notes:		Notes:
-	* Class-level <php>#[NoSerialize]</php> forbids serialization entirely by throwing a fatal error.	+	* Class-level <php>#[NoSerialize]</php> forbids serialization entirely by throwing an <php>Exception</php>.
	* It can be used to mark classes that represent resources, handles, or runtime-only objects.		* It can be used to mark classes that represent resources, handles, or runtime-only objects.
	* This provides a clear and consistent failure mode, identical to the mechanism used for internal non-serializable classes.		* This provides a clear and consistent failure mode, identical to the mechanism used for internal non-serializable classes.
Line 214:		Line 238:
	== Integration with internal classes: ==		== Integration with internal classes: ==

-	* All internal classes currently marked with <php>@not-serializable</php> in their stub metadata will automatically receive the corresponding <php>#[NoSerialize]</php> attribute during code generation.	+	* All internal classes currently marked with <php>@not-serializable</php> in their stub files (107 classes across 64 stubs) are migrated to <php>#[NoSerialize]</php> as part of this RFC, in the same way <php>@deprecated</php> was migrated to <php>#[\Deprecated]</php> in PHP 8.4.
-	* This ensures a consistent reflection view between internal and userland classes and unifies the representation of non-serializable behavior across the ecosystem.	+	* The <php>@not-serializable</php> tag remains supported by ''gen_stub.php'' for third-party extensions and keeps setting the same engine flag, but it does not synthesise the attribute. The relationship is one-way: <php>#[NoSerialize]</php> implies the flag, the tag does not imply the attribute. This mirrors <php>@deprecated</php> and <php>#[\Deprecated]</php> today.
		+	* This gives internal and userland classes the same reflection view of non-serializable behaviour.

	== Inheritance: ==		== Inheritance: ==
Line 281:		Line 306:
	This RFC has no negative impact on existing code and benefits frameworks, static analyzers, and serializers that rely on native PHP serialization.		This RFC has no negative impact on existing code and benefits frameworks, static analyzers, and serializers that rely on native PHP serialization.

-	All internal classes currently marked as <php>@not-serializable</php> in stub files will automatically receive the <php>#[NoSerialize]</php> attribute during stub generation.	+	All internal classes currently marked as <php>@not-serializable</php> in stub files are migrated to the <php>#[NoSerialize]</php> attribute as part of this RFC.
	This ensures consistency between engine-level metadata and reflection-based tooling.		This ensures consistency between engine-level metadata and reflection-based tooling.

-	While this synchronization will occur automatically for internal classes, it is recommended that future userland code and extensions explicitly use the <php>#[NoSerialize]</php> attribute rather than relying on documentation-only annotations.	+	It is recommended that userland code and extensions use the <php>#[NoSerialize]</php> attribute rather than relying on documentation-only annotations.

	==== To Existing Extensions ====		==== To Existing Extensions ====
	This RFC introduces no breaking changes for existing extensions.		This RFC introduces no breaking changes for existing extensions.

-	Extensions that already rely on the internal <php>@not-serializable</php> annotation will transparently benefit from this change — the corresponding <php>#[NoSerialize]</php> attribute will be automatically added to their stub metadata during generation.	+	Extensions that already rely on the <php>@not-serializable</php> annotation keep working unchanged: the tag stays supported and keeps setting the same engine flag. It does not synthesise the attribute, so reflection on those classes will not report <php>#[NoSerialize]</php> until the extension adopts it in its own stubs.

-	Adopting the <php>#[NoSerialize]</php> attribute in extension-defined classes is optional but recommended for consistency with internal and userland code.	+	Adopting the <php>#[NoSerialize]</php> attribute directly in extension-defined stubs is optional but recommended for consistency with internal and userland code.

	==== To SAPIs ====		==== To SAPIs ====
Line 303:		Line 328:

	===== Voting Choices =====		===== Voting Choices =====
-	<doodle title="Implement #[NoSerialize] attribute as outlined in the RFC?" voteType="single" closed="true" closeon="2025-01-01T15:30:00Z">	+
		+	As this is a language change, a 2/3 majority is required.
		+
		+	Voting starts TBD and ends TBD (two weeks later).
		+
		+	<doodle title="Implement #[NoSerialize] attribute as outlined in the RFC?" voteType="single" closed="true" closeon="2027-01-01T00:00:00Z">
	* Yes		* Yes
	* No		* No
-	* Abstain
	</doodle>		</doodle>

Line 323:		Line 352:
	===== Rejected Features =====		===== Rejected Features =====
	* Class-level #[NoSerialize] with replacing value by NULL		* Class-level #[NoSerialize] with replacing value by NULL
		+	* Asymmetric behaviour, where <php>unserialize()</php> restores a property marked with <php>#[NoSerialize]</php> if it is present in the payload

	===== Changelog =====		===== Changelog =====
		+	* v0.9 — 2026-09-07
		+	* Added ecosystem examples to the Introduction (Magento 2, Symfony, Laravel, Doctrine ORM)
		+	* Internal classes are migrated to the attribute explicitly (as done for #[\Deprecated] in 8.4); the @not-serializable tag remains supported for third-party extensions but no longer implies the attribute
		+	* <php>unserialize()</php> now skips properties marked with the attribute instead of restoring them (symmetric semantics, matching ''transient''/''[NonSerialized]'')
		+	* Documented how the attribute interacts with <php>__unserialize()</php> and <php>__wakeup()</php>
		+	* Stated explicitly that class-level <php>#[NoSerialize]</php> also blocks <php>unserialize()</php>, and specified the exception thrown (base \Exception, catchable); corrected the example output
		+	* Fixed the property-level example: an untyped property has an implicit NULL default, so the sample uses <php>mixed</php>
	* v0.8 — Added automatic #[NoSerialize] annotation for internal classes marked as @not-serializable in stubs		* v0.8 — Added automatic #[NoSerialize] annotation for internal classes marked as @not-serializable in stubs
	* v0.7 — Class-level behavior aligned with @not-serializable (now throws instead of serializing as NULL)		* v0.7 — Class-level behavior aligned with @not-serializable (now throws instead of serializing as NULL)

query_params

kocsismate (kocsismate@undisclosed.example.com) — 2026-09-07T12:39:17+00:00

2026/08/01 13:10		current
Line 26:		Line 26:

	public function __construct(		public function __construct(
-	int $parsingMaxQueryStringLength = 10000,	+	int $maxQueryStringLength = 10000,
-	int $parsingMaxParamCount = 1000,	+	int $maxParamCount = 1000,
	) {}		) {}
-
-	public function __debugInfo(): array {}
-
-	public function __serialize(): array {}
-
-	public function __unserialize(array $data): void {}
	}		}

	final readonly class QueryParamBuildingOptions		final readonly class QueryParamBuildingOptions
	{		{
		+	public int $maxNestingLevel;
	public string $trueValue;		public string $trueValue;
	public string $falseValue;		public string $falseValue;
Line 45:		Line 40:
	public function __construct(		public function __construct(
	int $maxNestingLevel = 64,		int $maxNestingLevel = 64,
-	string $trueValue = "0",	+	string $trueValue = "1",
	string $falseValue = "0",		string $falseValue = "0",
	bool $useNullAsEmptyString = false		bool $useNullAsEmptyString = false
	) {}		) {}
-
-	public function __debugInfo(): array {}
-
-	public function __serialize(): array {}
-
-	public function __unserialize(array $data): void {}
	}		}
	}		}
Line 132:		Line 121:
	public function __debugInfo(): array {}		public function __debugInfo(): array {}
	}		}
-	</code>
-
-	<code php>
-	namespace Uri\Rfc3986 {
-	final readonly class Uri
-	{
-	...
-
-	public function getQueryParams(): ?\Uri\QueryParams {}
-
-	...
-	}
-	}
-	</code>
-
-	<code php>
-	namespace Uri\WhatWg {
-	final readonly class Url
-	{
-	...
-
-	public function getQueryParams(): ?\Uri\QueryParams {}
-
-	...
-	}
-	}
	</code>		</code>

Line 351:		Line 314:
	$uri = $uri->withQuery($params->toRfc3986String());		$uri = $uri->withQuery($params->toRfc3986String());

-	echo $uri->getQuery(); // foo=a%20b	+	echo $uri->getQuery(); // foo=a%20b
	</code>		</code>

Line 361:		Line 324:
	$url = new Uri\WhatWg\Url("https://example.com?foo=a%20b"); // "%20b" is the percent-encoded form of "a b"		$url = new Uri\WhatWg\Url("https://example.com?foo=a%20b"); // "%20b" is the percent-encoded form of "a b"

-	$params = $url->getQueryParams();	+	$params = Uri\QueryParams::parseWhatWg($url->getQuery());

	$url = $url->withQuery($params->toWhatWgString());		$url = $url->withQuery($params->toWhatWgString());

-	echo $url->getQuery(); // foo=a+b	+	echo $url->getQuery(); // foo=a+b
	</code>		</code>

Line 431:		Line 394:
	The position of this RFC is that it's important to follow the road that ''http_build_query()'' has already paved because of better developer experience and better interoperability with the existing ecosystem. That's why the following type mapping behavior is proposed when a query parameter is added/updated:		The position of this RFC is that it's important to follow the road that ''http_build_query()'' has already paved because of better developer experience and better interoperability with the existing ecosystem. That's why the following type mapping behavior is proposed when a query parameter is added/updated:

-	* bool: Becomes string "0" (in case of ''false'') or string "1" (in case of ''true'')	+	* null: Omits the query parameter value by default
		+	* bool: Becomes string "0" (in case of ''false'') or string "1" (in case of ''true'') by default
	* int: Becomes a numeric string (123 -> "123")		* int: Becomes a numeric string (123 -> "123")
	* float: Becomes a decimal string (3.14 -> "3.14")		* float: Becomes a decimal string (3.14 -> "3.14")
Line 459:		Line 423:
	</code>		</code>

-	...	+	The default mapping of boolean and ''null'' values can be customized by passing a ''Uri\QueryParamBuildingOptions'' instance to the ''QueryParams'' constructor or its factory methods. The following properties control these conversions:
		+
		+	* ''$trueValue'': The string representation of ''true''. Defaults to ''"1"''.
		+	* ''$falseValue'': The string representation of ''false''. Defaults to ''"0"''.
		+	* ''$useNullAsEmptyString'': Whether ''null'' values are converted to empty strings. Defaults to ''false'', meaning that ''null'' is preserved and represents a parameter without an equals sign or a value.
		+
		+	For example, ''$trueValue'' can be used to represent enabled flags as ''"yes"'':
		+
		+	<code php>
		+	$options = new Uri\QueryParamBuildingOptions(trueValue: "yes");
		+	$params = new Uri\QueryParams($options);
		+	$params = $params->append("enabled", true);
		+
		+	var_dump($params->getFirst("enabled")); // string(3) "yes"
		+	echo $params->toRfc3986String(); // enabled=yes
		+	</code>
		+
		+	Similarly, ''$falseValue'' controls how disabled flags are represented:
		+
		+	<code php>
		+	$options = new Uri\QueryParamBuildingOptions(falseValue: "no");
		+	$params = new Uri\QueryParams($options);
		+	$params = $params->append("enabled", false);
		+
		+	var_dump($params->getFirst("enabled")); // string(2) "no"
		+	echo $params->toRfc3986String(); // enabled=no
		+	</code>
		+
		+	Setting ''$useNullAsEmptyString'' to ''true'' removes the distinction between a ''null'' value and an empty string. The query parameter name is stored in either case, but its value and string representation differ:
		+
		+	<code php>
		+	$options = new Uri\QueryParamBuildingOptions(useNullAsEmptyString: false);
		+	$params = new Uri\QueryParams();
		+	$params = $params->append("flag", null);
		+
		+	var_dump($params->getFirst("flag")); // NULL
		+	echo $params->toRfc3986String(); // flag
		+
		+	$options = new Uri\QueryParamBuildingOptions(useNullAsEmptyString: true);
		+	$params = new Uri\QueryParams($options);
		+	$params = $params->append("flag", null);
		+
		+	var_dump($params->getFirst("flag")); // string(0) ""
		+	echo $params->toRfc3986String(); // flag=
		+	</code>

	For reference, ''http_build_query()'' omits parameters with ''null'' values.		For reference, ''http_build_query()'' omits parameters with ''null'' values.
		+
		+	These conversions happen when PHP values are added or updated, rather than when the query string is recomposed. The building options are stored by ''QueryParams'' instances, so subsequent query parameter modifications use the same mapping rules. The configured strings are treated as ordinary parameter values: they are stored without percent-encoding and encoded when a query string is produced.
		+
		+	The mappings are not applied in reverse. For example, configuring ''$trueValue'' as ''"yes"'' does not cause a parsed ''"yes"'' value to become a PHP boolean. Likewise, passing the string ''"1"'' to ''append()'' does not apply the mapping for the boolean ''true''.
		+
		+	Values without a supported mapping cause a ''ValueError'' to be thrown. Resources, arrays passed directly to ''append()'' or ''set()'', and objects other than backed enum cases are rejected. Objects are not converted implicitly, even if they implement ''Stringable''.
		+
		+	<code php>
		+	enum Flag
		+	{
		+	case Enabled;
		+	}
		+
		+	$params = new Uri\QueryParams();
		+
		+	$params = $params->append("value", fopen("php://memory", "r+")); // Throws ValueError
		+	$params = $params->append("value", ["foo", "bar"]); // Throws ValueError
		+	$params = $params->append("value", Flag::Enabled); // Throws ValueError
		+	</code>
		+
		+	To use the string representation of a ''Stringable'' object, callers must explicitly cast it to a string before passing it as a parameter value. Backed enums do not require an explicit conversion: their backing value is mapped according to the rules for strings and integers.
		+
		+	Rejecting arrays as individual parameter values does not prevent array-based construction. ''fromArray()'' and ''withArray()'' provide a separate API for converting PHP arrays into parameter lists, as described in the following section.

	=== Array API ===		=== Array API ===

rfc - Moved "PREG_THROW_ON_ERRO" back to under discussion

aldemeery (aldemeery@undisclosed.example.com) — 2026-09-07T00:33:00+00:00

2026/09/06 17:15		current
Line 13:		Line 13:
	This section is for RFCs that are currently being voted on.		This section is for RFCs that are currently being voted on.

-	* [[rfc:preg_throw_on_error\|PREG_THROW_ON_ERROR]] (Created 2026-07-28, Discussion started 2026-07-28, Voting started 2026-09-04)	+	* None

	===== Under Discussion =====		===== Under Discussion =====
Line 19:		Line 19:
	This section is for RFCs that have been announced on the PHP "internals" mail list.		This section is for RFCs that have been announced on the PHP "internals" mail list.

		+	* [[rfc:preg_throw_on_error\|PREG_THROW_ON_ERROR]] (Created 2026-07-28, Discussion started 2026-07-28)
	* [[rfc:end_pear_endorsement\|End PEAR Project Endorsement]] (Created 2026-08-27)		* [[rfc:end_pear_endorsement\|End PEAR Project Endorsement]] (Created 2026-08-27)
	* [[rfc:throw_error_for_invalid_characters_for_number_base\|Throw ValueError for invalid characters in number base functions]] (Created 2026-08-11)		* [[rfc:throw_error_for_invalid_characters_for_number_base\|Throw ValueError for invalid characters in number base functions]] (Created 2026-08-11)

preg_throw_on_error - Cancel the vote.

aldemeery (aldemeery@undisclosed.example.com) — 2026-09-07T00:31:54+00:00

2026/09/04 17:09		current
Line 4:		Line 4:
	* Date: 2026-07-28		* Date: 2026-07-28
	* Author: Osama Aldemeery <aldemeery@gmail.com>		* Author: Osama Aldemeery <aldemeery@gmail.com>
-	* Status: Voting	+	* Status: Under Discussion
	* Implementation: https://github.com/php/php-src/pull/22797		* Implementation: https://github.com/php/php-src/pull/22797
	* Discussion thread: https://news-web.php.net/php.internals/132115		* Discussion thread: https://news-web.php.net/php.internals/132115
Line 224:		Line 224:
	Primary Vote requiring a 2/3 majority to accept the RFC:		Primary Vote requiring a 2/3 majority to accept the RFC:

-	<doodle title="Accept PREG_THROW_ON_ERROR as outlined in the RFC?" voteType="single" auth="aldemeery" closeon="2026-09-18T17:00:00Z">	+	<doodle title="Accept PREG_THROW_ON_ERROR as outlined in the RFC? (Restart)" voteType="single" auth="aldemeery" closed="true">
	* Yes		* Yes
	* No		* No

throw_error_for_invalid_characters_for_number_base

sjoerd (sjoerd@undisclosed.example.com) — 2026-09-05T14:51:36+00:00

2026/09/05 14:51		current
Line 34:		Line 34:
	* ''base_convert()'' - Convert a number between arbitrary bases		* ''base_convert()'' - Convert a number between arbitrary bases

-	===== Exception type =====	+	==== Exception type ====

	Originally the plan was to throw a ValueError. However, ValueError implies that the program has a bug, which is not necessarily the case when an invalid character is passed to one of these functions. Therefore, an Exception (as opposed to Error) seems to better fit.		Originally the plan was to throw a ValueError. However, ValueError implies that the program has a bug, which is not necessarily the case when an invalid character is passed to one of these functions. Therefore, an Exception (as opposed to Error) seems to better fit.

surface3d.png - created

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

	current

scaled_on_load_rotate.png - created

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

	current

watermarked.png - created

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

	current

scale_entropy_visual_check.png - created

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

	current

textcurve.png - created

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

1783692513	current

gradient_art.png - created

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

	current

tiger.png - created

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

	current

gradient_operators.png - created

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

	current

coroutine-lifecycle.svg - created

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

	current

supervisor.svg - created

edmond (edmond@undisclosed.example.com) — 2025-03-16T08:38:59+00:00

	current

exception_flow.svg - created

edmond (edmond@undisclosed.example.com) — 2025-03-16T08:38:59+00:00

	current

2026/09/01 16:23		current
Line 20:		Line 20:
	\| Aug 13 2026 \| Beta 1 + Soft feature freeze: all RFCs must have their voting concluded [[https://www.php.net/archive/2026.php#2026-08-13-1\|Announce]] [[https://downloads.php.net/~svpernova09/\|Files]] \|		\| Aug 13 2026 \| Beta 1 + Soft feature freeze: all RFCs must have their voting concluded [[https://www.php.net/archive/2026.php#2026-08-13-1\|Announce]] [[https://downloads.php.net/~svpernova09/\|Files]] \|
	\| Aug 27 2026 \| Beta 2 [[https://www.php.net/archive/2026.php#2026-08-27-1\|Announce]] [[https://downloads.php.net/~mbeccati/\|Files]] \|		\| Aug 27 2026 \| Beta 2 [[https://www.php.net/archive/2026.php#2026-08-27-1\|Announce]] [[https://downloads.php.net/~mbeccati/\|Files]] \|
-	\| Sep 10 2026 \| Beta 3 \|	+	\| Sep 10 2026 \| Beta 3 [[https://www.php.net/archive/2026.php#2026-09-10-1\|Announce]] [[https://downloads.php.net/~svpernova09/\|Files]] \|
	\| Sep 22 2026 \| Hard feature freeze: features, whether requiring an RFC or not, must be merged only with approval from the RMs. \|		\| Sep 22 2026 \| Hard feature freeze: features, whether requiring an RFC or not, must be merged only with approval from the RMs. \|
	\| Sep 24 2026 \| RC1 \|		\| Sep 24 2026 \| RC1 \|