Port break/continue

Port throw

ZEND_SEND_VAR and ZEND_SEND_VAL specialization

Port echo

Port return statement

Fix ZTS build

Use zend_string* in some places

Refactor class name resolution as well

Hack around global leak for now

Suppress warning "cast from pointer to integer of different size"

Refactored parameter passing mechanism.

In PHP-5.6 and below each argument passed to user function was copies on VM stack twice.
Now we always have ZEND_INIT_FCALL (or simular) opcode th

Refactored parameter passing mechanism.

In PHP-5.6 and below each argument passed to user function was copies on VM stack twice.
Now we always have ZEND_INIT_FCALL (or simular) opcode that pushes "call frame" on top of VM stack.
"Call frame" is actually the same zend_execute_data structure.
All the following ZEND_SEND instructions push arguments on top of the stack in a way that they directly comes into corresponding CV variables of the called frame. Extra arguments are copied at the end of stack frame (after all CV and TMP variables) on function enterance.

There are two minor incompatibilities:
1) It's not allowed to decalre functions redefining arguments e.g. "function foo($a,$a) {}".
2) func_get_arg() and func_get args() return the current value of argument and not the original value that was sent.

show more ...

Some refactoring of fn/const resolution

Drop addition of weird \ prefix for FQ consts

Also fixes a resolution bug

Rename ZEND_CONST to ZEND_AST_ZVAL

Drop dead code

Remove obseleted grammar productions

Reuse expr for static_scalar

Handle ::class in const expr via ast as well

Compile const refs to CONST

Compile class const refs to CONST zval

Add compilation state for static scalars

Const eval unary pm (as previously)

Implement constant expression folding as a separate pass

Implement CT eval of binary expressions

I totally hate this approach. It's ugly and I don't think I can
share code with the static scalar evaluation. Maybe I should use
the approach

Implement CT eval of binary expressions

I totally hate this approach. It's ugly and I don't think I can
share code with the static scalar evaluation. Maybe I should use
the approach that static scalars use instead?

show more ...

Support string interpolation