Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:57106 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 90856 invoked from network); 27 Dec 2011 03:19:12 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 27 Dec 2011 03:19:12 -0000 Authentication-Results: pb1.pair.com smtp.mail=pierre.php@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=pierre.php@gmail.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.213.170 as permitted sender) X-PHP-List-Original-Sender: pierre.php@gmail.com X-Host-Fingerprint: 209.85.213.170 mail-yx0-f170.google.com Received: from [209.85.213.170] ([209.85.213.170:61011] helo=mail-yx0-f170.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id B9/35-56324-F2939FE4 for ; Mon, 26 Dec 2011 22:19:12 -0500 Received: by yenl6 with SMTP id l6so7083991yen.29 for ; Mon, 26 Dec 2011 19:19:09 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=Vu/khn4up9gqhMyAVsXJXVLVPK8cb+RYenRVKXWsfDs=; b=muf2/uS5XTe/ftkTvwCPAptC40aJ7rz8G/js6xyIPNogKXlEcAU7nEW8sMuQB/jfUn pc2JbBfsXM3ZTRg8BP282J1EFgst7TxwsQ+6M8hWeLFvDVaj2bSHQu0eRjyqQmcMCAN2 YG0DCv1yGpZBuwI8ZW9gcQWU4s0804lMHp590= MIME-Version: 1.0 Received: by 10.236.127.144 with SMTP id d16mr36843114yhi.51.1324955949062; Mon, 26 Dec 2011 19:19:09 -0800 (PST) Received: by 10.146.238.8 with HTTP; Mon, 26 Dec 2011 19:19:09 -0800 (PST) In-Reply-To: References: Date: Tue, 27 Dec 2011 04:19:09 +0100 Message-ID: To: Patrick ALLAERT Cc: Ilia Alshanetsky , =?ISO-8859-1?B?QW5kcukgUvhtY2tl?= , David Soria Parra , Stas Malyshev , Derick Rethans , PHP Developers Mailing List Content-Type: text/plain; charset=ISO-8859-1 Subject: Re: [PHP-DEV] REQUEST_TIME change in PHP 5.4 From: pierre.php@gmail.com (Pierre Joye) hi Patrick, On Mon, Dec 26, 2011 at 6:24 PM, Patrick ALLAERT wrote: > 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! I tend to agree with you here, making date works smoothly with both would be the best way. However it requires more changes and work (and more risks) that simply add a new server variable. Cheers, -- Pierre @pierrejoye | http://blog.thepimp.net | http://www.libgd.org