Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:52024 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 3806 invoked from network); 27 Apr 2011 09:52:28 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 27 Apr 2011 09:52:28 -0000 Authentication-Results: pb1.pair.com header.from=tyra3l@gmail.com; sender-id=pass; domainkeys=bad Authentication-Results: pb1.pair.com smtp.mail=tyra3l@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.215.42 as permitted sender) DomainKey-Status: bad X-DomainKeys: Ecelerity dk_validate implementing draft-delany-domainkeys-base-01 X-PHP-List-Original-Sender: tyra3l@gmail.com X-Host-Fingerprint: 209.85.215.42 mail-ew0-f42.google.com Received: from [209.85.215.42] ([209.85.215.42:35856] helo=mail-ew0-f42.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 33/22-20725-B57E7BD4 for ; Wed, 27 Apr 2011 05:52:27 -0400 Received: by ewy2 with SMTP id 2so468015ewy.29 for ; Wed, 27 Apr 2011 02:52:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=EvpHKQjWlj7pNua5rCEUKVWwEOnzg7duR/ZuCeDD7sk=; b=vomkgIW3Zd7oXDvFOoQytaE//6NoaowhJMQE1CcQf5NRBSy44owM0kMrCUKQRfh5ig ZQpYduc3ac40EnA2wcLYyZLutOay2XJ4N6LrhmY+irR47io2e7NDM8j5TOXql4UAaMZ1 qtijUFnmAHqeddRlvCGt1BMh7J3HaG33I2dgg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; b=fZVRHFoAKKz4OKQI0LrfE1rvbxcK8uQ72y5zZ2L6BclZzi7GUYlSq7aT17ed/9I6nL oZllR5hjh3RRFzEt0qaJ72qIj206WJwo2qPHw5RLCWtaPjSpNvUmRWrZwn7pLq4WIRZh eK+tNe+UcyL/YccesL+LSRKeo22nUCzukcFjU= MIME-Version: 1.0 Received: by 10.14.4.157 with SMTP id 29mr789913eej.135.1303897944454; Wed, 27 Apr 2011 02:52:24 -0700 (PDT) Sender: tyra3l@gmail.com Received: by 10.14.127.79 with HTTP; Wed, 27 Apr 2011 02:52:24 -0700 (PDT) In-Reply-To: References: Date: Wed, 27 Apr 2011 11:52:24 +0200 X-Google-Sender-Auth: chWJ-xC2CTEwiEj8BeIDz0LE8G4 Message-ID: To: Pas Cc: internals@lists.php.net Content-Type: multipart/alternative; boundary=001636416314cd77b004a1e3651d Subject: Re: [PHP-DEV] [RFC] Return type-hint From: info@tyrael.hu (Ferenc Kovacs) --001636416314cd77b004a1e3651d Content-Type: text/plain; charset=UTF-8 On Wed, Apr 27, 2011 at 11:29 AM, Pas wrote: > On Wed, Apr 27, 2011 at 09:23, Ferenc Kovacs wrote: > > On Thu, Jul 29, 2010 at 3:49 AM, Felipe Pena > 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 > >> > > > > 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 > > On Wed, Apr 27, 2011 at 11:29 AM, Pas wrote: > On Wed, Apr 27, 2011 at 09:23, Ferenc Kovacs wrote: > > On Thu, Jul 29, 2010 at 3:49 AM, Felipe Pena > 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 > >> > > > > 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 > > https://wiki.php.net/rfc/typechecking Ilia's proposal was implemented, then reverted, and Derick's proposal was commited, but judging from the mails on internals, this will/could bereverted from the next release. the other proposals was never implemented. ps: we have a(many) different thread for scalar type-hint discussion Tyrael --001636416314cd77b004a1e3651d--