Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:28313
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain php.net from 66.79.163.178 cause and error)
Message-ID: <45F1E453.6060102@php.net>
Date: Fri, 09 Mar 2007 16:48:51 -0600
User-Agent: Thunderbird 1.5.0.10 (Windows/20070221)
MIME-Version: 1.0
To: Stanislav Malyshev <stas@zend.com>
CC: Ralph Schindler <ralph@smashlabs.com>, 
 internals <internals@lists.php.net>
References: <45F076AE.8010001@smashlabs.com> <45F07834.1020801@zend.com> <45F07AA2.9060007@smashlabs.com> <45F07DE6.6070401@zend.com>
In-Reply-To: <45F07DE6.6070401@zend.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Class name clashing
From: cellog@php.net (Greg Beaver)

Stanislav Malyshev wrote:
> No it isn't. I can see no single serious reason why the class must be
> named Case or you have to move to Smalltalk or give up OOP altogether.
> It's a minuscule annoyance at best.
> 
>> Anyway, I write so that perhaps, maybe, just maybe, someone might want
>> to see whats involved instead of simply writing off this request....
> 
> What's involved is probably changing language parser, not sure even
> current flex/yacc combo can do it.

sure.  All that would be needed is a new rule for each keyword:

T_CLASS T_CASE

in addition to

T_CLASS T_STRING

PITA, but possible :).  Also possible with flex would be to enter a new
state when T_CLASS is found, and return T_STRING for any text.  However,
I wouldn't want to be the one who implements this, when you can simply
add a _ to the class name or use a longer descriptive classname like
"UseCase" or "CaseOfVodka" or whatever kind of "case" you're actually
modeling.

:)
Greg