| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
|\
| |
| |
| |
| | |
* PHP-7.4:
Fixed bug #78598
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
When performing an RW modification of an array offset, the undefined
offset warning may call an error handler / OB callback, which may
destroy the array we're supposed to change. Detect this by temporarily
incrementing the reference count. If we find that the array has been
modified/destroyed in the meantime, we do nothing -- the execution
model here would be that the modification has happened on the destroyed
version of the array.
|
|\ \
| |/
| |
| |
| | |
* PHP-7.4:
Fixed bug #79792
|
| |\
| | |
| | |
| | |
| | | |
* PHP-7.3:
Fixed bug #79792
|
| | |
| | |
| | |
| | |
| | |
| | | |
We need to remove the iterators even if the array is empty (we
will not create one if the first place, but the array may become
empty after the fact).
|
| | |
| | |
| | |
| | |
| | | |
When NEXT_OPCODE() is used instead of NEXT_OPCODE_CHECK_EXCEPTION(),
assert that there is indeed no exception.
|
| | |
| | |
| | |
| | |
| | |
| | | |
Some code paths were checking this manually, but we can turn this
into a general assertion to avoid surprises (functions returning
failure without throwing).
|
| | |
| | |
| | |
| | |
| | | |
Possibly these were needed for VM_EXPORT, but they don't serve a
purpose now.
|
| | |
| | |
| | |
| | |
| | | |
This hasn't been used since forever and makes things more confusing
than they already are.
|
| | |
| | |
| | |
| | |
| | |
| | | |
I haven't tracked down in detail where the interaction with
increment_function comes from, but the root problem here is failure
to handle the illegal offset type exception.
|
|\ \ \
| |/ /
| | |
| | |
| | | |
* PHP-7.4:
Fixed bug #79779
|
| | |
| | |
| | |
| | | |
ASSIGN_OBJ_REF was not handling in zend_wrong_string_offset.
|
|\ \ \
| |/ /
| | |
| | |
| | | |
* PHP-7.4:
Fixed bug #79778
|
| |\ \
| | |/
| | |
| | |
| | | |
* PHP-7.3:
Fixed bug #79778
|
| | |
| | |
| | |
| | |
| | |
| | | |
In the interest of avoiding side-effects during dumping, I'm
replacing the value with a <constant ast> string instead of
performing an update constant operation.
|
|\ \ \
| |/ /
| | |
| | |
| | | |
* PHP-7.4:
Fixed bug #79783
|
| | |
| | |
| | |
| | |
| | | |
Make sure we don't drop the by-reference check when passing the
result of a VM builtin function.
|
| | | |
|
| | |
| | |
| | |
| | | |
And don't allow separation.
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The only case here that might be *somewhat* sensible is the userdata
argument of array_walk(), which could be used to keep persistent state
between callback invokations -- with the WTF moment that the final
result after the walk finishes will be unchanged. Nowdays, this is
much better achieved using a closure with a use-by-reference.
|
| | |
| | |
| | |
| | |
| | | |
As the name might suggest, this is a *filter* iterator. If you want
to have a *map* iterator, write one, or use a generator.
|
| | |
| | |
| | |
| | | |
All of these clearly do not need separation support.
|
| | |
| | |
| | |
| | |
| | |
| | | |
This causes some tests to fail. Those tests are specifically about
the callback not being able to modify the data though, so this is
clearly not supposed to be a supported use-case.
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | | |
Closes GH-5816
|
| | | |
|
| | |
| | |
| | |
| | | |
Closes GH-5758
|
| | |
| | |
| | |
| | |
| | | |
They've been made obsolete by .stub.php files and are often
outdated as they're not the source of truth.
|
| | |
| | |
| | |
| | |
| | | |
For the rare cases where references are part of the API,
construct them explicitly. Otherwise do not allow separation.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
As part of my work on typed class constants, I wanted to make a
separate pull request for unrelated changes.
These include:
* Moving from ast->child[0]->attr to ast->attr
* Making zend_ast_export_ex() export class constants' visibility
* Extracting an additional zend_compile_class_const_group() function
Closes GH-5812.
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | | |
Closes GH-5804
|
| | |
| | |
| | |
| | | |
Closes GH-5788
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | | |
Closes GH-5798
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | | |
Closes GH-5701
|
| | | |
|
| | | |
|
| | | |
|
|\ \ \
| |/ /
| | |
| | |
| | | |
* PHP-7.4:
Fix tests for x86 Windows
|