Re: REQUEST_TIME change in PHP 5.4
| From: | Patrick ALLAERT | Date: | Mon, 26 Dec 2011 17:24:26 +0000 |
| Subject: | Re: REQUEST_TIME change in PHP 5.4 | ||
| References: | 1 2 3 4 5 6 7 8 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-57104@lists.php.net to get a copy of this message | ||
2011/12/24 Pierre Joye <pierre.php@gmail.com>:
> hi Ilia,
>
> Right but there is a clear BC break here. And yes I really don't like
> how datetime deals with that but it is how it is, and it is certainly
> the only case where it fails (or almost).
>
> On Sat, Dec 24, 2011 at 4:18 PM, Ilia Alshanetsky <ilia@ilia.ws> wrote:
>> Introducing additional server
>> variables just makes things inconsistent, especially this late in the
>> release cycle.
On one side there's a clear BC break which, according to the related
RFC, is to be considered as a blocker, on the other one, a strong and
valid argument regarding spreading additional server variables.
I'm not sure being late in the release process is truely a valid
argument for accepting a BC break.
Can't we make some compromise here like making all date/time
classes/functions work uniformly with ints and floats?
Working with date/time features based on $_SERVER['REQUEST_TIME'] is
certainly not something fancy!
Patrick