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
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
