Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:25900
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 64.233.182.188 as permitted sender)
DomainKey-Status: good
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:sender:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition:x-google-sender-auth;
        b=REYyJkf//PyEIKmWscU+c3827tTtwgmi+BVDk8p2GyYrJhBCPr7dFnB1rLU9HAb/3G6zunwierNpW1dJ7NrAgYV9ewiGQ2s/X9PY3G03u1IptWnUszB4ifFeI4cQOKPpG/IooJ5GoTnr6ELnKM/ru1mTEKbi02rpw1qdSgnVBDE=
Message-ID: <28139bc0610010448x61445c4fg19c8ad08bcb5ddc2@mail.gmail.com>
Date: Sun, 1 Oct 2006 19:48:46 +0800
Sender: xuefer@gmail.com
To: internals@lists.php.net
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Subject: issue of current E_STRICT implemention and possible solution
From: phpxcache@gmail.com (phpxcache)

the E_STRICT is an error type that issued at compile-time. and user
error handler is called, switching to runtime. mixing
runtime/compile-time is imho, not good, and cause problem in the real
world.

the flow:
script, include -> compiling, issue E_STRICT -> user error handler.

official bug:
1. set up user error handler
2. issue E_STRICT inside class compiling

function my_error_handler()
{
   include_once "debugger.class.php"; // #1
   $dbg = Debugger::getInstance();
   ...
}

is the behavior defined at point #1 ? if it is allowed, what if wrote
"class Debugger { ..." into debugger.class.php ? it just tell me "u
cannot declare class inside another class" (something like this)

3rd party bug:
XCache is doing nice on late class binding by building "compiler
sandbox" for ZendEngine, which clear class_table/function_table
temporarily, to make the compiler-env exactly the same every time.

but inside the sandbox, functions/classes defined before compiling, is
never exists inside the compile-time, leading to a "undefined
function" or "undefined class" error inside user error handler.

yes, the author should hack, but it's better done in php-src or ZendEngine side.

solution propose:
1. never call user error handler for E_STRICT
2. add E_STRICT to pending list and issue it after compiling. (after
returning from compile_file)