Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:42345
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 72.14.220.158 as permitted sender)
DomainKey-Status: bad
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:reply-to:sender:to:subject:cc:in-reply-to
         :mime-version:content-type:content-transfer-encoding
         :content-disposition:references:x-google-sender-auth;
        b=R0JaOKoBp5pt3vmRuBjRbo5p95RnUK17ZsMezfHo+lIHvOloNTzVT8hiExlIgQvdyP
         Xz+ROO4in7rigYEjGR1UB+Im5bcRwokVHJvIUyv4zKVOJF7yjBsX6ALxwB9K2lt4j7aU
         ImVHzz8BRq5N+0oGKAUf060j7WN1EiQLIySR8=
Message-ID: <b19eae4e0812190538x6600d8eexc7ab2c10ce0fd40f@mail.gmail.com>
Date: Fri, 19 Dec 2008 13:38:36 +0000
Reply-To: viroteck@viroteck.net
Sender: surreal.w00t@gmail.com
To: "Kalle Sommer Nielsen" <kalle@php.net>
Cc: "Nathan Rixham" <nrixham@gmail.com>, "Dave Ingram" <dave@dmi.me.uk>, 
	"=?ISO-8859-1?Q?Cristian_Rodr=EDguez?=" <crrodriguez@suse.de>, 
	internals@lists.php.net
In-Reply-To: <2dedb8a0812181823q53a3b464oc1e2e2bd37792f98@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <69.22.48223.7E389494@pb1.pair.com> <494A3B12.80509@dmi.me.uk>
	 <494ABFD8.2090406@suse.de> <494ACAA8.6080600@dmi.me.uk>
	 <494ACEAE.2090700@gmail.com> <494AD2AF.9000702@gmail.com>
	 <2dedb8a0812181823q53a3b464oc1e2e2bd37792f98@mail.gmail.com>
Subject: Re: [PHP-DEV] Q on Primitives
From: viroteck@viroteck.net ("Robin Burchell")

Just a random thought I have from reading over that:

Would it not be more 'natural' to change 'function' to indicate a
method with a variant return type, and allow e.g.

'int somefunc()' instead of 'function (int) somefunc()' to indicate an
int return?

It would be a bit more in fitting with traditional languages, and
definitely less typing.. it may require some parser modification,
though..?

(I'd also like to throw my +1 in for scalar type hints, and optional
type coercion for return values - this is something I have run into
annoyances with and blogged about in the past)

Thanks,
Robin Burchell

On Fri, Dec 19, 2008 at 2:23 AM, Kalle Sommer Nielsen <kalle@php.net> wrote:
> 2008/12/18 Nathan Rixham <nrixham@gmail.com>:
>> Nathan Rixham wrote:
>>
>> and strongly typed returns.. nearly forgot
>>
>> public static function parseByte( Number $var ):bool {
>> or
>> public static function bool parseByte( Number $var ) {
>>
>> or such like
>>
>
> Theres already an RFC for this:
> http://wiki.php.net/rfc/typehint
>
>
>
>
> --
> Kalle Sommer Nielsen
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>