Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:89316
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain lerdorf.com designates 74.125.82.53 as permitted sender)
To: Phil Sturgeon <pjsturgeon@gmail.com>, Xinchen Hui <laruence@php.net>
References: <CAAyV7nG9E-7STWq2Hpe=y5Uf0nWzGMhka+FUX1p1FVNtYNVTJQ@mail.gmail.com>
 <112FFBCD-8445-40BC-B92F-3A97D3E97C4C@zend.com>
 <CAAyV7nE0bQba3Wr2yi8FbtDfDA=8ZSFz9dbQG5uZ+eF9bick2A@mail.gmail.com>
 <56523F74.9040708@lerdorf.com> <06a601d125c0$99d5cfd0$cd816f70$@belski.net>
 <CAL=_i_kArsu2JGYtdZBa-mah+k6DL-cCWtiX16mVcTsxH3WDrw@mail.gmail.com>
 <CABBJUpdTUwvdtK+uRc386R4pceocXCsSEd9s4bu4jvH87MD-8A@mail.gmail.com>
 <CABDNdAG84+cW9TohGbA2r0ik5=yrHVyAd5g2wk8dKRh=LeqvPQ@mail.gmail.com>
Cc: Joe Watkins <pthreads@pthreads.org>, Anatol Belski
 <anatol.php@belski.net>, Anthony Ferrara <ircmaxell@gmail.com>,
 Zeev Suraski <zeev@zend.com>, PHP internals <internals@lists.php.net>
Message-ID: <5652D782.40601@lerdorf.com>
Date: Mon, 23 Nov 2015 10:08:18 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101
 Thunderbird/38.3.0
MIME-Version: 1.0
In-Reply-To: <CABDNdAG84+cW9TohGbA2r0ik5=yrHVyAd5g2wk8dKRh=LeqvPQ@mail.gmail.com>
Content-Type: multipart/signed; micalg=pgp-sha1;
 protocol="application/pgp-signature";
 boundary="Q7KsMpeVc52Gngoe0aMA8k7QL1cspOMnT"
Subject: Re: [PHP-DEV] INDRECT in arrays causes count() to become
 unpredictable
From: rasmus@lerdorf.com (Rasmus Lerdorf)

--Q7KsMpeVc52Gngoe0aMA8k7QL1cspOMnT
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

On 11/23/2015 09:49 AM, Phil Sturgeon wrote:
> The "There will always be bugs" argument is a strawman, nobody is
> saying wait until it's perfect.
>=20
> People in this thread are consistently conflating "there will always
> be bugs" with "lets just ignore this bug which is 'around critical'
> and crack on because yolo."

You seem to be confused Phil. Nobody is arguing that this bug shouldn't
be fixed. The question is all about how severe it is and whether it
should trigger another release candidate.

-Rasmus



--Q7KsMpeVc52Gngoe0aMA8k7QL1cspOMnT
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)

iEYEARECAAYFAlZS14gACgkQlxayKTuqOuB5cACeJO6nLkHi8z8Zurw1zNPTTi7T
PiwAnjwy5yP5aZL5uL6jx2RpJOMCK6Iy
=QsaN
-----END PGP SIGNATURE-----

--Q7KsMpeVc52Gngoe0aMA8k7QL1cspOMnT--