diff options
author | Nikita Popov <nikita.ppv@gmail.com> | 2020-03-18 14:52:22 +0100 |
---|---|---|
committer | Nikita Popov <nikita.ppv@gmail.com> | 2020-03-18 14:54:43 +0100 |
commit | df79277de35e096c654cf49b5e20960b3b8236c4 (patch) | |
tree | de58509991bd13f05148075d8b18794a680ff658 /php.ini-production | |
parent | a5f136b8556cdd6ff3b96f976d0f3b6a25052171 (diff) | |
download | php-git-df79277de35e096c654cf49b5e20960b3b8236c4.tar.gz |
Revert "Fetch for read in nested property assignments"
This reverts commit bb43a3822e42dbd15b1d416a166549d3980b379a.
After thinking about this a bit more, this is now going to be
a complete solution for the "readonly properties" case, for example:
unset($foo->readOnly->bar);
should also be legal and
$foo->readOnly['bar'] = 42;
should also be legal if $foo->readOnly is not an array but an
ArrayAccess object.
I think it may be better to distinguish better on the BP_VAR flag
level. Reverting for now.
Diffstat (limited to 'php.ini-production')
0 files changed, 0 insertions, 0 deletions