Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:74765
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain schlueters.de from 217.114.215.10 cause and error)
To: Nicolai Scheer <nicolai.scheer@gmail.com>
Cc: PHP Internals <internals@lists.php.net>
In-Reply-To: <CAOg_pRQKDs5km9wBKDoKHkZaJs-UfjGRmUmgNSc0GdMi8twRBg@mail.gmail.com>
References:
	 <CAOg_pRSWn_oxGio9mUN6TUEdwOA7opZfRBHearcdxxEs=Sbz+Q@mail.gmail.com>
	 <1401917648.2282.175.camel@guybrush>
	 <CAOg_pRQKDs5km9wBKDoKHkZaJs-UfjGRmUmgNSc0GdMi8twRBg@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
Date: Fri, 06 Jun 2014 00:26:19 +0200
Message-ID: <1402007179.2282.209.camel@guybrush>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] zend_API.c - missing zend_update_property_resource
From: johannes@schlueters.de (Johannes =?ISO-8859-1?Q?Schl=FCter?=)

On Thu, 2014-06-05 at 21:21 +0200, Nicolai Scheer wrote:
> >       * resources are handled as zvals, thos can be passed by
> >         zend_update_property(). The other are just wrappers creating the
> >         zval first.
> >
> 
> Of course it is no big deal to use zend_update_property and create the zval
> myself :)

I think you'd have to pass all arguments of ZEND_REGISTER_RESOURCE to
such a function. For that to work you'd need the resource type
identifier. (le_foo), which usually is static in a C file, thus you
could use it only in few cases, which seem unlikely to me considering
resources being discouraged (see below)

> >       * Usage of resources is discouraged, instead of a resource use an
> >         object (extend zend_object to store pointers etc.)
> >
> 
> Didn't know that usage of resources was discouraged... Nearly all my
> knowledge comes from Sara's great book (btw. if you read this Sara, I'd
> love to see and buy a refreshed version!) and my own field tests.
> When you say "use an object", do you refer to the way described in [1]?
> From what I've read so far, this way sounds more complex than just
> registering a resource.
> Could you elaborate a bit on the rationale behind this recommendation?

They are (incomplete list)

      * slower than objects for many operations
      * have an api with some weird behavior (some operations give
        errors which are hard to catch as extension author)
      * any people consider OO APIs nicer
      * resources can't be introspected by PHP level debuggers, var_dump
        etc. whereas objects can provide required hooks

(For the performance aspect I once created an extension for a quick
demonstration  http://marc.info/?l=pecl-dev&m=135774573910117&w=2
https://github.com/johannes/resvsobj )


> [1]
> http://www.phpinternalsbook.com/classes_objects/custom_object_storage.html

http://www.phpinternalsbook.com/classes_objects/custom_object_storage.html#overriding-create-object
is the relevant section.

johannes