- Nuke const in function parameters. I just can't remember why this exists
- and it seems no one else remembers either. It has no semantic meaning.

Allow foo::$bar()

ntroduce infrastructure for supplying information about arguments,
including:

- Whether or not to pass by ref (replaces the old arg_types, with arg_info)
- Argument name (for future

ntroduce infrastructure for supplying information about arguments,
including:

- Whether or not to pass by ref (replaces the old arg_types, with arg_info)
- Argument name (for future use, maybe introspection)
- Class/Interface name (for type hints)
- If a class/interface name is available, whether to allow a null instance

Both user and builtin functions share the same data structures.

To declare a builtin function that expects its first arg to be an instance
of class 'Person', its second argument as a regular arg, and its third by
reference, use:

ZEND_BEGIN_ARG_INFO(my_func_arg_info, 0)
ZEND_ARG_OBJ_INFO(0, someone, Person, 1)
ZEND_ARG_PASS_INFO(0)
ZEND_ARG_PASS_INFO(1)
ZEND_END_ARG_INFO();

and use my_func_arg_info as the arg_info parameter to the ZEND_FE() family
of macros.

The first arg to each ZEND_ARG_*() macro is whether or not to pass by ref.

The boolean arg to ZEND_BEGIN_ARG_INFO() tells the engine whether to treat
the arguments for which there's no explicit information as pass by reference
or not.
The boolean argument to ZEND_ARG_OBJ_INFO() (4th arg) is whether or not to allownull values.

show more ...

Support references in foreach()
Syntax:
foreach ($arr as &$val)
foreach ($arr as $key => &$val)

Fix complex expressions for class names in NEW

Simplify

WS

Add final classes

Fix bug #23384 - static class::constant constants should now
work in static & array expressions.

updating license information in the headers.

Fix bogus implicit declarations of properties (squash bug #23671)

MEGA-patch: namespaces are R.I.P.

Fix ~ operator in class constants.

allow expressions within constants, so the following is possible

class foo {
const a = 1<<0;
const b = 1<<1;
const c = a | b;
}

this makes co

allow expressions within constants, so the following is possible

class foo {
const a = 1<<0;
const b = 1<<1;
const c = a | b;
}

this makes const a compile-time expression. all other operators are
unaffected.

show more ...

Revert Harald's commit

One line fix so that it will compile

removing the *syntactical sugar* again

# commiting that on behalf of the community :)
# don't blame me, i'm just acting as a proxy

Implement a different way to catch documentation comments.

Revert portions of the doc comment patch. There should be no parser
errors now.

Add __NAMESPACE__ auto-constant.

Multi-purpose patch:
- The fields of zend_namespace were not completely initialized which
led to a variety of problems.
- The occurrence of class/interface/namespace definition is no

Multi-purpose patch:
- The fields of zend_namespace were not completely initialized which
led to a variety of problems.
- The occurrence of class/interface/namespace definition is now
captured.
- Functions/classes/interfaces/namespaces can be preceded by doc
comments which are stored for use by extensions.

show more ...

Since zend_do_begin_class_member_function_call assumes the previous
opcode is FETCH_CONSTANT, swap the calls around.

Un-nest namespaces - now namespace X { namespace Y {} } is a parse error
Also refine namespaced includes

- Keep track of starting/ending line numbers for user functions.
- Store last parsed doc comment in a compiler global for future use.

Optimize