Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:60106
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain ralphschindler.com from 209.85.160.170 cause and error)
Message-ID: <4F8DC9E1.5020909@ralphschindler.com>
Date: Tue, 17 Apr 2012 14:52:01 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:11.0) Gecko/20120327 Thunderbird/11.0.1
MIME-Version: 1.0
To: internals@lists.php.net
References: <4F89D4F1.8070009@ralphschindler.com> <CA+Ky_uOofeE=A4S5JqZGTqYgaHy57LNoj3zJs1qcX1L5+SeoBQ@mail.gmail.com> <CA+Ky_uOCVM1ALdTFJRVmFMwRbBzCJwj--_zxoCx2sq7y7vaAeg@mail.gmail.com>
In-Reply-To: <CA+Ky_uOCVM1ALdTFJRVmFMwRbBzCJwj--_zxoCx2sq7y7vaAeg@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] New Feature: Fully qualified class name resolution
 as scalar with class keyword
From: ralph@ralphschindler.com (Ralph Schindler)



> Would changing the definition for class_name_scalar be sufficient?
>
>      class_name_scalar:
>          class_name { zend_resolve_class_name(&$1, ZEND_FETCH_CLASS_GLOBAL,
> 1 TSRMLS_CC); $$ = $1;  }
>      ;
>
> To my eye, this is the least surprising syntax.

As far as I can tell, this rule will not compile as it conflicts with 
other rules, namely around the namespace implementation rules.

Besides that though, an original design goal was to implement it closer 
to how other languages solve the same-ish problem.  This solution is 
somewhat in line with Java (.class) and Ruby (.class.name), Python 
actually uses the same but instead of .class, they use .__class__.__name__

-ralph