Derick Rethans wrote:
You should prefix your classes in the first place, as per: http://www.php.net/manual/en/userlandnaming.php especially point 1 of: http://www.php.net/manual/en/userlandnaming.rules.php
In the end (After reading the page on smalltalk), I concede. Stanislav makes some excellent points.. and while this is an annoyance, I agree I can (as well as other developers) be a little more creative in class/method naming to not find themselves in an issue with clashing.
That being said: I still think there exists validity in figuring out if adding a layer of 'user context' to the tokenizer/parser would be an interesting project. I would be interested to see if a) it could be done, and b) if it could be done with minimal impact on performance.. Which I have to say, is a key reason I have chosen PHP as a devlopment platform.
I also think having a context aware parser/tokenizer would segue into namespacing, which I have also heard could be a feature in the future of PHP..
Either way, I am dropping this for now, but perhaps when I can dedicate some time to the 'C frame of mind', I'll start poking around in php-source again.
In any case, thanks, -ralph -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
