Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:62186
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: <CAEKFTWWmER9FKsCW=3SzhZb16Gno-Xrd=zSSgQuPWStw_sSFeQ@mail.gmail.com>
References: <CAEKFTWWmER9FKsCW=3SzhZb16Gno-Xrd=zSSgQuPWStw_sSFeQ@mail.gmail.com>
Date: Wed, 15 Aug 2012 13:18:54 +0200
Message-ID: <CAF+90c-SBejveHxGD23CpgEz=zb_vbhfqkx35Q8=j9eXv9Y6Hw@mail.gmail.com>
To: Giedrius Dubinskas <d.giedrius@gmail.com>
Cc: internals@lists.php.net
Content-Type: text/plain; charset=ISO-8859-1
Subject: Re: [PHP-DEV] Proposal: use SomeClass::staticMethod
From: nikita.ppv@gmail.com (Nikita Popov)

On Wed, Aug 15, 2012 at 12:59 PM, Giedrius Dubinskas
<d.giedrius@gmail.com> wrote:
> Hello Internals!
>
> I'm just on and off luker here but thought I'll throw in an idea for a
> feature I'd love to see in PHP: aliasing static methods.
>
> Syntax would look something like this:
>
>   use Namespaced\SomeClass::staticMethod;
>   use Some\Foo::bar as fooBar;
>
>   staticMethod(); // would call Namespaced\SomeClass::staticMethod()
>   fooBar(); // would call Some\Foo::bar()
>
> This would make code more readable, by removing the the noise of
> repetition of class names. For use cases we can look at Java use cases
> for "import static".
>
> Aliasing class constants like that would also be very nice.
>
> What does everyone think?

I have the suspicion that you are just using static methods as a way
to group functions into a "namespace". If that's what you want, then
why not just use namespaced functions for that? Should be a lot less
confusing and also semantically more correct.

Nikita