Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:23853 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 61995 invoked by uid 1010); 1 Jun 2006 16:26:43 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 61980 invoked from network); 1 Jun 2006 16:26:43 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 1 Jun 2006 16:26:43 -0000 X-PHP-List-Original-Sender: boards@gmail.com X-Host-Fingerprint: 64.233.162.192 nz-out-0102.google.com Linux 2.4/2.6 Received: from ([64.233.162.192:48837] helo=nz-out-0102.google.com) by pb1.pair.com (ecelerity 2.0 beta r(6323M)) with SMTP id 84/EA-07504-3451F744 for ; Thu, 01 Jun 2006 12:26:43 -0400 Received: by nz-out-0102.google.com with SMTP id m22so334012nzf for ; Thu, 01 Jun 2006 09:26:40 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:organization:user-agent:mime-version:to:subject:x-enigmail-version:openpgp:content-type; b=tHqWz3mFWUKRakdBx6tihm31dOEoLgDEnMSS2ZQuK6ldo/8yLW2Zt0WNOkYbZKafVZM0PTkhrxzrErz01U2K0B6c0uK68Oqr1N8FVkSvV0Xqw5RJ/aWleoVEupU9Io68fghMSPaXF5DD2LzO4PzJt9PxKI3xJNuhF37ra4AUT9M= Received: by 10.36.20.2 with SMTP id 2mr1219861nzt; Thu, 01 Jun 2006 09:26:40 -0700 (PDT) Received: from ?192.168.1.2? ( [71.228.25.94]) by mx.gmail.com with ESMTP id 17sm560265nzo.2006.06.01.09.26.39; Thu, 01 Jun 2006 09:26:39 -0700 (PDT) Message-ID: <447F154F.6070009@gmail.com> Date: Thu, 01 Jun 2006 11:26:55 -0500 Reply-To: boards@gmail.com Organization: LX User-Agent: Thunderbird 1.5.0.2 (X11/20060522) MIME-Version: 1.0 To: PHP Internals X-Enigmail-Version: 0.94.0.0 OpenPGP: id=5E6DE353 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig51E95A47743BCC5C8B001966" Subject: Question regarding extension function entries. From: boards@gmail.com (Matt Sicker) --------------enig51E95A47743BCC5C8B001966 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable 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; differences: -unsigned char *func_arg_types; +struct _zend_arg_info *arg_info; +zend_uint num_args; +zend_uint flags; Technically, it would make sense to end the array with five NULLs instead= of three, but that doesn't seem to be reflected by 'ext/skeleton/skeleton.c', so I don't know if it's a necessary change or not. If it should be changed, I'd also recommend making a macro for the ending so that this sort of problem won't pop up again in the future, and= it would also make more sense than just having seemingly random NULLs which could be better described with a macro. --------------enig51E95A47743BCC5C8B001966 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (GNU/Linux) iD8DBQFEfxVP5tcAKF5t41MRAoSTAJ9oySwfCWNG8+6H38MWqLtaK7BcWQCcCT2n zue2QI224IfVQ/C7nzV97zI= =sOQW -----END PGP SIGNATURE----- --------------enig51E95A47743BCC5C8B001966--