Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:28302
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain smashlabs.com from 67.15.58.61 cause and error)
Message-ID: <45F07AA2.9060007@smashlabs.com>
Date: Thu, 08 Mar 2007 15:05:38 -0600
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.9) Gecko/20061207 Thunderbird/1.5.0.9 Mnenhy/0.7.4.666
MIME-Version: 1.0
To: internals <internals@lists.php.net>
References: <45F076AE.8010001@smashlabs.com> <45F07834.1020801@zend.com>
In-Reply-To: <45F07834.1020801@zend.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Class name clashing
From: ralph@smashlabs.com (Ralph Schindler)

Stanislav Malyshev wrote:
>> Is it still the position of internals that reserved words cannot be 
>> used as method names or class names?
> 
> Why allow it? It would probably require substantial change in the 
> parser, and what for?
> 

I guess so that we can have a language that will be able to model real 
world problems... instead of the real world changing the name of the 
problem to fit the language.

Its super frustrating when so many common words are marked as 'php 
scanner reservered' even when my context of use is completely different.

Or, how about creating a language thats always striving to be better.. 
With the adoption of PHP5 also comes the increased adoption of OOP.. and 
this issue is a speed bump.

Anyway, I write so that perhaps, maybe, just maybe, someone might want 
to see whats involved instead of simply writing off this request....

Thanks,
-ralph