Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:62143
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.215.42 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <A3182DBB9506422D9DCD5667BE48A0C4@pc>
References: <A3182DBB9506422D9DCD5667BE48A0C4@pc>
Date: Tue, 14 Aug 2012 07:51:20 -0600
Message-ID: <CAFMT4NpOEFgDckOUdSx5x8h=H0a6FPubmyyPyvz-SMgxKgyhdw@mail.gmail.com>
To: Stan Vass <sv_forums@fmethod.com>
Cc: internals@lists.php.net
Content-Type: text/plain; charset=ISO-8859-1
Subject: Re: [PHP-DEV] Inline typecasting / typehinting for classes and interfaces
From: morrison.levi@gmail.com (Levi Morrison)

On Tue, Aug 14, 2012 at 1:46 AM, Stan Vass <sv_forums@fmethod.com> wrote:
> I've felt the need for this for some time.
>
> 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.