php.net |  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login

go to bug id or search bugs for

Doc Bug #81423 UPGRADING doesn't mention that readonly becomes a reserved keyword
Submitted: 2021-09-07 16:34 UTC Modified: 2021-09-14 13:36 UTC
From: rh at tfli dot co dot uk Assigned:
Status: Open Package: Documentation problem
PHP Version: 8.1.0RC1 OS: Windows 10 (64Bit)
Private report: No CVE-ID: None
View Add Comment Developer Edit
Have you experienced this issue?
Rate the importance of this bug to you:

 [2021-09-07 16:34 UTC] 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.

Patches

Add a Patch

Pull Requests

Add a Pull Request

History

AllCommentsChangesGit/SVN commitsRelated reports
 [2021-09-07 20:41 UTC] dharman@php.net
-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
 [2021-09-07 20:41 UTC] dharman@php.net 
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
 [2021-09-14 13:36 UTC] cmb@php.net 
FTR, the PR has been applied.
 
PHP Copyright © 2001-2021 The PHP Group
All rights reserved. 		Last updated: Mon Oct 18 18:03:40 2021 UTC