Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:49161
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.212.42 as permitted sender)
DomainKey-Status: bad
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:from:date:message-id:subject:to
         :cc:content-type;
        b=uwbgfshN/hbORhT9pE/aACg0hR/SxBxMftTioS3PGNp7muFEo0dnF2lsqB521OTy+5
         XxUscGOkkkly5sFTmHlhUoqgkHMErCMRm2+tNl93t8v3f+uZDZSzV6jURF0NW/UO5rFD
         TxNqJj30Cfz6RwOnPyZiqXvZyrFZfjnDgxp0w=
MIME-Version: 1.0
In-Reply-To: <AANLkTim+SW7wM9U+eYTpyHWrg08_r49TABSxpoa_qVCm@mail.gmail.com>
References: <AANLkTimDdM4Udx53qW8jU4NuP3kU8+vmU6y4ZgXRVn+X@mail.gmail.com> 
	<AANLkTim+SW7wM9U+eYTpyHWrg08_r49TABSxpoa_qVCm@mail.gmail.com>
Date: Thu, 29 Jul 2010 09:47:38 +0200
Message-ID: <AANLkTi=eyqftrdnbVt+w2q9nrS=+DxNsRB8cL4Kf5+1n@mail.gmail.com>
To: Ferenc Kovacs <info@tyrael.hu>
Cc: Felipe Pena <felipensp@gmail.com>, internals <internals@lists.php.net>
Content-Type: text/plain; charset=UTF-8
Subject: Re: [PHP-DEV] [RFC] Return type-hint
From: daniel.egeberg@gmail.com (Daniel Egeberg)

On Thu, Jul 29, 2010 at 09:43, Ferenc Kovacs <info@tyrael.hu> wrote:
> On Thu, Jul 29, 2010 at 3:49 AM, Felipe Pena <felipensp@gmail.com> wrote:
>> Hi all,
>> I've updated the patch and the RFC that proposes the return type-hint
>> implementation (Engine + Reflection).
>> The proposed implementation is working just like the last changes in the
>> parameter type-hint (in trunk). i.e. working with the "scalar" and "numeric"
>> pseudo-types.
>>
>> http://wiki.php.net/rfc/returntypehint
>>
>> Thoughts?
>>
>> --
>> Regards,
>> Felipe Pena
>>
>
>
> Hi, I would love this feature.
> But I have some concerns.
> AFAIK you can declare classes with the name int ,scalar, etc. so
> hinting anything else than class names can be ambiguous.
> Or we have to set these keywords as reserved, so nobody could declare
> classes with such names.

Weren't they already made reserved with the parameter type hinting patch?

> But in this case, this would be a big BC problem, especially, because
> I think that there is many project out there which uses type
> names(int, object, etc.) as classname.
>
> Try to search "class Object{" or "class Object extends" on google codesearch.
>
> Maybe this was resolved with the last scalar type hinting patch, which
> got merged to the trunk, I don't know.
>
> ps: the spam filter rejected my previous email because of the
> codesearch links...
>
> Tyrael
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>



-- 
Daniel Egeberg