Remove namespace leftovers

- ZE coding style requires if ( instead of if(

updating license information in the headers.

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

Bugfix #23670: implements and extends cause Apache 2 crash

Patch by Marcus Börger to fix some memleaks

Split ZEND_NAMESPACE into user and internal namespaces. Hope this is
okay with engine folks.

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 ...

Eliminate TSRMLS_FETCH() calls in destroy_op_array() and zend_get_class_entry().

Add support for interfaces

Allow namespaces to have a number of parts. I.e., now you can do:
namespace foo {
function abc() {}
}
...
namespace foo {
functio def() {}
}

Avoid using a C++ reserved word

Namespace patch. Big changes:
1. Nested classes are gone.
2. New syntax for namespaces:
namespace foo {
class X { ... }
function bar { ... }
var x = 1;

Namespace patch. Big changes:
1. Nested classes are gone.
2. New syntax for namespaces:
namespace foo {
class X { ... }
function bar { ... }
var x = 1;
const ZZ = 2;
}
3. Namespaced symbol access: $x = new foo::X; - etc.
For now, namespaces are case insensitive, just like classes.
Also, there can be no global class and namespace with the same name
(to avoid ambiguities in :: resolution).

show more ...

Rework static class properties - now supports access restrictions

Reimplement PPP properties

- Added some missing CVS $Id$ tags, headers and footers.

Add additional stage to post-session cleanup.
We need separate cleanup stage because of the following problem:
Suppose we destroy class X, which destroys function table,
and in function t

Add additional stage to post-session cleanup.
We need separate cleanup stage because of the following problem:
Suppose we destroy class X, which destroys function table,
and in function table we have function foo() that has static $bar. Now if
object of class X was assigned to $bar, its destructor will be called and will
fail since X's function table is in mid-destruction.
So we want first of all to clean up all data and then move to tables
destruction.
Note that only run-time accessed data need to be cleaned up, pre-defined
data can not contain objects and thus are not probelmatic.
# Looks like we are having a lots of pain in the various parts of the body
# because of the destructors...

show more ...

Bump year.

h WHitespace

- Also tune jmpz_ex

- Improve performance of part of the jmps. More to follow.

- Improve opcode dispatching

- Commit patch to support protected member variables (by Timm Friebe w/
- some fixes by me).
- You can't access protected variables from outside the object. If you want
- to see a protect

- Commit patch to support protected member variables (by Timm Friebe w/
- some fixes by me).
- You can't access protected variables from outside the object. If you want
- to see a protected member from your ancestors you need to declare the
- member as protected in the class you want to use it in. You can't
- redeclare a protected variable as private nor the other way around.

show more ...

some type cleanup work

- Fix issues with $this when using it by itself without indirection such as
- $this->foo.