Skip to content

[Sync-En] ext/intl: correct the 8.4.0 Error normalization, it only concerns cloning #1203

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
PhilDaiguille merged 1 commit into from
Sep 1, 2026
+21 −8
Merged

[Sync-En] ext/intl: correct the 8.4.0 Error normalization, it only concerns cloning #1203

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 8 additions & 5 deletions appendices/migration84/other-changes.xml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,5 @@
<?xml version="1.0" encoding="utf-8"?>
<!-- EN-Revision: 858400b07586b88dcb1e17a95e7a178b54b89d86 Maintainer: PhilDaiguille Status: ready -->
<!-- Reviewed: yes -->
<!-- EN-Revision: 66bf3dcc3870f91bda607fe90717a8291d195236 Maintainer: PhilDaiguille Status: ready -->
<sect1 xml:id="migration84.other-changes">
<title>Otros cambios</title>

Expand Down Expand Up @@ -548,9 +547,13 @@
<title>Intl</title>

<simpara>
El comportamiento de la clase Intl se ha normalizado para siempre lanzar
excepciones <exceptionname>Error</exceptionname> al intentar usar
un objeto no inicializado, o cuando la clonación falla.
La clonación de un objeto Intl lanza sistemáticamente un
<exceptionname>Error</exceptionname> cuando la clonación no puede
realizarse, ya sea porque el objeto no ha sido inicializado, o porque la
operación de clonación subyacente de ICU ha fallado. Anteriormente, la
mayoría de estas clases lanzaban una
<exceptionname>Exception</exceptionname> en su lugar, y
<classname>Spoofchecker</classname> emitía un error fatal.
</simpara>
</sect3>

Expand Down
16 changes: 13 additions & 3 deletions reference/intl/book.xml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,7 +1,5 @@
<?xml version="1.0" encoding="utf-8"?>
<!-- $Revision$ -->
<!-- EN-Revision: a03f9eda2d45b725f75b4d6a1a22e8aec63e157a Maintainer: PhilDaiguille Status: ready -->
<!-- Reviewed: no -->
<!-- EN-Revision: 66bf3dcc3870f91bda607fe90717a8291d195236 Maintainer: PhilDaiguille Status: ready -->
<!-- CREDITS: DAnnebicque -->

<book xml:id="book.intl" xmlns="http://docbook.org/ns/docbook" xmlns:xlink="http://www.w3.org/1999/xlink">
Expand Down Expand Up @@ -100,6 +98,18 @@
</listitem>
</itemizedlist>

<note>
<simpara>
A partir de PHP 8.4.0, la clonación de un objeto Intl lanza
sistemáticamente un <exceptionname>Error</exceptionname> cuando la clonación
no puede realizarse, ya sea porque el objeto no ha sido inicializado (creado
sin invocar su constructor), o porque la operación de clonación subyacente
de ICU ha fallado. Anteriormente, la mayoría de estas clases lanzaban una
<exceptionname>Exception</exceptionname> en su lugar, y
<classname>Spoofchecker</classname> emitía un error fatal.
</simpara>
</note>

<!-- {{{ Enlaces -->
<section xml:id="intl.links">
<title>Enlaces</title>
Expand Down