Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:62144
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain fmethod.com from 209.85.215.170 cause and error)
Message-ID: <11C69123FA4344AFAC538DD431AEFC61@pc>
To: "Levi Morrison" <morrison.levi@gmail.com>
Cc: <internals@lists.php.net>
References: <A3182DBB9506422D9DCD5667BE48A0C4@pc> <CAFMT4NpOEFgDckOUdSx5x8h=H0a6FPubmyyPyvz-SMgxKgyhdw@mail.gmail.com>
Date: Tue, 14 Aug 2012 18:29:18 +0300
MIME-Version: 1.0
Content-Type: text/plain;
	format=flowed;
	charset="iso-8859-1";
	reply-type=original
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Inline typecasting / typehinting for classes and interfaces
From: sv_forums@fmethod.com ("Stan Vass")

>> Proposed syntax:
>> -------------------------
>>
>> $x = (InterfaceName) $container->service;
>
> I'm against this.  Let's be honest, how different is this that an
> optionally static type?
>
> InterfaceName $x = $container->service;
>
> To be clear, I WANT optionally static typing. For the most part,
> type-hinting in class methods solves the static typing needs, but if
> we were able to declare a class member to be a certain type that would
> be another significant improvement.  I have a proposal in the works,
> but I don't want to hijack your thread.
>
> To sum up: I think we need something LIKE what you are proposing, but
> I'm against this particular proposal.

What you want is option 4 under my alternative syntaxes section :)

I'm ok with syntax 4, in fact, the more I think about it, the more I prefer 
that one (the one you want).
I don't mind the syntax as much, I want the feature.

Stan