Doc #81423 [Opn]: UPGRADING doesn't mention that readonly becomes a reserved keyword
Edit report at https://bugs.php.net/bug.php?id=81423&edit=1
ID: 81423
Updated by: dharman@php.net
Reported by: rh at tfli dot co dot uk
-Summary: Crash in mysqlnd_fetch_stmt_row_cursor when calling
an SP with a cursor
+Summary: UPGRADING doesn't mention that readonly becomes a
reserved keyword
Status: Open
Type: Documentation Problem
Package: Documentation problem
Operating System: Windows 10 (64Bit)
PHP Version: 8.1.0RC1
Block user comment: N
Private report: N
New Comment:
Thanks. There is a PR[1] to change this, so I think it's a good idea to wait with documenting
the exact behaviour. The UPGRADING file can still be changed if it contains missing information. The
documentation pages haven't been created yet to my knowledge.
[1]: https://github.com/php/php-src/pull/7468
Previous Comments:
------------------------------------------------------------------------
[2021-09-07 16:34:16] rh at tfli dot co dot uk
Description:
------------
(Sorry if this is 'too early' and will be addressed prior to release anyway)
At present, https://github.com/php/php-src/blob/php-8.1.0RC1/NEWS
and https://github.com/php/php-src/blob/php-8.1.0RC1/UPGRADING
mention the new 'readonly properties' feature under new features, but don't mention
under 'Backward Incompatible Changes' that readonly can't be used as a class/function
name/etc.
------------------------------------------------------------------------
--
Edit this bug report at https://bugs.php.net/bug.php?id=81423&edit=1
Thread (4 messages)