Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:68279
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain wiedler.ch from 217.26.49.185 cause and error)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
In-Reply-To: <49965DF5-CBB7-4B2A-9281-2D9E299E452C@strojny.net>
Date: Tue, 23 Jul 2013 00:51:11 +0200
Content-Transfer-Encoding: quoted-printable
Message-ID: <9499A8FF-93C4-4343-A701-8AEFF4ED4870@wiedler.ch>
References: <60BF8DD5-FEEA-47D9-834F-6C7FDEF3B879@wiedler.ch> <49965DF5-CBB7-4B2A-9281-2D9E299E452C@strojny.net>
To: "internals@lists.php.net" <internals@lists.php.net>,
 Lars Strojny <lars@strojny.net>
Subject: Re: [PHP-DEV] [RFC] Importing namespaced functions
From: igor@wiedler.ch (Igor Wiedler)

Hi Lars,

I don't really like the idea of such ghost features that don't actually =
do anything. It sounds like it would just introduce wrong mappings. And =
since those other constructs *do* share a namespace it technically =
wouldn't make sense to make a distinction between them.

Any other thoughts?

Regards,

Igor

On Jul 22, 2013, at 7:05 PM, Lars Strojny <lars@strojny.net> wrote:

> Hi Igor,
>=20
> I like the proposal but one cosmetic thing: if we allow "use function =
=85", shouldn't we allow "use class =85"/"use abstract class =85"/"use =
interface =85"/"use namespace =85" as well? It would be just syntactic =
sugar and not checked at all, but it would allow for nice symmetry in =
the use part of a file.
>=20
> cu,
> Lars