Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:74748 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 37716 invoked from network); 4 Jun 2014 21:34:31 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 4 Jun 2014 21:34:31 -0000 Authentication-Results: pb1.pair.com header.from=johannes@schlueters.de; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=johannes@schlueters.de; spf=permerror; sender-id=unknown Received-SPF: error (pb1.pair.com: domain schlueters.de from 217.114.215.10 cause and error) X-PHP-List-Original-Sender: johannes@schlueters.de X-Host-Fingerprint: 217.114.215.10 mail.experimentalworks.net Received: from [217.114.215.10] ([217.114.215.10:47282] helo=mail.experimentalworks.net) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 0D/14-12394-5E09F835 for ; Wed, 04 Jun 2014 17:34:30 -0400 Received: from [192.168.2.31] (ppp-93-104-0-4.dynamic.mnet-online.de [93.104.0.4]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: johannes@schlueters.de) by mail.experimentalworks.net (Postfix) with ESMTPSA id E7FD73FF1C; Wed, 4 Jun 2014 23:34:27 +0200 (CEST) To: Nicolai Scheer Cc: PHP Internals In-Reply-To: References: Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="=-yohrZSXf6RpiNLaoStSC" Date: Wed, 04 Jun 2014 23:34:07 +0200 Message-ID: <1401917648.2282.175.camel@guybrush> Mime-Version: 1.0 X-Mailer: Evolution 2.30.3 Subject: Re: [PHP-DEV] zend_API.c - missing zend_update_property_resource From: johannes@schlueters.de (Johannes =?ISO-8859-1?Q?Schl=FCter?=) --=-yohrZSXf6RpiNLaoStSC Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Wed, 2014-06-04 at 21:52 +0200, Nicolai Scheer wrote: > Hi, >=20 > is it by itention, that there is no zend_update_property_resource in > zend_API.c (as of 5.5.12)? The reason most likely is that nobody needed it, yet. I also don't see the need right now: * resources are handled as zvals, thos can be passed by zend_update_property(). The other are just wrappers creating the zval first. * Usage of resources is discouraged, instead of a resource use an object (extend zend_object to store pointers etc.) > What is the usual and official way to add such a function and what can I = do > to make it happen? The typical case that a developer who has a need creates a patch and depending on impact and the developer's brevity pushes it, sends it to the ist or creates an RFC. Developers without karma can only do the later (or now somebody with karma) > If such a thing was added, would this be considered an api change - i.e. > the zend api number would be adjusted? Edge case. By strict rules yes, but there are enough previous examples where we added APIs. Depends on brevity and need as above ;-) johannes --=-yohrZSXf6RpiNLaoStSC Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (SunOS) iQEcBAABAgAGBQJTj5DPAAoJEH3sTmn8nIPXYmUIAMBA44VpB9RKsWC7Wdv/YaVQ J20FltbweIMjRRwKkhhr3LUYzXS9fk39nK8m+oHSGStevxX3kyFhDgPO/SmL/orA NLqzQ0I6ahcwLNAGGbV8zJGT+N9rm4xMS+hsAdb9HAe3pfhTZfRguE7ypkBBh9Gs 0/y1RxqXdPSSfklqlWOd6QMLqmMW4cR0uS16ENNsj/ImT4CLPSwXQz9qCQrgUK3y Nm0o1OTogrYOlhuETVss7kNTvGn+Fbj8gcno45vBSNmkzL6o//D8dbsCUbClm431 AW2EPuLw8c8Dr/uuhWynG2GLlgw1/7T6eFKOElnd5pUSEdWeiBUtIZRs3LrkvPU= =rEbH -----END PGP SIGNATURE----- --=-yohrZSXf6RpiNLaoStSC--