Quick check so I completely understand where we are:
- In Israel the timezone DB changes every year (we start savings time
on different dates every year depending on the parliament decision).
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?
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. 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.
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.
Thanks,
Andi
At 12:13 AM 9/29/2005, you wrote:
On Wed, 28 Sep 2005, Andi Gutmans wrote:
> When I agreed to commit this for PHP 5.1, Derick promised that
this was going
> to completely keep BC. That is obviously not happening. While I
appreciate his
> efforts, I think as with the reference change, this will cause much more
> widespread pain than we can even imagine.
Uhm, the stuff that we agreed to commit has nothing to do with this, as
it's still disabled just fine.
regards,
Derick
--
Derick Rethans
http://derickrethans.nl | http://ez.no | http://xdebug.org
Zend/PHP Conference & Expo
Power Your Business with PHP
October 18-21, 2005 - San Francisco
http://zend.kbconferences.com/
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
