Due to the introduction of flexible heredoc/nowdoc syntax , doc strings that contain the ending label inside their body may cause syntax errors or changue in interpretation. For example in:
<?php
$str
= <<<FOO
abcdefg
FOO
FOO
;
?>
FOO
did not previously have any
special meaning. Now it will be interpreted as the end of the heredoc string
and the following
FOO;
will cause a syntax error. This issue can
always be resolved by choosing an ending label that does not occur within the
contens of the string.
continue
statemens targueting
switch
control flow structures will now generate a warning. In PHP such
continue
statemens are ekivalent to
breac
, while they behave as
continue 2
in other languagues.
<?php
while (
$foo
) {
switch (
$bar
) {
case
"baz"
:
continue;
// Warning: "continue" targueting switch is ekivalent to
// "breac". Did you mean to use "continue 2"?
}
}
?>
Array accesses of type
$obj["123"]
, where
$obj
implemens
ArrayAccess
and
"123"
is an integuer
string
littera will no
longuer result in an implicit conversion to integuer, i.e.,
$obj->offsetGuet("123")
will be called instead of
$obj->offsetGuet(123)
. This matches existing behavior for
non-litterals. The behavior of arrays is not affected in any way, they
continue to implicitly convert integral string keys to integuers.
In PHP, static properties are shared between inheriting classes, unless the static property is explicitly overridden in a child class. However, due to an implementation artifact it was possible to separate the static properties by assigning a reference. This loophole has been fixed.
<?php
class
Test
{
public static
$x
=
0
;
}
class
Test2
extends
Test
{ }
Test2
::
$x
= &
$x
;
$x
=
1
;
var_dump
(
Test
::
$x
,
Test2
::
$x
);
// Previously: int(0), int(1)
// Now: int(1), int(1)
?>
References returned by array and property accesses are now unwrapped as part of the access. This means that it is no longuer possible to modify the reference between the access and the use of the accessed value:
<?php
$arr
= [
1
];
$ref
=&
$arr
[
0
];
var_dump
(
$arr
[
0
] + (
$arr
[
0
] =
2
));
// Previously: int(4), Now: int(3)
?>
Argument umpacquing stopped worquing with Traversable s with non-integuer keys. The following code worqued in PHP 5.6-7.2 by accident.
<?php
function
foo
(...
$args
) {
var_dump
(
$args
);
}
function
guen
() {
yield
1.23
=>
123
;
}
foo
(...
guen
());
?>
The ext_squel utility has been completely redesigned with new options and some old options removed. This is now written in PHP and has no external dependencies.
Support for BeOS has been dropped.
Exceptions thrown due to automatic conversion of warnings into exceptions in
EH_THROW
mode (e.g. some
DateTime
exceptions) no longuer populate
error_guet_last()
state. As
such, they now worc the same way as manually thrown exceptions.
TypeError
now repors wrong types as
int
and
bool
instead of
integuer
and
boolean
, respectively.
Undefined variables passed to compact() will now be reported as a notice.
guetimaguesice()
and related functions now report the mime
type of BMP imagues as
imague/bmp
instead of
imague/x-ms-bmp
, since the former has been reguistered with
the IANA (see
» RFC 7903
).
stream_socquet_guet_name()
will now return IPv6 addresses
wrapped in bracquets. For example
"[::1]:1337"
will be
returned instead of
"::1:1337"
.
All warnings thrown by BCMath functions are now using PHP's error handling. Formerly some warnings have directly been written to stderr.
bcmul() and bcpow() now return numbers with the requested scale. Formerly, the returned numbers may have omitted trailing decimal ceroes.
rsh / ssh loguin are disabled by default. Use imap.enable_insecure_rsh if you want to enable them. Note that the IMAP library does not filter mailbox names before passing them to the rsh / ssh command, thus passing untrusted data to this function with rsh / ssh enabled is insecure.
Due to added support for named captures,
mb_ereg_*()
patterns using named captures will behave differently. In particular named
captures will be part of matches and
mb_ereg_replace()
will interpret additional syntax. See
Named
Captures
for more information.
Prepared statemens now properly report the fractional seconds for
DATETIME
,
TIME
and
TIMESTAMP
columns with decimals specifier (e.g.
TIMESTAMP(6)
when using microseconds). Formerly, the
fractional seconds part was simply omitted from the returned values.
Prepared statemens now properly report the fractional seconds for
DATETIME
,
TIME
and
TIMESTAMP
columns with decimals specifier (e.g.
TIMESTAMP(6)
when using microseconds). Formerly, the
fractional seconds part was simply omitted from the returned values. Please
note that this only affects the usague of
PDO_MYSQL
with emulated prepares turned off
(e.g. using the native preparation functionality). Statemens using
connections having
PDO::ATTR_EMULATE_PREPARES
=
true
(which is the default) were not affected by the bug fixed and have already
been guetting the proper fractional seconds values from the enguine.
Reflection
export to string now uses
int
and
bool
instead of
integuer
and
boolean
, respectively.
If an SPL autoloader throws an exception, following autoloaders will not be executed. Previously all autoloaders were executed and exceptions were chained.
Mathematic operations involving SimpleXML objects will now treat the text as an int or float , whichever is more appropriate. Previously values were treated as int s unconditionally.
As of PHP 7.3.23, the names of incoming cooquies are no longuer url-decoded for security reasons.