Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:52047 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 44229 invoked from network); 28 Apr 2011 08:39:58 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 28 Apr 2011 08:39:58 -0000 Authentication-Results: pb1.pair.com smtp.mail=tyra3l@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=tyra3l@gmail.com; sender-id=pass; domainkeys=bad Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.215.170 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.170 mail-ey0-f170.google.com Received: from [209.85.215.170] ([209.85.215.170:34341] helo=mail-ey0-f170.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 62/23-28716-DD729BD4 for ; Thu, 28 Apr 2011 04:39:58 -0400 Received: by eyf5 with SMTP id 5so778670eyf.29 for ; Thu, 28 Apr 2011 01:39:55 -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=FLKs0Z0/BhmpyLneeAr6lAv5oMAvILDCGOlg9EfMnyg=; b=nNkebU8o7jtI/n+ctySC2at6uuTyqEiIJWhECE6nwmAvcs3/Qj3sqyiSpBMwL0w63x ptzy0qkIAashUH3Y9yNHNsrcCv3fm+6jImAoGdqkTs0y3HYaWmXqDb/PFm1N4THBfD4H ve/w9+vAEj7LMtfhH4dSZlL6hFZ1JrXolibjY= 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=df9DjgkxOIR0At/WbWl6QhJWxjBBirjd4f8RkJfjNdsTho/LYl9Jbm02QqDFWX1Umz 49cfZK97eavy4kw1jG8eE4/qIBa36HnuK/xf9xoIPSl93pmdC1gkH+wl471WSYw5nC8v P5tUuurhNBFI5qiXk4Q1oz8/DxQvKaKenNKKw= MIME-Version: 1.0 Received: by 10.14.148.67 with SMTP id u43mr1442236eej.7.1303979995048; Thu, 28 Apr 2011 01:39:55 -0700 (PDT) Sender: tyra3l@gmail.com Received: by 10.14.127.79 with HTTP; Thu, 28 Apr 2011 01:39:55 -0700 (PDT) In-Reply-To: <4DB923E6.3020307@sugarcrm.com> References: <4DB923E6.3020307@sugarcrm.com> Date: Thu, 28 Apr 2011 10:39:55 +0200 X-Google-Sender-Auth: D2oAW1QNUXKj3yRw49IyfY0dw6k Message-ID: To: Stas Malyshev Cc: Felipe Pena , internals Content-Type: multipart/alternative; boundary=bcaec51a7af8662a6804a1f68018 Subject: Re: [PHP-DEV] [RFC] Return type-hint From: info@tyrael.hu (Ferenc Kovacs) --bcaec51a7af8662a6804a1f68018 Content-Type: text/plain; charset=UTF-8 On Thu, Apr 28, 2011 at 10:23 AM, Stas Malyshev wrote: > Hi! > > http://wiki.php.net/rfc/returntypehint >>> >> for the upcoming 5.4 release, I think it would be extremely useful, even >> without the scalar stuff. >> > > > Personally, I see even less point in having strict return typing (please > stop using "hint" terminology, it confuses the whole matter, it's not "hint" > if it describes mandatory restriction on the data) than strict argument > typing. The RFC doesn't explain it either beyond "here how you can have some > nice errors". > But why would I want to see these errors? How they would make anything > easier or better? > -- > Stanislav Malyshev, Software Architect > SugarCRM: http://www.sugarcrm.com/ > (408)454-6900 ext. 227 > do you aware that without the scalar support, the return type hinting would behave just as "strict" as the argument type hinting is currently. http://php.net/manual/en/language.oop5.typehinting.php so maybe type hinting wasn't a good name at the first place, but we should be consistent with the current naming convention. Tyrael --bcaec51a7af8662a6804a1f68018--