Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:97897
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.161.175 as permitted sender)
To: Rasmus Schultz <rasmus@mindplay.dk>,
 PHP internals <internals@lists.php.net>
References: <CADqTB_gfRW6orcm8QXYSTz7iq=1ofv0RVf36=JsLeS7_6-R3LA@mail.gmail.com>
Message-ID: <b15fe9f4-0425-380d-b9a7-c769ec8e50dd@gmail.com>
Date: Fri, 20 Jan 2017 10:55:51 -0800
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0)
 Gecko/20100101 Thunderbird/45.6.0
MIME-Version: 1.0
In-Reply-To: <CADqTB_gfRW6orcm8QXYSTz7iq=1ofv0RVf36=JsLeS7_6-R3LA@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Not autoloading functions
From: smalyshev@gmail.com (Stanislav Malyshev)

Hi!

> Since the autoloading functions proposal is stalled, how about allowing for
> import of static functions instead?
> 
>     use function Foo::bar;
> 
>     bar(); // calls Foo::bar()

I'm not sure why it is good. This would certainly be confusing, if you
call strlen and turns out it's completely different function from what
you thought. One thing when it's the same namespace, at least you can be
aware what this package does, but if it's just an arbitrary function
from anywhere, it's really bad for understanding the code.

How hard is it to write Foo::bar? You never have to go more
than one level. I don't see a point in mixing internal function
namespace with class methods for the sake of saving typing couple of
characters.

-- 
Stas Malyshev
smalyshev@gmail.com