Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:72915
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain sugarcrm.com designates 108.166.43.107 as permitted sender)
Message-ID: <531675D6.1030203@sugarcrm.com>
Date: Tue, 04 Mar 2014 16:54:46 -0800
Organization: SugarCRM
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: "Shuhei Tanuma (chobie)" <chobieeee@php.net>, 
 Marc Bennewitz <php@marc-bennewitz.de>
CC: PHP internals <internals@lists.php.net>
References: <5307B1FE.1020604@marc-bennewitz.de> <CAGfRu7NGLvwQh-1R7tLpoxiPrqqya_Bpm+8_VvdxvhgviEf31A@mail.gmail.com>
In-Reply-To: <CAGfRu7NGLvwQh-1R7tLpoxiPrqqya_Bpm+8_VvdxvhgviEf31A@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] [php6] OOP resources
From: smalyshev@sugarcrm.com (Stas Malyshev)

Hi!

> I prefer resource as It makes easier to implement bindings.
> I've maintained several extensions. one of the library has 500
> approximates APIs.
> Imagine considering complicated OOP interface is really nightmare...

You don't have to do anything different there - you can still use the
same API. With minimal effort, you can also make the API dual-purpose,
i.e. foo_bar($foo, $bar) and $foo->bar($bar) would do the same. But it
doesn't have to be that, you can also stay with foo_bar($foo, $bar) and
have $foo as object.

> To encapsulate resource data structure to object isn't bad idea.
> but zend_list_insert is more convenient than
> zend_object_store_get_object, isn't it?

What would be the difference? It's pretty much the same API and macros
can be added to eliminate any boilerplate code. See how it's done in
intl, for example.
-- 
Stanislav Malyshev, Software Architect
SugarCRM: http://www.sugarcrm.com/
(408)454-6900 ext. 227