Hi Peter,
> You're describing the current behaviour; unless I'm missing something
> obvious, the warning is only displayed when you try to do something
> date-related. Your example script should not be presenting any warnings,
> regardless of the date.timezone INI setting or lack thereof.
>
>
you are right (I obviously missed some "hidden" [inside a library] date/time calls when
encountering this error).
This makes the following statement from Leszek interesting:
> Also, the check "if timezone not set show warning" would have to be shifted
> from initialization to call of each and every datetime function.
It seems, like this is the case then.
--
Cheers
Jannik