Re: timezones & date() breakage

> Again and for the record in this thread, I told you and here many > times, the only safe way is to develop the new features in a separate > code base (ext/date was planned to be used for this exact purpose > before you decided to move your code there). A separate code base is > the only way to keep user codes working. Whether user codes were good > or bad is not relevant as they worked and there was not valid > alternative in the PHP releases. Can't this still be done? Call the new extension "datetime" or something and keep the old ext/date the way it is. A renaming process shouldn't be too problematic, right? If I had a say in this (and I don't), I'd say, keep ext/date and add another, more intelligent date/time extension. Ron