Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:78629
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.216.49 as permitted sender)
MIME-Version: 1.0
Sender: are.you.winning@gmail.com
In-Reply-To: <0776A65F-D49A-4E8C-9771-6B5E5C4EA77E@ajf.me>
References: <002601cff777$eb923430$c2b69c90$@tutteli.ch>
	<CAFMT4NqJDcek6itqAUt2iOyHd2icc-tDdWsEjiRYvG1YFcc5cw@mail.gmail.com>
	<000601cff80a$972e0250$c58a06f0$@tutteli.ch>
	<5458937F.9020304@sugarcrm.com>
	<0776A65F-D49A-4E8C-9771-6B5E5C4EA77E@ajf.me>
Date: Tue, 4 Nov 2014 11:50:33 +0000
Message-ID: <CAGAGxbYhQ5iHdXnNk3vj33iapzV2A5NoYtCct1-=wbUb-oN+wg@mail.gmail.com>
To: Andrea Faulds <ajf@ajf.me>
Cc: Stas Malyshev <smalyshev@sugarcrm.com>, Robert Stoll <php@tutteli.ch>, 
	PHP Internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=001a1139838e1c63b3050707125d
Subject: Re: AW: [PHP-DEV] Types on the right or on the left
From: cw@daverandom.com (Chris Wright)

--001a1139838e1c63b3050707125d
Content-Type: text/plain; charset=UTF-8

On 4 November 2014 10:32, Andrea Faulds <ajf@ajf.me> wrote:

>
> > On 4 Nov 2014, at 08:51, Stas Malyshev <smalyshev@sugarcrm.com> wrote:
> >
> > I agree, this is not a very good situation. It would be much better to
> > take a systematic approach to this, but this is impossible since there
> > is no systematic approach to strict typing in PHP, just some pieces here
> > and there. I think this is not right, but obviously many people here
> > disagree and are happy to have the inconsistent syntax. I don't see why
> > "public Foo function bar()" would be so much worse than "public function
> > bar() : Foo"  but for some reason this possibility wasn't even
> > considered as far as I can see.
>
I thought it was inconsistent, but after discussions on StackOverflow, I
> don't think it actually is. Return types describe the return type of a
> function, not the type of a function. So there's no reason they have to go
> before the function name like parameter types do.
>
>
So, in a sentence:

In PHP, input types go on the left and output types go on the right.

This sounds like a convention that could be established and followed, and
no-one could reasonably call it inconsistent if it was adhered to.

--001a1139838e1c63b3050707125d--