Derick Rethans wrote:
gmdate() is for that, date() should always show a local time. The new
Local to who ;)
code (which is unfortunately not enabled), allows you do do all kinds of
timezone manipulation. Feel free to test it by setting your CFLAGS to
-DEXPERIMENTAL_DATE_SUPPORT and use the new functions following the
examples from the presentation.
I am building a calendar that requires the correct daylight saving
entries historically and ongoing. Will the new system support this or is
it purely designed to provide the current daylight saving setting -
which most sources I've tried to access seem to be limited to?
Providing a correct ongoing clock is one thing, but does not address the
real problem with timezones and daylight saving. When did they start,
what calendar do they follow, which setting do I use for - say - 2000 ?
Fortunately I have already stripped the date()/time() raw entries from
bitweaver and it uses getUTCTime() which means that only one routine
needs managing. Then the display routine works off the CLIENT selection
of time/daylight saving ;)
I just have not been able to correct the display of the CLIENT selection
for the calendar yet :(
--
Lester Caine
-----------------------------
L.S.Caine Electronic Services
Treasurer - Firebird Foundation Inc.
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
