Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:89202
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: unknown (pb1.pair.com: domain php.net does not designate 212.27.42.2 as permitted sender)
To: Stanislav Malyshev <smalyshev@gmail.com>, Andrea Faulds <ajf@ajf.me>,
 internals@lists.php.net
References: <56429DAB.6010005@dasprids.de> <AA.FC.21426.A26A2465@pb1.pair.com>
 <56455965.60101@gmail.com>
Message-ID: <5645C1E9.8000206@php.net>
Date: Fri, 13 Nov 2015 11:56:41 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101
 Thunderbird/38.3.0
MIME-Version: 1.0
In-Reply-To: <56455965.60101@gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Subject: Re: [PHP-DEV] Re: Resource typehint and return type
From: francois@php.net (=?UTF-8?Q?Fran=c3=a7ois_Laupretre?=)

Hi,

Le 13/11/2015 04:30, Stanislav Malyshev a écrit :
> Hi!
>
>> 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
> I think more specific reason is not that resource type is outdated, but
> that resource is not really a type - it's a collection of types. Mysql
> connection is a resource, and file is a resource, but they are certainly
> not interchangeable. So typing a value as "resource" would not achieve
> you much.
>

I agree. Some resources may disappear in the future but others, like 
opened streams, are not obsolete at all.

As 'resource' is not specific enough. What about including the resource 
type in some way ? Something like '@stream', '[stream]', '{stream}' ? 
Just need to replace spaces with underscores (e.g. 'persistent_stream').

Regards

François