I've said it twice in the past few days, but I guess with the flurry
of messages you've missed it.
I think it would be useful for the functionality inside the date
extension to go in, but it cannot go in as class date & class
timezone.
Why not?
These two classes need to be renamed if they are to go in
and I've proposed 2 different naming conventions just a few e-mails
ago. Perhaps if you were to vote on the names or second (or is it
3rd) Pierre' s proposal to shelf date until future releases we can
bring this discussion to some sort of a conclusion.
I already agreed with Pierre over this, and offered to support him in giving PEAR support for upgrading. So long as it goes in from the start of 5_3 branch, why not? (Like it should've done at the start of 5_2 already.) I think it's worth holding out for a few more months to get sane names in there - and the original names are the sanest, least confusing names.
- Steph