Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:67102
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain wiedler.ch from 217.26.49.183 cause and error)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
In-Reply-To: <5170E1F8.9060203@sugarcrm.com>
Date: Sun, 21 Apr 2013 05:00:03 +0200
Cc: "internals@lists.php.net" <internals@lists.php.net>
Content-Transfer-Encoding: quoted-printable
Message-ID: <A914DA0F-50F6-49DE-A8F1-111010D49D0F@wiedler.ch>
References: <E1585E09-FB82-4486-9192-271A3947C8F3@wiedler.ch> <5170E1F8.9060203@sugarcrm.com>
To: Stas Malyshev <smalyshev@sugarcrm.com>
Subject: Re: [PHP-DEV] Importing namespaced functions
From: igor@wiedler.ch (Igor Wiedler)

> What's wrong with referencing one part of it? It can be as short as =
two
> characters, and an an added bonus you won't suddenly have your strlen
> overridden by somebody without you knowing it. Functions live in =
global
> space, and there's a real lot of them, that's why importing them =
wasn't
> considered a good idea - it's going back to the same problem we were
> escaping with namespaces.
>=20
> Saving two keystrokes while sacrificing clarity is usually not the =
best
> idea.

The same argument could be made for classes. Why import them if you can =
just
import the namespace? I think it reduces noise and allows imported =
functions
to be treated as an extension of the language. Without polluting the =
global
namespace.

As it stands, functions are a second class citizen in PHP. It is harder =
to use
them due to arbitrary restrictions that don't apply to classes.=