Doc #73925 [Ver->Asn]: BC break on array overriding declared string

Edit report at https://bugs.php.net/bug.php?id=73925&edit=1 ID: 73925 Updated by: kalle@php.net Reported by: zoeslam at gmail dot com Summary: BC break on array overriding declared string -Status: Verified +Status: Assigned Type: Documentation Problem Package: Scripting Engine problem Operating System: Linux PHP Version: 7.1.0 Assigned To: cmb Block user comment: N Private report: N Previous Comments: ------------------------------------------------------------------------ [2017-01-14 10:53:48] zoeslam at gmail dot com *hope ------------------------------------------------------------------------ [2017-01-14 10:52:20] zoeslam at gmail dot com I think that consistency is important, and the fact that the variable ends in a weird state (string "A") is very misleading. In the next days I'm going to write an RFC, and I hoe it could be merged in 7.1 ------------------------------------------------------------------------ [2017-01-13 18:39:04] cmb@php.net > Ok, but the doc talk about a fatal error, here instead there is > only an E_NOTICE, a huge difference. Indeed, and that has to be documented in the PHP manual and also in UPGRADING. > May we uniform the behaviour to always raise a fatal error? I don't think that would make sense, but feel free to start the RFC process, see <https://wiki.php.net/rfc/howto>. :-) ------------------------------------------------------------------------ [2017-01-13 15:02:42] zoeslam at gmail dot com Ok, but the doc talk about a fatal error, here instead there is only an E_NOTICE, a huge difference. May we uniform the behaviour to always raise a fatal error? ------------------------------------------------------------------------ [2017-01-13 14:28:45] nikic@php.net Correct. The linked section currently only refers to the []= operation, while the same also applies to any [X]=. ------------------------------------------------------------------------ The remainder of the comments for this report are too long. To view the rest of the comments, please view the bug report online at https://bugs.php.net/bug.php?id=73925 -- Edit this bug report at https://bugs.php.net/bug.php?id=73925&edit=1