Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:52026
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.220.170 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:date:message-id:subject:from:to
         :content-type;
        b=tYF91mbFlTlRylo4avhBKt7sKcdhAUh5kjr7M5VqzAoQzEP4HUY60SufzMd5/yJtFp
         RTyH0TE85MdG+O1rXFGyotw+efDgZ7XTRUoQVgJI4TS/i0nDF2tooJUqy1Oq0xx/KUUN
         zYJJ1IrOA7IwCAYVU4gTbFsdhPYplk9bGtOXQ=
MIME-Version: 1.0
In-Reply-To: <BANLkTimzetTZ7FPQty9o1UAVN0-+ABPb0g@mail.gmail.com>
References: <AANLkTimDdM4Udx53qW8jU4NuP3kU8+vmU6y4ZgXRVn+X@mail.gmail.com>
	<BANLkTinMW_iqqOPJCuLnCB+-VEKxapPdGg@mail.gmail.com>
	<BANLkTimzetTZ7FPQty9o1UAVN0-+ABPb0g@mail.gmail.com>
Date: Wed, 27 Apr 2011 13:02:27 +0300
Message-ID: <BANLkTinQTk4GGe4LXAdLoaBPjePpaE=BYw@mail.gmail.com>
To: internals@lists.php.net
Content-Type: multipart/alternative; boundary=20cf307f354cb9ced204a1e3897d
Subject: Re: [PHP-DEV] [RFC] Return type-hint
From: arvids.godjuks@gmail.com (Arvids Godjuks)

--20cf307f354cb9ced204a1e3897d
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

There was no consensus on that, but as i remember the tendency was more to
the weak type hinting because of dynamic nature of PHP. You know - all the
http data comes as strings, most db data comes as strings and so on.
27.04.2011 11:30 =D0=BF=D0=BE=D0=BB=D1=8C=D0=B7=D0=BE=D0=B2=D0=B0=D1=82=D0=
=B5=D0=BB=D1=8C "Pas" <pasthelod@gmail.com> =D0=BD=D0=B0=D0=BF=D0=B8=D1=81=
=D0=B0=D0=BB:
> On Wed, Apr 27, 2011 at 09:23, 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 th=
e
>>> 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
>>>
>>
>> for the upcoming 5.4 release, I think it would be extremely useful, even
>> without the scalar stuff.
>>
>> Tyrael
>>
>
>
> Hi,
>
> Now that someone else necromanced this thread back to life, may I ask
> which variant of Type Hinting have emerged from the debate as the
> candidate for implementation?
>
> Also, I seem to remember a variant with both strict and weak type
> hinting/checking, using parentheses to distinguish behavior. What
> happened to that, never made it to an RFC?
>
> --
> Pas
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>

--20cf307f354cb9ced204a1e3897d--