Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:60104
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain googlemail.com designates 209.85.217.170 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <CA+Ky_uOCVM1ALdTFJRVmFMwRbBzCJwj--_zxoCx2sq7y7vaAeg@mail.gmail.com>
References: <4F89D4F1.8070009@ralphschindler.com>
	<CA+Ky_uOofeE=A4S5JqZGTqYgaHy57LNoj3zJs1qcX1L5+SeoBQ@mail.gmail.com>
	<CA+Ky_uOCVM1ALdTFJRVmFMwRbBzCJwj--_zxoCx2sq7y7vaAeg@mail.gmail.com>
Date: Tue, 17 Apr 2012 21:41:01 +0200
Message-ID: <CAF+90c-PRL-U7rYOsD7++LFSNEq=XXOjs6Qbinz3MF9XUkn_yQ@mail.gmail.com>
To: Galen Wright-Watson <ww.galen@gmail.com>
Cc: internals@lists.php.net
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] New Feature: Fully qualified class name resolution as
 scalar with class keyword
From: nikita.ppv@googlemail.com (Nikita Popov)

On Tue, Apr 17, 2012 at 9:36 PM, Galen Wright-Watson <ww.galen@gmail.com> w=
rote:
>Would it be easy to have a patch that simply allows use of the class name,
> or is the "::class" suffix necessary to resolve some ambiguity? Example
> usage:
>
> =A0 =A0$mock =3D $this->getMock(A\Namespaced\**ClassName);
> =A0 =A0# or
> =A0 =A0use A\Namespaced\ClassName;
> =A0 =A0$mock =3D $this->getMock(ClassName);
>
> Would changing the definition for class_name_scalar be sufficient?
>
> =A0 =A0class_name_scalar:
> =A0 =A0 =A0 =A0class_name { zend_resolve_class_name(&$1, ZEND_FETCH_CLASS=
_GLOBAL,
> 1 TSRMLS_CC); $$ =3D $1; =A0}
> =A0 =A0;
>
> To my eye, this is the least surprising syntax.
In your above example ClassName could just as well be a constant :)

Nikita