Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:89168
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain dasprids.de from 46.4.80.198 cause and error)
To: internals@lists.php.net
References: <56429DAB.6010005@dasprids.de> <AA.FC.21426.A26A2465@pb1.pair.com>
Message-ID: <5642A801.3050909@dasprids.de>
Date: Wed, 11 Nov 2015 03:29:21 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101
 Thunderbird/38.3.0
MIME-Version: 1.0
In-Reply-To: <AA.FC.21426.A26A2465@pb1.pair.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Re: Resource typehint and return type
From: mail@dasprids.de (Ben Scholzen 'DASPRiD')

On 11.11.2015 03:21, Andrea Faulds wrote:
> The reason for this is that the resource type is an anachronism from an
> age in which PHP did not have objects, yet still needed to make certain
> types of data opaque. The resource type is a type that exists only to
> shuffle around C pointers between internal functions. It has no semantic
> value. Because resources are now redundant, given the existence of
> objects, their time is running out, and they will be replaced at some
> point. Adding a type declaration for resource would mean that code using
> it would break if we replace any existing usage of resources with
> objects, preventing migration away from resource.

I see, I didn't really know about this. Although right now, we still use 
resources to pass around the fopen() pointers. Do you mean that it is 
planned to have a read/write object like we have in e.g. Python 
(supplied by the open() function)?

-- 
Ben Scholzen 'DASPRiD'
Community Review Team Member | mail@dasprids.de
Zend Framework               | http://www.dasprids.de