Bug #40213 [Com]: easter_date() returns wrong timestamp if ...

Edit report at https://bugs.php.net/bug.php?id=40213&edit=1 ID: 40213 Comment by: pierre dot renaudet at gmail dot com Reported by: oliver dot block at lycos dot de Summary: easter_date() returns wrong timestamp if ... Status: Suspended Type: Bug Package: Calendar related Operating System: Linux PHP Version: 5.2.1RC3 Block user comment: N Private report: N New Comment: I have add a Patch, to consider TimeZone. But Maybe Move ext/Calendar into ext/date will be more ogical... Previous Comments: ------------------------------------------------------------------------ [2007-03-06 19:10:51] oliver dot block at lycos dot de But it saves a lot of time and work. - I've feared that it may not convince you.:) ------------------------------------------------------------------------ [2007-03-06 12:11:37] tony2001@php.net Naaah, calling mktime() with call_user_function() is just a hack, not a solution. I've said we probably need to rewrite it from scratch and merge it into ext/date to use ext/date _internal_ functions directly, not through the user API. ------------------------------------------------------------------------ [2007-01-29 22:03:11] oliver dot block at lycos dot de I modified some of the testfiles from the former archives, because of wrong test results. It happens that easter date and DST shift occur on the same day. If so, date('Y-m-d H:i:s', easter_date($year)) will return a time portion of 01:00:00 and not 00:00:00 You find the archive here: http://www.block-online.eu/phptests/tests_easter_date.tar.gz ------------------------------------------------------------------------ [2007-01-25 21:04:02] oliver dot block at lycos dot de You will find the diff file here now: http://mitglied.lycos.de/oblock/php/easter.c.diff.gz ------------------------------------------------------------------------ [2007-01-25 20:20:22] bjori@php.net 404 not found.. ------------------------------------------------------------------------ The remainder of the comments for this report are too long. To view the rest of the comments, please view the bug report online at https://bugs.php.net/bug.php?id=40213 -- Edit this bug report at https://bugs.php.net/bug.php?id=40213&edit=1