Re: Re: date/timezone classes

From: Date: Fri, 08 Jul 2005 07:20:31 +0000
Subject: Re: Re: date/timezone classes
References: 1 2  Groups: php.internals 
Request: Send a blank email to internals+get-17189@lists.php.net to get a copy of this message
On Thu, 7 Jul 2005, Pierre-Alain Joye wrote: > The other are only duplicated with current function. This is maybe > useless. The worst being to rely on strtotime to manipulate date, > this is maybe human readable (understandable is another > question ;), but it is slooow, and the best way to hell for non > english application. I've been thinking about this, but the other way I could come up with is by passing a complex array instead of the textual description, something like: $modi = array('month' => 1); But then does that mean: next month, month 1 (january) or "first month"... I'm open here for other solutions, I just didn't find a better one that using strtotime() equivalent modifiers here. I also think that consistency is good :) > When we talked about a common object or resource in PHP, based on > what you did not read in pecl/date, it was about real transparency > throug methods able to work with date/time values. > > I suggest to make this enhancement in pecl/date. All the base is > already here. Right, one of the reasons that I made it an object, you can easily extend it there. > This is anyway a task post 5.1, for now your implementation has to > be bullet proofed until that (thinking about timezone and some > function like week number or other sources of annoyance). Week numbers work fine? Do you see a bug? If so, send me a reproducable script. Derick -- Derick Rethans http://derickrethans.nl | http://ez.no | http://xdebug.org

« previous php.internals (#17189) next »