Well, if PHP integers are turned into int64 datatypes, there'd be more room to operate for dates (I read in Derick's PDF that 2^31 presents problems, and therefor abstraction by an object class helps out). Then an OO datatype for dates wouldn't be needed.
But on the other hand, I can't say I'd mind if a date becomes a new OO datatype, as long as there's some point to it. Wherever this discussion goes, it seems to be the case that if the current situation needs to be changed (and apparently a lot of people feel it should), this could really get in the way of a PHP5.1 release date. Just something to remember. I wouldn't mind too much if PHP5.1 is postponed a little if quality is increased by it, but I'm sure some others will disagree. Ron "Edin Kadribasic" <[EMAIL PROTECTED]> schreef in bericht news:[EMAIL PROTECTED] > Lukas Smith wrote: > > Andreas Korthaus wrote: > > > >> People needing the new features (like me) would be happy if old > >> date/time behave the same as before 5.1, and if there is a new OO > >> interface for the new extension. > > > > > > I dont see a pressing need for an OO API and I also dont think that PHP > > internal API's should one by one be moved over to an OO interface either. > > I think the point is to have date() working as it was, and have a *new* > extension for all the fancy stuff (including OO). > > Edin -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
