Re: zend_API.c - missing zend_update_property_resource
| From: | Johannes Schlüter | Date: | Wed, 04 Jun 2014 21:34:07 +0000 |
| Subject: | Re: zend_API.c - missing zend_update_property_resource | ||
| References: | 1 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-74748@lists.php.net to get a copy of this message | ||
On Wed, 2014-06-04 at 21:52 +0200, Nicolai Scheer wrote:
> Hi,
>
> 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
Attachment: [application/pgp-signature] This is a digitally signed message part signature.asc
Attachment: [application/pgp-signature] This is a digitally signed message part signature.asc