On Thu, 29 Sep 2005, Andi Gutmans wrote: > - In Israel the timezone DB changes every year (we start savings time on > different dates every year depending on the parliament decision).
That is incorrect. That was only upto and including 2004. Since 2005 there is a set-rule for it. > I see that > in your implementation this DB is taken from a table written in C. Are you > saying that this table isn't currently being used? Or would I have to update > that C table every year? Ofcourse the table is in use, otherwise it would not have been put in. > All sysadmins in Israel pretty much have an automated way of getting the > updated timezone file from a central distribution FTP server which they just > drop in automatically into the system. Not allowing this to work would be a > serious problem. Israel's probably not the only country with a dynamically > changing DB. Brasil is AFAIK the only other one. > Also, it would require us to roll new PHP versions whenever such > a company changes their DB. So if this is the case, irregardless we should > support the old approach. Or we create a PECL extension that you can install and if it is installed then it uses the timezone database from there. And yes, ofcourse I keep updating the timezone database in CVS as soon as a new one is out. > Anyway, please give some more insight so that the situation is clear. > As stated in my previous email, irregardless, as Wez pointed out having two > sets of APIs is probably a better idea so that everyone is happy. That also means that we're reintroducing about a 20 bugs again. Please remember that the whole idea *why* I started with it was that the code now is broken, even although it might seem to work fine for you. regards, Derick -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
