Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:67118
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.219.47 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <CACv1KMiOZz+f4recM4t3eOUGOGDhDAhiLFMsVKLwNz9D+SR+3g@mail.gmail.com>
References: <E1585E09-FB82-4486-9192-271A3947C8F3@wiedler.ch>
	<5170E1F8.9060203@sugarcrm.com>
	<A914DA0F-50F6-49DE-A8F1-111010D49D0F@wiedler.ch>
	<C05AB708-11D0-41B9-8242-76406E75C629@wiedler.ch>
	<000e01ce3ee3$597521f0$0c5f65d0$@tutteli.ch>
	<5174EE1C.2030002@anderiasch.de>
	<CACv1KMiOZz+f4recM4t3eOUGOGDhDAhiLFMsVKLwNz9D+SR+3g@mail.gmail.com>
Date: Wed, 24 Apr 2013 08:15:00 +0200
Message-ID: <CAEp07h-HVg+uYejyuq1eMZC03_mocUkv7szSn6+Dsd49C78FDg@mail.gmail.com>
To: Daniele Orlando <dnl.rlnd@gmail.com>
Cc: Florian Anderiasch <ml@anderiasch.de>, Robert Stoll <rstoll@tutteli.ch>, Igor Wiedler <igor@wiedler.ch>, 
	PHP Development <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=001a11c2f402c8199404db1538c9
Subject: Re: AW: [PHP-DEV] Importing namespaced functions
From: martin.keckeis1@gmail.com (Martin Keckeis)

--001a11c2f402c8199404db1538c9
Content-Type: text/plain; charset=UTF-8

Hello together,

if you got a namespace with more than one functions, why not just create a
container class and make the methods static?
I know it's not exactly the same, but how many times you need this....

So you can write:
namespace Abc\Def;

class Something{
    public static function blubb();

    public static function blubb2();
}


use Abc\Def\Something;

Something::blubb();
Something::blubb2();

Best regards
Martin




2013/4/23 Daniele Orlando <dnl.rlnd@gmail.com>

> +1
>
> The current behavior is really annoying.
>
>
> 2013/4/22 Florian Anderiasch <ml@anderiasch.de>
>
> > On 04/22/2013 12:55 AM, Robert Stoll wrote:
> > > I agree with Igor. The readability could be improved and I do not see
> the
> > > problem of hiding built-in php functions (however, I would not
> recommend
> > > it).
> > > I would say, if someone hides the normal php built-in function then he
> or
> > > she is doing that on purpose and is aware of the consequences. Thus it
> is
> > > also fine if the same person imports the function, which hides the
> normal
> > > php built-in function, in another namespace.
> >
> > Huge +1 from me.
> >
> > I know that using only functions instead of OOP in PHP has this
> > 90s-PHP3-Vibe to it, but as a matter of fact you can write mostly
> > side-effect free code using only functions in PHP.
> >
> > This would make using functions much more flexible and even more
> > importantly, consistent to everything else.
> >
> > The only downside to this proposal, as Stas correctly mentioned is that
> > it would allow people to shoot themselves in the foot when using weird
> > import behavior. But as you deliberately have to misuse this I don't see
> > any real harm. Something like instance variable shadowing in Java is
> > much, much more error-prone and still hardly anyone complains about this
> > kind of feature.
> >
> > Greetings,
> > Florian
> >
> > --
> > PHP Internals - PHP Runtime Development Mailing List
> > To unsubscribe, visit: http://www.php.net/unsub.php
> >
> >
>

--001a11c2f402c8199404db1538c9--