On Wed, Dec 14, 2011 at 11:14 PM, Stas Malyshev <smalys...@sugarcrm.com> wrote: > Hi! > > >> I believe he's referring to sys/time.h, but this introduces >> portability issues. If it were just unix, that would be one thing. >> But maintaining this and a Windows alternative, and I have no idea >> what that is, is not worth it IMO. > > > Yes, portability is questionable. Though if we had a good patch that allows > to do it, I don't think it would be too bad to have it. Even Unix-only might > be (again, if enough people need it) fine, if we could use the data properly > in timelib functions.
By portability it is not (only) about APIs, APIs wrapping is easy these days, even on Windows. But the actual problem is to get a consistent and constantly updated set of data, reliable data. Data that applications can use blindly on any platforms without having to worry about bad information, as long as they use the latest PHP or timezone release (via PECL for example). And that, as stated earlier, is why we should not provide any alternative as any other solutions failed so far. It is also even less important as Oleg's target is the developer environment. If a developer cannot set his TZ correctly in a php.ini or in his application on his development box, then something is wrong there, but not in php :) For production server, I would never ever suggest to use the system's TZ, no matter the OS/distros/etc.. Cheers, -- Pierre @pierrejoye | http://blog.thepimp.net | http://www.libgd.org -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
