Hello Matthias, i think you didn't understand the whole point here. Naming something after an every day word just like 'Date' is like screaming for problems in bigger scenarios. It is a beginners mistake to not prefix such stuff. And if you weren't in a big project - well then simply rename your few hundred lines of code. Use some nice tools like Ultraedit since your a windows user the renaming is only a few clicks a way.
marcus Friday, November 25, 2005, 12:39:45 PM, you wrote: >> I didn't say that my code is more important, but if we don't >> get the date class now, we will get it in 5.1.1 and then >> break your code - so that doesn't really matter. THe only >> correct solution is to start prefixing the pear date class, >> as that needs to be done in the long run anyway. > Derick, this is not only about the PEAR date class but about pretty much > every larger PHP codebase/project. You don't seem to understand the > impact. >> No no, the core reserves the right to name whatever they >> want, it's the userland code that is responsible for >> prefixing their classes. > Actually I just decided to work through my 100,000 lines of code and > rename every class; for the sake of forwards compatibility, I'll > generate GUIDs for each class and keep a mapping table on my desktop. > Oh, and while I'm at it, I'll switch over to some other language as > well. > -mp. > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php Best regards, Marcus -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
