- Initial support for class constants. There are still a few semantic
- issues which need to be looked into but basically it seems to work.
- Example:
<?php
class foo

- Initial support for class constants. There are still a few semantic
- issues which need to be looked into but basically it seems to work.
- Example:
<?php
class foo
{
const hey = "hello";
}

print foo::hey;
?>

show more ...

- Support static members. The following script works:
<?
class foo
{
class bar
{
function init_values()

- Support static members. The following script works:
<?
class foo
{
class bar
{
function init_values()
{
for ($i=1; $i<10; $i++) {
foo::bar::$hello[$i] = $i*$i;
}
}

function print_values()
{
for ($i=1; $i<10; $i++) {
print foo::bar::$hello[$i] . "\n";
}
}
}
}

foo::bar::init_values();
foo::bar::print_values();

for ($i=1; $i<10; $i++) {
print $hello[$i]?"Shouldn't be printed\n":"";
}
?>

show more ...

- Fix internal classes

- Initial support for nested class definitions

More TSRMLS_FETCH work

Avoid TSRMLS_FETCH()'s (still lots of work left)

Redesigned thread safety mechanism - nua nua

Improved interactive mode - it is now available in all builds, without any significant slowdown

- Fix crash bug when opcodes array is erealloc()'ed to a different memory
area before it reaches the loop.
- Some whitespace stuff

- Fix crash bug reported by DBG author Dmitri Dmitrienko.

- Update copyright year

Fix possible corruption in line number information

- Beautify by using the standard #define.

- Increase op_array size faster and make eralloc() it in the end to save
memory.

The patch we promised - redesigned the compilation/execution API:
Advantages:
- Smaller memory footprint for the op arrays
- Slightly faster compilation times (due to saved erealloc() cal

The patch we promised - redesigned the compilation/execution API:
Advantages:
- Smaller memory footprint for the op arrays
- Slightly faster compilation times (due to saved erealloc() calls and faster zend_op
initialization)
- include_once() & require_once() share the same file list
- Consistency between include() and require() - this mostly means that return()
works inside require()'d files just as it does in include() files (it used to
be meaningless in require()'d files, most of the time (see below))
- Made require() consistent with itself. Before, if the argument was not a constant
string, require() took the include() behavior (with return()).
- Removed lots of duplicate code.
Bottom line - require() and include() are very similar now; require() is simply an include()
which isn't allowed to fail. Due to the erealloc() calls for large op arrays, require()
didn't end up being any faster than include() in the Zend engine.

show more ...

Fix order

Thoroughly initialize IS_UNUSED for proper cleanup

Pass the op_array to the ctor/dtor, instead of just the resource

Fix possible bug with extension dtors being called without the ctors being called first

Beautify

- Export pass_include() for Windows

Added !== (is not identical) operator.

- Include Andrea's fix for alloca.h

fix cast

- Some header dependencies cleanup
- Generalize zval_print() and zval_print_r()