Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:62166
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: <F5E021D8A355497C80E974B04320D375@pc>
To: "Stas Malyshev" <smalyshev@sugarcrm.com>,
	"Anthony Ferrara" <ircmaxell@gmail.com>
Cc: "Levi Morrison" <morrison.levi@gmail.com>,
	<internals@lists.php.net>
References: <A3182DBB9506422D9DCD5667BE48A0C4@pc> <CAFMT4NpOEFgDckOUdSx5x8h=H0a6FPubmyyPyvz-SMgxKgyhdw@mail.gmail.com> <CAAyV7nE-QTvXju3JayAaeLY1iDtUzWo6j+b66him11dzKAUKsw@mail.gmail.com> <502A86AA.2030203@sugarcrm.com>
Date: Wed, 15 Aug 2012 11:06:30 +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")

I'd like to also ask people to read what the intended effect of the proposal 
is instead of going into abstract discussions about how casting one class to 
another doesn't make sense (this is not what's being proposed).

Just like PHP typehints look like static typing but *aren't*, the same way 
the fact this looks like a static cast *doesn't* make it so. A dynamic 
language can't have static casts, and I'd think this is obvious to 
everybody.

Instead, I'm adapting the principle so it fits with existing PHP behaviors 
and patterns.

Syntax which looks like static typing is fine by me as well. Examples:

ClassName $foo = expression();

foreach ($list as InterfaceName $item) { ... }

etc.

The only operation done here is validating the variable is a valid instance 
of this type. No transformation is happening.

Stan