Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:23854
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Message-ID: <003501c6859c$a5b988b0$88051fac@OHRLVN4523SG>
To: <boards@gmail.com>
Cc: <internals@lists.php.net>
References: <447F154F.6070009@gmail.com>
Date: Thu, 1 Jun 2006 09:58:35 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	format=flowed;
	charset="UTF-8";
	reply-type=original
Content-Transfer-Encoding: 7bit
Subject: Re: Question regarding extension function entries.
From: pollita@php.net ("Sara Golemon")

> According to all documentation I've found, a
> zend_function_entry[] array should be ended
> with { NULL, NULL, NULL }, but I've noticed
> that _zend_function_entry now has five parts;
>
Your analysis is correct, however(functionally speaking) the only attribute 
that NEEDs to be explicitly set NULL is fname.  The rest can be garbage and 
everything will still function fine.  The second and third elements are set 
NULL becasue they can be safely without losing version agnosticism.

We could extend the skeleton with a couple of zeros in those elements, but 
it'd need a note on the indavisability of doing that if you need BC with 4 
(the compiler would spit error about excess elements in initializer).

I'm all for a macro, maybe even a full start/end set like the 
global/ini/arg_info declarations have.  Again, there's version BC to be 
considered, but that can be solved with some #ifndefs in the skeleton...

PHP_BEGIN_FUNCTION_LIST(extname)
    PHP_FE(...)
    PHP_FE(...)
    PHP_FE(...)
PHP_END_FUNCTION_LIST(extname)

Same for the module entry....

These are all just window dressing though so unless someone else sees this 
as a worthwhile thing...*shrug*

-Sara