Antony Dovgal's error message improvement - #27290

- Roll back VM commit

- Some architectural changes:
a) We specialize opcodes according to op_type fields. Each opcode has to
be marked with which op_type's it uses.
b) We support different execution meth

- Some architectural changes:
a) We specialize opcodes according to op_type fields. Each opcode has to
be marked with which op_type's it uses.
b) We support different execution methods. Function handlers, switch()
and goto dispatching. goto seems to be the fastest but it really
depends on the compiler and how well it optimizes. I suggest playing
around with optimization flags.

- Warning: Things might break so keep us posted on how things are going.
(Dmitry, Andi)

show more ...

fix crash #29893

String offset starts with 0, fix isset($str[$len])

- Cleanup

- Stop using garbage. Please let me know if you find any bugs resulting
- of this patch (very likely). (Dmitry, Andi)

- Don't use magic numbers

- Significantly improve performance of foreach($arr as $data). (Marcus)

More meaningfull error message

- Fix warnings

A gentler (performance wise) allocation of buffer for temp variables.

- More ptr_stack optimizations and cleanups

- Improve performance by inlining zend_ptr_stack_n_push(). var_args can
usually not be inlined by compilers.

Revert goto opcode

&tmp and label are the same thing, don't free it till we're done with it.

Plug some memory leaks and promote unknown label to E_ERROR.
If someone tries to jump to a non-existant label execution really
shouldn't try to carry on.

Add goto operator by popular request.

- Fix bug #29368 : The destructor is called when an exception is thrown from the constructor

Fix 0 Byte leak after alloca to emalloc change

- Nuke empty_string. It is a reminanent from the time where RETURN_FALSE()
used to return "" and not bool(false). It's not worth keeping it because
STR_FREE() and zval_dtor() always have

- Nuke empty_string. It is a reminanent from the time where RETURN_FALSE()
used to return "" and not bool(false). It's not worth keeping it because
STR_FREE() and zval_dtor() always have to check for it and it slows down
the general case. In addition, it seems that empty_string has been abused
quite a lot, and was used not only for setting zval's but generally in
PHP code instead of "", which wasn't the intention. Last but not least,
nuking empty_string should improve stability as I doubt every place
correctly checked if they are not mistakenly erealloc()'ing it or
calling efree() on it.
NOTE: Some code is probably broken. Each extension maintainer should
check and see that my changes are OK. Also, I haven't had time to touch
PECL yet. Will try and do it tomorrow.

show more ...

Bugfix #28464 catch() does not catch exceptions by interfaces

Fixed bug #29086 & #28064 (PHP crashes on extremly long scripts).

Ease off on severity of new error (Using Resources as array offsets)

BugFix #28879 Inconsistent behavior between explicit and implicit array creation.

Changes:

Throw E_WARNING "Illegal offset type" when explicitly creating
array elements with ob

BugFix #28879 Inconsistent behavior between explicit and implicit array creation.

Changes:

Throw E_WARNING "Illegal offset type" when explicitly creating
array elements with objects, arrays, or resorces as indexes.
This matches implicit creation w/ obj/arr indices.

Throw E_WARNING "Resource ID#%ld used as offset, casting to integer (%ld)"
when implicitly creating array with resource as index. (BC)

show more ...