Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:57072 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 40981 invoked from network); 24 Dec 2011 11:04:43 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 24 Dec 2011 11:04:43 -0000 Authentication-Results: pb1.pair.com header.from=pierre.php@gmail.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=pierre.php@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.161.170 as permitted sender) X-PHP-List-Original-Sender: pierre.php@gmail.com X-Host-Fingerprint: 209.85.161.170 mail-gx0-f170.google.com Received: from [209.85.161.170] ([209.85.161.170:41261] helo=mail-gx0-f170.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 26/28-16446-BC1B5FE4 for ; Sat, 24 Dec 2011 06:04:43 -0500 Received: by ggnv1 with SMTP id v1so7752180ggn.29 for ; Sat, 24 Dec 2011 03:04:40 -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:content-transfer-encoding; bh=8bz3LE6a4WH5Wx0FgLbYaE5Y+L8EhrOTOykA3C6mRF8=; b=aQQgD8YO9qfBMdz3lL6L9A9yTxshj5EWfwxmsDP0CpOEyz9/XXLNBZb2cLbTsjC8Q1 xhObwa6Y1aLn4aQy2GLoIepsKjzqOTnF0dseShS7lvC8T6jGgNL74nvynN9yZZlhNJ0A +iAVlVKku1+orgdex1iFublU/jPU93argn0KM= MIME-Version: 1.0 Received: by 10.101.164.19 with SMTP id r19mr7720774ano.58.1324724679739; Sat, 24 Dec 2011 03:04:39 -0800 (PST) Received: by 10.146.204.6 with HTTP; Sat, 24 Dec 2011 03:04:39 -0800 (PST) In-Reply-To: References: Date: Sat, 24 Dec 2011 12:04:39 +0100 Message-ID: To: =?ISO-8859-1?B?QW5kcukgUvhtY2tl?= Cc: internals@lists.php.net Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Subject: Re: [PHP-DEV] REQUEST_TIME change in PHP 5.4 From: pierre.php@gmail.com (Pierre Joye) hm, I should read better... "The REQUEST_TIME value inside server now returns a floating point number" How does it break BC except if one is doing a strong type test? which makes very little sense in this case. While a fix is easy, (int) casting and works with all previous versions, I would like to know how it breaks apps out there. On Sat, Dec 24, 2011 at 12:01 PM, Pierre Joye wrote: > hi, > > =A0I don't remember a change about it and did not check the log yet. > Would you mind to write here how it is broken please? It could help > the discussions :) > > But yes, if it has changed in an incompatible way, I'd to go with a > revert as well. > > Cheers, > > On Sat, Dec 24, 2011 at 11:13 AM, Andr=E9 R=F8mcke wrote: >> Hi, >> >> >> >> a bit late to the party maybe, but why was REQUEST_TIME broken in 5.4 >> instead of adding a new parameter? (like REQUEST_MICROTIME) >> Is the Release Process not followed yet? >> >> >> =A0 - x.y.z to x.y+1.z >> =A0 =A0 =A0- (...) >> =A0 =A0 =A0- Backward compatibility must be kept >> >> ( https://wiki.php.net/rfc/releaseprocess ) >> >> >> It is not a big deal (we are used to it), but it does break a couple of >> things in for instance eZ Publish & Zeta Components which will by the >> nature of things not be fixed before the next release. >> Most customers will hopefully make sure the version of the software they >> are using is tested/certified for php 5.4 before upgrading, but from >> experience, some will not. >> >> >> Other then that, happy xmas! > > > > -- > Pierre > > @pierrejoye | http://blog.thepimp.net | http://www.libgd.org --=20 Pierre @pierrejoye | http://blog.thepimp.net | http://www.libgd.org