Re: timezones & date() breakage
| From: | Markus Fischer | Date: | Wed, 28 Sep 2005 13:22:37 +0000 |
| Subject: | Re: timezones & date() breakage | ||
| References: | 1 2 3 4 5 6 7 8 9 10 11 12 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-19269@lists.php.net to get a copy of this message | ||
Hi,
Andreas Korthaus wrote:
Lukas Smith wrote:From my side it also about flexibility. The OO-Version is more flexible because you can derive your own class based on the internal date-class and provide additional features; not possible without it. - MarkusI 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.IMO date is a very good example where a nice OO API is very useful - particularly for people with advanced needs of date/timezone support. an example: $date_obj = date date_create(); date_timezone_set($date_obj, $timezone_obj); vs.: $date = new date; $date->setTimezone($timezone_obj);