|  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login
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
Welcome! If you don't have a Git account, you can't do anything here.
You can add a comment by following this link or if you reported this bug, you can edit this bug over here.
Block user comment
Status: Assign to:
Bug Type:
From: rh at tfli dot co dot uk
New email:
PHP Version: OS:


 [2021-09-07 16:34 UTC] rh at tfli dot co dot uk
(Sorry if this is 'too early' and will be addressed prior to release anyway)
At present, and 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.


Add a Patch

Pull Requests

Add a Pull Request


AllCommentsChangesGit/SVN commitsRelated reports
 [2021-09-07 20:41 UTC]
-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]
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. 

 [2021-09-14 13:36 UTC]
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